- the object also manages unflushed history
- the history DB has its own version, starting at 0
This is the first step to making history management into
a separate service and to larger block sizes.
The next step is an improved history format, which I hope will both
save space and be a solution to issue #185. The DB should be able to
upgrade in-place without re-syncing the chain.
* Implemented electrum_header for BTG to include solution (needed for validation on clientside)
Add RPC_PORT for BTG node
* Added node regtest compatibility
* Updated unittests
* Changed chunksize and regtest rpc port
* Changed bits transfer format to decimal
* Add testnet v3 params and corrected coin name
* Extract the Equihash mixin from Zcash
The extracted EquihashMixin and DeserializerEquihash are used when
the Equihash POW support is needed but the Zcash transaction parsing
is not.
* Add Bitcoin Gold support
* Minor formatting fixing
- COIN and NET strip surrounding whitespace
- new environment variable RPC_HOST, similar to HOST, but
for RPC. Permits fine-grained control of which addresses
the RPC server listens on.
- HOST and RPC_HOST strip surrounding whitespace from hostnames
and IP addresses
- tests and documentation updated to match
* Construct unpacking functions for byte format up front to save time
wasted on parsing format string every iteration.
* Store length ahead of time as the overhead adds up.
* Reduce object attribute lookups in hash functions.
* Clean up lib pkg API changes. Unit test new "public" API members.
Underscore prefix for internal hash module funcs. Make bytes.fromhex a
public function.
* Document recent performance findings.
It turns out clients pass 0.10 instead of 1.0 as the protocol version.
Distinguish some handlers for 1.0 and 1.1 protocols.
Log protocol version request
Add tests of new library function
Based on #215 by JustinTArthur.
- Accept EVENT_LOOP_POLICY of uvloop
- Move initilisation from electrumx_server to controller
- SocksProxy now requires a loop
- Update tests
