Every Bybit signer approved. No signature proved a human saw the real transaction.
Multisig assumes the approval surface is honest. Manav adds what the $1.5B taught: a ceremony on the signer’s own device that displays the canonical transaction semantics from an independent channel — amount, destination, calldata class — and binds a live human’s signature to exactly that.
The receipt below was signed and checked in this tab, with zero network calls.
Cryptographic fields
stolen from Bybit via a poisoned signing UI — every multisig signer approved. FBI: North Korea.
signed away at Radiant while Safe UI and simulations “showed no anomalies.”
In Bybit and Radiant the hardware wallets performed perfectly — they signed exactly the bytes they were handed. The compromised interface rendered a different transaction than the one being signed; N-of-M multisig just serialized identical deceptions, because every signer looked at the same poisoned screen. Whitelists failed because the payload was a contract upgrade, not a transfer. The missing primitive is a human-bound, phishing-resistant authorization of the actual semantics.
Three integration points. Your brand, our receipt.
// Before the consequential action, from your backend: const receipt = await manav.sign({ action: 'withdrawal.release', payload: { txHash, dest, calldataClass }, approver: signer.principal, assurance: 'passkey+liveness', }); if (receipt.ceremony === 'completed') proceed(receipt.id); // Anyone verifies the receipt offline against our published JWKS — forever.
Run the ceremony yourself. Then try to fake it.
A controlled sandbox of the exact flow above — your system asks, the enrolled human signs on their own device, a receipt is issued, and you attack it. Real Ed25519, in this tab, nothing sent anywhere.
A 30-minute integration conversation.
Bring the flow in your product where this belongs. We’ll run the ceremony on it and hand you a receipt you can verify yourself before the call ends — and a straight answer on what an embed looks like commercially.