gittensor rental economics spec

[JSONbored]

Problem: No mechanism is defined for how a customer's payment or stake translates into allocated compute-time on the gittensor subnet.

Area: Product spec / gittensor economics

Proposal: Define, in collaboration with the gittensor subnet side (not as a solo engineering decision), whether rental reuses existing subnet emission/registration mechanics or introduces a separate escrow/credit layer, and how compute-time gets metered and allocated per customer. Keep the spec at the level of mechanism and process — this issue is not the place to fix concrete pricing numbers or reward formulas; those are a downstream business decision informed by this spec (see #4804).

Deliverables:

• A written spec covering: the economic model chosen, the metering approach, and settlement/refund handling at a mechanism level.

Acceptance criteria:

• Spec has explicit sign-off from the gittensor subnet side, not gittensory engineering alone.

Boundaries:

• No hardcoded reward values, trust-score formulas, wallet addresses, or hotkey material belong in this spec or its issue thread.
• This is a cross-team decision — do not begin Neuron/hotkey registration flow #4789/E2/E3 implementation until this has explicit subnet-side agreement.

---

Part of #4778.

[linear-code]

JSO-3453