Vettor — Layer 1 blockchain for Real World Assets

Context

Real-world asset (RWA) tokenization has been one of the hottest blockchain areas since 2023: real estate, private equity, commodities, fund shares, debt and carbon credits living on-chain as regulated instruments. Most existing solutions, though, are built on general-purpose chains (Ethereum, L2s) and inherit their compromises: variable gas, insufficient throughput for periodic issuances, opaque governance, weak attention to the regulatory perimeter.

Vettor is built as a Layer 1 dedicated to RWA, optimised from day one for issuance, distribution, trading and governance of tangible assets under a concrete regulatory framework: the Italian DLT Pilot Regime (Law 52/2023) implementing the EU regulation.

Constraints and goals

• Immediate finality for regulated settlement (BFT, no probabilistic finality).
• Three-layer architecture: the blockchain (layer 3) stays separate from legal custody and instrument issuance, reducing regulatory friction.
• Built-in compliance at protocol level: on-chain DIDs, KYC/AML/Accredited/Qualified claims, deny lists and jurisdiction policies.
• Deflationary tokenomics with staking incentives and a sustainable validator set.
• Developer-friendly: WASM smart contracts writable in any language that compiles to WebAssembly, TypeScript SDK for application integration, EVM bridge for existing assets.

Architecture

The stack is organised in five layers, from the lowest to the highest.

Consensus · Tendermint BFT with DPoS. Target set of 21 active validators per epoch (1,200 blocks, ~1h); currently 1 active validator — the bootstrap node — pending external node onboarding. Constant 3s block time, immediate BFT finality. Slashing 5% for double-sign (immediate jailing), 0.1% per epoch on downtime > 50%. 21-day unbonding as a trade-off between economic security and flexibility.

Runtime · Wasmer 5 with Cranelift. WASM as the only runtime: smart contracts written in any compilable language (Rust as default). No native EVM — EVM stays as an interop layer via bridge. Lean modern crypto stack: Ed25519 for signatures, BLAKE3 for hashing, Borsh for serialization. Account address = last 20B of BLAKE3(pubkey).

Native core modules. Business logic integrated into the protocol instead of application-level smart contracts:

• RWA tokenization with a three-layer asset model: legal layer (issuing entity, jurisdiction ISO 3166-1, instrument type), economic layer (rights to revenue, voting, redemption, transfer constraints), DLT layer (token registry, transfer events, governance proposals). Each layer has its own compliance check without rigid coupling.
• Native DEX AMM x·y=k with 0.3% fee (0.25% LPs + 0.05% treasury). vUSDT as protocol stablecoin pegged 1:1 to USD; VTT-REV is a fixed-supply token (10,000) representing perpetual claim on 0.05% of fees.
• Bridge lock/mint and burn/release toward Ethereum mainnet and Base, relayer service monitoring both sides.
• Oracle quorum-based with median aggregation, authorised feed types (AssetValuation, MarketPrice, InterestRate, Custom) per node.
• Protocol-level governance with 201,600-block voting period (~7 days), 33% quorum, 50%+1 to pass. For asset governance the voting power is proportional to token holdings, not staking; critical actions (ChangeIssuer, DisposeAsset, FinalizeRedemption) require 67% supermajority.

Built-in compliance. On-chain DIDs with verifiable claims (KYC, AML Cleared, Accredited Investor, Qualified Purchaser, Jurisdiction, Custom). Transfer validation enforces claim requirements and deny lists before accepting any transfer. The whole application flow (issuers, investors, custodians) goes through the compliance layer before touching RWA or DEX.

Tokenomics. Total supply 1B VTT (18 decimals). Distribution: 30% validator rewards, 20% ecosystem, 15% team (4-year vesting), 15% public sale, 10% foundation, 10% treasury (governance-controlled). Target inflation 5%, staking ratio target 60% with dynamic multiplier 0.5x–2x. Gas: 70% burned, 30% to producer; block reward: 80% producer + 20% treasury.

Network stack. libp2p with TCP, Noise (XX handshake), Yamux multiplexing, Gossipsub for propagation, Kademlia DHT for discovery. RocksDB persistence with dedicated column families for accounts, assets, pools, validators, contracts, governance.

Outcomes at testnet

• Public testnet live on testnet.vettor.org
• 1 active validator (bootstrap node) on a target set of 21 per epoch, stable 3s block time
• Complete documentation with 50+ JSON-RPC 2.0 methods and crypto specifications
• Public TypeScript SDK (vtt-sdk) with primitives shared between core and applications
• Web stack (explorer, launchpad, dApp) and mobile/extension/Discord bot under private development
• Mainnet launch target: Q2 2026

Lessons learned

Building an L1 from zero means making permanent choices very early. The regulatory constraint was the strongest driver: I rejected convenient technical shortcuts (e.g. native EVM) because they widened the compliance review surface. The three-layer architecture was the most important design choice — separating blockchain, legal ownership and economic rights reduces regulatory risk and enables cooperation with authorised registrars without protocol-level changes.

The second lesson is about developer experience: an L1 without a solid SDK and runnable documentation is invisible, even if the consensus is perfect. The vtt-sdk TypeScript package shares primitives (Borsh schemas, crypto, RPC types) between core and applications, avoiding drift and duplication. Docs, SDK and CLI are part of the product, not an add-on.