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

[klondike]

thanks for your time Rob ...

is any solution why masternode crashed to NEW START REQUIRED? im wrote more topics about it on DASH and ppl got still this problems,every day checking their masternodes....it can be nervous still checking if something is running ....
1MN working stable 4+days and 1 go to that start req: so i start MN from controller and run watchman ...


andy idea? thanks

[Rob Andrews]

Hi Alex,
Not sure if you saw this post from Slovakia on the main thread, something to the extent of he believes the pool is stealing peoples blocks by hiding the blocks found, but it made me think of a potential enhancement to your BX.

If you label the MinersOfMen address and the Pool with pool.biblepay.org, then could you potentially make a "Coins Mined in Last 24 hours" metric and put it somewhere? Somewhere that is not hit every time, or, maybe you could cache it and put it right under the address in the richlist?  Another words whatever is convenient for you. (You can do exec getsubsidy height for nTip to nTip-202 when you call it then sum it and cache it for an hour).

Then we could have whoever reads it compare it to pool.biblepay.org coins mined on about page, and know they agree.

Then after that, all we have to worry about is why do we have 65% of the blocks solo mined?  Thats another important project.  Is there any way to see if the non pool blocks are going to random addresses? 

I have an idea that could thwart a botnet, but it needs to be tested in testnet.  I was thinking, if we took an element of proof-of-stake, Spending money to stake, and added it into POW, and required each miner to stake 1BBP while mining, it would make it almost impossible to not CPU mine (as the 1 bbp at stake would need to be added to the block).  Then we would need to require the 1BBP tx to never be older than say 60 seconds, so as to thwart any GPU or asic.  The problem is getadjustedtime() can be skewed up to 15 mins.  This is still a tough issue to solve.

 

[Rob Andrews]

thanks for your time Rob ...

is any solution why masternode crashed to NEW START REQUIRED? im wrote more topics about it on DASH and ppl got still this problems,every day checking their masternodes....it can be nervous still checking if something is running ....
1MN working stable 4+days and 1 go to that start req: so i start MN from controller and run watchman ...
andy idea? thanks

It looks like NEW_START_REQUIRED is triggered if your node fails the POSE test.  That means it either fails to vote within 24 hours for itself, gets ddossed, loses its static IP or crashes.  Then the other nodes vote to boot your node from the team and requires a restart by the owner of the sanctuary to get back "in" the payment queue.  You lose payments until you restart the node - from the controller - not from the node.

[klondike]

hm----- im using weak VPS for testing,may be because of ... on VULTR will be stable i hope
explorer changed GH to MH?
hm..... so its HPS2 or HPS1?

now is 72 000 000 HPS2? 1core gives .ca 5000 hps2= 72M/5khs=14400 1cores is 100% of site? or

and im talked with Slovakia and he got true....now is network all day around 72MH/s  Diff=10 000  and rewards is very bad..... we had double rewards on this Diff .. what is bad?

if will be exists botnet on solo mining, all is gone,nobody after new year will be mining bbp=not rentabile, pool died with this botnet=china guys
main idea for all is SUPPORT CHILDREN it will be sad if miners leave and botnet/china will be flourish to the detriment BIBLEPOOL


amen

[Rob Andrews]

I will add something like that to my list.

I think the block solo mined are probably mined by big miners that:
1) create an account and configure all their miners to point to the pool
2) maybe have a loss of hash power because of the connection between the pool and their miners (I'm guessing it could make a difference at large scale)
3) pay the pool fees
4) have a botnet and don't want to mine on the pool for the reasons above!

I also updated the testing BX with a "preview" of what I'm doing. It's all still very early.

Edit: Reimage is taking longer than expected but should be available soon.

Right, Im with you, I can imagine someone who has 50 servers, who pointed to the pool and then dont maintain those boxes and they all keep solo mining.

Note : I do want to say, the pool scans back 11 blocks after every block just to make sure someone didnt solve a back block.  So the pool goes back and backpays for every block paid to it.

If you have a botnet, and you fall out of the pool those actually start getting signed by You.  So pool never keeps a block not its own.

[Rob Andrews]

hm----- im using weak VPS for testing,may be because of ... on VULTR will be stable i hope
explorer changed GH to MH?
hm..... so its HPS2 or HPS1?

