GRAVITY RELAY
What Relay does:
Relay does not move or broadcast Bitcoin. It records submitted transaction IDs under a paid entitlement and produces deterministic relay artifacts.
How it works:
1. Generate invoice
2. Pay to activate entitlement
3. Submit TXIDs in batches
4. Receive relay artifacts tied to your invoice ID
System behavior:
• Each TXID produces an artifact
• Batch submission limits apply per tier
• Total usage is tracked and enforced
• Entitlements expire after their active window
Relay does not move or broadcast Bitcoin. It records submitted transaction IDs under a paid entitlement and produces deterministic relay artifacts.
How it works:
1. Generate invoice
2. Pay to activate entitlement
3. Submit TXIDs in batches
4. Receive relay artifacts tied to your invoice ID
System behavior:
• Each TXID produces an artifact
• Batch submission limits apply per tier
• Total usage is tracked and enforced
• Entitlements expire after their active window
What you receive:
.relay.json— machine-readable relay artifact for each submitted TXID.relay.sha256— integrity hash for each artifact- Batch ID — groups submissions under one invoice entitlement
- Usage record — shows submitted count and remaining entitlement limit
- T3 manifest/root — package-level verification for larger batches
Tier differences:
T1 — submit up to 1 TXID. Best for single transaction documentation.
T2 — submit up to 25 TXIDs. Best for small batches or investigation sets.
T3 — submit up to 100 TXIDs with manifest/root support. Best for larger evidence packages.
T1 — submit up to 1 TXID. Best for single transaction documentation.
T2 — submit up to 25 TXIDs. Best for small batches or investigation sets.
T3 — submit up to 100 TXIDs with manifest/root support. Best for larger evidence packages.
Relay records submitted Bitcoin transaction IDs into Gravity’s deterministic artifact system.
Capacity-governed. Time-bound. Deterministically enforced.
Capacity-governed. Time-bound. Deterministically enforced.
Upon payment confirmation:
• Invoice transitions → VERIFIED
• Entitlement transitions → ACTIVE
• Allocation slot is reserved for the entitlement duration
• Guard-enforced access boundaries apply
• Automatic expiration occurs at term end
TIER I — LIMITED
300,000 sats
Submit 1 TXID per batch.
Best for single transaction documentation.
Usage tracked under entitlement.
300,000 sats
Submit 1 TXID per batch.
Best for single transaction documentation.
Usage tracked under entitlement.
TIER II — EXTENDED
750,000 sats
Submit up to 25 TXIDs per batch.
Best for grouped transaction sets.
Usage tracked under entitlement.
750,000 sats
Submit up to 25 TXIDs per batch.
Best for grouped transaction sets.
Usage tracked under entitlement.
TIER III — PRIORITY
1,500,000 sats
Submit up to 100 TXIDs per batch.
Includes batch manifest and verification root.
Usage tracked under entitlement.
Once payment is detected on the Bitcoin network, a Bitcoin Transaction ID (TXID) will be assigned to the settlement.
Transaction ID (TXID):
1,500,000 sats
Submit up to 100 TXIDs per batch.
Includes batch manifest and verification root.
Usage tracked under entitlement.