mod_cure 2017-01-12 07:46:06
ok
mod_cure 2017-01-12 07:48:22
arubi, wouldnt i rollback block 'a' block '6' then go from block '5' -> c ?
nigelfroggy 2017-01-12 07:52:43
I'm offering 0.04 to the first person to tell me the reference that Meryl Streep made in her golden globes speech to this website: http://45.56.114.102
nigelfroggy 2017-01-12 07:52:43
sorry to repeat, but I got disconnected, I'm offering 0.04 btc to the first person to tell me the reference that Meryl Streep made in her golden globes speech to this website: http://45.56.114.102
piqure 2017-01-12 07:52:44
^^^ WARNING: any URL may lead directly or indirectly to COIN-STEALING MALWARE! ^^^
piqure 2017-01-12 07:52:46
^^^ WARNING: any URL may lead directly or indirectly to COIN-STEALING MALWARE! ^^^
arubi 2017-01-12 07:55:39
mod_cure, right, 5->b>c
arubi 2017-01-12 07:57:44
you do have 5->a and 5->b, but 5->a is active (say that's what your node decided). now block c builds on top of b, and like you heard about b, you hear about c. roll back the changes that block a did to block 5, apply block b, then block c
BloodSkin 2017-01-12 08:00:39
wait
BloodSkin 2017-01-12 08:00:41
what
BloodSkin 2017-01-12 08:00:43
lol
BloodSkin 2017-01-12 08:00:50
oh
BloodSkin 2017-01-12 08:00:56
i thought gribble got banned rofl
BloodSkin 2017-01-12 08:01:00
didnt read that properly
xissburg 2017-01-12 08:01:59
!tlast
gribble 2017-01-12 08:02:00
806.97
mod_cure 2017-01-12 08:08:05
arubi, so my node currnetly has two branches.. the new main branch(block 5 -> b -->c) and inactive branch that contains block a ? the branch thing kinda throws me off but i understand everyhing you said so far
arubi 2017-01-12 08:09:07
the inactive branch becomes 5->a and that's it, since 5->b-> is all there is, and it's longer
arubi 2017-01-12 08:09:55
if next some miner 'd' starts mining on top of the 5->a chain, and they get 3 blocks in a row, that becomes, 5->a->d1->d2->d3
arubi 2017-01-12 08:10:26
which is longer than 5->b->c , even though it originally overtook 5->a
mod_cure 2017-01-12 08:10:48
arubi, inactive branch only contains block 5 and block 'a'... and my main branch contains block 1,2,3,4,5,b,c ?
arubi 2017-01-12 08:11:04
no, the word branch is important here
arubi 2017-01-12 08:11:17
the branch begins at 5, and continues either to a or b
arubi 2017-01-12 08:15:01
mod_cure, the chain has tips, and sometimes tips can diverge. it's possible to track more than one divergence at a time. the question is what happens when you just started your node from scratch, and half the nodes say a#455000, and the other half says b#4555000
arubi 2017-01-12 08:15:02
er, b#455000.
mod_cure 2017-01-12 08:16:17
arubi, i see what you mean by branches now.. thats what I was so confussed about... one thing though.... why would miner 'd' start mining on top of 5->a chain since d1 wouldnt reference block 'a' as its parent ?
arubi 2017-01-12 08:17:52
whatever reason, I gave it as an example to how a branch can be active, then inactive, then active again
mod_cure 2017-01-12 08:17:59
arubi, oic sir
mod_cure 2017-01-12 08:18:54
arubi, thank you
arubi 2017-01-12 08:19:00
cheers mod_cure
Sterl 2017-01-12 08:25:07
hey fellow bitcoiners. Im struggling with a bit of a litecoin problem and ive already asked in the litecoin channel for help to no avail. basically i just compiled the new litecoin version statically. moved the binaries onto a brand new fedora server, moved my wallet.dat from the old server to the new one, ran litecoind, blocks syncing just fine in debug.log, but when i run ./litecoin-cli getinfo, i get ./litecoin-cli getinfo
Sterl 2017-01-12 08:25:08
error code: -1
Sterl 2017-01-12 08:25:08
error message:
Sterl 2017-01-12 08:25:08
GetOldestKeyPoolTime: read oldest key in keypool failed
Sterl 2017-01-12 08:26:21
Has any one else ever come across this problem?
Sterl 2017-01-12 08:27:08
i thought it may have something to do with permissions on my wallet.dat because i had to chown and chown again to move the file from server to server.
Sterl 2017-01-12 08:30:05
and then after a while of syncing, my terminal eventually reads: Error: Error: A fatal internal error occurred, see debug.log for details
Sterl 2017-01-12 08:30:05
Error: Error: A fatal internal error occurred, see debug.log for details
Sterl 2017-01-12 08:30:59
in debug.log: *** System error while flushing: CDB: Error -30974, can't open database wallet.dat
Sterl 2017-01-12 08:30:59
2017-01-12 19:28:15 Error: Error: A fatal internal error occurred, see debug.log for details
Sterl 2017-01-12 08:30:59
2017-01-12 19:28:15 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
Sterl 2017-01-12 08:30:59
2017-01-12 19:28:15 Shutdown: done
wumpus 2017-01-12 08:31:57
have you tried running database recovery?
Sterl 2017-01-12 08:33:26
wumpus, i have not. how would i go about doing that?
Sterl 2017-01-12 08:34:38
I've already tried deleting all my .litecoin files except wallet.dat and litecoin.conf
Sterl 2017-01-12 08:34:55
i suppose i can try again.
luke-jr 2017-01-12 08:35:58
Sterl: this is #bitcoin, not #litecoin
s17 2017-01-12 08:35:59
rename it to bitcoin and see if that helps
Sterl 2017-01-12 08:36:56
thank you luke-jr i realize that :) just trying to get some help since there is a larger bitcoin community
s17 2017-01-12 08:37:15
true!=false
luke-jr 2017-01-12 08:37:29
if we wanted to help with litecoin issues, presumably we'd be in #litecoin ;)
Sterl 2017-01-12 08:44:55
*Ahem* Im struggling with a bit of a bitcoin problem. basically i just compiled the new bitcoin version statically. moved the binaries onto a brand new fedora server, moved my wallet.dat from the old server to the new one, ran bitcoind, blocks syncing just fine in debug.log, but when i run ./bitcoin-cli getinfo, i get ./bitcoin-cli getinfo error code: -1 error message:
Sterl 2017-01-12 08:44:55
GetOldestKeyPoolTime: read oldest key in keypool failed
Sterl 2017-01-12 08:44:59
;)
