exit-format
exit-format copied to clipboard
Standard Exit Format for L2s built on EVM chains
See https://github.com/statechannels/go-nitro/pull/1082/commits/8c592080fff20cd9f64dac9fc17bd4822e4a3b67 This repo might be the best place to store similar structs in a variety of languages - ie, we do the same work describing the shape of the...
From #74, > this PR does not allow for fully qualified assets which are of type EIP-721 (nft) or EIP-1155 (multitoken standard). New combined types could be created to accommodate...
These should be left-padded with zeros.
Outside the scope of this PR, but somewhat higher priority because of it: we should specify how `executeSingleAssetExit` and `executeExit` behave when an asset transfer fails. I believe currently this...
For: - we use a monorepo; there's little point unless everything (or almost everything) lives inside - the usual upsides of a monorepo, including - we can make atomic commits...
* we already allow for the token type and the target channel outcome to be indexed in the transaction calldata, with an escape hatch, empty array `[]` implying "do them...
* is there an issue with reentrancy? * should the external contract call be `required` to succeed?