MAP Protocol September Monthly Report is here. • Added cross-chain support for Arc at the infrastructure layer, extending omnichain coverage to the stablecoin-focused chain • Upgraded the MAP Protocol Radar service with new event statistics and query interfaces • Improved sync-stall detection to reduce false reconnects • Modernized containerized delivery with multi-architecture Docker/GHCR pipeline • $95.2M cross-chain volume over the last 30 days Full report 👇🏻 medium.com/mapprotocol/map-p…

Users shouldn’t have to know the route.
They should just know the asset moved.

Monday. Same chains. Same work.

✅ MAP Protocol Mainnet is back online. Maintenance has been completed and all related services have been restored to normal. Thank you for your patience and understanding.

📢 MAP Protocol Mainnet Maintenance Notice MAP Protocol mainnet is currently undergoing maintenance, and related services have been temporarily suspended. Our team is working to restore normal operations as soon as possible. We’ll provide an update once maintenance is complete. Thank you for your patience and understanding.

Short node delays should no longer trigger reconnects. Radar previously reconnected when Ethereum or XRP made no progress for one minute, even when the node was simply slow. It now confirms a stall only after two consecutive minutes. Fewer false alerts. Steadier tracking.

The chain you use should matter about as much as which ATM you use. Invisible plumbing. That is the goal.

Monday. ☕ 💻 ☀️ new week.

Friday. Shipping all week. Builders still connecting chains through the weekend. Same job either way.

Cross-chain monitoring is now easier to inspect. Radar now shows 7-day MessageOut and MessageIn counts by chain, along with the configured event-listening rules for a selected chain. Stats refresh hourly. Clearer message flow. Faster checks.

New week. Same work: making value move across chains without making users think about the chain.

Q3 done. Q4 incoming. The work continues across chains.

Still shipping. Cross-chain should feel simple. The complexity stays underneath.

GM. Coffee first. Cross-chain next.

Different cities, different chains. Same full moon. Happy Mid-Autumn Festival 🌕🥮 Wishing everyone a night of reunion and togetherness.

Different chains, different rules. Not every blockchain works the same way. Different execution environments. Different signatures. Different verification models. Cross-chain infrastructure has to work across those differences, not only between chains that look alike.

GM. New week, same mission: making value move across chains. And making the gaps invisible to users.

What TSS does. In cross-chain asset flows, one signer should not control the process. MPC-based TSS splits signing power across multiple validators, so a valid action requires a threshold to participate. No single signer. No single point of control.

Two tools, one goal: less trust. Light clients help verify source-chain activity on-chain. MPC-based TSS helps secure asset flows across multiple validators. Different mechanisms, same direction: making cross-chain infrastructure rely less on any single party.