feat: registration, delegation, and MIR history account endpoints #292
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements 3 of the 10 remaining account related endpoints described in #256:
/accounts/{stake_address}/registrations- Querieshistorical_accounts_statefor registration history, then fetchesTxHashvalues fromchain_storeusing eachTxIdentifierto construct the Blockfrost aligned response./accounts/{stake_address}/delegations- Querieshistorical_accounts_statefor delegation history, resolvingTxHashviachain_store./accounts/{stake_address}/mirs- Querieshistorical_accounts_statefor MIR history, resolvingTxHashviachain_store.Main changes:
rest_blockfrostinitialization.handle_account_registrations_blockfrost,handle_account_delegations_blockfrost, andhandle_account_mirs_blockfrosttohandlers/accounts.rs.Notes:
accounts_statetohistorical_accounts_statealthough this would require passing the per stake address distribution on the message bus. Alternatively, we could rely on a second query in the rest handler to retrieve the account epoch stake fromaccounts_stateunder the assumption thatspdd-retention-epochsis configured to store all epochs.Next steps:
historical_accounts_stateand implement the corresponding REST handler.