MiradaoJv
-
Sinalizar
como inapropriado
-
Mostrar
Show review history
Well, instead of making "reset", based on "throwing away the history", another change can be made: "demurrage". Which means locking coins on Scripts like that: Then, it will make things easier for pruned nodes, because after a given amount of time, coins can be moved by anyone, unconditionally (which means "swept by miners" in practice). And instead of OP_CHECKLOCKTIMEVERIFY, it is possible to also use OP_CHECKSEQUENCEVERIFY. It is just about the way of defining the timestamp. If there will be a consensus rule, that "all scripts should be considered as OP_TRUE, after some calculated timestamp", then it can happen automatically. As shown above, it is possible to make a Script, which will enforce it on top of existing networks. So, all that is needed, is just changing the code, used to execute all Scripts, to always wrap everything in that kind of "demurrage envelope" before executing, and then, it should work automatically. So, that kind of scripts can explicitly appear in "scriptPubKey", or consensus rules could be changed, to mimic that behaviour, on top of any "scriptPubKey", even if it would be "OP_FALSE" or "OP_RETURN" (only some restricted opcodes, like OP_VERIF will burn the coins in that case, and only if used as a raw scripts, because behind P2SH, or other hashed addresses, there could be some hash function collisions). Edit: P2SH will also expire in that case. The only burned coins would use OP_VERIF or similar opcodes as raw scripts, or when miners would claim less coins in the coinbase transaction (which is what Proof of Burn enthusiasts should use anyway, to not spam the UTXO set).
Well, instead of making "reset", based on "throwing away the history", another change can be made: "demurrage". Which means locking coins on Scripts like that: Then, it will make things easier for pruned nodes, because after a given amount of time, coins can be moved by anyone, unconditionally (which means "swept by miners" in practice). And instead of OP_CHECKLOCKTIMEVERIFY, it is possible to also use OP_CHECKSEQUENCEVERIFY. It is just about the way of defining the timestamp. If there will be a consensus rule, that "all scripts should be considered as OP_TRUE, after some calculated timestamp", then it can happen automatically. As shown above, it is possible to make a Script, which will enforce it on top of existing networks. So, all that is needed, is just changing the code, used to execute all Scripts, to always wrap everything in that kind of "demurrage envelope" before executing, and then, it should work automatically. So, that kind of scripts can explicitly appear in "scriptPubKey", or consensus rules could be changed, to mimic that behaviour, on top of any "scriptPubKey", even if it would be "OP_FALSE" or "OP_RETURN" (only some restricted opcodes, like OP_VERIF will burn the coins in that case, and only if used as a raw scripts, because behind P2SH, or other hashed addresses, there could be some hash function collisions). Edit: P2SH will also expire in that case. The only burned coins would use OP_VERIF or similar opcodes as raw scripts, or when miners would claim less coins in the coinbase transaction (which is what Proof of Burn enthusiasts should use anyway, to not spam the UTXO set).
This review was marked as helpful by
5 people
boa tarde
-
Sinalizar
como inapropriado
Well, instead of making "reset", based on "throwing away the history", another change can be made: "demurrage". Which means locking coins on Scripts like that: Then, it will make things easier for pruned nodes, because after a given amount of time, coins can be moved by anyone, unconditionally (which means "swept by miners" in practice). And instead of OP_CHECKLOCKTIMEVERIFY, it is possible to also use OP_CHECKSEQUENCEVERIFY. It is just about the way of defining the timestamp. If there will be a consensus rule, that "all scripts should be considered as OP_TRUE, after some calculated timestamp", then it can happen automatically. As shown above, it is possible to make a Script, which will enforce it on top of existing networks. So, all that is needed, is just changing the code, used to execute all Scripts, to always wrap everything in that kind of "demurrage envelope" before executing, and then, it should work automatically. So, that kind of scripts can explicitly appear in "scriptPubKey", or consensus rules could be changed, to mimic that behaviour, on top of any "scriptPubKey", even if it would be "OP_FALSE" or "OP_RETURN" (only some restricted opcodes, like OP_VERIF will burn the coins in that case, and only if used as a raw scripts, because behind P2SH, or other hashed addresses, there could be some hash function collisions). Edit: P2SH will also expire in that case. The only burned coins would use OP_VERIF or similar opcodes as raw scripts, or when miners would claim less coins in the coinbase transaction (which is what Proof of Burn enthusiasts should use anyway, to not spam the UTXO set).
This review was marked as helpful by
05 people
João Matheus
-
Sinalizar
como inapropriado
-
Show history of
Well, instead of making "reset", based on "throwing away the history", another change can be made: "demurrage". Which means locking coins on Scripts like that: Then, it will make things easier for pruned nodes, because after a given amount of time, coins can be moved by anyone, unconditionally (which means "swept by miners" in practice). And instead of OP_CHECKLOCKTIMEVERIFY, it is possible to also use OP_CHECKSEQUENCEVERIFY. It is just about the way of defining the timestamp. If there will be a consensus rule, that "all scripts should be considered as OP_TRUE, after some calculated timestamp", then it can happen automatically. As shown above, it is possible to make a Script, which will enforce it on top of existing networks. So, all that is needed, is just changing the code, used to execute all Scripts, to always wrap everything in that kind of "demurrage envelope" before executing, and then, it should work automatically. So, that kind of scripts can explicitly appear in "scriptPubKey", or consensus rules could be changed, to mimic that behaviour, on top of any "scriptPubKey", even if it would be "OP_FALSE" or "OP_RETURN" (only some restricted opcodes, like OP_VERIF will burn the coins in that case, and only if used as a raw scripts, because behind P2SH, or other hashed addresses, there could be some hash function collisions). Edit: P2SH will also expire in that case. The only burned coins would use OP_VERIF or similar opcodes as raw scripts, or when miners would claim less coins in the coinbase transaction (which is what Proof of Burn enthusiasts should use anyway, to not spam the UTXO set).
This review was marked as helpful
by 157 people
