Skip to main content

Glossary

APPROVED · IMPLEMENTATION SPECIFICATION · London 0.1.0

TermLondon meaning
Approved specificationProduct-owner-authorised implementation baseline; not runtime or launch evidence
Independent operatorParticipant controlling the host/account and operating decision
Peer fillAuthorised node-to-node content transfer; earns no listening reward
Delivery nodeCache/server for authorised audio; not a validator or independent attestor
GrantShort-lived signed authorisation for one node, purpose and chunk
ConsumptionAtomic coordinator record admitting one request against a grant
ReceiptNode-signed assertion of bytes served and outcome
Eligible sessionClosed session whose valid unique complete chunks meet the threshold
Accepted durationSum of eligible unique manifest media intervals, not verified attention
Evidence batchFrozen inventory of grants, receipts and dispositions
CommitmentOn-chain digest/reference fixing the published artifact bytes
Immutable / tamper-evidentPrior chain record is retained; changed off-chain bytes fail digest verification
Accounting allocationFunded listener-attributed amount assigned under a frozen policy
StatementRecipient-private allocation detail with a public hash-index proof
Payment runExact approved set of transfer instructions and total cap
PaidSuccessful native-USDC transfer reconciled to asset, recipient and amount
UncertainA transaction outcome cannot yet be established; do not retry as a new payment
CorrectionNew linked artifact/ledger event preserving earlier evidence
Porto fallbackPorto-controlled serving when participant delivery is unavailable
SubsidySeparate pilot support, excluded from earned-reward economics
Full auditAuthorised recomputation from private evidence/funding/rights inputs
Artist verificationChecking own statement inclusion/arithmetic and transfer evidence, not all private inputs
App-chain migrationFuture separately approved work, not a London implementation dependency

Contents · Implementation plan · Launch inputs