Content
@
0 reply
0 recast
2 reactions
scottrepreneur
@scottrepreneur.eth
I'm looking for a simple example of using `L1CrossDomainMessenger` to move tokens/NFTs for a @safe on L1 to the aliased address on the /op-stack. @bountybot 0.125 ETH or equivalent on L2 Success criteria: 1. Safe on L1 with aliased address on L2 2. NFT and/or ERC20 tokens in the aliased address on L2 3. Execute a tx cross-chain via Safe to move the NFT/token to any other address Demo can be on Sepolia and Base/OP Sepolia with a Safe you control. Specifically looking to understand the message required to execute this transfer on the L2 address. Base contracts https://docs.base.org/docs/base-contracts Possibly relevant docs https://docs.optimism.io/connect/resources/glossary#address-aliasing https://docs.optimism.io/builders/app-developers/tutorials/cross-dom-solidity
8 replies
4 recasts
15 reactions
Topocount
@topocount.eth
I dealt with this a few months ago but never actually needed to put it in prod: https://github.com/topocount/sona-protocol/compare/l2-bridge?expand=1
2 replies
0 recast
1 reaction
Topocount
@topocount.eth
Here is the L1 interface https://github.com/topocount/sona-protocol/commit/3b2e98dc959ed982c684e270f947bc8dcf7c4453#diff-64408c03c8ce1c4163dc38b37093407a0d546b9ee5fe537e28a252c87be907b7R172-R192
1 reply
0 recast
1 reaction
Topocount
@topocount.eth
Here is the part for L2: https://github.com/topocount/sona-protocol/commit/733585c050706d283085199e5ab59337e8b8811b#diff-19a91f58cbf82db969f92a11dde2f0d34e2be9c4480d8266160b73f78fe34c6a The trick here is setting up the compliant interface that the L2 bridge interacts with. Your use case should be possible to do with one tx if the addresses are the same for the safe on each chain.
1 reply
0 recast
1 reaction
