jolestar
jolestar
We can improve documents based on the current version. > To general users * Introduction * Rooch * Rooch Network * Rooch Tech highlight * ... > To developers *...
We need to put it into the TxContext and do some refactoring. For simpler, we can maintain a random number sequence number in Move.
The `TransactionSequenceInfo` already in the TxContext https://github.com/rooch-network/rooch/blob/021a8ba0a88a255e14341e6e73c2b370a582a6ef/frameworks/rooch-framework/sources/transaction_validator.move#L130
> > rooch/frameworks/rooch-framework/sources/transaction_validator.move > > This function quotes from rooch_framework. Are we supposed to import rooch_framework move dependencies in MoveosStdlib toml pkg? Put the simple random module in the rooch_framework.
> How about generating random seed in Rust and stored in TxContext, and then read it in contract? It is unverifiable
> May the verifiable feature is not required unless we have consensus mechanism? The transaction needs to be synced to another executor or proposer node, so the execution result must...
A simple solution: 1. Let the sequencer generate a random seed and add it to `TransactionSequenceInfo`. 2. Include the `seed` in the data of the sequencer signature. 3. In the...
> Is the second issue `VRF on-chain` needing to be resolved? Make this TBD
list the table key/value via list_fields API
@vegetabledogdog already finish the list command