Tokens Did not Transfer from BlockDAG Node to Wallet #22
Comments
|
I think I have the same problem, however, there was a reported problem with this here: |
|
Goodday, on top of this chain this commands are mentioned. Update wallet ./blockdag-wallet qc updateblock (looks like it worked) when i run the first command i do ge the message please create a wallet first, [blockdag-wallet qc create]. during the setup process i did run the ./wallet.sh script and a wallet got created. any guidance on this? |
|
The node needs to be running for the server to accept the Remote Procedure Call (RPC) used to access bdag database and your wallet. I may well be entirely wrong about the possible reward for running a node which will depend what BlockDAG decides to do, #!/bin/bash The update block output will scroll and should look like this: |
|
Thank you Alan, sudo ./wallet.sh qx has been downloaded and installed at bin/qx. blockdag-wallet has been downloaded and installed at bin/wallet. result is that i do not get a private key and PK Address. |
|
Thank you everyone! I'll give the solution a try. |
|
@AlanJHancock, this is what I get. Not very encouraging for weeks of work. 2025-01-27|21:14:10.018 [INFO ] notify tx count txs=0 |
|
@AlanJHancock , I updated my servers and now all I get is the following when I run my Node. 2025-01-28|04:20:20.105 [WARN ] Side chain depth too large module=miner |
|
@DigiAdm01 Please make sure to pull the latest code from the |
|
I ran the following sequences: It did download something, not sure which version. When I checked the logs, I was getting: |
Asking for your expertise again. i can see blockdag is downloading blocks and imports new chain segment. Now still when i run the command i get the error Please create a wallet first,[blockdag-wallet qc create ] which is somewhat confusing to me. any suggestions? |
What command are you running exactly? |
|
Everything seems to be running smooth with the Node BUT here is what I get
I verified my PK address and it matches the above. I am still receiving the same output 2025-01-31|19:34:32.872 [INFO ] notify tx count txs=0 Yes I did verify all the updates. Even the text changes from MINNING...... ADRESS to ensure they say MINING_ADDRESS Any suggestions I might of missed? |
|
How doing now, guys? I installed BDAG node just today and am interested too... |
|
My results so far. Installation after a few hick ups went fine. Not 100% the documentation, also my knowledge and experience on this. That being said, i think i will make more profit with the mining app on my phone as through the node due to the crashes. |
|
Thanks for your feedback! Here's a typical example of what my node shows (through your script wallet-balance,sh)... does this mean i have earned something? 2025-02-10|17:12:15.633 [INFO ] notification rescan block start=16028582 end=16028834 Thanks once again! |
|
run the command: docker logs -f blockdag-testnet-network when you see f.e. 2025-02-10|14:53:19.023 [WARN ] Blockdag is downloading blocks... : Client in initial download module=miner It does mean it is still syncing. on the last line you can see the age 4m 1w 3d As far as i know as soon a that sync is completely done you will start mining and earning, not earlier, but perhaps someone can confirm that. |
|
Well, all my logs consist of following: 2025-02-09|22:18:56.581 [INFO ] Imported new chain segment number=28482 hash=875cd2..1e9472 blocks=1 txs=1 mgas=0.021 elapsed=13.092ms mgasps=1.604 age=4mo2w3d snapdiffs=3.84MiB triediffs=531.72KiB triedirty=653.22KiB I am not yet qualified enough to understand what that means... would be grateful for your considerations. |
|
i think you are still syncing, as the logs do mention it's importing chain segments that are 4 months , 2 weeks, 3 days old. |
|
It was just random lines I have cut from my logs... You can also check balance on https://bdagscan.com/address/address-of-your-node-wallet |
You are getting the rescan block messages because the node is still pulling blocks that are within the same block range as your node is pulling block start=16031062 end=16031522. |
|
@AlanJHancock are you running the node in Swindon ? |
No am not in Swindon that address is someone on Tiscali ISP |
|
@AlanJHancock |
My node is producing a lot of errors like this:
|
|
@AlanJHancock join us on Discord :-) |
|
Just a note for others the command line has changed to see your testnet BDAG wallet balance and no longer uses the "qc" option. The new command lines are as follows: Update wallet: ./blockdag-wallet bdagc updateblock LF |
I think you will find that the above method is not for the primordial testnet that started with a new genesis block. The bash script below is used on the primordial testnet set -xrpc_url="http://127.0.0.1:18545" echo Your Public Key : $pk_addr balance_hex=$(echo $response | jq -r '.result') balance_bdag=$(python3 -c "print(int('$balance_hex', 16) / 10**18)") Return balanceecho Your BDAG balance: $balance_bdag |
|
Ah yes thank you and super helpful 😊👍 |
and others
HI @dev001101,
I followed your advice provided on November 5th using the PK address generated by the BlockDAG script.
I did the following:
The node ran for about a week on the Testnet before i followed the above guidance, it said my balance is zero.
I also used my PK on the BlockDAG Explorer and it popped the famous 404 error (not found)
Any suggestions on checking my balance?
The text was updated successfully, but these errors were encountered: