Messages

3226

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

« on: March 05, 2018, 04:35:16 PM »

Me too  That was easier than expected, haha!

Were not out of the woods yet, because DGW can take up to 4 blocks to recalibrate the diff.  Looks like the next block is 2400~ diff.
It will probably take the full hour to solve it + 1 + 2 etc.  I see part of the problem:  This exec podcdifficulty command's scale is *10, so our diff is really 2400, not 24000.  Whew. Good to know.

Ill fix this, plus the crash when you do a diff+1, plus the getmininginfo diff should be visible, but these are all cosmetic things they can wait until windows 1101 is released (should be within an hour).  Ill release 1101 then we can start upgrading some prod nodes, and then add these 3 cosmetic changes in.

So, it might take us up to 3 more hours to solve blocks at a normal rate.

3227

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

« on: March 05, 2018, 04:20:31 PM »

What's going on, is it the end? 

No, but just in case this turns into a Prod drama, I wanted to thank everyone!

3228

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

« on: March 05, 2018, 04:16:42 PM »

restored wallet from backup, clean istall again and balance is back thanks God, because those are all of my BBP. I play all in

Good to hear!  Yes we should all keep an offsite backup of wallet.dat, just in case this happens.

Ive had many fried hard drives.

3229

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

« on: March 05, 2018, 04:13:16 PM »

Weve got a wild situation forming here, take a look at the legacy chain difficulty :
running this from the *new* wallet:

exec podcdifficulty 33120

Diff is about 24000....  So that explains why we are having issues solving block 33153.
So what happens is the block becomes 90% easier after 30 minutes - meaning that a 24000 diff is like a 2400 diff!  Thats crazy high for us little fish in this new pond.  We are going to have to recommend setgenerate 10 - we need to try to brute force 33153 together....

I just enabled 1 miner.

EDIT:  Yes Jaap just read your comment, exactly, but we have evaded this situation because of our late block rule above.  But whats strange is this 24000 diff is Way higher than normal!  We pissed someone off right before the fork started.

3230

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

« on: March 05, 2018, 04:03:23 PM »

So,
linux 1101, clean install, synced to block 33152 and my balance is still 0

You must have changed wallets? Can you go back to your original wallet?

3231

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

« on: March 05, 2018, 04:02:42 PM »

Oh, sorry  I just thought something went wrong because the networks split. I didn't know it was intentional.

Lol, no problem, no I didnt expect it actually, because we had some rogue actors over the years who shuttled blocks back and forth protocol versions in the past, eliminating the smaller chain.  This behavior is actually normal, the two shouldnt be communicating.  Lets see where this goes.

3232

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

« on: March 05, 2018, 03:43:45 PM »

THANK YOU ALL FOR TESTING PODC

WE ARE MAKING A DIFFERENCE IN THE WORLD, we are creating a Sanctuary Economy for the benefit of the Orphans!

3233

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

« on: March 05, 2018, 03:40:59 PM »

You can do a 'getblockhash 33152'

If you get this hash, you're in the same wrecked boat as us:
0b6062f664d324c169c77439b85bd0b1a20077f3f1739d9deaa9713eca72c7d1

You can find your ip if you google 'what's my ip' for instance But maybe it's not needed if you're on the same chain as us...

Why do you say wrecked?  The new chain is *the* chain - the 1089 chain is the one that is sinking with the titanic....

3234

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

« on: March 05, 2018, 03:39:44 PM »

so... i got synced to block 33152, but all my BBPs are gone.. my ballance is 0

Wait, Togo we are not hard forking yet due to the cutover rules - thats going in at block 33440, but I do believe our chains are forking due to network segmentation.
We have one chain (of the existing current prod users who didnt upgrade + the botnet) and then we have the new chain (us).

Orbis, you should not be losing BBP.  Did you get it back after you synced?  The only way to lose BBP is if you *mined* on a fork.  You should have the balance you had before the cutover.


Hey guys, I found a relatively minor bug in 1099, so I need to re-build windows with v 1101 (1100 is not possible, due to the zeroes) anyway, the bug only affects people with lots of sanctuary funds- it turns out, the PODC Update is "trying" to calculate its available amount using the unlocked calculation (I had fixed this in a prior version, but this morning when we moved to GetBalance due to the complaints - it reverted this.) So basically the workaround is if you are on 1099, you can set a low polpercentage, and the system will work temporarily, but tonight please focus on upgrading prod to 1101 when we all upgrade.

3235

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

« on: March 05, 2018, 02:43:55 PM »

I also have no connection in 1099 in prod.
No block source

Its most likely due to node.biblepay.org (the main seed node being on the old version).

Ill go ahead and upgrade it right now, now that windows is out.

3236

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

« on: March 05, 2018, 02:43:19 PM »

Windows 1.0.9.9 has been released, lets do some testing for a couple hours in prod also before I announce to the masses.

3237

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

« on: March 05, 2018, 02:32:14 PM »

for sure...
please give me newest block nr and blockhash
test and prod

Testnet:
getblockhash 16390

14:31:04

da5d2e13221e082e8946cb5efea75273f4cf76e0d9c671257bb6a5a4ed86b8a6

19~ connections.

Prod:  I havent attempted an upgrade yet

3238

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

« on: March 05, 2018, 02:00:54 PM »

Rob... nice... 1099 workings great...
podcupdate is now true in prod

Good to hear, all credit to Yeshua Hamashiach.

3239

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

« on: March 05, 2018, 01:59:47 PM »

Super minor: Something Ive noticed after stopping Biblepay on Ubuntu, I get message written to the command line like this: "written 0.000000  written 960.000000  written 0.000000", the longer its been running the longer the message, I can only backspace a little of it, I just have to click enter and then type my next command in, hasnt caused any issues

Upgrading both of my testnet sanctuaries to v1.0.9.9

Oh OK, thanks, yes that was the debug log from when we started testing SSL.  OK, I removed it for the next version, thanks.

3240

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

« on: March 05, 2018, 12:17:01 PM »

Biblepay 1.0.9.9
Mandatory Upgrade

- Use standard unlocked wallet balance for PODC UTXO stakes
- Require mandatory protocol upgrade for sanctuaries to 70717
- Added BBP address to exec getboincinfo for each CPID

* Windows is now building *


This new version breaks compatibility in test & prod.  Lets all upgrade to 1099 in test, ensure its functioning and then in the evening Ill start recommending we upgrade in prod to ensure things are propagating.