socket.error: [Errno 111] Connection refused #9
Comments
|
I have RPC enabled too, but don't see a config file to enter the credentials. If that is in fact the issue. |
|
I see the issue, in my bitcoin.conf file I have txindex=1 It appears you cannot have prune and txindex enabled at the same time. You need to disable pruning and redownload the blockchain. |
petertodd
pushed a commit
that referenced
this issue
Aug 24, 2017
Add witness merkle tree; Add parameters to stream_(de)serialize and (de)serialize methods; Check witness merkle tree. CheckBlock: - check MAX_BLOCK_WEIGHT; - check witness witnessScript; - check witness commitment.
petertodd
added a commit
that referenced
this issue
Aug 24, 2017
5cd3467 fixed issue in is_witness_scriptpubkey where self[0] is interpretted as str instead of the necessary int (Surya Bakshi) 2b50596 Add segwit block (de)serialization. (#9) (the9ull) d8a1a0f Closely match Core's (de-)serialization; remove old test case (Bob McElrath) 0c09892 Encode hashtype as signed (following bitcoind) (Bob McElrath) eca69b7 CTxWitness class, new message types (Bob McElrath) f4d1d2a BIP143 implementation and test vectors (Bob McElrath) 580f466 Initial segwit implementation, works with P2WPKH addresses (Bob McElrath) Pull request description: This is my initial implementation. It correctly serializes and deserializes P2WPKH segwit transactions. I haven't tested the other transaction types. Please don't merge this yet, but I wanted to make it available for others to work on. TODO - ~~BIP 143 tx signing~~ - ~~`CBlock` modifications to support witness data~~ - ~~P2WSH and BIP16 embedded scripts~~ - ~~tests!~~ Tree-SHA512: bc96c263467ae3f27aa86472afb4e29e6c1d81da527832ed153b05faa06ef8152ce518f9c9c1c1fdae45de7f93173c77fa237b160d5cfb7d1068532a8849c9f3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am almost there, but I get the following error when I execute:
python bump-fee.py 2010aa960b330022b2db175410b13530dc6bdd1a9b38071e55cdd45d96b51a64socket.error: [Errno 111] Connection refusedThe text was updated successfully, but these errors were encountered: