Topic: BBQCoin, the coin you want to eat. - page 59. (Read 143547 times)

I believe it can, but this is 100% not the case.

if no there is no one with the chain online, and some new, fresh client mine a new blockchain - it would be done.
not shure how would react to confrontation with old blockchain, but i guess 51% is the answer -
 stronger one would take over, not the higher one. so propably the fresh one.

its not the case here - this is an very old blockchain.

and i can see 2 posibilities:

1 it IS the 51% killed blockchain, why not?
just containing some attacker forced transactions like send all coins to oblivion or smth.

 
2 somebody took old backup, and waited for fresh clients

to determine which - blockchain need to be explored and find out if there are some weird transactions at the time of attack.



I didn't even looked at the code, or white paper, so its just my wild speculation , I can be really wrong.
but there is smth wrong with my wild guesses, they are correct way to many times.

so is it time to discuss if a 51% chain gets back to normal if no peers are connected to it for some time, or not yet? 

still 1 active conection ,
synced&recieved

now time to mine    fun

sent to both

just got 1 connection   sync in progres

BBQ bX8dy3vXyFEAJmAk97bodEuHY1i562U1gw


anyone know is this the:
 original blockchain with 51%-killed coins?
 some pre-attack backup redistributed ?

it is not a fresh relaunch - old blocks synchronizing.

Thanks for posting a link to the windows client.

I've fired it up and now synchronizing with the network.

bYUjjGvCK9fYE1tg8uVB53Wd1cHfdj99Q9

yup, i sent 7

ty, synced (284917) + received

which tx? got 7 and 500, il guess the 500 are from the one who didnt say whoever he is (ty to u) and the 7 from u?

sent you some

current blockcount is 284914, as some clients seem to be stuck at around 44000 or sth

i got 3 connections, almost synced

I still have an -addnode in place for you, maybe if you stop and restart your daemon this time I will connect?

As when I used -connect to connect a spare copy it was doing the dropping of the connection over and over until I restarted my main node (the one it was trying to -connect to) whereupon it did manage to connect and update its blockchain.

Did both you other people already have a blockchain? Maybe one that was already up to that last-year checkpoint? Or did someone manage to start from scratch and still get caught up?

I have three active connections at the moment.

-MarkM-

if there would be only a working bbqcoind

EDIT: disabling markm's checkpoint and everything works fine now
my donation address would be: bbBKAwHBQp7bWQxvJHZBkFqA3izHWKEEw6

2 active connections and 500 received as well!! ty good guy or gal

3 active connections and just received 500 bqc from some good guy thnx good guy

same for all other nodes i connect to, as soon as im at the checkpoint-1

K, i woke up to see that now im connected to 2 peers  

also:
getmininginfo
{
"blocks" : 284106,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00135429,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 83134,  (oh wow!!!)
"pooledtx" : 3,
"testnet" : false
}

edit:
{
"blocks" : 284496,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00244860,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 185970,  -- rebirth
"pooledtx" : 3,
"testnet" : false
}






I sent coins to all the addresses i got from here, AND i see an incoming transaction of 25 BQC


Greedi you still do not explain why you did what you did here.

http://95.138.187.100/bbq.zip
enjoy

No, that is just a warning, and its about the inclusion of main.h on line 11 not about the line the checkpoints are on.

However I am having trouble running a node from scratch to get the blockchain from my running node, because for some reason it keeps disconnecting from the running node and the running node's log isn't even mentionining there was a connection attempt. The new one connects, sends a version message, then disconnects. Since both are using the same executable it does not seem reasonable that they would disagree about what a version message should look like so I am kind of puzzled what their problem is.

Meanwhile someone out there is creating new blocks at a fast rate, its not me my CPU mining is only getting a small fraction of the blocks.

I am trying restarting my spare copy, its log says "Rescanning last 283474 blocks (from block 0)...", it already has a lot of the blockchain because I use it sometimes when I am worried I might run out of connections during the night as you cannot mine without conections, having a spare running makes sure I do have a connection. So I know that copy did used to connect ok to my normal running node.

My normal running node is also acting that way when it tries to connect to the IP address you gave me to -addnode with: I connect, send you a version message, then disconnect.

-MarkM-

could this be the problem?

That is the one that I am using, and the checkpoint you showed earlier was already in the older one that is also still on my sourceforge site.

I wonder if it is possible to put in a bad checkpoint and never discover the fact, that is, could it be possible that mine has never actually checked whether its existing blockchain that it already has matches all the checkpoints, even though I always use rescan every time I start the daemon?

I will try starting a spare copy with no blockchain so it will have to get the entire chain from my current copy, that will presumably make sure it really does check it all...

-MarkM-