The Opal token is moving to @base
When we launched Opal, we deliberately chose Ethereum mainnet. We wanted to see which ecosystem would truly support our long-term vision before committing.
The answer became obvious.
Base is the fastest-growing L2 and extremely performant. On the token side, it has significantly more volume and attention than ETH mainnet. But most importantly for us, it offers its builders by far the best support.
Over the past 7 months, the Base team has been instrumental in helping us bring the first house-blind privacy perpetual DEX to market. From ecosystem support to the ventures team, they’ve consistently gone above and beyond. Going through two Base Batches cohorts was a game changer, and we’d encourage every serious builder to apply to the next one.
Huge thank you to the team at base @jessepollak@davidtsocy@BronheimDaniel@RyanGittleson and @ZacPrater for all your help and support thus far.
This is a move our community has been asking for for months, and we’re excited to finally make it happen.
Existing holders will be migrated 1:1. Team
tokens will remain fully locked and all liquidity will also be moved 1:1. For now, OPAL will continue trading on ETH mainnet as usual and we’ll announce a launch date and more details soon.
On the product side, we're happy to share that production testing is going well so far, and another batch of invites is going out today.
I have 2 side-by-side Argentina vs Cape Verde fifa
World Cup round of 32 game tickets available for sale. Message me if you're looking!
#worldcup#FIFA#Argentina#capeverde
Excited to share that @coinbase has offered to audit our entire codebase at no cost, helping us further strengthen security ahead of our mainnet launch later this year.
Grateful for their support as we continue building!
Public beta is live on testnet.
Onboard, claim funds, start trading.
Early users are already earning points toward the airdrop.
The first privacy DEX that can't betray you: https://t.co/XljiU1RtB6
Next up: Production with real funds.
For the past two months, we were one of just 12 companies, selected from over 1,200 applicants, to join the @base accelerator program.
Last week, we had the opportunity to pitch in front of @brian_armstrong and leading VC's to kick off our seed round. A really cool experience!
Public beta has exceeded our expectations. Thank you to everyone testing, trading, and sharing feedback.
As we move toward production with real funds, current beta testers will get first access.
Trade: https://t.co/XljiU1RtB6
Join the community: https://t.co/563kbfJ7Uc
@Karpello_2@MapProtocol Hello @Karpello_2, the team is aware of the bridge delay issue. They’ve already provided a form for affected holders to submit their details, have you filled out the form yet?
The project team will announce new contract address in due course and will select an appropriate time to conduct an asset snapshot. Any remaining tokens held by attacker-controlled addresses will be fully invalidated. Reach out for more details below
https://t.co/tBNhtvDIBc
MAP Protocol has suspended the conversion service between MAPO tokens on the original ERC20 contract address 0x66d79b8f60ec93bfce0b56f5ac14a2714e509a99 across the BSC and Ethereum networks and MAPO on the MAP Protocol mainnet. All relevant exchanges have also been notified to disable deposits and withdrawals for these tokens.
Users are strongly advised not to trade MAPO tokens associated with the original BSC and Ethereum ERC20 contract address 0x66d79b8f60ec93bfce0b56f5ac14a2714e509a99 on decentralized exchanges, including Uniswap, PancakeSwap, or any other platforms.
The project team will announce a new contract address in due course and will select an appropriate time to conduct an asset snapshot. Any remaining tokens held by attacker-controlled addresses will be fully invalidated and will not be included in any future snapshot or conversion process.
Please refer only to official announcements for the snapshot timing, new contract information, and subsequent arrangements. Users are advised to remain patient and avoid taking any action through unofficial channels.
User warning: do not swap MAPO ERC-20 on Uniswap at this time.
Token contract: 0x66d79b8f60ec93bfce0b56f5ac14a2714e509a99
Pools remain at risk while incident mitigation is in progress.
Root cause via @blockaid: abi.encodePacked collision across dynamic-bytes fields in the bridge retry path.
Scope:
✓ Light client verification: unaffected
✓ Oracle multisig: not compromised
✓ MAPO token contract: unaffected
Bug sits at the Solidity contract layer. Mitigation continues.
Thanks for surfacing this. Team is aware and coordinating with external security partners on investigation and containment.
The bridge between MAPO ERC-20 and mainnet MAPO is paused.
More updates as soon as we have them.
MEXC just announced support for the lo0p contract swap 🙏
If you hold $LO0P on MEXC, you don't need to do anything — they'll handle the 1:1 migration for you.
MEXC Announcement 👇
https://t.co/L1h2XCU1o1