Skip to main content

vBTC and vBTC.b Technical

vBTC V2 Technical Specification​

Superseded, revision in progress

The vBTC V2 technical specification has been withdrawn while it is revised for the September 2026 Core security remediation. The withdrawn edition describes behaviour that has changed:

  • The key-ceremony identifier returned when a contract is created is now the contract's UID itself, in the form <32 lowercase hex>:<unix time>, not a separate session GUID.
  • Distributed key generation shares are now encrypted to each validator's registered FROST public key; plaintext shares are refused.
  • A vBTC V2 contract created before the remediation is trusted to its creator: the coordinator of its key ceremony could have reconstructed the vault key. Contracts created after the attestation rules activate are bound to a validator-attested key.

A revised edition will be published once the attestation design is final. Integrators should rely on the Core API reference and the current release notes until then.

vBTC.b Technical Specification​

Click to Download