* implement a basic tx db that stores how to spend revoked transactions
it's a simple db that stores spending tx indexed by their parent id
* bumped akka version to 2.4.8
* fixed wrong data type in CLEARING and NEGOTIATING handlers
* added a few common handlers
* moved sendAdd/receiveAdd logic to Commitments.scala
* moved htlc index to Commitments class
* cleaned up sig handlers
* removed unused variable
* storing their commit's txid so that we can identify spending tx
* added a log to unimplemented function 'handleTheirSpentCurrent'
* changed ascii art helpers->handlers
* fix misleading comments and code in Channel
* removed unused imports
* added test showing bug when two htlcs share the same r
* added a failing test showing that punish tx output isn't p2wpkh
* fix failing test
* use P2WPKH instead of P2PKH in our "punishment" tx
* fix failing test
* added helper methods in test
* fixed test
We use bitcoind 91abb77970f47b1f6166e564bc695ed30c75bb63
and lightningd 7727797bee8454d4bfaa310c578b94081187f59d from
https://github.com/sstone/lightning branch estimatefee.
Our interop test will now launch lightningd and bitcoind (in regtest mode).
This works on linux only.
* upgrade code to match latest lightningd
use secp256k1 format for sigs, update .proto, use timeouts in blocks insteads of seconds...
* update interrop test
* update comments and fix a few typos
* added nonreg tests on lightning types
* use our extensions for protobuf messages
* add comment to explain why we need getBlockCount
* create a specific data stucture for commitment data
* remove lenses
* move makeFinalTx to Helpers
* remove unused type, clean up CLOSING data
* code cleanup
* check revocation preimage
* use a "either" type to represent their next commit information
We either have their next revocation hash (most of the time), or their next commit
tx (when we've signed and are waiting for their revocation message)
