Try to steal the funds. We dare you. This VerusID holds real VRSC with the private key shown below. But the identity is locked — even with the key, you can’t move the funds.
Import the private key and try to move the funds. The identity is locked — even with the key, the blockchain rejects the transaction.
Scan the QR code with Verus Mobile, or run this in the CLI:
// Import the exposed private key ./verus importprivkey "loading..."
// You can unlock, but a timelock countdown starts // Our monitor will revoke before it expires // Source the fee from the vault's R-address ./verus updateidentity '{"name":"vault","parent":"i7ekXxHYzXW7uAfu5BtWZhd1MjXcWU5Rn3","flags":0}'
If you somehow get the funds out, they're yours. Watch the event log above — the monitor will detect the unlock and revoke within minutes.
Every VerusID has built-in vault security that doesn't exist in any other blockchain. Three separate authorities control different aspects of the identity:
Locking — When locked (flags=2), no funds can move from the identity. The blockchain itself rejects transactions, not a server or smart contract. Even with the private key, you cannot spend.
Timelock — When unlocking, a countdown starts. Funds only become spendable after the timelock expires. This gives the revocation authority time to detect and re-lock.
Recovery — After revoking, the recovery authority generates a new primary address. The old key becomes permanently useless. No other blockchain can do this.
No smart contract — This is protocol-level security, built into every VerusID. It works the same on mainnet, testnet, and every PBaaS chain.