Network · Live Gas Ledger

Every task,
on the record.

The gas ledger is the network’s accounting layer. Each compute task is priced from real cloud cost, recorded on success, split between the app, the node operator and the network, and settled in DGEN.

Tasks (30 days)12,480illustrative sample · your real counts are in your dashboard
Gas consumed$142.45illustrative sample · by your active web apps
Node gas earned+$218.90illustrative sample · from your connected devices
Net balance+$76.45illustrative sample · earnings minus consumption
Sample view

What a ledger looks like

An illustrative slice of a member’s ledger. Sign in to see your own rows in the Compute Gas panel of your dashboard.

TimeTaskStationAppGASYour shareStatus
14:02:11T4 AI chatnode · dsk-c09astudio-app0.0020+0.0008recorded
14:01:48T5 Agent sequencenode · dsk-c09astudio-app0.0070+0.0028recorded
13:58:05T3 SSR requestgend-me-gcpmarket-app0.0001networkbilled
13:51:30T1 Point transfernode · mob-7e11market-app0.00003+0.00001recorded
13:40:12T6 Multi-agent pipelinegend-me-gcpstudio-app0.0814networkbilled

Illustrative sample data. Station names, apps and amounts are examples; real rows carry idempotency keys and task ids from the catalog.

Rules of the ledger

Six things that are always true

Priced from real cost

A daily sync reads the cloud billing export, converts to CAD, applies the margin and proposes prices. Admins review before anything changes.

Recorded on success only

A task that fails is never billed and never paid. The row is written after the handler returns.

Three-way split

Each row splits the sale between the requesting app, the node operator (40%) and the network share.

Billed to your app

Unbilled rows roll up daily into a pending payment on the app’s membership, itemised as GAS compute usage.

Paid to operators

Operator shares accrue per job and pay out in whole DGEN cents to the device owner’s wallet.

Units in dollars

1 GAS = 1 CAD, and DGEN is accounted at one unit per Canadian dollar, so the ledger reads like a statement.

DGEN token →
Lifecycle of a row

Request to settlement

Request

An app, an agent or a member triggers a task of class T1 to T6.

Route

The dispatcher picks an eligible online node, or gend.me compute.

Execute

The handler runs: transfer, ledger write, request, chat, agent or pipeline.

Record

On success the row is written with its station, app, price and split.

Settle

Apps are billed daily; operators are paid as whole cents accrue.

For integrators

Ledger endpoints

catalog & ledger
# network administrators
GET  /wp-json/gdc-gas/v1/catalog
GET  /wp-json/gdc-gas/v1/ledger
POST /wp-json/gdc-gas/v1/usage
POST /wp-json/gdc-gas/v1/dispatch

# members: your own usage is in the dashboard
Dashboard → Hosting → Compute Gas
wallet
GET /wp-json/gend-cp/v1/wallet/balance
GET /wp-json/gend-cp/v1/ledger
GET /wp-json/gend-chain/v1/balances/{user}
GET /wp-json/gend-chain/v1/balances/{user}/history

# every endpoint answers 401 without credentials
See yours

Your ledger is waiting.

Sign in to view real rows, or register and start earning them.