Open roccomuso opened 4 years ago
@roccomuso The staking addresses are stored in the db-sync database in the format e1... and we query them in this form. So if you prefix the stake key you provided with e1, which results in e1c567f4e17b7a342b7575c4ccd123250b45efb70375240965c5c6ae93, our endpoint shows the same result as cardano scan. Notice that the second key you provided undergoes the same effects, it works for our endpoint, but doesn't work on cardano scan until you delete the e1 prefix.
Another question, How do I get also the "De registered" actions. Like shown here: https://cardanoscan.io/stakeKey/eea509f388819c0cb3a80a48360adab708b41980a9ea771890711963?tab=stakehistory
There's no stake key history API at the moment?
@roccomuso There is https://explorer2.adalite.io/api/account/stakeRegistrationHistory/e1eea509f388819c0cb3a80a48360adab708b41980a9ea771890711963 :) Note that i also added e1. FYI there's also /withdrawalHistory but cardano db sync still does not push rewards to the DB.
I was playing with the new api
account/delegationHistory
and noticed that not all the staking keys are returning consistent result.For example this address:
c567f4e17b7a342b7575c4ccd123250b45efb70375240965c5c6ae93
Id does seem to be delegating in Cardanoscan: https://cardanoscan.io/stakeKey/c567f4e17b7a342b7575c4ccd123250b45efb70375240965c5c6ae93
But returns empty result
[]
in adalite:https://explorer2.adalite.io/api/account/delegationHistory/c567f4e17b7a342b7575c4ccd123250b45efb70375240965c5c6ae93
This
e10fda85992352eb41fcfa52f06e0065d3ee7e3c7f82e1d58861bbbd76
instead works on both.