Create account

replied 2025d
I'm not sure of any other way to run it. I've always called with just ./bchd or since downloading from the aur just bchd works lol
replied 2025d
Ok, I have a new theory, can you try, on line 325, change

rpc.getBlock(ret.result, false, processBlockIntoDB);

to

rpc.getBlock(ret.result, 0, processBlockIntoDB);

(you can remove
replied 2025d
done! Now we get:

Processing Block Into SQL:525471
{ code: -8,
message:
'Failed to parse request: parameter #2 \'verbose\' must be type bool (got number)' }
Wait 0 seconds
replied 2025d
ok, let's try
rpc.getBlock(ret.result, "", processBlockIntoDB);
replied 2025d
now we get the same typeerror as before
replied 2025d
Ok, thanks for your patience - I think I've gotten to the bottom of it.
I've been using bitcoind-rpc@0.7.1 and there seems to be an incompatibility with the latest version bitcoind-rpc
replied 2025d
@0.8.1
I've updated the package.json with the required version numbers.

Try downloading and running again.
replied 2025d
Heading to bed now but will give it another go in the am! Thank you for all your hard work. :)
replied 2025d
Ok, and thanks for you help with debugging. I'll see you in the morning!
replied 2025d
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 2025d
Good morning! Ok - let try, in package.json file, change
"bitcoinjs-lib" : ">=3.3.2"

to

"bitcoinjs-lib" : "3.3.2"
replied 2025d
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 2025d
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 2025d
hours.
replied 2024d
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 2024d
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 2024d
updated & working!
replied 2024d
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 2024d
the utxos from your local node.
replied 2024d
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 2025d
Looks about halfway done now.
replied 2025d
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 2025d
Block Into SQL:534603
SQL processing queue:784
Processing Block Into SQL:534604
"
replied 2025d
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 2025d
js:489
var address = bitcoinJs.ECPair.fromPublicKeyBuffer(chunksIn[1]).getAddress();
^

TypeError: bitcoinJs.ECPair.fromPublicKeyBuffer is not a
replied 2025d
function
at getFirstSendingAddressFromTX (/home/jettscythe/Documents/server/sqlforaction.js:489:34)
at Object.sqlforaction.getSQLForAction (/home/jettscythe/Documents/server/s
replied 2025d
qlforaction.js:165:26)
at getSQLForTRX (/home/jettscythe/Documents/server/index.js:375:25)
at putSingleTransactionIntoSQLglobalvars (/home/jettscythe/Documents/server/index.js:
replied 2025d
511:19)
at putSingleTransactionIntoSQLglobalvarsResult (/home/jettscythe/Documents/server/index.js:505:5)
at Array.map (<anonymous>)
at processMempoolTX (/home/jettscythe/D
replied 2025d
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 2025d
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 2025d
node I also see: "http: TLS handshake error from 127.0.0.1:35608: EOF" still occurring
replied 2025d
repeating until I stop it
replied 2025d
the previous console.log line we added)