VAULTFI TRANSPARENCY

Trust should be verifiable.

VaultFi is designed around customer-authorized wallet activity, transparent transaction lifecycles and clearly separated service boundaries. This page explains what VaultFi can do, what it cannot do, and which trust improvements are already implemented versus still planned.

Core wallet: Non-custodial design Signing: Customer-authorized Balance authority: Blockchain/RPC Updated: September 17, 2026

✓

You authorize transactions

VaultFi's core wallet is designed so that transaction signing remains customer-authorized. Creating a VaultFi account does not give the application unrestricted authority to move assets from the core wallet.

◉

Blockchain is the source of truth

VaultFi uses blockchain and RPC state as the authoritative source for real wallet funds. Database balances are operational and accounting records, not a replacement for on-chain state.

↻

Reconcile before retry

When the outcome of an on-chain write is uncertain, VaultFi's architecture requires reconciliation before another write is attempted rather than blindly resubmitting a transaction.

WALLET CONTROL

What VaultFi can — and cannot — do

Trust starts with being clear about the boundary between the wallet interface and the user's assets.

VaultFi can

display supported wallet addresses and blockchain balances;
prepare transactions requested by the user;
submit a properly authorized transaction;
track transaction lifecycle and confirmations;
display activity, status and external transaction references; and
operate optional services when the user explicitly enters or authorizes those flows.

VaultFi's core wallet is not designed to

give the backend unrestricted authority over customer wallets;
silently recreate a customer's wallet or replace their established address;
treat a database balance as more authoritative than the blockchain;
blindly retry a transaction whose broadcast outcome is uncertain; or
silently mix an unrelated product's accounting into the customer's core wallet balance.

WALLET FOUNDATION

Wallet identity is preserved

Existing VaultFi users maintain their established wallet identity, wallet/account mappings, derivation paths and blockchain addresses. A user-interface or transaction issue is not treated as a reason to recreate customer wallets.

VaultFi uses Turnkey-backed wallet/account infrastructure as part of its production wallet foundation. VaultFi's application architecture is designed around customer authorization rather than unrestricted backend wallet signing.

TRANSACTION INTEGRITY

Transaction state is tracked, not guessed

Send Destination, amount, network requirements, transaction state and resulting activity can be tracked through the wallet operation lifecycle.

Receive Incoming wallet activity is verified against blockchain state rather than relying only on a locally cached balance.

Convert VaultFi's current Convert architecture uses the defined THORChain flow and tracks inbound, outbound, completed, failed and refunded lifecycle states.

Uncertain writes A transaction that may already have been accepted or broadcast should be reconciled before retrying.

SERVICE BOUNDARIES

Not every VaultFi product is the core wallet

Optional products may use their own accounting, settlement, treasury or service flow. VaultFi aims to keep those boundaries explicit rather than presenting every product balance as if it were the same thing as an on-chain core wallet balance.

Trading Wallet Trading accounts, journals, transfers, withdrawals and settlement records are kept as a distinct trading/accounting system.

Premium Premium status and benefits are determined server-side and maintained separately from the underlying wallet identity.

USDT Radar Reward eligibility and claim lifecycle are separate from ordinary wallet funds.

Cashout Cashout is a distinct authorized service flow with its own principal, fee, transaction and settlement requirements.

Crypto Switch Crypto Switch is an optional automation layer and reuses the existing Convert execution architecture rather than silently creating a separate wallet.

Future products New products should define their own ledger, settlement and ownership boundaries before being integrated into VaultFi balances.

PRODUCTION SAFEGUARDS

How production changes are handled

Backups before production changes VaultFi production work follows a backup-first process before changing live application files or database behavior.

Staged changes New files and patches are staged and checked before being installed into the live path where practical.

Syntax and health verification Backend changes are syntax-checked and the production health endpoint is verified after relevant deployments.

Rollback discipline Production changes are expected to retain a recovery path and roll back when post-install verification fails.

No secrets in audit bundles Production credentials, private keys and other secrets should not be printed or packaged into source or audit bundles.

Existing wallet preservation Customer wallets are not recreated simply to fix an interface, transaction or service bug.

TRANSPARENCY ROADMAP

What exists today and what is still planned

VaultFi does not present future security work as if it has already been completed.

Customer-authorized core wallet signing Current production architecture.

CURRENT

Blockchain-first balance verification Blockchain/RPC state is the authoritative source for real wallet funds.

CURRENT

Reconcile-before-retry transaction policy Intended production rule for uncertain blockchain writes.

CURRENT

Independent VaultFi application security assessment External review of VaultFi's own application, authentication and transaction layers.

PLANNED

Public vulnerability disclosure / bug bounty A formal channel and policy for security researchers.

PLANNED

Public service status and incident history Transparent operational status and material incident reporting.

CURRENT

Formal compliance and legal review by service Review of wallet, Cashout, card, trading and future settlement products according to applicable jurisdictions.

IN REVIEW

SOC 2 readiness program Formalize operational and information-security controls before pursuing independent attestation.

FUTURE

USER VERIFICATION

Don't rely only on what VaultFi says

Users should independently verify recipient addresses, selected networks, transaction amounts and blockchain transaction status. Public blockchain activity can be checked using independent blockchain explorers. VaultFi aims to make transaction references and lifecycle status visible so that important activity can be independently verified.