VKS (Vilna Key Security) coordinates transaction approval and signing according to the signer rules you configure in a vault. Use the first-connection guide for an ordered walkthrough and the API reference for request and response schemas.
vks.vilna.io/v1 Workspace VKS key vks:access
VKS supports signing on mainnet and test networks for EVM, Tron and supported Bitcoin address formats. Use the network table to choose a compatible account format and signing nodes.
Get workspace limits returns signer used and effective max. Usage includes registered signers and unexpired pending invitations. A max of 0 prevents new invitations; used can exceed a lowered maximum. These values are informational and do not reserve capacity.
Issue a VKS key in the Dashboard and send it in X-Api-Key. All published VKS operations require vks:access. A Platform, RPC or management key does not replace it. The public Management API has no VKS-key issuance operation.
| Resource | Purpose |
|---|---|
| Signer | A signing node with a registration identity, fingerprints, connection status and supported signing methods. |
| Vault | A group of registered signers and an approval rule: all required signers plus threshold_k additional signers. |
| Account | A blockchain account created in an active vault; usable for signing only after setup reaches active. |
| Ceremony | An account setup attempt; inspect its progress using an attempt ID from the account. |
| Transaction | A request for approval and signing, including selected signers, decisions, signed result and send history. |
A vault has at most five signers and every signing group needs at least two. Choose one complete group from minimal_quorums for each transaction. Signers must accept the vault before it becomes active. Account setup then starts automatically, without another approval step. Only one account may be in setup per vault.
The public API creates signer invitations and reports registration state; the signer operator completes registration through the signer management interface. Compare the hub identity from GET/v1/info and the registered signer's fingerprints through a trusted channel. A name alone does not verify identity.
Vault acceptance and transaction approval also happen on the signer side. This API has no public HTTP operation to register a signer or approve a vault or transaction. Arrange the operator workflow before starting. See the setup prerequisites for Beta access, a demo and the signer management interface.
The Platform API monitors public blockchain activity and invoices. VKS instead receives transaction intent and signer decisions. It can return a signed result and optionally submit a complete signed transaction to a blockchain node.
Check result_form: transaction is ready for submission; ingredient must first be included in a sponsor-paid transaction. raw_tx is Base64-encoded.
A signing deadline does not delete an existing signed result; results remain available without automatic deletion. Deleting a signer revokes catalogue access but does not erase keys on its device or history in related resources. Account deletion is limited to unsuccessful setup states.
Sending through VKS returns 202 when the request is saved. Inspect transaction logs for attempts; node acceptance is not chain confirmation. VKS does not track confirmations. See networks for supported networks and account formats and idempotency before retrying any mutation.