Create account

replied 1998d
now we get the same typeerror as before
replied 1998d
Ok, thanks for your patience - I think I've gotten to the bottom of it.
I've been using [email protected] and there seems to be an incompatibility with the latest version bitcoind-rpc
replied 1998d
@0.8.1
I've updated the package.json with the required version numbers.

Try downloading and running again.
replied 1998d
Heading to bed now but will give it another go in the am! Thank you for all your hard work. :)
replied 1998d
Ok, and thanks for you help with debugging. I'll see you in the morning!
replied 1997d
Good morning! So with the most recent download, I edited the config to have my username & password, as well as config.bchdgrpcenabled = true;
config.bchdhost = '127.0.0.1:8335';.

sin
replied 1997d
Good morning! Ok - let try, in package.json file, change
"bitcoinjs-lib" : ">=3.3.2"

to

"bitcoinjs-lib" : "3.3.2"
replied 1997d
seems to be working! Still getting a handshake error now and then but the output rn looks like:
"SQL processing queue:485
Processing Block Into SQL:534599
SQL processing queue:656
Pro
replied 1997d
That's great! It looks like it is working.
It acquires a lock on the db while processing history so you won't be able to run any queries on it until it is up to date - it'll take a few
replied 1997d
hours.
replied 1997d
https://memo.cash/a/8f10828b45

Still some minor issues.
For example, clicking a notification just leads to perpetual loading rather than serving up the post / reply / etc/
replied 1997d
Good to hear.

One other setting you might want to change - the client uses bitbox as a utxo server by default. You can test the utxo server functionality by changing the /release/js/c
replied 1997d
updated & working!
replied 1997d
onfig.js file from

utxoServer = "https://rest.bitcoin.com/v2/";

to

utxoServer = "http://127.0.0.1:3123/v2/";

Then reload the client, and click on your balance to see if it grabs
replied 1997d
the utxos from your local node.
replied 1997d
ohp... working now. Just had to restart it I guess lol.
On restart I do get handshake errors still, but seems like I have main functionality.
replied 1997d
Looks about halfway done now.
replied 1997d
cessing Block Into SQL:534600
SQL processing queue:712
Processing Block Into SQL:534601
SQL processing queue:723
Processing Block Into SQL:534602
SQL processing queue:781
Processing
replied 1997d
Block Into SQL:534603
SQL processing queue:784
Processing Block Into SQL:534604
"
replied 1997d
ce all indexes and grpc is enabled on my node.
Running node index.js Fetched And Processed Upto Block 613740 however, I got the error: "/home/jettscythe/Documents/server/sqlforaction.
replied 1997d
js:489
var address = bitcoinJs.ECPair.fromPublicKeyBuffer(chunksIn[1]).getAddress();
^

TypeError: bitcoinJs.ECPair.fromPublicKeyBuffer is not a
replied 1997d
function
at getFirstSendingAddressFromTX (/home/jettscythe/Documents/server/sqlforaction.js:489:34)
at Object.sqlforaction.getSQLForAction (/home/jettscythe/Documents/server/s
replied 1997d
qlforaction.js:165:26)
at getSQLForTRX (/home/jettscythe/Documents/server/index.js:375:25)
at putSingleTransactionIntoSQLglobalvars (/home/jettscythe/Documents/server/index.js:
replied 1997d
511:19)
at putSingleTransactionIntoSQLglobalvarsResult (/home/jettscythe/Documents/server/index.js:505:5)
at Array.map (<anonymous>)
at processMempoolTX (/home/jettscythe/D
replied 1997d
ocuments/server/index.js:500:12)
at /home/jettscythe/Documents/server/index.js:482:51
at IncomingMessage.<anonymous> (/home/jettscythe/Documents/server/node_modules/bitcoind-rp
replied 1997d
c/lib/index.js:107:7)
at IncomingMessage.emit (events.js:203:15)"
The entire time.
I run log into member server, but the feed just says: "Something is wrong:Error."
On my BCHD
replied 1997d
node I also see: "http: TLS handshake error from 127.0.0.1:35608: EOF" still occurring