bitcoin-s/chain
Torkel Rogstad a87858247c Service identifier and node cleanup (#522)
* Log messages more granularely in node

* Add pong message

* Rework P2P service identifier

The old implementation didn't catch the notion
that service identifiers was a bit field where
multiple services could be set at the same time.

* Make Peer take InetSocketAddress

Previously it took NetworkIpAddress.
This doesn't make any sense, as we
need to know the services bitfield
to construct a NetworkIpAddress.

* Clean up logs and toString methods

* Clean up node README and main method

* Make all networks final case objects

* Skip publishing of wallet, node and chain

* Clean up logging of node and chain modules

* Add logging of max height in SpvNodeMain

* Clean up Scaladoc and toStrings

* Add logging configuration as symlinks in node

We'll have to figure out a more stable solution to
configure logging for the SPV node, but for the time
being this is an acceptable solution.

* Fix 2.11 compiler error
2019-06-17 14:27:51 -05:00
..
src/main/scala/org/bitcoins/chain Service identifier and node cleanup (#522) 2019-06-17 14:27:51 -05:00
build.sbt Node (#490) 2019-06-04 09:53:00 -05:00
README.md Node (#490) 2019-06-04 09:53:00 -05:00

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.