Arc Mainnet is launching soon!
Want to be active from Day 1? Bookmark these:
• OTC: unstableotc .com
• Bridges: @lifiprotocol & @StargateFinance
• DEX Tracker: ArcDEXScan
• DEX: @TowerExchange
• Explorer: https://t.co/wBMt6cpGiL
• Faucet: https://t.co/Q210Yd0vSD
• App Kit: https://t.co/IxBDB97dcB
Save this now and be ready when mainnet goes live. 🔥
Looks like Across Protocol deploying their Arc chain bridge infrastructure
Details:
- SpokePool (0x9b4A302A...): the main bridge contract on Arc. Users deposit here to bridge out, and receive funds here when bridging in.
- SP1Helios (0x3baD7AD0...): a ZK light client that proves Ethereum state on Arc. This is how Arc verifies that something actually happened on mainnet without trusting a third party.
- Safe (0xd396CcB6...): a 5-of-5 multisig wallet for the team to manage the deployment. The 3-of-5 threshold means any 3 of the 5 listed owners must sign to execute transactions.
Arc isn't in the standard Safe deployment registry, so the team had to add a workaround the --use-canonical-infra flag and the canonicalSafeInfraAddresses.json file.
his manually provides the Safe contract addresses instead of looking them up from the registry, since Arc is too new to be included.
[CHAIN_IDs.ARC]: {
cctpV2TokenMessenger: "0x28b5a0e9C621a5BadaA536219b3a228C8168cf5d",
cctpV2MessageTransmitter: "0x81D40F21F12A8F0E3252Bccb954D722d4c464B64",
},
TROLL IS KING.
Also love seeing the dex screener screenshots lately on the TL.
$TROLL got one of the sexiest banners in the game if I do say so myself 😎👍
as we prepare to set sail to @opensea, a note on the wrap contract. 🦄✨
when we deployed it, duplicate (''twin'') protection was included. the intention was right but the execution created a problem we couldn't ignore.
holders who acquired duplicate objects on Peg2Peg did so in good faith. locking them out permanently through no fault of their own wasn't something we were willing to do.
more importantly - deciding which objects can and cannot wrap is centralised interference. the moment we arbitrate validity, we become the thing this project was built to avoid.
the mechanism already handles this. duplicate objects share visual traits. they do not share IDs. different IDs. different Eras. different histories.
It’s simple: the lower the ID, the older the object. age is the one thing no duplicate can replicate.
twin labels will be added to Peg2Peg for any objects that share a visual seed. use it as a reference.
every uPeg can wrap, and then market sorts it out, as it always does. 🦄