Skip to content
This repository has been archived by the owner on Feb 26, 2020. It is now read-only.

BTC not showing up #14

Open
Matt0000 opened this issue Dec 28, 2017 · 7 comments
Open

BTC not showing up #14

Matt0000 opened this issue Dec 28, 2017 · 7 comments

Comments

@Matt0000
Copy link

Matt0000 commented Dec 28, 2017

So I seem to be having another issue.

I created a test transaction, sent the BTC, and after executing curl http://localhost:2222/check_payment/3LRqq2SSQMozv9ucBvgTGybiuuNYLoaPK5 I get {"btc_expected":0.00034435,"btc_actual":0,"btc_unconfirmed":0}

Is this normal? When I put the address 3LRqq2SSQMozv9ucBvgTGybiuuNYLoaPK5at bitref.com it can see the transaction so how come Cashier-BTC isn't able to?

EDIT: I am by no means an expert, but I have tried to recover my funds by downloading the database and extracting the WIF. After trying to convert it to a private key it comes out as invalid, so maybe the issue is that invalid WIFs are stored.

Inputting sample WIFs at http://gobittest.appspot.com/PrivateKey successfully gets the private key, but when I put my own WIFs from the database the site returns "Private key is not on curve" indicating they're invalid.

@Overtorment
Copy link
Owner

Overtorment commented Dec 28, 2017 via email

@Matt0000
Copy link
Author

Thank you for the quick reply!
I believe that it should be running. Since I want to keep it running, I used this forever js command for all three nodejs files:
forever start --minUptime 10000 --spinSleepTime 10000 worker.js

Maybe that could be breaking it?

@Matt0000
Copy link
Author

Matt0000 commented Dec 28, 2017

Ok, so I ran worker.js by with the normal nodejs command so that I can see the output and it does not seem to be updating. It lets me know that it keeps checking but everything still isn't showing



worker.js address: 33FAM6CpEv3rovcyhz7L3KrtvUTwWksMw5 expect: 0.005 confirmed: 0 unconfirmed: 0
worker.js address: 3LBNqsGtJU8H6U82EvQ4N8braZARG8vpVc expect: 0.005 confirmed: 0 unconfirmed: 0
worker.js address: 3LRqq2SSQMozv9ucBvgTGybiuuNYLoaPK5 expect: 0.00034435 confirmed: 0 unconfirmed: 0
worker.js address: 3DNHyWrDDnELrmWsGAwVwchYBRF3AehoEY expect: 0.0000072 confirmed: 0 unconfirmed: 0

The last two are actual transactions that I paid

@Overtorment
Copy link
Owner

Overtorment commented Dec 28, 2017 via email

@Matt0000
Copy link
Author

Ok, from now on I'm passing -rescan to the bitcoind binary, By having core synced, do you mean that I have to download the entire blockchain that is more than 100GB?

@Overtorment
Copy link
Owner

Overtorment commented Dec 28, 2017 via email

@Overtorment
Copy link
Owner

Overtorment commented Dec 28, 2017 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants