BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

Ok so my MN in prod has been on latest version for 12 hours. I just got a payment. But looks like blockchain is divided because I see payment on Togo's block explorer but not Alex's. Also block numbers are different. Anyway main point is that we seem to be confirming transactions. I now have stakebalance!

Code: [Select]

"Command": "stakebalance",
  "StakeBalance": 110000
In my config file I have

Code: [Select]

gen=1
genproclimit=1
polpercentage=50
so should be using over 50% of my 110k stake...

But!!!!

exec getboincinfo

Code: [Select]

  "8f273b30f8e0a298ed26e242762df701_RAC": 37944.24,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 100,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 25,
  "Total_RAC": 37944.24,

My UTXO is only 25. Should be 100, correct?

We are moving in the right direction!
By the way, the 33400 block number is the one on the old version? Then we are only hours away!

My block explorer was supposed to switch to the new version right before block 33400 as this is what I understood was the cut off before a fork. It seems the chain forked waaaay before that block hence why you see different things znffal.

I finally see my CPID after confirmations started working. However I want to separate the controller wallet for PoDC from the MN controller one, to another windows machine.

Can I run QT wallet on a new windows machine and re-associate to Rosetta, or do I have to "un-link" the current association first?
Thank you

My block explorer was supposed to switch to the new version right before block 33400 as this is what I understood was the cut off before a fork. It seems the chain forked waaaay before that block hence why you see different things znffal.

Yes for sure. Been a busy week!
Looks like your explorer is down?

So the botnet will be kicked due to mandatory at block 33400.
But 33400 on our chain or the bot chain?

Yes for sure. Been a busy week!
Looks like your explorer is down?

So the botnet will be kicked due to mandatory at block 33400.
But 33400 on our chain or the bot chain?

I would say that bot is already out of the "official" PoDC chain because we are getting our own confirmations (finally) and bot is 30 blocks ahead on its own chain. It can go on like that forever.

If bot tries to upgrade and hook to the "official" PoDC chain, he will mine by PoW until 33400 is reached (not likely as we are pretty close now).

I would say that bot is already out of the "official" PoDC chain because we are getting our own confirmations (finally) and bot is 30 blocks ahead on its own chain. It can go on like that forever.

If bot tries to upgrade and hook to the "official" PoDC chain, he will mine by PoW until 33400 is reached (not likely as we are pretty close now).

Oh cool. So it is unclear if Sanctuary rewards from the previous 8 hours from bot chain will persist, but rewards on new chain (in last few hours) should

Yes for sure. Been a busy week!
Looks like your explorer is down?

So the botnet will be kicked due to mandatory at block 33400.
But 33400 on our chain or the bot chain?

It depends what you call botnet as it seems there has been different uses for that word around here. With the standard and used definition of what a botnet is,  it's impossible to know if the miners of this/these botnet(s) were upgraded or not and are therefore on the new chain (or not). They will eventually end up upgrading anyway.

There should only have been 1 chain until block 33400. Then those who didn't upgrade would have continued mining with PoBH and those who upgraded would have gone on a new chain with PoDC.

From what I understood, the new protocol (PoDC) was supposed to kick off on block 33400 and hence should have been the splitting point between those who upgraded and those who didn't upgrade (there is no such thing as the botnet chain/non-botnet chain, etc).

That did not happen and instead there was a split between those who upgraded and those who didn't upgrade waaaaay before block 33400 for other reasons  (haven't looked at the exact block but it happened at least 5 hours ago).

The block explorer is offline right now while I put it back on the chain used by people on version 1010002.

Edit:

To reply to Mike even though I'm sure Rob might not agree with that as we seem to have different definition of what a botnet is.

I'm going off this definition when I am talking about botnet:

"Cybercriminals use special Trojan viruses to breach the security of several users’ computers, take control of each computer and organise all of the infected machines into a network of ‘bots’ that the criminal can remotely manage."

The botnet(s) can/will mine with PoBH if it still make sense (financially) or is still the most profitable for them. They can mine using the same software you use to mine MIP. That's why you can't stop it as you can't separate your computer for example, from a computer that has been taken control of illegitimately and is being used to mine BBP.

It depends what you call botnet as it seems there has been different uses for that word around here. With the standard and used definition of what a botnet is,  it's impossible to know if the miners of this/these botnet(s) were upgraded or not and are therefore on the new chain (or not). They will eventually end up upgrading anyway.

There should only have been 1 chain until block 33400. Then those who didn't upgrade would have continued mining with PoBH and those who upgraded would have gone on a new chain with PoDC.

From what I understood, the new protocol (PoDC) was supposed to kick off on block 33400 and hence should have been the splitting point between those who upgraded and those who didn't upgrade (there is no such thing as the botnet chain/non-botnet chain, etc).

