Closed benbjohnson closed 5 years ago
Does this address #33 and/or #34? Or is it a straight port of the existing code?
Does this address #33 and/or #34? Or is it a straight port of the existing code?
It's mostly a straight port except that the block storage is updated so that we can compute the best chain instead of doing the weird block slots data structure that existed in the JS implementation. #33 should be resolved with this. #34 wouldn't be difficult to change now but you had a comment on there that made it sound like that might not be important.
Block times appear to be rounded to whole seconds:
Did we lose auto lookup by ip? Is that something we need a Go alternative for?
When a node restarts with a new version, the Node type
details are not updated in the UI.
When a node goes down, it no longer shows as gray (remains green as if online).
Block times appear to be rounded to whole seconds
Fixed
Did we lose auto lookup by ip? Is that something we need a Go alternative for?
For some reason I thought we were pulling geo from the trusted
file. I added GeoIP lookup via MaxMind and it downloads the MaxMind lite DB into the Docker container.
When a node restarts with a new version, the Node type details are not updated in the UI.
Fixed
When a node goes down, it no longer shows as gray (remains green as if online).
Fixed.
Also, I didn't mention it already but there are now /debug/nodes
and /debug/blocks
endpoints to dump out the current state of the DB in pretty-print JSON for easier debugging.
For some reason I thought we were pulling geo from the trusted file
We are, but not for everyone.
This commit converts the backend from node.js to Go.
TODO
BlockPropagation()
MinerCount()
/external
API of new highest block.