Messages

121

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 02:00:42 PM »

Hey Mike, thanks for the quick response.

{
  "version": 1010003,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.0.3",
  "balance": 43.58675910,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33441,
  "timeoffset": 2,
  "connections": 8,
  "proxy": "",
  "difficulty": 1561.54112909823,
  "testnet": false,
  "keypoololdest": 1515744128,
  "keypoolsize": 1001,
  "unlocked_until": 0,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Wait 5 blocks, then close and restart your wallet. Run exec getboincinfo again and we'll go from there.

122

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 01:47:42 PM »

Hi guys

I'm trying to bring two machines on to the new PODC. Last night I tried the GUI to associate my Rosetta account with Biblepay. Waited and nothing showed up this morning. I ran it again earlier this morning and waited, still nothing. This is the current readout of getboincinfo from my debug. Am I right in understanding my CPID is NOT associated with my Biblepay wallet?

{
  "Command": "getboincinfo",
  "CPID": "",
  "Address": "",
  "CPIDS": "",
  "CPID-Age (hours)": 422347,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -2,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

I just ran a command line associate a few blocks ago, and then I ran it again and it says.

"Results": "A DCBTX was advertised less then 5 blocks ago. Please wait a full 5 blocks for your DCBTX to enter the chain."

I'm hoping this will work. But just wondering if anyone else had trouble with using the GUI to associate? Thanks.

If you ran it again within 5 blocks it will say that. Can you post your getinfo?

123

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 01:40:22 PM »

I'm doing that, because my CPID 1BBP transaction disappeared and I'm back without registration... let's hope it works this time

My sanctuary was on the lower height but then it jumped to an even lower one for some reason so I'm re-syncing that one for now.

Update:
Done, looks like it is also on the higher blockchain now.

124

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 01:33:31 PM »

Yes, this is one other great issue, the payment drops to 600 after the cutover block, so that also should break the botnet! 
So lets see if diff drops like this after 33440:

1500, 1500, 750,750,750, 325,325,325,325, 170,170,80,80,40,40 - by then I think we can take over with CPIDs.

Well, do you suggest I delete the chains and resync? I'm pretty sure I'll be on your chain then.

125

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 01:03:09 PM »

I made a mistake on the block number - its 33440 actually , sorry .  Thats 1 block from now.

Btw, the latest version that I checked in , 1103 - shows the CPID who solved the block after block 33440.  We will need this info to analyze blocks 33440+ to ensure the subsidy < 600 for the heat side, and that a cpid is solving it etc.

I think most of us trying to get on PODC is on the lower height chain. The higher chain is the old one correct? It looks like that chain will win at the moment. I made a new wallet and it's also syncing to the higher chain.

126

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 12:57:23 PM »

Is there a way to view all the forked blockchains?
I tried running getchaintips command but it crashes my wallet LOL

Main Explorer is on 33438 (so is a wallet that I reindexed)
https://biblepay-explorer.org/

Backup Explorer is on 33407
http://explorer.biblepay.org:3001/

Which chain are we waiting to reach 33440?

I think we are waiting to see which one wins. The block has already passed, it was 33400.

127

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 11:59:05 AM »

Yeah, were on a different chain, Im going to rebuild that particular sanc now.

Probably unfruitful to look at the blockhash right now, lets check them after 33440, and see if we can match up then.

Sanc:
getblockhash 33401
a5fc139e2881da15080abe85e2caf500abf02ae145f1a257755bbd5613b5384f

Wallet:
getblockhash 33401
a5fc139e2881da15080abe85e2caf500abf02ae145f1a257755bbd5613b5384f

128

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 11:05:25 AM »

So things look semi-OK, I guess on a scale from 1-10, maybe a 5 for this go live.  Primarily low because none of our transactions are confirming.
So here is the first rock in the rocky start:
The exec testvote, this is used to "prime" our sancs for the first contract (no need to ever do this later once we are rolling), gave me an error- I cant paste it : Something to the effect of Unable to calculate magnitudes, project RAC below minimum.

Looking at this in detail, it appears this is because no one on the network really has any UTXO weight that is confirmed. 

So if you type exec datalist utxoweight, from a sanc (not from the machine that sent the UTXO), my Sancs list is empty.  The reason you see utxo weight locally, is because that orphaned tx, the one with the "?" around it - it is alive in your local wallet but not in the sanc (as it was not confirmed by the network).  So we will need to -zapwallettxes once we get past this mandatory cutover block, restart the clients, and do the 'exec podcupdate' again, to ensure we all have utxo weight.

Once that happens I believe then we can try the exec testvote from the sanc, and hopefully generate contract #1 in prod.

Rob, I think we are on a different chain:

Code: [Select]

{
  "DataList": "UTXOWEIGHT",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-07-2018 14:44:31)": "100",
  "4004B7FEC94751F61FE9135977BAC553 (03-07-2018 13:38:25)": "100",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-07-2018 15:01:37)": "50",
  "6BCD1F25DC07679DB5AD812A012DF1A4 (03-07-2018 14:21:22)": "0",
  "84D803E4D82D3BDCDF8E2AB601E93E20 (03-07-2018 15:53:17)": "100",
  "8735CFE64D964416DBA6015EB414CF7E (03-07-2018 12:17:54)": "60",
  "8F273B30F8E0A298ED26E242762DF701 (03-07-2018 09:56:52)": "25",
  "940552F602F67A3CF57A452438F36EE9 (03-07-2018 05:44:28)": "25",
  "96892EC0FC8A2710FA84F26C9C84CD3E (03-07-2018 12:03:32)": "60",
  "968D0A04AA31FA9BBBFF2EB6A87B02F2 (03-07-2018 09:56:52)": "25",
  "A9420A038E44750C69CA4497FE08C2A9 (03-07-2018 15:01:37)": "60",
  "CA895B47AACFFBDBF906201821AF2F9F (03-07-2018 14:21:22)": "50",
  "D4E56169934BF307F145C75BCB2896A2 (03-07-2018 15:14:26)": "25",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-07-2018 08:33:51)": "100",
  "E6CE50042187D4B285568D86EF458F32 (03-07-2018 15:14:26)": "75",
  "E7AE6ABD6284B05F3FD5F7C780E60BC7 (03-07-2018 16:26:29)": "100",
  "E94C1704C75F731F8BFDE303F08408EE (03-07-2018 13:01:08)": "75"
}


