tari-project / blockchain-explorer-api Goto Github PK

probably a good idea, will take a look soon

• base node grpc client should be updated to have all the necessary calls used in this api
• then it should be published to npm
• and used in this repo

This will save having to keep the proto files up to date in this repo

Not sure if this is a FE or BE issue.

It looks like blocks are being skipped if more than one new block appears during a sync. This might very well be a non-issue (because I'm guessing prod will rarely fetch more than one block per sync), but in case it is, we might want to fix this.

If you guys were already aware of the issue, maybe you know where I can start looking?

i would like some tests to hold my hand during refactoring

Use websockets to stream block changes on block updates so the frontend can update automatically.

On sync check that the previous block's hash matches our store version, roll back to where we diverged and resync.