Security & upgrades

What the contracts cannot do

DeVOLT never holds your funds. Every transaction is signed by you, and there is no arrangement in which the protocol moves your money without a signature. It cannot close your position, cannot liquidate you, and cannot act if the price moves while you are away.

When you approve a token so a position can be opened, you are approving a specific contract to spend a specific token. That is an ordinary step every application using your tokens needs, and it is worth knowing you can revoke it at any time from any wallet tool.

Where a position lives

On some venues the position sits on your own address and you can manage it in that venue’s own app without DeVOLT existing at all. On others it sits in a contract created for you and controlled only by you. The Custody chapter covers the difference and why it matters when you want to leave.

What the owner can change

Some settings are adjustable by whoever owns the contracts. They are listed here because a non-custodial product should be specific about the powers that do exist rather than implying there are none.

the fee

The share taken from the collateral a transaction buys. The contract refuses any value above its own hard ceiling, so the limit is enforced rather than promised. The chapter on what it costs states both.

approved routers

Which trading contracts a swap may be routed through. An address that is not on the list cannot be used, which is what stops arbitrary code being called with your funds mid-transaction.

adapters

Which contract drives which lending venue. Registering a new one does not move existing positions, by the design above.

upgrades

The main contract can be upgraded. That is a real power, and the mitigation is the immutable controller above rather than a claim that it will not be used.

How changes to the code are checked

Contract behaviour is exercised against forks of the live chains: the real contracts, at a recent block, with real quotes from real aggregators rather than stand-ins. A position is opened and unwound, and the result recorded with the date it was taken. The Verification chapter explains what the resulting badge does and does not claim.

What has not been proven

A security page that lists only reassurances is marketing. So, plainly: much of the recent contract work has been exercised on forks and in tests, and has not been driven end to end by a real wallet holding real funds. Strategy Vaults marked live run on a private fork with test funds and their contracts have not been audited.

None of that means the code is wrong. It means the evidence for it is fork evidence and test evidence rather than production evidence, and you should size any position with that in mind.