Should include MB/s and IOPS so that users may know how fast they are reading from things and get an idea of it they are hitting the theoretical maxes for the devices in question. Network bandwidth rate estimate for network sources.
Add rpc call to either read a block of data or read a merkle tree intermediate node over the network. This way, each arktika node won't need filesytem access to all chunks.
API already exists, need to add something to estimate the fee needed. Maybe using the fee rate 1/3 of the way into current mempool or something?
So we already have automatic sorting by fee, so high fee things get included first. But we can still be flooded by transactions for very low or zero cost, we should switch to a configurable max amount of block to be filled with low fee transactions. Maybe something like, at most 100k per block,at least one transaction (that way if someone makes a huge low fee transaction, it can still get in eventually). This way, we can start requiring fees to fill blocks and still allow older clients that do no fee to send transactions. The bitcoin solution was to do some complicated madness with larger enough transactions for funds that haven't moved in a long time being free, but that seems more complex with a limited upside.
[snowblossomcoin/snowblossom] Issue closed by fireduck64
[snowblossomcoin/snowblossom] Issue closed by fireduck64
[snowblossomcoin/snowblossom] Issue opened by fireduck64
[snowblossomcoin/snowblossom] Issue closed by fireduck64