now is 72 000 000 HPS2? 1core gives .ca 5000 hps2= 72M/5khs=14400 1cores is 100% of site? or

and im talked with Slovakia and he got true....now is network all day around 72MH/s  Diff=10 000  and rewards is very bad..... we had double rewards on this Diff .. what is bad?

if will be exists botnet on solo mining, all is gone,nobody after new year will be mining bbp=not rentabile, pool died with this botnet=china guys

Dont refer to the total HPS in testnet, its just a sum of how much Chain Diff went into the last 100 blocks.
Pay more attention to the comparable getmininginfo HPS achieved by each processor on testnet.
This f8000 algo is slower and harder to solve than f7000, but not subject to the node mutex.

If you guys like the HPS per processor and OS flavor in testnet, it will succeed very strongly in Prod.

[Rob Andrews]

I guess better late than never. The "preview" is now live on https://testnet.biblepay-explorer.org

Wow man, I love the idea of linking new proposals in there.  That will be awesome for sanctuaries!  Between the pool and BX, we almost have what Dash Central has.  I guess if we force new proposals into a certain thread, you can always pick them up.

I noticed the popup reftagger no longer works, did u remove that?

Its nice.  I think 1 px font size increase might be nice for the main page.  Any chance of our new logo going in?

[klondike]

Alex your testnet is on bad chain 

and when i click on my 2 MN wallets i see error

yW3UTp2qhNLoHJfnTP57jkgJ7RHzQYtBTH
yfyTLmXcnn1hXvWBGbKCz4QkRobJiUDeAt

[Rob Andrews]

Yup I removed it for now. I will just directly provide a link to the scripture if you click on a verse.

The css is def temporary and unfinished. I just needed something to test things. I increased the font size of the verses on the main page though! (prob need to clear your cache to see the difference)

As long as it has an API to let me grab the proposals I'm fine with anything (this forum or another website)

I was actually on my way to maybe totally rewrite it using socket.io but I guess ajax is good enough for now!

I still have a few more functions to add before eventually focusing on the appearance on the website.

Edit: Oh for what it's worth, I also added some cool api calls such as:
https://testnet.biblepay-explorer.org/ext/getverses/54798c78811d466a6dd29144f6bc82838068049fcf4680e05e06709287f1649e

Edit2: reindexing the db so the link above may not work until the block is back in the db.

The one in prod is really clean looking though (sorry for constructive criticism) I know you have been pouring time into this:

https://biblepay-explorer.org/block/6fcaabd2b7df5c5e530e32e02ce3ddea56944fbbaf804b0af73dd4f4e6dc544d
and the reftagger popups are cool...

So, couldnt you add your two new widget sections (proposals and threads) to the existing style one in prod?
Or are you recreating an entirely new BX so its going to be the "Alex" branch?

[tiras]

Hi Admin , 

what will be the procedure of promoting masternodes after or on Christmas ?

Will it be enough to start  a sanctuary and masternode on the main network as we did for testing  or there is anything else involved ?

thanks

[Rob Andrews]

Hi Admin , 

what will be the procedure of promoting masternodes after or on Christmas ?

Will it be enough to start  a sanctuary and masternode on the main network as we did for testing  or there is anything else involved ?

thanks

Hi Tiras,

It should be very similar to testnet.  Once the mandatory is released we will have a certain block number announced where the Sanctuaries actually enable themselves.  You can still send the escrow to the address early, and get the VM ready.  But the masternodelist wont populate until after that block number kicks over.

Once that kicks over, the sanctuaries should start talking to each other and voting to pay each other.  We will also have a separate block number for the first superblock.  I think we will need to space that out to give time for the new nodes to acclimate themselves (maybe 15-25 days later).

We also need to remember to send instructions for people to switch their watchman-on-the-wall configs over to Prod.

Rob

[tiras]

Hi Tiras,

It should be very similar to testnet.  Once the mandatory is released we will have a certain block number announced where the Sanctuaries actually enable themselves.  You can still send the escrow to the address early, and get the VM ready.  But the masternodelist wont populate until after that block number kicks over.

Once that kicks over, the sanctuaries should start talking to each other and voting to pay each other.  We will also have a separate block number for the first superblock.  I think we will need to space that out to give time for the new nodes to acclimate themselves (maybe 15-25 days later).

We also need to remember to send instructions for people to switch their watchman-on-the-wall configs over to Prod.

