BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

[Rob Andrews]

Oh this is mainnet not testnet sorry

Oh I see, OK we have a solid reason for this.  So in mainnet, tithe blocks are active til Christmas but in TestNet they are not.
Since the block the miner works on is n+1, if it will be an *upcoming* tithe block, the hash changes to be Higher, to allow the Diff to be Lower, so is normal for the blocks in Prod that will end in n+1 % 10 to be different, you can see if you increment the height up through n+9 no changes until you hit another tithe block.
Yeah, I confirm that hash is 011 in prod, and 2aaa for the tithe block .

So far, so good! I guess I can let you burn in for a while longer.


This is excellent, this will most likely fix the reason we went out of sync twice in testnet.

EDIT:  THANKS ALEX FOR YOUR PERSEVERANCE AND FINDING THIS FLAW!!!!!

[klondike]

ROB im enabled now .... i was think,that when i run watchman ... PRE_ENABLED will be immediately ENABLED: we have to wait few minutes

[togoshigekata]

Ok on Linux machine I just realized I never removed the banlist.dat file from the ~/.biblepaycore/testnet3 folder, woops,
I only had 2 connections before, now I have 12! Not sure how much this affected the retirement coin testing 

I assume in the future we will want banlist.dat file?
Is there a linux command to delete the contents inside the file?
I just used rm (remove) command, but I assume that means I cant ban anyone going forward now.

===

Rebuilding/Resyncing Chain:

GUI:  Tools >> Wallet Repair >> Rebuild index
Linux:  ./biblepayd -daemon -reindex

===

Windows GUI Wallet is now v1.0.5.9
Linux Wallet is now v1.0.6.1

[Rob Andrews]

Ok on Linux machine I just realized I never removed the banlist.dat file from the ~/.biblepaycore/testnet3 folder, woops,
I only had 2 connections before, now I have 12! Not sure how much this affected the retirement coin testing 

I assume in the future we will want banlist.dat file?
Is there a linux command to delete the contents inside the file?
I just used rm (remove) command, but I assume that means I cant ban anyone going forward now.

===

Rebuilding/Resyncing Chain:

GUI:  Tools >> Wallet Repair >> Rebuild index
Linux:  ./biblepayd -daemon -reindex

===

Windows GUI Wallet is now v1.0.5.9
Linux Wallet is now v1.0.6.1

Thanks, well that would have worked its way out after 24 hours as the max ban flag is one day, but yeah, I think Alexs discovery had a lot to do with our shrinking and decomposing network, with increasing banned nodes.

Since a few hours have passed I think the general consensus is that Alex hasnt found any new issues so I will probably ask you all to update to the latest version so we can do a pulse test of stability over the next 10 days.  Id like to see no banned nodes, no lost syncs, and a good masternode list.  But hold off for a couple hours as I am working on a feature we may be able to test together.

Regarding the retirement testing, I did find a bug in there, very minor, and its "technically" corrected in the last version but not tested.  Let me go ahead and test that first before we try more retirement tests.

The other thing is I am hoping to release e-commerce alpha soon.  Then we can test that also.

[Rob Andrews]

Just checked all my logs and Yup, no errors!

I've also successfully set up a masternode on testnet.

Best thing I heard all week!  Great!  Thanks for the help!

Yeah, Im testing the new version and compiling one for windows now, and Im going to send it out as a highly recommended (just short of mandatory upgrade) to Prod & Testnet in a few hours.

(Cant go with Mandatory as it may upset CCEX).

[Rob Andrews]

BiblePay - 1.0.6.1 Available
Mandatory Release for TestNet


- Fix checkblock(1) errors diagnosed with Alex that occasionally results in an invalid BibleHash
- Upgrade wallet graphics with new logo pack
- Show OpenSSL version in Tools | Info

www.biblepay.org | Downloads
https://github.com/biblepay/biblepay/

[Rob Andrews]

I guess we can try another retirement trade.  Togo?  If not, anyone else?

You must be on 1061 to test retirement trading.  Windows is out there also.

[Rob Andrews]

Hey Rob, I was looking through my logs and I'm seeing a new error now from time to time.

I was wondering if you had any idea where it could be coming from?

** TestBlockValidity FAILED - pindexNew->pprev != chainActive.Tip() (assert(pindexNew->pprev == chainActive.Tip())); **
2017-11-18 01:32:04 TestBlockValidity failed while creating new block
2017-11-18 01:32:04 BiblepayMiner -- Keypool ran out, please call keypoolrefill before restarting the mining thread

(my wallet has 40000 keys  pre-generated so it's def not running out of that)

That means the best block changed while you were generating a new block for mining.  The keypool error is misleading, should be taken out.

Please verify this only happens once every few hours then that will confirm it.

[Rob Andrews]

Yup it's only every few hours. Thanks!

Thanks for checking, yeah Ill fix that area, please follow up with me in a week and we can ensure its right (regarding the keypool test and message), I need to get past this hump with the ecommerce release and need to ask more people to help test these retirement accounts starting tomorrow.

[togoshigekata]

How can I help test these retirement accounts?

http://wiki.biblepay.org/Retirement_Accounts

exec retirementbalance
exec tradehistory
exec orderbook
exec listorders
exec order [  Buy/Sell/Cancel ]   Qty  Symbol [Price]

Im free to test too

[Rob Andrews]

http://wiki.biblepay.org/Retirement_Accounts

exec retirementbalance
exec tradehistory
exec orderbook
exec listorders
exec order [  Buy/Sell/Cancel ]   Qty  Symbol [Price]

Im free to test too

I just got back in and should be around for an hour or two.

Anyone up for a trade?

Dont forget, when you do the exec orderbook, you can widen your rpc display to see it better.

I just did: exec order sell 50000 rbbp .0293

If someone wants to add the opposing Buy order?

Please do an exec retirementbalance before trading so you can see the prior balance.

After 5 confirms on our trade, then you can do an exec tradehistory, and exec retirementbalance and reconcile them..

[Rob Andrews]

I added some sell orders a hour ago.

Yeah, I see one is like 660 MM BBP, I dont think we have enough to execute that one LOL.

[Rob Andrews]

Haha yeah I was just playing with it.

Ok, I did this buy:


exec order buy 1000 rbbp 345.1

Whose is that?
Btw you wont see the trade come back in the wallet for 5 confirms.

[Rob Andrews]

Ive had some very strange things happen to me while coding Biblepay- hundreds of 777s, too many to go into right now, but get this, my auto-generated BBP address on my test linux node starts with:
Yah Son Qxv 2L Jsus

So, yes, I know its not perfect, but its really wild that Yah is Yahweh (God the Father), Son, is Jesus, Qxv I have not determined (but I think it means To Be command to), 2L is 2Love, Jsus is Jesus.  Its really hard to believe, except the Qxv didnt work out quite too well unless someone has a clue what that could mean in there.  I didnt change the order either of the letters, these are verbatim - of course after the Jsus, its all just normal alphanumeric stuff.

[Rob Andrews]

That is mine. I also just bought the sell order you placed before

root@test-node-1:~# biblepay-cli exec order buy 50000 RBBP 0.0293
{
  "Command": "order",
  "Action": "BUY",
  "Symbol": "RBBP",
  "Qty": 50000,
  "Price": 0.0293,
  "Rec Address": "yNKoGx96D7kMDJ3SkkwyZwz4v3Gmqwg453",
  "Placing Order": "00000000000000000000000000000000e0e201d1d345628c3938949611c3ccbc"
}

Hmm, I see the 50,000 went through, but my retirement balance is only down by 7000, is yours up by 50000?

My 1465 payment went out to you I believe?