ergoplatform / ergoplatform/explorer-backend
Unique transaction representation
Open
API v1
- Dominant language
- Scala
- Stars
- 23
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Please provide the same json structure for transactions returned by `/transactions/unconfirmed`, `/transactions/unconfirmed/byAddress/
` and `/addresses//transactions`.For lighweight clients it is very useful to have `address` and `value` information in inputs (when it is possible)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the JSON responses from /transactions/unconfirmed, /transactions/unconfirmed/byAddress/
, and /addresses//transactions. Trace the entry points that produce these responses and identify where their transaction representations diverge. Done means the endpoints share one structure and include address and value information in inputs where possible.Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend, blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100