only 46,672.35 USDC exists across the entire @arc chain, yet 142 tokens are already PvPing for the same tiny liquidity bag
> 142 DEX-indexed tokens, up from 85 yesterday
> $ARCANINE: $14.9k mcap, $3.64k liquidity, 137 traders
> $NOAH: $5.9k mcap, $1.09k liquidity, 104 traders
> $BRC: $4.9k mcap, $641 liquidity, 78 traders
the token count exploded because launch rails are now cooking
@ArcDEXScan’s LaunchFactory deploys a fixed 1B-supply token, opens a 1% Uniswap V3 pool and seeds it in the same tx. creators can bundle the first buy before snipers enter. the LP NFT gets sent into a no-withdraw FeeSplitLocker, with trading fees split 70% to the creator and 30% to the protocol
54 of the 142 indexed tokens already came through this factory
@SharcFun added another rail with a @Pumpfun-style bonding curve quoted in native USDC and migration infra waiting behind it
so every launcher, sniper and early bag is currently farming the same 46.7k USDC inside a closed casino
but casino may become public very soon - someone burned 2 USDC on Base through Circle’s Bridging Kit. 1.982753 native USDC landed on Arc four seconds later
Base burn:
https://t.co/afAz53nwoO
Arc mint:
https://t.co/gNWedbtnyy
Circle’s public Iris API still labels the message PENDING and @lifiprotocol still can’t return an executable quote
the pipe works. public access stays gated
once Circle flips the route for everyone, fresh stables flood in, the OTC premium gets nuked and every early Arc bag gets repriced against real outside liquidity
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:
https://t.co/0PHiGLQCM3
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:
https://t.co/tMGnq7jKce
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
https://t.co/vwrVEcKCXy
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:
https://t.co/X0mV7DPYay
human-readable deployment:
https://t.co/bc4W67FWU8
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
https://t.co/mYwrPQvk8I
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
https://t.co/zUhbnuS2dR
the config exposes:
> RPC https://t.co/NA6Ci26M7d
> explorer https://t.co/8Ddx9DHpfX
> https://t.co/BZL1VPpsBk 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:
https://t.co/N2FWKRjJjD
mobile commit:
https://t.co/7iRxhfor4L
the mobile implementation is the interesting part. it injects Arc into existing wallets using:
https://t.co/Iq97pwrq8c${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
https://t.co/d7BDlPORZJ
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
https://t.co/ZlasdWXVtU
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
https://t.co/ElkcTzbMLL
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 - https://t.co/GEywR4oJ0h
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:
https://t.co/QZb6jgzvL7
Cannes recap:
https://t.co/k8p1aNYii1
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$ - https://t.co/4XV3ryYBJm
would be glad to pivot back to the roots from @arc to @BNBCHAIN
oh wait...Tim told there are scammers operating on arc thats why i can't do it anymore. moreover, now you are pvping in trenches not only against other traders but against corporate bozos
-ev
Thanks for digging this up👇. Thought it was made clear.
I had no communication with the Giggle Team about the recent selling (of donated tokens), but @GiggleAcademy do have a rule-of-thumb to convert/sell most donated tokens to BNB near the end of each month. I don’t manage the address personally.
If you send or donate token to someone’s address, without any prior agreement or contract in place, don’t expect the receiving party to act according to your wishes, such as a burn. That just creates more work for the receiving party, which they have not agreed to do.
If you wish someone to interact by sending them coins, then be ready for that interaction to be a sell.
If you called it a donation, then expect them to use it. You should be ashamed to then say you expected them to burn it. How is that a donation then?
If you donate to @GiggleAcademy, they will sell, and use the proceeds to fund free education for kids all around the world, reaching more than a million kids in less than 2 years.
I support all meme coins. I might even buy (or sell) one or two in the next few weeks to test a few new things. May the best memes win! 🙏
so @arc are gonna freeze and blacklist your funds
tbh i don't really believe but i hope they'll do this to confirm once again that I don't need to waste my ADHD attention on corporate smart alecks like them or base who aren't worthy of making money off of me
if you already bridged to @arc - time to add some CAs to your watchlist. my choice:
1. $USDC - FatCatBatRatWifHat
CA: 0x0006ed5d37a9d6687d1ecc8b642ff9c4760d9a16
people falsely claim that 1st ever memecoin is arcanine because @ArcDEXScan shows that - they track when live USDC pool launched - thats exactly Arcanine. but 1st ever deployed og token is FatCatBatRatWifHat
> FatCat - block 10,460,249
> $ARCANINE - block 10,460,272. 12 sec later
moreover, currently wrong FatCatBatRatWifHat is pumped. 0xb94bfde76ea7cd55e8f63ae19fd7c74370e0f389 is sitting at $1.6m while og is at $600k
2. But if we are talking about the first Arc-native memecoin with a live USDC pool - its def Arcanine
> ARCANINE pool 0x6d8d…316d - first-seen block 10,458,871
> FatCat pool 0xefae…e7cd - block 10,460,252
CA: 0xf3715bf5c2de299f08b81180ffb739a8372a175f
everything else i like way less and with worse risk/reward
3. $BIRDIE - Posted by @chrisries this july
CA: 0x8e604ae97dda3deb77d9856606a8dc3135998fc4
4. $NOAH - first memecoin from @Noxa_Fi
CA: 0x1ed9306725b8b4ca1a1a56d32970e49e64c51dde
5. $BRC by @Brc_meme - DEX + Bridge, working infra
CA: 0x11c87c506acf3ea0799f8717127fe55a184f8efd
6. $MISCHA - @circle posted about this cat
CA: 0x6520feceeff3474020ebf9b59234575e94655ec2
buying at https://t.co/vbzoxduRVV
now shill your bags