This repository has been archived by the owner on Feb 26, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 103
BTC not showing up #14
Comments
Is worker.js running? Thats the process that checks the balance and sets the correct statuses.
…On Dec 28, 2017, 03:52 +0000, Matt0000 ***@***.***>, wrote:
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?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Thank you for the quick reply! Maybe that could be breaking it? |
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
The last two are actual transactions that I paid |
Looks like address wasnt imported in bitcoin core node for some reason. You can import it manually (make sure setting rescan to true). And investigate why it wasnt imported.
PS. Core is fully synced, I assume
…On Dec 28, 2017, 11:03 +0000, Matt0000 ***@***.***>, wrote:
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
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Ok, from now on I'm passing |
Yes, otherwise latest transactions wont be visible
…On Dec 28, 2017, 15:02 +0000, Matt0000 ***@***.***>, wrote:
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?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Oh, and you need rescan only one time, to manually import address that wasnt imported for some reason. See importaddress rpc call in documentation
…On Dec 28, 2017, 15:02 +0000, Matt0000 ***@***.***>, wrote:
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?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
3LRqq2SSQMozv9ucBvgTGybiuuNYLoaPK5
at 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.
The text was updated successfully, but these errors were encountered: