The repository is the recipient.
A pledge points to an immutable provider and owner/repository identity. It can exist before any maintainer joins.
Compute Supply protocol v0.1
Compute Supply turns provider credentials into repository-bound resources that maintainers can trust before they create an account—and safely use without ever seeing a sponsor’s key.
A pledge points to an immutable provider and owner/repository identity. It can exist before any maintainer joins.
A limit snapshot is evidence, not escrow. The protocol rechecks the provider and exposes freshness, expiry, and failures.
Secrets are envelope-encrypted. Maintainers use a Compute Supply gateway token constrained by repository, amount, model policy, and time.
Before claim, sponsors can cancel freely. After activation, revocation creates a permanent public event and a 12-month reputation penalty.
Grant lifecycle
A sponsor names a repository, amount, provider, constraints, and expiry.
The provider key reports enough remaining limit and passes an independent check.
A GitHub identity proves maintain or admin control of the named repository.
The maintainer receives a scoped gateway token and usage receipts begin.
The committed amount is consumed or released after the declared outcome.
What “backed” guarantees
Honest limitations
The sponsor can still disable a key or spend the parent account elsewhere. Compute Supply does not pretend otherwise. It makes the promise inspectable, detects broken backing quickly, rate-limits exposure, and prices sponsor reliability into how much the network trusts future pledges.