Bible Pay

Read 66282 times

Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #495 on: December 08, 2017, 08:26:45 pm »
Alex your testnet is on bad chain  ;)

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

yW3UTp2qhNLoHJfnTP57jkgJ7RHzQYtBTH
yfyTLmXcnn1hXvWBGbKCz4QkRobJiUDeAt

It's not on "bad chain". It just didn't finish indexing everything when you tried and I'm guess your addresses are in the higher blocks so that's why it didn't find any transaction. It should be fine now.


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #496 on: December 09, 2017, 08:45:57 am »
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?






Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #497 on: December 09, 2017, 09:30:14 am »
Constructive criticism is always welcome!

There's a lot of new stuff, both in what you see and the backend. I actually added/rewrote a lot of things but I could add the proposals and recent post to the current iquidus explorer easily. The issue is I don't think it scales well and is one of the reasons I'm modifying it.
For example, the current iquidus explorer doesn't keep separate tracks of blocks and transactions so once you get some transactions in, it becomes quite impractical.
(the index page is actually getting data from api calls I created. For example for the proposals, it's something really simple that gets data from the xml feed of smf and get what I need out of it - https://testnet.biblepay-explorer.org/api/getproposals)

For the block page:
I think the current reftagger is a bit useless on the block page because all it does is display the scripture already displayed on that page unless you click on more - then it redirects you to their website where you can read the whole chapter. So, I was just going to have the verses of the block page link directly to that page instead of having that redundancy.

For the main page:
The main page only has the verses so it would make sense to have the reftagger there to get the scriptures so that will be there!

The BX is pretty much brand new in terms of "views". Only the "Wealth distribution page" still uses the old code -for now-, I think everything else has been rewritten. I'm also slowly touching the backend too and I'm now separating transactions and blocks for example . So I'm really moving away from the traditional iquidus explorer most altcoins are using!


  • tiras
  • Jr. Member

    • 57


    • 1
    • September 01, 2017, 02:00:09 pm
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #498 on: December 10, 2017, 09:49:51 pm »
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
« Last Edit: December 10, 2017, 10:00:59 pm by tiras »


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #499 on: December 12, 2017, 08:41:15 am »
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
  • Jr. Member

    • 57


    • 1
    • September 01, 2017, 02:00:09 pm
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #500 on: December 12, 2017, 10:57:13 pm »
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
  • Sr. Member

    • 439


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #501 on: December 12, 2017, 11:10:24 pm »
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]
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)
« Last Edit: December 13, 2017, 11:00:58 am by togoshigekata »


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #502 on: December 13, 2017, 08:42:27 am »
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
  • Sr. Member

    • 439


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #503 on: December 13, 2017, 09:53:17 am »
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 :)


  • tiras
  • Jr. Member

    • 57


    • 1
    • September 01, 2017, 02:00:09 pm
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #504 on: December 13, 2017, 07:59:26 pm »
check out this provider for VPS  :  https://www.hyperexpert.com

1GB 1CPU $3
2GB 2CPU $5

I've been  using it on testnet with no problems so far .



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #505 on: December 13, 2017, 09:29:55 pm »
check out this provider for VPS  :  https://www.hyperexpert.com

1GB 1CPU $3
2GB 2CPU $5

I've been  using it on testnet with no problems so far .
Thanks! Looks like they lost all their customers data once, but for clones of cryptonodes, might be pretty good, as long as static IPs never change.


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #506 on: December 14, 2017, 01:24:47 pm »
Hey Rob, I was just wondering. Is the client version 1.0.6.5 the mandatory or is anything with the protocol 70709 good?

I'm just asking because I totally forgot the dnsseeder is actually only looking at the protocol version to determine if a node is good or not. I could modify it to look at the client version instead but I would like to get a confirmation from you before I go ahead with that.


  • togoshigekata
  • Sr. Member

    • 439


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #507 on: December 14, 2017, 01:37:30 pm »
I updated the backup explorer: http://explorer.biblepay.org:3001/
I plan to move it from AWS to a cheaper Vultr server in the near future, which I guess means I would need a DNS record update to point to new address, Ill let you know Rob!

====

In addition to Robs Original Sanctuary Guide:
http://wiki.biblepay.org/Create_Sanctuary

I also am working on a more detailed/step by step Sanctuary 2 Guide (wasnt sure what to name it):
http://wiki.biblepay.org/Create_Sanctuary_2


  • jaapgvk
  • Hero Member

    • 617


    • 31
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #508 on: December 15, 2017, 03:12:01 am »
I tried setting up a masternode in prod, but in my sanctuary wallet I get the following message when I type 'masternode status':

Code: [Select]
Not capable masternode: Masternode not in masternode list
Mnsync is 999 and everything else went without errors as far as I know. My controller wallet is showing the masternode as 'pre-enabled', but I can't find it on my sanctuary wallet masternodelise.

It's masternode '12161bf30e75b1bebe9d7b0ebf0d73902e0bea07021c400d166debab4a655552' on '84.29.208.33'.

Does anyone know what this might mean? Otherwise I just have to try and setup the masternode again from the start, I guess...



Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #509 on: December 15, 2017, 03:16:48 am »
Try to redownload the blockchain by deleting the "blocks" and "chainstate" folders.