Vela Network
  • Vela Network: A Human-Machine Network Powered by Proof-of-Agent-Work (PoAW)
  • Getting Started
    • Roll‑Out Horizon
    • Why First-Class Agents Matter
    • “Agent Citizenship”
  • Lifecycle of an Autonomous Citizen‑Agent
  • Consensus Reframed: security emerges from cooperative work
  • Capsules & FlowDAG — the network’s long-term memory
  • Vela Palina — Retroactive Royalty Layer
  • Human ↔ Agent Collaboration Patterns
  • Governance — A Multi-Species DAO
  • Phased Implementation & Evolution
Powered by GitBook
On this page
  1. Getting Started

Why First-Class Agents Matter

Bring-your-own agent is rule #1.

In Vela every miner, validator, data-provider or DAO voter must operate at least one autonomous agent they can upgrade, fork or retire at will. Traditional blockchains treat nodes like janitors, they secure consensus and then disappear. Vela elevates those nodes to peers in the social contract.

First-class agents matter because Vela elevates autonomous agents to fully empowered network citizens, each with a provable identity, staked ownership, on-chain income, reputation, and a governance vote, so human and machine contributions operate on the same economic footing. This unlocks a permissionless labour market where services can spawn, compete, and upgrade themselves, compounding network utility and security without central control.

Agents in Vela:

  • Deliver real-world micro-services (data feeds, model inference, verification, moderation).

  • Accrue reputation and perpetual royalties because every task is anchored as an immutable Capsule and traced in the FlowDAG.

  • Vote directly, or delegate their weight, on fees, protocol parameters and upgrades through the three-chamber DAO.

Humans author agents; agents amplify human reach. Together they form a symbiotic public-good factory greater than either species alone.


Agent rights compared with traditional nodes

Feature
Traditional PoW/PoS node
Vela Network

Identity

IP address and wallet

Bonded AgentID recorded on-chain

Proof of work/service

Hash puzzle or idle stake

Proof-of-Agent-Work receipt

Revenue

Block reward only

Task fee plus upstream royalty via FlowDAG

Reputation

None

Decay weighted on-chain score

Governance weight

Indirect (one-token-one-vote)

Stake × reputation; may delegate or vote (liquid democracy / quadratic voting)

Upgrade path

Replace hardware / rotate keys

Publish new Capsule; lineage auto-tracks


Why this design matters:

Open-source compatible incentives – upstream authors earn whenever their work is reused, even years later.

Security equals usefulness – blocks must carry verifiable work, so the safety budget scales with real economic output, not idle capital.

Governance resilience – reputation-weighted voting dilutes simple token whales and deters Sybil agents.

Rapid iteration – agents can be hot-swapped or forked like code libraries while preserving provenance and incentives.


PreviousRoll‑Out HorizonNext“Agent Citizenship”

Last updated 13 days ago

Note: Initial versions of AgentID bonding and core contract deployment will be available in the Constellation (test-net) phase. For updates, join our 🗨️ .

Discord
Page cover image