Antioch Peverell
Antioch Peverell
We have some very tight coupling between `node` and `wallet` regarding json serialization/deserialization of transactions. After building a transaction a wallet will "push" the transaction to the node, to broadcast...
We pass `is_floo` around in a bunch of places related to the `BIP32Hasher`. This is used to differentiate between `mainnet` and `floonet` with some prefix bytes on the public and...
This issue is more of a reminder to go investigate the `partitions` crate * https://docs.rs/crate/partitions/0.2.4 This is an implementation of https://en.wikipedia.org/wiki/Disjoint-set_data_structure This feels _very_ similar to what we do with...
### tl;dr * New Cuckarooz PoW and header version 4 for latest hardfork. * TUI optimizations and overal code improvements * Server and backend DB code optimizations and improvements *...
We call `write()` on `Writeable` when serializing things to bytes. Not just for serializing full data but also when we serialize during a call to `hash()`. Block hash -> BlockHeader...
We currently enforce uniqueness across inputs, outputs and kernels in both transactions and blocks. This is checked via `verify_sorted_and_unique()`. This is done by kernel __hash__ so two kernels with the...
I have been doing some investigation into our MMR backend files, how/when we fsync them to disk and a variety of assumptions we make around this, both implicit and explicit....
Node appears to be locked up when serving a txhashset archive to a syncing peer. The txhashset "response" is a small message with an "attachment" containing the bytes for `txhashset.zip`....
I have spent a few days digging into the low level process of how we handle the "transactional" txhashset extension. We now have a better understanding of exactly what the...
These are important pieces of internal data that we maintain per block. It would be really useful to expose them at the individual block level via the api somehow. Most...