mirror of
https://github.com/bitcoin-s/bitcoin-s.git
synced 2024-11-19 18:02:54 +01:00
c934d8efc2
* Address issue #673, also refactor fixture stuff to be in companion objects rather than traits so they can be re-used without extending the trait itself. This allows for more modularity with our fixtures * fix bugs in unit tests, address #675 to make MerkleBufferTests faster * Refactor test timeout in UpdateBloomFitlerTest * fix callback logic bug on matching unrelated txs/addresses in UpdateBloomFilterTest, re-order broadcasting of things to avoid async bugs hopefully * Make a def in NodeUnitTest, this keeps tests in the same suite from using the same config. This allows us to write multiple tests per suite, instead of just one. This also adds implicit parameters to our fixture constructors/destructors to properly create and destroy this config. The long term goal here also should be getting rid of config.initialize() we are calling everywhere as this is a anti-pattern, fixtures should take care of construction and destruction of things * Broadcast tx earlier in test case for UpdateBloomFilterTest * Rework NodeWithWalletTest to use the new fixtures we have in the node project, now use SpvNodeFundedWalletBitcoind |
||
---|---|---|
.. | ||
src/main/scala/org/bitcoins/chain | ||
build.sbt | ||
README.md |
chain
This is meant to be a stand alone project that process a new block / transaction and stores it. It also provides a interface to query information related to a blockchain.
The design goal with this project is to be agnostic of how the project is receiving the blockchain data, just that it processes and stores it. For instance you could provide the blockchain data via
- rpc
- zmq
- p2p
- sattelite
This project just stores relevant block
and transaction
information and allows
for it to be queried via a api.