Radar deployments are now reproducible across architectures.
amd64 and arm64 images are automatically tested, built, and published through GHCR.
Containers run as non-root, while secrets and production configuration are excluded from the build context.
Safer releases. Smaller attack surface.
amd64 and arm64 images are automatically tested, built, and published through GHCR.
Containers run as non-root, while secrets and production configuration are excluded from the build context.
Safer releases. Smaller attack surface.
0
1
3
Radar now accounts for Arc’s fast block time.
Arc’s 0.25-second block time has been added to Radar’s chain parameters, improving sync-progress calculations and lag alerts.
More accurate Arc monitoring. Sharper tracking.
Arc’s 0.25-second block time has been added to Radar’s chain parameters, improving sync-progress calculations and lag alerts.
More accurate Arc monitoring. Sharper tracking.
0
1
5
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.
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.
0
1
3
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.
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.
0
1
2
Different cities, different chains. Same full moon.
Happy Mid-Autumn Festival 🌕🥮
Wishing everyone a night of reunion and togetherness.
Happy Mid-Autumn Festival 🌕🥮
Wishing everyone a night of reunion and togetherness.
0
1
5
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.
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.
0
1
2
GM.
New week, same mission: making value move across chains.
And making the gaps invisible to users.
New week, same mission: making value move across chains.
And making the gaps invisible to users.
0
1
5
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.
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.
0
1
3
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.
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.
0
1
5
Peer-to-peer, across chains.
A cross-chain request should be valid because it happened on the source chain, not because a trusted third party said it did.
MAP Protocol uses light-client verification, so messages can be checked on-chain through the protocol itself.
Validity ion.
A cross-chain request should be valid because it happened on the source chain, not because a trusted third party said it did.
MAP Protocol uses light-client verification, so messages can be checked on-chain through the protocol itself.
Validity ion.
1
1
1
Don't trust, verify.
In many cross-chain systems, users depend on someone else to confirm what happened.
MAP Protocol uses on-chain light clients to verify proofs of source-chain activity, so cross-chain messages can be checked instead of simply trusted.
Verification over assumption.
In many cross-chain systems, users depend on someone else to confirm what happened.
MAP Protocol uses on-chain light clients to verify proofs of source-chain activity, so cross-chain messages can be checked instead of simply trusted.
Verification over assumption.
1
2
5
One framework, connected chains.
In many cross-chain setups, adding a chain means adding another route to build and maintain.
MAP Protocol is built around a shared interoperability layer, so connected chains can interact through the same framework instead of starting from zero Connect wider.
In many cross-chain setups, adding a chain means adding another route to build and maintain.
MAP Protocol is built around a shared interoperability layer, so connected chains can interact through the same framework instead of starting from zero Connect wider.
0
2
4
Omnichain vs bridges.
A bridge connects chains point to point. Add more chains, and you add more separate connections to build and run.
Omnichain is one shared interoperability network, so any connected chain can reach the rest without a new link each time.
One layer, wider reach.
A bridge connects chains point to point. Add more chains, and you add more separate connections to build and run.
Omnichain is one shared interoperability network, so any connected chain can reach the rest without a new link each time.
One layer, wider reach.
0
1
3
4 scrambled words. Every crypto native should get these.
Think you are? Unscramble all 4 👇
No prize, just respect.
Think you are? Unscramble all 4 👇
No prize, just respect.
1
1
3
What is a relay chain?
Instead of a separate link between every pair of chains, MAP routes through one relay chain in the middle. A chain connects once and reaches the whole network. One hub, not a tangle of one-off links.
Instead of a separate link between every pair of chains, MAP routes through one relay chain in the middle. A chain connects once and reaches the whole network. One hub, not a tangle of one-off links.
1
1
5
Multichain vs omnichain. Used interchangeably, but they're not the same.
Multichain is the same app deployed separately across many chains. Copies that don't talk. Omnichain is those chains working together as one connected system. Copies vs connection.
Multichain is the same app deployed separately across many chains. Copies that don't talk. Omnichain is those chains working together as one connected system. Copies vs connection.
0
1
7
Why siloed chains are the problem.
Every blockchain is its own island. Assets, apps and users are split across dozens of them, isolated by default. Interoperability is the work of making them behave like one system instead of many silos.
Every blockchain is its own island. Assets, apps and users are split across dozens of them, isolated by default. Interoperability is the work of making them behave like one system instead of many silos.
1
1
4
You don't have to trust this tweet. The chain keeps its own receipts.
A full week of MAP activity, on maposcan.io
A full week of MAP activity, on maposcan.io
0
1
3
What is MAP Protocol?
Cross-chain infrastructure that lets separate blockchains connect and move value and data between each other. Not an app on one chain, the connective layer beneath many.
Cross-chain infrastructure that lets separate blockchains connect and move value and data between each other. Not an app on one chain, the connective layer beneath many.
0
1
3
Another 7 days, all on chain.
Mainnet live, every cross-chain swap settled in the open. The explorer has the full picture.
maposcan.io
Mainnet live, every cross-chain swap settled in the open. The explorer has the full picture.
maposcan.io
0
1
3
Another 7 days, all on chain.
Mainnet live, every cross-chain swap settled in the open. The explorer has the full picture.
maposcan.io
Mainnet live, every cross-chain swap settled in the open. The explorer has the full picture.
maposcan.io
0
1
2
Last 7 days on MAP Protocol, straight from the explorer: All public, all verifiable.
maposcan.io 🔵
maposcan.io 🔵
0
1
1
Tuesday.
Still the same one job on the calendar: make chains work as one.
Not more islands. One network.
That's the whole point of omnichain.
Still the same one job on the calendar: make chains work as one.
Not more islands. One network.
That's the whole point of omnichain.
0
1
2
Multichain and omnichain are often used as if they mean the same thing. They don’t.
Multichain is one app deployed separately across a dozen chains. A dozen islands.
Omnichain is those chains actually working as one. That's the part most people skip.
Multichain is one app deployed separately across a dozen chains. A dozen islands.
Omnichain is those chains actually working as one. That's the part most people skip.
0
1
3
If the world runs on one language, it's probably emojis 😄
Chains could use one too. That's the whole omnichain idea, everything speaking to everything.
Chains could use one too. That's the whole omnichain idea, everything speaking to everything.
1
1
4
Robinhood Chain is now part of the omnichain. @RobinhoodCrypto
MAP's cross-chain infrastructure now connects it to the wider ecosystem, verified by light clients and ZK proofs.
MAP's cross-chain infrastructure now connects it to the wider ecosystem, verified by light clients and ZK proofs.
1
1
6
Omnichain, explained simply.
Instead of building a new connection for every pair of chains, each chain plugs into one layer that handles the routing.
One layer. Every chain connected.
Instead of building a new connection for every pair of chains, each chain plugs into one layer that handles the routing.
One layer. Every chain connected.
0
1
5
Choose interoperability
BREAKING: Two people have climbed to the top of the Empire State Building in New York City, holding a banner from the skyscraper's antenna reading, "When the power of love beats the love of power, the world knows peace."
As of now it's unclear how the pair reached the top of the to get them down from the spire, 1,454 feet above the ground.
0
1
2
Somehow we're already halfway through 2026.
six months of chains talking to each other.
six more to go. heads down, building.
six months of chains talking to each other.
six more to go. heads down, building.
0
1
1
The data speaks for itself.
Mainnet producing blocks without interruption.
And cross-chain is moving: $10.1M volume and 12,257 swaps in the last 7 days.
Omnichain infrastructure built to hold. 🔵
maposcan.io
Mainnet producing blocks without interruption.
And cross-chain is moving: $10.1M volume and 12,257 swaps in the last 7 days.
Omnichain infrastructure built to hold. 🔵
maposcan.io
0
1
8
Thank you to everyone who submitted questions.
We've gathered them all and the team will be answering them live.
Community AMA: Friday, June 12, 10:00 UTC
📍t.me/MAPprotocol
See you there!
We've gathered them all and the team will be answering them live.
Community AMA: Friday, June 12, 10:00 UTC
📍t.me/MAPprotocol
See you there!
Community AMA is live.
Ask us anything about MAP. We'll answer in the session.
Questions close Tuesday, June 9. AMA date and time to be announced soon.
Submit your questions here 👇 forms.gle/uuUZLqBcgEPj67…
2
3
6
Community AMA is live.
Ask us anything about MAP. We'll answer in the session.
Questions close Tuesday, June 9. AMA date and time to be announced soon.
Submit your questions here 👇 forms.gle/uuUZLqBcgEPj67…
Ask us anything about MAP. We'll answer in the session.
Questions close Tuesday, June 9. AMA date and time to be announced soon.
Submit your questions here 👇 forms.gle/uuUZLqBcgEPj67…
4
1
1
Eligible Ethereum ERC20 and BSC BEP20 MAPO holders have received the new ERC20/BEP20 MAPO based on the official snapshot list. Legacy MAPO under the original ERC20/BEP20 contracts has been deprecated. Legacy ERC20/BEP20 MAPO unauthorized-minted by the attacker is treated as ridged into MAP Protocol mainnet.
MAP Protocol mainnet is running normally and mainnet security has not been affected in any way. The recent incident did not affect MAP Protocol mainnet consensus, mainnet assets, mainnet security mechanisms, the light client, Oracle multisig, or project team private keys.
Total MAPO supply remains 10,000,000,000 MAPO. ERC20/BEP20 MAPO are MAPO bridged from the mainnet.
The ERC20/BEP20 new contract mapping is a 1:1 mapping based on the pre-attack secure snapshot. It does not constitute new issuance and does not change the existing circulating supply.
MAP Protocol mainnet is running normally and mainnet security has not been affected in any way. The recent incident did not affect MAP Protocol mainnet consensus, mainnet assets, mainnet security mechanisms, the light client, Oracle multisig, or project team private keys.
Total MAPO supply remains 10,000,000,000 MAPO. ERC20/BEP20 MAPO are MAPO bridged from the mainnet.
The ERC20/BEP20 new contract mapping is a 1:1 mapping based on the pre-attack secure snapshot. It does not constitute new issuance and does not change the existing circulating supply.
8
2
14