Consumed (nonce, block_expiry_height) pairs are scoped to the verifying
contract, not to the signing key, so a random nonce is the choice that
stays safe when several keys sign for one contract; a lone key may count
instead. Draws from the platform's crypto.getRandomValues.
A uniformly random
u64for Operation.nonce.Consumed
(nonce, block_expiry_height)pairs are scoped to the verifying contract, not to the signing key, so a random nonce is the choice that stays safe when several keys sign for one contract; a lone key may count instead. Draws from the platform'scrypto.getRandomValues.