Know what your address has revealed on BNB Smart Chain.
No wallet connection or signature required.
Ethereum Foundation researcher Justin Drake urged the industry to prepare for a future where AI-assisted mathematics could threaten today's cryptography.
Signatures could become vulnerable. A public key might reveal more than it once did. Vitalik Buterin took the risk seriously while cautioning against rushed wallet migrations.
Billions left Binance wallets. TRM Labs reported that attackers used EIP-7702 delegation on Ethereum alongside ordinary signed transfers across other chains.
Cryptography had not been proven broken. The infrastructure handling our signatures had failed.
TRM's analysisYour wallet address is derived from a public key. Sign a transaction and observers can recover that key from the signature.
bBunker checks exposure. It does not protect funds or certify that an address is safe.
About EIP-7702It means the address has a zero account nonce and no contract code at the BNB Smart Chain block we checked. It does not cover other chains, offchain signatures, pending transactions, or a compromised private key. It is evidence about this chain, not a safety certificate.
An ordinary incoming transfer does not require the recipient to sign. Receiving funds or unsolicited tokens alone does not prove that an address has exposed its public key. Sending transactions and signing authorizations are different.
No. EIP-7702 also powers legitimate smart wallet features. A delegation result shows which contract currently runs on behalf of the address. You still need to verify that contract and its permissions with your wallet provider.
Signed activity is normal for an active wallet and does not prove a compromise. Review its history and current delegation. If you choose a fresh address, verify your wallet's backup and recovery process, the receiving address, and the network before moving funds. Avoid rushed transfers.