Running a vault day to day

Finding your way around

The left-hand menu is the whole application. The parts you will use most:

• Vaults — every vault you can act on, and the way in to a single one.
• Portfolio — the balances and actions of whichever vault you have selected.
• Transactions — everything proposed, waiting, submitted or finished, with who voted.
• Address book — saved destinations, so payments are not retyped from memory.
• Deploy Asset — issuing your own Stellar asset.
• dApps — connect a vault to an external application over WalletConnect.

Reading a vault

Opening a vault shows its balances, its address, and its actions. A few things there are worth knowing:

• The address can be copied straight from the header — that is what you give anyone paying the vault, subject to the contract-address caveat in sending and receiving.
• Version. Vault details show which contract version it was built on. If it is behind the current one an Upgrade button appears, and some features — swapping among them — need a recent version.
• Add NFT/Token makes an asset visible in the vault's holdings. It is a display setting, not a transaction: it takes no votes, moves nothing, and does not change what the vault can receive.

Watching what is happening

Transactions is where a proposal's life is visible: what was proposed, who has voted which way, and whether it has been submitted. Anything waiting on votes is waiting on a person, so this is the list to check when a payment has not gone out.

Once submitted, a transaction carries a Stellar hash. Any network explorer will show the same transaction independently of us, which is worth doing for anything significant.

Who can do what

There are two separate ideas here, and confusing them causes most access questions.

• Vault owners are Stellar addresses written into the contract. They are what decides whether a transaction can be submitted, and the chain enforces it. Changing them is a vault transaction — see owners and thresholds.
• Account roles decide what a person sees in Volta Circuit. An organisation admin can manage the organisation and its members, a member works with the vaults they have access to, and a read-only account can look but not initiate anything.

Using a vault with other applications

dApps connects a vault to an external application through WalletConnect. The application proposes actions and the vault's owners vote on them exactly as they would on a payment, so connecting grants no ability to move funds on its own.

Read what you are approving. A connected application can request anything a vault can do, and the protection is the vote, not the connection.