L1 validators (blockchain)
L1 Validators are responsible for maintaining the Vana Layer 1 blockchain’s security and consensus through a Proof-of-Stake (PoS) mechanism. These nodes are operated by professional node operators and reputable institutions, prioritizing network stability and data security. For more details, refer to the Validator Setup documentation.Key responsibilities
- Block production — L1 Validators propose new blocks and ensure their validity, adding them to the blockchain.
- Transaction validation — Validators confirm that transactions are legitimate, preventing double-spending or malicious activity.
- Network security — Validators maintain the integrity of the blockchain by staking VANA tokens, which serve as collateral. Misbehavior, such as attempting to validate fraudulent transactions, can result in penalties (slashing) to their stake.
- Finalization — Validators ensure the finality of transactions and the immutability of data on the blockchain.
How it works
- Staking — Validators are required to stake VANA tokens as collateral. The more VANA tokens staked, the higher the chance to propose and validate blocks. Max effective balance is 35K Vana.
- Consensus mechanism — The network uses a Proof-of-Stake (PoS) mechanism, where validators are chosen to propose blocks based on the size of their stake.
- Block rewards — Validators earn rewards in VANA tokens for their role in securing the network and validating transactions.
- Penalties for misbehavior — Validators that act maliciously or fail to perform their duties are penalized through slashing, reducing their staked VANA tokens.
Hardware requirements
To operate efficiently and maintain the network, L1 Validators must meet specific hardware standards: Testnet- 2-core CPU
- 8 GB RAM
- 100 GB SSD
- x86-64 architecture
- 8-core CPU
- 32 GB RAM
- 1.2 TB SSD
- x86-64 architecture
Satya validators (data / TEE)
Satya validators (also called data validators) run inside Trusted Execution Environments (TEEs). They validate data contributions for DataDAOs (Proof of Contribution), generate attestations, and process data-access requests. Data is decrypted and processed only inside the TEE; the operator and the chain only see proofs and metadata, not raw user data.Summary
| Item | Details |
|---|---|
| Role | Validate data for Data Liquidity Pools (DLPs); run PoC; process data consumer requests. |
| Technology | Intel TDX (Trusted Domain Extensions); previously SGX. |
| Rewards | VANA for completed validation jobs. Data contributors pay a fee per job; stakers to Satya validators can share in these fees. |
| Hardware | Intel TDX–enabled machine (exact specs in official Satya Validator documentation). |
Flow (high level)
- Contributors submit encrypted data to a DLP; a reference is written onchain.
- A validation job is requested (e.g. via the TEE Pool contract); the contributor pays a job fee.
- A Satya node is assigned; it receives the encryption key and runs the PoC container inside the TEE.
- The node decrypts the data in the TEE, runs the Proof-of-Contribution logic, and produces an attestation.
- The proof is recorded onchain; the node claims the job fee.
POST /RunProof), and environment variables for PoC containers, see Proof of Contribution.
Becoming a Satya validator
You need an Intel TDX–capable machine and access to the Satya Validator Docker images. Follow the technical guidelines in the official Satya Validator Documentation (check vana.org or Discord for the latest link).More detail
- L1 and Satya validator setup — See the official validator documentation; check vana.org or Community & Discord for the latest links.
- Staking (delegating to validators): Staking & Bridging