Receipt issuance
Project scopedA gateway request that reaches a terminal state can produce a signed UsageReceiptV1. The receipt records observed usage, but it is not payment proof or a wallet attestation.
Open projectsTokscale
Builder Passport
Proof of Actual Work.
Attested seal: the red stamp appears only when at least one receipt epoch has a source-owned Local Anvil or GIWA Sepolia publication label. It does not assert provider-source verification, identity authority, or challenge resolution.
Builder Passport
This route maps the evidence needed for a Builder Passport. It does not invent an account Passport projection or treat holder-disclosed local artifacts as current chain truth.
Tokscale is the pass every request travels through. The passport is the proof the journey leaves behind. Proof of Actual Work.
A gateway request that reaches a terminal state can produce a signed UsageReceiptV1. The receipt records observed usage, but it is not payment proof or a wallet attestation.
Open projectsAn attestation and its membership proof are evaluated separately from receipt validity. Local Anvil evidence does not establish current GIWA chain state.
There is no durable challenge, adjudication, or appeal lifecycle in this console, so this route presents no dispute status or verdict.
Earn
Earn is a future lifecycle, not a balance or rewards dashboard. This page outlines the contracts required before any bounty, qualification, claim, or payout can be represented.
Every token has a 'dev.' Few have a developer. Tokscale verifies the ones who actually build.
Wallet-bound evidence needs a trusted attestation source and a production verification policy.
A sponsor must publish durable bounty scope, funding, scoring, and expiry rules.
A reviewable snapshot and challenge lifecycle must explain why a builder qualifies.
Authorization, submission, confirmation, recovery, and audit records must be implemented before funds can move.