feat: support horizon

[suchapalaver]

Horizon Gateway Upgrade

This horizon gateway provides TAP v2 receipt generation while maintaining full backward compatibility with existing v1 receipts from the upstream implementation.

Overview

This is a horizon-ready gateway that adds TAP v2 (collection-based) receipt support to the existing edgeandnode/gateway which only supports TAP v1 (allocation-based) receipts. This implementation generates exclusively v2 receipts while maintaining backward compatibility for processing existing v1 receipts.

Key Changes from Pre-Horizon Gateway

TAP Protocol Support

• Pre-Horizon: Only supports TAP v1 (allocation-based) receipts
• Horizon: Generates TAP v2 (collection-based) receipts, can process v1 receipts for redemption

Receipt Generation

• Upstream: Uses create_receipt(allocation, fee) for v1 receipts
• Horizon: Uses create_receipt(collection, fee, payer, data_service, service_provider) for v2 receipts

ID Types

• Pre-Horizon: Uses AllocationId for receipt generation and payment tracking
• Horizon: Uses CollectionId for receipt generation, supports both types for processing

Receipt Structure

v1 Receipts (Pre-Horizon):

• allocation_id: Address of the allocation
• timestamp_ns: Timestamp in nanoseconds
• nonce: Random nonce
• value: Fee amount in wei

v2 Receipts (Horizon):

• collection_id: Collection identifier
• payer: Address of the payer
• data_service: Address of the data service
• service_provider: Address of the service provider
• timestamp_ns: Timestamp in nanoseconds
• nonce: Random nonce
• value: Fee amount in wei

Migration from Pre-Horizon

For Operators

1. Dependencies: Updated tap_graph to support v2 receipts
2. Configuration: No configuration changes needed
3. Deployment: Requires horizon contracts to be deployed on the network
4. Compatibility: Can still process existing v1 receipts

For Indexers

1. Receipt Processing: Must support v2 receipt processing
2. Collection IDs: Should use collection IDs instead of allocation IDs
3. Backward Compatibility: Can still redeem any existing v1 receipts

[tmigone]

shouldnt this be collection?

[suchapalaver]

Right. Thank you!

[suchapalaver]

So this @tmigone is being consumed by other components I think and so I'm being conservative about changing the interface and that's what I'm trying to get at in the comments.

[tmigone]

Closing this PR in favor of: #1119. It contains the same changes with added fixes.