Quick update on my bank situation. They booted me.
No real reason given. They demanded insight into my bitcoin transactions, I told them they get nothing bitcoin related, done.
This happened a mere few days before I'm going on a global tour, starting with asia, then eastern europe and finally south america. No big. I can buy plane tickets directly with btc, my only bills are my cellie which my family can handle from their accounts, there is the occasional btc atm around the world... it will be interesting to see how well it works to be bankless.
Presumably they will write you a cheque totalling your account balances so you can cash it when you get a new bank? Asking for future reference. For the moment I have simply moved my money to a family account. I don't intend to actually use that account for anything more than simply storing my money, but it is there as an extra emergency backup if needed. This is ideally a temporary measure. I have not looked for a new bank and do not intend to. Merited for cutting edge reporting. And, what if they go after your familly account because "it did receive the btc-tainted kroner, ha!" - how likely do you reckon such an event is? Hey speaking of, the entire west is heading towards communism.
In germany a baker was faced with a 25k euro fine for having KG instead of kg on the signs in his shop. We are already living under stalinist conditions.
I'd like to hear the facts from two sources. It's not the commies IMO. It's obsessive insistence with The Rulez and the stantarts that neet to be folloft. The Germans are chronically prone to it, as are some other people, each in their own way. There must be a way for a peep to carve himself some slack. I would start to look for any specific reference to minuscule g's in the letter of the law. As for the spirit, typography apart, it's probably meant to ban unconverted pounds or ounces. |
|
|
|
|
Hello Tera, how you doin'? You aren't forgotten here, see?
Nice to hear your contrarian voice again.
|
|
|
|
|
Bart with no debart
Sunday in the countryside
didn't post haiku
|
|
|
|
Good afternoon gentlemen!Observing sideways price action from my favourite place (fillipone - look, the correct WO sign).  Practice makes perfect! Practice is more effective with some backgrounds than with others. LFC's solid choice of backgrounds appears to ensure very effective learning. |
|
|
|
|
^^^
In the debug log, I only see blocks that "make sense": height 585264 onwards. No explicit mapping between block number and blk file, but I'd say these are the newest - blocks that never were on the backup server to begin with. They are, now.
|
|
|
|
|
Gashes or cleavage?
Unrelatedly staring
at a fissured wall
#haiku
|
|
|
|
Or maybe no one will EVER understand what the fuck bitcoin actually is. Right, like that's really a private key underneath that scratcher? Pretty fucking lazy scam if you ask me. I would trust such a card after 6 mere confirmations. Basically , it clears after one statistical hour, and it only does once. Good for people with some gentleman time on their hands. |
|
|
|
Observing @~10300 since what feels like years I start to feel like this:  Don't poke her FFS!!  |
|
|
|
From time to time I post comments here from a contact that has some very close ties with high ups in the CCP. For anyone who is interested, Here is something I read from him today. His comment is in response to a recent macrovoices interview regarding China, trade deal, etc. And an article speculating on Chinas purported lack of dollar reserves. Listening now and almost fell off my seat laughing at the whole " Trump and Xi kiss and make up to get a trade deal" talk. It is such a western view and coming from someone living in Hong Kong, it is puzzling how he can miss the background for the current niceties...
1. 70th anniversary on Oct 1 is key to Xi. But dropping existing tariffs and removing some key elements from the talks are also import to the Chinese position. Trump may cave, it is always possible, but Xi can't (not won't, can't). A Xi back down now will spell the end for the CCP and expose all the mishandling of issues in the economy and ag sector.
2. I have always said there will be some element of trade, and the timing for the 'trade" concessions by China is amusing because based on USDA data I saw, a large harvest is underway with out any markets to take a large percentage of the crop output. So, if true, China won't be paying nosebleed levels for ag goods because the US needs a market. On the pork side, pay attention to the US export data (10,000 ton pork exports to China last month) not the Trump tweets. Most of these exports are from Smithfields (Chinese owned) and in carcase form not processed which means it is actually costing jobs in the sector in the US. This is significant info IMHO. Hard facts and numbers do hit eventually. Tweet or print as much as you may. |
|
|
|
Truth is, OpSec and smartphone is something that doesn't normally go together. Unless you have one of the rare (non Android) Linux phones, installed and secured by yourself, instead of the usual android/ios...
The Android ecosystem is very vulnerable and exploits have been occurring nonstop. Its almost as dangerous as running Windows in a PC, thanks to its closed proprietary software ecosystem, and "shortcuts" taken in its OS design.
Would be interesting to see if Huawei's OS fares any better. At least they promised to provide the source code...
Huawei software is a joke. Horrible bloat without a use, and you can't delete any of it. This could appear to be unrelated, but it's a prime sign of sloppy thinking. Besides, they are not giving out bootloader unlock codes, because "the user experience could be worsened by customizations". Yes, that's their official response. So you're in their hands - no alternative option. I'll believe a software vendor cares about security when they slim the software down to reasonable sizes. Going full open source would be another green mark. |
|
|
|
The log doesn't mention any more indexing than I expected - that is, apparently only from the first "new block" onwards. I've filtered the content for relevance. 2019-09-11T08:59:44Z * Using 2.0 MiB for block index database
2019-09-11T08:59:44Z * Using 255.8 MiB for transaction index database
2019-09-11T08:59:44Z init message: Loading block index...
2019-09-11T08:59:44Z Opening LevelDB in /home/btc/.bitcoin/blocks/index
2019-09-11T08:59:44Z Using obfuscation key for /home/btc/.bitcoin/blocks/index: 0000000000000000
2019-09-11T09:01:45Z block index 121209ms
2019-09-11T09:01:45Z Opening LevelDB in /home/btc/.bitcoin/indexes/txindex
2019-09-11T09:01:46Z Using obfuscation key for /home/btc/.bitcoin/indexes/txindex: 0000000000000000
2019-09-11T09:01:46Z txindex thread start
2019-09-11T09:01:46Z txindex is enabled at height 585264
2019-09-11T09:01:46Z txindex thread exit
2019-09-11T09:11:52Z * Using 2.0 MiB for block index database
2019-09-11T09:11:52Z * Using 255.8 MiB for transaction index database
2019-09-11T09:11:52Z init message: Loading block index...
2019-09-11T09:11:52Z Opening LevelDB in /home/btc/.bitcoin/blocks/index
2019-09-11T09:11:52Z Using obfuscation key for /home/btc/.bitcoin/blocks/index: 0000000000000000
2019-09-11T09:12:07Z block index 15025ms
2019-09-11T09:12:07Z Opening LevelDB in /home/btc/.bitcoin/indexes/txindex
2019-09-11T09:12:08Z Using obfuscation key for /home/btc/.bitcoin/indexes/txindex: 0000000000000000
2019-09-11T09:12:08Z txindex thread start
2019-09-11T09:12:08Z Syncing txindex with block chain from height 585265
2019-09-11T09:13:21Z Syncing txindex with block chain from height 585266
2019-09-11T09:13:46Z txindex is enabled at height 585366
|
|
|
|
Good afternoon WO!
Observing @ $ 10,210
And I have 40 pages in the queue to look for.
May be I can take help from JSRAW 😉
Here you go bro 1. ................................. -snip-Great summary as usual! Merited. I have a suggestion. How about tagging your summaries with some unique identifier like #JSRAWdigest or something like that? It would make it a lot easier when catching up  |
|
|
|
Did you have to reindex after restoring the backup?
I think so, but I'm not sure. Any easy way to check after the fact? The bitcoind daemon has kept itself quite busy (20-25% CPU according to the top utility) as soon as I launched it. It seems a little too much for simple verification of the new blocks. |
|
|
|
|
This looks a bit different from the latest bart/debart. More like the previous ramps, which did raise the floor a bit. Go bitcoin, go.
|
|
|
|
$11000 in one hour  Just wait until they're done with the printing press... |
|
|
|
manually compare the hashes of the old and new files. sha256sum them for instance. the reason being that timestamp changes can also trigger rsync. from the man page: Rsync finds files that need to be transferred using a "quick check" algorithm (by default) that looks for files that have changed in size or in last-modified time.
if the hashes are the same then that means the file contents haven't changed and only the timestamp has been changed. then see if there's an rsync option that lets you ignore file timestamps and only compare file hashes. Good call, but... unfortunately the old files have all been replaced by the new backup, so I can't check again. However, I did check the timestamps before launching the backup (I knew the timestamp could trigger a "changed" state for rsync) and all the blk*.dat files had the same date on the backup server and on the bitcoin node. This is consistent with my intuitive hypothesis that after being downloaded/assembled, they are only read: probably never written to again. EDIT The rsync dry runs were 100% consistent with what happened in the real run and among themselves. File corruption is the only possible explanation for this behavior I can come up with. Possibly the corruption occured while copying back the backup to the target machine, which had a busy disk and a busy network connection from downloading/installing several software packages. However, I just made another daily backup (and several dry runs just to check), and only the expected files were transferred. If anyone has a better hypothesis than selective file corruption, I'd like to hear it. |
|
|
|
|
Come on don't be so hard on yourself man, you're a legendary poster at heart already.
|
|
|
|
Did the name of your hard drive change? Any difference between the old hard drive's directory path and the new hard drive's directory path will trigger a discrepancy between the files for backup purposes.
I don't think the name changed. It's linux. But even if it changed, why should this affect only part of the files? The backup didn't begin with blk0000.dat, and several files have been skipped - half, more or less. |
|
|
|
Thanks, LFC! I just posted my question in the subforum you suggested.
Yeah, you’ll get answers there, I’m sure of it. Those guys are really helpful. First was "our" fillippone ;-) Boblawblaw also runs a node, but he isn't posting that much recently. |
|
|
|
|
I'm still on 0.18.0 as I was before.
Besides, the format of raw blk*.dat files (basically, a copy of the blockchain) hasn't ever changed AFAIK.
|
|
|
|
|
Show Posts
