Relay
Issued Package Deliverables
Relay Deliverables
A completed Gravity Relay package is designed as an invoice-bound verification record package tied to submitted Bitcoin transaction references, not a loose list of TXIDs. The issued package is designed to include:
Relay Certificate
Submission Manifest
Batch Manifest for grouped TXID submissions
Integrity Root for package-level validation
Verification Record
Retrieval Package
Independent Validation Instructions
Tier-bound capacity controls
Capacity Rule
T1 accepts 1 TXID, T2 accepts up to 25 TXIDs, and T3 accepts up to 100 TXIDs per batch. Submissions above the selected tier limit are not accepted. Submissions above 100 TXIDs require a separate Gravity review rather than automatic Relay processing.
Integrity Root
Every Relay tier is designed to include an Integrity Root. For T1, the Integrity Root represents the single submitted TXID record package. For T2 and T3, Gravity groups submitted TXIDs into a deterministic Batch Manifest and generates an Integrity Root that represents the submitted set.
What Relay does:
Relay converts submitted Bitcoin transaction references into standardized Gravity verification records through an invoice-bound retrieval and artifact workflow. The service is designed for situations where Bitcoin activity needs verifiable records, manifests, and retrieval continuity after settlement. Gravity does not custody funds, move Bitcoin, or broadcast transactions on behalf of clients.
How it works:
1. Enter Bitcoin TXID references
2. Generate Relay invoice
3. Pay the invoice
4. Gravity waits for confirmation settlement
5. Relay issued records enter Gravity preservation and retrieval continuity
6. Records become retrieval-ready
7. Verification and retrieval remain tied to the invoice ID
System behavior:
• Each TXID produces an artifact
• Batch submission limits apply per tier
• Total usage is tracked and enforced
• Access expires after their active window
Relay converts submitted Bitcoin transaction references into standardized Gravity verification records through an invoice-bound retrieval and artifact workflow. The service is designed for situations where Bitcoin activity needs verifiable records, manifests, and retrieval continuity after settlement. Gravity does not custody funds, move Bitcoin, or broadcast transactions on behalf of clients.
How it works:
1. Enter Bitcoin TXID references
2. Generate Relay invoice
3. Pay the invoice
4. Gravity waits for confirmation settlement
5. Relay issued records enter Gravity preservation and retrieval continuity
6. Records become retrieval-ready
7. Verification and retrieval remain tied to the invoice ID
System behavior:
• Each TXID produces an artifact
• Batch submission limits apply per tier
• Total usage is tracked and enforced
• Access expires after their active window
What you receive:
- Invoice-bound transaction artifact records
- Structured transaction grouping by batch
- Integrity-linked retrieval records
- Human-readable transaction preservation summaries
- Stronger package integrity support for larger transaction sets
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 Batch Manifest and Integrity Root support. Best for larger evidence packages requiring grouped preservation, retrieval, and independent validation.
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 Batch Manifest and Integrity Root support. Best for larger evidence packages requiring grouped preservation, retrieval, and independent validation.
Relay does not transmit client documents through Bitcoin and does not relay Bitcoin transactions. Relay records submitted Bitcoin transaction references into Gravity’s deterministic artifact system after invoice settlement.
Relay is designed for situations where Bitcoin transaction references must become grouped, preserved, retrievable, and independently referenceable Gravity records rather than remaining scattered across wallets, screenshots, spreadsheets, or public explorers alone.
Relay is designed for situations where Bitcoin transaction references must become grouped, preserved, retrievable, and independently referenceable Gravity records rather than remaining scattered across wallets, screenshots, spreadsheets, or public explorers alone.
After required confirmations, Relay issued records enter Gravity’s deterministic retrieval and finalization workflow before becoming retrieval-ready through the associated invoice ID.
What happens next?
1. Generate a Relay invoice.
2. Complete Bitcoin settlement.
3. Gravity waits for the required confirmations.
4. Relay records are prepared automatically.
5. Completed Relay records are retrieved using your Invoice ID.
1. Generate a Relay invoice.
2. Complete Bitcoin settlement.
3. Gravity waits for the required confirmations.
4. Relay records are prepared automatically.
5. Completed Relay records are retrieved using your Invoice ID.
Priority Processing moves qualifying requests ahead of standard queue order. It does not bypass payment settlement, required Bitcoin confirmations, verification requirements, or access controls.
What is a TXID?
A TXID is the public reference number for a Bitcoin transaction.
You can usually find it:
Invoice ID = Gravity retrieval reference
TXID = Bitcoin transaction reference
A TXID is the public reference number for a Bitcoin transaction.
You can usually find it:
- In your wallet transaction history
- In your exchange withdrawal history
- In a Bitcoin block explorer
Invoice ID = Gravity retrieval reference
TXID = Bitcoin transaction reference
When to use Relay
Relay is for Bitcoin-settled verification records
Use Relay when Bitcoin activity needs invoice-bound verification records, manifests, and retrieval artifacts after settlement.
Verify occurrenceConfirm that a Bitcoin transaction reference was submitted into a Gravity workflow.
Preserve continuityKeep transaction-reference context available for later review.
Create retrievalGenerate an invoice-linked record path that can be retrieved after settlement.
Record Organization
Every Gravity service package includes client-supplied record organization fields so the issued record remains understandable during future retrieval.
Record Title identifies what is being preserved.
Group Label organizes the record under a client-defined category such as Treasury, Legal, Operations, Finance, or Evidence.
Record Context briefly explains why the record package exists and how it should be understood later.
These fields become part of the invoice-bound Gravity record package, including retrieval materials, manifests, and package summaries.
Every Gravity service package includes client-supplied record organization fields so the issued record remains understandable during future retrieval.
Record Title identifies what is being preserved.
Group Label organizes the record under a client-defined category such as Treasury, Legal, Operations, Finance, or Evidence.
Record Context briefly explains why the record package exists and how it should be understood later.
These fields become part of the invoice-bound Gravity record package, including retrieval materials, manifests, and package summaries.
TIER I — LIMITED
300,000 sats
Submit 1 TXID per batch.
Best for single transaction documentation.
Usage tracked under access status.
300,000 sats
Submit 1 TXID per batch.
Best for single transaction documentation.
Usage tracked under access status.
TIER II — EXTENDED
750,000 sats
Submit up to 25 TXIDs per batch.
Best for grouped transaction sets.
Usage tracked under access status.
750,000 sats
Submit up to 25 TXIDs per batch.
Best for grouped transaction sets.
Usage tracked under access status.
TIER III — ARCHIVE
1,500,000 sats
Submit up to 100 TXIDs per batch.
Submissions above 100 TXIDs are not accepted under Tier III.
Includes Relay Certificate, Submission Manifest, Batch Manifest, Integrity Root, Verification Record, Retrieval Package, and Independent Validation Instructions.
Usage tracked under access status.
Once payment is detected on the Bitcoin network, the payment transaction may have its own TXID. That payment TXID is not the same as the submitted Relay transaction references.
Next Step
Relay uses TXIDs as submitted transaction references. TXIDs are not access status keys.1,500,000 sats
Submit up to 100 TXIDs per batch.
Submissions above 100 TXIDs are not accepted under Tier III.
Includes Relay Certificate, Submission Manifest, Batch Manifest, Integrity Root, Verification Record, Retrieval Package, and Independent Validation Instructions.
Usage tracked under access status.
Use your invoice ID for Relay status, access, and artifact retrieval.
• Invoice ID controls service status and access.