KT1何时被销毁的新规则是什么?还是必须使用“ --burn-cap”向tz1 / tz2 / tz3帐户汇款?
2 个回答
- 投票数
-
- 2019-03-25
截至003_PsddFKi3:
一个原始帐户是永远的. [ 1 ]
"分配"了一个隐式帐户 [ 2 ] 和'deleted' [ 3 ] ,因为它的余额超过了零,回到了零(如果不是委托 [ 4 ] . >
当前,您必须为存储一个隐式帐户付出大笔的存储费用,删除后不予退款.操作的
storage_limit
会导致这种刻录(以及KT1的原始刻录和脚本的存储增长). [ 5 ] [ 6 =[sup < " https://gitlab.com/tezos/tezos/blob/366f64f3df266cf02a06412d6760f73626d0a2bf/src/proto_003_PsddFKi3/lib_protocol/src/fees_storage.ml#L82" rel="noreferrer"> 7 ]--burn-cap
告诉客户端您愿意将storage_limit
设置为多少(以字节为单位)(以字节为单位).您必须在storage_limit
为正数的任何时候提供它,以确认您愿意烧掉tez. [ 8 ]As of 003_PsddFKi3:
An originated account is forever.[1]
An implicit account is 'allocated'[2] and 'deleted'[3] as its balance goes above and back to zero (if it is not a delegate[4]).
Currently you must pay a storage burn to allocate an implicit account, and there is no refund upon deletion. The
storage_limit
for an operation accounts for this burn (along with the origination burn for KT1's, and storage growth for scripts).[5][6][7]The
--burn-cap
tells the client how high (in tez) you are willing to set thestorage_limit
(in bytes). You must provide it any time thestorage_limit
will be positive, to confirm you are willing to burn the tez.[8]-
我对上标链接感到惊讶,并想知道您如何做,直到看到您实际上不愿意输入sup html标签:)应该有一种更简单的方法!:)I was amazed by the superscript links and wondered how you did until i see you actually took the pain to type the sup html tags :) there should be an easier way to do that! :)
- 0
- 2019-03-25
- Ezy
-
-
我确实记得,过去的情况是,如果余额过低,合同将完全消失,但是隐性账户并没有遭受这种损失.现在,我似乎无法耗尽KT1使其消失.而且,似乎在某些情况下转移到隐性帐户会产生额外的费用–burn-cap吗?I do recall that used to be the case that contracts would be disappeared completely if the balance ever go too low, but that implicit accounts didnt suffer this. and now, it seems I cannot drain a KT1 such that it disappears. and also, it seems that in some cases is costs extra `--burn-cap` to transfer to an implicit account?
- 0
- 2019-03-24
- Bo Byrd
-
KT1被销毁时的新规则是什么?它会低于一定平衡吗?
tz1/tz2/tz3呢?我注意到有时必须使用
--burn-cap
进行汇款.为什么会这样?