Tracking: on-chain transactions

[hopeyen]

Problem statement

Missing on-chain components. The original plan was to wait for protocol v2 but we might as well go ahead exploring the options to make it compatible with v1.

Expectation proposal

Options to be compatible with protocol v1

• Allocation based on subfiles
• Allocation based on an IPFS file to an indexer url

Create a Transaction manager entity that

• Allows the Publisher to deploy an IPFS hash on-chain
  - [ ] Server registers its URL
• Add a CLI for the server for allocation management Feat: Service allocation management #36
  • send an allocate transaction against the IPFS hash -> Get allocation_id
  • send an close transaction against the IPFS hash with 0x POI
• Service payment collection
  • require moving service to indexer-rs framework Feat: Port server to indexer framework #30
  • send redeem tx to Escrow contracts (This should be handled by indexer-agent collect tap ravs graphprotocol/indexer#831
• Client wallet query payments Feat: Client wallet connection and dumb TAP payment #21
  • sends deposit transactions - identify indexers as receivers
  • Receipt Signer
  • Send receipts in query requests (chunking wrt to package sizes and budget)

[hopeyen]

Start with staking contract that enables on-chain transactions allocate and closeAllocation
and Escrow contract that enables deposit, depositMany, and redeem