Thanks, LFC! I just posted my question in the subforum you suggested.
|
|
|
My bitcoin node runs on a linux box. I've been away a few weeks, and I kept it switched off. When I got back, I found the main drive had some problem, so I replaced it and reinstalled the system and some of the software, including bitcoind. So far so good. After this, I proceeded to restore the latest daily backup of the .bitcoin directory. I then left the node running to verify and sync. The surprise came when the catching up was done, and I launched the new daily backup. I use rsync, so only files that have actually changed do get transferred. Well, apparently about half of the blocks need uploading to backup, which was never the case during my previous daily backup routine. Why have older block files changed? I'm talking about blk0XXXX.dat files. The latest is blk01790.dat, so I expected the backup to begin well after blk01000.dat, but rsync's output begins like this: .bitcoin/blocks/blk00028.dat .bitcoin/blocks/blk00031.dat .bitcoin/blocks/blk00033.dat .bitcoin/blocks/blk00036.dat .bitcoin/blocks/blk00037.dat .bitcoin/blocks/blk00038.dat ... Why the change in all these old blocks?
|
|
|
I have a technical question about my bitcoin node for my fellow verifiers. My bitcoin node runs on a linux box. I kept it switched off while I was away. When I got back, I found the main drive had some problem, so I replaced it and reinstalled the system and some of the software, including bitcoind. So far so good. After this, I proceeded to restore the latest daily backup of the .bitcoin directory, which among other things contains the local copy of the blockchain. I then left the node running to verify and sync. The surprise came when the catching up was done, and I launched the new daily backup. I use rsync, so only files that have changed actually get transferred. Well, apparently about half of the blocks need uploading to backup, which was never the case during my previous daily backup routine. Why have older block files changed? I'm talking about blk0XXXX.dat files. The latest is blk01790.dat, so I expected the backup to begin well after blk01000.dat, but the current backup (still running) begins with .bitcoin/blocks/blk00028.dat .bitcoin/blocks/blk00031.dat .bitcoin/blocks/blk00033.dat .bitcoin/blocks/blk00036.dat .bitcoin/blocks/blk00037.dat .bitcoin/blocks/blk00038.dat What could have happened?
|
|
|
I prefer offtopic talking about precious metals or dirty fiat, but please, take the Bcash talk to another place.
I prefer rocket/train memes and cleavage Let's not forget about double bottoms - or single ones, actually.
|
|
|
Merit of the Beast. Now don't spoil this number by randomly awarding me dozens. Or do if you're really itching. I'm dry so you will be stuck at 666 for a while Pity. My advanced psychology trick didn't work... Related: A few days ago someone posted a link to a thread where members can upload screenshots of interesting merit/activity/etc figures. I haven't been able to find it by searching - either bitcointalk or google. The link was in this thread, of course. Can anyone help?
|
|
|
Merit of the Beast. Now don't spoil this number by randomly awarding me dozens. Or do if you're really itching.
|
|
|
I should have posted that tomorrow.
|
|
|
Good and simple read. Merit-worthy, but I'm dry. +1 WOsMerit (Sorry: valid in the WOT only, as per instructions from management.)
|
|
|
I am a BTC believer. I am a HODLer. Sometimes, however, the serpent of doubt slithers through my soul. This halving might be different from the others. What we know is that halvings are going to be more and more irrelevant as the supply decreases. What we don't know is the rate of increase of the irrelevance. In order to estimate possible halving effects, we can use a priori data and contingent data. A priori data: current level of supply. Contingent data: state of adoption, price, market sentiment, etc. Just for a rough estimate, assuming the price at the halving is in the same ballpark as today: Date | Reward (BTC) | Price (USD/BTC) | Reward (USD) | 2012.11.28 | 50BTC | 12.35 | 617.50 $ | 2016.07.09 | 25BTC | 650 | 16.250 k$ | 2020.05.XX | 12.5BTC | 10500 | 131.250 k$ |
I've been looking at this table and pondering for a while, but the serpent isn't dead, not yet at least. Any food for thought? I'm still staying strong anyway, we all know why. I am a BTC believer. I am a HODLer.
|
|
|
So we had our flash dumplet - nothing really worrying as it was, just one more dip to buy moar. There was strong resistance just below 10k, and getting back over that line was a matter of minutes. Some bought a little. My guess is no one panic sold - and certainly no WO peep.
TL;DR Yawn.
|
|
|
I think I bought something at the very (local) bottom. Got lucky with a stop. My suffering long position has increased, and its liquidation price got closer to 3k. I'm willing to risk moar and bring my liquidation price just under 5k, or even higher. But I'll have to wait until 15k before getting that bold.
|
|
|
Oh gawd, Roach. You are devolving into delirium. Devolving? Revolving.
|
|
|
Good day Bitcoinland Ten four four two U.S. bucks (Bitcoinaverage).
Still going sideways When will this crap ever end? Maybe November.
Buying those cheap coins Still plentiful time brothers Hurry though moon soon 5 7 5 I got it, right? Formally perfect debut deserving merit LFC scrapped it? +1 WOsMerit to LFC (if the #haiku was actually written by him, and this isn't a quoting mistake by ulrich_zh)
|
|
|
one point three percent every shitcoin bagholder is this alt season? Unknowingly, or...? Posted a visual #haiku! Goose with a surprise
|
|
|
Watching the corn grow In the field and on the chart it's #Haiku Sunday There. I obliged
|
|
|
Actually it's as Lauda says. The Segregated Witness thingy basically alters the transaction format so that certain (most) cryptographic proofs (the "witness") are not on the main blockchain (they're "segregated"). That's why space can be saved: segwit transactions can be stored more efficiently because some data can be discarded. This is why fees are significantly lower.
This is also incorrect. The signatures get stored in the chain as before, they just aren't counted towards the classic block size limit due to the segregation that you have mentioned. I stand corrected. Witness data can be removed from the Merkle tree, not from the chain.
|
|
|
another bcash idiot for my ignore list
saying that segwit is not bitcoin is the same like saying TCP is not IP. it's the same, but it's another layer. TCP can't exist without IP and segwit can't exist without bitcoin.
Saying that is actually wrong. You are mixing up SegWit and LN. LN is another layer. SegWit is part of Bitcoin. I'm not sure about this, maybe you are right. But LN is based on segwit and segwit has a second name, the consensus layer. Actually it's as Lauda says. The Segregated Witness thingy basically alters the transaction format so that certain (most) cryptographic proofs (the "witness") are not on the main blockchain (they're "segregated"). That's why space can be saved: segwit transactions can be stored more efficiently because some data can be discarded. As a result, the average transaction fee is significantly lower.
|
|
|
But do you bring h-jobs? Sorry, couldn't resistLol. NO But know this "A jerk in the hand is worth two in the bush." Well... now you just need a hat.... and then you be styling, dude.
I'll get one someday will all your help A little help from me because of the lulz.
|
|
|
Observing.....................to little, to low prices......
Cumming Bull Observing $10,313.90 Mooooo... That must be a cow who was born in the wrong body. She's needing a strap-on badly. Who knows why I have a hunch she'd like the attachment to be green. It's this modern gender thing, you know. See what happens, the world is rotting. In my day, good ol' times, blahblahblah.
|
|
|
|