1
Operator source selected
Jerry or operator confirms a real beta top-up source for the pilot record.
- Payment reference or internal ledger id
- Provider-credit purchase basis
- User choice note and destination choice
ZevRouter proof architecture
Operator-controlled real beta top-up flowchart
One operator-run beta top-up becomes a user-inspectable clean-energy participation receipt: source evidence is hashed, the ZevRouter accounting split is reviewed, the allocation is written to Base, and the energy pool movement points to a destination note.
$105
Paid beta top-up amount
$100
Provider-credit basis
$5
Service uplift routed into ZEV accounting
2% + 1%
Energy-token path selected
$4
Clean-energy participation allocation
PUNL
Destination asset for the first real beta path
End-to-end flow
2
Source packet hashed
Private details stay redacted while the public record gets stable hashes.
- Redacted source packet
- SHA-256 packet hash
- Reviewer note hash
3
ZevRouter accounting split
The top-up is split using the current provider-credit basis policy.
- $105 paid top-up
- $100 provider-credit basis
- $5 service uplift
4
Clean-energy allocation
The selected energy-token path turns the basis into a $4 participation amount.
- 2% API-credit component
- 2% + 1% energy-token component
- $100 x 4% = $4 allocation
5
Reviewed allocation record
A JSON receipt binds the source hash, accounting split, destination, and review.
- Top-up id and user alias hash
- Policy hash and allocation packet hash
- Reviewer attestation hash
6
Base registry write
The reviewed packet is anchored to the ZEVTopUpAllocationRegistry on Base.
- Registry record id
- Base tx and block reference
- Settlement status for the selected path
7
Energy pool movement
The $4 participation amount moves into an energy pool or reserve ledger.
- Pool funding tx or reserve tx
- PUNL destination allocation note
- Destination note hash
8
Public receipt journey
User and AI evaluators inspect one page instead of chasing scattered artifacts.
- Official zev.city mirror
- Machine-readable JSON receipt
- BaseScan, PUNL, and evidence links
Proof layers
Private operator vault
Payment/sourceReceipt, transfer id, or internal ledger row.
Provider basisEvidence that the top-up maps to $100 provider-credit basis.
User choiceEnergy-token path selected for the pilot record.
Reviewer contextHuman note tying the source to the reviewed packet.
Public hash layer
Source hashVerifies the redacted packet without exposing raw data.
Policy hashLocks the 5% uplift and 2% / 4% path rules.
Allocation hashLocks amount, path, destination, and reviewer fields.
Note hashLinks the energy destination note to the receipt.
Base and energy pool
Registry writeBase mainnet record in ZEVTopUpAllocationRegistry.
SettlementSelected path is reflected in the registry record.
Pool movement$4 moves into energy pool or reserve accounting.
PUNL linkDestination asset page and allocation note are linked.
User and AI surface
Receipt pageOne-page journey for non-technical users and AI eval.
Receipt JSONMachine-readable path for model inspection.
Evidence indexllms.txt and sitemap point to official mirrors.
Eval loopFour-model review can score the updated proof journey.
Approval gates for Jerry
- Source Confirm the beta top-up source that can be hashed and referenced as an operator-controlled real record.
- Path Use the 2% + 1% energy-token path so the public receipt shows a $4 clean-energy participation allocation from a $100 provider-credit basis.
- Destination Use PUNL for this first path because current AI eval already recognizes PUNL, Base settlement, and the $4 allocation chain.
- Broadcast Review the preview packet, then approve the Base registry write and the matching energy pool or reserve movement.