A vault is a component that maintains secret key material and is responsible for the creation and signing process of outgoing ledger transactions.
A vault executes transaction orders once they are fully approved and delivers the signed ledger transaction to the system for broadcast. A single instance of Harmonize can hold multiple vaults, which may provide complementary features (e.g., various distributed ledger protocols), key stores (e.g., different hardware vendors or multi-party computation-based algorithms), or key isolation (e.g., connected, or air-gapped). For example, a system can leverage a hot vault (for hot accounts) and an air-gapped vault (for cold accounts). Accounts within the system are associated with specific vaults.
The registration of the public key of a vault, publicKey, allows the system to verify any information returned by the vault.
The locking of a vault prevents the execution of any transaction order related to the specific vault.
- Mock serverhttps://docs.ripple.com/_mock/pt-br/products/custody/devbox/v1/vaults
curl -i -X GET \
'https://docs.ripple.com/_mock/pt-br/products/custody/devbox/v1/vaults?limit=1&startingAfter=497f6eca-6276-4993-bfeb-53cbbbba6f08&sortBy=id&sortOrder=ASC&alias=alias1&publicKey=MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAENYOHIq0Pgg5ERTQOahVK3I45%2BefvsRvw1rcyk%2Boqpnj7qkXSEis3BbgnwBY42uolGg7lPbusmAMWVDYRqKMApQ%3D%3D&lock=Locked%2CUnlocked&metadata.createdBy=fdeeeb4b-f987-4ec4-9880-1eb280581d49&metadata.lastModifiedBy=90c4cf2f-ebe0-4bf7-91cd-4c45cd02277b&metadata.description=description1&metadata.customProperties=key1%3Avalue1%2Ckey2%3Avalue2&additionalDetails.processingStatus=Pending' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'{ "items": [ { … } ], "count": 0, "currentStartingAfter": "string", "nextStartingAfter": "string" }