News linked to both this project and an event.
The core AI suite of the FLOA ecosystem, FloaClaw, has been officially launched in full, simultaneously releasing a multi-scenario AI skills matrix. These features are only accessible to Agents of Level 3 and above.As the core AI tool of the FLOA ecosystem, FloaClaw's usage requires adherence to clear rules: Users need to recharge BNB to obtain compute power-tokens (tokens), with skill consumption increasing along with task complexity; subsequently, FloaClaw will continue to iterate and scale, unlocking more new AI skills and tool modules, while also advancing a creator dividend system. This will allow Agent creators to share in the compute power-token (token) revenue from user skill consumption, and support one-click exchange and withdrawal of BNB, thereby building a sustainable creator economy loop.FLOA is an intelligent Web3 Agent ecosystem platform on the BNB Chain, integrating core capabilities such as data analysis and on-chain automation. Featuring an open incentive mechanism, it serves both as a tool for user empowerment and an efficient growth engine for the Web3 ecosystem.
According to an official disclosure by Hyperbridge, the losses from the Token Gateway vulnerability incident on April 13 have been revised upward from an initial estimate of $237,000 to approximately $2.5 million. The increase stems primarily from losses incurred in incentive pools on Ethereum, Base, BNB Chain, and Arbitrum. The attacker extracted roughly 245 ETH from related contracts, then bypassed the MMR proof verification mechanism by forging cross-chain messages, minting 1 billion bridged DOT tokens and dumping them onto illiquid markets. Currently, some of the stolen funds have been traced on-chain to Binance. Hyperbridge is collaborating with Binance’s compliance team and law enforcement agencies to investigate the incident. Polkadot-native DOT and products such as Intent Gateway remain unaffected. The Token Gateway and bridged DOT contracts on the four affected EVM chains remain suspended. An external audit of the patched MMR verification logic is underway, and bridging functionality will be restored upon completion of the audit.