Attestation
Cryptographic proof that your swap executed exactly as quoted. No trust required — verify.
What is Attestation?
In the Velox protocol, attestation is the process by which an independent network of verifier nodes cryptographically confirms that a swap executed at the exact rate displayed to the user — no hidden spread, no post-hoc price adjustment, no tampering. Every completed swap produces an attestation record that is verifiable on-chain and publicly auditable on TronScan.
Think of attestation as a digital notary for your trade. The verifier network witnesses the quoted rate, the executed rate, the amounts, the wallet addresses, and the block timestamp — then signs a proof that binds all of it together. That proof is stored on-chain and can be independently verified by anyone running a TRON node.
What an Attestation Proves
Rate fidelity: The execution rate matches the quoted rate within the user's slippage tolerance.
Amount correctness: The recipient wallet received exactly the number of tokens displayed in the confirmation screen.
Non-custodial settlement: Funds moved directly from the user's wallet (or the liquidity pool) to the destination — Velox never held them.
Gas sponsorship: The network fee was paid by Velox's gas reserve, not deducted from the user's output.
Attestation Lifecycle
Every swap moves through four defined stages. Each stage is recorded on-chain, giving you a complete audit trail from confirmation to final proof.
Quote Requested
The swap widget displays a live rate. Rate is locked for 15 seconds. No transaction has been submitted to the network yet.
Transaction Signed
You sign the swap in your wallet. The transaction is broadcast to TRON mainnet. A unique attestation ID is generated.
Block Inclusion
TRON validators include the transaction in a block (~3s). Verifier nodes detect it and begin collecting execution parameters.
Proof Finalised
A supermajority of verifier nodes sign the attestation. The proof is written on-chain and the attestation is permanently archived.
How On-Chain Attestation Works
Velox attestations are not stored in a proprietary database — they are committed to the TRON blockchain using an on-chain registry contract. This means any third party can verify an attestation independently, without trusting Velox.
Attestation Data Structure
struct Attestation {
bytes32 attestationId; // Unique hash of the swap parameters
address user; // Wallet that initiated the swap
uint256 quotedRate; // Rate displayed at confirmation (scaled 1e18)
uint256 executedRate; // Actual on-chain settlement rate (scaled 1e18)
uint256 inputAmount; // Tokens sent by user
uint256 outputAmount; // Tokens received by user
uint256 gasSponsored; // TRX spent by Velox gas reserve
uint256 blockNumber; // TRON block containing the swap
uint256 timestamp; // Unix timestamp at block inclusion
bytes verifierSigs; // Aggregated BLS signatures from verifier quorum
bool attested; // True once quorum threshold is met
}
The attestation registry contract at TXpY...8kLm on TRON mainnet is immutable — it cannot be altered after deployment. Once an attestation is written, it's permanent. Any change to the executed rate, output amount, or gas sponsorship would produce a different attestation hash, making tampering cryptographically detectable.
Verifier Node Requirements
Attestations are signed by a geographically distributed network of verifier nodes. Each node must meet strict technical and operational standards to participate.
| Requirement | Specification | Rationale |
|---|---|---|
| TRON Full Node | Dedicated TRON Java-Tron full node, synced within 2 blocks of tip. No light clients or API proxies. | Ensures verifiers observe chain state directly, not through a third-party RPC that could be manipulated. |
| Independent Operator | Each verifier must be operated by a separate legal entity with no ownership overlap with Velox or any other verifier. | Prevents single-entity control of the attestation quorum. Geographic and jurisdictional diversity required. |
| BLS Key Pair | Each verifier provisions a BLS12-381 key pair. The public key is registered in the attestation registry. Signatures are aggregated on-chain. | BLS enables compact signature aggregation — a single 96-byte proof covers the entire quorum, keeping on-chain costs minimal. |
| Minimum Stake | 200,000 TRX bonded in the verifier staking contract. Stake is slashed for provably false attestations. | Economic security — a verifier has more to lose by cheating than they could gain. Slashing is enforced by the on-chain contract. |
| Uptime SLA | 99.5% monthly uptime. Nodes below threshold for 2 consecutive months are removed from the active set. | Attestation must complete within 6 blocks (~18s). A down verifier delays quorum and degrades user experience. |
| Hardware Baseline | 8 vCPU, 32 GB RAM, 1 TB NVMe SSD, 1 Gbps dedicated link. Bare metal or dedicated cloud instance. | TRON full nodes are resource-intensive. Underspecced hardware introduces sync lag and attestation delay. |
| Quorum Threshold | Minimum 7 of 11 verifier signatures required for an attestation to be considered final. | A 2/3 supermajority ensures no single verifier (or small colluding set) can fabricate or withhold an attestation. |
Verify Any Attestation
You don't need to take our word for it. Every attestation can be independently verified using only publicly available TRON blockchain data.
1. Look up the transaction on TronScan
Every swap produces a TRON transaction hash. Paste it into TronScan to see the exact token transfers, block number, and timestamp — all independently verifiable.
2. Call the attestation registry contract
Use the getAttestation(bytes32 id) function on the registry contract to retrieve the full attestation record. Compare the executed rate and output amount against the transaction data.
3. Verify the BLS signature
The aggregated BLS signature can be verified against the registered public keys of the active verifier set. Any BLS library (ethers.js, bls-signatures) can perform this check — no Velox infrastructure required.
Attestation is not a marketing claim. It is a cryptographic guarantee baked into the protocol's architecture. If the verifier network were to disappear tomorrow, every attestation ever issued would remain independently verifiable against the immutable TRON blockchain.