@POSTHUMAN_DVS@osmosis No matter what anyone says, we've become better - and we'll make the price even higher than it once was on the highs - it's just a matter of time
We are waiting for verification of new PHMN on @osmosis:
https://t.co/dv0WxnLlBL
But liquidity is already live, and you can buy and sell PHMN in pair with BTC on Osmosis
@rickoets@AtoneZone@_gnoland That's not true - the best developer, Atom Space, has left space and is creating a new, timely product with like-minded people.
@AtoneZone@_gnoland Many have stopped being active and searching, but in vain - the super story continues - those who dropped out of the game will later catch Fomo
The vote to recover the expired IBC client from Stargaze has passed with a 99.93% "Yes" vote and a 42.51% turnout.
Thank you to all community members who participated and helped shape the future of AtomOne.
📢 Axelar is introducing its new interface at https://t.co/UEc6OI8YhY , a new way for moving assets across chains through @axelar ’s secure and decentralized interoperability network.
@BSCNews@SeiNetwork I don't know exactly why you're migrating from space, but it's obvious there are problems there, and I'm very much against the current leadership in space.
SEI TO EXCHANGES: ONE CHAIN, ONE INTEGRATION BY JUNE 15
Sei Labs called on exchanges and custodians supporting $SEI to complete their EVM integration by June 15, 2026, before remaining Cosmos and IBC functionality on the network is deprecated.
The team's core message: Sei EVM is not a separate chain. "It's the same chain with a second way to interact with it," Sei Labs said in the announcement. Any venue that treats "Sei" and "Sei EVM" as two distinct integrations needs to consolidate them into one.
The push closes out SIP-3, the May 2025 governance vote that approved Sei's pivot to a fully EVM-only architecture. The transition has rolled out in stages through 2026, with EVM staking added in January, inbound IBC transfers disabled in February, and the native oracle replaced by Chainlink, Pyth and API3 in March.
@Sei_Labs published four migration paths in its developer docs.