Idea: OP_RETURN Index
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 568
- Forks
- 447
- PR merge metrics
- No merged PRs in 30d
Description
Proposal:
- Query all
OP_RETURNdata for a given block - Filter query by a multi-byte prefix, so individual protocols may be targeted
Query responses contain the txid as well as the OP_RETURN data itself, so that clients may make additional requests for full transaction data.
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, tests, or entry points are named. Start by locating the server's block-query and indexing paths, then determine how OP_RETURN data and transaction IDs could be stored and queried. Done means supporting block queries and multi-byte-prefix filtering while returning each matching txid with its OP_RETURN data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100