Rob

thanks Rob.

sounds good.  we can set it up before the holidays.

>>We also need to remember to send instructions for people to switch their watchman-on-the-wall configs over to Prod.

Can a test sanctuary be just reconfigured  to run on the main network then ?

[togoshigekata]

Ok, so Im stepping through sanctuary (masternode) creation process, this time with Vultr as host
(I was originally using AWS, but the Vultr pricing is a bit cheaper $5/mo vs $8.30/mo for 1CPU 1GB RAM)
[This is also my first time testing the swap file solution to extend the 1GB RAM]

===

Reference: http://wiki.biblepay.org/Create_Sanctuary
Note: 1,500,001 needs to be updated to 1,550,001

===

1. Create Account
https://www.vultr.com/register/

2. Add Payment Information

3. Download & Install PuTTY (SSH Client):
http://www.putty.org/

4. OPTIONAL: Generate SSH Public/Private Keys
https://www.vultr.com/docs/how-do-i-generate-ssh-keys/

5. Deploy Instance
https://my.vultr.com/deploy/

Instance Type:  VC2
  1. Server Location: Random
  2. Server Type: Ubuntu 16.04 x64
  3. Server Size: 1 CPU, 1024MB RAM, $5/mo (*Assuming using SWAP file later for more RAM)
  6. SSH Key: Add and Select Public Key you added in Step #4
  7. Serverhostname: Add unique name

6. Use Putty to Connect to Vultr Server
Enter IP Address, Port 22, Connection type SSH
You can add your private key file: Connection >> SSH >> Auth >> Browse
You can name and save your connection info:
Session >> Saved Sessions >> Enter a Unique Name >> Save

7. Install BiblePay
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

7a. Swap File
Before running last command "sudo make", set up the swap file:
https://digitizor.com/create-swap-file-ubuntu-linux/
http://forum.biblepay.org/index.php?topic=16.msg151#msg151

Code Select Expand

free #check if swap is 0
dd if=/dev/zero of=/var/swap.img bs=1024k count=1000
mkswap /var/swap.img
swapon /var/swap.img
free #check if swap is 1024

===

Comments:
- I failed to do the public/private key correctly I'm not sure what I did wrong, weird
- the swap file thing is interesting I've never done that before

===

8. Continue on with Create Sanctuary Wiki: http://wiki.biblepay.org/Create_Sanctuary
My previous masternode notes: http://forum.biblepay.org/index.php?topic=16.msg151#msg151
(waiting for BiblePay to compile so will continue tomorrow and report back any issues I run into)

[Rob Andrews]

thanks Rob.

sounds good.  we can set it up before the holidays.

>>We also need to remember to send instructions for people to switch their watchman-on-the-wall configs over to Prod.

Can a test sanctuary be just reconfigured  to run on the main network then ?

Yes - the testnet sanctuary can be switched to prod mode, but requires a few adjustments. 

The watchman config should be OK after just changing to point to prod (by uncommenting and recommenting the two lines in the watchman.conf file).    (IE its database should adjust to prod without a problem).

The masternode keypair however Is different in prod than testnet.  So I recommend commenting out the masternodeprivkey in the config file, and then you will need to generate a new keypair and of course send escrow to the correct address and that will yield a new vout txid string.

Once these things are set, booting into prod mode should work.  We should be able to test this tomorrow as soon as c-cex puts us in maintenance.

The mandatory upgrade is almost ready, so, if all goes well I will release it tonight and we can do our "prod" testing with the new version.



Togo, thanks, I noticed that also this morning and updated it.


Yeah, let me know if you have any issues with that $5 vultr node and the instructions, and if I should merge your instructions in, or do you want to clone the Create_Sanctuary wiki and merge yours into a new one to make a more detailed version?  Maybe that would be better then the gurus can use the generic one and move to your detailed one if they fail?

[togoshigekata]

Yeah, let me know if you have any issues with that $5 vultr node and the instructions, and if I should merge your instructions in, or do you want to clone the Create_Sanctuary wiki and merge yours into a new one to make a more detailed version?  Maybe that would be better then the gurus can use the generic one and move to your detailed one if they fail?

Im open to either! I did originally plan to create a sanctuary guide but didnt move forward on it, I think this would be a good time to do it since Ill be stepping through the process again