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

[Rob Andrews]

but my Linux biblepayd doesnt working, i had to run it again: very weird
so i have to run from controller wallet classic command by msaternode alias-start NICK?
ill try when i will be at home: now im on nightshift

What do you mean when you say linux not working?  Not syncing?  It probably lost all its nodes when I was offline. 
Yes, from the controller wallet, just do a 'masternode start-all'.

[togoshigekata]

I have a Ryzen CPU mining BiblePay,

"AMD RYZEN 7 1700 8-Core 3.0 GHz (3.7 GHz Turbo) Socket AM4 65W YD1700BBAEBOX Desktop Processor"
https://www.newegg.com/Product/Product.aspx?Item=N82E16819113428&cm_re=ryzen_7-_-19-113-428-_-Product

It has Ubuntu 16.04 installed and an SSD drive
I overclocked it from 3.0GHz to 3.65GHz

it currently has been solo mining and is running v1.0.6.1 of BiblePay on mainnet
At 26 mining threads (100% CPU) I am getting a HPS of 280k

====

What is f8000?
Ill switch the pc to testnet and report back

[togoshigekata]

So, e-commerce is just about ready to test in testnet. 

So far you can list the products from amazon, buy a product, track your order and see your order status history.

I need to write a wiki though similar to retirement accounts in order for you to understand how to test it.

The code has changed, so that will require an upgrade.  Ill be checking it in in about 15 minutes.

Is anyone out there up for an e-commerce test?

Here is a little Primer on BiblePay E-Commerce:

http://wiki.biblepay.org/Ecommerce

Please see directions.

The new Ecommerce code requires 1.0.6.2.   Please upgrade in testnet.

Oh one other thing, on the e-commerce, if you will go ahead and set your actual real home delivery address in the client for the test, I am giving a free gift.  Im giving the actual bible seen in the wiki page to testnet testers.  This way we can test, receive a bible and also see the USPS tracking # in the client.  So if anyone wants to put in the info and go ahead and order it let me know the order guid and Ill see if the biblepay Mouse API worked or not.

Ill update my masternode to v1.0.6.2 right now

And update my biblepay.conf
delivery_name
delivery_address
delivery_address2
delivery_city
delivery_state
delivery_zip
delivery_phone

Ecommerce Commands:
exec listproducts
exec buyproduct 0718083291
exec orderstatus

===

I think Im the only enabled masternode at the moment? Do I need to reindex?

[togoshigekata]

For the ecommerce config,

is it okay to have spaces in the config values?
Do I need to put double quotes around values with spaces?

For state should I use TX or Texas?
For phone do I need to add dashes or anything?

Thanks!

[togoshigekata]

./biblepay-cli exec buyproduct 0718083296
error code: -1
error message:
Delivery name, address, city, state, zip, and phone must be populated.  Please modify your biblepay.conf file to have: delivery_name, delivery_address, delivery_address2 [OPTIONAL], delivery_city, delivery_state, delivery_zip, and delivery_phone populated.

I have the main biblepay.conf file inside ~/.biblepayconf edited with these values added hmmmm

[togoshigekata]

I tested v1.0.6.2 in testnet on my Ryzen,
at 26 threads I got 12.3-13k HPS, it fluctuated alot in that range
Does this seem correct? >.>

[klondike]

how long will be being ASSETID=999?

ROB: now only you and me ENABLED masternodes

[klondike]

nice testnet explorer,perfect 

edit:// for 2 masternodes on 1 controller win wallet is tutorial same?  again send 500k to controller wallet and compile?

[tiras]

masternode was shut down on it's own.

updated the wallet from git.
started the daemon . 
after re-syncing got the status "NEW_START_REQUIRED"

rebooted the VPS.
started the daemon . 
after a while the same :  "NEW_START_REQUIRED"

checking watchdog :

cd /root/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py
Invalid Masternode Status, cannot continue.

what did I do wrong ?

thanks

[togoshigekata]

after re-syncing got the status "NEW_START_REQUIRED"

I think you just need to run the masternode start-alias command from the controller wallet:

Code Select Expand

masternode start-alias SANCTUARY_ALIAS

replace SANCTUARY_ALIAS with the label/alias you named your masternode address

[klondike]

tiras,   yes like togo wrote: i dit it same

VPS rebooted, started daemon then started watchdog and then in controller wallet did command :   masternode start-alias POKUS and worked

[jaapgvk]

My laptop had some problems, so my masternode went down. But I am syncing as we speak, so I should be online again soon.

Aside from that, I'm taking a step back from the crypto world, for a while at least. In my experience, there is so much power and greed involved in bitcoin at the moment, that I feel I can't really cope with the pressure of 'keeping up with the news'. Core vs Jihan etc. So I'm blocking all bitcoin-related sites for a while.

This forum will be the only crypto-related thing I will be keeping an eye on. I will keep the masternode enabled to support our testnet, and if I find the time I will write a guide for the pool (I'm sorry I didn't get to that Rob, and if anyone else want to give it a go, be my guest).

[Rob Andrews]

For the ecommerce config,

is it okay to have spaces in the config values?
Do I need to put double quotes around values with spaces?

For state should I use TX or Texas?
For phone do I need to add dashes or anything?

Thanks!

Hi Togo,
I tested spaces the other day and the spaces actually work, without quotes. 

For state, please use TX.  For Phone yes please use the dashes so you have a 12 character phone.

This will be interesting, let me know when you place the order and Ill see if any errors occurred.

[Rob Andrews]

My laptop had some problems, so my masternode went down. But I am syncing as we speak, so I should be online again soon.

Aside from that, I'm taking a step back from the crypto world, for a while at least. In my experience, there is so much power and greed involved in bitcoin at the moment, that I feel I can't really cope with the pressure of 'keeping up with the news'. Core vs Jihan etc. So I'm blocking all bitcoin-related sites for a while.

This forum will be the only crypto-related thing I will be keeping an eye on. I will keep the masternode enabled to support our testnet, and if I find the time I will write a guide for the pool (I'm sorry I didn't get to that Rob, and if anyone else want to give it a go, be my guest).

Thanks Jaap, I commend your decision!  Im going through the same thing right now- the other community is begging me to do something greedy, to switch to a base of a private version of Ethereum and I said no, I cant take it, I would leave, and besides Im here for BiblePay forever now.  The Greed is killing Americans, and they are choking Jesus out of their lives.  How much is enough?

Anyway yes, once we get this testnet bug-free hopefully you will be back by Christmas to launch a full node.

Have a good one in the mean time.
Rob

[Rob Andrews]

masternode was shut down on it's own.

updated the wallet from git.
started the daemon . 
after re-syncing got the status "NEW_START_REQUIRED"

rebooted the VPS.
started the daemon . 
after a while the same :  "NEW_START_REQUIRED"

checking watchdog :

cd /root/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py
Invalid Masternode Status, cannot continue.

what did I do wrong ?

thanks

I think klondike already answered but I wanted to add:
The masternode requires a status of "999" before it actually listens to our commands (I know, pain), so add this into the process:
After rebooting a masternode wait until 'mnsync status' shows 999, then issue the commands from the controller like start-many etc.

I did prove the other day that you do not have to restart a masternode (physically) when it says new start required.  You can do the start-many and it will respond, as long as its already synced.

Another words life in prod should be like this:

As days go by, and no upgrades are being pushed out:  If you ever see new start required, you go to your controller and issue the start-many command.

Reboots should only be necessary when upgrades (to the software) are required.