clemahieu
clemahieu
The class is a facade around the active_transactions class and exposes a query scheduler::limiter::available to see if there is capacity available and a method scheduler::limiter::insert which checks for availability before...
Currently the block table maps block_hash -> block data. Each block is keyed on random data which causes frequent database page splits, hurting performance and causing internal fragmentation. For highest...
Currently there is a limit on the total number of active transactions a node can track, however, there is not a limit on the number of transaction an individual bucket...
Moved in to nano::store: - nano::store::make_store - nano::store::write_database_queue Moved in to nano::voting: - nano::local_vote_history -> nano::voting::history - nano::vote_cache -> nano::voting::cache - nano::vote_processor -> nano::voting::processor - nano::vote_generator -> nano::voting::generator - nano::request_aggregator...
It is an incorrect rep configuration to operate a rep on multiple machines concurrently. We should be able to identify this configuration by: - A node tracks the vote timestamps...
When combining the following improvements: Time-bounded proofs of work: https://github.com/nanocurrency/nano-node/issues/4197 Bounded scheduler bucket sizes: https://github.com/nanocurrency/nano-node/issues/4194 Improved bucket sorting: https://github.com/nanocurrency/nano-node/issues/4169 The number of unconfirmed transactions a node needs to track will...
The general idea is to mix a timestamp along with the attempt nonce when generating proofs of work for blocks. The node would then be able to consider the timestamp...
Disabled in https://github.com/nanocurrency/nano-node/pull/4030 since windows wasn't assembling the CRYPTOPP_EXTRA files.