You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With current EUTXO model, state machines inherit following properties
Utxo containing state variable must be consumed, and new utxo must be created every time even if state doesn't change.
Current state of state machine can only be used once per block because utxos can be consumed only once. (Note that it is possible that a person trying to use a state can never use it because of race condition. Some other transaction pops up and consumes the script utxo the person is interested in )
In most of the use cases, it is already clear that there will be states that will be read very frequently but changes are less frequent.
I suggest including a new field witness to ScriptContext.
Witness are the utxos that we are interested in but don't want to consume. The validation script at which the witness utxo sits will also be run during the transaction. In such utxos, usually we are interested in the datum field. Since witnessUtxos are not consumed, it possible to use the same utxo in multiple transactions in same block or future blocks, unless the utxo is consumed as input.
The text was updated successfully, but these errors were encountered:
With current EUTXO model, state machines inherit following properties
In most of the use cases, it is already clear that there will be states that will be read very frequently but changes are less frequent.
I suggest including a new field
witness
toScriptContext
.Witness are the utxos that we are interested in but don't want to consume. The validation script at which the witness utxo sits will also be run during the transaction. In such utxos, usually we are interested in the datum field. Since witnessUtxos are not consumed, it possible to use the same utxo in multiple transactions in same block or future blocks, unless the utxo is consumed as input.
The text was updated successfully, but these errors were encountered: