Bible Pay

Read 7841 times

  • Rob Andrews
  • Administrator

    • 1920


    • 26
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #465 on: May 22, 2019, 05:30:50 pm »
I was using 1429 because I didn't know that there is new version. I didn't found any mention about new version here ;)
Now I have 1431 and here are my answers:
A) Yes, I agree 1.4.3.1 has no extra boxes in the About page
B) I've got a message from my antivirus (Avast) that the file is clear and it's working good now
C) That debug.log is still there. BUT  this debug.log is not in %appdata%. It's in install DOC folder. Here is a screenshot: https://prnt.sc/nrhg7t This file is from end of the March and here is the beginning of that file:
Code: [Select]
2019-03-29 16:54:05 BiblePay Core version 1.4.0.5
2019-03-29 16:54:05 InitParameterInteraction: parameter interaction: -externalip set -> setting -discover=0
2019-03-29 16:54:05 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-03-29 16:54:05 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-03-29 16:54:05 GUI: QCssParser::parseHexColor: Unknown color name '#yellow'
2019-03-29 16:54:05 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-03-29 16:54:05 ***************************************** BIBLEPAY  ***************************************************
2019-03-29 16:54:05 ProdMode: Prod 0.000000BiblePayVersion 1.4.0.5 (BiblePay Core)

It's nice that the BiblepayEvo insttall file is on main page. But I have question for Ubuntu packages. Will they be ready on Evo start? Will be there any changes in repository or the ppa:biblepay-official/mainnet remains the same? Because I'm using packages for my VPS and it wouldn't be fair to be in a disadvantage :)

And I have another wish :) It would be nice to have smart contract reward txs on wallet main page Recent transactions list, because now they are only in tx page.

Hi Orbis,

Yes, your right, I forgot to tell everyone to test 1.4.3.1, good point.  The only new feature we didnt test here was 'leaderboard'.  1.4.3.1 will also show your individual diary entries (or all diary entries).

So yes - I found that log, good find.  It will be removed in 1.4.3.2.

On that GSC rewards being enabled to be on the overview page Recent, could you please add a github issue to the new evolution branch? 

So on our RPM releases, good news and bad news.  So MIP makes the RPMs normally, but we have an issue- one of the third party components in dash-evo will not build in an RPM (its an upstream problem actually).  So here is our plan:  We will compile and release MacOSX, Win64, Win32, Ubuntu16, and Ubuntu18 binaries and deploy all of them to the web site.  So the main thing we are missing is the ability to use a PPA on linux.  We expect to have this resolved within 90 days however but its a complicated problem and MIP is actively researching it. 

Ill post when I have some more builds ready so we can verify the debug is gone.



  • oncoapop
  • Newbie

    • 44


    • 7
    • October 23, 2018, 12:31:17 pm
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #466 on: May 24, 2019, 02:25:04 am »
Thank you for the EVO update
Here are the results of  testing   EVO 1.4.3.1 on MAINNET

==================================================
>exec getcampaigns
{
  "List Of": "BiblePay Campaigns",
  "campaign HEALING": "HEALING",
  "campaign POG": "POG",
  "List Of": "BiblePay CPKs",
  "member [oncoapop2]": "BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr",
  "member [evo@main]": "BEv63xKxjAvZpQMCG2dzpLU7wTCcUhpRYd",
  "member [Heb]": "BQHKwoVx4bwN8ewJvvxFXsrYVBzcPTsqvM",
  "member [evo1.4.2.8]": "BTHqzzo9rRDHYNfXqQAEtua1iKxkQz7wya",
  "List Of": "Campaign Participants"
}


>exec join POG
{
  "Command": "join",
  "Results": false,
  "Error": "Unable to sign CPK BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr (Private key not available)"
}

(I did not unlock my wallet; wallet needs to be unlocked as a transaction is sent in order for it to be registered on the blockchain)

>exec join POG
{
  "Command": "join",
  "Results": true
}

>exec join HEALING
{
  "Command": "join",
  "Results": true,
  "Warning!": "Please read this guide: https://wiki.biblepay.org/BiblePay_Healing_Campaign with critical instructions before attempting Spiritual Warfare or Street Healing.  Thank you for joining the BiblePay Healing campaign. "
}

(wait for about 10-15 min)

>exec getcampaigns
{
  "List Of": "BiblePay Campaigns",
  "campaign HEALING": "HEALING",
  "campaign POG": "POG",
  "List Of": "BiblePay CPKs",
  "member [oncoapop2]": "BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr",
  "member [evo@main]": "BEv63xKxjAvZpQMCG2dzpLU7wTCcUhpRYd",
  "member [Heb]": "BQHKwoVx4bwN8ewJvvxFXsrYVBzcPTsqvM",
  "member [evo1.4.2.8]": "BTHqzzo9rRDHYNfXqQAEtua1iKxkQz7wya",
  "List Of": "Campaign Participants",
  "campaign-HEALING-member [oncoapop2]": "BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr",
  "campaign-POG-member [oncoapop2]": "BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr"
}

===========================================
>exec sendgscc "This is a test to see what I can enter"
{
  "Command": "sendgscc"
}

Don't know how this is supposed to work on MAINNET without EVO sancs. So we would probably not appear on the leaderboard?

>leaderboard
{
  "Prominence": "Details",
  "Healing": "Diary Entries",
  "Prominence": "Totals"
}

=======================================
Minor fixes
1. Some extra boxes can still be found under the menu items:
>Help>Command-line options and PrivateSend info


  • oncoapop
  • Newbie

    • 44


    • 7
    • October 23, 2018, 12:31:17 pm
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #467 on: May 24, 2019, 05:09:44 pm »
Set up of EVO on mainnet on pool. May be config is incorrect?

  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; ",
  "gsc_errors": "",
  "poolmining": false,
  "pool_url": "https://pool.biblepay.org/",
  "required_abn_weight": 0

Config:
#Turn ON to mine
gen=1

# Pool Mining
pool=https://pool.biblepay.org/
workerid=oncoapop



  • Rob Andrews
  • Administrator

    • 1920


    • 26
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #468 on: May 24, 2019, 05:30:03 pm »
Set up of EVO on mainnet on pool. May be config is incorrect?

  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; ",
  "gsc_errors": "",
  "poolmining": false,
  "pool_url": "https://pool.biblepay.org/",
  "required_abn_weight": 0

Config:
#Turn ON to mine
gen=1

# Pool Mining
pool=https://pool.biblepay.org/
workerid=oncoapop




Hmmm, try taking off the trailing slash on pool.  I see you created the workerid.


I will also reply to that last post asap.




  • oncoapop
  • Newbie

    • 44


    • 7
    • October 23, 2018, 12:31:17 pm
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #469 on: May 24, 2019, 06:05:45 pm »



Hmmm, try taking off the trailing slash on pool.  I see you created the workerid.


I will also reply to that last post asap.

Ok thank you for the reply.
It works and EVO wallet is hashing...

Cheers!


  • oncoapop
  • Newbie

    • 44


    • 7
    • October 23, 2018, 12:31:17 pm
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #470 on: May 24, 2019, 07:11:21 pm »
It took awhile but it appears on the leaderboard on the Mainnet.

leaderboard
{
  "Prominence": "Details",
  "POG: BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr [oncoapop2], Pts: 1858.00": "94.95%",
  "Prominence": "Totals",
  "ALL: BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr [oncoapop2], Pts: 1858.00, Reward: 2479809.15": "94.95%"
}


  • oncoapop
  • Newbie

    • 44


    • 7
    • October 23, 2018, 12:31:17 pm
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #471 on: May 25, 2019, 07:21:44 am »
It took awhile but it appears on the leaderboard on the Mainnet.

leaderboard
{
  "Prominence": "Details",
  "POG: BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr [oncoapop2], Pts: 1858.00": "94.95%",
  "Prominence": "Totals",
  "ALL: BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr [oncoapop2], Pts: 1858.00, Reward: 2479809.15": "94.95%"
}

Maybe this is a bit premature as we don't have any EVO sancs on mainnet (see health) but leaderboard output only appears on the console/cli but not in the Winx64 GUI.

>exec health
{
  "Command": "health",
  "pam_hash": "0000000000000000000000000000000000000000000000000000000000000000",
  "pam_hash_internal": "000000000000000000000000000000004c10cf0f7b47a9a04a5dcbe59b528b76",
  "WARNING": "Our internal PAM hash disagrees with the network. ",
  "govobjhash": "0000000000000000000000000000000000000000000000000000000000000000",
  "Amounts": "",
  "Addresses": "",
  "votes": 0,
  "required_votes": 10,
  "last_superblock": 121380,
  "next_superblock": 121585,
  "next_superblock_triggered": false,
  "Healthy": false,
  "GSC_Voted_In": false
}


  • Rob Andrews
  • Administrator

    • 1920


    • 26
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #472 on: May 27, 2019, 10:26:42 am »
Maybe this is a bit premature as we don't have any EVO sancs on mainnet (see health) but leaderboard output only appears on the console/cli but not in the Winx64 GUI.

>exec health
{
  "Command": "health",
  "pam_hash": "0000000000000000000000000000000000000000000000000000000000000000",
  "pam_hash_internal": "000000000000000000000000000000004c10cf0f7b47a9a04a5dcbe59b528b76",
  "WARNING": "Our internal PAM hash disagrees with the network. ",
  "govobjhash": "0000000000000000000000000000000000000000000000000000000000000000",
  "Amounts": "",
  "Addresses": "",
  "votes": 0,
  "required_votes": 10,
  "last_superblock": 121380,
  "next_superblock": 121585,
  "next_superblock_triggered": false,
  "Healthy": false,
  "GSC_Voted_In": false
}

Yeah, that is OK, because we are checking for the Evo cutover height in that Gui area, so it populate 200 blocks after the cutover height (after 123,200).

I didn't forget about the last two posts, I will still address them.

(We are doing some testing on ChainLocks in the background and readying a new phase for TestNet).

We decided in IT to keep this thread going after the Evo go live to allow us to test everything Dash has been working on in 0.14+ that won't make the BiblePay-Evo release deadline.




  • Rob Andrews
  • Administrator

    • 1920


    • 26
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #473 on: May 27, 2019, 11:41:03 am »
Thank you for the EVO update
Here are the results of  testing   EVO 1.4.3.1 on MAINNET

==================================================
Code: [Select]
>exec getcampaigns
{
  "List Of": "BiblePay Campaigns",
  "campaign HEALING": "HEALING",
  "campaign POG": "POG",
  "List Of": "BiblePay CPKs",
  "member [oncoapop2]": "BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr",
  "member [evo@main]": "BEv63xKxjAvZpQMCG2dzpLU7wTCcUhpRYd",
  "member [Heb]": "BQHKwoVx4bwN8ewJvvxFXsrYVBzcPTsqvM",
  "member [evo1.4.2.8]": "BTHqzzo9rRDHYNfXqQAEtua1iKxkQz7wya",
  "List Of": "Campaign Participants"
}


>exec join POG
{
  "Command": "join",
  "Results": false,
  "Error": "Unable to sign CPK BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr (Private key not available)"
}

(I did not unlock my wallet; wallet needs to be unlocked as a transaction is sent in order for it to be registered on the blockchain)

>exec join POG
{
  "Command": "join",
  "Results": true
}

>exec join HEALING
{
  "Command": "join",
  "Results": true,
  "Warning!": "Please read this guide: https://wiki.biblepay.org/BiblePay_Healing_Campaign with critical instructions before attempting Spiritual Warfare or Street Healing.  Thank you for joining the BiblePay Healing campaign. "
}

(wait for about 10-15 min)

>exec getcampaigns
{
  "List Of": "BiblePay Campaigns",
  "campaign HEALING": "HEALING",
  "campaign POG": "POG",
  "List Of": "BiblePay CPKs",
  "member [oncoapop2]": "BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr",
  "member [evo@main]": "BEv63xKxjAvZpQMCG2dzpLU7wTCcUhpRYd",
  "member [Heb]": "BQHKwoVx4bwN8ewJvvxFXsrYVBzcPTsqvM",
  "member [evo1.4.2.8]": "BTHqzzo9rRDHYNfXqQAEtua1iKxkQz7wya",
  "List Of": "Campaign Participants",
  "campaign-HEALING-member [oncoapop2]": "BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr",
  "campaign-POG-member [oncoapop2]": "BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr"
}

===========================================
>exec sendgscc "This is a test to see what I can enter"
{
  "Command": "sendgscc"
}
Don't know how this is supposed to work on MAINNET without EVO sancs. So we would probably not appear on the leaderboard?

>leaderboard
{
  "Prominence": "Details",
  "Healing": "Diary Entries",
  "Prominence": "Totals"
}

=======================================
Minor fixes
1. Some extra boxes can still be found under the menu items:
>Help>Command-line options and PrivateSend info


Thanks, yes, I see we set up the sporks in prod, and you have been able to join the campaign successfully, cool.
Since we don't have any 4.5MM sancs set up yet this is probably a little premature for us to test, so lets try jumping on this around block 123,200 (this is 200 blocks after the May superblock pays).  Ill jump in and help at that time also.   By block 123,100 Ill have at least 5 sancs running in Evo mode also.





  • oncoapop
  • Newbie

    • 44


    • 7
    • October 23, 2018, 12:31:17 pm
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #474 on: May 31, 2019, 01:25:39 am »
I would guess that we need EVO sancs for this to work on mainnet?

>exec price
{
  "Command": "price",
  "consensus_price": 0,
  "qt_phase": 0,
  "qt_prior_phase": 0,
  "qt_future_phase": 0,
  "qt_enabled": false,
  "cur_price": "0.000000000000",
  "BBP/BTC": "0.000000000000",
  "BTC/USD": 0
}

I know that we have tested a host of functions in TestNet. Which of these will be active at block 123,000, please?
1. EVO wallets & EVO sancs, for sure.
2. Heat mining. Will ABN be introduced and if so, what is that going to be set at?
3. QT?

What is the roadmap for the (re-)introduction of
4. exec join campaigns? POG? Healing? Proportion of the emission?

Maybe this was announced elsewhere but sorry to have missed it. Thank you.


  • Rob Andrews
  • Administrator

    • 1920


    • 26
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #475 on: May 31, 2019, 09:52:13 am »
I would guess that we need EVO sancs for this to work on mainnet?

>exec price
{
  "Command": "price",
  "consensus_price": 0,
  "qt_phase": 0,
  "qt_prior_phase": 0,
  "qt_future_phase": 0,
  "qt_enabled": false,
  "cur_price": "0.000000000000",
  "BBP/BTC": "0.000000000000",
  "BTC/USD": 0
}

I know that we have tested a host of functions in TestNet. Which of these will be active at block 123,000, please?
1. EVO wallets & EVO sancs, for sure.
2. Heat mining. Will ABN be introduced and if so, what is that going to be set at?
3. QT?

What is the roadmap for the (re-)introduction of
4. exec join campaigns? POG? Healing? Proportion of the emission?

Maybe this was announced elsewhere but sorry to have missed it. Thank you.

I'm going to add the heights to this new wiki page today, and post to the bitcointalk forum, but in the mean time:
Actually at 123,000 we do a very lateral move and nothing much changes, this is the height in which we expect people to start upgrading and running Evo and mining on Evo.  At 123,001 we retire classic governance sancs, and ask all the sancs to start upgrading to 4.5MM sancs - which I expect to take a few days.

So during the first 400 blocks or so, (after 123,000) its POBH as usual.

QT does require :  QT height to pass, and 4.5MM sancs to have quorums, so that wont start for a couple thousand blocks after the go-live (Ill give exact height in the wiki page).  So yeah it will be zeroes for a while that is actually normal.

The ABN Height and Anti-gpu height is also a couple thousand blocks in the future (after 123,000) - I will also add that height to the wiki today.



  • Rob Andrews
  • Administrator

    • 1920


    • 26
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #476 on: May 31, 2019, 10:42:29 am »
I would guess that we need EVO sancs for this to work on mainnet?

>exec price
{
  "Command": "price",
  "consensus_price": 0,
  "qt_phase": 0,
  "qt_prior_phase": 0,
  "qt_future_phase": 0,
  "qt_enabled": false,
  "cur_price": "0.000000000000",
  "BBP/BTC": "0.000000000000",
  "BTC/USD": 0
}

I know that we have tested a host of functions in TestNet. Which of these will be active at block 123,000, please?
1. EVO wallets & EVO sancs, for sure.
2. Heat mining. Will ABN be introduced and if so, what is that going to be set at?
3. QT?

What is the roadmap for the (re-)introduction of
4. exec join campaigns? POG? Healing? Proportion of the emission?

Maybe this was announced elsewhere but sorry to have missed it. Thank you.


I'll be posting this on the forum later today after I add some of the getting started links:

https://wiki.biblepay.org/Evolution_Upgrade


Please let me know if I didnt answer any of your questions or if you have any concerns that we are missing for the public.



  • Rob Andrews
  • Administrator

    • 1920


    • 26
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #477 on: May 31, 2019, 11:07:38 am »
Great news!  ChainLocks passed testing at Dash and is now deployed to Dash-Prod, this means that for BiblePay, we will be adding ChainLocks to testnet over the next 30 days!

So we held back ChainLocks in prod for our Evo release, but we expect to test ChainLocks over the next quarter and schedule it in for our September release.  At that point, we would have all of the major features and be up to date with Dash's feature set.

It also means that we will have new opportunities to explore things like Proof of Orphan Mining, since it will be impossible to attack BiblePay with a 51% attack.