[FEATURE]: Add transaction and receipt lookup RPC methods
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 58/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- api, backend-api-design
Research direction
Start by locating the JSON-RPC server and the code that handles transaction submission, block queries, and account balances. Trace how transactions and receipts are stored and serialized, then add lookup methods that return the requested data or null. Done means tests cover existing transactions and receipts, unknown hashes, and continued operation of existing RPC methods.
Written by the indexing model from the issue text.
Description
Description
I noticed that MiniChain's RPC server currently supports sending transactions and querying blocks and account balances. However, there are no RPC methods to look up a transaction or its receipt using a transaction hash.
This would be useful for developers building wallets, explorers, or applications on top of MiniChain, as they need a way to check transaction details and execution status.
Proposed Changes
Add two RPC methods:
mc_getTransactionByHash(txHash)– Returns the transaction details for the given hash, ornullif it is not found.mc_getTransactionReceipt(txHash)– Returns the corresponding receipt, including status, gas used, logs, and contract address, ornullif no receipt is available.
Expected Outcome
Developers should be able to retrieve transaction details and execution results directly through MiniChain's JSON-RPC interface.
Testing
- Test lookup of an existing transaction.
- Test lookup of an existing transaction receipt.
- Test unknown transaction hashes.
- Ensure existing RPC methods continue to work.
I would like to work on this feature if the maintainers consider it useful.
- Dominant language
- Python
- Stars
- 12
- Forks
- 27
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from StabilityNexus/MiniChain
-
[BUG]: Handle JSON-RPC notifications and empty batches correctlyPossibly taken @Muneerali199 claimed this 10 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
StabilityNexus/MiniChain#177 · 2 comments ·
Maintainers usually reply within 1 day
-
automatic-copyright-year: keep README copyright currentPossibly taken @anshulchikhale30-p claimed this 7 days ago. Opendocumentation enhancement
Difficulty 3/5 Half a day Newbie friendliness 35/100
StabilityNexus/MiniChain#189 ·
Maintainers usually reply within 1 day
-
Difficulty: bound per-block EMA moves, add a difficulty floor, and preserve state across restartsPossibly taken @anshulchikhale30-p claimed this 7 days ago. Openbug documentation enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
StabilityNexus/MiniChain#187 ·
Maintainers usually reply within 1 day
-
[BUG]: Blocks on a different parent are classified INVALID and get the sender bannedPossibly taken @kansalakshat claimed this 7 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
StabilityNexus/MiniChain#185 ·
Maintainers usually reply within 1 day
-
[BUG]: P2P sync downloads full 500-block chunks without headers-first validationPossibly taken @anshulchikhale30-p claimed this 14 days ago. Openbug documentation enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
StabilityNexus/MiniChain#178 ·
Maintainers usually reply within 1 day
All issues in StabilityNexus/MiniChain
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/datasets#9128 ·
Maintainers usually reply within 1 day
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenHands/extensions#975 ·
Maintainers usually reply within 1 day
-
Function/dict state handlers can't supply provider-state injected values (`generate.provider_state`)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pact-foundation/pact-python#1789 ·
Maintainers usually reply within 9 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
juandresrodca/AdminForge#66 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day