Initial draft of Alligator Interop spec #285
Conversation
corydickson
requested review from
protolambda,
tynes,
ajsutton,
sebastianst and
mslipper
as code owners
|
|
||
| # Overview | ||
|
|
||
| The goal of this specification is to allow interoperability between the base and superchains for that use the [`Alligator`](alligator.md) predeploy. This allows the support of the |
There was a problem hiding this comment.
One common misconception is that each chain is called a superchain, but really the superchain is made up of individual chains. What do you mean the base here?
There was a problem hiding this comment.
Explicated the use of other OP chains that are not mainnet and their interaction with the Alligator contract
| the new storage field and update the voting power of the delegate. | ||
|
|
||
| ```solidity | ||
| function afterTokenTransferInterop( |
There was a problem hiding this comment.
Can we just add this to afterTokenTransfer instead of having 2 functions? ie update the post hook?
There was a problem hiding this comment.
Done, updates now only happens if the contract is deployed on OP mainnet
| nativeChainId := chainid() | ||
| } | ||
|
|
||
| if (nativeChainId != uint256(10)) { |
There was a problem hiding this comment.
This is not going to be scalable as every token transfer on a remote chain will require a relayer to send a transaction on op mainnet. This means gov will need to front the costs here because nobody else has the incentive to do so. Wondering if there is a way that we can:
- send batched diffs
- not need to be aware of the chainid
Going to brainstorm a bit on this
|
|
||
| uint256 nativeChainId; | ||
| assembly { | ||
| nativeChainId := chainid() |
There was a problem hiding this comment.
You can do block.chainid in modern solidity
|
I believe there has been a lot of progress on this that has not yet been specified |
This adds the additional specification to allow interop functionality to the
Alligatorcontract: #247