TeaBag

mainnet @arc somebody is already buying usdc on arc for 40$ to catch a runner on a new chain. so here is deep dive on whats going on there BitGo appears to have leaked a working Arc mainnet RPC while fixing a failed CI deployment. the network is supposed to be private right now, but this endpoint answers public JSON-RPC calls: rpc.blockdaemon.mainnet.arc.… it returns: > chain ID 5042 / 0x13b2 > client reth/v1.11.3 > live peer connections > 10m+ produced blocks the cleanest way to reconstruct the rollout is to walk through GitHub chronologically, then verify every useful artifact onchain > may 10 - Arc mainnet enters Chainlist. Chainlist merges an Arc mainnet config with chain ID 5042. commit: github.com/ethereum-lists/ch… this only proves the network metadata existed. it does not prove the chain was producing blocks yet. but 2 days later, the genesis timestamp hits > may 12 - genesis @circle 's published genesis.json is timestamped May 12. the file itself reached the public arc-node repo later, so the precise wording matters: genesis is dated May 12, while the next block appeared on May 15 github.com/circlefin/arc-nod… the config reveals a lot: > chain ID 5042 > 500ms target block time > 30m gas limit > native USDC gas > 11 genesis validators > permissioned validator manager > predeployed USDC, Permit2 and Multicall > admin, pauser, controller and validator roles by July 13, Arc had already produced more than 10m blocks > may 26 - @Uniswap deploys V2, V3, V4, Universal Router and the supporting contracts. deployment manifest: github.com/Uniswap/contracts… human-readable deployment: github.com/Uniswap/contracts… Arc is unusual because its native gas asset is not ETH, WETH or even ARC it is USDC that sounds simple until every EVM assumption starts expecting ETH-shaped plumbing. routers, wallet logic, gas estimation, token pickers, wrapped-native abstractions and bridge interfaces all need special handling some of the repos involved in the Arc rollout literally contain Claude or Cursor co-author metadata while teams work through these edge cases the final Uniswap deployment used 19 transactions with no reverts ownership was later handed to a 3-of-5 Safe, which looks much more like a coordinated production rollout than a random devnet deployment the public economy is still basically switched off, though. the 2 V2 pairs I found are ArcSmokeA / ArcSmokeB smoke tests rather than real markets. contracts live, liquidity absent Ю june 1 - @Morpho adds Arc to its Blue SDK using addresses from its deployment repo github.com/morpho-org/sdks/c… the commit is refreshingly explicit about one Arc quirk: there is no real wrapped-native token because USDC is the gas asset. Morpho Blue bytecode is also present on Arc mainnet, so this is more than an SDK enum still, deployed lending infrastructure does not automatically mean active markets, deposits or yield. those are separate things > june 2 - @lifiprotocol, the team behind @jumperapp , merges Deploy Arc mainnet core setup github.com/lifinance/contrac… the config exposes: > RPC arc-rpc.transferto.xyz/ > explorer explorer.arc.io > LI.FI Diamond 0xA4072583658Fae592A3506A42431cb6316a8d40b the explorer and that RPC have been access-controlled, which fits the private rollout > june 3 - @MetaMask first adds Arc to its internal asset and network tooling. then the integration keeps getting deeper: june 3 - Arc enters the Asset Controller june 9 - Arc enters the Bridge Controller june 12 - MetaMask Extension enables Arc mainnet for Swap/Bridge june 24 - MetaMask Mobile adds Arc through a persisted-state migration extension commit: github.com/MetaMask/metamask… mobile commit: github.com/MetaMask/metamask… the mobile implementation is the interesting part. it injects Arc into existing wallets using: arc-mainnet.infura.io/v3/${INFURA_PROJECT_ID} if a user already has MetaMask's popular-network mode enabled, Arc can be inserted as an enabled network automatically that is a distribution switch sitting inside one of the largest wallets in crypto public launch day may not require users to find a leaked RPC, paste a chain ID and pray. the wallet rails are already being prepared for them > june 3 - @worldnetwork ID deploys its identity stack this is the sleeper integration World ID, the identity protocol associated with Sam Altman's World project, deploys a verifier, permissioned gateway and WorldID Satellite on Arc mainnet the deployment is timestamped June 3 and appears in GitHub on June 9 under the very direct title: wip: deploy arc mainnet github.com/worldcoin/world-i… I checked every address through the leaked Arc RPC. all 4 have bytecode why does a stablecoin L1 need a proof-of-humanity stack before the public mainnet is even open? the straightforward answer is application infrastructure projects may want proof-of-personhood for sybil resistance, reputation, compliance-aware flows, grants, gated markets or fairer incentive distribution the spicier airdrop read is obvious, but it needs a giant caveat: there is no evidence that an ARC distribution will require World ID, and there is no confirmed ARC airdrop at all the deployment only proves that identity and sybil-resistant application primitives are already available on the private mainnet still, the timing is hard to ignore > june 8 - @LayerZero_Core marks Arc active LayerZero adds arc-mainnet, chain ID 5042, and V2 endpoint ID 30417. its deployment metadata marks the network active and includes V1/V2 infrastructure metadata.layerzero-api.com/v… once again, endpoint deployment does not mean there is a liquid public bridge route. but by this point the pattern is pretty clear: > the chain is producing blocks > DEX infrastructure is live > lending infrastructure is live > CCTP plumbing is configured > LayerZero endpoints are live > wallet distribution is being wired > identity infrastructure is deployed > june 23 - Circle updates the ARC whitepaper arc.io/arc-token-whitepaper the proposed initial supply is 10bn ARC: > 60% ecosystem > 25% Circle > 15% long-term reserve Circle describes a fee flywheel: > users pay fees in USDC > protocol-level mechanisms convert part of the fee > flow into ARC > part goes to stakers > part may be burned more network activity means more demand flowing through the ARC coordination layer the token is also supposed to handle staking, governance, validator economics, fee discounts and access across Circle and ecosystem services *we are here* Architect roles started appearing in the timeline today. the timing gets more interesting because Arc's next hackathon starts today Programmable Money runs from July 13 to August 22 as an online event - arc.io/community Circle has already shown that these events are not purely ceremonial. previous Arc tracks paid: > $10k USDC at HackMoney. 155 teams submitted > $15k USDC at ETHGlobal Cannes. 69 teams submitted HackMoney recap: arc.io/blog/meet-the-arc-tra… Cannes recap: arc.io/blog/meet-the-arc-tra… the projects Circle keeps rewarding are not generic fork-and-farm DeFi apps they usually sit around: > AI agents with their own wallets > x402 and nanopayments > stablecoin FX > crosschain treasury management > payroll and global payouts > RWA settlement > programmable escrow > agent-to-agent commerce at Cannes, 98% of submissions used AI agents 40% used Circle Nanopayments, and 4 of the 6 winners made nanopayments part of the core product the meta is not subtle Circle wants Arc to become the settlement layer for software that holds wallets, hires services and pays other software without a human clicking every transaction the whitepaper gives this theory some actual weight - 60% of the proposed ARC supply is reserved for the ecosystem so you say me to whom they'll distribute them and btw otc to buy a USDC on Arc for 40$ - unstableotc.com