That did not happen and instead there was a split between those who upgraded and those who didn't upgrade waaaaay before block 33400 for other reasons  (haven't looked at the exact block but it happened at least 5 hours ago).

The block explorer is offline right now while I put it back on the chain used by people on version 1010002.

Right, I was using the Botnet chain as meaning the "other/old" chain. But PoBH chain would have made more sense.
Ok then so the 33400 block target number should be on the new/PoDC chain

Right, I was using the Botnet chain as meaning the "other/old" chain. But PoBH chain would have made more sense.
Ok then so the 33400 block target number should be on the new/PoDC chain

33400 should be when the new protocol kicks off. But there is already been a fork between those who upgraded and those who didn't for other reasons. So if you upgraded, you are already on a new chain.

Edit:

Just to make to make it clear. It's not (or shouldn't be PoDC yet), it just forked for other reasons. Probably by forcing new clients to drop the connection from old clients. Both chains should still be exclusively PoBH right now.

33400 should be when the new protocol kicks off. But there is already been a fork between those who upgraded and those who didn't for other reasons. So if you upgraded, you are already on a new chain.

Edit:

Just to make to make it clear. It's not (or shouldn't be PoDC yet), it just forked for other reasons. Probably by forcing new clients to drop the connection from old clients. Both chains should still be exclusively PoBH right now.

Awesome, thanks. That's clear and makes sense.

Guys, I set my alarm to watch all the fireworks but unfortunately I have to take my son somewhere, so Ill join the party as soon as possible.

I see the non-PODC chain (the botnet is at block 33401 with a difficulty of 5000! a very high diff) and the PODC chain is still at 33376 with a 97 diff, and Im hoping that with the confirms and wild differences forming in the two chains, none of the "botnet" blocks will bleed back over to our podc chain, lets hope all these confirms stick.

Looks like somebody was "smart" and connected to an upgraded node from the "other chain". Since it's the same protocol but is/was/has the longest chain, the upgraded nodes now took all these blocks in or may be stuck I guess depending on your situation.

I was talking to canopus and he is stuck on the old chain with the latest daemon. Just be aware of that.

Update:
Just found out my sanctuary crashed an hour ago:

Code: [Select]

2018-03-07 13:00:03 DSEG -- Sent 168 Masternode invs to peer 6366
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:48 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:48 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:48 ERROR: AcceptBlockHeader: prev block not found
2018-03-07 13:00:48 Misbehaving: 109.230.40.66:58706 (23 -> 44)
2018-03-07 13:00:48 ERROR: invalid header received fc91647bc98f1427627243475c5b3cb8b17b72ed6ed1e6ad1635ec301877486d
2018-03-07 13:00:48 ERROR: AcceptBlockHeader: prev block not found
2018-03-07 13:00:48 Misbehaving: 109.230.40.66:58706 (44 -> 65)
2018-03-07 13:00:48 ERROR: invalid header received f301478b883c7bd4a4f486a53210f4816f38724c3bcfb0608bf8aa7f186df2a6
2018-03-07 13:00:48 ERROR: AcceptBlockHeader: prev block not found
2018-03-07 13:00:48 Misbehaving: 109.230.40.66:58706 (65 -> 86)
2018-03-07 13:00:48 ERROR: invalid header received 26b92a245a8d0897fd3595e6ac5308b020f3f0108d84fe9649cd0a57a26ddab8
2018-03-07 13:00:48 ERROR: AcceptBlockHeader: prev block not found
2018-03-07 13:00:48 Misbehaving: 109.230.40.66:58706 (86 -> 107) BAN THRESHOLD EXCEEDED
2018-03-07 13:00:48 ERROR: invalid header received 08dd452df7d78364f8778c302b6afc7b62cd5646560f39f63659a465a9f46567
2018-03-07 13:00:51 MASTERNODEPAYMENTSYNC -- Sent Masternode payment votes to peer 6316
2018-03-07 13:57:57


I've got three different wallets open, and all three seem to be on different chains:

33355:

Code: [Select]

15:08:26

getblockhash 33355


15:08:26

752a784656582f0123dc396e5afc0fc8f20d2cfd958675165138137fdeadaef1

33357:

Code: [Select]

15:05:39

getblockhash 33357


15:05:39

3a230e3e705441c8c02fa412191ff3aa11380205cb41cfe10e677f470fe558fd


33410:

Code: [Select]

15:07:05

getblockhash 33410


15:07:05

8de885ac26fed11683af444c59d1ed5f159a774a36088f473e7695df42abf76f


I've got three different wallets open, and all three are on different chains:

Did you check the block height for all 3?

I'm on height 33380.


09:11:43

getblockhash 33380


09:11:43

62e1c04282bb448cc3e51eab8e3a254e9b4ead3273878b1cb8c6d34cc4c921b8