129

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 10:24:21 AM »

Is everyone's magnitude at zero or is it just me? (Been at zero for 12 hours or so.)

130

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 09:28:27 AM »

I'm going to sleep and wish everyone the best while you all figure out that situation.

Should keep me awake throughout the day.

131

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 09:11:46 AM »

canopus - Today at 10:07 AM
HEALTH NODES
addnode "54.37.156.244" "add"
addnode "139.99.101.222" "add"
addnode "47.93.223.203" "add"
addnode "45.32.7.66" "add"
addnode "80.211.203.45" "add"
addnode "45.76.56.211" "add"
can you post it in testnetforum....for add

These nodes are on 33384 I believe, I didn't check them. Just reposting.

Question: If another chain wins, how do I switch over. How do I check which chain is winning?

132

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 08:41:10 AM »

You can also just go to dos prompt and type:

cd c:\program files\biblepaycore
biblepay-qt -zapwallettxes=1

Etc.

Thank, yup that's what I did.

133

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 08:24:32 AM »

Or more like "stupid", as anyone who created a fraudulent client to "help" the botnet in my opinion is a traitor, and practices dissent.

So should I be banning peers with height greater then 33400 or should i just let it play out? But it's crashing my masternode.

134

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 08:10:05 AM »

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

135

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 07:55:31 AM »

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