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

[Rob Andrews]

Robert,nice synced: but can i mining on testnet? cos doesnt working
i set in my config this:

testnet=1
genproclimit=24
gen=1

thanks for help

Something does appear to be hanging - but I dont see a problem with the code.  It could be the remaining nodes who havent upgraded yet.  I see that you and I are the only ones that upgraded (I have 3 nodes).

Anyway, I would recommend starting at threadlimit 3 with the new algorithm.  I can mine on 2 of my boxes.  Try 'setgenerate true 3' to see if you get any hashps in getmininginfo.

[klondike]

no result with mining:
may be this help you where is bug

[Rob Andrews]

no result with mining:
may be this help you where is bug

Yes, that helps.  I think the code is OK though.  I see a few guys just upgraded.  Let me see if I can start a hot sanctuary.

Im hoping we can all get synced and rebootstrapped today, and hopefully we dont need any code changes.

Let me do some testing.

[klondike]

im again stuck with sync 

[Rob Andrews]

im again stuck with sync 

Ive got a few pieces of info now.

Overall things are looking a little better, as I think about 80% have synced to the right block but we seem to have fractured the masternode network and that part of it will need tackled next, but first we need to get over one more hump.

The miner will not run unless the miner thinks the blockchain is synced.
We are having an issue where the wallet thinks its not synced.  If you type mnsync status, see the row that says IsBlockChainSynced?  That prevents the miner from running.
The reason I can mine on a couple nodes, is because those are not masternodes, and the connected peers are synced.

The other problem we are having is you can not broadcast a masternode to be started unless its mnsync status reaches 999.  It cant reach 999 unless its chain is synced.  Its chain cant sync in the current environment. 

You can set masternode=0 if you want, and go down a level and try to get your chain synced first.  (Synced not only to the tip but synced with mnsync status 999).

Im working on that next on my end; Im taking the nodes that arents synced and rebuilding the chain from 0.

[Rob Andrews]

I was able to get further on one linux node even though this did not work this morning the environment has changed:

stop the node
cd testnet3
rm blocks -R
rm chainstate -R
rm *.dat (except wallet.dat)
restart

Then after the next block came in After resyncing, mnsync status went to 999, and I was able to finally start one hot masternode.

Now I am able to mine on the hot masternode in linux.

[Rob Andrews]

Looks like our masternodes are coming back online now; the list is re-filling.  Things looking a lot better.  Ill wait for your opinions.

[jaapgvk]

I was away for a few days, but I'm back and compiling as we speak

EDIT: my masternode shows 'PRE-ENABLED', so I guess I'll be back online soon

[klondike]

all working now correct and stable+ mining working now well too

o/

good job Rob

[Rob Andrews]

Thanks guys, well we seem to be relatively stable now in testnet.

We really need to test this stuff thoroughly - as the last thing we need is go live at Christmas and find something didnt work as intended.

Has anyone decided to test blockchain news?

As far as f8000 goes, lets share some info on it.  Can we please test to see if the HPS in the miner is now more consistent across OS flavors and bitness, and prevents multiple copies from exploiting any increase? 

Here is my hashps using f8000:
Windows 64 bit - 6 core desktop : 4000 hps
Debian 64 bit - 1 core $10 per month vultr vm: 1000 hps

We should also circle back around, and have someone create a real budget item (please create one below 30000 bbp since superblocks in testnet are only 74000 bbp).  Create a thread for it also please.   Lets make one that we all will vote yes on?  I just want to see if this works for someone other than me.

[Rob Andrews]

 
So I did a test where my controller win wallet is receiving the subsidy for cold sanctuary #1.  I took the windows wallet offline for 30 hours to see if my sanctuary payments were sent by other nodes, and when I came back online sure enough the payments are coming in.  So that tells me we are 98% finished with the actual sanctuary mechanism.

I just created Oct recurring orphan expenses proposal - please vote on it after about an hour it should be available for voting (it has to send itself into the network, and that requires that it sends collateral, then waits 6 blocks, then creates the proposal object, then sends it, etc- the pool does all this for you right now).

Btw, the way I was thinking that pay to preach might work is (that is if P2P is approved in the budget), we create a pool receiving address for P2P, we add a proposal for P2P for say 1Q 2018, when approved, the payment is sent to the pool P2P key.  Then we give the pool the ability to reward "priests" who are on the schedule with subsidies after a successful sermon.  So basically, Priests register on the pool, we set up a biweekly sermon in a chatroom, participants come in, the priest preaches to the biblepay group, then the pool releases the payment after the sermon is over.  We keep doing that until the funds are exhausted, and do not vote on a new P2P campaign until exhausted.  We can add "Priests" and "Sermons" objects to the pool so we can see, and we can add a metric for the P2P balance.

[tiras]

Hi guys

I'm trying to set up a test sanctuary .

Can you send me 500K tBBP please :

yd4AaGDNstGbqFPknhAz7uYKHxAPEyqQya

thanks

[jaapgvk]

Hi guys

I'm trying to set up a test sanctuary .

Can you send me 500K tBBP please :

yd4AaGDNstGbqFPknhAz7uYKHxAPEyqQya

thanks

Good to have another sanctuary tester on board. I have sent you some coins

[tiras]

Good to have another sanctuary tester on board. I have sent you some coins

thank you Jaapgvk.  500K received.   

[tiras]

finished configuring the test sanctuary .

now it shows in the "masternode list" output  as "PRE_ENABLED" .
Do I need to do anything else to finalize it ?


root@BUS7-14:~/biblepay/src# ./biblepay-cli masternode list
{
  "2b41b04ac488c033073562090aba186ccf57faf8ecae00dbc1f072a0ac9eebdf-1": "ENABLED",
  "82da38dd4db20bc6fa5fd30ebeda707d1edbce1b3890c386497db7f4abffe90c-1": "ENABLED",
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "NEW_START_REQUIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "EXPIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "PRE_ENABLED"