Second Day:
Topic: [CHALLENGE] Run A Bitcoin Node: 14 Days To 14 Merits - page 82. (Read 19213 times)
Where is everyone else
All you have to do is run a node and get it synced - no strings attached.If this is still open Will setup my system later today and join the "Run A Bitcoin Node challenge"
Though from the looks of this looks like that 1000merit barrier sent users watching from the fence, but challenge accepted.
Bitcoin core downloaded
and now waiting for the pre sync to be done and should see some progress...25 weeks to go
Let the fight for Ram begin....Chrome just joined the chat
DAY 1
Progress: (valid as of the creation date of this post)
If you see any error in the progress report like your name isn't listed correctly, and so on, please let me know so I can fix it.
Code:
Day 1:
kuriboh
Day 6:
bayu7adi
Day 11:
oktana
Shishir99
Day 12:
spiker777
Day 13:
SilverCryptoBullet
apogio
Day 15+:
DYING_S0UL (awaiting 99% synced)
If you see any error in the progress report like your name isn't listed correctly, and so on, please let me know so I can fix it.
Day 11
Day 13
Code:
{
"chain": "main",
"blocks": 826550,
"headers": 826550,
"bestblockhash": "00000000000000000003af57904acc3564a0f71e4cec5f5154df6c58499ccc9b",
"difficulty": 73197634206448.34,
"time": 1705753719,
"mediantime": 1705750068,
"verificationprogress": 0.9999980860976642,
"initialblockdownload": false,
"chainwork": "00000000000000000000000000000000000000006659c2c68026f36e506fe79f",
"size_on_disk": 4924156856,
"pruned": true,
"pruneheight": 824053,
"automatic_pruning": true,
"prune_target_size": 4999610368,
"warnings": ""
}
Day 11
Code:
{
"chain": "main",
"blocks": 721281,
"headers": 826537,
"bestblockhash": "000000000000000000027119328593460d4855e50265b017a5f3f70d1057b444",
"difficulty": 26643185256535.46,
"time": 1643684204,
"mediantime": 1643682249,
"verificationprogress": 0.7405031947519984,
"initialblockdownload": true,
"chainwork": "000000000000000000000000000000000000000027f694d30cbed896d7ca579e",
"size_on_disk": 371440213225,
"pruned": true,
"pruneheight": 400915,
"automatic_pruning": true,
"prune_target_size": 499999834112,
"warnings": ""
}
DAY 13:
Code:
{
"chain": "main",
"blocks": 826528,
"headers": 826528,
"bestblockhash": "00000000000000000002a28d6e42a52050c498763666c128b3bf892a2fd82bf8",
"difficulty": 73197634206448.34,
"time": 1705741563,
"mediantime": 1705739934,
"verificationprogress": 0.9999970392334309,
"initialblockdownload": false,
"chainwork": "000000000000000000000000000000000000000066540a266dd9d07996c75bb9",
"size_on_disk": 616003949862,
"pruned": false,
"warnings": ""
}
"chain": "main",
"blocks": 826528,
"headers": 826528,
"bestblockhash": "00000000000000000002a28d6e42a52050c498763666c128b3bf892a2fd82bf8",
"difficulty": 73197634206448.34,
"time": 1705741563,
"mediantime": 1705739934,
"verificationprogress": 0.9999970392334309,
"initialblockdownload": false,
"chainwork": "000000000000000000000000000000000000000066540a266dd9d07996c75bb9",
"size_on_disk": 616003949862,
"pruned": false,
"warnings": ""
}
...
Just curious, don't you have control over when and why your device goes off, for a shutdown? I strongly advise to shutdown Bitcoin Core always gracefully as you don't want to risk that your chainstate and blocks data may get corrupted which could happen to my knowledge.
It doesn't mean you'd need to re-download the blockchain, but cleaning up such a corruption takes extra steps that you can easily avoid.
If your computer is unstable, fix the causes of instability first. Unreliable power is best mitigated with a laptop which can overcome wall power issues with his built-in battery.
No, my computer is not broken. Sometimes it could be that I took it out with me. I know about block data getting corrupted, and it happened to me 2 times already (sadly). What I have learnt from it is that it is better that your device suddenly goes off than your device going off when you’re trying to shutdown Bitcoin core appropriate. If let’s say your laptop gets low and you do not shut down Bitcoin core, when it gets back on, it continues (from my observations).
DAY 15 progress: Almost Finished...
DAY 6
+2,98%
+2,98%
I started downloading Bitcoin Core today. It appears that it will be very late because of how slowly my network is operating here, but it should be fine in a while. It might crash very soon, though.
1st Day
1st Day
Day (11) and 12 Progress:
Unfortunately I couldn't send Day 11 report yesterday. Kindly accept my apology. I also couldn't get the blockchaininfo for yesterday.
Code:
{
"chain": "main",
"blocks": 439480,
"headers": 826434,
"bestblockhash": "000000000000000000c9dfaaac6654150ae5ad0d57bb5b90b7cd6d79788dbae2",
"difficulty": 254620187304.0614,
"time": 1479454024,
"mediantime": 1479451225,
"verificationprogress": 0.1797939415491666,
"initialblockdownload": true,
"chainwork": "0000000000000000000000000000000000000000002f1f3cd74cc81e187546f3",
"size_on_disk": 104040783102,
"pruned": true,
"pruneheight": 0,
"automatic_pruning": true,
"prune_target_size": 299999690752,
"warnings": ""
}
"chain": "main",
"blocks": 439480,
"headers": 826434,
"bestblockhash": "000000000000000000c9dfaaac6654150ae5ad0d57bb5b90b7cd6d79788dbae2",
"difficulty": 254620187304.0614,
"time": 1479454024,
"mediantime": 1479451225,
"verificationprogress": 0.1797939415491666,
"initialblockdownload": true,
"chainwork": "0000000000000000000000000000000000000000002f1f3cd74cc81e187546f3",
"size_on_disk": 104040783102,
"pruned": true,
"pruneheight": 0,
"automatic_pruning": true,
"prune_target_size": 299999690752,
"warnings": ""
}
Unfortunately I couldn't send Day 11 report yesterday. Kindly accept my apology. I also couldn't get the blockchaininfo for yesterday.
Judging by your screenshot, the wallet is "Up to date.", which means it's connected. Click Window > Peers to confirm it's connected.
Maybe you're just not used to seeing the real interface without IBD
You can create a wallet now.
Maybe you're just not used to seeing the real interface without IBD
You can create a wallet now.Yes, It was up to date and I understood that. Yes, indeed, I am not used to seeing this interface. But, What I was trying to say was, that there was some connection issue with my device. Later I used a VPN and everything worked fine. Now I have created a wallet as well.
@Shishir99 from your screenshot it says that your node is up to date. So all you have to do is every day keep posting it to prove that you are still running it.
Sure. I will continue posting my up-to-date wallet. But, I don't want to top up this wallet for now. I hope it's okay.
Day 10
Progress: (valid as of the creation date of this post)
If you see any error in the progress report like your name isn't listed correctly, and so on, please let me know so I can fix it.
Congratulations to tech30338 for finishing the challenge: You will receive your merit shortly.
@Shishir99 from your screenshot it says that your node is up to date. So all you have to do is every day keep posting it to prove that you are still running it.
Code:
Day 5:
bayu7adi
Day 9:
Shishir99
Day 10:
oktana
Day 11:
spiker777 (awaiting progress report for day 11)
Day 12:
SilverCryptoBullet
apogio
Day 14:
tech30338
DYING_S0UL (awaiting 99% synced)
bayu7adi
Day 9:
Shishir99
Day 10:
oktana
Day 11:
spiker777 (awaiting progress report for day 11)
Day 12:
SilverCryptoBullet
apogio
Day 14:
tech30338
DYING_S0UL (awaiting 99% synced)
If you see any error in the progress report like your name isn't listed correctly, and so on, please let me know so I can fix it.
Congratulations to tech30338 for finishing the challenge: You will receive your merit shortly.
@Shishir99 from your screenshot it says that your node is up to date. So all you have to do is every day keep posting it to prove that you are still running it.
Finish the task for 14 days , did everyone finish syncing? This is nice everyone is participating, and trying to run their own node
Day 12
Code:
{
"chain": "main",
"blocks": 826391,
"headers": 826396,
"bestblockhash": "00000000000000000001e85f7b3b5fb30a6b067f26ede6d174c8d6b5b59c1932",
"difficulty": 73197634206448.34,
"time": 1705656425,
"mediantime": 1705652580,
"verificationprogress": 0.9999856862007611,
"initialblockdownload": false,
"chainwork": "000000000000000000000000000000000000000066306987703f483fccd0aeb8",
"size_on_disk": 4922961344,
"pruned": true,
"pruneheight": 823901,
"automatic_pruning": true,
"prune_target_size": 4999610368,
"warnings": ""
}
"chain": "main",
"blocks": 826391,
"headers": 826396,
"bestblockhash": "00000000000000000001e85f7b3b5fb30a6b067f26ede6d174c8d6b5b59c1932",
"difficulty": 73197634206448.34,
"time": 1705656425,
"mediantime": 1705652580,
"verificationprogress": 0.9999856862007611,
"initialblockdownload": false,
"chainwork": "000000000000000000000000000000000000000066306987703f483fccd0aeb8",
"size_on_disk": 4922961344,
"pruned": true,
"pruneheight": 823901,
"automatic_pruning": true,
"prune_target_size": 4999610368,
"warnings": ""
}
DAY 12:
Code:
{
"chain": "main",
"blocks": 826379,
"headers": 826379,
"bestblockhash": "000000000000000000012359df8ed548d973ef4c68a2283092385fff80791d44",
"difficulty": 73197634206448.34,
"time": 1705647868,
"mediantime": 1705645253,
"verificationprogress": 0.9999957009800249,
"initialblockdownload": false,
"chainwork": "0000000000000000000000000000000000000000662d4aa47d899245f32eee0c",
"size_on_disk": 615713257117,
"pruned": false,
"warnings": ""
}
"chain": "main",
"blocks": 826379,
"headers": 826379,
"bestblockhash": "000000000000000000012359df8ed548d973ef4c68a2283092385fff80791d44",
"difficulty": 73197634206448.34,
"time": 1705647868,
"mediantime": 1705645253,
"verificationprogress": 0.9999957009800249,
"initialblockdownload": false,
"chainwork": "0000000000000000000000000000000000000000662d4aa47d899245f32eee0c",
"size_on_disk": 615713257117,
"pruned": false,
"warnings": ""
}
when I started the node again, it couldn't connect to the peers anymore.
Judging by your screenshot, the wallet is "Up to date.", which means it's connected. Click Window > Peers to confirm it's connected.Maybe you're just not used to seeing the real interface without IBD
You can create a wallet now. 
...
Just curious, don't you have control over when and why your device goes off, for a shutdown? I strongly advise to shutdown Bitcoin Core always gracefully as you don't want to risk that your chainstate and blocks data may get corrupted which could happen to my knowledge.
It doesn't mean you'd need to re-download the blockchain, but cleaning up such a corruption takes extra steps that you can easily avoid.
If your computer is unstable, fix the causes of instability first. Unreliable power is best mitigated with a laptop which can overcome wall power issues with his built-in battery.
Unfortunately I can’t send the log of my node for today because my pc went off just before I could paste it on here, but my progress was at 65% which is about 9% increase from my last update. By tomorrow I will continue to post with the log. So,
DAY 10
65% downloaded
DAY 10
65% downloaded
Jump to: