-
### Summary
This logging/tracing framework will help log every node operation (tracing the exact path blocks travel across components of the node), allowing it to be later analyzed with Python or o…
-
### Summary
The goal is to unify, simplify, & update builds into a single workflow. See the following PRs for more detail:
- #4256
- #4258
Still some work left with getting the Sanitizers …
-
### Summary
"There is one more algorithm that is present in legacy bootstrap but not in new ascending one, and that is frontier scan. Currently each request can only sample a single account, but wi…
-
### Summary
Piotr is working on potential vote hinting improvements for the Nano node. Screenshot from a heavily desynchronized local dev environment (~2M backlog):
![image](https://github.com/n…
-
### Summary
Please consider upgrading the docker ubuntu version to the newest version for all docker files based on ubuntu.
Ref: https://hub.docker.com/_/ubuntu?tab=description&page=1&ordering=l…
-
Nano Node v24.0 returns no values for unused accounts rather than 0 in pre v24.0
Nano Node PR: https://github.com/nanocurrency/nano-node/pull/3790
To Reproduce:
Use v24.0 API node in Nault
If …
-
Maybe there already is a mechanism of this kind but if there isn't, this is the issue:
Considering the edge case where new blocks are being published at a higher rate than the network can confirm i…
-
"Catch-all" issue to track non-functional maintenance updates (e.g. dependency versions). For example:
- [ ] Boost
- [ ] Cryptopp
- [ ] FlatBuffers
- [ ] LMDB
- [ ] Miniupnp
- [ ] QT
- [ ] Ro…
-
When we go beyond bandwidth limits we're not only doing unnecessary work by constructing confirmation requests / trying to broadcast blocks, but also there is no feed back process to inform the electi…
-
### Summary
Just opening up this issue for the link.
**This issue is only affecting new Nodes.**
**FIX: Downgrade to V22-V23.0 ... wait for sync and then upgrade to V23.3**
I'm still tes…