Use VKS through the Vilna website. See the VKS overview for the resource model.
Connect signing nodes, configure vault approval rules and request transaction signatures in the Vilna Dashboard.
A signer is the software node that participates in signing. Its operator manages the node and reviews approval requests in the signer management interface.
VKS supports mainnets and testnets. Available operations depend on the address format, the selected nodes and the network. Check network compatibility before using an address.
Sign in, select a workspace and open VKS. Your workspace membership needs VKS access; ask a workspace administrator if the section is unavailable. Working through the website does not require a VKS API key.
The signer software is open source and in Beta. Contact support@vilna.io to obtain its source code and installation instructions, or to try a demo.
Arrange at least 2 signing nodes with their operators. This walkthrough starts with installed signer software. Operators can manage their nodes through signer.vilna.io. This management interface is also open source and can be hosted on your own infrastructure.
To select networks and assets later, you need api:blockchain:read and api:asset:read in a project whose catalogue contains them. For a Bitcoin transfer, also register the source address on the intended network in that project and ensure you have api:address:read to read its unspent outputs (UTXOs).
- Open Nodes, choose Connect node, then Create connection token.
- Compare the service identity and fingerprint shown by Vilna with the operator through a trusted channel. Pass the token privately to that operator and save it before closing the dialog.
- The operator connects the node through its management interface. Return to Nodes, check registration and connection status, and compare the registered node's fingerprint with the operator.
- Repeat for the second node. You can reuse existing registered nodes after checking their identities and capabilities.
Keep connection tokens out of messages to shared channels, logs and screenshots.
Open Vaults and choose Create vault. A vault defines the participating nodes and their approval rule.
For a first setup, select 2 registered nodes and require both. For another configuration, choose 2–5 nodes and the number of node approvals required; Advanced rule also lets you designate mandatory nodes. Review the displayed rule before creating the vault.
Each operator reviews and accepts or rejects the configuration in their signer management interface. Vilna shows the received decisions. Continue after the vault becomes active; a rejected or expired request needs attention before you can create an address.
In the active vault, choose Create address, or use the same action under Addresses. Select the intended blockchain family and address format, review the settings and confirm creation.
Wait for Address ready. The website shows progress; you do not need to prepare API requests or track protocol stages yourself. If creation fails or expires, open the address to inspect its status before trying again.
The address represents a VKS blockchain account, separate from your Vilna user account. Choose the network when using the address; Bitcoin address formats also distinguish mainnet and testnet.
- Open the ready address and choose Send.
- Select the catalogue project, network and asset, then enter the recipient and amount. The form offers operations supported by that address and network. For this walkthrough, choose a transfer with fee payment from the source address.
- Choose Calculate preview and check the sender, network, asset, recipient, amount and estimated fee. Make sure the source address has enough funds for the operation and fees.
- Select a signing group that satisfies the vault rule, then choose Request signature.
The selected operators review the request and approve or reject it through their signer management interfaces. Follow the result under Signing requests in Vilna. A created request is not yet a completed signature; it may be rejected, fail or expire.
Open the signing request and check its result. For a complete signed transaction, choose Send when you want VKS to submit it to the blockchain node. Producing a signature does not send it automatically.
After you request sending, VKS may automatically retry after a temporary error or an unknown outcome, using the same signed transaction. Check VKS send attempts.
Accepted by blockchain node means node acceptance, not blockchain confirmation. VKS does not track confirmations; use blockchain monitoring to check what happened on-chain.
If acceptance is unknown, inspect the existing request and send history before starting another action: the transaction may already have reached the network.
Open the existing vault, address or signing request and check its current state. An interrupted page load or an error message does not by itself prove that the action was cancelled. Check the existing result before creating a replacement request.
Expiry of a signing request does not erase an already produced signature. The VKS overview explains retained results and deletion limits.
For a custom integration, use the VKS API reference.