Blockchain

Understand the blockchain

Vulcan's blockchain stack separates execution, ordering, state, authorization and history. Knowing those boundaries helps you reason about what a service does and which layer enforces each rule.

Execution: Vega

Vulcan source compiles to a .vega image. Vega executes the image. Host bindings connect execution to the capabilities available in a particular environment; native and browser embeddings do not automatically expose the same capabilities.

Ordering: Relativity

Relativity provides the ordering state machine. Its pure core has no sockets, I/O or clock. An engine and its adapters supply timing, persistence and networking. Qualifying the pure core is not the same as qualifying a deployed network.

State and accounting

Mnemo handles world state. Flux provides the accounting layer. Keep the application's state model and accounting rules explicit: successful execution alone is not proof that an operation satisfies its business invariants.

Authorization and history

Guardian is the authorization layer. Historian handles sealed history and custody. UI visibility, a test actor's name and a field observation are not authorization decisions; services must enforce access at the appropriate boundary.

Begin with a local service

The Local chain guide creates a development service and publishes it to a local chain. No public RPC endpoint, token faucet or mainnet contract address is implied by that walkthrough.