paritytech / paritytech/json-rpc-interface-spec
[Archive API] Add transaction receipt query endpoint for historical transactions
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 37
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Problem Statement
DApp developers currently face challenges accessing transaction receipts on the Polkadot network. The existing WebSocket connections are unreliable, and there's no efficient way to query transaction status for historical transactions without downloading entire blocks. This creates a significant developer experience gap compared to other blockchain frameworks.
Proposed Solution (from discussion internally in the matrix chat):
Archive API Enhancement
- Add new function to the Archive API specifically for transaction status queries
- Should work over stateless HTTP connections (not require stateful WebSocket)
- Would enable querying of historical transaction status efficiently
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified. Start by reviewing the Archive API specification and the referenced internal matrix discussion to determine the endpoint contract for historical transaction status over stateless HTTP. Done means the Archive API includes a defined transaction-status query endpoint that avoids downloading entire blocks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- api, blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100