¿Cuáles son las nuevas reglas para cuando se destruye un KT1?¿O cuando se debe usar "--burn-cap" para enviar fondos a una cuenta tz1 / tz2 / tz3?

Apartir de 003_PsddFKi3:

Una cuenta originadaespara siempre. ^{[ 1 ]}

Se 'asigna' una cuentaimplícita ^{[ 2 ]} y 'eliminado' ^{[ 3 ]} ya que su saldo sube y vuelve a cero (sinoes un delegado ^{[ 5 ]} 5 ] gitlab.com/tezos/tezos/blob/366f64f3df266cf02a06412d6760f73626d0a2bf/src/proto_003_PsddFKi3/lib_protocol/src/fees_storage.ml#L61 "rel="norefer>sup [<> 6 "https://gitlab.com/tezos/tezos/blob/366f64f3df266cf02a06412d6760f73626d0a2bf/src/proto_003_PsddFKi3/lib_protocol/src/fees_storage.ml#L82" rel=> 7 ]norefersup >

El --burn-cap le dice al cliente quétan alto (entez)está dispuesto aestablecerel storage_limit (enbytes). Debeproporcionarlo cada vez queel storage_limit seapositivo,para confirmar queestá dispuesto agrabareltez. ^{[ 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 the storage_limit (in bytes). You must provide it any time the storage_limit will be positive, to confirm you are willing to burn the tez.^[8]

No creo que una dirección se destruyanunca.Tienes quegrabar XTZpara crear una dirección.

I don't think that an address gets ever destroyed. You have to burn XTZ in order to create an address.