Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide some mappings between Algod v2 and Indexer #283

Open
purestaketdb opened this issue Jan 18, 2021 · 0 comments
Open

Provide some mappings between Algod v2 and Indexer #283

purestaketdb opened this issue Jan 18, 2021 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@purestaketdb
Copy link

The current state
https://developer.algorand.org/docs/reference/rest-apis/indexer/#block
https://developer.algorand.org/docs/reference/rest-apis/algod/v2/#get-v2blocksround

The proposed state
In every case where Algod v2 and Indexer v2 have the same field BUT an entirely different encoding - provide a) a definition of the value (i..e previous block hash in Indexer is ACTUALLY a b64 string) and then a mapping back to the other. So to make Indexer previous block hash equal to the Algod v2 previous block hash one has to decode from b64 and then encode into base32.

Provide any additional context
This may be obvious to the dev team, but I cannot tell you how much time i've wasted numerous times trying to puzzle out how something is encoded and how to translate it back into something else to verify it. The indexer DB and the msgpacked blocks are other examples of this.

@purestaketdb purestaketdb added the documentation Improvements or additions to documentation label Jan 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants
@purestaketdb and others