Bible Pay

TestNet => Active Discussions => Topic started by: Rob Andrews on March 24, 2019, 01:17:09 pm

Title: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 24, 2019, 01:17:09 pm
EVOLUTION



Currently testing Dash 0.14 features in BiblePay v1.4.5.1+



Testnet Download Links:

Windows v.1.4.5.2+:
https://biblepay.org/biblepayevo32develop.exe


Linux PC 32bits
Daemon: https://biblepay.org/biblepayd-evo-testnet-i686-pc-linux-gnu.tar.gz
QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

Linux PC 64bits
Daemon: https://biblepay.org/biblepayd-evo--testnet-x86_64-pc-linux-gnu.tar.gz
QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

Linux ARM64 daemon: https://biblepay.org/biblepayd-evo-testnet-aarch64-linux-gnu.tar.gz
Linux ARM32 daemon: https://biblepay.org/biblepayd-evo-testnet-arm-linux-gnueabihf.tar.gz

MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg






Mac-OS QT version here:
https://www.biblepay.org/biblepaycore-testnet.dmg



The purpose of this thread is to test BiblePay-Evolution and our new GSCs.

BiblePay-Evolution is our next release (scheduled for June 2019).

It includes all of the features that Bitcoin and Dash added to Dash over the course of 2018.
Including Segwit, Security updates, Lightning network support, BIPS and DIPS, ChainLocks (51% attack prevention), Deterministic Masternodes, Non-financial transactions, the Depends Development Build environment, C++14 compatibility for devs, more reliable chain syncing, better chain reorganization code, more reliable Governance messages, more efficient messages, HD wallets, High definition display support, InstantSend improvements, and more.

In BIblePay, we have added ABN (Anti-BotNet) mining.  This is a feature that requires miners to include an ABN transaction in each of their blocks that spends coin-age according to the network coin-age requirement (see getmininginfo).

We have also added GSCs (Generic Smart Contracts) client and server side.  The GSC allows BiblePay to abstract payments away from a hard consensus to allow the business logic rules to be malleable and configured so that they do not break consensus rules.  This results in a more reliable prod environment.

Before testing, please read about our GSC's here:
https://wiki.biblepay.org/Generic_Smart_Contracts


To Download BiblePay-Evolution, look for v1.4.0.1+ for windows on this link (at first, we will stay with 32 bit builds until we get close to Prod):
https://biblepay.org/biblepaycore-1.4.0-win32-setup.exe

MIP is working on building linux and MAC builds.  If necessary I will be able to release a link for Ubuntu64 builds/linux also.

To self compile Evo:
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

Let us start by testing standard core functionality in testnet.

Launching the client:

Create a biblepaytest.conf file with the following contents:
testnet=1
debug=1

Place the file in ~/.biblepayevolution

Start testnet by typing:
./biblepay-qt -conf=biblepaytest.conf

(Note the blocks and chainstate will sync into the ./biblepayevolution/testnet3 folder.

NOTE:  We are keeping BiblePay's blocks, wallet, and chainstate in its own dedicated folder until the end of the test cycle at which time we determine if it is safe to change our pointer back to legacy biblepay files (as Evolutions blocks support a new file format, compressed, and Evo's wallet format has also been upgraded), so it is safer for us to keep these separate for now. 

NOTE: This version will also work side-by-side our production nodes, it will sync blocks, send and receive coins, however it will not peer with legacy Sanctuaries (as their protocol is too old).  We will need to test creation and usage of Sancs in Prod in Evo, and upgrade all legacy Sancs with a mandatory.




Getting started with Evolution:
https://wiki.biblepay.org/Getting_Started_with_Evolution
GSC's:
https://wiki.biblepay.org/Generic_Smart_Contracts
Healing Campaign:
https://wiki.biblepay.org/BiblePay_Healing_Campaign
Street Healing:
https://wiki.biblepay.org/Street_Healing
Spiritual Warfare:
https://wiki.biblepay.org/Spiritual-Warfare-I

How to upgrade a legacy Sanc:
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

How to create a deterministic sanc from scratch:
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html






** Low hassle Syncing from Zero **

As our blockchain gets bigger it will be useful for us to release utilities to allow one click syncing from zero.
This first version is only for testnet and linux.  Later, I will extend this to windows and prod.

Is anyone interested in testing?  I just tested this from my ubuntu remote box and I was able to sync in a couple minutes.

I will check this into github later, but for now, let me give manual instructions to use the script:

From your linux box:

cd ~/biblepay-evolution
(This is where your source starts, ie /src is one folder down)
wget biblepay.org/syncblocks_testnet.sh
chmod 777 syncblocks_testnet.sh

Now to get in sync for TestNet only, the script automatically deletes just the data files (dont worry, it wont delete anything else), then it pulls down the snapshot of the blocks gzipped and unzips them into the correct places (including the llmq and all necessary governance files), then its up to you re-launch the wallet.  The script does close biblepay as long as your machine supports pkill.

To sync from 0 type:
./syncblocks_testnet.sh

EDIT:

I just created a windows version and tested it on windows 7 and it works.  Will check-in during the next Develop release.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 24, 2019, 08:08:46 pm
Looks like testnet is working, I have one local node and one VM node synced in testnet, here is the hash:

getblockhash 1960
aa5e6bda46848227f6746cd87242881534c662c763614eb80896c91a1da5f83d

BTW!, We restarted the chain in testnet so please just sync from 0.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: thesnat21 on March 25, 2019, 05:18:21 am
Looks like testnet is working, I have one local node and one VM node synced in testnet, here is the hash:

getblockhash 1960
aa5e6bda46848227f6746cd87242881534c662c763614eb80896c91a1da5f83d

BTW!, We restarted the chain in testnet so please just sync from 0.

I'll get a few nodes up today.

Is the chain restart just for testing, or is this being looked at for prod as well?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 08:22:45 am
I'll get a few nodes up today.

Is the chain restart just for testing, or is this being looked at for prod as well?

Only for testnet.

You can sync in prod in evolution with this version.

EDIT:  One of the reasons for this is in Testnet, we changed the Sanc requirement to 1,550,001 (to mirror prod).

Btw, we will need to set up some testnet sancs.

Does anyone need any tBBP?



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: thesnat21 on March 25, 2019, 08:53:50 am
Only for testnet.

You can sync in prod in evolution with this version.

EDIT:  One of the reasons for this is in Testnet, we changed the Sanc requirement to 1,550,001 (to mirror prod).

Btw, we will need to set up some testnet sancs.

Does anyone need any tBBP?

Sounds good, i'll do some mining on there see how quick it ramps up.

Interesting, the default "Prod' theme is the old pink bars,  testnet default is the belazeel theme, is this intentional?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 09:25:31 am
Sounds good, i'll do some mining on there see how quick it ramps up.

Interesting, the default "Prod' theme is the old pink bars,  testnet default is the belazeel theme, is this intentional?

No - I ported the line that supposed to set the default, not sure why it changed.

I was using Bezaleel the whole time til last night I noticed a new node had the non bez.  Will look at this.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 11:42:09 am
No - I ported the line that supposed to set the default, not sure why it changed.

I was using Bezaleel the whole time til last night I noticed a new node had the non bez.  Will look at this.
I fixed the PNGs for the next version; I verified the default is already set to Bezaleel; I think the 'pick' problem has to do with the name of the key its using (will still check that).


I just started two legacy-type sancs (IE non deterministic) in testnet.


We are now waiting for 80 blocks to pass to see if we can test a GSC.


In the mean time, you guys can do a 'exec cpk nickname' to create a CPK.

Then do a "exec join pog" .


Then wait 40 blocks and see if your system sends a "GSC-Transmission".

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: thesnat21 on March 25, 2019, 12:39:06 pm
I fixed the PNGs for the next version; I verified the default is already set to Bezaleel; I think the 'pick' problem has to do with the name of the key its using (will still check that).


I just started two legacy-type sancs (IE non deterministic) in testnet.


We are now waiting for 80 blocks to pass to see if we can test a GSC.


In the mean time, you guys can do a 'exec cpk nickname' to create a CPK.

Then do a "exec join pog" .


Then wait 40 blocks and see if your system sends a "GSC-Transmission".

I see a notice "every sanctuary (of 1 known ones) is on a newer version than you".

So far i've "earned" 350k bbp, but none has matured yet.   I'll take some tbbp for a mn i supposeyjGK2wqh2M5SMiieyayiqtD2i7EqnwHVLZ

I'll do the register/join as soon as i'm able.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 12:55:13 pm
I see a notice "every sanctuary (of 1 known ones) is on a newer version than you".

So far i've "earned" 350k bbp, but none has matured yet.   I'll take some tbbp for a mn i supposeyjGK2wqh2M5SMiieyayiqtD2i7EqnwHVLZ

I'll do the register/join as soon as i'm able.

One interesting thing I just learned (no wonder the Bezaleel setting was already set), QT actually dumps the settings to a place the user doesn't pick (IE the checkbox settings), I think to ~/user/.config/username/settings.conf - so that would explain how we are picking up non-default values, lol, there is a reason for everything.  Ill add a logprintf with the exact location this afternoon.

Sent 2.5 mm.

Please dont mine Toooo fast, as it will slow us all down ha ha.

Ill be back I have to run a couple errands.

Uhhh, I think the notice of the sanc alert is because I set the sancs proto version higher than the wallet version (I was trying to prevent all the errors in the log we are seeing in Prod, because our sancs in prod are too old to peer with the Evo sancs - even the legacy evo compatibility will not work in our case because the BiblePay classic messages are too short, so I believe that fixed that), so Ill increment the core version in the next build to see if that removes the status bar error.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: thesnat21 on March 25, 2019, 01:13:31 pm
One interesting thing I just learned (no wonder the Bezaleel setting was already set), QT actually dumps the settings to a place the user doesn't pick (IE the checkbox settings), I think to ~/user/.config/username/settings.conf - so that would explain how we are picking up non-default values, lol, there is a reason for everything.  Ill add a logprintf with the exact location this afternoon.

Sent 2.5 mm.

Please dont mine Toooo fast, as it will slow us all down ha ha.

Ill be back I have to run a couple errands.

Uhhh, I think the notice of the sanc alert is because I set the sancs proto version higher than the wallet version (I was trying to prevent all the errors in the log we are seeing in Prod, because our sancs in prod are too old to peer with the Evo sancs - even the legacy evo compatibility will not work in our case because the BiblePay classic messages are too short, so I believe that fixed that), so Ill increment the core version in the next build to see if that removes the status bar error.

Lol it's an old machine running 3 cores mining shouldn't be too crazy but I can scale back if it becomes an issue..

will try to setup sanc tonight
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: madmurphy on March 25, 2019, 01:47:30 pm
I have set testnet up but it seems that I need tBBP to start with
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 02:54:56 pm
Lol it's an old machine running 3 cores mining shouldn't be too crazy but I can scale back if it becomes an issue..

will try to setup sanc tonight

Maybe its not you then, I had a few machines running and got the diff up to 1.  Someone came on and got it up to 70, now it dropped to 52.

No problem, it is working its way out.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 02:55:16 pm
I have set testnet up but it seems that I need tBBP to start with
Thanks man, we can use the help!

Whats your address?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 03:00:23 pm
One interesting thing I just learned (no wonder the Bezaleel setting was already set), QT actually dumps the settings to a place the user doesn't pick (IE the checkbox settings), I think to ~/user/.config/username/settings.conf - so that would explain how we are picking up non-default values, lol, there is a reason for everything.  Ill add a logprintf with the exact location this afternoon.

Sent 2.5 mm.

Please dont mine Toooo fast, as it will slow us all down ha ha.

Ill be back I have to run a couple errands.

Uhhh, I think the notice of the sanc alert is because I set the sancs proto version higher than the wallet version (I was trying to prevent all the errors in the log we are seeing in Prod, because our sancs in prod are too old to peer with the Evo sancs - even the legacy evo compatibility will not work in our case because the BiblePay classic messages are too short, so I believe that fixed that), so Ill increment the core version in the next build to see if that removes the status bar error.


The "mystery" of where Evo is getting its theme-name and checkbox settings is solved. 
The first very good thing I confirmed, is if you delete the Machine settings file, our default really is Bezaleel (for a brand new machine install), so that is very good as new users wont see the pink theme.

(Also in the next version I fixed the PNGs for the other themes that had the invalid icons).

So the checkbox settings are stored here:  /username/.config/Biblepay/ProgramName-Qt-TestOrProd.conf

This explains How the old "./biblepay-qt" settings were auto-migrated to Evo (for test or prod).

So in the end, this is good as regardless of our working dir, settings are migrated, and that means the existing theme is honored.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: madmurphy on March 25, 2019, 03:00:51 pm
yd3Nnd7W2Wmy546wBZGPKV1kN2LDmYq1mQ

thanks
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 25, 2019, 03:21:44 pm
One interesting thing I just learned (no wonder the Bezaleel setting was already set), QT actually dumps the settings to a place the user doesn't pick (IE the checkbox settings), I think to ~/user/.config/username/settings.conf - so that would explain how we are picking up non-default values, lol, there is a reason for everything.  Ill add a logprintf with the exact location this afternoon.

Sent 2.5 mm.

Please dont mine Toooo fast, as it will slow us all down ha ha.

Ill be back I have to run a couple errands.

Uhhh, I think the notice of the sanc alert is because I set the sancs proto version higher than the wallet version (I was trying to prevent all the errors in the log we are seeing in Prod, because our sancs in prod are too old to peer with the Evo sancs - even the legacy evo compatibility will not work in our case because the BiblePay classic messages are too short, so I believe that fixed that), so Ill increment the core version in the next build to see if that removes the status bar error.

I would like to try too, if I may, please.  I have a VPS on testnet (45.62.245.243) but cannot mine or exec cpk as I need tBBP. Can you please send me some and is there a checklist of tasks/features that we should test and report on?  Thank you.

biblepay-cli getaccountaddress ""
yiPiWHpzixrPh9cyVvRLhXwBsVUMUsgHjC
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 03:30:36 pm
I would like to try too, if I may, please.  I have a VPS on testnet (45.62.245.243) but cannot mine or exec cpk as I need tBBP. Can you please send me some and is there a checklist of tasks/features that we should test and report on?  Thank you.

biblepay-cli getaccountaddress ""
yiPiWHpzixrPh9cyVvRLhXwBsVUMUsgHjC

Thanks for joining!  Sent 2.7MM and also to Mad Murphy.

Yes, let me see what else we need to test, I am currently waiting  6  more blocks (as then the next superblock starts) and then I can test a fake Sanc vote, that should give us more things to test.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 25, 2019, 03:35:53 pm
Thanks for joining!  Sent 2.7MM and also to Mad Murphy.

Yes, let me see what else we need to test, I am currently waiting  6  more blocks (as then the next superblock starts) and then I can test a fake Sanc vote, that should give us more things to test.

Thank you! Glad to be part of this project!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 03:47:42 pm
Thank you! Glad to be part of this project!

If we focus on testing the CPK and Pog, we can see if all CPK's and all members of the POG campaign are listed, so right now if we do an:
exec getcampaigns
(This is very crude and hard to understand in this first version, the first two rows are just campaign names- DUMMY was one I created just to ensure logic is working, but its disabled.  The rows labeled "member" are CPKs (the nicknames are current missing).
Then finally the rows labeled 'campaign-POG-member' these are the ones we are most interested in.  We should see one row per -CPK-POG-member, I do see 3 currently.

These 3 should automatically send a GSC transmission within the next hour.

Then soon I will confirm what kind of stats we have for the next superblock.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 03:51:29 pm
Regarding the ABN feature:  The current network ABN requirement per block is 5,000 (this is in coin*age).  Meaning that for example, if you had 2 coins of 2500 each, each being 2 days old, you currently have 10,000 coin*age in your wallet, one of those coins would be used in the ABN transaction for the block.

To see what kind of conformity we have, you can do a 'getblock blocknumber' (we support block numbers in evo in addition to hashes its a biblepay feature), look for the ABN weight field.

Note the reason a lot of blocks dont have weight is because the feature is "on" but we currently only Log the errors and do not reject the blocks (see the log for "ERROR") - I will ensure the next version actually rejects the blocks.  Its ironic as that feature would have kept the diff way down in testnet, but actually we did need to bootstrap the coin since hardly any of us have any coin age.

Then you can do a getrawtransaction txid 1 to see the ABN info.  Ive been auditing these abn's and they look good (we enforce an abn signature on each one, so we know the coin age is really spent).


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 04:04:19 pm
Ok, things are picking up now, we moved ahead about 5 blocks.

So on the positive side, my exec testgscvote actually worked, and I could see that we generated a smart contract for 'yesterday'.  However I didnt actually vote on it because my sanc is in pre-enabled condition - so thats on hold.

Next everyone can type 'exec prominence'.  This shows the report of where your CPK is in the leaderboard (for the next daily reward).  I see this list has no proper formatting, IE the % rank, should be from .01 - 99% - it looks like its rounded up to the int.  Anyway whoever yY8t* is has 94% prominence (this is similar to 94.00% of the daily magnitude), and yVER* has 6% etc.  So the 6% entry would receive 6% of the daily superblock.

Looking at the next problem, I tried to create a test proposal in Proposals | Add and it errored out with an invalid Gov Proposal, LOL.

Let me try to start a second sanc so we can vote on this daily proposal.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: madmurphy on March 25, 2019, 04:25:26 pm
I entered the exec getcampaigns and getblock blocknumber and here is the outcome.


22:21:39

exec getcampaigns


22:21:39

{
  "campaign DUMMY": "DUMMY",
  "campaign POG": "POG",
  "member yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "member yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w": "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w",
  "member yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "member ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "member yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk",
  "campaign-POG-member": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "campaign-POG-member": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "campaign-POG-member": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk"
}


22:22:47

getblock blocknumber


22:22:47

Block not found (code -5)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 25, 2019, 04:31:46 pm
[email protected]:~/.biblepaycore/testnet3$ cli exec getcampaigns
{
  "campaign DUMMY": "DUMMY",
  "campaign POG": "POG",
  "member yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "member yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w": "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w",
  "member yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "member ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "member yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk",
  "campaign-POG-member": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "campaign-POG-member": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "campaign-POG-member": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk"
}

[email protected]:~/.biblepaycore/testnet3$ cli getblockcount
2685
[email protected]:~/.biblepaycore/testnet3$ cli getblock 2685
{
  "hash": "20e3934682df269bfa04d6b65edd67ae216211060834993f16e41fd5c64c2975",
  "confirmations": 1,
  "size": 765,
  "height": 2685,
  "version": 536870913,
  "versionHex": "20000001",
  "merkleroot": "9c3e77326912c2f80d37e00031fb8a3be9707428a56e38764fd7a8825592370b",
  "tx": [
    "959aa7b54f6fa4272bb1ec3a473ab321eacebba7afe9e183d044a558fdf4ab6e",
    "842ef21e8d9d72d90ff7ebf037c8f1e3e9da7441f96a2c9bd34d6a1e2847308d"
  ],
  "cbTx": {
    "version": 1,
    "height": 2685,
    "merkleRootMNList": "0000000000000000000000000000000000000000000000000000000000000000"
  },
  "time": 1553550857,
  "mediantime": 1553548705,
  "hrtime": "03-25-2019 21:54:17",
  "nonce": 133,
  "bits": "1c410e78",
  "difficulty": 39.34979913424137,
  "chainwork": "0000000000000000000000000000000000000000000000000000012a02906cd6",
  "subsidy": 10293,
  "anti-botnet-weight": 6493.106991538543,
  "blockversion": 1401,
  "sanctuary_reward": 0,
  "previousblockhash": "24570b3630565fd7cbb89b2123c8f76a02d2242853538405a4d032513bb33f18",
  "verses": "Sa2|1|6| And the young man that told him said, As I happened by chance upon mount Gilboa, behold, Saul leaned upon his spear; and, lo, the chariots and horsemen followed hard after him.\r\nIsa|21|12| The watchman said, The morning cometh, and also the night: if ye will enquire, enquire ye: return, come.\r\nHag|1|8| Go up to the mountain, and bring wood, and build the house; and I will take pleasure in it, and I will be glorified, saith the LORD.\r\nMat|9|34| But the Pharisees said, He casteth out devils through the prince of the devils.\r\nGen|17|19| And God said, Sarah thy wife shall bear thee a son indeed; and thou shalt call his name Isaac: and I will establish my covenant with him for an everlasting covenant, and with his seed after him.\r\nEze|46|1| Thus saith the Lord GOD; The gate of the inner court that looketh toward the east shall be shut the six working days; but on the sabbath it shall be opened, and in the day of the new moon it shall be opened.\r\nMat|28|18| And Jesus came and spake unto them, saying, All power is given unto me in heaven and in earth.\r\nJer|51|46| And lest your heart faint, and ye fear for the rumour that shall be heard in the land; a rumour shall both come one year, and after that in another year shall come a rumour, and violence in the land, ruler against ruler.\r\n",
  "satisfiesbiblehash": "true",
  "biblehash": "0000000032499f2827e7f74da81f2931b89218175cf53a5c85338598766b986c",
  "chaindata": "<VER>1.4.0.1</VER><abnlocator>1</abnlocator>"
}

[email protected]:~$ cli getrawtransaction 3f386f615e535e25135b41ac85ff8b3ce7396fd0b0437954bc987887b6d354c4
010000000104fe28f332170dd410eff63539bb631a156ea96d011a69a5e5d741624e58a4d6010000006a4730440220141fb61848dc814528921322f9320485de43a29b11bed4cc089df8438df5970002204f25e13b8aa614b96a541dab8e344d830a3338d3e2b9aa66e21235676931ed92012102ab6ec2ed3d0dcdf40bde8cb2d3d9515af77ff8cde5d168cc582b683d92876d47feffffff0200e1f505000000001976a914529b518f59a0f45beb1e15541983bb74eed9715c88acfd29013c4d543e43504b3c2f4d543e3c4d4b3e5959503659524a504f4252545044514f5748544647504d47384e4e454a575942534f3c2f4d4b3e3c4d563e7959703679726a706f6252545064716f7748544647704d47386e6e454a775942536f7c6f6e636f61706f707c313535333535303433377c376637396131386534346162346334643534323431306331376530383036343562336662353034373433646231663532313532396639303534653932336233377c4878503450633471633479505a71714e794751666f69566e6546732f362f6e50336b545a76493755737051354357425457434c335a443449596e664c765237302f4c2f674c2b4a786a4846447572666d47503361474a343d3c2f4d563e3c4e4f4e43453e313535333535303433373c2f4e4f4e43453e684452671cfa00001976a9149d2c3d461028c79253c038fb4dc62471ad86503288ac007a0a0000

[email protected]:~$ cli exec prominence
{
  "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS [N/A] - 12254.00": 0,
  "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9 [N/A] - 1245885.00": 6,
  "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w [N/A] - 20691253.00": 94,
  "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW [N/A] - 11200.00": 0
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 25, 2019, 04:38:59 pm
Associate cpk to nickname. Need to wait for 5 (?) confimations and can only do it once.

[email protected]:~/.biblepaycore/testnet3$ cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": true
}

[email protected]:~/.biblepaycore/testnet3$ cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": false,
  "Error": "A CPK was advertised less then 4 blocks ago. Please wait for your CPK to enter the chain."
}

[email protected]:~$ cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": false,
  "Error": "ALREADY_IN_CHAIN"
}
.....
Try to associate with a new nickname - cannot.

[email protected]:~/biblepay-evolution$ cli exec cpk new
{
  "Command": "cpk",
  "Results": false,
  "Error": "ALREADY_IN_CHAIN"
}

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 05:04:49 pm
Associate cpk to nickname. Need to wait for 5 (?) confimations and can only do it once.

[email protected]:~/.biblepaycore/testnet3$ cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": true
}

[email protected]:~/.biblepaycore/testnet3$ cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": false,
  "Error": "A CPK was advertised less then 4 blocks ago. Please wait for your CPK to enter the chain."
}

[email protected]:~$ cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": false,
  "Error": "ALREADY_IN_CHAIN"
}
.....
Try to associate with a new nickname - cannot.

[email protected]:~/biblepay-evolution$ cli exec cpk new
{
  "Command": "cpk",
  "Results": false,
  "Error": "ALREADY_IN_CHAIN"
}

Sweet, yeah, I dont know if we should let them reassociate with a new nickname, I guess we should.

Good on the exec campaign list guys; looks good.


I see the problem with Proposal Add, it will be fixed in this next build.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 05:06:01 pm
I entered the exec getcampaigns and getblock blocknumber and here is the outcome.


22:21:39

exec getcampaigns


22:21:39

{
  "campaign DUMMY": "DUMMY",
  "campaign POG": "POG",
  "member yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "member yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w": "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w",
  "member yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "member ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "member yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk",
  "campaign-POG-member": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "campaign-POG-member": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "campaign-POG-member": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk"
}


22:22:47

getblock blocknumber


22:22:47

Block not found (code -5)

Good, it matches mine, and the getblock requires either the actual block # (int) or the hash.

Checking some things now... Ill check to see if there is any chance of the sancs voting for this contract without all of us needing to upgrade.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 25, 2019, 05:19:41 pm
Sweet, yeah, I dont know if we should let them reassociate with a new nickname, I guess we should.

Good on the exec campaign list guys; looks good.


I see the problem with Proposal Add, it will be fixed in this next build.

Well, I was just trying to test expected behaviour. I was wondering what happens if you pick a nickname that already is the blockchain?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 05:26:04 pm
Well, I was just trying to test expected behaviour. I was wondering what happens if you pick a nickname that already is the blockchain?

Right now, it allows dupes; but I just added an item to scan first and prevent dupes; and also to allow them to reassociate with a new nick (with force=true).  We should probably add a field for Vendor=1 also, as we can use this CPK as the record for churches (this allows tithes by the congregation).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 25, 2019, 05:49:49 pm
Right now, it allows dupes; but I just added an item to scan first and prevent dupes; and also to allow them to reassociate with a new nick (with force=true).  We should probably add a field for Vendor=1 also, as we can use this CPK as the record for churches (this allows tithes by the congregation).

Excellent! Can one vendor "tithe" to another e.g. church sending its share to association office or for pooled common mission support?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 25, 2019, 06:04:53 pm
Excellent! Can one vendor "tithe" to another e.g. church sending its share to association office or for pooled common mission support?

In the old version, one user can send BBP to another via e-mail address (with a contact record) but no one used it, so I didn't even port it (primarily because we are trying to move to new messages types anyway).

But, as far as one church sending to another, thats a good idea, we can definitely make a command to send BBP to 'nickname', and that would allow a church to send BBP to another church, interesting idea.

So guys, I have found a few bugs that I need to patch tonight so we probably can wait until tomorrow for further testing.

However, it does look like I will be able to manually vote on this superblock, Ill do that now and see if the GSC emits.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 26, 2019, 01:42:09 am
output of listtransactions that might be useful

{
    "account": "CHRISTIAN-PUBLIC-KEY",
    "address": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
    "category": "receive",
    "amount": 275301.80437000,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 2,
    "confirmations": 7,
    "instantlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "d339748db7e7ff13739a34fc1f1519e0f9e75ebccd81e8d6a1ac6764a44b0126",
    "blockindex": 3,
    "blocktime": 1553584016,
    "txid": "fffeae95b36e99389be9ff66cffe01e6a35f71e8d77a7a3a05f51602af23d577",
    "walletconflicts": [
    ],
    "time": 1553583265,
    "timereceived": 1553583265
  },
  {
    "account": "",
    "address": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
    "category": "send",
    "amount": -275301.80437000,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 2,
    "fee": -0.00728000,
    "confirmations": 7,
    "instantlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "d339748db7e7ff13739a34fc1f1519e0f9e75ebccd81e8d6a1ac6764a44b0126",
    "blockindex": 3,
    "blocktime": 1553584016,
    "txid": "fffeae95b36e99389be9ff66cffe01e6a35f71e8d77a7a3a05f51602af23d577",
    "walletconflicts": [
    ],
    "time": 1553583265,
    "timereceived": 1553583265,
    "abandoned": false
  },
  {
    "account": "",
    "address": "yTrEKf8XQ7y7tychC2gWuGw1hsLqBybnEN",
    "category": "send",
    "amount": -7.00000000,
    "vout": 0,
    "fee": -0.00728000,
    "confirmations": 7,
    "instantlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "d339748db7e7ff13739a34fc1f1519e0f9e75ebccd81e8d6a1ac6764a44b0126",
    "blockindex": 3,
    "blocktime": 1553584016,
    "txid": "fffeae95b36e99389be9ff66cffe01e6a35f71e8d77a7a3a05f51602af23d577",
    "walletconflicts": [
    ],
    "time": 1553583265,
    "timereceived": 1553583265,
    "abandoned": false
  },
  {
    "account": "CHRISTIAN-PUBLIC-KEY",
    "address": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
    "category": "receive",
    "amount": 247700.92247500,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 1,
    "confirmations": 7,
    "instantlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "d339748db7e7ff13739a34fc1f1519e0f9e75ebccd81e8d6a1ac6764a44b0126",
    "blockindex": 2,
    "blocktime": 1553584016,
    "txid": "7abcb11cd0d9db2b07ec6c91885120b4c097c645d12e43d8ab10f2fe224bb582",
    "walletconflicts": [
    ],
    "time": 1553583265,
    "timereceived": 1553583265
  },
  {
    "account": "",
    "address": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
    "category": "send",
    "amount": -247700.92247500,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 1,
    "fee": -0.00578000,
    "confirmations": 7,
    "instantlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "d339748db7e7ff13739a34fc1f1519e0f9e75ebccd81e8d6a1ac6764a44b0126",
    "blockindex": 2,
    "blocktime": 1553584016,
    "txid": "7abcb11cd0d9db2b07ec6c91885120b4c097c645d12e43d8ab10f2fe224bb582",
    "walletconflicts": [
    ],
    "time": 1553583265,
    "timereceived": 1553583265,
    "abandoned": false
  },
  {
    "account": "",
    "address": "yTrEKf8XQ7y7tychC2gWuGw1hsLqBybnEN",
    "category": "send",
    "amount": -7.00000000,
    "vout": 0,
    "fee": -0.00578000,
    "confirmations": 7,
    "instantlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "d339748db7e7ff13739a34fc1f1519e0f9e75ebccd81e8d6a1ac6764a44b0126",
    "blockindex": 2,
    "blocktime": 1553584016,
    "txid": "7abcb11cd0d9db2b07ec6c91885120b4c097c645d12e43d8ab10f2fe224bb582",
    "walletconflicts": [
    ],
    "time": 1553583265,
    "timereceived": 1553583265,
    "abandoned": false
  }, cli exec getcampaigns
{
  "campaign DUMMY": "DUMMY",
  "campaign POG": "POG",
  "member yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "member yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "member yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w": "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w",
  "member yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "member ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "member ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "member ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "member yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "member yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk",
  "campaign-DUMMY-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-DUMMY-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-DUMMY-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-POG-member": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "campaign-POG-member": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "campaign-POG-member": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "campaign-POG-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-POG-member": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "campaign-POG-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk"
}


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 26, 2019, 08:28:50 am
output of listtransactions that might be useful
Code: [Select]
{
    "account": "CHRISTIAN-PUBLIC-KEY",
    "address": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
    "category": "receive",
    "amount": 275301.80437000,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 2,
    "confirmations": 7,
    "instantlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "d339748db7e7ff13739a34fc1f1519e0f9e75ebccd81e8d6a1ac6764a44b0126",
    "blockindex": 3,
    "blocktime": 1553584016,
    "txid": "fffeae95b36e99389be9ff66cffe01e6a35f71e8d77a7a3a05f51602af23d577",
    "walletconflicts": [
    ],
    "time": 1553583265,
    "timereceived": 1553583265
  },
  {
    "account": "",
    "address": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
    "category": "send",
    "amount": -275301.80437000,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 2,
    "fee": -0.00728000,
    "confirmations": 7,
    "instantlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "d339748db7e7ff13739a34fc1f1519e0f9e75ebccd81e8d6a1ac6764a44b0126",
    "blockindex": 3,
    "blocktime": 1553584016,
    "txid": "fffeae95b36e99389be9ff66cffe01e6a35f71e8d77a7a3a05f51602af23d577",
    "walletconflicts": [
    ],
    "time": 1553583265,
    "timereceived": 1553583265,
    "abandoned": false
  },
  {
    "account": "",
    "address": "yTrEKf8XQ7y7tychC2gWuGw1hsLqBybnEN",
    "category": "send",
    "amount": -7.00000000,
    "vout": 0,
    "fee": -0.00728000,
    "confirmations": 7,
    "instantlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "d339748db7e7ff13739a34fc1f1519e0f9e75ebccd81e8d6a1ac6764a44b0126",
    "blockindex": 3,
    "blocktime": 1553584016,
    "txid": "fffeae95b36e99389be9ff66cffe01e6a35f71e8d77a7a3a05f51602af23d577",
    "walletconflicts": [
    ],
    "time": 1553583265,
    "timereceived": 1553583265,
    "abandoned": false
  },
  {
    "account": "CHRISTIAN-PUBLIC-KEY",
    "address": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
    "category": "receive",
    "amount": 247700.92247500,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 1,
    "confirmations": 7,
    "instantlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "d339748db7e7ff13739a34fc1f1519e0f9e75ebccd81e8d6a1ac6764a44b0126",
    "blockindex": 2,
    "blocktime": 1553584016,
    "txid": "7abcb11cd0d9db2b07ec6c91885120b4c097c645d12e43d8ab10f2fe224bb582",
    "walletconflicts": [
    ],
    "time": 1553583265,
    "timereceived": 1553583265
  },
  {
    "account": "",
    "address": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
    "category": "send",
    "amount": -247700.92247500,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 1,
    "fee": -0.00578000,
    "confirmations": 7,
    "instantlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "d339748db7e7ff13739a34fc1f1519e0f9e75ebccd81e8d6a1ac6764a44b0126",
    "blockindex": 2,
    "blocktime": 1553584016,
    "txid": "7abcb11cd0d9db2b07ec6c91885120b4c097c645d12e43d8ab10f2fe224bb582",
    "walletconflicts": [
    ],
    "time": 1553583265,
    "timereceived": 1553583265,
    "abandoned": false
  },
  {
    "account": "",
    "address": "yTrEKf8XQ7y7tychC2gWuGw1hsLqBybnEN",
    "category": "send",
    "amount": -7.00000000,
    "vout": 0,
    "fee": -0.00578000,
    "confirmations": 7,
    "instantlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "d339748db7e7ff13739a34fc1f1519e0f9e75ebccd81e8d6a1ac6764a44b0126",
    "blockindex": 2,
    "blocktime": 1553584016,
    "txid": "7abcb11cd0d9db2b07ec6c91885120b4c097c645d12e43d8ab10f2fe224bb582",
    "walletconflicts": [
    ],
    "time": 1553583265,
    "timereceived": 1553583265,
    "abandoned": false
  }, cli exec getcampaigns
{
  "campaign DUMMY": "DUMMY",
  "campaign POG": "POG",
  "member yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "member yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "member yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w": "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w",
  "member [b]yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo[/b]": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "member ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "member ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "member ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "member yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "member yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk",
  "campaign-DUMMY-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-DUMMY-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-DUMMY-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-POG-member": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "campaign-POG-member": "[b]yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo[/b]",
  "campaign-POG-member": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "campaign-POG-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-POG-member": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "campaign-POG-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk"
}


Good, thanks, everything looks good so far, although yyp6* is not in the next superblock (thats because the payment window for it is for contributions between blocks 2480-2685, but you should be in the superblock after that.

We have a superblock coming up @2890 (that pays for contributions up to 2685), coming in 65 more blocks. 

NOTE:  Blocks are supposed to be once per minute in testnet, but we are clearly being attacked.  I think the same person who is sending 6.66 to SouthXchange is doing this as the foundation in testnet is receiving 6.66 tithes and the diff jumped to 115.  This would be a very good time for us to exercise our anti-botnet blocks and see if they work.

We need an upgrade anyway, so let me work on consolidating changes and making a release.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: sunk818 on March 26, 2019, 09:50:05 am
NOTE:  Blocks are supposed to be once per minute in testnet, but we are clearly being attacked.  I think the same person who is sending 6.66 to SouthXchange is doing this as the foundation in testnet is receiving 6.66 tithes and the diff jumped to 115.  This would be a very good time for us to exercise our anti-botnet blocks and see if they work.

We need an upgrade anyway, so let me work on consolidating changes and making a release.


You are back to deleting posts again Rob? So much for decentralization and non-censorship.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 26, 2019, 09:53:47 am

You are back to deleting posts again Rob? So much for decentralization and non-censorship.

Sun, you called me a Fraud and a Fake Christian just now.  There is no reason for this vile, anger and hate.  You also swore at me in SX.

I don't want this type of behavior here!  I invite the Holy Spirit here.

Please, stop this Sun, and apologize for this horrible behavior and admit you sinned and repent.

Then I will accept you back to this project.  Until then do not post anymore or hurt other users.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 26, 2019, 11:32:12 am
1.4.0.2-TestNet Mandatory Upgrade

- Enable Anti-botnet-rules and sporks
- Disconnect from pre 1402 nodes
- Ensure daily superblocks honor avg trailing difficulty level (this
ensures emission is within the Covenant)
- Enable Proposal Add
- Fix Proposal List Voting issue
- Fix bad Bezaleel graphics
- Enable CPK icon in TxList
- Scan for duplicates in nicknames before accepting CPK nickname
- Add nickname to exec prominence
- Ensure Sanc Quorum can create a conforming contract
- Increment Gov Testnet version in attempt to remove status bar warning

EDIT: The download link has not changed:
https://biblepay.org/biblepaycore-1.4.0-win32-setup.exe

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: madmurphy on March 26, 2019, 01:47:00 pm
I have downloaded the new version but I seem to be stuck connecting to peers ?
The progress bar says I am 76 mins behind but it does not progress.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 26, 2019, 03:53:50 pm
I have downloaded the new version but I seem to be stuck connecting to peers ?
The progress bar says I am 76 mins behind but it does not progress.

Yeah, I had to shut my 3 nodes down because we had a biblepay vendor demand a change in the old code, sigh.

Please hang on...
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 26, 2019, 04:13:15 pm
I have downloaded the new version but I seem to be stuck connecting to peers ?
The progress bar says I am 76 mins behind but it does not progress.


Ok we are rolling again, Im on 2886.  Lets see if we solve a GSC superblock :).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 26, 2019, 04:50:52 pm

Ok we are rolling again, Im on 2886.  Lets see if we solve a GSC superblock :).

I just set up the anti-botnet-enforcement flag to enabled, but this will take a few blocks to kick in - so hopefully after that, we won't see anymore hash attacks in testnet, lets see.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 26, 2019, 05:04:34 pm
Set up a sanctuary but cannot seem to enable watchman. Nonetheless  got a payment of 10286 .

Block 2887
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 26, 2019, 08:20:35 pm
Set up a sanctuary but cannot seem to enable watchman. Nonetheless  got a payment of 10286 .

Block 2887
Sorry to dissapoint you, but I haven't ported watchman over yet to Evo -- I'm still checking to make sure we need it.  But if your sanc moves to Enabled, at least we can use it in testnet.

On another note, I see we did not emit the superblock at 2890.  We had 2 votes (which is the minimum) but its possible due to the versioning it didn't emit - checking into that now.

(Your 10k block was a regular mined block).  Diff is starting to drop.  I see that each block has ABN weight now (except blocks that were Late IE over an hour old).  Hopefully in a couple more blocks we will be back to normal block spacing.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 26, 2019, 08:24:16 pm
So I finally see why the status bar is appearing to warn us that sancs have newer software than our own software.

There is a new Evo file that needs updated on each release - So whats happening is the "build" is picking up 1.2.0.1 from the first release and converting it to 1020010 which is less than 1040020, so Ill add this to the build process and the next version should be without warnings.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 26, 2019, 08:34:12 pm
I see in 'exec prominence' im the only one with a nickname.  We added the feature in this version to allow you to re-force your CPK with a nick.

'exec cpk nickname true' (true means force).  Note, you have to pick a new nickname if its in use.

Then do the exec prominence again and see if it picks it up.

Prominence is our leaderboard.

(The digit scale is fixed).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 26, 2019, 08:52:20 pm
Ill be going to sleep soon, but the main goal today is to see if we can get GSC superblock 3095 to emit (if blocks speed up this should emit in about 4 hours).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 26, 2019, 09:01:26 pm
Also, someone can test Adding a fake proposal, and once it is in the chain and list, then vote on the proposal.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 26, 2019, 10:07:05 pm
I see in 'exec prominence' im the only one with a nickname.  We added the feature in this version to allow you to re-force your CPK with a nick.

'exec cpk nickname true' (true means force).  Note, you have to pick a new nickname if its in use.

Then do the exec prominence again and see if it picks it up.

Prominence is our leaderboard.

(The digit scale is fixed).

I can find my nickname on  cli exec getcampaigns
{
  "campaign DUMMY": "DUMMY",
  "campaign POG": "POG",
  "member [oncoapop]yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4": "yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4",
  "member []yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "member []yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "member [randrews2]yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w": "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w",
  "member []yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "member []ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "member []ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "member [randrews]ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "member []yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "member []yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk",
  "campaign-DUMMY-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-DUMMY-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-DUMMY-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-POG-member": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "campaign-POG-member": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "campaign-POG-member": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "campaign-POG-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-POG-member": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "campaign-POG-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk"

Address appears in campaigns but not in leaderboard

cli exec prominence
{
  "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS [N/A] - 22118.00": 0.17,
  "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9 [N/A] - 2545762.00": 19.22,
  "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w [randrews2] - 7278035.00": 54.94,
  "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo [N/A] - 2373441.00": 17.92,
  "yboD6R7BNsYprPh3VutRYo9miVvNx7qurC [N/A] - 211051.00": 1.59,
  "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1 [N/A] - 387274.00": 2.92,
  "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW [N/A] - 63873.00": 0.48,
  "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk [N/A] - 365706.00": 2.76
}

Changing the nickname
cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": false,
  "Error": "Sorry, NickName is already taken."
}
Good. duplicate names are prevented.

[email protected]:~$ cli exec cpk "onco12&23\45" true
{
  "Command": "cpk",
  "Results": true
}

Let's see how it takes characters in nickname


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 26, 2019, 11:15:10 pm
I can find my nickname on  cli exec getcampaigns
{
  "campaign DUMMY": "DUMMY",
  "campaign POG": "POG",
  "member [oncoapop]yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4": "yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4",
  "member []yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "member []yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "member [randrews2]yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w": "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w",
  "member []yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "member []ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "member []ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "member [randrews]ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "member []yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "member []yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk",
  "campaign-DUMMY-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-DUMMY-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-DUMMY-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-POG-member": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "campaign-POG-member": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "campaign-POG-member": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "campaign-POG-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-POG-member": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "campaign-POG-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk"

Address appears in campaigns but not in leaderboard

cli exec prominence
{
  "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS [N/A] - 22118.00": 0.17,
  "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9 [N/A] - 2545762.00": 19.22,
  "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w [randrews2] - 7278035.00": 54.94,
  "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo [N/A] - 2373441.00": 17.92,
  "yboD6R7BNsYprPh3VutRYo9miVvNx7qurC [N/A] - 211051.00": 1.59,
  "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1 [N/A] - 387274.00": 2.92,
  "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW [N/A] - 63873.00": 0.48,
  "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk [N/A] - 365706.00": 2.76
}

Changing the nickname
cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": false,
  "Error": "Sorry, NickName is already taken."
}
Good. duplicate names are prevented.

[email protected]:~$ cli exec cpk "onco12&23\45" true
{
  "Command": "cpk",
  "Results": true
}

Let's see how it takes characters in nickname

Nice work! It appears to strip them out...

 cli exec getcampaigns
{
  "campaign DUMMY": "DUMMY",
  "campaign POG": "POG",
  "member [onco122345]yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4": "yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4",
  "member []yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "member []yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "member [randrews2]yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w": "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w",
  "member []yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "member []ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "member []ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "member [randrews]ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "member []yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "member []yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk",
  "campaign-DUMMY-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-DUMMY-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-DUMMY-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-POG-member": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "campaign-POG-member": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "campaign-POG-member": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "campaign-POG-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-POG-member": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "campaign-POG-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk"
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 27, 2019, 12:17:35 am
Also, someone can test Adding a fake proposal, and once it is in the chain and list, then vote on the proposal.

I tried to add proposal on http://pool.biblepay.org/ on testnet
Used this as the receiving address "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo"
and this is the result
Invalid receiving address. [test]

Is there a way to create a proposal using command line?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 27, 2019, 09:11:04 am
I tried to add proposal on http://pool.biblepay.org/ on testnet
Used this as the receiving address "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo"
and this is the result
Invalid receiving address. [test]

Is there a way to create a proposal using command line?

Hi!  Thanks for testing.

Are you sure you had the receiving address in that field?  I added one from the UI yesterday morning and it went in.  Could you please try again from the UI, and if it doesnt work, give me the amount and the actual URL you used also?

No, currently no way to enter one from the command line.  Just from QT or the Pool.

Also, you do have to wait 6 blocks once you see it enter, so please dont shut the wallet down after you enter it - just keep going back to the add page and reading the bottom status caption.

EDIT:  Ok, I just entered a 2nd one and it worked, you might have had a space in the receiving address or something.  I used this testnet URL as my url.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 27, 2019, 09:36:58 am
I can find my nickname on  cli exec getcampaigns
{
Code: [Select]
  "campaign DUMMY": "DUMMY",
  "campaign POG": "POG",
  "member [[b]oncoapop[/b]]yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4": "yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4",
  "member []yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "member []yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "member [randrews2]yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w": "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w",
  "member []yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "member []ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "member []ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "member [randrews]ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "member []yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "member []yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk",
  "campaign-DUMMY-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-DUMMY-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-DUMMY-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-POG-member": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "campaign-POG-member": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "campaign-POG-member": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "campaign-POG-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-POG-member": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "campaign-POG-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk"

[b][u]Address appears in campaigns but not in leaderboard[/u][/b]

cli exec prominence
{
  "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS [N/A] - 22118.00": 0.17,
  "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9 [N/A] - 2545762.00": 19.22,
  "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w [randrews2] - 7278035.00": 54.94,
  "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo [N/A] - 2373441.00": 17.92,
  "yboD6R7BNsYprPh3VutRYo9miVvNx7qurC [N/A] - 211051.00": 1.59,
  "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1 [N/A] - 387274.00": 2.92,
  "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW [N/A] - 63873.00": 0.48,
  "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk [N/A] - 365706.00": 2.76
}

[b][u]Changing the nickname[/u][/b]
cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": false,
  "Error": "Sorry, NickName is already taken."
}
Good. duplicate names are prevented.

[email protected]:~$ cli exec cpk "onco12&23\45" true
{
  "Command": "cpk",
  "Results": true
}
Let's see how it takes characters in nickname


Thanks a lot for your help.  10-4 on the positive parts.

I added a punchlist item to verify why nicks appear in exec campaigns and not in exec prominence (it might be intentional due to the way this new system has better data integrity for each superblock, but either way Ill investigate that).  Things look pretty good overall.

Waiting for this next superblock to hit... Block 3095, 100 more blocks.

Then we will know if daily GSC superblocks are being paid.  (For the first time).




Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 27, 2019, 10:16:45 am
Hi!  Thanks for testing.

Are you sure you had the receiving address in that field?  I added one from the UI yesterday morning and it went in.  Could you please try again from the UI, and if it doesnt work, give me the amount and the actual URL you used also?

No, currently no way to enter one from the command line.  Just from QT or the Pool.

Also, you do have to wait 6 blocks once you see it enter, so please dont shut the wallet down after you enter it - just keep going back to the add page and reading the bottom status caption.

EDIT:  Ok, I just entered a 2nd one and it worked, you might have had a space in the receiving address or something.  I used this testnet URL as my url.

Maybe I am doing something wrong? Output for all is Invalid receiving address. [test]. My pool balance is 0 though.

Note:   ** [test] Note: Each new Proposal costs 2500 BBP. Please do not Save the proposal unless you agree to pay 2500 BBP **
Proposal Name   
Testnet Test proposal from Pool
 
Funding Receiving Address   (tried the following >2500 BBP balance addresses)
yaQdt98JLVRnFce9QqgKrc93jdA3L3uG1W
ygcrhpgHgQiXEZg9zHJhrdfo72JPs3qfp9
ycpq3yrsCfqQBTPePfkBV8mnQESFy6xCQZ
yXtakbG2nNnx6zkEoBFHADTSVtiYUq7P88
yN3hPTGWFiaRa4shVNyn5aSDX9FN35gRwW
yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4
 
Proposal Amount   
10000
 
Discussion URL   
https://forum.biblepay.org/index.php?topic=391.msg5569#msg5569
 
Expense Type:   IT

Output
Invalid receiving address. [test]
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 27, 2019, 10:21:39 am
Maybe I am doing something wrong? Output for all is Invalid receiving address. [test]. My pool balance is 0 though.

Note:   ** [test] Note: Each new Proposal costs 2500 BBP. Please do not Save the proposal unless you agree to pay 2500 BBP **
Proposal Name   
Testnet Test proposal from Pool
 
Funding Receiving Address   (tried the following >2500 BBP balance addresses)
yaQdt98JLVRnFce9QqgKrc93jdA3L3uG1W
ygcrhpgHgQiXEZg9zHJhrdfo72JPs3qfp9
ycpq3yrsCfqQBTPePfkBV8mnQESFy6xCQZ
yXtakbG2nNnx6zkEoBFHADTSVtiYUq7P88
yN3hPTGWFiaRa4shVNyn5aSDX9FN35gRwW
yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4
 
Proposal Amount   
10000
 
Discussion URL   
https://forum.biblepay.org/index.php?topic=391.msg5569#msg5569
 
Expense Type:   IT

Output
Invalid receiving address. [test]

Ohhhh ok, 0 balance, OK, we must have a bad error message when it does not have enough for the minimum collateral! 


EDIT: I just realized you said "pool balance", and you obviously have tBBP.


I just added a check in the wallet for a minimum of 2500 bbp in order to create a proposal.

One sec...

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 27, 2019, 10:36:20 am
Ohhhh ok, 0 balance, OK, we must have a bad error message when it does not have enough for the minimum collateral! 


EDIT: I just realized you said "pool balance", and you obviously have tBBP.


I just added a check in the wallet for a minimum of 2500 bbp in order to create a proposal.

One sec...

Ok, I just realized you were testing this from the Pool.

(You dont have to test the pool, as I know that part works - although yes we should test Evo against the pool a little later for sanity sake but I dont have the pool daemon pointed to Evo yet).

But yeah I would like to test Adding a proposal through the QT wallet, and voting on a proposal.

(I added a couple to the qt wallet and was able to vote on them but more eyes are better).


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 27, 2019, 12:41:21 pm
I can find my nickname on  cli exec getcampaigns
{
  "campaign DUMMY": "DUMMY",
  "campaign POG": "POG",
  "member [oncoapop]yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4": "yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4",
  "member []yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "member []yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "member [randrews2]yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w": "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w",
  "member []yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "member []ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "member []ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "member [randrews]ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "member []yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "member []yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk",
  "campaign-DUMMY-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-DUMMY-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-DUMMY-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS",
  "campaign-POG-member": "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9",
  "campaign-POG-member": "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo",
  "campaign-POG-member": "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1",
  "campaign-POG-member": "ybywyyKM2GaBQchYM72fnVYEk5vVBF9Yvf",
  "campaign-POG-member": "ygNZ6UjvRt6kRShw5X1hwFuv8KaYUJ96Z8",
  "campaign-POG-member": "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "campaign-POG-member": "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk"

Address appears in campaigns but not in leaderboard

cli exec prominence
{
  "yTTkbxTnZuq7ozZk1xLzSsgZMrHmvVVTYS [N/A] - 22118.00": 0.17,
  "yVERuh8wC1nVatoxcCmL7TysDSqoKXk4e9 [N/A] - 2545762.00": 19.22,
  "yY8tWKFao1Krn4qkiS7FcQmsHdqATRo48w [randrews2] - 7278035.00": 54.94,
  "yYp6yrjpobRTPdqowHTFGpMG8nnEJwYBSo [N/A] - 2373441.00": 17.92,
  "yboD6R7BNsYprPh3VutRYo9miVvNx7qurC [N/A] - 211051.00": 1.59,
  "ybp7dgG47SXPou2Lruxu1RRtV5v9ZkuAB1 [N/A] - 387274.00": 2.92,
  "yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW [N/A] - 63873.00": 0.48,
  "yjYjk8edWJLX1Rubu3CtYFJjETJuB65gDk [N/A] - 365706.00": 2.76
}

Changing the nickname
cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": false,
  "Error": "Sorry, NickName is already taken."
}
Good. duplicate names are prevented.

[email protected]:~$ cli exec cpk "onco12&23\45" true
{
  "Command": "cpk",
  "Results": true
}

Let's see how it takes characters in nickname

So I checked on this one, and everything is fine - here is the reason:  Your nick (oncoapop) (plus the new suffix) is part of the CPK record (and has been updated).

The prominence report pulls the state of our campaign miners as of the Last superblock through Last Superblock minus 205 blocks (IE that is the window that will be Paid next).  The issue is the current 'exec prominence' didnt pick up Oncoapop yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4 GSC Transmission yet (you might be in exec prominence under another key though).

So another words, if Oncoapop made a GSC transmission after block 2890, you will see yourself in prominence after that superblock is paid (IE after block 3095 is paid, you should see Oncoa in *that* prominence).



Next, I only found one bug in Smart-Contract server today, and I just fixed it and it requires an upgrade (in todays build).

So I think everyone can hold off now til this is built (unless you are testing other parts of Evo, or the proposals entry and voting).


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 27, 2019, 02:06:22 pm
1.4.0.3-TestNet Mandatory Upgrade

- Show GSC Transmission icon on txlist
- Fix bug preventing GSC contract from being auto-created and auto-voted
- Fix bug showing StatusBar warning for Sanc-Version-mismatch
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 27, 2019, 02:09:25 pm
Ok, I just realized you were testing this from the Pool.

(You dont have to test the pool, as I know that part works - although yes we should test Evo against the pool a little later for sanity sake but I dont have the pool daemon pointed to Evo yet).

But yeah I would like to test Adding a proposal through the QT wallet, and voting on a proposal.

(I added a couple to the qt wallet and was able to vote on them but more eyes are better).

Sorry, was not familiar with that procedure. Thank you for clarifying. I fired up the biblepay-qt on the VPS using X-windows (didn't know I could do it! so glad I tried - learnt something new!).

I also voted for the first and against the second proposal using the GUI and made a third proposal:

Successfully Prepared Proposal 2aa3b879374e76c41da4ce90371a61250dea8aa56207bb60ff225fd05b08b520.   NOTE: You must wait 6 confirms for the proposal to be submitted.  Please check back on this page periodically to ensure a successful transmission and that no error message is listed in the bottom area of the page.  Thank you for using the BiblePay Governance System.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 27, 2019, 02:16:03 pm
Sorry, was not familiar with that procedure. Thank you for clarifying. I fired up the biblepay-qt on the VPS using X-windows (didn't know I could do it! so glad I tried - learnt something new!).

I also voted for the first and against the second proposal using the GUI and made a third proposal:

Successfully Prepared Proposal 2aa3b879374e76c41da4ce90371a61250dea8aa56207bb60ff225fd05b08b520.   NOTE: You must wait 6 confirms for the proposal to be submitted.  Please check back on this page periodically to ensure a successful transmission and that no error message is listed in the bottom area of the page.  Thank you for using the BiblePay Governance System.

Sweet! I'm upgrading all of mine now, will look.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: thesnat21 on March 27, 2019, 03:03:36 pm
1.4.0.3-TestNet Mandatory Upgrade

- Show GSC Transmission icon on txlist
- Fix bug preventing GSC contract from being auto-created and auto-voted
- Fix bug showing StatusBar warning for Sanc-Version-mismatch

It may be annoying but posting the link is helpful if you don't mind :)

Ehh nevermind, it's easy enough on the first post..
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 27, 2019, 03:22:31 pm
It may be annoying but posting the link is helpful if you don't mind :)


Can use the following script, given the frequency of performing upgrades in testnet environment.

#!/bin/bash

cd ~/biblepay-evolution
git pull origin master
cd src
make
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: thesnat21 on March 27, 2019, 03:29:46 pm
Can use the following script, given the frequency of performing upgrades in testnet environment.

#!/bin/bash

cd ~/biblepay-evolution
git pull origin master
cd src
make

I'm runnin on windows so can't do that... could do a batch script i suppose.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 27, 2019, 04:48:16 pm
It may be annoying but posting the link is helpful if you don't mind :)

Ehh nevermind, it's easy enough on the first post..

I just put the link in a bigger font at the beginning of the OP post - I think that might work for everyone , hopefully.  Since we will probably have 30 upgrades.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 27, 2019, 11:18:23 pm
Interesting, this appears to be the anti-botnet feature you implemented, Rob.

Can you kindly explain what is happening? It appears that I staked BBP to mine a block?
So in this example, I staked 30,953 BBP to mine a 10,300 BBP block?

{
    "account": "",
    "address": "ybEzAPVjwGqqDVKHsJZUoDG82jpiGPcKMg",
    "category": "immature",
    "amount": 10299.50936000,
    "vout": 0,
    "confirmations": 1,
    "instantlock": false,
    "generated": true,
    "blockhash": "0dbfcd1587816e0516b8928ca53ca022ce95261be90c3b8a6f65bc3908a9cdf9",
    "blockindex": 0,
    "blocktime": 1553749516,
    "txid": "e69ed826877f71811361a12aef4702f9b3a2ad915caf8caef7c62e9779ffe5d3",
    "walletconflicts": [
    ],
    "time": 1553749516,
    "timereceived": 1553749532
  },
  {
    "account": "CHRISTIAN-PUBLIC-KEY",
    "address": "yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4",
    "category": "receive",
    "amount": 30953.52702350,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 0,
    "confirmations": 1,
    "instantlock": false,
    "Anti-BotNet-Transaction": true,
    "blockhash": "0dbfcd1587816e0516b8928ca53ca022ce95261be90c3b8a6f65bc3908a9cdf9",
    "blockindex": 2,
    "blocktime": 1553749516,
    "txid": "9a5ce7d79cf10d36c232e73fe480b26dc2b69132b50955519eb13ea92fb90679",
    "walletconflicts": [
    ],
    "time": 1553749516,
    "timereceived": 1553749532
  },
  {
    "account": "",
    "address": "yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4",
    "category": "send",
    "amount": -30953.52702350,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 0,
    "fee": -0.00500000,
    "confirmations": 1,
    "instantlock": false,
    "Anti-BotNet-Transaction": true,
    "blockhash": "0dbfcd1587816e0516b8928ca53ca022ce95261be90c3b8a6f65bc3908a9cdf9",
    "blockindex": 2,
    "blocktime": 1553749516,
    "txid": "9a5ce7d79cf10d36c232e73fe480b26dc2b69132b50955519eb13ea92fb90679",
    "walletconflicts": [
    ],
    "time": 1553749516,
    "timereceived": 1553749532,
    "abandoned": false
  }
]
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 28, 2019, 12:31:29 am
Also, someone can test Adding a fake proposal, and once it is in the chain and list, then vote on the proposal.

Proposal appears to be successfully made. If you need me to set up another sanctuary, vote for or else vote against.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on March 28, 2019, 01:20:15 am
just one small bug
the info/staff on this popup windows is not updating acordanly to status bar on the main window.
(https://i.imgur.com/UTAMZTt.png)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: rastiks on March 28, 2019, 03:19:33 am
Hey guys,

I would like to join the testing party as well. Would somebody send me some tBBP?

yTdd2pbWbHTnxjj8iGmRgzHFraQcMDjP2w

Thx
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 07:31:13 am
Hey guys,

I would like to join the testing party as well. Would somebody send me some tBBP?

yTdd2pbWbHTnxjj8iGmRgzHFraQcMDjP2w

Thx

Sent, welcome aboard!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 07:33:14 am
just one small bug
the info/staff on this popup windows is not updating acordanly to status bar on the main window.
(https://i.imgur.com/UTAMZTt.png)

Thats because any block less in duration than 60 mins is "the end" according to our progress bar, but, I believe as soon as the Sanctuary sync process starts, this is cleared, so I think this is not a live bug, but Ill keep an eye on it, thanks.  Im pretty sure Ive seen this but it clears after a couple more mins.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 07:33:49 am
Proposal appears to be successfully made. If you need me to set up another sanctuary, vote for or else vote against.

Thanks a lot, voted on it!

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 07:45:16 am
Interesting, this appears to be the anti-botnet feature you implemented, Rob.

Can you kindly explain what is happening? It appears that I staked BBP to mine a block?
So in this example, I staked 30,953 BBP to mine a 10,300 BBP block?

{
    "account": "",
    "address": "ybEzAPVjwGqqDVKHsJZUoDG82jpiGPcKMg",
    "category": "immature",
    "amount": 10299.50936000,
    "vout": 0,
    "confirmations": 1,
    "instantlock": false,
    "generated": true,
    "blockhash": "0dbfcd1587816e0516b8928ca53ca022ce95261be90c3b8a6f65bc3908a9cdf9",
    "blockindex": 0,
    "blocktime": 1553749516,
    "txid": "e69ed826877f71811361a12aef4702f9b3a2ad915caf8caef7c62e9779ffe5d3",
    "walletconflicts": [
    ],
    "time": 1553749516,
    "timereceived": 1553749532
  },
  {
    "account": "CHRISTIAN-PUBLIC-KEY",
    "address": "yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4",
    "category": "receive",
    "amount": 30953.52702350,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 0,
    "confirmations": 1,
    "instantlock": false,
    "Anti-BotNet-Transaction": true,
    "blockhash": "0dbfcd1587816e0516b8928ca53ca022ce95261be90c3b8a6f65bc3908a9cdf9",
    "blockindex": 2,
    "blocktime": 1553749516,
    "txid": "9a5ce7d79cf10d36c232e73fe480b26dc2b69132b50955519eb13ea92fb90679",
    "walletconflicts": [
    ],
    "time": 1553749516,
    "timereceived": 1553749532
  },
  {
    "account": "",
    "address": "yMjm7qwu2pQ3xRwtxu6qcGrdzdtCTPgcU4",
    "category": "send",
    "amount": -30953.52702350,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 0,
    "fee": -0.00500000,
    "confirmations": 1,
    "instantlock": false,
    "Anti-BotNet-Transaction": true,
    "blockhash": "0dbfcd1587816e0516b8928ca53ca022ce95261be90c3b8a6f65bc3908a9cdf9",
    "blockindex": 2,
    "blocktime": 1553749516,
    "txid": "9a5ce7d79cf10d36c232e73fe480b26dc2b69132b50955519eb13ea92fb90679",
    "walletconflicts": [
    ],
    "time": 1553749516,
    "timereceived": 1553749532,
    "abandoned": false
  }
]

Yes sir exactly, let me try to explain and please let me know if I left anything out.

So now we have ABN mining enabled, and each block requires (about 5005 ABN weight according to getmininginfo).  So no block is accepted in testnet except those over 60 minutes old or those that have the weight.  You can see how much weight yours had by doing : getblock 3109.  It shows: abn-weight : 22500.42.   Thats because the coin amount spent * the age = 22500.42.

Now moving on to the actual transaction, our wallet create an "anti-botnet-transaction" by finding the stake-age, creating the transaction and placing it somewhere in the block (the reason we moved to dynamic block transaction positions, is our wallet now supports chainlocks, and ChainLock might put a transaction in vout[1], so BiblePay made it dynamic).  To find out where it is we have a field called abnlocator, you can find the value by doing a 'getrawtransaction txidvout[0] 1' (for the coinbase transaction) and looking at that transactions output fields, for ablocator, and then get the value and it points to "where" your signed stake is.

As far as the monetary value, the stake was for 30953, but note - all abn transactions are sent to self, so you actually received it all back (IE you spent 30953, received 30953 + the block reward).  (You also keep the tx-fee because the staker is the solver).

We have very high security on this feature also, as evo doesnt ever allow double spends or malleability, we dont allow stakes sourced from stakes, stakes make people lose coin age, we verify the signature, and also, we verify the solver is the one who created it, so in my experience I feel this is a solid feature.

I also love how it will use up the coin-age for a person who has a couple hundred PCs!  That gives more distinct users to biblepay.

We should also thank MIP and give him half of the credit, because although we spoke about this back when we were designing POL, I forgot about it until he reminded me recently.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 07:57:58 am
** GSC Update **

Overall I'm pretty excited that we are making 'normal' progress for the most part.
Good and not-perfect news. 
The good news is block 3095 (our last superblock) was voted on by 3 sancs, so it had 3 votes, and technically it should have emitted, but-- 3095 was a regular block.  Its hard to say exactly why it didnt emit, it could either be not running watchman (doubtful that is the issue), or could be something to do with the height being a daily height, anyway I'll research this in detail now and find out what happened to our payments.  So at this point everyone who was waiting for the daily got skipped and now we are waiting for block 3300 (although we don't want to hold our breath, as the problem now needs solved for 3300 to work).
On the bright side, our blocks become 1 minute blocks after height 3200 so testing should start zipping by faster with faster progress.

According to getgovernanceinfo, we have until height 4305 for our 'monthly' superblock - thats when we see the outcome of our QT proposals.

Ill check into this daily superblock issue now...

Great work everyone!

exec prominence shows 9 users in the leaderboard for height 3300.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 10:13:45 am
So, I see the reason we didn't pay at the last superblock.  I'm going to try to create a release really quick, if we can get a good chunk of us upgraded by block 3300, we have a shot at checking to see if the bug is dead.

Building....

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 11:03:32 am
1.4.0.4-TestNet Mandatory Upgrade

- Enhance ABN mining (allow miner to sleep if block is not late and ABN
is insufficient, ensure all miners wake up when blocks are late)
- Enable daily superblock logic
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 11:46:10 am
Cancel that last post; we are now waiting for block 3505 in a hands-off fashion.

The last superblock was not paid before everyone upgraded, so it was also a regular block.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 12:12:47 pm
Cancel that last post; we are now waiting for block 3505 in a hands-off fashion.

The last superblock was not paid before everyone upgraded, so it was also a regular block.

Ok, I think we did it.  I received a reward for 3505. 
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 12:17:21 pm
I added the BBP reward amount to the prominence rows for the next version.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 03:00:33 pm
1.4.0.4-TestNet Mandatory Upgrade

- Enhance ABN mining (allow miner to sleep if block is not late and ABN
is insufficient, ensure all miners wake up when blocks are late)
- Enable daily superblock logic

As you upgrade each node, please re-sync.  You could be on your own chain (as this was a mandatory) and it was not released with a cutover height.




Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 28, 2019, 03:37:51 pm
As you upgrade each node, please re-sync.  You could be on your own chain (as this was a mandatory) and it was not released with a cutover height.

Kindly confirm if this is also what you are on. The testnet network is really sparse too. Thank you.

[email protected]:~$ block
4111
[email protected]:~$ cli getblockhash 4111
fe1c896a86d64c3986807a33109a73a51a069c96693f9a99af71c41a9d5452bc
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 03:40:34 pm
Kindly confirm if this is also what you are on. The testnet network is really sparse too. Thank you.

[email protected]:~$ block
4111
[email protected]:~$ cli getblockhash 4111
fe1c896a86d64c3986807a33109a73a51a069c96693f9a99af71c41a9d5452bc
Yes, your on it!

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: rastiks on March 28, 2019, 04:03:46 pm
Yes sir exactly, let me try to explain and please let me know if I left anything out.

So now we have ABN mining enabled, and each block requires (about 5005 ABN weight according to getmininginfo).  So no block is accepted in testnet except those over 60 minutes old or those that have the weight.  You can see how much weight yours had by doing : getblock 3109.  It shows: abn-weight : 22500.42.   Thats because the coin amount spent * the age = 22500.42.

Now moving on to the actual transaction, our wallet create an "anti-botnet-transaction" by finding the stake-age, creating the transaction and placing it somewhere in the block (the reason we moved to dynamic block transaction positions, is our wallet now supports chainlocks, and ChainLock might put a transaction in vout[1], so BiblePay made it dynamic).  To find out where it is we have a field called abnlocator, you can find the value by doing a 'getrawtransaction txidvout[0] 1' (for the coinbase transaction) and looking at that transactions output fields, for ablocator, and then get the value and it points to "where" your signed stake is.

As far as the monetary value, the stake was for 30953, but note - all abn transactions are sent to self, so you actually received it all back (IE you spent  , received 30953 + the block reward).  (You also keep the tx-fee because the staker is the solver).

We have very high security on this feature also, as evo doesnt ever allow double spends or malleability, we dont allow stakes sourced from stakes, stakes make people lose coin age, we verify the signature, and also, we verify the solver is the one who created it, so in my experience I feel this is a solid feature.

I also love how it will use up the coin-age for a person who has a couple hundred PCs!  That gives more distinct users to biblepay.

We should also thank MIP and give him half of the credit, because although we spoke about this back when we were designing POL, I forgot about it until he reminded me recently.

May I have few questions?

1. You say ABN weight is about 5005.  His stake was 30953. Is it because he did not have a coin with lower value?

2. From this it seems beneficiary to have multiple smaller coins, otherwise all larger ones would be spent on mining. Is exec bankroll working in evolution?

3. iI the ABN weight moving automatically or is it a static setting?

4. you wrote "we dont allow stakes sourced from stakes". Does this mean that if a coin is spent on a stake, it cannot be spent on another stake again, even after it ages out?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 05:59:23 pm

May I have few questions?

Please see inline:

1. You say ABN weight is about 5005.  His stake was 30953. Is it because he did not have a coin with lower value?
->  Yes, his lowest coin * age was 30953.  If he had smaller coins it would have used those instead.


2. From this it seems beneficiary to have multiple smaller coins, otherwise all larger ones would be spent on mining. Is exec bankroll working in evolution?
->  Imho, I think in prod, the average coin will be more like 5000 due to the spending and rewards, and requirements so much higher it will always take multiple coins to make a stake --   and in this system, it automatically combines multiple coins to make a stake.  We don't have exec bankroll in evo.  I cant think of a reason we need it (for this use case).  But, we could port it though just to have it so we can consolidate coins easier for people with a lot of change, but even that case is not really going to happen much, since both ABN and GSC-POG makes a lot of consolidated change back to the wallet, so technically in evo, we will have tidy consolidated wallets all the time.

3. iI the ABN weight moving automatically or is it a static setting?
->  Its not completely static.  Its a spork setting.  But, Im thinking in prod it will be more like 100,000 as its most likely best to set it to be a factor of our money supply and the average capital reqd to solve one block per day, for example.   (EDIT: I think it has to be toward the low end closer to 100K so that smaller users can also mine).

4. you wrote "we dont allow stakes sourced from stakes". Does this mean that if a coin is spent on a stake, it cannot be spent on another stake again, even after it ages out?
-> You can re-spend the output of a stake in another block.  I just meant from a security perspective with Evo it wont be possible to do any funny business like that.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 28, 2019, 07:40:04 pm
EDIT:

Ill need to release a mandatory upgrade tomorrow morning to ensure everyone is on the same chain.  We have too many old versions floating around.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: uptimeminer on March 28, 2019, 09:55:00 pm
On TestNet...Can you please send tBBP: ygM8C2FbeMxSCd77TNZNAyTUmym9nwgCFL
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 29, 2019, 07:36:36 am
On TestNet...Can you please send tBBP: ygM8C2FbeMxSCd77TNZNAyTUmym9nwgCFL

Welcome aboard; please hang on.

I noticed last night an unusually high amount of spam in our debug logs.

Let me take care of this spam, the mandatory upgrade version, and anything that looks strange, and then make a release for testnet.

ETA about 3 more hours.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 29, 2019, 07:46:07 am
EDIT:

Ill need to release a mandatory upgrade tomorrow morning to ensure everyone is on the same chain.  We have too many old versions floating around.

Dear Rob,
Thank you for all your hard work that MIP and you and others have put into the development and maintenance. Glad to help and be part of testnet.
Can I make one small suggestion, if I may?  Each time after a Mandatory Update - at least on Testnet where this is so frequent - can you kindly post the latest block and blockhash so that we can all periodically check that we are on the right chain as we may have missed these frequent updates as we were away or something.
That would be greatly appreciated! Thank you.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 29, 2019, 09:34:56 am
Dear Rob,
Thank you for all your hard work that MIP and you and others have put into the development and maintenance. Glad to help and be part of testnet.
Can I make one small suggestion, if I may?  Each time after a Mandatory Update - at least on Testnet where this is so frequent - can you kindly post the latest block and blockhash so that we can all periodically check that we are on the right chain as we may have missed these frequent updates as we were away or something.
That would be greatly appreciated! Thank you.

Yes, will do.  I already realize that this needs done, but what intereferes in testnet, sometimes our testnet chain legally continues after I shut my nodes down.  Meaning that you guys are technically the ones that should post a good hash on the forum once all the nodes resync (as sometimes its out of my control).

But anyhow, in this case, we are making a mandatory that will require us all to delete our cached gov objs, and resync, so I think in this case I will be able to post a good hash after we all upgrade.

Building...
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 29, 2019, 11:30:45 am
1.4.0.5 - TestNet Mandatory Upgrade

- 2 min testnet blocks in testnet after block 5000 (diff was too low for
anti-fork code)
- Remove log spam
- Add GSCTransmission icon to txlist
- Fix getchaintips
- Add end_epoch to GSC Smart contract (prevents a type of validation
error)
- Verify CPK is in good standing before transmitting a GSC transmission
- Correct block subsidy on GSC server side total to account for first
reward
- Disconnect old versions (prior to 1405 in testnet)
- Add feature to logger to prevent duplicate log rows


** Critical instructions for upgrade:  Please clean the blocks data first, then restart the node, and in addition please ensure you delete these governance files:


rm blocks -r
rm chainstate -r
rm evodb -r
rm gov*
rm mnc*
rm mnp*



(One of our superblock calculations was incorrect -- and its cached in our nodes, hence the reason we went off the rails, so now we have to ensure this data is deleted before restarting).

The chain is rolling back to block 3500 or so, will post a hash.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 29, 2019, 11:41:35 am
I'm in agreement on 3 nodes:


getblockhash 3550

c4dafb2ddfa0a3f734fda2049c1a54ad46b4b87d19e0c11ac1d0cca6ac5d3812


Please ensure your sancs have enough collateral (if you started them after 3550) and that you rejoin the pog campaign if you joined after 3550.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 29, 2019, 12:13:11 pm
Also, please re-enter any proposals again.  I re-entered one.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 29, 2019, 12:18:21 pm
On TestNet...Can you please send tBBP: ygM8C2FbeMxSCd77TNZNAyTUmym9nwgCFL

I lost most of my non-sanc funds; sent 125k to start.  Please remind us in another 500 blocks and we can send more.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: rastiks on March 29, 2019, 02:41:06 pm
OK, seems I am back on the correct chain.

How come that I lost most of my tBBP in the meantime ? (over 2 000 000)
I deleted all files except wallet.dat before starting the newest version.

I see many debit transactions like these:

Code: [Select]
{
    "account": "",
    "address": "yPpyP7oXSH4e5jq8kQuCYFdDnDFbX1B7xU",
    "category": "send",
    "amount": -407184.34410700,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 1,
    "fee": -0.00500000,
    "confirmations": 0,
    "instantlock": false,
    "Anti-BotNet-Transaction": true,
    "trusted": false,
    "txid": "a559a4c16f2c1f6a937412620538da1d0cb4f1dd10fddf7d61b432b0c43d500d",
    "walletconflicts": [
    ],
    "time": 1553805526,
    "timereceived": 1553805536,
    "abandoned": false
  },

there are no matching credit transations for those..
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: rastiks on March 29, 2019, 02:53:04 pm
exec prominence shows empty list now for me:

Code: [Select]
biblepay-cli exec prominence
{
}

getblockhash 4109
341d64d1b90f739dd16500834dffea8e6a4cc3bc514a8ebf0f9fd8467c077de1
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 29, 2019, 03:25:26 pm
exec prominence shows empty list now for me:

Code: [Select]
biblepay-cli exec prominence
{
}

getblockhash 4109
341d64d1b90f739dd16500834dffea8e6a4cc3bc514a8ebf0f9fd8467c077de1

Yeah, this is because most of our testnet members lost most of their coin-age, and their miner has not sent a new GSC transmission since, so therefore that particular superblock was empty.  I just set the spork to make our gsc transmissions more frequent for now (once an hour) - but this requires you to reboot the wallet.

(Next version has a command to send a GSC manually also btw).

So far it looks like we are staying in sync now.

Btw your hash matches.  I did receive a payment in the first superblock, and like everyone else waiting for the next GSC transmission.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 29, 2019, 03:27:37 pm
OK, seems I am back on the correct chain.

How come that I lost most of my tBBP in the meantime ? (over 2 000 000)
I deleted all files except wallet.dat before starting the newest version.

I see many debit transactions like these:

Code: [Select]
{
    "account": "",
    "address": "yPpyP7oXSH4e5jq8kQuCYFdDnDFbX1B7xU",
    "category": "send",
    "amount": -407184.34410700,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 1,
    "fee": -0.00500000,
    "confirmations": 0,
    "instantlock": false,
    "Anti-BotNet-Transaction": true,
    "trusted": false,
    "txid": "a559a4c16f2c1f6a937412620538da1d0cb4f1dd10fddf7d61b432b0c43d500d",
    "walletconflicts": [
    ],
    "time": 1553805526,
    "timereceived": 1553805536,
    "abandoned": false
  },

there are no matching credit transations for those..

We rolled back 24 hours primarily because I found that the first superblock created had a piece of bad business logic for the first amount, so I moved back to before that first superblock.

Your wallet probably has some orphaned debits, just restart with:
-zapwallettxes=1

And they should then be free.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: rastiks on March 29, 2019, 03:39:02 pm
We rolled back 24 hours primarily because I found that the first superblock created had a piece of bad business logic for the first amount, so I moved back to before that first superblock.

Your wallet probably has some orphaned debits, just restart with:
-zapwallettxes=1

And they should then be free.

right, -zapwallettxes=1 helped, thanks!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: uptimeminer on March 29, 2019, 04:14:55 pm

Quote
I lost most of my non-sanc funds; sent 125k to start.  Please remind us in another 500 blocks and we can send more.


Thanks Rob... Got the TestNet payment...Looks like I will have plenty tBBP from mining payments..

getblockhash 4316 - d111449fa5aa59f9c042eab06cfdb053f2e5703ca0ea38db70cb2cb3910ed362

 ...Look ok?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 29, 2019, 04:18:43 pm

Thanks Rob... Got the TestNet payment...Looks like I will have plenty tBBP from mining payments..

getblockhash 4316 - d111449fa5aa59f9c042eab06cfdb053f2e5703ca0ea38db70cb2cb3910ed362

 ...Look ok?
Yes, perfect.    If you need any more I have more now, please dont hesitate to ask.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 29, 2019, 04:46:54 pm
I wanted to clarify one nice thing about ABN, as I think we have people under the 'perception' that ABN uses up all your coin-age and you can't participate in a GSC campaign (like POG) because you now lack coin-age.

This is primarily not true - first of all ABN only uses up coin-age if you solve a block.  So it stifles the success of a bot-net miner by using up coin-age *as* they solve blocks.

For a normal miner, who isn't actually solving many blocks, the coin-age is not spent (as we only add it to the block once and it is freed after each block ticks by), so another words, the average user will be able to participate in GSC's with almost full coin-age. 


On a side note, I've disabled most of our features temporarily while we test proposals, GSCs, GSC transmission and payments.
We can then isolate some of our other features and test them in distinct phases.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 29, 2019, 08:42:13 pm
We were doing great til about block 5000, cat debug.log | grep bits

Something went wrong with DGW.   Will check in the morning...

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 30, 2019, 07:01:03 am
We were doing great til about block 5000, cat debug.log | grep bits

Something went wrong with DGW.   Will check in the morning...

So just to explain whats going on over here, I believe DGW is not a cause but an effect.  It looks like the problem started at block 4940 (that is the forkpoint).
Basically, we had 3 sancs online (I think all 3 were mine at the time as it was early in the game). 

Sanc #1 had 8 triggers in memory for block 4940 (this was a gsc superblock), and 7 of them had some type of epoch time issue - (that is problem #1; first of all we need to fix this problem - I do have a log of this issue so I will fix this first, meaning the IsSuperblockTriggered will not complain about the event_block_height not matching the start_epoch blockStart).

Next problem, our minimum vote quorum level is 20% net yes in testnet, but this is only .60 in testnet with 3 sancs (we do have a floor of 2 for Creation, but not for Superblock Triggering) another words, this needs beefed up and standardized so that both creation requires a better minimum and also triggering matches the same number (it does not match).  In prod this wont be a problem because we will be dealing with a much bigger number, like 80 sanctuaries for example.  So I will move the floor to 3 in testnet, and standardize the agreement on the trigger also - this would have prevented Sanc #1 from actually emitting the superblock.

As far as the fork itself, Sanc #1 emitted the superblock, the others rejected it -  (I can see from sanc #2s log at 4940 that it says, Superblock Not triggered - normal block) (This is where things get bad), so basically half of the network accepted the superblock, and this forked the chain at 4940, the other 2 sancs banned my sanc, and split the network.

Im also going to move sanc #1 to the cloud so as to standardize the connectivity (as I see a strange DNS problem on sanc #1 also).

As you can see I have a lot of work to do, so it is no longer necessary to continue testing until we have another release.
Thanks for everyones help so far.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 30, 2019, 11:54:30 am
I'll post again when the next version is ready.  I'm going to attempt to test the first superblock alone to make sure everything is sane.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 30, 2019, 05:44:25 pm
I'll post again when the next version is ready.  I'm going to attempt to test the first superblock alone to make sure everything is sane.

So, I don't want to release an official testnet release until this superblock issue is tested, but I will release an alpha tonight for the brave users.

Anyone who feels like jumping in early can upgrade (after I post the release version in about 30 mins), testing is purely to help us reach block 5000.
If everything goes well we can stay on the chain.

NOTE:  It is Extremely important to follow these directions before you upgrade:

cd testnet3
rm blocks -r
rm chainstate -r
rm evodb -r
rm mnc*
rm mnp*
rm gov*
cd ../SAN
rm pra* <-- Extremely important, you must remove the prayers file, as it contains cached campaign data that must be removed for testing to be successful
optional: rm testnet wallet.dat (this will just clean up the txlist and make it a smaller file.)

In this version, we needed to reset the chain again, primarily because of a change I made to DGW for testnet (to clean it up while our engine is on the floor).
So this means we also have to re-create our sancs.

I've recreated 3 new sancs in the cloud this time for more reliability, and we are synced up to block 2266 so far.

Linux users, you can get the latest now if you want, or wait until the alpha test is finished.

Remember we also must recreate our CPK (exec cpk nickname), and (exec join pog).





Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 30, 2019, 06:04:54 pm
1.4.0.6b-TestNet Mandatory Upgrade

- Remove log spam
- Standardize minimum quorum level for both creating and emitting GSC
superblocks
- Require the minimum quorum in IsSuperblockTriggered for GSCs
- Change DGW for testnet to be more straightforward
- Fix bug in getchaintips where it does not show correct branch length
- Allow miner to know if ABN weight is sufficient when abn is off
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 30, 2019, 11:27:58 pm
So, I don't want to release an official testnet release until this superblock issue is tested, but I will release an alpha tonight for the brave users.

Anyone who feels like jumping in early can upgrade (after I post the release version in about 30 mins), testing is purely to help us reach block 5000.
If everything goes well we can stay on the chain.

NOTE:  It is Extremely important to follow these directions before you upgrade:

cd testnet3
rm blocks -r
rm chainstate -r
rm evodb -r
rm mnc*
rm mnp*
rm gov*
cd ../SAN
rm pra* <-- Extremely important, you must remove the prayers file, as it contains cached campaign data that must be removed for testing to be successful
optional: rm testnet wallet.dat (this will just clean up the txlist and make it a smaller file.)

In this version, we needed to reset the chain again, primarily because of a change I made to DGW for testnet (to clean it up while our engine is on the floor).
So this means we also have to re-create our sancs.

I've recreated 3 new sancs in the cloud this time for more reliability, and we are synced up to block 2266 so far.

Linux users, you can get the latest now if you want, or wait until the alpha test is finished.

Remember we also must recreate our CPK (exec cpk nickname), and (exec join pog).

If you send some tBBP, I can set up a sanc, if needed. or else, will just roll in testnet with zero.
yMSnfBPVTqdstm2grmztDxmxqkLdPzJCJG

Thanks!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on March 30, 2019, 11:32:05 pm
If you send some tBBP, I can set up a sanc, if needed. or else, will just roll in testnet with zero.
yMSnfBPVTqdstm2grmztDxmxqkLdPzJCJG

Thanks!

oh, that's strange, I got block reward without even staking (I have zero in the wallet).

should be on the same chain as I can see your 3 sancs

getblockhash 4297
7b8125733561d649d5a89694dc8e0f7509abae344e7a4da9b5a233911b04bc30
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 31, 2019, 06:28:28 am
If you send some tBBP, I can set up a sanc, if needed. or else, will just roll in testnet with zero.
yMSnfBPVTqdstm2grmztDxmxqkLdPzJCJG

Thanks!

Thanks!  Sent in 2Tx.

On a side note, so far things are looking good (knock on wood).

We made it through the first superblock, all nodes are in agreement, all 3 sancs are up and none are banned, the network did not split, and we are 50 blocks in towards the next superblock.

I see a couple (very minor things that we can fix) on a side note, I see that none of my nodes have been sending gsc updates (this would be a good time for us to go over the rules and the overrides anyway), so Im not sure if Ill be in the next superblock but we have 150 more blocks to make attempts to enter it.

The other thing is its pretty obvious that its hard to get good reporting at this stage, so I need to look into making a better report to see whats happened over the last few superblocks.

So far its probably safer for more to come onboard, but lets see what happens.

One other bug I noticed:  I can see in the 'exec datalist cpk' list, that the CPKs do have nicknames (I see uptime, randrews, etc), but in exec prominence there are no nicknames.  Ill be sure we fix that again.

Edit:
 
To be more specific on an emergency wishlist:
- 1. Add the nickname to exec prominence and exec getcampaigns
- 2. Add a parameter to exec prominence to show the contents of the *next* superblock (maybe this should be the default).  Right now the default is to show the contents of the *last* superblock.  (This would allow us to see changes that are occurring, for example, if you sent a second gsc update in one day, your total points and payments would increase in the dynamic report).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 31, 2019, 06:34:08 am
oh, that's strange, I got block reward without even staking (I have zero in the wallet).

should be on the same chain as I can see your 3 sancs

getblockhash 4297
7b8125733561d649d5a89694dc8e0f7509abae344e7a4da9b5a233911b04bc30

Btw, you can create a sanc if you want (you might want to wait 150 blocks to see if our next superblock passes through gracefully), but either way, its up to you.


Let me look into your block reward.

Btw you can also type 'getblock 4297' in biblepay.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 31, 2019, 06:59:59 am
Btw, you can create a sanc if you want (you might want to wait 150 blocks to see if our next superblock passes through gracefully), but either way, its up to you.


Let me look into your block reward.

Btw you can also type 'getblock 4297' in biblepay.

So just on a side note, the last superblock was @ 5350 and I believe there were 2 GSC payments in there, and they occur once every 205 blocks- so this height is just a normal height.

This 10.5k payment is just a normal mining payment.  Btw, you as the miner will get the entire reward if the sancs didnt vote more than the threshhold for another sanc (IE you claim the mining + the sanc reward in that case).

So yeah we need to get some GSC transmissions out within 100 blocks and see if we can be in the next superblock.

To manually send one type:  exec sendgscc

If it does not appear, most likely it has to do with the internal timer, I will go over that asap.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 31, 2019, 07:24:55 am
So on the failed client-side GSC transmissions, if your node didn't send one, you can look in your log and grep for
CreateGSCTransmission::Fail

Most likely the reason is:  Too many transactions for fee policy; this means that since we did all mining up to this point our wallets have so many small rewards, the gsc transmission (50% of the transactions) would be bigger than 10K (the default max size).  On this note, I will increase this to 100K for the next version.

In the mean time what you can do to get around this problem is enable coin control, go to coin control, send yourself 50-100 of the transactions back to yourself to consolidate the wallet.  Then do the 'exec gscc'.

I will also bubble the GSCC error up to the UI for the 'exec gscc' in case this happens after we raise the tx limit.

So now I just consolidated my coins and my gscc went out. 


Now we are waiting for 50 more blocks for the next superblock.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 31, 2019, 08:35:10 am
1.4.0.6b-TestNet Mandatory Upgrade

- Remove log spam
- Standardize minimum quorum level for both creating and emitting GSC
superblocks
- Require the minimum quorum in IsSuperblockTriggered for GSCs
- Change DGW for testnet to be more straightforward
- Fix bug in getchaintips where it does not show correct branch length
- Allow miner to know if ABN weight is sufficient when abn is off

It looks like things are working!

Feel free to upgrade.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 31, 2019, 08:38:26 am
I've got to head out to church but if anyone is having problems sending a gscc, in addition to the coin-age advice above (which works alone) but this is for convenience, you can optionally add this to your config file:

campaignname_coinagepercentage=.001-.999

This is the coin age percentage the client side uses to select coins.  If you have too many coins, you could for example do:
pog_coinagepercentage=.005

And it would theoretically use .005% of your coins (meaning you dont need to consolidate them in coin control) and they would eventually auto consolidate.
Then you can increase the percentage later.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 31, 2019, 02:37:02 pm
This is the hash Im seeing currently guys:

15:36:49

getblockhash 6100


15:36:49

97f052dc466dbfca07b386618aea0c9d70dccd15b974890d929f0420b1c6c60d


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: rastiks on March 31, 2019, 02:42:15 pm
This is the hash Im seeing currently guys:

15:36:49

getblockhash 6100


15:36:49

97f052dc466dbfca07b386618aea0c9d70dccd15b974890d929f0420b1c6c60d

I'm on it
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: rastiks on March 31, 2019, 02:52:34 pm
BTW, I can create a sanctuary as well, need 1 000 000 more tBBP:

yTdd2pbWbHTnxjj8iGmRgzHFraQcMDjP2w
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 31, 2019, 03:00:42 pm
BTW, I can create a sanctuary as well, need 1 000 000 more tBBP:

yTdd2pbWbHTnxjj8iGmRgzHFraQcMDjP2w
Sure, that will help stabilize things.  Sent.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 31, 2019, 03:35:27 pm
Ok all, we are doing really good, but we need an update.

There is a missing rule on the sanc side, and I feel that if we don't stop now we may go out of sync without the rule.  The chain is good, but please stop testing.

I have a nice punchlist of things we need to add anyway.

Please hang on for the next version.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 31, 2019, 09:08:27 pm
1.4.0.7-TestNet Mandatory Upgrade

- Add 'select some' feature to coin control to help people consolidate
wallets (this selects 20% of the list)
- Add 'exec bankroll' rpc feature - this allows people to consolidate
coins into bigger notes
- Added business logic to prevent generation of bad gsc superblocks
- Added checkpoint
- Allow forcing a gsc client transmission (exec sendgscc)
- Widen Amount in Send money UI page
- Add nickname to exec prominence, Add ability to run prominence from
prior heights, future or last superblock (exec prominence last | future
| height); default is future
- Add nickname to exec getcampaigns
- Raise absurdly high fee 100* higher (this is about 1 bbp compared to
.001 bbp) as the fee was too low to send a 100 output transaction from
coin control in the past
- Increment version for prior incompatibility
- Remove Log Spam


** I believe the Sanctuaries will need to:
rm evodb -r
rm chainstate -r
rm blocks -r
resync
** 
(The regular nodes are most likely OK).  We need to ensure we are all in sync after restarting.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on March 31, 2019, 10:27:00 pm
Hash:




23:33:59

getblockhash 6450


23:33:59

640b069e1e802d1ae8ab2a632674b9617055974bc41e21391e30f05054a0eecf

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 01, 2019, 07:11:15 am
Now that things are stabilizing, does anyone have any questions about what we are actually doing with GSCs or how the transmissions or rewards are structured?

Basically, since testnet has 2 minute blocks, the daily contract zips by much quicker (IE about 3.25 hours for each day zipping by).

So the idea is, once per day, the participant of a campaign will receive a "Smart contract reward"  (You should see this in your transaction list).  (Btw, I recommend testing in QT for a while until all of our bugs are worked out, as you can see the labels and things and double click on the transaction etc).

Currently, the miner is set to send a "GSC Transmission" once an hour (this could be more like once per 12 hours in Prod, to prevent spam).
The GSC transmission contains the Stake that your node will send for the first campaign (the only active campaign: POG).

So in theory, if we hone in on one smart contract day, we should see 3 transmissions, and one payment.

We should double click on the 3 transmissions and check how much coin-age we sent, and then reconcile this to the points and the reward in the following superblock reward.


EDIT: In the next version we will have a command to audit the points per tx.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 01, 2019, 01:27:31 pm
** New version coming in one hour **

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 01, 2019, 03:20:03 pm
1.4.0.8-TestNet Mandatory Upgrade

- Add Watchman On the Wall (BiblePay version)
- Modify Sanctuary IsSuperblockValid trigger rule to trigger when
fCachedFunding is set
- Add rpc command 'getpogpoints' (this shows the pog points for a
transaction)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on April 01, 2019, 08:19:07 pm
1.4.0.8-TestNet Mandatory Upgrade

- Add Watchman On the Wall (BiblePay version)
- Modify Sanctuary IsSuperblockValid trigger rule to trigger when
fCachedFunding is set
- Add rpc command 'getpogpoints' (this shows the pog points for a
transaction)

Sorry but I am unable to start watchman. can you please advise?

-342: non-JSON HTTP response with '401 Unauthorized' from server
Cannot connect to biblepayd. Please ensure biblepayd is running and the JSONRPC port is open to watchman.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 02, 2019, 08:50:11 am
Sorry but I am unable to start watchman. can you please advise?

-342: non-JSON HTTP response with '401 Unauthorized' from server
Cannot connect to biblepayd. Please ensure biblepayd is running and the JSONRPC port is open to watchman.
Sorry for providing too little information about the Watchman environment; let me try to explain.

In Prod, we are running a 1.5 year old codebase with Dashs Sentinel in Python (we renamed it Watchman-on-the-wall) - and we still use it in prod as-is from Dash (and its still required today since it helps create the budgets etc, creates watchdogs, etc).

In Evo, I have not ported Sentinel to Watchman yet (so its unavailable still), so we do not have to Test it yet.

What I'm considering however, is porting Watchman to c++, so we don't have to run both watchman and Evo as separate programs in each sanc (in the future).  (Thats what this release info was about, but - its really just in step 1).  I'm still going to do some internal testing on my end, then provide more info as how we can test the integrated version of watchman, so please don't worry about testing that yet.




Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 02, 2019, 09:30:08 am
** Update **

So for the last few re-releases the common theme has been:
- No signs of a problem with abn weight, or gsc client side transactions, or creation of the pog points
- No signs of problems with actual POBH heat mining (IE no forks resulting from POW)
- No signs of problems on the *monthly* superblock budget system or its creation of budget data

- Every re-release so far and enhancement resulted from a problem related to the Daily superblock contract
 (not a problem with the actual contract, a problem with the sancs not *finding* the contract, some find it, some lose it)

So I've been trying to hone in on this for the last 2 days - because at first I believed running only 3 sancs meant that one sanc out of 3 was not syncing properly- so we added rules to strengthen the minimum requirements of the voting required for a superblock to pass.  Yesterday however, all 3 sancs could see the votes on the superblock (we had 4), but only 2 of them had the actual gobject in memory (that is obviously a problem).

Let me explain this a different way, so we can all understand how a soft consensus can still fork the chain in testnet.
Sanc #1 and Sanc #2 had the gobject in memory (this is the GSC contract with its payments and addresses).  Sanc 1,2,and 3 had the *vote* for the gobject in memory and they all agreed the superblock was good and should pass.

Here is what happened on block 6990:

Sanc #1 found both the gobject and the trigger votes, and it said:  Valid, accepted
Sanc #2 found the votes only, and said "valid superblock at this height" but actually rejected the block because:  IsBlockValueValid, too few superblock payments <-- this is because it was missing the gobject with the hex data

So lets see what happens; Sanc #2 goes on its own chain now, Sanc 1 and 3 continue on the chain with the higher work.  This actually splits the testnet network because now Sanctuary votes for 1 cause (mnpayments to decrease), IE do to our mnpayments relying on chainheights- this becomes a hard split - and in a small
 testnet network we cant have this, so therefore we have to fix the root of the problem.

This ends up causing a hard fork, because #2 will never re-correct its view of this block until completely resynced as it has now marked the block as a fail.

First, lets stop testing again until I can release a plan to fix this.
(It does not appear to be watchman).
It appears to be more of a timing issue.  In Dash, the gobjects are synced over a longer time span (as we normally have a month to get all the data for the monthly votes), but in our case, we are trying to sync (with 2 minute blocks) all the superblock data within 190 blocks (IE < 3 hours)-- so I can see if one sanc misses a gobject, its going to make a bad call on the next superblock.

So, my plan is this next:
1. I will investigate all code that syncs gobjects, and see if we are lacking something (Ie timing issues) and beef this up
2. I will do something special to allow us to Monitor the next daily gsc superblock, like a command line that will alert us that a node is going to make a bad call on the next block
3. We will make the sanc go out of its way to Pull the data it needs to make a good call on the block manually

Then we regroup here and do an in-depth analysis on the actual superblock heights as they are about to tick by and post something on the forum to see what the state of each one is as they occur. 

Please hang on for the next version, it might take a day, it might take less depending on how complex the timing issue is.




Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 02, 2019, 01:39:01 pm
1.4.0.9-TestNet Mandatory Upgrade

- Remove more log spam
- Add 'exec health'; we use this to check the health of the next GSC
superblock manually
- Make the Sanc quorum relay the crown jewel once every 9 blocks
- Make the Sanc or the non-sanc detect an unhealthy GSC condition, and
Reset resyncing gov objs
- Prevent d-dossing other sancs for having a bad previous block header
- Lengthen gobject deletion time by 1 day
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 02, 2019, 03:15:05 pm

16:14:22

exec health


16:14:22

{
  "Command": "health",
  "govobjhash": "0000000000000000000000000000000000000000000000000000000000000000",
  "Amounts": "",
  "Addresses": "",
  "votes": 0,
  "required_votes": 3,
  "last_superblock": 8835,
  "next_superblock": 9040,
  "next_superblock_triggered": false,
  "Healthy": false,
  "GSC_Voted_In": false
}


16:14:24

getblockhash 9000


16:14:24

eca1364b2b58b06d07aaad98685382b1e67b3a053a3db26c77bfddd61042fdd8


If all goes well, we will all go to "healthy".

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 02, 2019, 04:08:27 pm
1.4.0.9b-TestNet Mandatory Upgrade

- Remove more log spam
- Add 'exec health'; we use this to check the health of the next GSC
superblock manually
- Make the Sanc quorum relay the crown jewel once every 9 blocks
- Make the Sanc or the non-sanc detect an unhealthy GSC condition, and
Reset resyncing gov objs
- Prevent d-dossing other sancs for having a bad previous block header
- Lengthen gobject deletion time by 1 day


** All, please ensure you upgrade again to the newest version **
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 02, 2019, 04:41:38 pm
Ok I went to healthy on all my nodes, lets hope you all see the same.

'exec health'

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: uptimeminer on April 02, 2019, 10:32:52 pm
Switched to healthy=true on my node..

Quote
"Command": "health",
  "govobjhash": "a2ce1dd9f8fcb55ed32d62b3a071338928dc85f812f207ae918e04c38d49b4e1",
  "Amounts": "594237.00|299260.00|359384.00",
  "Addresses": "yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8|yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe|ygavD5YuAJXpHDMLRyiiJ199YM5y9fTWfB",
  "votes": 3,
  "required_votes": 3,
  "last_superblock": 9040,
  "next_superblock": 9245,
  "next_superblock_triggered": false,
  "Healthy": true,
  "GSC_Voted_In": true
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 03, 2019, 05:30:45 am
Switched to healthy=true on my node..
Yes, thank God we finally made it through the entire night and all the superblocks passed all the rules this time (we had about 4 so far I think).


getblockhash 10120

e13331a79a04776297f1ef66634525bb3d16aca8c9ff8d61a5be21f2c5202caf

I can see we are all still in sync also.  I forgot to mention, you can see by the difficulty that the chain is solid now as it jumped up to 1.4 (from .10 when we had the issues).


Great, now I can take a look at the proposal rules for the monthlies and see if we can expose the height, and test watchman. 


I'm going to be explaining a (what I consider to be) novel use of our new campaigns later today.

We can discuss bearing fruit in Jesus Name with Healing campaigns and spiritual warfare in Evo. 

I'm thinking we can add a CPK startup wizard, with the ability to read an instruction PDF, join a campaign that requires directions (as spiritual warfare for instance is dangerous if a person does not know what they are doing), and once they join, we also need the ability for a user to type in a days activity back into BiblePay.    This would allow the campaign to keep a diary of what the user is doing for the points (for these specific campaigns).



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 03, 2019, 08:37:33 am
I've got a fun project coming up for us. 

So basically, here are the requirements for Watchman On The Wall we need to fulfill for replacement of The Sentinel, and be the first coin with our own integrated Watchman (not requiring python):

- Nodes get banned and not paid if they are not running watchman (this prevents people from running sancs that do not help vote on the budget)
- Nodes do not get voted on for a sanc payment if they are down (IE watchdog expired)
- Nodes who do run watchman can create a budget, sort it by votes, exclude proposals that pay dont fit, and vote on the proposal automatically during the warning period

We've got the first two covered (Watchman will automatically run in our sancs in c++, sancs will only vote on sancs who are Up (as we do test for that already), and we already have a spork for payment enforcement), and by the end of our testing, we will ensure Sanc don't expire prematurely--  so in light of all this, all that is left (the elephant in the room), is to test Watchman Budgeting.

In light of that, I am now modifying Watchman to handle budgets.  Where you all will come in to help, is we need to create about 10 *new* proposals (as the old ones are bad) -- for the next superblock (see 'getgovernanceinfo' to see the next budget is at height 11480, with getsuperblockbudget 11480 = 4.1MM bbp).

What we need to do in the future is : Verify proposals that missed a prior superblock deadline are no longer in the proposals list (this is broken currently), that future unpaid proposals are in the proposals list, and that watchman picks up these for budgeting, and sorts them by votes descending, and also excludes items that dont fit the cap.

What I want to do is have us all vote on these, and ensure the ones with low votes are not included and those that are too high for the budget cap are excluded automatically.

The current version *is* capable of taking new proposal now - for block 11480, so please, start now by creating 5-7 new proposals (please only create One at a time and then ensure the block has passed before creading another one).  I think if each of you create 2-3 that is sufficient.

Ill create a few myself now.

After the next release, the bugs above will be fixed and then we can test a watchman dry run at a height of 10% before block 11480 (that is the warning period) (IE 115 blocks early).



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on April 03, 2019, 01:17:01 pm
** Update **

So for the last few re-releases the common theme has been:
- No signs of a problem with abn weight, or gsc client side transactions, or creation of the pog points
- No signs of problems with actual POBH heat mining (IE no forks resulting from POW)
- No signs of problems on the *monthly* superblock budget system or its creation of budget data

- Every re-release so far and enhancement resulted from a problem related to the Daily superblock contract
 (not a problem with the actual contract, a problem with the sancs not *finding* the contract, some find it, some lose it)

So I've been trying to hone in on this for the last 2 days - because at first I believed running only 3 sancs meant that one sanc out of 3 was not syncing properly- so we added rules to strengthen the minimum requirements of the voting required for a superblock to pass.  Yesterday however, all 3 sancs could see the votes on the superblock (we had 4), but only 2 of them had the actual gobject in memory (that is obviously a problem).

Let me explain this a different way, so we can all understand how a soft consensus can still fork the chain in testnet.
Sanc #1 and Sanc #2 had the gobject in memory (this is the GSC contract with its payments and addresses).  Sanc 1,2,and 3 had the *vote* for the gobject in memory and they all agreed the superblock was good and should pass.

Here is what happened on block 6990:

Sanc #1 found both the gobject and the trigger votes, and it said:  Valid, accepted
Sanc #2 found the votes only, and said "valid superblock at this height" but actually rejected the block because:  IsBlockValueValid, too few superblock payments <-- this is because it was missing the gobject with the hex data

So lets see what happens; Sanc #2 goes on its own chain now, Sanc 1 and 3 continue on the chain with the higher work.  This actually splits the testnet network because now Sanctuary votes for 1 cause (mnpayments to decrease), IE do to our mnpayments relying on chainheights- this becomes a hard split - and in a small
 testnet network we cant have this, so therefore we have to fix the root of the problem.

This ends up causing a hard fork, because #2 will never re-correct its view of this block until completely resynced as it has now marked the block as a fail.

First, lets stop testing again until I can release a plan to fix this.
(It does not appear to be watchman).
It appears to be more of a timing issue.  In Dash, the gobjects are synced over a longer time span (as we normally have a month to get all the data for the monthly votes), but in our case, we are trying to sync (with 2 minute blocks) all the superblock data within 190 blocks (IE < 3 hours)-- so I can see if one sanc misses a gobject, its going to make a bad call on the next superblock.

So, my plan is this next:
1. I will investigate all code that syncs gobjects, and see if we are lacking something (Ie timing issues) and beef this up
2. I will do something special to allow us to Monitor the next daily gsc superblock, like a command line that will alert us that a node is going to make a bad call on the next block
3. We will make the sanc go out of its way to Pull the data it needs to make a good call on the block manually

Then we regroup here and do an in-depth analysis on the actual superblock heights as they are about to tick by and post something on the forum to see what the state of each one is as they occur. 

Please hang on for the next version, it might take a day, it might take less depending on how complex the timing issue is.

I appear to be on the correct chain by as far as I can tell (checking manually), I have not seen my sanc (the 4th) vote for any superblock. Does this have to be done manually?

[email protected]:~/Sanctuary$ cli getblockhash 10120
e13331a79a04776297f1ef66634525bb3d16aca8c9ff8d61a5be21f2c5202caf
[email protected]:~/Sanctuary$ cli exec health
{
  "Command": "health",
  "govobjhash": "9ff38ea222d3bb56085b2c696a10ddf02d16548cdb23beec3db828ae5ed8b929",
  "Amounts": "736194.00|180067.00|173696.00|101790.00|23491.00|37641.00",
  "Addresses": "yR26BVwFeGTnkgdfw1RRNgVF2LyPnrZqaT|yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8|yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|ygavD5YuAJXpHDMLRyiiJ199YM5y9fTWfB|yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "votes": 2,
  "required_votes": 3,
  "last_superblock": 10680,
  "next_superblock": 10885,
  "next_superblock_triggered": true,
  "Healthy": true,
  "GSC_Voted_In": false
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 03, 2019, 01:58:18 pm
I appear to be on the correct chain by as far as I can tell (checking manually), I have not seen my sanc (the 4th) vote for any superblock. Does this have to be done manually?

[email protected]:~/Sanctuary$ cli getblockhash 10120
e13331a79a04776297f1ef66634525bb3d16aca8c9ff8d61a5be21f2c5202caf
[email protected]:~/Sanctuary$ cli exec health
{
  "Command": "health",
  "govobjhash": "9ff38ea222d3bb56085b2c696a10ddf02d16548cdb23beec3db828ae5ed8b929",
  "Amounts": "736194.00|180067.00|173696.00|101790.00|23491.00|37641.00",
  "Addresses": "yR26BVwFeGTnkgdfw1RRNgVF2LyPnrZqaT|yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8|yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|ygavD5YuAJXpHDMLRyiiJ199YM5y9fTWfB|yiWrpMBA8YXfVmxntAgZZ1dh18ueaBerbW",
  "votes": 2,
  "required_votes": 3,
  "last_superblock": 10680,
  "next_superblock": 10885,
  "next_superblock_triggered": true,
  "Healthy": true,
  "GSC_Voted_In": false
}

I think things are OK on the back end, but we might need another field - but first whats your sanc Ip, I can check some things to make sure I see your vote?

Btw, no - you should not have to vote manually, this is all automatic.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on April 03, 2019, 02:14:44 pm
I think things are OK on the back end, but we might need another field - but first whats your sanc Ip, I can check some things to make sure I see your vote?

Btw, no - you should not have to vote manually, this is all automatic.

Thanks.

[email protected]:~$ ifconfig
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 45.62.239.200  netmask 255.255.255.0  broadcast 45.62.239.255
        inet6 fe80::250:56ff:fe95:4682  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:95:46:82  txqueuelen 1000  (Ethernet)
        RX packets 600708  bytes 190734759 (190.7 MB)
        RX errors 0  dropped 276  overruns 0  frame 0
        TX packets 530771  bytes 225023604 (225.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 03, 2019, 02:35:48 pm
Thanks.

[email protected]:~$ ifconfig
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 45.62.239.200  netmask 255.255.255.0  broadcast 45.62.239.255
        inet6 fe80::250:56ff:fe95:4682  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:95:46:82  txqueuelen 1000  (Ethernet)
        RX packets 600708  bytes 190734759 (190.7 MB)
        RX errors 0  dropped 276  overruns 0  frame 0
        TX packets 530771  bytes 225023604 (225.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


Yes, I see you as the 4th enabled sanc, great.

So trying to track this down took me longer than when it actually passed, so I found that it would be useful for us to have a couple more features.
1- The ability to see that the exec testgscvote is actually picking the most popular contract; right now I see 2 in there and it appears to be voting on the right one, but we cant really see it from the rpc
2- A way to filter the gobject get with a wildcard. 

Let me enhance the next version then we can test another one.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 03, 2019, 05:19:07 pm
1.4.1.0-Leisure Upgrade for TestNet

- Add cascading GSC superblock creation (this decreases the propensity
for duplicate GSCs)
- Add intelligent GSC voting system (this means we vote yes on the
lowest PAM hashes and vote no on the highest PAM hashes)
- Add Watchman on the Wall budgeting
- Add 'gobject listwild all type wildcard' - This allows us to search
objects or proposals or gscs or triggers by wild card.  You can also
search by gov plain text data or by hash.
- Add getgschashes - This gives us a list of current gsc hashes for the
next superblock and pertinent data for each hash
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 04, 2019, 12:37:02 am
very time the new wallet version is out, my wallet forked. I figured out, if I all of the sudden have several millions of tbbp than new version is out.  :o
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 04, 2019, 08:19:47 am
So I have all the logs and I can see exactly what happened.
So we made it further this time, we passed through a couple days worth of superblocks without problems.
The problem is still with the GSC superblock (again), this time at height 11,500 it was rejected - half of the network accepted it and the other half rejected it causing a split at 11,501 and this is the reason half of our sancs now show Expired (they are on the wrong chain).

On the bright side, watchman-on-the-wall actually worked already and paid the proper amounts in the last monthly superblock and Im very happy about that.  Even though no one entered the proposals that we needed to test the overages - I had enough in there to at least test one overage (I had the block overpaid by 50K and it did successfully pick the first 3 highest voted that fit).

So looking at the root cause as to why two of my nodes rejected the block, I can see clearly that a non-sanctuary thought it was completely synced with the Sanc network (this has nothing to do with the chain sync, just the gobject sync) but in reality it did Not have the information it needed to make a good call. 

In light of this, what I plan on doing next is tackling this another way.

Please halt testing until the next version.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 04, 2019, 01:17:47 pm
1.4.1.2b-TestNet Mandatory Upgrade

- Refine GSC Voter
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: uptimeminer on April 04, 2019, 09:24:32 pm
Hi Rob...How can I verify what version I am on Win32 wallet (testnet)...Help->About says 1.4.0.9 last couple of updates...
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 04, 2019, 09:28:59 pm
Hi Rob...How can I verify what version I am on Win32 wallet (testnet)...Help->About says 1.4.0.9 last couple of updates...

Hmmm, it appears the link changed.

Please see the OP post now (edited).

Thanks!

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on April 05, 2019, 02:04:37 am
1.4.1.2b-TestNet Mandatory Upgrade

- Refine GSC Voter

Ready for MacOS

Regarding Ubuntu PPAs, I still have to figure out how to compile Chia-BLS and Relic into PPAs themselves, then add them as an internal dependency... not an easy task at the moment, will report any progress.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 05, 2019, 07:19:48 am
Hey All,

I'm reviewing the logs and have discovered something critical that we need.

This is excellent because it explains why we had so many problems originally coming to a consensus, and I knew something had to be missing for the nodes to behave this way (IE share only half of their gobjects then create their own).

There is a setting missing that is causing a rate overflow when we share data. 

I will look into fixing this today.

(http://pool.biblepay.org/images/bulb.png)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 05, 2019, 10:38:13 am
So as a sneak preview as to what we are trying to accomplish in Evo with campaigns, one of the themes I'm going to introduce in the next Evo nutritional information guide is "BiblePay - Bearing Fruits".

This quantifiable measurement of Bearing Fruit can potentially be accomplished by fostering user activity that bear fruit, such as Healing on the street, Spiritual Warfare campaigns, spreading the gospel, reading the bible, etc. 

It will be a long discussion to find a way to "prove" that one actually bears fruit, but in this next revision, what we will do is place the lions share of the payment weight on hard-consensus rules (IE possibly 90% of the reward % goes toward things like stake-weight or foundation donations) but the remaining percent may possible be voted to go towards bearing fruit another way - healing on the streets, keeping a diary of entries, promising in a contract that a CPK is doing what a CPK claims, and reputation scores.  (Towards the end of the year, users who are caught lying or seem to be anti-Christ can be voted down by others and this will ruin their reputation scores, so the non-hard-consensus earnings get to be more accurate).

To test this out as a guinea pig in Evo, Im going to create a Healing campaign.
(This will also allow us to test multiple campaign payment mix percentages at once- allocation to Healing, and allocation to POG) - since we will have 2 campaigns.  I think in testnet we will make POG 95% and Healing 5% (to satisfy the non-provable component).

In essence Healing is when a person goes out on the street and prays for a total strangers illness or medical condition.  They keep a diary of the persons name and the outcome (and if a video is possible they make a video).

Later in the night the person must type this into biblepay in the diary area of the campaign (only if they are member of Healing).  The system will store this in the blockchain as a GSC-Healing-Transmission with a certain % of stakeweight attached and the Diary note.

This campaign for example might be 5% of the daily rewards.  The user with a diary entry receives a future slice of the daily payment for that particular campaign.

I have reached out to Torben Sondergaard to try to Partner with TLR (The Last Reformation).  He has responded to me (Im actually a street healer already, and Ive been through the kickstart and go out weekly and pray on the streets etc -- and Ive seen miracles occur -- regulary now).  I am waiting to find if Torben will allow us to partner with him.  If so we will make this relationship much more professional.  Otherwise, we can ask him for permission to use "Like TLR" for our brand of healing.  If that fails, we can discuss making our own campaign.

Once this is released Ill explain how to test this.

We should have phase 1 ready today.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 05, 2019, 01:05:14 pm
1.4.1.3-Mandatory Upgrade for TestNet

- Remove more log spam
- Add Anti-GPU function phase 1 (not enabled yet)
- Increase GSC sharing capability (increase gov rate limits)
- Enhance exec prominence to show point details by campaign, then totals
per user
- Add ability for Sancs to calculate points from multiple campaigns
- Add configurable tithe and coin-age per campaign per user setting
(with spork defaults)


* Ill post more on how to test the Healing campaign *

Regarding our gobject syncing, we should see a more consistent exec health report in 50 blocks or so if we are successful in fixing the issue.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 05, 2019, 01:11:31 pm
I just want to mention, this is our first release with a soft-consensus change to the Sanc side, meaning this exercises our ability to release a point-calculation change to the payment algorithm without breaking the prod chain.

So in this case exec health will be wrong until over 51% upgrade to the new version (this is because the contract creator changed, so as sancs upgrade, the actual contents of the contract will change).

Once we get the upgrades, the exec health warning will dissapear.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 05, 2019, 01:17:14 pm
So from a very high level, the plan for the Healing campaign is to create a workflow, where the user  :  Joins, accepts critical documents and signs off, makes diary entries, sends healing transmission records, and then receives payments.

The flow will most likely be like this:  User types 'exec join HEALING', BiblePay sends them a URL with a PDF (explaining what they are getting into), User authorizes acceptance of the terms, User is now enrolled,  User sends a diary entry each time they heal by going to Send Money, typing it in the Diary text memo box, click the Diary checkbox, Select the Campaign Name (Healing), Click Send, .01 BBP is sent out (with a Healing stake in the transmission), the user can read the diary by double clicking on the txlist-tx.  On the server side, we assess the diary text entry as a valid source of Points.


In this rudimentary version today, all we have is the campaign, and a generic stake transmission for healing.

To get started please do this:

exec join HEALING

<BiblePay says true>

exec sendgscc true
(This is force)

Wait for next superblock - check exec prominence - see if we receive revenue from Healing.

Tomorrow I will work on the Diary entries.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 05, 2019, 01:26:57 pm
Another side project:

Please refer to the prior post about entering watchman-on-the-wall proposals.
Id like to perform a more elaborate test (one with at least 10 proposals).
Lets wait until block 14350 (the monthly superblock) passes before we start.
Lets add some complicated figures that total more than 4.5 mm biblepay, and lets stress test watchman for the following monthly governance superblock.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 05, 2019, 01:57:27 pm
I cant  see what is in Proposals tab anymore.
(https://i.imgur.com/LlVV42j.png)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 05, 2019, 02:25:51 pm
I cant  see what is in Proposals tab anymore.
(https://i.imgur.com/LlVV42j.png)

Thats because they are all paid.

Proposals tab shows Active proposals.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 05, 2019, 02:29:36 pm
One piece of info guys and crypto-gals:

When we have multiple campaigns, exec prominence will show percentages in the detail section that total to that campaigns Percent of the global total, so let me give an example:
We have 5% of our GSC budget set up for HEALING
We have 95% set up for POG currently

The participants in HEALING will total 5% in exec prominence details.  The participants in POG will total 95% in details.

The "Totals" section however will just be points, prominence % (of global), and grand total.


Next, since we require coin-age as a gsc-heal-transmission there really is technically no exploit for bad behavior currently, but it will still be nice to have reputation scores eventually.  Either way we will have the diary very soon.  We can use the diary in the spiritual-warfare campaign also, that will be nice.





Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 05, 2019, 03:32:14 pm
Ready for MacOS

Regarding Ubuntu PPAs, I still have to figure out how to compile Chia-BLS and Relic into PPAs themselves, then add them as an internal dependency... not an easy task at the moment, will report any progress.

Thanks!  If you have a link for me to put on the OP post I will.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 05, 2019, 09:45:04 pm
So far, its purring like a kitten...

It looks like we smashed the bug.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on April 06, 2019, 12:02:24 am
Good job so far. I have a question:

1/3 sancs that I have reports a different health output:

 "votes": 1,
  "required_votes": 3,
  "last_superblock": 14985,
  "next_superblock": 15190,
  "next_superblock_triggered": true,
  "Healthy": true,
  "GSC_Voted_In": false
mastenode outputs
{
  "626a61b0dfa151374bb42f1c432853efacb1742292318f9389c121f51b3310e4": "1"
}

-------------------------
2/3 report this:
  "votes": 5,
  "required_votes": 3,
  "last_superblock": 14985,
  "next_superblock": 15190,
  "next_superblock_triggered": true,
  "Healthy": true,
  "GSC_Voted_In": true

Is that normal behaviour?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 06, 2019, 06:48:18 am
Good job so far. I have a question:

1/3 sancs that I have reports a different health output:
Code: [Select]
"votes": 1,
  "required_votes": 3,
  "last_superblock": 14985,
  "next_superblock": 15190,
  "next_superblock_triggered": true,
  "Healthy": true,
  "GSC_Voted_In": [b]false[/b]
mastenode outputs
{
  "626a61b0dfa151374bb42f1c432853efacb1742292318f9389c121f51b3310e4": "1"
}

-------------------------
2/3 report this:
  "votes": 5,
  "required_votes": 3,
  "last_superblock": 14985,
  "next_superblock": 15190,
  "next_superblock_triggered": true,
  "Healthy": true,
  "GSC_Voted_In": true
Is that normal behaviour?



Thanks for the testing, so let me explain a little more about health, this is a relatively long explanation :) but Ill try to make it succinct.

So the fact that we see "1" positive vote on your first node, the answer from a high level is, Its "probably OK", but we should do a little more investigation to try to find out whats going on.

On a side note, the underlying goverance-obj hash, that is the native Dash hash for the object, but the PAM hash is the hash of the payments and addresses in the GSC contract. 

The node will be able to recover by the time the superblock hits using various methods, it will attempt to sync (mnsync status, govobjs) first, then it will attempt to unpack the gsc contract manually (this is since it actually runs the same code as the server side), and finally before it fails it will still follow normal superblock rules (IE mark the block as good if its a node thats out of sync), but its still worth going a little further with this one, to see if we have any gov-obj data sync errors.

So lets try to isolate the missing govobj hash.
If you run 'exec health' you will see the height is 15805 (for the next superblock).
Then go to a healthy node and type 'gobject listwild all triggers 15805' and you should see one or more contract triggers (preferably one).
Then copy the governance-object hash (this is the very first hash on the page) to notepad.
Then cat.debug.log | grep hash  in your node that only has one vote.  And see if an error occurred in syncing that hash (it might say something like Exception: failed to sync governance-object nnnnnn) but not exactly this wording.

If we can find that exception, then I can track down why that node did not fully sync.  Also let us know if it recovered.
And also if 'mnsync status' shows that the node is out of sync (IE the row that reads 'IsSynced').  If that failed, the node didn't get all of its gobjects.

Another possibility is being on testnet, we have 4 enabled sancs, and 4 down, it could be that node is still trying to iterate through to the enabled nodes.

I think during testing if we are still having gobject sync problems they will most likely reveal themselves as a lot of data will be passing back and forth.

Right now all 4 of mine are in sync, with exec health true and 4 votes, but I will check my logs to see if any sync errors have been flying around through the night.

(I know we need to shorten the delete duration of gobjects in the next release, this will cut some of this spam and chattiness down also).









Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 06, 2019, 11:31:03 am
So I thought of another feature we could use in testnet: the ability to see total outbound tithes, outbound coin-age, and inbound-revenue over a superblock period.  And make exec prominence show your user information as a total (so you dont have to look through the list).

Any other requests in that vein?

This would theoretically show the user the summary that they need per day and reveal the ROI and totals that they used for the staking component.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 06, 2019, 12:04:21 pm
We still need help entering more proposals, please enter some.

Next superblock @ 17220.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 06, 2019, 05:08:10 pm
We still need help entering more proposals, please enter some.

Next superblock @ 17220.

Still no proposals, I've entered about 5, could use more.  Also, I need help voting on these!  Please go to proposals in the QT wallet and vote on them also, thanks.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 07, 2019, 11:33:06 am
When or how Sanctuarie gets Enabled? I made it few days ago, but still I hopw to start is every couple of hours and then it recive PRE Enabled status.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 07, 2019, 12:10:17 pm
When or how Sanctuarie gets Enabled? I made it few days ago, but still I hopw to start is every couple of hours and then it recive PRE Enabled status.

From what I started seeing a couple days ago, I think everything has been purring like a kitten now (knock on wood, praise Jesus).

I honestly believe that you are potentially having a problem related to being on a prior versions fork.
Because ever since I reindexed at block 10,500 I have not had one single problem with my 3 sancs (IE they went to enabled and never died again), I dont have to restart them.

Could you please try deleting your mncache.dat, banlist.dat, mnp*.* and gov*.dat, and resyncing from 0, (delete evodb -r and chainstate and blocks), then after the 'mnsync status' shows 999, then do a start on the sanc, and let me know if it ever goes from ENABLED back to anything else (as I highly do want to know feedback in this area, because we are replacing watchman-on-the-wall and I feel we can add value to the blockchain by having our own brand in this area, this way we can be valuable).

Thanks...

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 07, 2019, 12:12:31 pm
Just to give an update on watchman @ 16625, this is the last superblock, we were successful:
gobject listwild all triggers 16625
Everything was paid properly, and Im extemrely happy about that.

I see you guys have started entering new proposals also, thanks.  We will test those on the next superblock.

Congrats!

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 07, 2019, 12:13:25 pm
When or how Sanctuarie gets Enabled? I made it few days ago, but still I hopw to start is every couple of hours and then it recive PRE Enabled status.

I forgot to ask, is your sanc on a cloud hosted provider with public IP?  It will also fail if its not on a public IP.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 07, 2019, 01:03:13 pm
ok, will try to re-sync.
no could, it's on privat sever. I have been running couple of masternodes in the past.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 07, 2019, 01:23:10 pm
ok, will try to re-sync.
no could, it's on privat sever. I have been running couple of masternodes in the past.
After you resync could you please give your ip?  Ill try to connect to you from here.
EDIT:  Also, you may need to set this in your config if you run from home:
externalip=my_ipv4_address:40001

Thats the testnet port.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 07, 2019, 02:34:33 pm
aha, I didnt have this externalip=my_ipv4_address:40001
and I enter different port 19999. its (213.250.22.35)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on April 07, 2019, 02:40:54 pm
Hi guys,

If I find some spare time in the coming week, I will read through all the documentation and fire up a testnet rig  :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 07, 2019, 07:38:55 pm
aha, I didnt have this externalip=my_ipv4_address:40001
and I enter different port 19999. its (213.250.22.35)

Good point, I will fix that 19999 typo now in the Evo source.

Hey - I cant connect to you (telnet 213.250.22.35 40001).  You also must port forward 40001 to your biblepay host IP in your router.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 07, 2019, 07:41:05 pm
Hi guys,

If I find some spare time in the coming week, I will read through all the documentation and fire up a testnet rig  :)

Thanks, that would be awesome!

The diary feature should be out within the next 2 days.

So far we've only tested legacy sanctuaries, GSC creation and emission, watchman, and proposals, but I expect testing to go much smoother now that we are over the very large hump (the gsc data-health test).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 08, 2019, 12:04:13 pm
Hi all,
after few weeks I'm back :) and I wanted to start testing, but I don't know how :D
I've read GSC wiki page, this thread, but I don't know how to join POG.
I've made "exec cpk orbis", "exec join pog" and I have confirmation tx's in my wallet (on April 3rd).
But after mining for few days, I haven't any POG reward or any POG tx (GSC transmission) from my wallet.
My biblepay.conf has "pog_coinagepercentage=.50 pog_foundationdonation=1000" but still nothing.
I see myself in "exec getcampaigns" but not in "exec prominence".

Is there any command to make GSC transmission manually?
I've found "exec sendgscc" but after it nothing happens ("results": 1 but without GSC tx).
I've tried to join to HEALING 20 blocks ago so I'll see the result with this. For now it was with ""Results": true".
I'm running on WIN10, 1143 version, encrypted wallet.
May be that problem, that I run my wallet locked? Is it needed to have wallet unlocked like in POG, PODC? If yes, it would be nice to have "password popup" on start and "-headlesspodcpassword" on linux.
I dont have MN for now, but after MN consolidation I won't have MN in prod too, so I take testing of this on you :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 08, 2019, 12:16:42 pm
Hi all,
after few weeks I'm back :) and I wanted to start testing, but I don't know how :D
I've read GSC wiki page, this thread, but I don't know how to join POG.
I've made "exec cpk orbis", "exec join pog" and I have confirmation tx's in my wallet (on April 3rd).
But after mining for few days, I haven't any POG reward or any POG tx (GSC transmission) from my wallet.
My biblepay.conf has "pog_coinagepercentage=.50 pog_foundationdonation=1000" but still nothing.
I see myself in "exec getcampaigns" but not in "exec prominence".

Is there any command to make GSC transmission manually?
I've found "exec sendgscc" but after it nothing happens ("results": 1 but without GSC tx).
I've tried to join to HEALING 20 blocks ago so I'll see the result with this. For now it was with ""Results": true".
I'm running on WIN10, 1143 version, encrypted wallet.
May be that problem, that I run my wallet locked? Is it needed to have wallet unlocked like in POG, PODC? If yes, it would be nice to have "password popup" on start and "-headlesspodcpassword" on linux.
I dont have MN for now, but after MN consolidation I won't have MN in prod too, so I take testing of this on you :)

Glad to see you here Orbis!

So lets deal with POG first and Healing a little later today as that is more minor (and waiting for the diary anyway).

So yes you do need to have a CPK and be joined to POG, but you already did the 'exec cpk orbis' , and you did the exec join pog, and I do confirm: I see you in exec getcampaigns.


Most likely there is an error in your exec sendgscc.  Once you resolve this the miner will become automatic again.
Please grep your log for this:
Created client side transmission

It probably has an error behind it.

To resolve the error, I think all you have to do is consolidate some of your coins (to have less than would result in a 100,000 byte GSCC transaction).
You can either manually consolidate (we have a new button in QT called 'check some' ) or you can do the 'exec bankroll' feature.

Then once consolidated, try the 'exec sendgscc true' again and confirm no error is in the log?

PS I don't see a gscc tx from you - you are not in exec prominence

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 08, 2019, 01:06:12 pm
Many of my greps are similiar like this:
Code: [Select]
2019-04-08 14:25:53
SmartContract-Client::Creating Client side transaction for campaign POG
Created client side transmission -  [Sorry, wallet must be unlocked.] with txid 0000000000000000000000000000000000000000000000000000000000000000 UpdateTip: new best=4dad01934762a84a41b2290711372190258a7339f4d6eb4be4a203e6b1838a9c height=18471 version=0x20000001 log2_work=42.10664032 tx=41984 date='2019-04-07
So it looks, that wallet must be unlocked.
Now I have it unlocked, and after  'exec sendgscc true' it was successful and I have 2x GSC-Transmission tx :)
I don't know why it was not successful before (I've tried it with unlocked wallet too)
So, will be there "password popup" on start and "-headlesspodcpassword" on linux?
BTW, I've made bankroll and I'm waiting for confirmations, but I didn't found 'check some' button. Where is it?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 08, 2019, 01:52:14 pm
Good point, I will fix that 19999 typo now in the Evo source.

Hey - I cant connect to you (telnet 213.250.22.35 40001).  You also must port forward 40001 to your biblepay host IP in your router.
it should be open now. I had some trouble.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 08, 2019, 02:29:02 pm
It looks, that now it is working fine for me and I'll be waiting for automatic GSC tx.
But I have few questions :)
I've read wiki few times, but I didn't understand how (POG) GSC tx exactly works.
Like I said  few times, maybe it's with language barrier, maybe I just don't get it :D
After my 1st successful GSC I've had conf like this:
Code: [Select]
pog_coinagepercentage=.5
pog_foundationdonation=1000
but I saw that my donation was only 7tBBP, like default and I have 2 GSC txs each with around 50k tBBPs spent.
I've changed conf to:
Code: [Select]
pog_coinagepercentage=1
pog_foundationdonation=1000
and tried forced GSC again.
Result was that my donation is still 7 tBBPs and those 2 GSC txs spend each around 145k tBBPs.
So I'm really confused.
Thanks :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 08, 2019, 02:34:33 pm
it should be open now. I had some trouble.

Yes, got it to connect now, you should stay in enabled then - please let us know if it fails.

Good luck.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 08, 2019, 02:48:18 pm
Many of my greps are similiar like this:
Code: [Select]
2019-04-08 14:25:53
SmartContract-Client::Creating Client side transaction for campaign POG
Created client side transmission -  [Sorry, wallet must be unlocked.] with txid 0000000000000000000000000000000000000000000000000000000000000000 UpdateTip: new best=4dad01934762a84a41b2290711372190258a7339f4d6eb4be4a203e6b1838a9c height=18471 version=0x20000001 log2_work=42.10664032 tx=41984 date='2019-04-07
So it looks, that wallet must be unlocked.
Now I have it unlocked, and after  'exec sendgscc true' it was successful and I have 2x GSC-Transmission tx :)
I don't know why it was not successful before (I've tried it with unlocked wallet too)
So, will be there "password popup" on start and "-headlesspodcpassword" on linux?
BTW, I've made bankroll and I'm waiting for confirmations, but I didn't found 'check some' button. Where is it?

Something in my gut makes me dislike that pop up-type in password wizard.  (Partially from the boot-up annoyance, partially from the anticipation from security experts that it pops up during boot) -- I feel the security experts may frown on it (even though we store it in a securestring).  So in Evo, I added this:
exec setautounlockpassword password
(as an alternative).  This way, the user must be competent enough to initiate the process to type it in.  So please test that and let me know if it solves the issue?

(On the before:  There was probably a different error in the log, as I did raise the max transaction bytes to 100K during the last release).

We should also bubble up any GSC errors to the user in getmininginfo I suppose.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 08, 2019, 03:09:44 pm
It looks, that now it is working fine for me and I'll be waiting for automatic GSC tx.
But I have few questions :)
I've read wiki few times, but I didn't understand how (POG) GSC tx exactly works.
Like I said  few times, maybe it's with language barrier, maybe I just don't get it :D
After my 1st successful GSC I've had conf like this:
Code: [Select]
pog_coinagepercentage=.5
pog_foundationdonation=1000
but I saw that my donation was only 7tBBP, like default and I have 2 GSC txs each with around 50k tBBPs spent.
I've changed conf to:
Code: [Select]
pog_coinagepercentage=1
pog_foundationdonation=1000
and tried forced GSC again.
Result was that my donation is still 7 tBBPs and those 2 GSC txs spend each around 145k tBBPs.
So I'm really confused.
  • I think that 2 GSC txs are because POG and HEALING. Is that true?
  • Why is my donation only 7 tBBPs?
  • Why there is so huge difference between spended amount? (50k vs 145k is not .5 vs 1)
  • Is the spended amount same as Coin Amount in your POG formula?
  • How it is the spended amount counted? What is it based on?
  • Is it possible to set spended amount to exact number? e.g. 5000
  • How to find expected Coin Amount and Coin Age Days?
Thanks :)

Yeah, lets iron this out.
:

Yes, because the rules vary from campaign to campaign, the wallet will iterate through each enrolled campaign, and send one GSCC transmission individually.  I thought about originally having one big transaction, but for multiple reasons, one individual for each campaign is better (primarily because we might have a stake-interest for example, that requires distinct coins to be staked for the Interest campaign, and distinct Other coins staked for POG for example).  We can label the transaction in the UI "Healing" soon (I just added to my list).

It looks like this is case sensitive (this needs fixed).  For now, please make it :  POG_foundationdonation=nnnn  and it should work.

Its due to the coin*age it found breaching the original coinage percentage setting, as compared to "all your coins" at once.  I'm making a feature now that will shed light on this - please wait for the next versions report and Ill explain how to run this.

On a side note you can type 'exec getpogpoints txid' and it will show you how many points you earned for a gscc transmission.  But, let me see if I can answer this question for you based on a tool.  For now, the high level answer is : If you have .50 coin age percentage selected, the wallet will multiply your CoinAmount*Age(inDays) for each coin in the wallet, and collect half of the coin age out of the wallet in a big transmission, staked to yourself.   Let me know if that part does not answer it.

Hmmm, that would add complexity, then we would need more wallet settings.  I think most people will want to set a Percentage of their wallet coins for a certain project.  We can talk more about this if you can convince me on the usefulness.  Know that Im making a report now that will clearly show the metrics in/out and it might shed light on the mechanics of the ROI for these campaigns.

Expected coin*age:
Go to coin control, take the age in days of a coin, multiply that * the coin amount = coin_age.

How to find "click some" button:
Go to coin control, look for 2nd button on the top left


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 08, 2019, 05:06:04 pm
Thanks Rob.
Now it makes more sense to me :)
I'll be collecting more question for later :D
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 09, 2019, 11:21:35 am
nope,... It is getting EXPIRED again.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 09, 2019, 11:39:55 am
nope,... It is getting EXPIRED again.

Yeah, looking in my sancs logs for your ip 213.250*, I see you are masternode lockpoint 9e54110*, and I do see "Masternode ping is invalid" last night @ 19:53:13 2019-04-08. 

The other sancs will vote you down for payment if they receive bad health pings back over a certain threshhold, and then your node will be required to be restarted. 

It probably has something to do with your LAN consistency - as my sancs haven't been expiring.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 09, 2019, 03:48:52 pm
1.4.1.4-Mandatory Upgrade for TestNet

- Remove debug spam
- Add Quantitative Tightening (with sporks)
- Fix Sanc Port # in Documentation
- Reset govobj deletion delay back to original parameters
- Bubble GSC transmission errors into getmininginfo
- Add Diary Entry to sendcoinsentry UI page
- Add ability to make a Diary entry for campaigns supporting diary
entries
- Add ability to see Diary Entry from the Transaction List double click
- Add ability to send GSC transmission from Send Coins entry UI
- Add QT Level and BBP Price to Overview page, getblock nnnn, exec price
- Change exec getpogpoints to exec getpoints, make getpoints capable of
showing any GSC transmission type tx points
- Modify exec prominence to show personal prominence (exec prominence
true) or all (exec prominence false)
- Modify exec sendgscc to take a diary entry
- Added exec sentgsc report (To see mining expenses, run this, this
breaks down donations, coinage transmissions, and totals).  To see
revenue, run exec prominence true.
- Modified campaigns that take diaries to reward 0 without diary entry
- Added exec price (this shows the current BBP price, BTC price, and QT
level)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 09, 2019, 03:49:20 pm
I'll explain some of these release notes asap.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 10, 2019, 08:03:47 pm
1.4.1.5-Mandatory Upgrade for TestNet

- Mandatory upgrade before block 25,500 for TestNet
- Add leaderboard UI
- Ensure QT does not turn on until sancs vote on the first future price,
ensure monthly governance budget is based on last months QT level for
planning purposes
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 10, 2019, 09:02:37 pm
This is just a personal observation about the Healing campaign - and overall fairness.  However I do feel strongly about the benefit we can achieve by bearing quantifiable fruit in Jesus name (IE rewarding people for physical actions).

I realize that it would be unfair to single out 'healing campaigns' as 5% of the total GSC budget, so I think what we can do is change the Healing campaign to be a more general category for the total budget allocated to campaigns that require a diary entry.

So, what I plan on doing is creating a few PDFs with instructions, one for spiritual warfare, one for healing/driving out demons, one for spreading the gospel, and one for praying for others.  And what we do is ask the user to follow the PDF (or all the PDFs) before engaging in any of the activities requiring a diary entry.

In the end, anyone enrolled in 'healing' can then enter a diary entry for :
- Conducting spiritual warfare
- Healing/Driving out demons (healing is pray for a persons health affliction and commanding the affliction out)
- Witnessing out in public (spreading the gospel)
- Praying for loved ones/prayer list (prayer closet)

All of these things bear fruit, but the idea is to summarize the daily activity that made a difference into a diary entry once per day and enter it - regardless of the actual category above (later we can add the sub categories).  This will share the 5% among everyone with an active diary entry for the day.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 10, 2019, 09:10:22 pm
1.4.1.4-Mandatory Upgrade for TestNet

- Bubble GSC transmission errors into getmininginfo
- Add Diary Entry to sendcoinsentry UI page
- Add ability to make a Diary entry for campaigns supporting diary
entries
- Add ability to see Diary Entry from the Transaction List double click
- Change exec getpogpoints to exec getpoints, make getpoints capable of
showing any GSC transmission type tx points
- Modify exec prominence to show personal prominence (exec prominence
true) or all (exec prominence false)
- Added exec sentgsc report (To see mining expenses, run this, this
breaks down donations, coinage transmissions, and totals).  To see
revenue, run exec prominence true.
- Added exec price (this shows the current BBP price, BTC price, and QT
level)

1) We now bubble GSC errors into getmininginfo.  That should take care of the problem Orbis had.

2) To see your total outbound GSCTs sent in the last 205 blocks, just type : exec sentgsc

3) You can type 'exec getpoints txid' to see the point calculation for a sent-gsc-tx

4) You can compare exec sentgsc (as your mining expense) to exec prominence true (as your revenue).  Exec prominence true shows only your details.

5) You can now see the Leaderboard UI totals by clicking the Leaderboard menu.  (QT).

6) To enter a diary entry (for one of the bearing fruit records), (first be sure you have joined Healing with exec join healing), then go to Send Money, click Diary Entry.  Type the diary entry. 

7) At 25,500 we can test QT (Quant-tightening).  I am deliberately testing things in layers.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 11, 2019, 08:14:25 am
6) is it working? because it doesnt make a transaction. -diary entry
If you check "Donate to fundation" is the same address and it make a transaction.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 11, 2019, 09:04:22 am
I think we are on this blockhash :

09:03:54

getblockhash 25354


09:03:54

72887c9dec86fe2cc3c97ef7caa3691505c81adbb021af177fd34088c72fdbfd

(Some nodes got banned as we upgraded etc).

Diff = .41

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 11, 2019, 09:05:44 am
6) is it working? because it doesnt make a transaction. -diary entry
If you check "Donate to fundation" is the same address and it make a transaction.

Yes.

Please post the error you get, as we bubble the error to the screen in QT (are you using QT)?
If no error on the screen its also written to the log.

EDIT: Also, please post the diary entry here, so I can reproduce.  It must be > 10 chars in length to be valid.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 11, 2019, 12:04:02 pm
Nothing happens, well no error, it just clear everything out.
I am using QT, desktop version. Unless I am doing smth wrong.

Quote
2019-04-11 16:59:19 WalletModel::CreateDiaryEntry::Creating diary entry ... DIARY ENTRY : HELLO WORLD OF BIBLE Received a GET request for / from 202.97.251.157:46264
2019-04-11 16:59:33 ProcessMessages(version, 109 bytes) FAILED peer=8360
2019-04-11 16:59:39 CMasternodeSync::NotifyHeaderTip -- pindexNew->nHeight: 25553 fInitialDownload=0
2019-04-11 16:59:39 UpdateTip: new best=0368d885bd5aa5517ede5ff01bf470a270ad63e79df5154f3e2d39cb960e744a height=25553 version=0x20000001 log2_work=44.48151079 tx=81668 date='2019-04-11 16:59:28' progress=0.999999 cache=0.0MiB(0txo)
2019-04-11 16:59:39 {PNB}: ACC 
block rejected.CreateNewBlock() packages: 0.00ms (0 packages, 0 updated descendants), validity: 0.00ms (total 0.00ms)
2019-04-11 16:59:41  ABN OK: 1.000000 CreateNewBlock() packages: 0.00ms (0 packages, 0 updated descendants), validity: 0.00ms (total 0.00ms)
2019-04-11 16:59:44  ABN OK: 1.000000 CMasternodeMan::CheckAndRemove -- mMnbRecoveryGoodReplies size=0
2019-04-11 16:59:46 CreateNewBlock() packages: 0.00ms (0 packages, 0 updated descendants), validity: 0.00ms (total 0.00ms)
2019-04-11 16:59:46  ABN OK: 1.000000

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 11, 2019, 01:02:01 pm
Nothing happens, well no error, it just clear everything out.
I am using QT, desktop version. Unless I am doing smth wrong.

I have a different hash for 25553.  I am pretty sure some nodes banned each other (due to the mandatory), could you please rm chainstate -r rm evodb -r rm blocks -r rm banlist.dat, and resync and see if your hash matches the one from a few blocks earlier - then please retry the tx? 

Then also see if you can scrape the txid out of the transaction double click, and also, it should have the diary entry at the very end of the window.

I think we are on this blockhash :

09:03:54

getblockhash 25354


09:03:54

72887c9dec86fe2cc3c97ef7caa3691505c81adbb021af177fd34088c72fdbfd
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 11, 2019, 01:17:33 pm
this one is the sameon my side :

20:16:32

getblockhash 25354


20:16:32

72887c9dec86fe2cc3c97ef7caa3691505c81adbb021af177fd34088c72fdbfd
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 11, 2019, 01:21:13 pm
this one is the sameon my side :

20:16:32

getblockhash 25354


20:16:32

72887c9dec86fe2cc3c97ef7caa3691505c81adbb021af177fd34088c72fdbfd


But when you pasted your log it shows a bad hash here:

2019-04-11 16:59:39 UpdateTip: new best=0368d885bd5aa5517ede5ff01bf470a270ad63e79df5154f3e2d39cb960e744a height=25553 version=0x20000001 log2_work=44.48151079 tx=81668 date='2019-04-11 1

Did you resync just now?


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 11, 2019, 01:55:38 pm
We will have to be a little patient as we have most likely Slovakia playing games - the diff is 20 now in prod and chain is reorging. 

Im sure it has nothing to do with Evo or the latest version, because the mandatory height hasn't hit yet.

I see we rolled back when this person who tithes 666.66 hit us with big hash.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on April 11, 2019, 02:12:24 pm
Seems that all my sanc are went out of sync and are unable to sync up to that block. Stuck at 23234 when I initially got one sanc to sync with your 3 even after resync.

isn’t the ABN feature supposed to prevent these sorts of attacks? Please help me understand in layperson terms what is happening and how did that bypass ABN?

Thank you.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 11, 2019, 02:18:33 pm
Seems that all my sanc are went out of sync and are unable to sync up to that block. Stuck at 23234 when I initially got one sanc to sync with your 3 even after resync.

isn’t the ABN feature supposed to prevent these sorts of attacks? Please help me understand in layperson terms what is happening and how did that bypass ABN?

Thank you.

1) We had synced from 23234 up to about 23336 but with a difficulty of .10 (IE very low).
The wallet will reorganize back to 23234 if it finds a chain with greater total chain work (which is possible since 23234 had a diff of 20.)

(As long as the re-org block is valid).

2) ABN tries to prevent single rich kiddies (IE someone who has 20 servers) from solving an inordinate amount of blocks personally.  It does this by using up their coin-age.  But in testnet this 20 diff could come from a few high powered machines, although more likely 4-5 miners running full speed right up to that block (so you are correct abn might have helped, but in testnet everyone has a lot of coin age also).

2a.  We actually don't have ABN turned on right now :), I disabled it so we can test one feature at a time.  I planned on enabling qt next then abn later, but now we have to figure out this sync problem first.

3.  I am also rolled back to 23234 right now, so you are experiencing the same thing as me (another words the hash I posted is no longer valid).

Ill do some poking around.  We probably need to turn up our miners to more threads to solve the next block.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on April 11, 2019, 02:46:49 pm
1) We had synced from 23234 up to about 23336 but with a difficulty of .10 (IE very low).
The wallet will reorganize back to 23234 if it finds a chain with greater total chain work (which is possible since 23234 had a diff of 20.)

(As long as the re-org block is valid).

2) ABN tries to prevent single rich kiddies (IE someone who has 20 servers) from solving an inordinate amount of blocks personally.  It does this by using up their coin-age.  But in testnet this 20 diff could come from a few high powered machines, although more likely 4-5 miners running full speed right up to that block (so you are correct abn might have helped, but in testnet everyone has a lot of coin age also).

2a.  We actually don't have ABN turned on right now :), I disabled it so we can test one feature at a time.  I planned on enabling qt next then abn later, but now we have to figure out this sync problem first.

3.  I am also rolled back to 23234 right now, so you are experiencing the same thing as me (another words the hash I posted is no longer valid).

Ill do some poking around.  We probably need to turn up our miners to more threads to solve the next block.

Ok thank you for that explanation!  We seem to be moving along.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 11, 2019, 02:50:27 pm
thats why I am stuck at 25237 after re-sync.
 019-04-11 19:45:03 SPORK -- hash: 00f31f1feb64a49df40213e52e3e3ce2191e6f19f6241a1740043f08efdb1ba6 id: 10011 value:          0 bestHeight: 25237 peer=436 seen
2019-04-11 19:45:03 SPORK -- hash: 644278d68318691dc8f02c6f714a12eaf27a63764caf590fc8aaeb6118725051 id: 10090 value:          0 bestHeight: 25237 peer=436 seen
2019-04-11 19:45:27 SPORK -- hash: 0b55391d2c25736279fb64125f046026b833b7021b00cafb296dcd287b72106f id: 10008 value:          0 bestHeight: 25237 peer=5 seen
2019-04-11 19:45:27 SPORK -- hash: 00f31f1feb64a49df40213e52e3e3ce2191e6f19f6241a1740043f08efdb1ba6 id: 10011 value:          0 bestHeight: 25237 peer=5 seen
2019-04-11 19:45:27 SPORK -- hash: 644278d68318691dc8f02c6f714a12eaf27a63764caf590fc8aaeb6118725051 id: 10090 value:          0 bestHeight: 25237 peer=5 seen
2019-04-11 19:45:27 SPORK -- hash: 0b55391d2c25736279fb64125f046026b833b7021b00cafb296dcd287b72106f id: 10008 value:          0 bestHeight: 25237 peer=6 seen
2019-04-11 19:45:27 SPORK -- hash: 00f31f1feb64a49df40213e52e3e3ce2191e6f19f6241a1740043f08efdb1ba6 id: 10011 value:          0 bestHeight: 25237 peer=6 seen
2019-04-11 19:45:27 SPORK -- hash: 644278d68318691dc8f02c6f714a12eaf27a63764caf590fc8aaeb6118725051 id: 10090 value:          0 bestHeight: 25237 peer=6 seen
2019-04-11 19:45:29 ProcessMessages(version, 109 bytes) FAILED peer=558
2019-04-11 19:45:29 ProcessMessages(version, 109 bytes) FAILED peer=559
2019-04-11 19:45:33 ProcessMessages(version, 109 bytes) FAILED peer=561
2019-04-11 19:45:39 ProcessMessages(version, 109 bytes) FAILED peer=562
2019-04-11 19:45:41 ProcessMessages(version, 109 bytes) FAILED peer=563
2019-04-11 19:45:42 ProcessMessages(version, 109 bytes) FAILED peer=564
2019-04-11 19:46:17 ProcessMessages(version, 109 bytes) FAILED peer=565
2019-04-11 19:46:24 ProcessMessages(version, 109 bytes) FAILED peer=566
2019-04-11 19:47:07 ProcessMessages(version, 109 bytes) FAILED peer=568
2019-04-11 19:47:19 ProcessMessages(version, 109 bytes) FAILED peer=569
2019-04-11 19:47:22 ProcessMessages(version, 109 bytes) FAILED peer=570
2019-04-11 19:47:52 ProcessMessages(version, 109 bytes) FAILED peer=571
2019-04-11 19:47:53 ProcessMessages(version, 109 bytes) FAILED peer=572
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 11, 2019, 02:52:58 pm

But when you pasted your log it shows a bad hash here:

2019-04-11 16:59:39 UpdateTip: new best=0368d885bd5aa5517ede5ff01bf470a270ad63e79df5154f3e2d39cb960e744a height=25553 version=0x20000001 log2_work=44.48151079 tx=81668 date='2019-04-11 1

Did you resync just now?

Now I am resyncing.
Did I forked after 25354?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 11, 2019, 03:08:12 pm
thats why I am stuck at 25237 after re-sync.
 019-04-11 19:45:03 SPORK -- hash: 00f31f1feb64a49df40213e52e3e3ce2191e6f19f6241a1740043f08efdb1ba6 id: 10011 value:          0 bestHeight: 25237 peer=436 seen
2019-04-11 19:45:03 SPORK -- hash: 644278d68318691dc8f02c6f714a12eaf27a63764caf590fc8aaeb6118725051 id: 10090 value:          0 bestHeight: 25237 peer=436 seen
2019-04-11 19:45:27 SPORK -- hash: 0b55391d2c25736279fb64125f046026b833b7021b00cafb296dcd287b72106f id: 10008 value:          0 bestHeight: 25237 peer=5 seen
2019-04-11 19:45:27 SPORK -- hash: 00f31f1feb64a49df40213e52e3e3ce2191e6f19f6241a1740043f08efdb1ba6 id: 10011 value:          0 bestHeight: 25237 peer=5 seen
2019-04-11 19:45:27 SPORK -- hash: 644278d68318691dc8f02c6f714a12eaf27a63764caf590fc8aaeb6118725051 id: 10090 value:          0 bestHeight: 25237 peer=5 seen
2019-04-11 19:45:27 SPORK -- hash: 0b55391d2c25736279fb64125f046026b833b7021b00cafb296dcd287b72106f id: 10008 value:          0 bestHeight: 25237 peer=6 seen
2019-04-11 19:45:27 SPORK -- hash: 00f31f1feb64a49df40213e52e3e3ce2191e6f19f6241a1740043f08efdb1ba6 id: 10011 value:          0 bestHeight: 25237 peer=6 seen
2019-04-11 19:45:27 SPORK -- hash: 644278d68318691dc8f02c6f714a12eaf27a63764caf590fc8aaeb6118725051 id: 10090 value:          0 bestHeight: 25237 peer=6 seen
2019-04-11 19:45:29 ProcessMessages(version, 109 bytes) FAILED peer=558
2019-04-11 19:45:29 ProcessMessages(version, 109 bytes) FAILED peer=559
2019-04-11 19:45:33 ProcessMessages(version, 109 bytes) FAILED peer=561
2019-04-11 19:45:39 ProcessMessages(version, 109 bytes) FAILED peer=562
2019-04-11 19:45:41 ProcessMessages(version, 109 bytes) FAILED peer=563
2019-04-11 19:45:42 ProcessMessages(version, 109 bytes) FAILED peer=564
2019-04-11 19:46:17 ProcessMessages(version, 109 bytes) FAILED peer=565
2019-04-11 19:46:24 ProcessMessages(version, 109 bytes) FAILED peer=566
2019-04-11 19:47:07 ProcessMessages(version, 109 bytes) FAILED peer=568
2019-04-11 19:47:19 ProcessMessages(version, 109 bytes) FAILED peer=569
2019-04-11 19:47:22 ProcessMessages(version, 109 bytes) FAILED peer=570
2019-04-11 19:47:52 ProcessMessages(version, 109 bytes) FAILED peer=571
2019-04-11 19:47:53 ProcessMessages(version, 109 bytes) FAILED peer=572

The failed messages just mean we hang up on peers less than our version (they have not upgraded yet).

We solved about 5 more blocks after the 20 diff block, but Im still waiting for warnings to clear.

I think everything is ok, but lets solve a few more and let the warnings clear first then we can try another diary entry.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 12, 2019, 03:33:01 am
emm, I have differnet hash on that block like yesterday-

10:31:55

getblockhash 25354

10:31:55

ce7fbfd5dfbab275f35984dac4b447db7866d1bd38eac7c19010764b1f603085
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 12, 2019, 06:48:56 am
emm, I have differnet hash on that block like yesterday-

10:31:55

getblockhash 25354

10:31:55

ce7fbfd5dfbab275f35984dac4b447db7866d1bd38eac7c19010764b1f603085

Yes, that matches mine, that is normal, we were reorganizing when I posted that hash yesterday and everyone was upgrading.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 12, 2019, 08:53:38 am
1.4.1.6-Mandatory Upgrade for TestNet

- Limit nickname length to 10 characters
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 12, 2019, 08:59:12 am
Btw, our last Monthly governance superblock did pay out the rewards correctly.

I see someone has in an orphan sanctuary proposal, good, please monitor it to make sure it pays (and you receive the payment) when 27265 occurs.
I will enter a few more proposals now, but lets ensure we vote your Orphan Sanc up, and monitor the highest votes descending are included for payment.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 12, 2019, 09:07:14 am
So QT (Quantitative Tightening) has now been turned on in Evo (In testnet only).
We are in Day #1.
Fortunately in testnet, we have the equivalent of 4 superblocks per day, so we should transcend from QT level 1-4 in one day.

Lets keep an eye on the chain, make sure it does not fork (I deliberately have not turned on any other layers yet).
We have a difficulty of 12, that is a good indication the chain is healthy.

Lets keep an eye on our daily superblock budget and our monthly budget also, and see that it remains stable (its now based on *last* months budget - IE 6000 blocks behind where we are now).

To see the qt level, type exec price, or look at the overview page in biblepay-qt.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: thesnat21 on April 12, 2019, 10:09:18 am
1.4.1.6-Mandatory Upgrade for TestNet

- Limit nickname length to 10 characters

Can this be increased?   10 Characters can run out rather quickly once we get more main-stream adoption
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 12, 2019, 12:43:51 pm
Can this be increased?   10 Characters can run out rather quickly once we get more main-stream adoption

No, but people will receive a message letting them know its in use.

10 is enough for 20,000 users or so, that should get us to the next platform version, then we can discuss changing.  We can also discuss it if we have 20,000 by the end of the year as I will have quite a surprise by then as long as we are priced over 14 satoshi at the time.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 12, 2019, 01:17:07 pm
How to check last payed GSC rewards?
I have 3 GSC transmission txs 20h ago, but no reward.
those txs:
571a2ccd45cb1adf4231765e03b3357bd92a626973fab422fe119b8b9ccc1cd1
4bca9b0487a6bb597bdb6d223c095dbf2b63a2ee7626bd78fc17bbc8d42ecbb5
bb0c5c85d39ca7c30b6f732a543f2d7a00491a8d2e3f367e0d678a20a659ec5a
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 12, 2019, 02:00:59 pm
How to check last payed GSC rewards?
I have 3 GSC transmission txs 20h ago, but no reward.
those txs:
571a2ccd45cb1adf4231765e03b3357bd92a626973fab422fe119b8b9ccc1cd1
4bca9b0487a6bb597bdb6d223c095dbf2b63a2ee7626bd78fc17bbc8d42ecbb5
bb0c5c85d39ca7c30b6f732a543f2d7a00491a8d2e3f367e0d678a20a659ec5a

So if we type 'exec points txid', I see 25 million points accrued across the sum of these 3 tx's, and the height was 25470 as of the transmission, meaning the next superblock was @ 25625.  (height % 20 + 205 arrives at 25625).

So doing the 'exec prominence false 25625', I see the chain assessed you at 21 mil in that superblock.

So far everything is good from the Accrual side.

Then we do a getblock 25625, and getrawtransaction 03e4* to look at the coinbase, and woila, the problem is that block became a regular block (not a superblock).

We do have a rule in place that will delay the superblock up to 15 minutes (in case sancs are coming to consensus at that time), so I think whats happened here is this is the height where I deployed a mandatory upgrade and everyone upgraded and overjumped this block (IE it took more than 15 mins to upgrade, so a normal block was allowed, and the sancs were down).  I believe this will be the case if this is the *only* missing block-payment, as I have been watching the last 10 superblocks and historically the last few days of blocks and they are all emitting fine as long as the sancs vote on the supermajority. (See exec health = 4 votes almost every single new sb height etc).

Another words in prod, this would never happen, unless we have half the sancs running on a conflicted version and they all disagree.

Is this your only missed payment?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 12, 2019, 03:29:23 pm
I've chceked my txs and i looks, that this is my only missing reward.
Thanks for explanation.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 12, 2019, 04:35:15 pm
Whoever is sending donations of 666.66 to the orphanage foundation, I rebuke your donations in the name of Jesus.

I hereby command and bind up demons assigned or attacking this project to go now to the deepest part of the abyss and stay there until Jesus deals with you.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 12, 2019, 04:38:14 pm
I've chceked my txs and i looks, that this is my only missing reward.
Thanks for explanation.

Great, please let us know if our accuracy maintains 100% over the next few days.

We are now in qt-level 4!  This is great.

Thanks to all participants!




Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: thesnat21 on April 13, 2019, 07:42:11 am
My windows testnet node is still giving me trouble,  refuses to find any peers.

Side-note:  I got a bit frustrated and deleted the wallet.dat along with all other info .. so no more coins lol

Also,  I noticed the "testnet" client creates/uses the SAN directory in the main client's folder, not the testnet3 folder.

The error message for all peers is: using obsolete version 209 after DIP3 activation; disconnecting


Erm... nevermined

Didn't realize the download link had changed, so i was stuck on .0.6

fixing now

Was this a test? lol
(https://i.imgur.com/c4NddxC.png)

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 13, 2019, 01:32:22 pm
My windows testnet node is still giving me trouble,  refuses to find any peers.

Side-note:  I got a bit frustrated and deleted the wallet.dat along with all other info .. so no more coins lol

Also,  I noticed the "testnet" client creates/uses the SAN directory in the main client's folder, not the testnet3 folder.

The error message for all peers is: using obsolete version 209 after DIP3 activation; disconnecting


Erm... nevermined

Didn't realize the download link had changed, so i was stuck on .0.6

fixing now

Was this a test? lol
(https://i.imgur.com/c4NddxC.png)

Great to have you back in the gang! 
So on the failure to find peers, I truly believe it was the old peer version disconnect - (as last week I added my 3 public nodes to our compiled in testned seed list) so technically I think people should be able to find a peer if they run the latest.

Yes, on the SAN, we do have only one (as there is also another intentional quirk in Dash, that causes it to use the root anyway, so for this SAN dir, we actually store prayers_test in a separate file - so thats OK.

So yeah I didnt enter that prayer, thats quite a long prayer.  Will take a look at these prayers asap.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: thesnat21 on April 13, 2019, 01:55:02 pm
Great to have you back in the gang! 
So on the failure to find peers, I truly believe it was the old peer version disconnect - (as last week I added my 3 public nodes to our compiled in testned seed list) so technically I think people should be able to find a peer if they run the latest.

Yes, on the SAN, we do have only one (as there is also another intentional quirk in Dash, that causes it to use the root anyway, so for this SAN dir, we actually store prayers_test in a separate file - so thats OK.

So yeah I didnt enter that prayer, thats quite a long prayer.  Will take a look at these prayers asap.

Working on getting the tools setup for testnet, will see about adding a campaigns tab as well
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 13, 2019, 02:59:27 pm
We have a monthly budget coming at 30135.  I just entered 3 proposals.  Feel free to enter some more and vote up-down so we can test watchman.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 13, 2019, 03:00:52 pm
Working on getting the tools setup for testnet, will see about adding a campaigns tab as well

Great, I will look into adding features for Grandma starting tomorrow. 
I think I will add "Leaderboard" as an rpc command (without exec) asap to show the 'exec prominence' defaults also.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 14, 2019, 08:49:41 am
We have a monthly budget coming at 30135.  I just entered 3 proposals.  Feel free to enter some more and vote up-down so we can test watchman.

I entered 3 proposals (no one entered any others I see) and the two totaling 3.8 MM were paid (getblock 30135 to see them), that is correct as the other one was over budget.

So watchman succeeded, but I do see a bug in the proposal UI.  It still shows the 3 old proposals that are paid.  Ill work on analyzing this. 



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 14, 2019, 09:14:25 am
I entered 3 proposals (no one entered any others I see) and the two totaling 3.8 MM were paid (getblock 30135 to see them), that is correct as the other one was over budget.

So watchman succeeded, but I do see a bug in the proposal UI.  It still shows the 3 old proposals that are paid.  Ill work on analyzing this.

I found the bug, this will be fixed in the next release.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 14, 2019, 09:15:36 am
So far, it appears QT is working correctly.

I will be enabling ABN soon and we can test that next. 



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 14, 2019, 01:08:54 pm
So far, it appears QT is working correctly.

I will be enabling ABN soon and we can test that next.

ALL:

I just enabled the enforcement of ABN weight.  We currently require 1000 abn weight.

Lets keep an eye on the difficulty and ensure everything rolls forward properly.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 14, 2019, 03:15:01 pm
My windows testnet node is still giving me trouble,  refuses to find any peers.

Side-note:  I got a bit frustrated and deleted the wallet.dat along with all other info .. so no more coins lol

Also,  I noticed the "testnet" client creates/uses the SAN directory in the main client's folder, not the testnet3 folder.

The error message for all peers is: using obsolete version 209 after DIP3 activation; disconnecting


Erm... nevermined

Didn't realize the download link had changed, so i was stuck on .0.6

fixing now

Was this a test? lol
(https://i.imgur.com/c4NddxC.png)

I forgot to ask, do you need any tBBP?


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 15, 2019, 02:24:25 pm
Rob,
I think, that would be nice to have these stats (from production) in tx details:
Code: [Select]
Height: XXX
Difficulty: XXX
Time: XXX
Subsidy: XXX
Now its really hard to count block height when the tx has been done.
Maybe block height would be enough.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 15, 2019, 02:57:09 pm
Rob,
I think, that would be nice to have these stats (from production) in tx details:
Code: [Select]
Height: XXX
Difficulty: XXX
Time: XXX
Subsidy: XXX
Now its really hard to count block height when the tx has been done.
Maybe block height would be enough.


Good idea, I will add them (added to list).


Also I was just reading about the procedure to upgrade a Sanc to a deterministic sanc, and although on the positive side, its just a single page of commands that can be done from the home wallet itself, if someone owns a lot of sancs, they might miss out  on a major family event like birth of new child, etc.  In light of that I was thinking it might be useful for us to add an upgrade command.  I believe we can potentially access what we need by scanning down to the existing entry in the masternode.conf, then generating the new info, signing it and sending it.  One last step we can not do is move the 'masternodeblsprivkey=' to the hosted sanc, but we can emit that in the output of the upgradesanc command.  I think Ill work on this command before we move to dip3.      https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html

Something like 'upgradesanc existing_sanc_name' would be nice.  Then it outputs: masternodeblsprivkey=nnnnnn.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 16, 2019, 09:55:01 am
So, I did add the legacy double click info to our txlist, and over the last day, I added a new command to allow us to upgrade a sanc to deterministic.

Let me iterate through the punchlist, and verify some other small things we might need for our next round of testing, and then ill create a new release for testnet.

BTW, our ABN feature worked about 95%, but I did discover a bug in it so only 1 of its 2 features are enabled, will fix this as part of this next release also.

Progress is now speeding up, and everything looks very solid.  I feel bullish about the next version of BiblePay.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 17, 2019, 03:36:51 pm
The new version is almost ready, but I see the 4.5MM lockup poll is most likely winning.

I believe this is a good time for us to include the higher collateral in the next release (since we need a mandatory change anyway for the ABN rule).

We will need to re-create our sancs @ 4.5 MM.

Stay tuned...

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 17, 2019, 04:20:12 pm
I'm starting to add some documentation to explain to new users how to get started:

Getting started with Evolution:
https://wiki.biblepay.org/Getting_Started_with_Evolution
GSC's:
https://wiki.biblepay.org/Generic_Smart_Contracts
Healing Campaign:
https://wiki.biblepay.org/BiblePay_Healing_Campaign
Street Healing:
https://wiki.biblepay.org/Street_Healing
Spiritual Warfare:
https://wiki.biblepay.org/Spiritual-Warfare-I



I realize we need a specific section for Grandma also - I'll continue to refine the getting started guide.

Please let me know if anyone would like to see more expanded info on any of these, and/or if this is sufficient to call us "easy to use" with the release of Evo.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 17, 2019, 04:36:20 pm
1.4.1.7 - Mandatory Upgrade for TestNet

- Fix bug showing old proposals in Proposals List page
- Change sanctuary lockup collateral to 4,500,001
- Upgrade persisted data storage system from v1.0 to v1.1
- Add txlist double click drill in: display of biblepay-classic fields:
height, time, difficulty
- Add RPC leaderboard command (leaderboard me=true/false [height ||
last || future]
- Add exec upgradesanc sancname.  This is a BiblePay utility that allows
you to upgrade a non-deterministic sanc to a deterministic sanc.  We
also add the deterministic.conf file, so the user can write scripts to
read their own deterministic sanc keys and automate the deployment of
the keys to the remote server(s).
- Fix low-abn-weight bug
- Make exec join healing display the wiki URL so the user can learn
about the healing campaign first


Note:  We just changed our sanctuary lockup collateral to 4,500,001.  Please re-create your sancs.

We will talk about Deterministic a little later, for now please re-create the standard way - but note: It is recommended that we re-create Cold sancs, as the upgrade to dip3 will require cold sancs.  (Hot sancs cannot be upgraded to dip3).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 18, 2019, 08:34:12 am
I'm seeing this hash:
getblockhash 37124
1e0d0a836d61d246d0202507747a71e2960eaf683668d45b38365616cbed6ffa

Last night I recreated my 3 sancs and enabled them but through the night people upgraded and reorganized and erased the block I sent my 4.5MM in.
I just recreated my 3 legacy sancs again; re-starting sancs now.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 18, 2019, 09:13:15 am
Actually it looks like we are encountering a brand new Evo-specific issue as of a new block from yesterday:

2019-04-18 13:59:56 ERROR: ConnectBlock(): ProcessSpecialTxsInBlock for block 4b1205177d60daa173491b742e39501ae29a48605bf3ed617ade77149feb6fb2 failed with bad-protx-collateral (code 16)

It looks like two of us tried to create deterministic sancs before the spork was enabled.  But what is interesting is this was legal yesterday but today the block is actually being rejected.  (I can understand that partially since all the sancs are disabled right now), but what is interesting to me is that we reject the entire block if the Pro-reg-tx fails.

Let me take a look at this issue in detail.  In the mean time I think the only way to sync is to re-sync every node to before 34510 occurred.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 18, 2019, 09:24:00 am
Actually it looks like we are encountering a brand new Evo-specific issue as of a new block from yesterday:

2019-04-18 13:59:56 ERROR: ConnectBlock(): ProcessSpecialTxsInBlock for block 4b1205177d60daa173491b742e39501ae29a48605bf3ed617ade77149feb6fb2 failed with bad-protx-collateral (code 16)

It looks like two of us tried to create deterministic sancs before the spork was enabled.  But what is interesting is this was legal yesterday but today the block is actually being rejected.  (I can understand that partially since all the sancs are disabled right now), but what is interesting to me is that we reject the entire block if the Pro-reg-tx fails.

Let me take a look at this issue in detail.  In the mean time I think the only way to sync is to re-sync every node to before 34510 occurred.

Ok.  I see whats going on here.  At first it seems a little strange that a single bad pro-reg tx could fork the chain (because business logic rejects the entire block that contains the bad pro-reg) -- but thats not whats really happening in the bigger picture. 

In the bigger picture we will always have a supermajority of sancs online in prod to make the call, so with sancs actually online, the pro-reg would have been processed or the sanc-quorum would have rejected the block.

The rule goes like this:  For chainlocks, llmqs, and pro-reg-special-transactions, all of these are forwarded to a processor that checks validity based on the llmq (long living masternode quorum), and if any fail, the entire block is rejected.

So what we need to do first everyone, please re-sync your chain to before 34510 and please do not send any 'upgradesanc' commands or pro-regs until we successfully recreate our sanc quorum with 4.5 mm locks.  Also just to be safe, lets ensure diff is > 1.0 and we solve the next GSC superblock after that with exec health showing true.

Then we can re-group and talk about testing the next layer(s).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 18, 2019, 12:08:06 pm
Ok, Ive resynced all my nodes and restarted my sancs  - they went to enabled, Im seeing this hash:

getblockhash 34746
123eebf58f402f349adc10d578ef80a9e8a4200a45326db28b6eb39ab0b364a8
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on April 19, 2019, 05:27:11 am
1.4.1.7 - Mandatory Upgrade for TestNet


I compiled a version of the daemon/cli for Linux amd64, available here
https://www.biblepay.org/biblepayd-1.4.0.7-x86_64-pc-linux-gnu.tar.gz

And MacOS QT version here
https://www.biblepay.org/biblepaycore-testnet.dmg
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 19, 2019, 12:25:21 pm
I am stuck the whole day at Syncing Headers 96,3% , progress bar  is  2sec behind.

19:25:02
getblockhash 36743

19:25:02
d7d64e0701e5480e3b53429d7015b03ae0351c025dfd6d4de9c86f05f8294bd6
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 19, 2019, 12:32:52 pm
I am stuck the whole day at Syncing Headers 96,3% , progress bar  is  2sec behind.

19:25:02
getblockhash 36743

19:25:02
d7d64e0701e5480e3b53429d7015b03ae0351c025dfd6d4de9c86f05f8294bd6

I took a look at that stuck 1-10 second behind header issue, and it turns out what that means is your node doesn't have a fully synced gobject list (IE it believes the masternodes and gobjects are not synced) - also, if you do an mnsync status, you are probably in chain synced true and gobjects synced = false. 
Another words, that is a feature that lets you know something is wrong with the mnsync status only.

EDIT: Ok, so yes you are synced on the blockchain - my hash agrees.

I think you just have a bad mncache.

Try this:  stop node, rm mnc*.*, rm gov*, rm mnp*,  restart wallet, wait 10 mins - see if mnsync status shows all trues then and the bar dissapears?



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 19, 2019, 12:35:33 pm
I see someone was nice enough to enter about 15 proposals right before we upgraded!

Thanks!

Who was that btw?

Unfortunately all this work was in vain because we had the mandatory upgrade right after, and there were no sancs around to vote at that height for that superblock (see getgovernanceinfo, see last superblock height), that block ended up turning out to be a regular block.

This is to be expected in this case.

So please let us do it again soon.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 19, 2019, 01:05:41 pm
I compiled a version of the daemon/cli for Linux amd64, available here
https://www.biblepay.org/biblepayd-1.4.0.7-x86_64-pc-linux-gnu.tar.gz

And MacOS QT version here
https://www.biblepay.org/biblepaycore-testnet.dmg

Thanks - added the Mac version to the OP post.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 19, 2019, 02:32:24 pm
Please ensure your hashes match - someone came on with high hash:
getblockhash 36743
d7d64e0701e5480e3b53429d7015b03ae0351c025dfd6d4de9c86f05f8294bd6


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 19, 2019, 05:22:50 pm
I had to delete everything, than it synced headers as well.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 19, 2019, 09:45:28 pm
I had to delete everything, than it synced headers as well.

Glad you are synced.  I believe your headers were already synced before this step. 

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 20, 2019, 09:49:40 am
So I found a "bug" in 1417.  It appears that when we move to dip3, our sancs cant sign the signature for one of our features properly (primarily because the structure of this feature has changed in Evo, so its really a class change that breaks compatibility with one of our old methods).

This means I need to upgrade the function in 1418 and have another mandatory release.

It looks like Im the only one who updated my sancs so far (I see my 3 online) so hopefully this wont be too big a deal.

Please hold off on testing while I fix this. 



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 20, 2019, 01:37:03 pm
1.4.1.8-Mandatory Upgrade for TestNet

- Improve GSC consensus rule
- Add historical BTC price to each gsc superblock for future reports
- Prevent multiple UI popups within 7 seconds
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on April 21, 2019, 05:48:32 am
1.4.1.8-Mandatory Upgrade for TestNet

- Improve GSC consensus rule
- Add historical BTC price to each gsc superblock for future reports
- Prevent multiple UI popups within 7 seconds

Daemon/cli for Linux amd64, available here
https://www.biblepay.org/biblepayd-1.4.0.8-x86_64-pc-linux-gnu.tar.gz

And MacOS QT version here
https://www.biblepay.org/biblepaycore-testnet.dmg
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on April 21, 2019, 05:56:02 am
Sorry wrong version number

Daemon/cli for Linux amd64, available here
https://www.biblepay.org/biblepayd-1.4.1.8-x86_64-pc-linux-gnu.tar.gz
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 21, 2019, 08:35:02 am
1.4.1.8-Mandatory Upgrade for TestNet

- Improve GSC consensus rule
- Add historical BTC price to each gsc superblock for future reports
- Prevent multiple UI popups within 7 seconds

Could some people please confirm they have upgraded?

I only see my sancs have upgraded (3) and a couple single nodes.


We have a lot to test starting at block 40,000 so we need some help in order to make the June deadline.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 21, 2019, 12:25:50 pm
Does anyone agree with this hash:
getblockhash 39718
442b195612beaa846afcc49d5fa4e3184e94bcff6200f2a486cf71ae0cfe58c0


** ABN **

I enabled ABN (anti-botnet).  We can start testing this next.  ABN required weight is currently 1000.

QT starts at block 40,000.  We can test them both.




Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 22, 2019, 10:09:27 am
I see we have a problem syncing from 0 in testnet (bad block at 31150).

Some people are past it some aren't.

Will send out a release correcting this problem in 1 hour.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 22, 2019, 10:56:46 am
1.4.1.9-Leisure upgrade for TestNet

- Fix bad configuration setting allowing a bad block in at 31150

If anyone has a low diff, just upgrade then resync and lets see if we can test the 40K features.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 22, 2019, 11:21:55 am
After resyncing my sancs and starting them I see this hash:

11:21:31

getblockhash 40668


11:21:31

9c1b6d67d8737b9976eed162b8edce7018430a9f2d16cfd97e4c83b14943baf6


Anyone agree with mine?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 22, 2019, 07:53:24 pm
Just documenting my adventure, Im compiling on Ubuntu
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

Line 16 after cloning the repo I needed to cd into it
Code: [Select]
cd biblepay-evolution
Line 23 I ran into issue trying to run make command

I ran:
Code: [Select]
uname -ato confirm my architecture

For this command:
Code: [Select]
./configure --prefix {pwd}/depends/x86_64-pc-linux-gnu
I had to use:
Code: [Select]
./configure --prefix `pwd`/depends/x86_64-pc-linux-gnu
Nabbed it from here:
https://github.com/dashpay/dash/blob/master/doc/build-generic.md

I dont know anything about bash
https://ss64.com/bash/syntax-expand.html
https://unix.stackexchange.com/questions/98391/what-is-the-difference-between-echo-date-echo-date-and-echo-date

I also used the swap file commands since Im on 1GB:
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

Ill let you guys know when Im synced up and ready for some tBBP :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 23, 2019, 01:16:06 am
After resyncing my sancs and starting them I see this hash:

11:21:31

getblockhash 40668


11:21:31

9c1b6d67d8737b9976eed162b8edce7018430a9f2d16cfd97e4c83b14943baf6


Anyone agree with mine?

well I resynced and my last block is 34929
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on April 23, 2019, 06:43:06 am
1.4.1.9-Leisure upgrade for TestNet

- Fix bad configuration setting allowing a bad block in at 31150

If anyone has a low diff, just upgrade then resync and lets see if we can test the 40K features.

Daemon/cli for Linux amd64, available here
https://www.biblepay.org/biblepayd-1.4.1.9-x86_64-pc-linux-gnu.tar.gz

And MacOS QT version here
https://www.biblepay.org/biblepaycore-testnet.dmg
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 23, 2019, 07:50:31 am
After resyncing my sancs and starting them I see this hash:

getblockhash 40668
9c1b6d67d8737b9976eed162b8edce7018430a9f2d16cfd97e4c83b14943baf6

Anyone agree with mine?

I agree with that hash on my daemon and now Im on block 42305

Code: [Select]
./biblepay-cli getblockhash 42305
ad4e735a7db8aacd92dfd7e50775d35e528c441bb95fd440fb9a7956aa056619

Could I have some tBBP please? Thanks!
Code: [Select]
yUEdCwzLCm58oXksh42R3eBroTrU9MN3hX
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 23, 2019, 08:17:03 am
Just documenting my adventure, Im compiling on Ubuntu
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

Line 16 after cloning the repo I needed to cd into it
Code: [Select]
cd biblepay-evolution
Line 23 I ran into issue trying to run make command

I ran:
Code: [Select]
uname -ato confirm my architecture

For this command:
Code: [Select]
./configure --prefix {pwd}/depends/x86_64-pc-linux-gnu
I had to use:
Code: [Select]
./configure --prefix `pwd`/depends/x86_64-pc-linux-gnu
Nabbed it from here:
https://github.com/dashpay/dash/blob/master/doc/build-generic.md

I dont know anything about bash
https://ss64.com/bash/syntax-expand.html
https://unix.stackexchange.com/questions/98391/what-is-the-difference-between-echo-date-echo-date-and-echo-date

I also used the swap file commands since Im on 1GB:
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

Ill let you guys know when Im synced up and ready for some tBBP :)

Thanks -

1) I added the swap file commands to the BuildBiblePay.txt file at the beginning as Optional.

2) I see what you mean about {pwd}.  I believe I didnt run into that problem is I typed out the path.  I have changed it to `pwd` in the docs.

3) Our build-generic.md is in the repo also, but I realize it can't be found without navigating around github as its probably not searchable on google yet.

4) Glad you got through the depends hurdle, that is the main hurdle to upgrade to Evo.

5) Ill send some tBBP, but I see we have 20 new nodes online, so we are all at different heights. 
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 23, 2019, 08:22:32 am
well I resynced and my last block is 34929

I see a similar problem, my 3 sancs reorged back to 34929 when these 20 new nodes came online.

Let me explain to everyone one conundrum (this affects Dash also).  The sancs must be online in order for our daily superblock consensus to work, and for masternode payments to work (as their vote heights must be exact and correct), and the sancs go out of sync when the supermajority of the miners reorganize (meaning they need Re-Enabled manually).  While they are not enabled, the entire network is really just free-riding.  Its that chicken and egg issue I explained earlier.

Once the sancs are enabled while they are at a similar height as the supermajority things should clear up.

Right now all sancs are out of sync and disabled.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 23, 2019, 09:14:19 am
I'm seeing this hash:

09:12:55

getblockhash 42424


09:12:55

5bf45962948b72ca0d74a9cc353aa89d7765c702741954718809623656bb09a8



If your node does not agree, please try this additional step, in addition to deleting the normal 6 folders and files (evodb, chainstate, blocks, mnp*, mnc*, gov*) also delete : /SAN/*.*

Then restart.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on April 23, 2019, 10:29:23 am
I'm seeing this hash:

09:12:55

getblockhash 42424


09:12:55

5bf45962948b72ca0d74a9cc353aa89d7765c702741954718809623656bb09a8



If your node does not agree, please try this additional step, in addition to deleting the normal 6 folders and files (evodb, chainstate, blocks, mnp*, mnc*, gov*) also delete : /SAN/*.*

Then restart.

I've been trying to catch up with you guys for more than a week now :P Every time I finally had my nodes up and running, you guys already jumped to the next version :p

Anyway, I have two nodes that are also stuck in the 35*** range. Will try to delete these files and see what happens.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on April 23, 2019, 02:43:04 pm
I've been trying to catch up with you guys for more than a week now :P Every time I finally had my nodes up and running, you guys already jumped to the next version :p

Anyway, I have two nodes that are also stuck in the 35*** range. Will try to delete these files and see what happens.

Deleting those files helped :) I'm synced to the chain with the same hash for block 42424:
5bf45962948b72ca0d74a9cc353aa89d7765c702741954718809623656bb09a8

Next step will be to try and set up some sanctuaries I guess :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 23, 2019, 02:45:30 pm
Deleting those files helped :) I'm synced to the chain with the same hash for block 42424:
5bf45962948b72ca0d74a9cc353aa89d7765c702741954718809623656bb09a8

Next step will be to try and set up some sanctuaries I guess :)

Great!
Remember they are now 4,500,001 and they must be cold sancs now (so we can all upgrade to dip3 sancs later).

Let me know if you need tBBP.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 23, 2019, 03:28:51 pm
I found a bug today that requires us to upgrade to 1.4.2.0.

Please know that the upgrade is coming in about an hour.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 23, 2019, 04:13:19 pm
1.4.2.0-Mandatory Upgrade for TestNet

- Fix bug not allowing QT to properly start
- Add -erasechain parameter (this allows you to erase the chain during
boot)
- Add Togos suggestions to the BuildBiblePay.txt docs file

** Note: The link has changed in the OP post due to rolling over to a new major version **
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 23, 2019, 05:19:38 pm
One thing that might make it easier to sync in future upgrades:  set gen=0 in the config file, upgrade, then after confirming you are synced then manually turn on generate.

I found its so easy to solve a block in testnet this will easily put you on your own chain.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 23, 2019, 06:21:18 pm
Upgraded to v1.4.2

I confirm same hash for 42424

Code: [Select]
./biblepay-cli getblockhash 42424
5bf45962948b72ca0d74a9cc353aa89d7765c702741954718809623656bb09a8

Im currently at:

Code: [Select]
./biblepay-cli getblockhash 43157
ffa38ab5eaf5b7516ed1891c78aedf428160fc1cc9493420927c6f7f7808fa62
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 23, 2019, 07:44:34 pm
Upgraded to v1.4.2

I confirm same hash for 42424

Code: [Select]
./biblepay-cli getblockhash 42424
5bf45962948b72ca0d74a9cc353aa89d7765c702741954718809623656bb09a8

Im currently at:

Code: [Select]
./biblepay-cli getblockhash 43157
ffa38ab5eaf5b7516ed1891c78aedf428160fc1cc9493420927c6f7f7808fa62

Good, we match.  Hopefully you received the tBBP.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 23, 2019, 08:38:24 pm
Thanks Rob! I have about 7.9 million tBBP now, Ill set up a masternode soon
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 24, 2019, 08:02:03 am
Is everyone mining, because I only see a .10 diff and 4 people in the leaderboard.

Anyone who is not in the leaderboard, you can join by adding your cpk then 'exec join pog'. 

I'm reluctant to turn on ABN until diff is about 1. 

QT is enabled, we are now at qt level 2.  It appears the new GSC contract version is working (this version contains the prices).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 25, 2019, 08:30:03 am
Good news, things look pretty good.  I did discover a bug causing a couple issues that get logged as ERROR, and also a couple necessary enhancements for the anti-fork feature, but these can wait a tad longer til we add at least one more thing from the punch list.  I see we have 10 participants in the GSC block now.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on April 25, 2019, 09:24:53 am
1.4.2.0-Mandatory Upgrade for TestNet

- Fix bug not allowing QT to properly start
- Add -erasechain parameter (this allows you to erase the chain during
boot)
- Add Togos suggestions to the BuildBiblePay.txt docs file

** Note: The link has changed in the OP post due to rolling over to a new major version **

Daemon/cli for Linux amd64, available here
https://www.biblepay.org/biblepayd-1.4.2.0-x86_64-pc-linux-gnu.tar.gz

And MacOS QT version here
https://www.biblepay.org/biblepaycore-testnet.dmg
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 26, 2019, 03:41:52 pm
1.4.2.1b-Mandatory Upgrade for TestNet

- Improve anti-fork business logic
- Remove ABN error log spam
- Add Church Tithing subsystem
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 26, 2019, 07:32:45 pm
Upgraded to v1.4.2.1b

Code: [Select]
./biblepay-cli getblockhash 48789
f8359bfbfa16f3faa02eaf6bab8c9d5143962ec24e3c99953e14f0a709d670a9
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: uptimeminer on April 26, 2019, 08:44:52 pm
getblockhash 48789
f8359bfbfa16f3faa02eaf6bab8c9d5143962ec24e3c99953e14f0a709d670a9

Agree....Just updated to 1.4.2.1b
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 26, 2019, 09:54:59 pm
getblockhash 48789
f8359bfbfa16f3faa02eaf6bab8c9d5143962ec24e3c99953e14f0a709d670a9

Agree....Just updated to 1.4.2.1b
Agreed.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 27, 2019, 04:53:49 pm
Ok everyone, I was waiting for the code to stabilize and diff to increase and the height to pass a few hundred past all our changes before I started flipping switches.

It appears we are all staying in sync (although diff is only .50 - I think that is because we are mining with low power machines) so that should be fine.  My sanc#2 has 21 connections so that is good (none are banned).

In the last version, we fixed the ABN (anti-bot-net feature) to stop throwing errors in the log.  As of 44350, we now enforce the low abn height rule (minimum 1000 abn weight required per block).

So lets start by testing this.  Im going to look in the logs, and grep for "ERROR" and does not meet anti-bot-net-minimum required guidelines.  We should no longer see this in the log.  Then we will do a getblock 50560, 50561, ... etc, and check the anti-bot-net weight on each block- it should be > 1000.

Ok, Test #1 passed:  We no longer have this anti-bot-net ERROR in the log after the cutover height.  The only ERROR I see now is 'superblock has no recipients' at 50225 - thats normal. 

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 27, 2019, 05:10:35 pm
I just enabled our antigpu feature starting @ 50560.  This is similar to the rule we had in PODC, where a CPID could not solve any block within a 4 consecutive block lookback in prod (and 1 block in testnet).  So in Evo, this means a distinct CPK cannot solve more than 1 block per 1 block lookback in test (4 blocks in prod).

So to test this, we will do a getblock 50560, look for the CPK field, and ensure it is changing each consecutive block forward) - no back to back solutions in testnet.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 27, 2019, 05:12:28 pm
I don't see any other cold sancs (other than my 3 in testnet).  It's going to be hard to perform quality testing with just me on board.
Is anyone planning on starting a sanc?

Im thinking about testing dip3 sancs tomorrow.

(We need to test upgrading a legacy sanc to a deterministic sanc).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 27, 2019, 08:31:34 pm
Im attempting to setup a masternode now

I was trying to do it by command line but sent coins to wrong address,
so now I installed lubuntu and am trying again

=

These are my old notes:
https://forum.biblepay.org/index.php?topic=190.msg3701#msg3701
https://forum.biblepay.org/index.php?topic=108.msg1444#msg1444

Attempt to use VNC:
https://forum.biblepay.org/index.php?topic=244.msg4525#msg4525
https://forum.biblepay.org/index.php?topic=244.msg4523#msg4523

Masternode guide:
http://wiki.biblepay.org/Create_Sanctuary_2

=

I get nothing back when typing masternode outputs,
then I tried checking the balance of the address (getbalance) I sent to and it was 0,
I turned on coin control and checked, and it seems almost all the coins are in a "(change)" address

Ill try again

I also noticed there was an additional 10% Foundation tithe added on to the initial transaction, even though I didnt click any checkboxes in the GUI
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 27, 2019, 08:44:11 pm
Hmm it happened again, got screenshots:
https://imgur.com/a/F882yIp
looks like coins get split up into the "CHRISTIAN-PUBLIC-KEY" address automatically
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on April 27, 2019, 10:34:18 pm
I've been trying to start a Sanctuary, but I can't seem to sync my wallets properly :(
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 28, 2019, 12:52:42 am
I've been trying to start a Sanctuary, but I can't seem to sync my wallets properly :(

rm blocks -r
rm chainstate -r
rm evodb -r
rm SAN -R
rm gov*
rm mnc*
rm mnp*

I just delete everything other than the wallet.dat, backups folder, biblepay.conf, peers list and masternode.conf

And then I do a ./biblepayd -dameon -reindex
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 28, 2019, 02:41:26 am
Hmm it happened again, got screenshots:
https://imgur.com/a/F882yIp
looks like coins get split up into the "CHRISTIAN-PUBLIC-KEY" address automatically
Togo, there has to be sanctuary lockup collateral to 4,500,001, not for 4,500,000. Or am I wrong?
Maybe that is the problem.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 28, 2019, 04:34:01 am
Hi all,
finally after 1421b update I was back on chain.
I had really big problem with ABN feature and I wasn't be able to sync.
I've tried it for few days and I spent many hours with clean install and resync.
Mostly it tooks me more than 3-4 hours to reach last block, then ABN error stops me and I started whole process again.
I was really disappointed and upset :)
Yesterday I was finally synced and it looks good, but then I stopped my wallet and today it wont synced again :(
Today there is problem with antigpu:
Code: [Select]
2019-04-28 09:12:54  AntiGPU i 0.000000, CPK ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg      ERROR: TestBlockValidity: Consensus::ContextualCheckBlock:  (code 0)
I'm stucked at block 50706, So I need to make resync again :(
That lead me to the question of whether you are thinking about creating "bootstrap.dat" copy on your servers to sync faster.
Others coins has this like common "service".
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 28, 2019, 04:35:38 am
And there is also ABN error again:
Code: [Select]
2019-04-28 09:34:09
CreateNewBlock::Unable to add ABN because Sorry, must be unlocked to create an anti-botnet transaction.antibotnetsignature failed on tx baddb353bac2364d696ad7749c0237092d3e0409ee9bafd5c983144216d351dc with purported coin-age of 0.000000
2019-04-28 09:34:09 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock:  (code 0)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 07:58:22 am
And there is also ABN error again:
Code: [Select]
2019-04-28 09:34:09
CreateNewBlock::Unable to add ABN because Sorry, must be unlocked to create an anti-botnet transaction.antibotnetsignature failed on tx baddb353bac2364d696ad7749c0237092d3e0409ee9bafd5c983144216d351dc with purported coin-age of 0.000000
2019-04-28 09:34:09 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock:  (code 0)

In order to ABN mine you have to unlock the wallet :
walletpassphrase nnnnn

It appears we dont respect this command yet:
exec setautounlockpassword your_password

EDIT:  Let me take a look at blackcoin and see if its possible for us to sign the stake in a similar way without asking the user to unlock the wallet (IE for staking only) as this will be a big nuisance if we don't investigate this.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 08:09:00 am
Hmm it happened again, got screenshots:
https://imgur.com/a/F882yIp
looks like coins get split up into the "CHRISTIAN-PUBLIC-KEY" address automatically
Sorry for the inconvenience but the lockup was changed to 4,500,001.  The change is normal (its just giving change back from the transaction).
The lack of masternode outputs is because it didnt recognize the 4,500,000 as a collateral tx.

However I will take a look at the above posts regarding foundation tithes etc but in the mean time you should be able to create a sanc.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 08:10:21 am
I've been trying to start a Sanctuary, but I can't seem to sync my wallets properly :(

Please try 'gen=0' in the biblepay.conf  first, then see if it reaches the top?
It is probably trying to mine every time the blocks pause.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 08:18:25 am
Hi all,
finally after 1421b update I was back on chain.
I had really big problem with ABN feature and I wasn't be able to sync.
I've tried it for few days and I spent many hours with clean install and resync.
Mostly it tooks me more than 3-4 hours to reach last block, then ABN error stops me and I started whole process again.
I was really disappointed and upset :)
Yesterday I was finally synced and it looks good, but then I stopped my wallet and today it wont synced again :(
Today there is problem with antigpu:
Code: [Select]
2019-04-28 09:12:54  AntiGPU i 0.000000, CPK ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg      ERROR: TestBlockValidity: Consensus::ContextualCheckBlock:  (code 0)
I'm stucked at block 50706, So I need to make resync again :(
That lead me to the question of whether you are thinking about creating "bootstrap.dat" copy on your servers to sync faster.
Others coins has this like common "service".

We can look at the bootstrap for prod later once we know everything is fine, but we should be able to sync in less than 15 mins in testnet, otherwise we have bigger issues.
Please try putting the 'gen=0' in your biblepay.conf first also.
If you try Togos post above, can you see if it syncs to the top without a problem? 
I am thinking this AntiGPU error in your log has to do with you solving a block before the tip then being unable to mine because its the only last block on your chain (which makes the next one from you illegal).



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 08:29:00 am
Hmm it happened again, got screenshots:
https://imgur.com/a/F882yIp
looks like coins get split up into the "CHRISTIAN-PUBLIC-KEY" address automatically

You scared me a little on this one, lol, OK I reproduced it and I can see whats going on.

So to reproduce, make a new receiving address (like T101), copy the To address, paste it in a new Send To Transaction, dont click any checkboxes,
and when you click send, the "Verification" list shows a Tithe of 10% in it (but it does not actually add it to the transaction total and does not really send it).

So the bug is just a validation message bug.

(You can see in the drill in of the sent tx list its just the base tx being sent).

On a side note, the only change back to the CPK should be coming from those ABN/GSC transactions, when we create an ABN/GSC stake, we send the change back to the CPK. 

So I will add fixing this Tithe validation now to the punchlist.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 28, 2019, 08:50:33 am
In order to ABN mine you have to unlock the wallet :
walletpassphrase nnnnn

It appears we dont respect this command yet:
exec setautounlockpassword your_password

EDIT:  Let me take a look at blackcoin and see if its possible for us to sign the stake in a similar way without asking the user to unlock the wallet (IE for staking only) as this will be a big nuisance if we don't investigate this.
Ok, this is new knowledge to me :)
I don't know that it is needed to have unlocked wallet. I'll try to unlock wallet everytime I start it :)
exec setautounlockpassword your_password didn't worked for me.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 08:59:50 am
Ok, this is new knowledge to me :)
I don't know that it is needed to have unlocked wallet. I'll try to unlock wallet everytime I start it :)
exec setautounlockpassword your_password didn't worked for me.

Well it looks like I made the 'exec setautounlockpassword' work with GSC transmissions only (but not with ABN) so for this current version you must unlock the wallet fully to ABN mine.  (with walletpassphrase blah time).

Looking at staking (and mixing) I can see why we ended up here.  We really must ask the user to either enter the pop up password, or run a command to have the securestring key handy for ABN mining (or for gsc) to work (IE its a must).  So in light of that, that means we need to take baby step 1 and get this 'setautounlockpassword' to be respected in both places, so I will do that first.  We dont necessarily need to make the pop-up work (its a decision we can think of later) as remember about 15 pages back I explained that might be frowned upon - so for now Ill fix the consistency with this autounlock password.

Let me know if you do Not have a syncing problem also, as I really want to ensure no one has a syncing problem in Evo. 


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 28, 2019, 09:12:37 am
We can look at the bootstrap for prod later once we know everything is fine, but we should be able to sync in less than 15 mins in testnet, otherwise we have bigger issues.
Please try putting the 'gen=0' in your biblepay.conf first also.
If you try Togos post above, can you see if it syncs to the top without a problem? 
I am thinking this AntiGPU error in your log has to do with you solving a block before the tip then being unable to mine because its the only last block on your chain (which makes the next one from you illegal).
So, I'm stucked on block 50561 again.  It looks, that resync is waiting for me again. Rob, in few last days I've made more than 10 full resync (deleted everything from biblepaycore folder - like in Togos post) but it never took less than 2 hours for me.
Maybe it is problem of my PC, but we've talked about this before latest mandatory testnet.
May it be caused with mine huge activity in constant download of data from my peers? May I be blocked somehow?
Sometimes it starts withou problem, but after some time download fall to 10kB/s.
I can guarant that it is not caused with my internet connection.
I have now tho internet providers (300 Mbps and 500Mbps) and it is the same on both. So, it can be caused with my PC, but on my second PC it was the same. Slow connection with peers.

I have tried to set gen=0, but there is still problem with sync.
Here is part from my debug.log:
Code: [Select]
2019-04-28 13:55:37 ERROR: AcceptBlockHeader: block f5cbf4edfd4df18b3204ac8c72b44ba04296e0334d50a9d40e9b208f4f835913 is marked invalid
2019-04-28 13:55:37 ERROR: invalid header received

So, I'll start resync again with gen=0 and I'll see if the sync will be faster.
BTW: Rob, can you delete debug.log from WIN wallet install file?
It is in ...BiblepayEvolution\doc\ folder after install and it has more then 67MB :D I think that it is not neccessary for us ;)
There are some old logs from end of March.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 28, 2019, 10:12:36 am
Thanks for looking into things Rob!

=

On a side note, the only change back to the CPK should be coming from those ABN/GSC transactions, when we create an ABN/GSC stake, we send the change back to the CPK. 

1. So this coin splitting behavior is intended and happens automatically every so often? when mining? (and every wallet is now set to mine by default?)
1.a. Is an amount of 4500001 ignored for coin splitting? when user is setting up a masternode?
1.b. Does this mean new miners have to own some amount of BBP coins in their wallet to participate in mining? (but they can jump in to mine when block hasnt been solved for 60 minutes if they dont have coins?)

2. Also for the CPK, I noticed that I never ran a command (exec cpk my_nickname) to create one, is default behavior that one is created automatically? And the command is to just add a nickname to it?

=

Just poking around the documentation:

https://wiki.biblepay.org/Getting_Started_with_Evolution
https://wiki.biblepay.org/Generic_Smart_Contracts

GSC (Generic Smart Contract)
"The GSC is split into a client server architecture. The client side user joins campaigns with a CPK (Christian Public Keypair) and competes in these campaigns for points. The server side (our Sanctuaries) assess user points and tracks user progress. Once per day, the points are converted and paid in a Generic Smart Contract. The GSC is voted on by the Sanctuaries automatically at a certain chain height. The GSC is paid once per day as a superblock from BiblePay core, and is split among campaigns by points rewarded per campaign per user. "

ABN (Anti-BotNet)
"which requires a certain amount of coin*age to be present in each mined block in order to mine BiblePay"
"Our network requires an average calculated and pre-assessed static amount (posted in getmininginfo) of required coin*age and stores this in the chain. Each miner checks this number, and will search the wallet (this is all automatic) for coins totaling the requirement and place these coins in an ABN Stake transaction - and then begin mining"

=

3. Is the ABN Stake transaction just coins going to the CPK address?
3.a. I havent noticed any of the CPK address transactions in my Transactions list, filter set to All, but I do notice coins moving around in Send >> Inputs (Settings >> Options >> Wallet >> Enable coin control features)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 28, 2019, 10:30:20 am
Ive tried to make masternode again now with 4500001 tBBP,
I was able to add it to masternode.conf and start it!

Now I just need to setup Watchman?

=

Also I got a popup message about masternodeblsprivkey
"BiblePay Core - Warning - You should specify a masternodeblsprivkey in the configuration. Please see documentation for help."

https://docs.dash.org/en/stable/masternodes/setup.html#generate-a-bls-key-pair

https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html#enter-the-bls-key-on-the-masternode
https://docs.dash.org/en/stable/masternodes/maintenance.html#updating-masternode-information
https://blog.dash.org/secret-sharing-and-threshold-signatures-with-bls-954d1587b5f

Im kind of confused how the bls keypair works

"The ProRegTx contains 2 Dash addresses (also called public keys) and one BLS public key, which represent 3 different roles in the masternode and define update and voting rights. The keys are:

ownerKeyAddr: This is a Dash address (public key) controlled by the masternode owner. It is different from the address used for the collateral. Because the owner uses the private key associated with this address to issue :ref:`ProUpRegTx <update-dip3-config>` transactions, it must be unique for each masternode.

operatorPubKey: This is the BLS public key of the masternode operator. Only the operator is allowed to issue :ref:`ProUpServTx <update-dip3-config>` transactions. Because the operator key is used during live masternode operation to sign masternode-related P2P messages, quorum-related messages and governance trigger votes, the BLS key must be unique for each masternode.

votingKeyAddr: This is a Dash address (public key) used for proposal voting. Votes signed with the corresponding private key are valid while the masternode is in the registered set."
https://github.com/dashpay/docs/blob/master/masternodes/understanding.rst

=

Masternode Setup:

https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

These are my old Masternode setup notes:
https://forum.biblepay.org/index.php?topic=190.msg3701#msg3701
https://forum.biblepay.org/index.php?topic=108.msg1444#msg1444

Attempt to use VNC:
https://forum.biblepay.org/index.php?topic=244.msg4525#msg4525
https://forum.biblepay.org/index.php?topic=244.msg4523#msg4523

Masternode guide:
http://wiki.biblepay.org/Create_Sanctuary_2
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 28, 2019, 10:43:00 am
Sorry for providing too little information about the Watchman environment; let me try to explain.

In Prod, we are running a 1.5 year old codebase with Dashs Sentinel in Python (we renamed it Watchman-on-the-wall) - and we still use it in prod as-is from Dash (and its still required today since it helps create the budgets etc, creates watchdogs, etc).

In Evo, I have not ported Sentinel to Watchman yet (so its unavailable still), so we do not have to Test it yet.

What I'm considering however, is porting Watchman to c++, so we don't have to run both watchman and Evo as separate programs in each sanc (in the future).  (Thats what this release info was about, but - its really just in step 1).  I'm still going to do some internal testing on my end, then provide more info as how we can test the integrated version of watchman, so please don't worry about testing that yet.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 01:40:09 pm
I was able to add it to masternode.conf and start it!

Now I just need to setup Watchman?

I believe we are the first masternode coin to have The Sentinel compiled into biblepaycore, so that means:
You do not have to install watchman-on-the-wall.  Its built in now, and its one of the things we started testing (so far successfully) but it needs a little more testing before prod.

It runs automatically also, so there are no settings to configure.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 01:46:09 pm
Ive tried to make masternode again now with 4500001 tBBP,
I was able to add it to masternode.conf and start it!

Now I just need to setup Watchman?

=

Also I got a popup message about masternodeblsprivkey
"BiblePay Core - Warning - You should specify a masternodeblsprivkey in the configuration. Please see documentation for help."

https://docs.dash.org/en/stable/masternodes/setup.html#generate-a-bls-key-pair

https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html#enter-the-bls-key-on-the-masternode
https://docs.dash.org/en/stable/masternodes/maintenance.html#updating-masternode-information
https://blog.dash.org/secret-sharing-and-threshold-signatures-with-bls-954d1587b5f

Im kind of confused how the bls keypair works

"The ProRegTx contains 2 Dash addresses (also called public keys) and one BLS public key, which represent 3 different roles in the masternode and define update and voting rights. The keys are:

ownerKeyAddr: This is a Dash address (public key) controlled by the masternode owner. It is different from the address used for the collateral. Because the owner uses the private key associated with this address to issue :ref:`ProUpRegTx <update-dip3-config>` transactions, it must be unique for each masternode.

operatorPubKey: This is the BLS public key of the masternode operator. Only the operator is allowed to issue :ref:`ProUpServTx <update-dip3-config>` transactions. Because the operator key is used during live masternode operation to sign masternode-related P2P messages, quorum-related messages and governance trigger votes, the BLS key must be unique for each masternode.

votingKeyAddr: This is a Dash address (public key) used for proposal voting. Votes signed with the corresponding private key are valid while the masternode is in the registered set."
https://github.com/dashpay/docs/blob/master/masternodes/understanding.rst

=

Masternode Setup:

https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt
Great on setting up a sanc!

So on the BLS key pair, the pro-reg, dip3, and deterministic sancs:

So we have a two step process for testnet:
Setting up a legacy cold non-deterministic sanctuary, using a masternodeprivkey only.  This is the way we have been doing it up til now (IE the old dash codebase from 2017 that is in biblepay-classic).

Step 2 (future - IE in about 1 more day):
We upgrade a legacy sanc to a deterministic sanc (also called a dip3 sanc).  These dip3 sancs do use 2 keypairs:  BLS and regular privkey, have reward addresses and voting addresses and all that other stuff. 

So what I would like to ask all of us to do is set up a *legacy* sanc first, and ensure it is running.  Then in a day or so, we will enable dip3 (after we ensure our anti-gpu and abn and all this is stable).  I will post instructions on how to upgrade , and this step will automatically create the BLS privkey and the second address.

For now you can ignore the BLS warning on boot, that is normal.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 01:52:02 pm
So, I'm stucked on block 50561 again.  It looks, that resync is waiting for me again. Rob, in few last days I've made more than 10 full resync (deleted everything from biblepaycore folder - like in Togos post) but it never took less than 2 hours for me.
Maybe it is problem of my PC, but we've talked about this before latest mandatory testnet.
May it be caused with mine huge activity in constant download of data from my peers? May I be blocked somehow?
Sometimes it starts withou problem, but after some time download fall to 10kB/s.
I can guarant that it is not caused with my internet connection.
I have now tho internet providers (300 Mbps and 500Mbps) and it is the same on both. So, it can be caused with my PC, but on my second PC it was the same. Slow connection with peers.

I have tried to set gen=0, but there is still problem with sync.
Here is part from my debug.log:
Code: [Select]
2019-04-28 13:55:37 ERROR: AcceptBlockHeader: block f5cbf4edfd4df18b3204ac8c72b44ba04296e0334d50a9d40e9b208f4f835913 is marked invalid
2019-04-28 13:55:37 ERROR: invalid header received

So, I'll start resync again with gen=0 and I'll see if the sync will be faster.
BTW: Rob, can you delete debug.log from WIN wallet install file?
It is in ...BiblepayEvolution\doc\ folder after install and it has more then 67MB :D I think that it is not neccessary for us ;)
There are some old logs from end of March.

Let me try to reproduce first and  Ill comment.  Maybe we can make a snapshot of the first 50,000 blocks.
The main thing is that we ensure blocks 50k+ don't have any checkblock errors in them so I dont want you to sync past any bad blocks and cover up a problem.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 28, 2019, 01:57:13 pm
Awesome, Thanks Rob!
Thank you for all of your hard work!
This is exciting!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 02:32:50 pm
So, I'm stucked on block 50561 again.  It looks, that resync is waiting for me again. Rob, in few last days I've made more than 10 full resync (deleted everything from biblepaycore folder - like in Togos post) but it never took less than 2 hours for me.
Maybe it is problem of my PC, but we've talked about this before latest mandatory testnet.
May it be caused with mine huge activity in constant download of data from my peers? May I be blocked somehow?
Sometimes it starts withou problem, but after some time download fall to 10kB/s.
I can guarant that it is not caused with my internet connection.
I have now tho internet providers (300 Mbps and 500Mbps) and it is the same on both. So, it can be caused with my PC, but on my second PC it was the same. Slow connection with peers.

I have tried to set gen=0, but there is still problem with sync.
Here is part from my debug.log:
Code: [Select]
2019-04-28 13:55:37 ERROR: AcceptBlockHeader: block f5cbf4edfd4df18b3204ac8c72b44ba04296e0334d50a9d40e9b208f4f835913 is marked invalid
2019-04-28 13:55:37 ERROR: invalid header received

So, I'll start resync again with gen=0 and I'll see if the sync will be faster.
BTW: Rob, can you delete debug.log from WIN wallet install file?
It is in ...BiblepayEvolution\doc\ folder after install and it has more then 67MB :D I think that it is not neccessary for us ;)
There are some old logs from end of March.

So, I think I have reproduced the same problem that you have (Im syncing from zero to 50558).  I'm running a deep analysis now with more logging to confirm the exact root cause at 50558.


In the mean time while I'm doing this, I think the speed problem has more to do with the latency from SK to the US servers (not the machine or the bandwidth).  Its a chatty process to download each block with all the back and forth confirms.

I recommend doing this for now (as most likely in prod, people will not be regularly syncing from 0 - although Im not against making a snapshot file in the future but we still have a pretty small block file).  Could you try this, delete all the normal files from earlier, and sync to block 50,000.  When it hits 50,000 click on File | Exit (do not pkill it, otherwise the flush may be bad on the blocks).  Then copy the "blocks","Chainstate" and "evodb" out to a subfolder (like /snapshot for instance).

Then when I post the resolution, just go back to 50K and start again for each testnet session.  (You can start back at 50K by removing the blocks, chainstate, evodb- and then copying the contents of your subfolder back to the appdata directory).

What I believe happened yesterday is when I set the evodb chainheight abnheight param we were at around block 50558 and I set it for 50560, meaning it didnt have enough blocks to propogate past the minimum for a newly syncing user from 0.  Meaning that I believe your node had memorized the prior height while checking the block (this is what Ive got running now in the background to double verify this before I release a fix).  If this is the case, we will have to bump a couple params and make a new release and all ensure we synced up past this height.


Btw, once you encounter a bad block you can forget trying to test the abn feature and the antigpu, because the wallet cant find proper coin age when its out of sync (or should I say its trying to build on faulty blocks on the wrong height etc).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 28, 2019, 02:40:47 pm
Ok. So, now I'm stucked on 50655 :D
I was away of my PC, so I'll try to sync it again to 50k and make a backup :)
I hope, I'll stop it in right time :D
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 02:41:11 pm
Awesome, Thanks Rob!
Thank you for all of your hard work!
This is exciting!
Thanks, Ill answer that CPK stuff soon, in the mean time
do you have blockhash 06af* for 52240? 
Also whats your IP for your sanc, Id like to see if it shows in my enabled list.
(You see 4 enabled in your sanc list correct)?
Are you in the leaderboard yet Togo, as I only have 5 participants there?



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 02:44:01 pm
Ok. So, now I'm stucked on 50655 :D
I was away of my PC, so I'll try to sync it again to 50k and make a backup :)
I hope, I'll stop it in right time :D

Thats because the wallet pulls more blocks after the problem until it cant (you can check the log for ERROR to see the real root problem really occurs "ABN ERROR!  Block 50558.000000 does not meet anti-bot-net-minimum required guidelines: BlockWeight 0.000000" at 50558. 
^ Thats got to be the real root problem in every log right now.

If you want you can exit even earlier at 49000 to give you more time - I would recommend that.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 03:12:34 pm
Thats because the wallet pulls more blocks after the problem until it cant (you can check the log for ERROR to see the real root problem really occurs "ABN ERROR!  Block 50558.000000 does not meet anti-bot-net-minimum required guidelines: BlockWeight 0.000000" at 50558. 
^ Thats got to be the real root problem in every log right now.

If you want you can exit even earlier at 49000 to give you more time - I would recommend that.

Also, I have successfully recovered a node with getchaintips just now, but lets go through that later, since we know we need another mandatory I dont want to confuse everyone right now.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 28, 2019, 03:13:13 pm
do you have blockhash 06af* for 52240? 
Also whats your IP for your sanc, Id like to see if it shows in my enabled list.
(You see 4 enabled in your sanc list correct)?
Are you in the leaderboard yet Togo, as I only have 5 participants there?

Im in agreement on blockhash for 52240
My masternode IP is:  108.61.194.83
I see 4 ENABLED masternodes

I never registered my cpk, so I just ran "exec cpk togo"

How do you view the leaderboard?
"exec prominence" is not working for me "Command not found"

Also do I need to run "exec join pog"?
Are POG and ABN different things?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 03:55:57 pm
Im in agreement on blockhash for 52240
My masternode IP is:  108.61.194.83
I see 4 ENABLED masternodes

I never registered my cpk, so I just ran "exec cpk togo"

How do you view the leaderboard?
"exec prominence" is not working for me "Command not found"

Also do I need to run "exec join pog"?
Are POG and ABN different things?

Ok great, just checking for my own sanity cause 5 participants seemed rather lonely.
Yes, I see your 108.61 as enabled, good deal.

So, when you ran the 'exec cpk togo' that did register your CPK.  (The Christian-Public-Keypair Address book entry can actually get created by another process, Ill explain that in the post when I reply to your other post).

So the exec prominence was changed to rpc command: leaderboard  (for ease of use).  Now you should see about 5 in there, but you will have to do a:
exec join pog
First, and then force out a GSC to get in the next superblock (exec sendgscc true). 

You can also view the leaderboard in QT by clicking "Leaderboard" (its like our old pog view).


So once you have a CPK, you are basically just in our list of CPKs (that lets you vote on future things and gives you voting weight depending on how much your average stake is).  You have to join pog in order to actually send GSC transmissions.

POG & abn are different:  POG is BiblePay campaign #1, proof-of-giving, its a hybrid stake/giving campaign requiring coin*age to get rewards, and a small component of it is POG (donations to the foundation).  These transmissions are one type.  ABN is another.

ABN is strictly for POW miners.  It adds the requirement to POBH mining to have coin age in each solved block.  So when your wallet is about to solve a POBH, it adds on the ABN with coin*age in it.  So each of these require distinct unlocks of the wallet for them to be successful.

Im adding the code now to support the autounlock command so people can type that in every time they boot.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 04:07:02 pm
Thanks for looking into things Rob!

=

1. So this coin splitting behavior is intended and happens automatically every so often? when mining? (and every wallet is now set to mine by default?)
1.a. Is an amount of 4500001 ignored for coin splitting? when user is setting up a masternode?
1.b. Does this mean new miners have to own some amount of BBP coins in their wallet to participate in mining? (but they can jump in to mine when block hasnt been solved for 60 minutes if they dont have coins?)

2. Also for the CPK, I noticed that I never ran a command (exec cpk my_nickname) to create one, is default behavior that one is created automatically? And the command is to just add a nickname to it?

=

Just poking around the documentation:

https://wiki.biblepay.org/Getting_Started_with_Evolution
https://wiki.biblepay.org/Generic_Smart_Contracts

GSC (Generic Smart Contract)
"The GSC is split into a client server architecture. The client side user joins campaigns with a CPK (Christian Public Keypair) and competes in these campaigns for points. The server side (our Sanctuaries) assess user points and tracks user progress. Once per day, the points are converted and paid in a Generic Smart Contract. The GSC is voted on by the Sanctuaries automatically at a certain chain height. The GSC is paid once per day as a superblock from BiblePay core, and is split among campaigns by points rewarded per campaign per user. "

ABN (Anti-BotNet)
"which requires a certain amount of coin*age to be present in each mined block in order to mine BiblePay"
"Our network requires an average calculated and pre-assessed static amount (posted in getmininginfo) of required coin*age and stores this in the chain. Each miner checks this number, and will search the wallet (this is all automatic) for coins totaling the requirement and place these coins in an ABN Stake transaction - and then begin mining"

=

3. Is the ABN Stake transaction just coins going to the CPK address?
3.a. I havent noticed any of the CPK address transactions in my Transactions list, filter set to All, but I do notice coins moving around in Send >> Inputs (Settings >> Options >> Wallet >> Enable coin control features)
On coin splitting -  There is no actual splitting.  We are just sending the transactions change back to you when you break a bill (the same as classic does).  The only new thing to know is if your wallet is about to create a GSCC transmission for the POG (or other) campaign(s), if it assembles a 1 million coin*age stake by using 1.1 million in coins, the 100,000 of change is sent back to your CPK (Christian-Public-Key) address.  This also happens if you make a 1.1 million ABN stake - the leftover change is sent back to your CPK.



"1. So this coin splitting behavior is intended and happens automatically every so often? when mining? (and every wallet is now set to mine by default?)"
->  This ABN transaction only occurs if you solve a POBH block, or create a new GSCC transmission.  These GSCCs are sent once an hour in testnet, and once every 24 hours in prod.

1.a. Is an amount of 4500001 ignored for coin splitting? when user is setting up a masternode?
->  Yes, any normal send from the Send UI works as classic does (no splitting, no difference in change, etc).


1.b. Does this mean new miners have to own some amount of BBP coins in their wallet to participate in mining? (but they can jump in to mine when block hasnt been solved for 60 minutes if they dont have coins?)
->  Yes, if the block is > 60 minutes (late block threshhold = true), anyone can mine it.  But yes, with ABN enabled on the network, with a 1000 minimum ABN weight, every mining use must have coin*age to mine.  So yes they would actually need biblepay to mine a POBH block.

2. Also for the CPK, I noticed that I never ran a command (exec cpk my_nickname) to create one, is default behavior that one is created automatically? And the command is to just add a nickname to it?
->  So on the CPK auto creation, when the wallet tries to mine, it realizes you had some coin*age for the ABN but you didn't have a CPK yet.  So it pre-created the wallet receive address for the CPK (and it is smart enough to re-use it when you register your cpk), so this is OK and normal.  This way it can re-access it for every ABN it tries to make.  (This also because you can mine BBP with just a plain old wallet with 5K in it for example and dont have to register your CPK or join any projects if you want to be simple).  I know we added a step to require BBP to mine BBP, but this is a tradeoff to enable the anti-bot-net weight rules.

Basically, we can make it harder for rich miners with hundreds of servers to keep pinching out the newbies if we ratchet up the minimum ABN weight requirement.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 28, 2019, 04:14:57 pm
Stucked again.
Block 50564.
log:
Code: [Select]
2019-04-28 20:52:36 {PNB}: ACC 
ContextualCheckBlock::ABN ERROR!  Block 50564.000000 does not meet anti-bot-net-minimum required guidelines: BlockWeight 0.000000, RequiredWeight 1000.000000ERROR: AcceptBlock: low-abn-weight, Insufficient ABN weight (code 16)
2019-04-28 20:52:36 Misbehaving: 193.187.180.41:40001 peer=1 (0 -> 1)
2019-04-28 20:52:36 ERROR: ProcessNewBlock: AcceptBlock FAILED: low-abn-weight, Insufficient ABN weight (code 16)
But good news is that my backup works :D
But....
next stuck block 50589:
Code: [Select]
2019-04-28 21:05:47 {PNB}: ACC 
ContextualCheckBlock::ABN ERROR!  Block 50589.000000 does not meet anti-bot-net-minimum required guidelines: BlockWeight 0.000000, RequiredWeight 1000.000000ERROR: AcceptBlock: low-abn-weight, Insufficient ABN weight (code 16)
2019-04-28 21:05:47 Misbehaving: 108.61.194.83:40001 peer=5 (0 -> 1)
2019-04-28 21:05:47 ERROR: ProcessNewBlock: AcceptBlock FAILED: low-abn-weight, Insufficient ABN weight (code 16)
2019-04-28 21:05:47  AntiGPU i 0.000000, CPK yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe      UpdateTip: new best=ffd3388b019833152c97333ad0b92c682decb88d52a0c2915d0c28197d078766 height=50543 version=0x20000001 log2_work=45.94637348 tx=143538 date='2019-04-27 21:55:43' progress=0.994223 cache=0.0MiB(0txo)
2019-04-28 21:05:48 {PNB}: ACC   AntiGPU i 0.000000, CPK ygavD5YuAJXpHDMLRyiiJ199YM5y9fTWfB      UpdateTip: new best=639d36532617d90194c7cb36e05e4c6b6130671377871fc2c054543eecd8a6bd height=50544 version=0x20000001 log2_work=45.94637566 tx=143540 date='2019-04-27 21:56:10' progress=0.994225 cache=0.0MiB(0txo)
2019-04-28 21:05:48 {PNB}: ACC  ERROR: ReadBlockFromDisk: OpenBlockFile failed for CBlockDiskPos(nFile=-1, nPos=0)
BTW: now i have gen=0 and unlocked wallet
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 04:17:32 pm
Thanks for looking into things Rob!


3. Is the ABN Stake transaction just coins going to the CPK address?
3.a. I havent noticed any of the CPK address transactions in my Transactions list, filter set to All, but I do notice coins moving around in Send >> Inputs (Settings >> Options >> Wallet >> Enable coin control features)

On #3,  Yes, its as if your wallet is finding enough coin*age, taking those coins, making a transaction to yourself, and sending those to your CPK address (which proves you owned that much coin*age).  It only does this however if you solved that POBH block.

On #3a, We do not show the ABN tx as a separate row on the txlist (because then you would see two entries for every block mined).  (This is the same behavior as we see in blackcoin and other staking systems) - it looks really cluttered if we do that.  You can see the tx though if you double click your mining reward, we show the debug info.  You can also get the txid and type : getrawtransaction txid 1, and see all the coins it used for the stake.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 04:19:38 pm
Stucked again.
Block 50564.
log:
Code: [Select]
2019-04-28 20:52:36 {PNB}: ACC 
ContextualCheckBlock::ABN ERROR!  Block 50564.000000 does not meet anti-bot-net-minimum required guidelines: BlockWeight 0.000000, RequiredWeight 1000.000000ERROR: AcceptBlock: low-abn-weight, Insufficient ABN weight (code 16)
2019-04-28 20:52:36 Misbehaving: 193.187.180.41:40001 peer=1 (0 -> 1)
2019-04-28 20:52:36 ERROR: ProcessNewBlock: AcceptBlock FAILED: low-abn-weight, Insufficient ABN weight (code 16)
But good news is that my backup works :D
But....
next stuck block 50589:
Code: [Select]
2019-04-28 21:05:47 {PNB}: ACC 
ContextualCheckBlock::ABN ERROR!  Block 50589.000000 does not meet anti-bot-net-minimum required guidelines: BlockWeight 0.000000, RequiredWeight 1000.000000ERROR: AcceptBlock: low-abn-weight, Insufficient ABN weight (code 16)
2019-04-28 21:05:47 Misbehaving: 108.61.194.83:40001 peer=5 (0 -> 1)
2019-04-28 21:05:47 ERROR: ProcessNewBlock: AcceptBlock FAILED: low-abn-weight, Insufficient ABN weight (code 16)
2019-04-28 21:05:47  AntiGPU i 0.000000, CPK yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe      UpdateTip: new best=ffd3388b019833152c97333ad0b92c682decb88d52a0c2915d0c28197d078766 height=50543 version=0x20000001 log2_work=45.94637348 tx=143538 date='2019-04-27 21:55:43' progress=0.994223 cache=0.0MiB(0txo)
2019-04-28 21:05:48 {PNB}: ACC   AntiGPU i 0.000000, CPK ygavD5YuAJXpHDMLRyiiJ199YM5y9fTWfB      UpdateTip: new best=639d36532617d90194c7cb36e05e4c6b6130671377871fc2c054543eecd8a6bd height=50544 version=0x20000001 log2_work=45.94637566 tx=143540 date='2019-04-27 21:56:10' progress=0.994225 cache=0.0MiB(0txo)
2019-04-28 21:05:48 {PNB}: ACC  ERROR: ReadBlockFromDisk: OpenBlockFile failed for CBlockDiskPos(nFile=-1, nPos=0)
BTW: now i have gen=0 and unlocked wallet

Yes, sorry, I was not clear  - actually I never got back to you yet :),  lol, we do need an upgrade here because I confirm that the height issue introduced about 48 hours ago causes all people who have to sync from below 50K to get stuck at your height, but the people already running are still running, thats why you are pulling your hair out.

Im working on trying to get the other suggestions in at the same time (like the autounlock feature).


So, Im glad you have your backup though to fall back to.  Ill notify asap as soon as its ready.





Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 28, 2019, 04:27:51 pm
Thank you for answering all my questions Rob!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 04:39:11 pm
Thank you for answering all my questions Rob!

No problem, so while we are discussing splitting, MIP had also asked about this, can we potentially not send the stake back to the CPK, but instead to an anonymous change address.  I investigated that today, and there are many issues here that surface - for one in order to prove that the CPK (who is registered) actually staked the amount, we currently send the coins to our own CPK and when we check the sig, we verify the recipient sig is the one who signed the coins.

So, although we could make a whole new scheme, I want to explain, my idea in the future is to take the average amount staked to each CPK per day, and use that for the CPKs voting weight (for those Christian object votable lists).  And for non-sanc polls (such as multi-choice community steering polls).  Another words, in this system we expose the users average free balance for voting weight.

So Im thinking what we do is when we create our training manual - for security concious individuals concerned with anonymity, we create a use case where users will generally create sancs with their anonymizable balances and lock those.
Then the non-anon part of Biblepay is your free balance.  This is used for GSC campaigns, mining, ABN staking, and voting. 

So I think this idea works relatively well to appease concerns from both camps.  We need to be anon-concious for investors, but we also need to be spreading the gospel and doing the cool things necessary on the public side with the CPKs.

The primary change in the future to make this a reality is to explain to the anon camp they will need to create cold storage addresses for their sanc outputs (not send them back to the hot wallet where our GSC will pick them up and convert them to CPK funds).


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 28, 2019, 05:16:24 pm
Yes, sorry, I was not clear  - actually I never got back to you yet :),  lol, we do need an upgrade here because I confirm that the height issue introduced about 48 hours ago causes all people who have to sync from below 50K to get stuck at your height, but the people already running are still running, thats why you are pulling your hair out.

Im working on trying to get the other suggestions in at the same time (like the autounlock feature).


So, Im glad you have your backup though to fall back to.  Ill notify asap as soon as its ready.
I can confirm that it's impossible to get over it (I've tried it so many times, but still nothing) :)
In the meantime, while I'll be waiting for mandatory I have few cosmetic update tips :)
1. I've looked so many times on "synchronization screen" that I realized it is based on biblepay-light theme and it would be better to have it based on biblepay-traditional theme, because it's more bezaleel friendly visual.
You can see it side by side here: https://prnt.sc/ni1npi
2. Other thing which disturbs me is min window height in bezaleel theme. It's 855px and it's impossible to make it smaller. When you change it to traditional theme it's only 740px which is better to me, but I think it can be even lower :)
Side by side here: https://prnt.sc/ni1p7r
3. Leaderboard button should be on left menu (like with POG).
4. Leaderboard sorting is not going well. It sorts badly. Try to sort it and it sorts based on first digit not by whole number. I haven't screenshot, because I'm not able to sync, byt you can try it :) This problem was in POG leaderboard too, but if I remember correctly MIP repaired it.
5. Leaderboard doesn't respect window width and when the window is smaller it just put there horizontal scrollbar. E.g. columns in tx view adjust their width based on window width and there is only vertical scrollbar. Maybe this problem is in other views (maybe proposals) but I'm not synced to confim that.

Maybe more tips will be after I'll be synced after new mandatory release :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 06:33:48 pm
I can confirm that it's impossible to get over it (I've tried it so many times, but still nothing) :)
In the meantime, while I'll be waiting for mandatory I have few cosmetic update tips :)
1. I've looked so many times on "synchronization screen" that I realized it is based on biblepay-light theme and it would be better to have it based on biblepay-traditional theme, because it's more bezaleel friendly visual.
You can see it side by side here: https://prnt.sc/ni1npi
2. Other thing which disturbs me is min window height in bezaleel theme. It's 855px and it's impossible to make it smaller. When you change it to traditional theme it's only 740px which is better to me, but I think it can be even lower :)
Side by side here: https://prnt.sc/ni1p7r
3. Leaderboard button should be on left menu (like with POG).
4. Leaderboard sorting is not going well. It sorts badly. Try to sort it and it sorts based on first digit not by whole number. I haven't screenshot, because I'm not able to sync, byt you can try it :) This problem was in POG leaderboard too, but if I remember correctly MIP repaired it.
5. Leaderboard doesn't respect window width and when the window is smaller it just put there horizontal scrollbar. E.g. columns in tx view adjust their width based on window width and there is only vertical scrollbar. Maybe this problem is in other views (maybe proposals) but I'm not synced to confim that.

Maybe more tips will be after I'll be synced after new mandatory release :)

I have #3 already, and I think Marcus can probably do #1 if  hes working on the new Bezaleel now, but Ill take care of all the rest for the next release.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 28, 2019, 08:13:14 pm
1.4.2.2b-Mandatory upgrade for TestNet

- In sendcoinentry, only add tithe validation if its a tithe
- Raise ABN starting height to 54000, and prevent chain from stalling
around 50000 due to a low abn height
- Add 2 params to getchaintips (minimum diff and minimum branch length)
- Add RPC command:  setautounlockpassword password (This allows the
gsc-transmissions or the abn transactions to automatically be created)
- Make ABN check more graceful to allow people syncing from 0 to sync to
the top
- Add Leaderboard to Left Menu
- Make leaderboard numeric columns sortable
- Decrease default bezaleel frame size to accomodate the sync modal page
- Decrease Leaderboard default grid size
- Correct PODC verbiage in autounlock

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 28, 2019, 10:49:13 pm
Upgraded to v1.4.2.2b

=

Yeah on the anonymous talk, I think its important for fungibility to have anonymity,
I also think its important for personal safety,
I think in the much much past you may have been open to disable PrivateSend?,
but it sounds like you may now lean more towards privacy/anonymity?

Also, I noticed in the evo docs theres a section about Tor
https://github.com/biblepay/biblepay-evolution/blob/master/doc/tor.md

Casa Node just added a Tor update
https://www.reddit.com/r/Bitcoin/comments/beu2zm/casa_releases_support_for_tor/

I really dont know much of anything about Tor,
Ive heard rumors/stories that most of the exit nodes have been compromised,
but anyways Id be open to testing it out for BiblePay
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 29, 2019, 08:17:32 am
Are we all in agreement:


08:15:36

getblockhash 53668


08:15:36

c9fbda30f682499ddbfe4516dca28d3bf5ded73caf36f8c65edd60a8394423bf


I only see a few pog participants in the leaderboard.

I do see 2 new sancs in New Start Required state though.


As a side note, ABN and AntiGPU are disabled til block 54000 hits then we can test those two again both from mining perspective and from syncing from 0.

Now we also should be testing the auto unlock password; ensure you can mine with a locked encrypted wallet, and ensure you can send a gscc also.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 29, 2019, 11:09:14 am
So, finally after upgrade I'm synced.
Mining is working and I'm waiting for GSC transmission :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on April 29, 2019, 11:33:04 am
Please try 'gen=0' in the biblepay.conf  first, then see if it reaches the top?
It is probably trying to mine every time the blocks pause.

Thanks (and also thank you Togo)!

I already tried deleting everything (including the 'SAN' folder) except my wallet.dat a couple of times, but that didn't help. I now upgraded to the latest version and put the gen=0 in my biblepay.conf. Let's see how that goes :)

I don't have a lot of spare time at the moment, but I'm going to try and keep up with you guys!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 29, 2019, 11:58:04 am
Looks like I went on a lone fork, I reindexed and Im back in agreement
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 29, 2019, 12:10:14 pm
we also should be testing the auto unlock password;
ensure you can mine with a locked encrypted wallet, and ensure you can send a gscc also.

I clicked Settings >> Encrypt Wallet

"getmininginfo" shows hashps

I tried to do "exec sendgscc true"
but I got message "Diary entry incomplete. (code -1)"
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on April 29, 2019, 12:48:48 pm
Thanks (and also thank you Togo)!

I already tried deleting everything (including the 'SAN' folder) except my wallet.dat a couple of times, but that didn't help. I now upgraded to the latest version and put the gen=0 in my biblepay.conf. Let's see how that goes :)

I don't have a lot of spare time at the moment, but I'm going to try and keep up with you guys!

Alright! Turning off mining seems to have helped :)

Does someone have tBBP for me so I can start a Sanctuary? I only got 400k left when I finally synced to the top.

yc4G3KS6ZSmGRb89LrLSECpRy6AHfEfy59

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 29, 2019, 02:52:49 pm
I send you some "change"
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 29, 2019, 03:18:33 pm
Alright! Turning off mining seems to have helped :)

Does someone have tBBP for me so I can start a Sanctuary? I only got 400k left when I finally synced to the top.

yc4G3KS6ZSmGRb89LrLSECpRy6AHfEfy59

I took a look at the problem we had and I think it was more related to the abn fork rules- I believe the gen=0 probably didnt help, anyway I also sent you some tBBP.

Good news, we are at over 5+ diff with ABN on, great.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 29, 2019, 03:22:32 pm
I clicked Settings >> Encrypt Wallet

"getmininginfo" shows hashps

I tried to do "exec sendgscc true"
but I got message "Diary entry incomplete. (code -1)"

Ok, we need to straighten out the docs, but let me re-clarify :

We used to need "true" in there in the first few versions to force the gscc so it would override the mining timer and send it.  Then later, I made this particular command always force it (as obviously they want to do it).  So you no longer need force=true.

So now its just two situations:  If you are a member of HEALING (exec join healing), you can do this:
exec sendgscc "healed a leper on the street"  ... (or prayed for someone, etc).

OR

exec sendgscc


In Case A, it will send the gscc to every applicable project PLUS ones that take diary entries.

In Case B, it will send it to all non-diary projects.


Good on the mining with a locked wallet, we are halfway there.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 29, 2019, 04:19:41 pm
Reporting back, I was able to run "exec sendgscc" with encrypted/locked GUI wallet,
Output:
{
 "Command": "sendgscc",
 "results": 1
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 29, 2019, 05:24:55 pm
Reporting back, I was able to run "exec sendgscc" with encrypted/locked GUI wallet,
Output:
{
 "Command": "sendgscc",
 "results": 1
}

Ok great!  (Ill be back on asap to answer those other security questions etc).

I discovered a bug today with ABN - this is a good one, now I can see why the network has been crawling soooo slow for the miners.

The ABN mining transaction needs a small adjustment.
For now the block solving speed is extremely slow.

I'm working on the patch.

We are close to moving on, I think these two issues are nearing completion.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 29, 2019, 05:32:33 pm
Thanks (and also thank you Togo)!

I already tried deleting everything (including the 'SAN' folder) except my wallet.dat a couple of times, but that didn't help. I now upgraded to the latest version and put the gen=0 in my biblepay.conf. Let's see how that goes :)

I don't have a lot of spare time at the moment, but I'm going to try and keep up with you guys!

We will probably have an update either in 6 hours or tomorrow morning, and I believe it will be a leisure.
Right now its slow to mine.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 29, 2019, 05:53:43 pm
Upgraded to v1.4.2.2b

=

Yeah on the anonymous talk, I think its important for fungibility to have anonymity,
I also think its important for personal safety,
I think in the much much past you may have been open to disable PrivateSend?,
but it sounds like you may now lean more towards privacy/anonymity?

Also, I noticed in the evo docs theres a section about Tor
https://github.com/biblepay/biblepay-evolution/blob/master/doc/tor.md

Casa Node just added a Tor update
https://www.reddit.com/r/Bitcoin/comments/beu2zm/casa_releases_support_for_tor/

I really dont know much of anything about Tor,
Ive heard rumors/stories that most of the exit nodes have been compromised,
but anyways Id be open to testing it out for BiblePay


Regarding me actually being against PrivateSend, I wouldn't say I am actually against it, I think what happened is 616West raised the concern a couple of times that if we are a Christian Crypto, why should we be touting private send features in a do-good environment (IE he was viewing this as why would a villain want to use biblepay if this is a Christian wallet).  And I know we have a savvy group, but what we have to communicate to people is Personal Safety Risk is real - IE there are cases where a normal Christian family has a few hundred grand in their 401k, and they might be the type of family that would rather move it to crypto (I know this sounds crazy to old timers, but look at the world, we may be in the end-times, etc, do you trust all the governments to do the right thing and print and print), anyway, lets say John Doe does move 300K into crypto, doesnt he have the right to remain anonymous and not get traced back to his IP and then have his crypto be taken at gunpoint?  So this issue really had more than one response, when I responded the one time that we should "hide" private send from the overview page, I was talking from a BBP UI perspective to make it easy to use - but I have never been against anonymity.  I think we need to educate the average user into knowing that anonymous features are not here to promote shady behavior from the ones trying to buy shady transactions, these features are here to protect the identity of people who want anonymous balances.

So to reiterate, I think BiblePay should provide two clear facilities, we should embrace Dash's features (untraceable balances) for investors, but we should also provide the public gospel side, and make it very clear in the training manual what could allow those two systems to intermingle.  (System A keeps balances in system A untraceable, while funds sent in System B are associated with a CPK and are public funds).  What this boils down to is if an anon investor intermingles their CPK with their cold storage sanc rewards (or cold locked Sanc collateral), they will expose their identity on the BX for everyone to see. 

So this is not about private send itself; its about starting to demarcate (all the components of every subsystem) in these two systems and make it easy to keep them separate, make sure our business logic doesnt allow breaking the rules and letting the anon user down, and we should also make a training manual for anon education.  We can be clear in our manual we are doing this to maintain the safety of the end user (not to promote shady behavior) inside BBP.

Actually Togo since you are excited about anon features if you want to take on the training manual, I will work with you to split the use cases and you can document them?

As far as Tor, I have never used it.  I sort of know how it works since I have a network engineering background.  Tor is basically going to be for people who are afraid another BBP endpoint would log their nodes IP (IP can be geo-located to your general block, now with Google streets sometimes down to the house number).  BBP does not store the IP (pools might), but all of this can be documented for anon users.  Tor is going to try to prevent the IP from being leaked (as you are coming in from the Tor point IP).  But as you said Tor might even be compromised - but there are other VPNs available for security concious individuals.

However, the IP is not as big of a problem as the actual anon balance.  The idea is if you can create an anonymous investor sanc balance, and never comingle your cold wallet rewards back to your CPK, then you are never going to be a public figure in the BX or a target for a villain (if they just see a key and a balance, they do not know your nickname and cant tie you to any other systems).  So I think this distinct goal is a worthy one for a page in the training manual alone.  You could make a separate endeavor to protect IPs.




Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 29, 2019, 10:41:50 pm
1.4.2.3-Mandatory Upgrade for TestNet

- Push ABN, GSC, and Anti-GPU errors up into getmininginfo errors
display
- Fix ABN bug preventing creation of ABN transactions (causing very slow
mining)
- Note: in 'exec getabnweight nnnnn' you can see the coin*age data
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 30, 2019, 09:20:32 am
Thank you for clarifying Rob!

Upgraded to v1.4.2.3 and did a reindex, ran into an error reading a bad block,
doing a full clean now and reindexing again

getblockhash 55072
002c22d0c230b*
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on April 30, 2019, 10:22:45 am
i have the same hash
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 30, 2019, 10:30:22 am
Reporting back, I was able to run "exec sendgscc" with encrypted/locked GUI wallet,
Output:
{
 "Command": "sendgscc",
 "results": 1
}

Hi.
So I've tested 1423 and mining is working with locked wallet perfectly.
But GSC is not working for me.
Like Togo, my I have
Code: [Select]
"results": 1, but no tx was made.
After wallet unlock it's working.
I've tried
Code: [Select]
exec sendgscc "healed a leper on the street" and it works too.
But when I tried
Code: [Select]
exec sendgscc "healed" there was
Code: [Select]
Diary entry incomplete. (code -1)Are there some restriction in sendgscc "text"?

Rob and can you explain me please how GSC exactly works?
When I run it for longer time it sends 4 GSC-Transmission (every hour) before I receive Smart-Contract-Payment.
How is the testnet speeded? Are those 4 hours like one day and it means that there were 4 GSC tx per day?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 30, 2019, 10:57:22 am
Thank you for clarifying Rob!

Upgraded to v1.4.2.3 and did a reindex, ran into an error reading a bad block,
doing a full clean now and reindexing again

getblockhash 55072
002c22d0c230b*

Looks like we match, good.
I see diff is at .31 - not too horrible.  We have 9 in the leaderboard, not horrible.

I dont know if anyone noticed this cool new feature in getmininginfo, but if your CPK triggered the anti-gpu latch you will see the error.  Its kind of cool to see you are the one who solved the last block.

(BTW, any errors in getmininginfo are cleared in about 3 minutes- this gives you a chance to see them).


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 30, 2019, 11:08:37 am
Hi.
So I've tested 1423 and mining is working with locked wallet perfectly.
But GSC is not working for me.
Like Togo, my I have
Code: [Select]
"results": 1, but no tx was made.
After wallet unlock it's working.
I've tried
Code: [Select]
exec sendgscc "healed a leper on the street" and it works too.
But when I tried
Code: [Select]
exec sendgscc "healed" there was
Code: [Select]
Diary entry incomplete. (code -1)Are there some restriction in sendgscc "text"?

Rob and can you explain me please how GSC exactly works?
When I run it for longer time it sends 4 GSC-Transmission (every hour) before I receive Smart-Contract-Payment.
How is the testnet speeded? Are those 4 hours like one day and it means that there were 4 GSC tx per day?

So, testing sending the gscc transmission with a locked encrypted wallet, with the 'setautounlockpassword' set, I just tested this, and my GSCC went, so its not the password causing it (if yours didnt send I recommend looking in your log under "CreateGSCTransmission::Fail::" and see if there is an error.  We do bubble the error to getmininginfo now also, but it is erased after 3 mins so check the log.  You can just run it again and look for the error).

Regarding the diary entry, it must be 10 chars or greater - so I just expanded that error message for the next version.

BTW, the most common GSC error is if you have a high setting set for your pog coinagepercentage (pog_coinagepercentage key) and you have more than 500 tx's in your wallet - check to see if they need consolidated once by going into coincontrol - and if they are not consolidated click Send some and consolidate the wallet first.   The error in the log would be something like GSC transaction size too large for a block.

We have 2.5 min blocks in testnet, so that means we end up with 4 GSC blocks per day (instead of 1 like prod).  And then we also have one GSC transmission per hour per project (instead of one per 24 hour in prod).  We only send ONE GSC per project - so that should mean you should see 2 per hour.     One for HEALING and one for POG.

I added the links for the docs for GSC to the OP post, let me know if there is still something that is unclear on GSC.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 30, 2019, 11:29:46 am
I just want to note, when I tested the encrypted/locked wallet, I didnt use: "setautounlockpassword", should I test again using that?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 30, 2019, 11:42:28 am
I just want to note, when I tested the encrypted/locked wallet, I didnt use: "setautounlockpassword", should I test again using that?

Hmmm, u mean u just manually unlocked it?  Yes, please test it with being locked and with only the setautounlockpassword set, that way it will confirm a locked user can abn mine and send gsc.

I tested last night successfully but more eyes are better.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on April 30, 2019, 01:04:01 pm
So all I did was encrypt the wallet, the wallet turned off, I turned it back on,
(so its just an encrypted/locked wallet, no setautounlockpassword, and no manual unlock)

and then I typed "getmininginfo", looking more carefully, it says I have hashps,
but in poolinfo3 says "Unable to create abn tx (wallet locked)"
and in gsc_errors says "POG: Sorry, wallet must be unlocked"

for "exec sendgscc", its the output
{
 "Command": "sendgscc",
 "results": 1
}
but I only see "Mined" transactions in my transaction list
Should it send a GSC Transmission transaction as soon as I run that command?

===

Testing now with "setautounlockpassword"

I typed "getmininginfo" again
poolinfo3 and gsc_errors are now empty

Im a little confused though, if my wallet has been locked this whole time,
Im still able to get "Mined" transaction rewards?

I typed "exec sendgscc"
and immediately saw a GSC Transmission transaction pop up
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 30, 2019, 01:29:49 pm
So all I did was encrypt the wallet, the wallet turned off, I turned it back on,
(so its just an encrypted/locked wallet, no setautounlockpassword, and no manual unlock)

and then I typed "getmininginfo", looking more carefully, it says I have hashps,
but in poolinfo3 says "Unable to create abn tx (wallet locked)"
and in gsc_errors says "POG: Sorry, wallet must be unlocked"

for "exec sendgscc", its the output
{
 "Command": "sendgscc",
 "results": 1
}
but I only see "Mined" transactions in my transaction list
Should it send a GSC Transmission transaction as soon as I run that command?

===

Testing now with "setautounlockpassword"

I typed "getmininginfo" again
poolinfo3 and gsc_errors are now empty

Im a little confused though, if my wallet has been locked this whole time,
Im still able to get "Mined" transaction rewards?

I typed "exec sendgscc"
and immediately saw a GSC Transmission transaction pop up

1.  Its a very, very complicated beast when you first boot.  To test this, please start the wallet encrypted, then type 'walletlock' then 'setautounlockpassword blah'.  The reason for this is an error is thrown when the first mining thread is started and you havent finished typing in the setautounlock, and that error is not cleared for 3 mins.  So you really have to disregard the first error in getmininginfo.
2.  After the error has cleared, then ensure you are mining with HPS and no errors with the setautounlockpassword only.
3.  I found out today that results:1 only means that sendgscc created a tx (but didnt necesarily send it).  So, I just removed it.  But i also see that *if* an error occurs, a ERROR row will also appear.  So please retest that, and just manually check the txlist to see if it was sent, and if it was then it passes.
4.  On the 'exec sendgscc', it should send one - if it didnt, check the log under CreateGSCC and see what the reason is - like I replied to Orbis - the reason is bubbled up to getmininginfo also.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 30, 2019, 01:30:03 pm
I've tested locked wallet with setautounlockpassword and it works.
Mining and gsc is working fine.
I've tested HEALING again aand yes there are two GSC txs right now.

I have few more questions and notes.
1. setautounlockpassword  command  is similar like -headlesspodcpassword? Because when you unlock it with setautounlockpassword headless linux it will be visible in bash history and cleaning it out is not effective.
2. Rob, I read those GSC docs, but I still don't understand how are points in HEALING counted. E.g. I sent exec sendgscc "text" and I have around 33k points, but you has more than 18.6M. And that is really huge difference :) Till now I was in HEALING campaign, but without Diary Entry, so I was without reward and only with 1 GSC tx. But like I see, there is only you in leaderboard within HEALING.
3. I understand it correctly, that If I want to be in HEALING I need to write diary entry every day?
4. How it will be controlled what is in HEALING diary entry? E,g, I can wrote there every day "My wife was prayed with our children before go to bed for ...", because they everyday pick someone who are they prayed for and I will be in every HEALING reward. Or I can wrote there some fairytale and if it is not controlled I'll be there too.
5. There could be some output e.g. exec healinginputs where can be visible all inputs.
6. Leaderboard output from menu item show only cumulative leaderboard. Would it be hard to get there some other buttons and after click show e.g. POG only and second button HEALING only leaderboard?
7. BTW, after the 1422 update and "Decrease Leaderboard default grid size" it's worst for me. Leaderboard window is smaller, with both scroller and not reflecting the GUI window size. Wallet window size cannot be smaller. And if you pick up Leaderboard from menu, it is not "lightened", there is lightened your previous view. In my case on screenshot it is "Send". Here is screenshot: https://prnt.sc/nit7gz
8. I've found that leaderboard true works, like exec prominenc true, so it's good :)
9. Now I'll be little personal. Rob, I think that we could be apolitical. It is not good to mess Biblepay with some political attitude. I'm writing about BiblePay_Healing_Campaign wiki page. I saw it before, but didn't tell anything even though if there were prayers in wallet, but now I saw it again and it's not good. Just take a look on last sentence: warfare example. I don't know how it looks in US, but here for most people is Trump with his behaviours and acts something like bad joke. And he is definitelly not good example of Christian. Many people has many political attitude, but most of Biblepay-related people are christians and I think it's not good to divide people with political themes.

And that's al for now :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on April 30, 2019, 01:51:15 pm
I've tested locked wallet with setautounlockpassword and it works.
Mining and gsc is working fine.
I've tested HEALING again aand yes there are two GSC txs right now.

And that's al for now :)




I have few more questions and notes.

1. setautounlockpassword  command  is similar like -headlesspodcpassword? Because when you unlock it with setautounlockpassword headless linux it will be visible in bash history and cleaning it out is not effective.

--->  Yes, and so would walletpassphrase (be visible in a bash history), what suggestion do you have, going back to the popup window in qt?



2. Rob, I read those GSC docs, but I still don't understand how are points in HEALING counted. E.g. I sent exec sendgscc "text" and I have around 33k points, but you has more than 18.6M. And that is really huge difference :) Till now I was in HEALING campaign, but without Diary Entry, so I was without reward and only with 1 GSC tx. But like I see, there is only you in leaderboard within HEALING.

---->  On Healing, it only pays 5% of the daily GSC budget (95% goes to POG).  But you must be reading wrong, I actually have 0 right now.  Do a 'leaderboard', take a look at the first 15 rows (only the rows that show healing).  Those rows add up to 5% of the GSC budget.  You are receiving 5% (all of it) and I am receiving 0.  Now on randrews in the pog budget, I have 76.9 million points (18.9%) of the gsc pog budget because on that machine, I mined 105,000,000 bbp and Im staking 50% of it (pog_coinagepercentage=.50), another words in real life, most people would have used 90% of that on sancs and I probably have 1 mil free (not 105 mil free for staking).  You can see how the payout works btw, if you take a gsc txid, and type 'exec getpoints txid' and it shows (you can see the coin*age*factor in the GSC payment doc example also).


3. I understand it correctly, that If I want to be in HEALING I need to write diary entry every day?

--->  You dont need to write one, but if you dont, you will be left out of that payment cycle.  So yes, but you can do it for : warfare, prayers, healing, driving out demons, etc.  Almost any Christian activity.



4. How it will be controlled what is in HEALING diary entry? E,g, I can wrote there every day "My wife was prayed with our children before go to bed for ...", because they everyday pick someone who are they prayed for and I will be in every HEALING reward. Or I can wrote there some fairytale and if it is not controlled I'll be there too.

---->  For now, God will monitor it (as it pays so low).  In the future at the end of the year approximately, we will have reputation scores. 


5. There could be some output e.g. exec healinginputs where can be visible all inputs.

---->  Yes, I love that, I did of course realize that, but let me add that to my punchlist now.  It would at least be useful for us to see the fruits of our labor on some type of scrolling view on the overview page .



6. Leaderboard output from menu item show only cumulative leaderboard. Would it be hard to get there some other buttons and after click show e.g. POG only and second button HEALING only leaderboard?

---->    Hmm, Ill add this to my list as a "potential nice to have todo", these either get passed to another dev, unless I have time ( as compared to some of the other priorities that come up around here day to day, like making the pool hashes work and testing with Capulo).


7. BTW, after the 1422 update and "Decrease Leaderboard default grid size" it's worst for me. Leaderboard window is smaller, with both scroller and not reflecting the GUI window size. Wallet window size cannot be smaller. And if you pick up Leaderboard from menu, it is not "lightened", there is lightened your previous view. In my case on screenshot it is "Send". Here is screenshot: https://prnt.sc/nit7gz

---->  Ok, I see its not expanding to the size of the window, I added this back to my todo list.



9. Now I'll be little personal. Rob, I think that we could be apolitical. It is not good to mess Biblepay with some political attitude. I'm writing about BiblePay_Healing_Campaign wiki page. I saw it before, but didn't tell anything even though if there were prayers in wallet, but now I saw it again and it's not good. Just take a look on last sentence: warfare example. I don't know how it looks in US, but here for most people is Trump with his behaviours and acts something like bad joke. And he is definitelly not good example of Christian. Many people has many political attitude, but most of Biblepay-related people are christians and I think it's not good to divide people with political themes.

----->  Its an overall good thing to encourage Christians to bear fruit through: spiritual warfare campaigns, healing the sick, casting out demons, praying (IE the things Jesus commanded us to do), spread the gospel etc.  Your specifically talking about my use of Trump as an example in a wiki.  So yes, we should make it a different example (thats all). 

As far as Trump being a good Christian himself, (and the following paragraph is Not related to BiblePay in any way, its my personal view):   We know here in the US that Trump came from a prior life of sinful activities, owning a gambling casino and had many wives, but a Christian can also repent- and the point is that we are not saying we are behind Trump because he is the savior of the US, we are behind him because we view he is our chosen Cyrus, that God can Use anyone for his master plan, and Trump is here to represent Christians in the best way possible in this broken world.  This means giving us extended grace, not caving to the NWO, helping usher in the end times, building the 3rd temple, provoking Ezekiel 38, etc.  Its the opposite of being rounded up into fema camps and being beheaded.  So this spiritual warfare campaign is strictly to protect the president from harm, let him not be slandered, and be a vessel for Gods will in America.  Its just one of many exampels of possible warfare.  One good example is praying for the welfare of Slovakia, to break demonic strongholds down in all your cities and that Gods precious gospel may penetrate deep in all those strongholds.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on April 30, 2019, 02:41:47 pm
1. setautounlockpassword  command  is similar like -headlesspodcpassword? Because when you unlock it with setautounlockpassword headless linux it will be visible in bash history and cleaning it out is not effective.

--->  Yes, and so would walletpassphrase (be visible in a bash history), what suggestion do you have, going back to the popup window in qt?
I took a look on that in GUI console there is no problem. After command I can use "clear console" and commands are gone. But in headless it's more complicated. But if -headlesspodcpassword still worked it is solved :) If not, put the -headlesspodcpassword there againd and it will be solved ;)

2. Rob, I read those GSC docs, but I still don't understand how are points in HEALING counted. E.g. I sent exec sendgscc "text" and I have around 33k points, but you has more than 18.6M. And that is really huge difference :) Till now I was in HEALING campaign, but without Diary Entry, so I was without reward and only with 1 GSC tx. But like I see, there is only you in leaderboard within HEALING.

---->  On Healing, it only pays 5% of the daily GSC budget (95% goes to POG).  But you must be reading wrong, I actually have 0 right now.  Do a 'leaderboard', take a look at the first 15 rows (only the rows that show healing).  Those rows add up to 5% of the GSC budget.  You are receiving 5% (all of it) and I am receiving 0.  Now on randrews in the pog budget, I have 76.9 million points (18.9%) of the gsc pog budget because on that machine, I mined 105,000,000 bbp and Im staking 50% of it (pog_coinagepercentage=.50), another words in real life, most people would have used 90% of that on sancs and I probably have 1 mil free (not 105 mil free for staking).  You can see how the payout works btw, if you take a gsc txid, and type 'exec getpoints txid' and it shows (you can see the coin*age*factor in the GSC payment doc example also).
Ok, now I look myself with 5% but before it was you with 4,99% and me with 0,01% with those points. I've tried to figure it out, but I'm still confused :D It's better to use pog_coinagepercentage=.25 and has bigger coin_age or pog_coinagepercentage=1 and has lower coinage? :)

9. Now I'll be little personal. Rob, I think that we could be apolitical. It is not good to mess Biblepay with some political attitude. I'm writing about BiblePay_Healing_Campaign wiki page. I saw it before, but didn't tell anything even though if there were prayers in wallet, but now I saw it again and it's not good. Just take a look on last sentence: warfare example. I don't know how it looks in US, but here for most people is Trump with his behaviours and acts something like bad joke. And he is definitelly not good example of Christian. Many people has many political attitude, but most of Biblepay-related people are christians and I think it's not good to divide people with political themes.

----->  Its an overall good thing to encourage Christians to bear fruit through: spiritual warfare campaigns, healing the sick, casting out demons, praying (IE the things Jesus commanded us to do), spread the gospel etc.  Your specifically talking about my use of Trump as an example in a wiki.  So yes, we should make it a different example (thats all). 

As far as Trump being a good Christian himself, (and the following paragraph is Not related to BiblePay in any way, its my personal view):   We know here in the US that Trump came from a prior life of sinful activities, owning a gambling casino and had many wives, but a Christian can also repent- and the point is that we are not saying we are behind Trump because he is the savior of the US, we are behind him because we view he is our chosen Cyrus, that God can Use anyone for his master plan, and Trump is here to represent Christians in the best way possible in this broken world.  This means giving us extended grace, not caving to the NWO, helping usher in the end times, building the 3rd temple, provoking Ezekiel 38, etc.  Its the opposite of being rounded up into fema camps and being beheaded.  So this spiritual warfare campaign is strictly to protect the president from harm, let him not be slandered, and be a vessel for Gods will in America.  Its just one of many exampels of possible warfare.  One good example is praying for the welfare of Slovakia, to break demonic strongholds down in all your cities and that Gods precious gospel may penetrate deep in all those strongholds.
Ok, whatever :) I just thought that being apolitical is good idea.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 01, 2019, 11:00:54 am
I was thinking, maybe we should make the POBH miner chain a chunk of verses together in succession, so when we look at a block, we can actually read a coherent passage. 

(Currently we chain them together with math pointers, but we could point to a section, then get 7 verses for example after that verse, and that would let people read something that makes sense when they look at a block).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 01, 2019, 04:57:47 pm
I took a look on that in GUI console there is no problem. After command I can use "clear console" and commands are gone. But in headless it's more complicated. But if -headlesspodcpassword still worked it is solved :) If not, put the -headlesspodcpassword there againd and it will be solved ;)
Ok, now I look myself with 5% but before it was you with 4,99% and me with 0,01% with those points. I've tried to figure it out, but I'm still confused :D It's better to use pog_coinagepercentage=.25 and has bigger coin_age or pog_coinagepercentage=1 and has lower coinage? :)
Ok, whatever :) I just thought that being apolitical is good idea.

1.  Yes, probably good to be neutral politically.  I edited the Trump to be a different campaign for breaking demonic strongholds.  (Note that this is really an idea where if we organize properly, we can use this campaign as a biblepay spiritual warfare campaign for a specific purpose in the future - like anti-witchcraft for Trump for example).

2.  Good idea on the headless password, I forgot how smart we were in the past.  I just ported the headlesspassword option and improved it a little (IE it just takes the -headlesspassword arg, then it presents the input box) - ill explain it in the next version.

3.  I modified the leaderboard UI page dimensions and set the stretch property, will be in the next version.  ( I also made that left menu set as the checked color, btw ).

4.  On the issue where I am consuming all the rewards for healing, to give you a better example, I just sent one.  Since this node has 100 mil, and I have the coinagepercentage set for .10%, when I sent my diary entry, it used 10 mil in the stake.  So, please see this txid:  exec getpoints txid:  b242e6c0c6844c474e791294d50b9379f4f24141ec8a529ef0d852d962e739d9.  You will see the Heal rules are like this :  Coin Amount * Coin Age = Points, as long as the diary entry is => 10 chars long.  Now you can make one on your end and compare the points and will probably see how it works.  Now you can also see that there is no real advantage between heal and POG either (since both use coin age).


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 02, 2019, 07:27:31 am
Hi Guys,

I'm having trouble getting the GUI wallet to start in Xubuntu 18.04. I've followed all the installation instructions (coupled with Togo's remarks) and as far as I know everything went correctly.

But when I try to start the wallet with the ./biblepay-qt command, it says:
Quote
[email protected]:~/biblepay-evolution/src$ ./biblepay-qt
bash: ./biblepay-qt: No such file or directory

I think that the headless version starts fine (./biblepayd). The testnet folder etc was created when I started the wallet this way. But when I try to cli into it, it says:
Quote
error: Could not locate RPC credentials. No authentication cookie could be found, and no rpcpassword is set in the configuration file (/home/bible/.biblepayevolution/biblepay.conf)

I know it' s not a lot of information, but does someone have a clue what could it going wrong?


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 02, 2019, 08:59:33 am
Hi Guys,

I'm having trouble getting the GUI wallet to start in Xubuntu 18.04. I've followed all the installation instructions (coupled with Togo's remarks) and as far as I know everything went correctly.

But when I try to start the wallet with the ./biblepay-qt command, it says:
I think that the headless version starts fine (./biblepayd). The testnet folder etc was created when I started the wallet this way. But when I try to cli into it, it says:
I know it' s not a lot of information, but does someone have a clue what could it going wrong?
I think these two are easy ones, but Im not sure  :)

1) To start biblepay-qt:
cd ~/biblepay-evolution/src/qt
./biblepay-qt -conf=biblepaytest.conf

(I believe you were one level down)


2) To get past the rpc error:
cd ~/biblepay-evolution/src
./biblepayd
....
In another terminal, run
./biblepay-cli

(The RPC is thrown if biblepayd is not running)


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 02, 2019, 09:34:38 am
Note:  A release is coming in approx 45 mins.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 02, 2019, 10:08:06 am
1.4.2.4-Mandatory Upgrade for TestNet

- Add scrolling diary entries (over last 30 days) to overview page
- Ensure the daily GSC budget does not go overbudget due to QT changes,
and allow the Sanc Quorum to downvote an overbudget gsc contract
- Modify POBH-Evo to produce consecutive chained bible verses.  We now
produce 7 consecutive verses from the starting point.  This allows the
user who does a 'getblock height' to actually read the passage
coherently.
- Make the Leaderboard UI support both a Summary or Detail view (this
allows users to view the Healing campaign detail rows). (Fixed the grid
size also, and the left menu click activation color).
- Add the headless autounlock password.  (This allows the password to be
entered via biblepay cli and not enter the bash history) - Usage:
./biblay-cli -headlesspassword <enter>
Biblepay Prompts for headless password
Enter the headless password <enter>
BiblePay shows the length.
To verify biblepay is using the password:  Type ./biblepay-cli
autounlockpasswordlength (verify the length is correct).
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 02, 2019, 10:48:02 am
So looking at the last N blocks, I see ABN is working 100% successfully (and we have it on full enforcement mode, meaning the chain will fork if its violated- its been this way since 54000).  I also see the anti-gpu feature has been working properly. 

I see we have reached QT level 60% (the cap).  I'm going to let it sit here for about 8 superblocks and watch things, and ensure we all stay synced with these 3 features.  Then I plan on changing the QT spork cap to 0 (simulating as if BiblePays price surpassed the threshhold of .01 cents, so we can simulate a reversal in QT).  Id like to ensure we can weather a reversal back to 0 QT% without any forks.

We can also test the dip3 deterministic sanc upgrade very soon.

Lets take a look at the scrolling diary entries today and ensure they match the 'exec datalist diary'.  (This is similar to exec datalist prayer).

As far as Watchman, we should do some more testing with that.  Lets do that as soon as the 4th sanc is online and enabled.  Lets enter some more fake proposals and watch the ones that get voted on before the next governance height.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 02, 2019, 02:06:24 pm
I think these two are easy ones, but Im not sure  :)

1) To start biblepay-qt:
cd ~/biblepay-evolution/src/qt
./biblepay-qt -conf=biblepaytest.conf

(I believe you were one level down)


2) To get past the rpc error:
cd ~/biblepay-evolution/src
./biblepayd
....
In another terminal, run
./biblepay-cli

(The RPC is thrown if biblepayd is not running)

I feel so dumb about the first one  :-X Of course I needed to run it from the qt path. I did it like that in the past, but somehow I forgot.

Didn't know about the second one. Thanks! Now I can finally try and start my Sanctuary :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on May 02, 2019, 03:02:48 pm
1.4.2.4-Mandatory Upgrade for TestNet


Rob, thanks for hearing and implementation of my requirements :)
Leaderboard looks good, but sorting by first two columns includes leaderboard stats too (nickname, points, diff, ...) and my nickname is not highlighted.
Healing Campaign results works but :)
sometimes it doesn't show whole text for me. If the diary entry is longer it is not showed correctly.
You can see it on my screenshot: https://prnt.sc/njmv3a
There is place on the bottom right corner which is not used and it could be used like I sketched :) Or there could be more tx's.
I've tried to sent diary entry with different symbols from send menu and from console and both works, but when I sent it from Send menu it sent only one tx instead of two when it was sent from console.
And when I sent diary entry from Send menu it asks me for password even if my wallet was unlocked with setautounlockpassword. Maybe that is the problem.
Thanks for headlesspassword getting back without arg :)
I'll definitely use it in my VPS.
And next tip for your maybe-to-do list :D
What about to put Bible verses of mined block to tx detail? I'm still looking there and it's thing that I missed. And hash too :)
My idea: https://prnt.sc/njnlbl

And sorry, that I'm still complaining :D
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on May 02, 2019, 04:08:53 pm
I have an error from my VPS which I am sure does not have a GPU, but does not appear to have any consequences as I am still able to receive immature 3500 tBBP payments which I presume to be mining rewards.

from getmininginfo:

{
  "blocks": 58834,
  "currentblocksize": 1842,
  "currentblocktx": 2,
  "difficulty": 0.05928717518932814,
  "errors": "",
  "pooledtx": 0,
  "chain": "test",
  "genproclimit": 6,
  "networkhashps": 877889.1198299188,
  "hashps": 306.3897603130411,
  "minerstarttime": "05-02-2019 19:13:20",
  "hashcounter": 2062114,
  "pooledtx": 0,
  "chain": "test",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "gsc_errors": "anti-gpu triggered on my CPK",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 1000
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on May 02, 2019, 05:11:52 pm
I have an error from my VPS which I am sure does not have a GPU, but does not appear to have any consequences as I am still able to receive immature 3500 tBBP payments which I presume to be mining rewards.

from getmininginfo:

{
  "gsc_errors": "anti-gpu triggered on my CPK",
}
I have same error too.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on May 02, 2019, 05:21:05 pm
I cleaned wallet and reindexed, and restarted masternode

getblockhash 58859
6a0005b2*

Do I match?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on May 02, 2019, 05:37:39 pm
I cleaned wallet and reindexed, and restarted masternode

getblockhash 58859
6a0005b2*

Do I match?

6a0005b24145a7bdcfb9e7c245342f400a48f18d12a8a9f8b5cd7052190f99a8

matches with my sanc. I seem not to be able to bring more than one sanc online as each time I send create a new address and send the locked funds to the (self) address on the controlling wallet, when I type masternode outputs, the previous output is overwritten and my previously enabled sanc goes missing...
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 02, 2019, 09:26:36 pm
Rob, thanks for hearing and implementation of my requirements :)
Leaderboard looks good, but sorting by first two columns includes leaderboard stats too (nickname, points, diff, ...) and my nickname is not highlighted.
Healing Campaign results works but :)
sometimes it doesn't show whole text for me. If the diary entry is longer it is not showed correctly.
You can see it on my screenshot: https://prnt.sc/njmv3a
There is place on the bottom right corner which is not used and it could be used like I sketched :) Or there could be more tx's.
I've tried to sent diary entry with different symbols from send menu and from console and both works, but when I sent it from Send menu it sent only one tx instead of two when it was sent from console.
And when I sent diary entry from Send menu it asks me for password even if my wallet was unlocked with setautounlockpassword. Maybe that is the problem.
Thanks for headlesspassword getting back without arg :)
I'll definitely use it in my VPS.
And next tip for your maybe-to-do list :D
What about to put Bible verses of mined block to tx detail? I'm still looking there and it's thing that I missed. And hash too :)
My idea: https://prnt.sc/njnlbl

And sorry, that I'm still complaining :D

Thanks for the suggestions.
These are all ready to go in the next version.
Btw, I liked that idea about the verses in the txlist drill in page!  Looks good.

Btw, I noticed that particular diary entry you have in your screen shot (with the TX_OUT stuff in it).  Although this is moot now (since the next version has a wide display), that particular diary entry is not in my exec datalist diary 999.  I think thats a very old corrupted entry when we first started testing.  If you delete your /SAN -r directory and restart, you should see that one purged.  (It would not have been a run-on sentence without the strange field).   Moot anyway, it will work itself out on the next version.

On the diary entry only sending One from the Send Money UI, thats normal because we only send the Healing GSC transmission from that action (but the miner iterates through every applicable project).  A user has to manually type exec sendgscc to send a POG manually.

Let me ponder about that walletpassphrase issue from send money.  I suppose we could use the passphrase.  Adding to my todo list now.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 02, 2019, 09:29:50 pm
I have an error from my VPS which I am sure does not have a GPU, but does not appear to have any consequences as I am still able to receive immature 3500 tBBP payments which I presume to be mining rewards.

from getmininginfo:

{
  "blocks": 58834,
  "currentblocksize": 1842,
  "currentblocktx": 2,
  "difficulty": 0.05928717518932814,
  "errors": "",
  "pooledtx": 0,
  "chain": "test",
  "genproclimit": 6,
  "networkhashps": 877889.1198299188,
  "hashps": 306.3897603130411,
  "minerstarttime": "05-02-2019 19:13:20",
  "hashcounter": 2062114,
  "pooledtx": 0,
  "chain": "test",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "gsc_errors": "anti-gpu triggered on my CPK",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 1000
}

This is normal, it means your CPK has solved the last block in testnet and is prevented from mining until someone else solves the next block.

In testnet - we only enforce N-1, but in prod N-1 through N-4 must be distinct.

This error should clear once someone else solves a block.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 02, 2019, 09:31:11 pm
6a0005b24145a7bdcfb9e7c245342f400a48f18d12a8a9f8b5cd7052190f99a8

matches with my sanc. I seem not to be able to bring more than one sanc online as each time I send create a new address and send the locked funds to the (self) address on the controlling wallet, when I type masternode outputs, the previous output is overwritten and my previously enabled sanc goes missing...

Yeah this is by design (part of Dash).  Basically you can do one of two things:
Either send yourself 4,500,001, then go to coin control and right click and Lock the funds you just sent to yourself, Or
B) You can add the entry to your masternode.conf file, and then restart the wallet, and the funds will be locked, then create the next sanc.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 02, 2019, 09:34:08 pm
I cleaned wallet and reindexed, and restarted masternode

getblockhash 58859
6a0005b2*

Do I match?

Hmmmm,  I kind of thought we had this fork ever since block 57800 or so (this is when I added the overbudget rule to the last mandatory).

Whats strange is I resynced a couple sancs and ended up on the .10 chain (I think you guys are on the .05 chain).
I assume you guys are all running without sancs?  Solving empty superblocks?  You can tell by looking at Sanctuaries | All.  You should not see my 3.

Let me re-index a couple sancs and see if I end up on my same chain.  Its 4 of us - uptimeminer, plus my 3.
Maybe your nodes have banned mine, thats why we didnt resync, when we reindex we should also delete the banlist.dat file.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on May 03, 2019, 02:07:35 am
1.4.2.4-Mandatory Upgrade for TestNet


Daemon/cli for Linux amd64, available here
https://www.biblepay.org/biblepayd-1.4.2.4-x86_64-pc-linux-gnu.tar.gz

And MacOS QT version here
https://www.biblepay.org/biblepaycore-testnet.dmg
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on May 03, 2019, 02:22:38 am
Yeah this is by design (part of Dash).  Basically you can do one of two things:
Either send yourself 4,500,001, then go to coin control and right click and Lock the funds you just sent to yourself, Or
B) You can add the entry to your masternode.conf file, and then restart the wallet, and the funds will be locked, then create the next sanc.

Thank you for your advice, Rob. (2) worked for me. For (1), when I tried to lock the "unlocked" coins using "toggle lock state" button, the "locked" become "unlocked" and vice versa.

I thought I would try multiple sancs in testnet since it I would not be able make any on the mainnet with the new requirements....  :'(

We should all be on the same chain as I can see all 10 testnet sancs.

getblockhash 59604
3e5dffdc3509a0d4e32915fe2a7b7025b998591e2a0303d1df3b47e52cc0dc61


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 03, 2019, 08:02:03 am
Thank you for your advice, Rob. (2) worked for me. For (1), when I tried to lock the "unlocked" coins using "toggle lock state" button, the "locked" become "unlocked" and vice versa.

I thought I would try multiple sancs in testnet since it I would not be able make any on the mainnet with the new requirements....  :'(

We should all be on the same chain as I can see all 10 testnet sancs.

getblockhash 59604
3e5dffdc3509a0d4e32915fe2a7b7025b998591e2a0303d1df3b47e52cc0dc61

Ok great, thanks.

Yes, it looks like now we are all on the same chain.

My hypotheses on part of the network going out of sync during upgrades is I think one of our nodes bans a network segment, that segment mines on its own with higher hashpower than my 3 sancs, the other half starts rejecting my sancs blocks (and vice-versa) and then a day after this higher POW chain is established then I upgrade.  At least its happened like this a few times now.

Either way we are all synced now, but we must do some thorough analysis over the next 14 days to ensure we dont have any "ERROR"'s in the log pointing to any fork rules or bad checkblocks as we must get all these problems worked out before prod preferably this month as I would really like to go live in June.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 03, 2019, 08:11:56 am
So, I see we still have people playing games with the Diary entries (the kind of babies who ruin it for everyone else in the class, but vengeance is not ours, its God's).

Either way, we can't go to prod with the ability for a demonically controlled derelict to deface BiblePays overview page.

So I thought about options this morning, but I want people to be aware, I would rather wait and finish a really nice feature for biblepay properly, so we have something to be proud of, the feature that allows upvoting-downvoting of Christian content lists, and this is not going to be ready in time for the Evo release (as it is also waiting for another dependency that is being programmed). 

In light of that I think a good temporary measure that we can use (until approx the end of the year when the above is ready) is I will add a spork containing the list of CPKs that did not deface and use this to bubble up those those diary entries to the UI. 

At the end of the year we can roll out something that will allow upvoting-downvoting and affecting the reputation score of the actual CPK and the content, then we can add business logic that will show or not show things based on these instead.

PS Although I regretfully was joking about 'Healed a leper', now lets change and put in encouraging things in going forward.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 03, 2019, 02:49:12 pm
1.4.2.5-Mandatory Upgrade for TestNet

- Added our bible verses to the txlist details (this is the txlist
double click drill in ui)
- Made the Leaderboard highlight work again, and sorting only on the
numeric cols
- Add ability to send diary entry using the autounlockpassword without
prompting the user for the wallet to be unlocked from the send coins
entry page
- Made prayer and diary entries on overview page take up the entire
width, diary entries be from reputable cpks, and diary entries to span
up to 7 days old to be included in the scrolling overview
- Made sancs reward 0 points to those who tithe 666 variations to the
foundation (we received 13,000 tithes for 666 variations)
- Make nickname visible on diary entry
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 03, 2019, 05:32:55 pm
Note:

We have a vagrant trying to hack biblepay (someone who is not God Fearing).

I say this because I feel we are creating a tool (BiblePay) - to help spread the gospel to IT geeks, and to blockchain enthusiasts, and we are helping orphans.
Therefore this project is doing Gods will.

Please everyone stop testing until the next version is ready.

Thanks.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 03, 2019, 09:02:46 pm
1.4.2.6-Mandatory Upgrade for TestNet

- Prevent tithe spam in memory pool
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on May 03, 2019, 09:16:54 pm
Upgraded masternode earlier to v1.4.2.5, upgrading again to v1.4.2.6
Ive just been upgrading, havent been testing anything lately (but still interested to try out TOR)

Keep fighting the good fight Rob!
Every attack makes BiblePay stronger!

Bitcoin Security: Bubble Boy and the Sewer Rat by Andreas Antonopoulos
https://www.youtube.com/watch?v=810aKcfM__Q
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 04, 2019, 01:38:48 am
I've upgraded to the latest version, and finally got my Sanctuary working :)

I don't have a lot of spare time, but if I can help with anything specific, just let me know!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 08:37:20 am
Upgraded masternode earlier to v1.4.2.5, upgrading again to v1.4.2.6
Ive just been upgrading, havent been testing anything lately (but still interested to try out TOR)

Keep fighting the good fight Rob!
Every attack makes BiblePay stronger!

Bitcoin Security: Bubble Boy and the Sewer Rat by Andreas Antonopoulos
https://www.youtube.com/watch?v=810aKcfM__Q
Yeah, thanks.  It appears we have mitigated the problem.

Good video, I watched it.  Its funny how he calls each bitcoin node a sewer rat. 

Regarding Tor, this will just ensure the user does not reveal their IP to biblepay, but like I said in one of the prior posts, biblepaycore does not store the IP anywhere (so it is more of a precautionary measure for one of those ultra-secure hackers who have an identity to protect like maybe Satoshi).  It would actually be more important to tor into a pool (as the third party services like forum.biblepay, pools, and any web code generally stores the IP all over the place - every major web server stores the IP in the logs even without a dev writing a line of code - bitcointalk stores IPs etc).   (Plus you mentioned Tors endpoints are probably infected anyway).

Impo Im still really concerned with the user being empowered on how to create an anonymous and untraceable cold wallet balance with sancs attached  (and wth those rewards going to an anon cold address also).

Well it looks like everyone resynced in this version thats nice we have 1.0 diff.  Hash:
getblockhash 62042
4d32aab9042e18a6ecc2229875b0e94499204be423e4084bd18076c02f7e2748
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 08:42:28 am
I've upgraded to the latest version, and finally got my Sanctuary working :)

I don't have a lot of spare time, but if I can help with anything specific, just let me know!
Great, well I see 6 enabled now - thats great.  For some reason only 4 voted.   Maybe 2 upgraded synced and shut off.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 08:51:34 am
Great, well I see 6 enabled now - thats great.  For some reason only 4 voted.   Maybe 2 upgraded synced and shut off.

Well I guess we can test Watchman (we now have it integrated into the core wallet) so we no longer need the python watchman-on-the-wall with Evo.

I see someone was nice enough to create one proposal just now (Coinmarketcap ad).

Lets all add a proposal and see if it pays right.

Ill add a couple right now.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 10:13:11 am
One of the prerequisites before we upgrade to deterministic sancs is SPORK6 (New signatures).

I just set it to Enabled, lets make sure we dont fork next. 

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 10:31:02 am
I just enabled InstantSend autolocks.  I believe this feature allows us to instantly send money and get an immediate 6 confirms for the receiver.

If anyone wants to paste their address I can send some IX to you ?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 04, 2019, 11:51:40 am
Great, well I see 6 enabled now - thats great.  For some reason only 4 voted.   Maybe 2 upgraded synced and shut off.

Hmm... My Sanctuary seems to have gone missing... And I can only see 4 in total, all of which say 'PRE-ENABLED', My own Sanctuary wallet says "Not capable masternode: Masternode not in masternode list"...

The hash for both my wallets for block 62042 is the same as yours though...


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 04, 2019, 11:54:32 am
I just enabled InstantSend autolocks.  I believe this feature allows us to instantly send money and get an immediate 6 confirms for the receiver.

If anyone wants to paste their address I can send some IX to you ?

yfBWKnEBzhwGMK9cC6CAdgZuQJEP68mBKR
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 11:55:12 am
Hmm... My Sanctuary seems to have gone missing... And I can only see 4 in total, all of which say 'PRE-ENABLED', My own Sanctuary wallet says "Not capable masternode: Masternode not in masternode list"...

The hash for both my wallets for block 62042 is the same as yours though...
This usually happens if one of the mn* files wasnt deleted, I would delete the gov* and the .dat files and restart the controller, let the mnsync status go to 999, then restart it.

Then post your sancs ip and I will also see if it says enabled on my end too.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 11:56:22 am
yfBWKnEBzhwGMK9cC6CAdgZuQJEP68mBKR
Sent, but Im not sure that we have enough sancs for this to work properly, but we will see.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 04, 2019, 11:57:27 am
Sent, but Im not sure that we have enough sancs for this to work properly, but we will see.

It didn't work :,(
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 04, 2019, 12:05:40 pm
This usually happens if one of the mn* files wasnt deleted, I would delete the gov* and the .dat files and restart the controller, let the mnsync status go to 999, then restart it.

Then post your sancs ip and I will also see if it says enabled on my end too.

That seems to have worked :) It's in PRE-ENABLED mode now because I restarted it. My sancs IP is the 84.92 one.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 12:06:05 pm
It didn't work :,(
It looks like 100% of our sancs are in pre-enabled status right now.  Lets re-test when 5 of us become deterministic sancs.

I think im going to try to upgrade a sanc now.

I believe what brought on the instability was I flipped dip15 on then off.

I realized we need to wait on dip15 until the sancs have already been upgraded, then flip it back on.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 04, 2019, 12:06:37 pm
That seems to have worked :) It's in PRE-ENABLED mode now because I restarted it. My sancs IP is the 84.92 one.

84.29 :p
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on May 04, 2019, 12:33:51 pm
I upgraded but forgot to turn my QT back on, Im up now and match

getblockhash 62042
4d32aab9042e18a6ecc2229875b0e94499204be423e4084bd18076c02f7e2748

Masternode was in UPDATE_REQUIRED status, just started it, now in PRE_ENABLED
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 12:54:20 pm
It appears my sanc 45.63 has upgraded to Deterministic (dip3).  I manually voted on a proposal and the vote went through, and it says ENABLED.  Checking now to see if it votes on the next GSC automatically.

NOTES:  We must remember this critical Note!  After we upgrade all of our testnet sancs to deterministic, and I flip DIP15, this will make the non-deterministic list dissapear.  We need to ensure that someone can still create a legacy sanc and upgrade it after that moment (so we know how to deal with that scenario).  I hope that also works, because we will surely have some stragglers who want to add a few sancs after dip15 is enabled - who dont want to go through the long process of creating a deterministic sanc.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on May 04, 2019, 12:54:38 pm
Hey Rob, what are the steps to upgrade to a deterministic masternode?
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html

From some digging, looks like you added a command in v1.4.1.7:
Code: [Select]
exec upgradesanc sancname
Reference: https://forum.biblepay.org/index.php?topic=391.msg5798#msg5798
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 12:56:55 pm
Hey Rob, what are the steps to upgrade to a deterministic masternode?
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html

From some digging, looks like you added a command in v1.4.1.7:
Code: [Select]
exec upgradesanc sancname
Reference: https://forum.biblepay.org/index.php?topic=391.msg5798#msg5798

Yeah, I just upgraded one of my sancs and it worked.

Lets go ahead and upgrade some, one sec.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 01:02:01 pm
*** UPGRADING A LEGACY BIBLEPAY SANCTUARY TO A DETERMINISTIC SANCTUARY ***



Guys, go ahead and try this.
1.  You must have a *cold* sanc (that means your sanctuary doesn't have the locked funds in it and you have a controller wallet with the funds locked, and the old sanctuary works (IE its probably ENABLED right now), and your controller wallet has a masternode.conf file.

2.  From your controller wallet, go to the RPC terminal and type:
Code: [Select]
exec upgradesanc sanctuary_name 0(where 0 means dry run, and sanctuary_name is the name of the sanctuary (the first field) in the masternode.conf file).

3.  Check the output of that command and make sure there are no errors.  If so continue to the next step.

4.  From the controller wallet, RPC terminal type:
Code: [Select]
exec upgradesanc sanctuary_name 1Ensure this command does not throw an error.

If the results are successful, you will be in the dip3 sanctuary tab (from the Sanctuaries page | Dip3 sancs).

Note that we create a deterministicsanctuary.conf file for your convenience (this is a biblepay feature).  We automatically add all your dip3 sancs to that file.
This will be useful if you have more than say 10, then you can write a script to pull values from this file and do things like update remote configs, run remote commands etc.  Its also highly useful if you need to access your BLSprivkey or BLSpubkey, or voting information.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 04, 2019, 01:12:11 pm
*** UPGRADING A LEGACY BIBLEPAY SANCTUARY TO A DETERMINISTIC SANCTUARY ***



Guys, go ahead and try this.
1.  You must have a *cold* sanc (that means your sanctuary doesn't have the locked funds in it and you have a controller wallet with the funds locked, and the old sanctuary works (IE its probably ENABLED right now), and your controller wallet has a masternode.conf file.

2.  From your controller wallet, go to the RPC terminal and type:
Code: [Select]
exec upgradesanc sanctuary_name 0(where 0 means dry run, and sanctuary_name is the name of the sanctuary (the first field) in the masternode.conf file).

3.  Check the output of that command and make sure there are no errors.  If so continue to the next step.

4.  From the controller wallet, RPC terminal type:
Code: [Select]
exec upgradesanc sanctuary_name 1Ensure this command does not throw an error.

If the results are successful, you will be in the dip3 sanctuary tab (from the Sanctuaries page | Dip3 sancs).

Note that we create a deterministicsanctuary.conf file for your convenience (this is a biblepay feature).  We automatically add all your dip3 sancs to that file.
This will be useful if you have more than say 10, then you can write a script to pull values from this file and do things like update remote configs, run remote commands etc.  Its also highly useful if you need to access your BLSprivkey or BLSpubkey, or voting information.

Cool! Seems to have worked for me. My sanc is now in the dip3 tab :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 01:23:04 pm
Cool! Seems to have worked for me. My sanc is now in the dip3 tab :)

Thats awesome man!  So to elaborate a little more:
1) Dash allows a sanctuary owner to specify where future rewards go (IE they allow you to tell the wallet a specific address to receive sanc rewards).  This is useful if you are trying to make an untraceable wallet.
2) Dash allows any designated public key to be a voting delegate.  This means a friend can vote on a sanc poll for you if you provide their pubkey.

To make this easy to start, the upgradesanc command fills those two things in for you.

To find out how we filled them in, go to receiving addresses, look for:
Yoursancname-D and Yoursancname-V.

The D is the address biblepay set up for your rewards.
The V is the address we created for your voting.

The vote-many and vote-alias automatically finds your V address to vote from (no changes are necessary there).

The rewards will start coming in to the D address (theoretically), lets check that.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 01:26:54 pm
I forgot to mention, we have to wait until everyone upgrades their legacy sancs first, then we flip dip15 to on, then we can check to see if the deterministic rewards start coming into the new address.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 04, 2019, 01:39:27 pm
Thats awesome man!  So to elaborate a little more:
1) Dash allows a sanctuary owner to specify where future rewards go (IE they allow you to tell the wallet a specific address to receive sanc rewards).  This is useful if you are trying to make an untraceable wallet.
2) Dash allows any designated public key to be a voting delegate.  This means a friend can vote on a sanc poll for you if you provide their pubkey.

To make this easy to start, the upgradesanc command fills those two things in for you.

To find out how we filled them in, go to receiving addresses, look for:
Yoursancname-D and Yoursancname-V.

The D is the address biblepay set up for your rewards.
The V is the address we created for your voting.

The vote-many and vote-alias automatically finds your V address to vote from (no changes are necessary there).

The rewards will start coming in to the D address (theoretically), lets check that.

Nice features :) I can confirm that the D and V addresses have been created. You're doing a great job Rob!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 08:29:43 pm
As founder I am keeping a very serious eye on any potential forks, as one of the goals of Evo is to eliminate forks with extra prevention layers.

So far we have had a reason for every fork: a mandatory upgrade with half of the sancs running on the old version forced on the network.

I just want to make everyone aware that something we did today should have caused a fork:  Enabling dip15 erases all of the old sancs votes (meaning the daily gsc superblock could fail and I see in the logs the one after that height did fail), then we picked back up later but I see a lot of ddos going on.

We will have to remember, when we are about to go live, we should plan on upgrading all of the sancs in Evo before the cutover height to GSC, have the spork enabled, then start GSC in deterministic mode to prevent this risk in prod.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 09:37:42 pm
Our amateur hacker is back online - it seems to be the same person who likes to send 666 to SX.  Probably Slovakia or Noko.

Anyway I have a mandatory upgrade coming in 30 mins, please shut off the miners.

They are going to lose this cat & mouse game- I've been through this before, but this time I'm working for God.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 04, 2019, 10:20:59 pm
1.4.2.7-Mandatory Upgrade for TestNet

- Prevent memory pool tithe attacks
 
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on May 05, 2019, 11:01:11 am
Setup another wallet, Upgraded both my wallets to v1.4.2.7

getblockhash 63152
48394253*

I still have an old hot masternode (1 wallet), setting up cold masternode now (2 wallets)
Reference: http://wiki.biblepay.org/Create_Sanctuary_2
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 05, 2019, 12:09:41 pm
I've been having a hard time resyncing every time we have a mandatory upgrade.  I know part of the problem is when we force a new protocol version, it knocks all the sancs offline.  (I have an old biblepay classic feature I am going to port that prevents that, allowing us to sync easier but still forces us to upgrade), so I will need to put this in today.

Two other things, I have realized one of the reasons we have trouble syncing when the diff is < .02 is because the wallet is having a hard time figuring out which fork is valid (in its diff calculator).  I believe we will need a couple consensus rules added.  For one, we should only add and enforce ABNs when the diff is > 1.0 in testnet (and a higher number in prod).  I think this would help us immensely (coming to consensus).  The other is the same with anti-gpu.  We shouldnt really be monitoring or enforcing that if the diff < 1.0.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 05, 2019, 12:13:33 pm
Setup another wallet, Upgraded both my wallets to v1.4.2.7

getblockhash 63152
48394253*

I still have an old hot masternode (1 wallet), setting up cold masternode now (2 wallets)
Reference: http://wiki.biblepay.org/Create_Sanctuary_2

I agree with you.  Ill stick it out for a while and keep the chain, lets see how we do.

(I'll still put these 3 new features in however, for the next mandatory).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on May 05, 2019, 12:24:35 pm
I've been having a hard time resyncing every time we have a mandatory upgrade.  I know part of the problem is when we force a new protocol version, it knocks all the sancs offline.  (I have an old biblepay classic feature I am going to port that prevents that, allowing us to sync easier but still forces us to upgrade), so I will need to put this in today.

Two other things, I have realized one of the reasons we have trouble syncing when the diff is < .02 is because the wallet is having a hard time figuring out which fork is valid (in its diff calculator).  I believe we will need a couple consensus rules added.  For one, we should only add and enforce ABNs when the diff is > 1.0 in testnet (and a higher number in prod).  I think this would help us immensely (coming to consensus).  The other is the same with anti-gpu.  We shouldnt really be monitoring or enforcing that if the diff < 1.0.
what about checkpoints? I saw in some wallets using checkpoints for easier sync or what.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 05, 2019, 12:28:13 pm
what about checkpoints? I saw in some wallets using checkpoints for easier sync or what.

A checkpoint will help the wallet get on the right chain after one particular block in history at a certain mandatory height that passed.

But what I wrote explains a things in a lot greater detail than a checkpoint.

We do use checkpoints in our wallet (we have about 10 in classic etc), I added one to testnet but I havent been adding them because they dont address the problem fully, but Ill add one during the next mandatory.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on May 05, 2019, 01:07:31 pm
I was able to set up a cold masternode successfully,
and was able to upgrade to a dip3 masternode successfully!

Masternode IP: 149.248.35.69
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 05, 2019, 01:54:48 pm
I was able to set up a cold masternode successfully,
and was able to upgrade to a dip3 masternode successfully!

Masternode IP: 149.248.35.69
Thats great!


Hey everyone I want to mention something important.


Before we enable dip15 (deterministic masternodes), we need to copy our 'masternodeblsprivkey' to our cold sanctuary biblepay.conf file (just like we usually copy the masternodeprivkey over there).

This is not used until we flip dip15.  As I believe the moment we flip dip15 the sancs will rely on this privkey to sign all the messages (and thats likely why we had hundreds of failed votes yesterday once I flipped it for a couple mins). 

So either way its mandatory that we copy the key to the sanc before dip15, so lets make that part of the upgrade to deterministic process.

I also forgot to mention this is the main reason I added the deterministicsanctuary.conf file - so you can open it back up and get the value out of it (or write a script to copy the value to the sanc).


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 05, 2019, 01:58:21 pm
Btw, although we had a rug yank, I think Watchman worked correctly:
getrawtransaction f04a7c58940972fb4784033e926f07b90d9647a9d0ad9ee5904efff0e4ec5f92 1

If I remember right, the 1 mil proposal was either voted down or had the least votes.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 05, 2019, 02:00:49 pm
I agree with you.  Ill stick it out for a while and keep the chain, lets see how we do.

(I'll still put these 3 new features in however, for the next mandatory).

I was on a different chain with both my wallets. I'm reindexing now...
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 05, 2019, 02:11:46 pm
Since we all appear to be on the correct chain now, let's ask everyone to upgrade to deterministic sancs by tomorrow - and Ill flip to dip15 tomorrow.

Remember to add your blsprivkey to your sanc.

This way we can see as of tomorrow afternoon if things are going to work.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on May 05, 2019, 02:31:14 pm
Before we enable dip15 (deterministic masternodes), we need to copy our 'masternodeblsprivkey' to our cold sanctuary biblepay.conf file (just like we usually copy the masternodeprivkey over there).

For cold masternode setup, we will need to:
1. Local/Controller Wallet:
replace the masternodeprivkey value in masternode.conf with masternodeblsprivkey?

do we need to also:
2. Remote/Masternode Wallet:
A. replace the masternodeprivkey value in biblepay.conf with masternodeblsprivkey?
B. or add new line masternodeblsprivkey=?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 05, 2019, 02:53:17 pm
Thats great!


Hey everyone I want to mention something important.


Before we enable dip15 (deterministic masternodes), we need to copy our 'masternodeblsprivkey' to our cold sanctuary biblepay.conf file (just like we usually copy the masternodeprivkey over there).

This is not used until we flip dip15.  As I believe the moment we flip dip15 the sancs will rely on this privkey to sign all the messages (and thats likely why we had hundreds of failed votes yesterday once I flipped it for a couple mins). 

So either way its mandatory that we copy the key to the sanc before dip15, so lets make that part of the upgrade to deterministic process.

I also forgot to mention this is the main reason I added the deterministicsanctuary.conf file - so you can open it back up and get the value out of it (or write a script to copy the value to the sanc).

I already put the 'masternodeblsprivkey' in the biblepay.conf when I set-up my Sanctuary. I'm don't remember it exactly, but I think there was something in the set-up notes about it (maybe in Togo's) and I think that my (legacy) Sanctuary didn't even want to start when I didn't have it in there?

Anyway, I'm om the right chain, my Sanctuary is in DIP3, so I'm ready to roll  8)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 05, 2019, 02:55:58 pm
For cold masternode setup, we will need to:
1. Local/Controller Wallet:
replace the masternodeprivkey value in masternode.conf with masternodeblsprivkey?

do we need to also:
2. Remote/Masternode Wallet:
A. replace the masternodeprivkey value in biblepay.conf with masternodeblsprivkey?
B. or add new line masternodeblsprivkey=?

Since deterministic sancs only support cold sancs, you do not need to do #1 (otherwise the controller could only support one sanc which wouldnt be too nifty).

We need to add the masternodeblsprivkey to the Sanctuary side.
The masternodeprivkey is still needed until after the cutover, so we can leave those in there until reason comes to start fresh.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 05, 2019, 02:57:35 pm
I already put the 'masternodeblsprivkey' in the biblepay.conf when I set-up my Sanctuary. I'm don't remember it exactly, but I think there was something in the set-up notes about it (maybe in Togo's) and I think that my (legacy) Sanctuary didn't even want to start when I didn't have it in there?

Anyway, I'm om the right chain, my Sanctuary is in DIP3, so I'm ready to roll  8)

Dash's notes have the instructions to do it, but those notes are very complicated (to create a deterministic sanc from scratch).
Yes, the sanc throws a warning right now if the masternodeblsprivkey is missing, but it still starts. (Using the masternodeprivkey).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 05, 2019, 03:06:38 pm
Ok, I just made my 3 deterministic and set up the masternodeblsprivkey on the remote sancs, and rebooted them.
So it looks like we have:
Rob, Rob, Rob,
Togo,
Jaap

Upgraded.
Anyone else need to upgrade?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 05, 2019, 03:08:49 pm
Dash's notes have the instructions to do it, but those notes are very complicated (to create a deterministic sanc from scratch).
Yes, the sanc throws a warning right now if the masternodeblsprivkey is missing, but it still starts. (Using the masternodeprivkey).

Ah, right! I probably got the warning and then proceeded to google the Dash notes.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 06, 2019, 08:32:41 am
It looks like we made it through the night with no issues (and no spam).  We have a .50~ diff and 5 enabled sancs (all deterministic).

Today I will flip dip15 and see if we wreak havoc or if we continue smoothly.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 06, 2019, 09:05:31 am
Ok, we are now transitioning to deterministic masternodes at height 64960!

At this point, your sanctuary reward payments should shift from the old mining address to your new deterministic address.

All proposal votes (on GSCs in this intermediate block will become invalid).

Lets see how the GSC system handles creation of the next proposal and if votes for it work also.

EDIT:  Please check your cold sanctuary and see if it reports all the new fields in:  masternode status

EDIT2:  Please ensure you can vote on proposals both from UI, command line alias and command line many.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on May 06, 2019, 10:50:37 am
In Sanctuaries tab, I only see DIP3 Sanctuaries tab now

Name of my masternode is MN1, and in Transactions I notice rewards going to MN1-D address

In the cold setup, on the remote masternode, for masternode status command,
I see lots of new fields!

Code: [Select]
./biblepay-cli masternode status
{
  "outpoint": "e94e309dfc51d4166294a300a8e4a935c36e81614c95bc7ccf4b4abd054fb1b9-1",
  "service": "149.248.35.69:40001",
  "proTxHash": "04b7167841f9c174d135eed04c4011b077b4ead1b3c5050d45eae8e0a409e2e9",
  "collateralHash": "e94e309dfc51d4166294a300a8e4a935c36e81614c95bc7ccf4b4abd054fb1b9",
  "collateralIndex": 1,
  "dmnState": {
    "service": "149.248.35.69:40001",
    "registeredHeight": 63324,
    "lastPaidHeight": 64958,
    "PoSePenalty": 0,
    "PoSeRevivedHeight": -1,
    "PoSeBanHeight": -1,
    "revocationReason": 0,
    "ownerAddress": "yZZ64ZSubgwAbSU6y7hpTNLV75ASDS4JeQ",
    "votingAddress": "yZZ64ZSubgwAbSU6y7hpTNLV75ASDS4JeQ",
    "payoutAddress": "yhTodPvmgv2RagCgtmPFvENztSm2FTeRRm",
    "pubKeyOperator": "02ea2b9f2dcad455907f2aaf547087118cb7ec30a12d0f2a529ea41125ea05e41ba5ad53bece8d1a0362a1c4f344c0a9"
  },
  "state": "READY",
  "status": "Ready"
}

In Proposals, I voted Yes for Speaking_Hall, No for Dog_Mascot and Abstain for Minecraft_Integration
(How do I check votes? gobject getvotes hash? and how do I link it back to an address?, Looks like it links to a masternodes collateral hash?)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 06, 2019, 11:53:52 am
In Sanctuaries tab, I only see DIP3 Sanctuaries tab now

Name of my masternode is MN1, and in Transactions I notice rewards going to MN1-D address

In the cold setup, on the remote masternode, for masternode status command,
I see lots of new fields!

Code: [Select]
./biblepay-cli masternode status
{
  "outpoint": "e94e309dfc51d4166294a300a8e4a935c36e81614c95bc7ccf4b4abd054fb1b9-1",
  "service": "149.248.35.69:40001",
  "proTxHash": "04b7167841f9c174d135eed04c4011b077b4ead1b3c5050d45eae8e0a409e2e9",
  "collateralHash": "e94e309dfc51d4166294a300a8e4a935c36e81614c95bc7ccf4b4abd054fb1b9",
  "collateralIndex": 1,
  "dmnState": {
    "service": "149.248.35.69:40001",
    "registeredHeight": 63324,
    "lastPaidHeight": 64958,
    "PoSePenalty": 0,
    "PoSeRevivedHeight": -1,
    "PoSeBanHeight": -1,
    "revocationReason": 0,
    "ownerAddress": "yZZ64ZSubgwAbSU6y7hpTNLV75ASDS4JeQ",
    "votingAddress": "yZZ64ZSubgwAbSU6y7hpTNLV75ASDS4JeQ",
    "payoutAddress": "yhTodPvmgv2RagCgtmPFvENztSm2FTeRRm",
    "pubKeyOperator": "02ea2b9f2dcad455907f2aaf547087118cb7ec30a12d0f2a529ea41125ea05e41ba5ad53bece8d1a0362a1c4f344c0a9"
  },
  "state": "READY",
  "status": "Ready"
}

In Proposals, I voted Yes for Speaking_Hall, No for Dog_Mascot and Abstain for Minecraft_Integration
(How do I check votes? gobject getvotes hash? and how do I link it back to an address?, Looks like it links to a masternodes collateral hash?)

Wow thats awesome, yes I see your vote for minecraft, so I can see it worked from the deterministic sancs cold controller, good.
So to see votes, you can:
1) Look at Proposals UI
2) gobject listwild all proposals Minecraft  (Note the case sensitivity on Minecraft)
Scrape the gobject
gobject get hash
It should show the votes after the gobject description.

The votes are linked by "Sent proregtxid " (the last field in deterministicsanctuary.conf).  You can also scrape this hash by right clicking on a deterministic sanc and saying Copy proreg-txid to clipboard.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on May 06, 2019, 12:05:06 pm
Awesome!
Also, that gobject listwild is very useful!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 06, 2019, 02:19:09 pm
Awesome!
Also, that gobject listwild is very useful!

Thanks, as you can imagine I needed it for a lot of debugging while looking for missing GSCs.

Note that you can also search by part of the hash with it (IE the beginning of the gobject id).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 06, 2019, 02:20:35 pm
Can someone do us a favor, please create a new legacy sanc (and of course you wont be able to see it in the sancs list because we are past dip15), and see if you can upgrade it to deterministic successfully?

Just want to ensure stragglers can still create sancs the old way and just upgrade them.

Remember we do need to paste the masternodeblsprivkey into the cold sancs biblepay.conf also.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 06, 2019, 03:34:00 pm
I'm starting to review this page:
https://wiki.biblepay.org/Nutrition_Information
To see what we forgot to test, and I wanted to mention something about soft forks and stable-prod features in Evo:

We did test the stable-prod feature a couple of releases back successfully.

At the time, we were not rewarding for diary entries and QT was around 30% and climbing.

I added two business logic changes to the server side and we had a leisure, and did not specifically mention it, but what happened was the current GSCs with existing votes were downvoted automatically and the new GSC (because of the 2% contract change in that GSC superblock) was upvoted, meaning this feature was tested successfully (we had a leisure upgrade for sancs, no hard consensus change release) and we succeeded in emitting a GSC.  So this is really great and very useful in the future as I can see a lot of possible releases in mid quarter updates with useful things between exchange mandatory upgrades.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 06, 2019, 03:38:45 pm
Church Tithing/Mobile-wallet staking:
MIP is working on it.  If we don't get it finished by the end of June we will push it back to September.  On a side note, BBP has a PO Box (actually we have a physical address po box) now, and MIP is working on a relationship with Apple so he can also release BiblePay for iPhone.

ChainLocks:
This is most likely the only feature in this guide that won't make it in time for an end of June release.  This is only because Dash is still testing it and MIP and I would like to see it promoted to Dash-Prod before we release it in BiblePay. 



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 06, 2019, 03:50:51 pm
Next we need to ensure the payment amounts are correct for : POBH, monthly superblocks, daily superblocks and the qt effect on it.


After this it appears the entire wishlist has been fulfilled.  Let me know if anyone has any questions or concerns for this next version of BiblePay.

I believe we have tested almost all of the pieces successfully!


On a side note, I hope people have noticed the chained bible verses are now consecutive and the txlist double click shows these also.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 06, 2019, 03:52:55 pm
Oh btw, I did test Evo against prod last month, and also tested Pool mining (in prod mode).

If anyone feels up for it, please sync in prod, and verify you can sync to the top in prod.
Then configure the miner to be pointed at a pool, and ensure pool mining is working.
Note:  It would be very helpful if someone could test Purepool.  I only tested mining in evo in prod against pool.biblepay.org (successfully).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on May 07, 2019, 05:33:40 am
Oh btw, I did test Evo against prod last month, and also tested Pool mining (in prod mode).

If anyone feels up for it, please sync in prod, and verify you can sync to the top in prod.
Then configure the miner to be pointed at a pool, and ensure pool mining is working.
Note:  It would be very helpful if someone could test Purepool.  I only tested mining in evo in prod against pool.biblepay.org (successfully).

$ ~/biblepay-evolution/src/biblepay-cli getblockcount
117799

$ ~/biblepay-evolution/src/biblepay-cli getblockhash 117799
1a038e93b4046038444f7a98abd546aa2a7a8580ade7771224a73685b79314b5

I don't know what exactly is required but here is the output of getmininginfo of EVO on the main chain pointed to purepool.

{
  "blocks": 117798,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 10211.68938254838,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 1,
  "networkhashps": 14937188254.95241,
  "hashps": 28.84073865488929,
  "minerstarttime": "05-07-2019 10:24:22",
  "hashcounter": 4865,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "gsc_errors": "",
  "poolmining": true,
  "pool_url": "https://pool.purepool.org",
  "required_abn_weight": 0
}


The progress can be followed here http://www.purepool.org/main/miner/BD9gmJ5vmPJtDewo9NyqUT7fJQgV39AW7R
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on May 07, 2019, 06:01:32 am
Interesting, I managed to send funds (BBP not tBBP) from my wallet on the mainnet to the wallet running EVO!

~/biblepay-evolution/src/biblepay-cli getinfo
{
  "version": 1040207,
  "protocolversion": 70732,
  "walletversion": 61000,
  "balance": 100.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 117804,
  "timeoffset": 0,
  "connections": 11,
  "proxy": "",
  "difficulty": 9338.691900918453,
  "testnet": false,
  "keypoololdest": 1557217142,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 0.01000000,
  "errors": ""
}

~/biblepay-evolution/src/biblepay-cli listtransactions
  {
    "account": "",
    "address": "BC2RsquwDER8sCKcMmDCy9rgKSusWLZpGn",
    "category": "receive",
    "amount": 100.00000000,
    "label": "",
    "vout": 1,
    "confirmations": 2,
    "instantlock": false,
    "blockhash": "49d1f7e4d26f8547da3ae9c25a40232080706293a95859f2e0c0770aa05d5270",
    "blockindex": 1,
    "blocktime": 1557225899,
    "txid": "29f1b61e84d4f6eae1ef9eb49b8ef3f9f49366576b3eeb57282e2e7367f9c917",
    "walletconflicts": [
    ],
    "time": 1557225892,
    "timereceived": 1557225892
  }

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on May 07, 2019, 06:16:22 am
~/biblepay-evolution/src/qt/biblepay-qt loads ok but perhaps to be expected crashed when you try to view leaderboard and proposals.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on May 07, 2019, 06:34:26 am
I guess the next step is to see if one can create a DIP3 masternode on the mainnet but I am unable to help with that as I do not have the required collateral...
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 07, 2019, 10:43:20 am
I guess the next step is to see if one can create a DIP3 masternode on the mainnet but I am unable to help with that as I do not have the required collateral...

Yes, the collateral is going up to 4,500,001, so its quite a risky thing to tie up 3* the amount currently LOL.
Well this is actually a very critical issue and relies on something that isn't readily apparent in the code that sort of drives our decision to do this a certain way.
The new Dash non-financial transactions require the pro-reg-tx payload to be stored in a certain way that starts storing data in the prod chain in an extended place, that I really don't want to be intermingled with biblepay-classic nodes.  Another words, we must ensure the dip15 cutover is on a height well after our mandatory upgrade height to evo - we will have to phase Evo in at a certain height, and run legacy sancs first:
For example:
Height 135,000 - Cutover to Evolution - convert sancs from 1.55m to 4.5MM
Height 145,000 - Upgrade to Deterministic sancs (between 135K-145K)
Height 145,001 - Mandatory upgrade to deterministic non-financial txes (dip15 is enabled)
Its a shame that we have to do this in two steps, but its really the only way I can see doing this - if we go directly to deterministic sancs, we would break the biblepay classic nodes (as the extra non-financial data would not be parseable).

But yes, we will talk more about this soon, and I will act as a sacrificial lamb with one of my sancs and create it in Prod through evo as a 4.5MM and ensure it starts. 
I think we will need to organize this endeavor in a way where we ask our Prod sancs to upgrade 7 days before the mandatory cutover height (IE before the exchanges even upgrade), because moving to evo requires all sancs to re-organize into a 4.5MM farm.
(If we asked them to upgrade after the height prod would have no sancs at the cutover height).  We also have to take into consideration the monthly budget height.
It would be good to frame this upgrade right after either May 30ths block, or June 30th's block.
At that point Sancs in prod would download Evo, upgrade to 4.5 MM in classic mode, then around the 7th, the mandatory height passes, the exchanges upgrade and then we have a certain buffer (say 25 more days) to upgrade to deterministic.




Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 07, 2019, 10:46:31 am
I see the two 500K proposals won in the last superblock (getgovernanceinfo:last superblock height).  I see the 1Mil (dog mascot) didnt get paid, so it appears this one worked also.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 07, 2019, 10:48:24 am
~/biblepay-evolution/src/qt/biblepay-qt loads ok but perhaps to be expected crashed when you try to view leaderboard and proposals.

Ok, thanks a lot, that is something we missed, I am adding this to the list right now. 

Thats great that you synced to the top though, awesome!

On a side note, Dash added more messages and a protocol change to governance, so Evo cant load the governance objects from Biblepay-classic nodes (thats why the proposals dont show yet in prod). 


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 07, 2019, 10:53:16 am
Interesting, I managed to send funds (BBP not tBBP) from my wallet on the mainnet to the wallet running EVO!

~/biblepay-evolution/src/biblepay-cli getinfo
{
  "version": 1040207,
  "protocolversion": 70732,
  "walletversion": 61000,
  "balance": 100.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 117804,
  "timeoffset": 0,
  "connections": 11,
  "proxy": "",
  "difficulty": 9338.691900918453,
  "testnet": false,
  "keypoololdest": 1557217142,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 0.01000000,
  "errors": ""
}

~/biblepay-evolution/src/biblepay-cli listtransactions
  {
    "account": "",
    "address": "BC2RsquwDER8sCKcMmDCy9rgKSusWLZpGn",
    "category": "receive",
    "amount": 100.00000000,
    "label": "",
    "vout": 1,
    "confirmations": 2,
    "instantlock": false,
    "blockhash": "49d1f7e4d26f8547da3ae9c25a40232080706293a95859f2e0c0770aa05d5270",
    "blockindex": 1,
    "blocktime": 1557225899,
    "txid": "29f1b61e84d4f6eae1ef9eb49b8ef3f9f49366576b3eeb57282e2e7367f9c917",
    "walletconflicts": [
    ],
    "time": 1557225892,
    "timereceived": 1557225892
  }

Yes, thats awesome, thanks for the tests.

Yes, the hash algorithm and miner is backwards compatible in evo up to a certain height.  After a certain height, we do switch to a newer version of POBH (with ABN), and the chained verses, but Evo works in all ways with the biblepay-classic nodes, Except it cant receive governance data from the classic sancs.

Hence the reason we have to fire up 50 or so Evolution sanctuaries for our mandatory cutover height (first).
So basically, the Evo sancs will become the official sancs at the cutover height.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 07, 2019, 10:55:02 am
$ ~/biblepay-evolution/src/biblepay-cli getblockcount
117799

$ ~/biblepay-evolution/src/biblepay-cli getblockhash 117799
1a038e93b4046038444f7a98abd546aa2a7a8580ade7771224a73685b79314b5

I don't know what exactly is required but here is the output of getmininginfo of EVO on the main chain pointed to purepool.

{
  "blocks": 117798,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 10211.68938254838,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 1,
  "networkhashps": 14937188254.95241,
  "hashps": 28.84073865488929,
  "minerstarttime": "05-07-2019 10:24:22",
  "hashcounter": 4865,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "gsc_errors": "",
  "poolmining": true,
  "pool_url": "https://pool.purepool.org",
  "required_abn_weight": 0
}


The progress can be followed here http://www.purepool.org/main/miner/BD9gmJ5vmPJtDewo9NyqUT7fJQgV39AW7R


Thanks a lot for doing this!  This is immensely helpful!

It appears from Purepools stats that you have successfully mined!

Sweet!


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on May 07, 2019, 12:15:43 pm
There are some differences in the output of the getmininginfo

>EVO -version
BiblePay Core RPC client version 1.4.2.7
>getmininginfo
{
  "blocks": 117855,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 9372.552218530582,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 1,
  "networkhashps": 10394307548.78834,
  "hashps": 222.8212327270187,
  "minerstarttime": "05-07-2019 11:16:12",
  "hashcounter": 4675568,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "Submitting Solution 05-07-2019 17:04:52; ",
  "poolinfo3": "",
  "gsc_errors": "",
  "poolmining": true,
  "pool_url": "https://pool.purepool.org",
  "required_abn_weight": 0
}

-version
Biblepay Core RPC client version 1.2.0.1
biblepay-cli getmininginfo
{
  "blocks": 117855,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 9372.552218530582,
  "errors": "",
  "genproclimit": 2,
  "networkhashps": 1418552.369007834,
  "hashps": 187.8965827796162,
  "minerstarttime": "05-07-2019 14:17:00",
  "hashcounter": 1903566,
  "pooledtx": 1,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 3052,
  "poolmining": true,
  "pool_url": "https://pool.purepool.org",
  "poolmining_use_ssl": true
}

Notice the great differences in networkhasps. Does this mean that early EVO (>v1.4.2.7) upgraders are at a severe disadvantage in terms of POBH mining when competing with v1.2.0.1? Or is this because I am the sole v1.4.2.7 on the mainnet? Difficulty appears to be similar though....

Can you kindly explain? Thank you. Testing is also a good educational experience for us all!


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 07, 2019, 12:36:35 pm
There are some differences in the output of the getmininginfo

>EVO -version
BiblePay Core RPC client version 1.4.2.7
>
Code: [Select]
getmininginfo
{
  "blocks": 117855,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 9372.552218530582,
  "errors": "",
  "pooledtx": 0,
  "chain": "[b]main[/b]",
  "genproclimit": 1,
  "networkhashps": [u][b]10394307548.78834[/b][/u],
  "hashps": 222.8212327270187,
  "minerstarttime": "05-07-2019 11:16:12",
  "hashcounter": 4675568,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "Submitting Solution 05-07-2019 17:04:52; ",
  "poolinfo3": "",
  "gsc_errors": "",
  "poolmining": true,
  "pool_url": "https://pool.purepool.org",
  "required_abn_weight": 0
}

-version
Biblepay Core RPC client version [u][b]1.2.0.1[/b][/u]
biblepay-cli getmininginfo
{
  "blocks": 117855,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 9372.552218530582,
  "errors": "",
  "genproclimit": 2,
  "networkhashps": [u][b]1418552.369007834[/b][/u],
  "hashps": 187.8965827796162,
  "minerstarttime": "05-07-2019 14:17:00",
  "hashcounter": 1903566,
  "pooledtx": 1,
  "testnet": false,
  "chain": "[b]main[/b]",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 3052,
  "poolmining": true,
  "pool_url": "https://pool.purepool.org",
  "poolmining_use_ssl": true
}
Notice the great differences in networkhasps. Does this mean that early EVO (>v1.4.2.7) upgraders are at a severe disadvantage in terms of POBH mining when competing with v1.2.0.1? Or is this because I am the sole v1.4.2.7 on the mainnet? Difficulty appears to be similar though....

Can you kindly explain? Thank you. Testing is also a good educational experience for us all!

First of all, know that mining in Evo against prod (solo or against the pool) is virtually the same as mining in classic (as far as HPS, efficiency, and fairness) - there is no advantage to either client (except Evo might be 1% better due to its more optimized compiler and Depends environment etc).

Regarding the Network HashPS, first let me try to explain how Bitcoin calculates it.  Its a trailing average of chain hashpersecond found in the last 10 blocks or so (the blocks contain this data because we track the nonce req count and chain weight etc).  But, where this discrepency starts occuring is back in POBH v3, Alex and I were doing some testing and we realized due to our very unique hash algorithm we put waaaay more hashes in per hash than the networkhashps reported so we tweaked it in classic to be our new fangled estimate.

So the answer is in Evo its too low.  I remember now why this was not updated:  POBH changed in Evo.  I just made a punchlist item to fix this.
But in summary, its a barometer being affected by the wrong multiplier currently.

EDIT:  Actually Evo looks pretty accurate as-is (it seems this fig is too high in Classic).  Since I have the exact HPS in the pool, and the % of blocks solved by pool.bibepay.org, we really are doing about the Evo-hps right now in prod.







Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 07, 2019, 01:42:21 pm
1.4.2.8b-Mandatory upgrade for TestNet

- Add testnet checkpoint
- Enhance ABN consensus rule to only require ABN when diff is greater
than threshhold (this should improve the SetBestChain business logic)
- Port biblepay-classic peer disconnect rules (enforcing network time
and minimum version)
- Ensure wallet does not crash in Prod when people click on Leaderboard
or Proposals
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 07, 2019, 02:41:35 pm
We should technically re-sync better on this version (I mean the initial sync after upgrading only), as now we have classic's code for mandatory upgrades in.

BTW:  Please dont erase any files, just upgrade.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on May 08, 2019, 01:41:17 pm
We should technically re-sync better on this version (I mean the initial sync after upgrading only), as now we have classic's code for mandatory upgrades in.

BTW:  Please dont erase any files, just upgrade.
ha, to late. I deleted everything and now I have a problem, no peers
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 08, 2019, 01:49:15 pm
ha, to late. I deleted everything and now I have a problem, no peers

Check system clock ensure its correct within 5 mins and timezone is correct.

Delete banlist.dat, restart.

If you arent synced after 15 mins post IP address here and Ill search my log for the reason for your ban as we have 3 seed nodes in testnet.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on May 08, 2019, 03:00:46 pm
nope, something doesnt work at all. Like I am on my own
(https://www.dropbox.com/s/4l893gct027smi4/Screenshot%202019-05-08%2021.56.33.png?dl=0)

what are the nodes, i saw them in previus version, but cant remeber. ns.biblepay.org?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on May 08, 2019, 03:26:58 pm
Upgraded both wallets to v1.4.2.8b yesterday

I tried to just run them normally, but they would crash right away, tried to reindex and same thing, didnt see anything in the log (may have forgotten to add debug=1), so I wanted till today and tried again with reindex, both worked a couple hours ago

getblockhash 69207
6e40d8f*
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 08, 2019, 03:31:25 pm
Upgraded both wallets to v1.4.2.8b yesterday

I tried to just run them normally, but they would crash right away, tried to reindex and same thing, didnt see anything in the log (may have forgotten to add debug=1), so I wanted till today and tried again with reindex, both worked a couple hours ago

getblockhash 69207
6e40d8f*

When you say crash, what do you mean, and what version are you running (qt or non) and what platform (unix linux mac)?

Yeah, since I have not seen a crash yet except clicking on leaderboard in prod (which was fixed in the last version) I would really like to know how to reproduce.

Also, if anyone else has ever crashed in evo in testnet it would be really nice to have more info so we can fix it before we go to prod (thats what testnet is for).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 08, 2019, 03:33:02 pm
nope, something doesnt work at all. Like I am on my own
(https://www.dropbox.com/s/4l893gct027smi4/Screenshot%202019-05-08%2021.56.33.png?dl=0)

what are the nodes, i saw them in previus version, but cant remeber. ns.biblepay.org?
Like I alluded to in the prior message, they would be compiled in if they are seed nodes so you dont need them, and I synced today with a node.

Is there a reason you are hiding your ip?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 08, 2019, 03:40:24 pm
Upgraded both wallets to v1.4.2.8b yesterday

I tried to just run them normally, but they would crash right away, tried to reindex and same thing, didnt see anything in the log (may have forgotten to add debug=1), so I wanted till today and tried again with reindex, both worked a couple hours ago

getblockhash 69207
6e40d8f*

Synced

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on May 08, 2019, 03:43:30 pm
no, there is no reason. didnt even know I am hiding it.
I uncomment this below and now it got the connection.
#rpcuser=
#rpcpassword=
#rpcallowip=127.0.0.1
#rpcport=40001
#listen=0
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 08, 2019, 03:45:40 pm
So I have a few pieces of advice for anyone creating new deterministic sancs:

1) Do not lose your masternodeblsprivkey (or pubkey).  Keep a copy of your deterministic.conf somewhere.  If you lose your wallet.dat, your sanc will keep running as long as the collateral is locked, and you will not be able to change its IP or its collateral without that blsprivkey and owner privkey.
2) However, I did a test today and found a way to immediately kill your old sanctuary (and allow upgrading).  If you spend your collateral, within minutes the sanctuary will dissapear from the active sancs list! 
3) You cannot re-register the same IP with a new sanc until you either Revoke your old sanctuary (with a proUpRevTx), or if you spend your collateral.

I was successfully able to re-create a new sanc today after I spent my collateral and did a new upgradesanc command.

If otoh you do an upgradesanc before spending and revoking, you will receive an error (duplicate service IP).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 08, 2019, 03:47:45 pm
no, there is no reason. didnt even know I am hiding it.
I uncomment this below and now it got the connection.
#rpcuser=
#rpcpassword=
#rpcallowip=127.0.0.1
#rpcport=40001
#listen=0

Ok good, I was only asking because yesterday I saw some strange activity that looked like someone was sending things from a fraudulent client (IE a self compiled fraudulent client).

Yeah the addresses are:  dns1.biblepay.org, dns2.biblepay.org and dns3.biblepay.org

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on May 08, 2019, 03:52:34 pm
I saw in debug " 0 addresses found from DNS seeds" so I was planning in adding them manualy but ok.
 
prict from previus post
(https://i.imgur.com/5xUvJJu.png)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 08, 2019, 03:54:50 pm
Upgraded both wallets to v1.4.2.8b yesterday

I tried to just run them normally, but they would crash right away, tried to reindex and same thing, didnt see anything in the log (may have forgotten to add debug=1), so I wanted till today and tried again with reindex, both worked a couple hours ago

getblockhash 69207
6e40d8f*

Are you sure the terminal window didnt say "assertion failed" when you ran it?

(Thats not a crash - thats an ungraceful exit).  That happens when evo chain pindex != pindexbest.  (Ive seen that a few times).  That happens when the database exits uncleanly without a flush.  We put in a fix for that in classic, but we left it the way it is in Dash since they have it in there I figured it was good enough for us, but its obviously a 6 1/2 dozen other conundrum type issue.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 08, 2019, 03:57:09 pm
I saw in debug " 0 addresses found from DNS seeds" so I was planning in adding them manualy but ok.
 
prict from previus post
(https://i.imgur.com/5xUvJJu.png)

We add them in a non-conforming way (we force them in).

Usually they kick in after 15 mins if your IP was temporarily banned.
That happens very easily when you are on your own chain, your client forwards block headers to the seed nodes, they ddos you and build up a certain amount of minutes ban, then they allow you in again after you stop the activity and try to start from zero.


One other problem with syncing from zero is you may need gen=0 to get started as in testnet its suuuuper easy to solve a block and get on your own chain (I had to do the gen=0 today to sync properly).


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on May 08, 2019, 04:01:47 pm
v1.4.2.8b, both Ubuntu, both command line daemon, one Ubuntu 16.04, other Ubuntu 18.04,

I was checking the log that didnt have debug=1 in it and couldnt see anything stick out,

by crash, I mean it started up and I typically keep entering "biblepay-cli getinfo" to check its progress, but it would give me some RPC error and biblepayd wouldnt be inside "ps -ef", and Id have to start it up again, and then it would crash again

I just downloaded the one that had debug=1 on, about to go through it, 80mb debug file

=

I believe this is the relevant section of the debug.log, hopefully it is and Im not wasting your time
(uploaded it to file hosting site, 4.7MB)
https://ufile.io/pqaao2vj

=

Code: [Select]
2019-05-08 04:50:28  ABN OK: 1.000000 LoadExternalBlockFile: Processing out of order child 7d37aaa250a86221b5ba434365aec3dc127183af7ccbabdec9367b7e9fa14719 of 4e5bcad04e7082d25315cfc964b463c70f8053de1e68013e532ce38f43d78d95
2019-05-08 04:50:28 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at CBlockDiskPos(nFile=0, nPos=39353)
2019-05-08 04:50:28 *** Failed to read block
2019-05-08 04:50:28 Error: Error: A fatal internal error occurred, see debug.log for details
...
2019-05-08 04:50:28 Interrupting HTTP server
2019-05-08 04:50:28 Interrupting HTTP RPC server
2019-05-08 04:50:28 Interrupting RPC
2019-05-08 04:50:28 Exited http event loop
2019-05-08 04:50:28 addcon thread exit
2019-05-08 04:50:28 mncon thread exit
...
2019-05-08 04:50:28 PrepareShutdown: In progress...
2019-05-08 04:50:28 Stopping HTTP RPC server
2019-05-08 04:50:28 Unregistering HTTP handler for / (exactmatch 1)
2019-05-08 04:50:28 Stopping RPC
2019-05-08 04:50:28 RPC stopped.
2019-05-08 04:50:28 Stopping HTTP server
2019-05-08 04:50:28 Waiting for HTTP worker threads to exit
2019-05-08 04:50:28 Waiting for HTTP event thread to exit
2019-05-08 04:50:28 Stopped HTTP server
2019-05-08 04:50:28 CDBEnv::Flush: Flush(false)
2019-05-08 04:50:28 CDBEnv::Flush: wallet.dat checkpoint
2019-05-08 04:50:28 CDBEnv::Flush: wallet.dat detach
2019-05-08 04:50:28
BiblepayMiner -- terminated
 0CDBEnv::Flush: wallet.dat closed

Is this the culprit?
Code: [Select]
2019-05-08 04:50:28 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at CBlockDiskPos(nFile=0, nPos=39353)
2019-05-08 04:50:28 *** Failed to read block
2019-05-08 04:50:28 Error: Error: A fatal internal error occurred, see debug.log for details

=

From other logs it seems typically theres:
Code: [Select]
ThreadRPCServer method=stopor with GUI
Code: [Select]
GUI: requestShutdown : Requesting shutdown
GUI: shutdown : Running Shutdown in thread
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 08, 2019, 04:30:57 pm
v1.4.2.8b, both Ubuntu, both command line daemon, one Ubuntu 16.04, other Ubuntu 18.04,

I was checking the log that didnt have debug=1 in it and couldnt see anything stick out,

by crash, I mean it started up and I typically keep entering "biblepay-cli getinfo" to check its progress, but it would give me some RPC error and biblepayd wouldnt be inside "ps -ef", and Id have to start it up again, and then it would crash again

I just downloaded the one that had debug=1 on, about to go through it, 80mb debug file

=

I believe this is the relevant section of the debug.log, hopefully it is and Im not wasting your time
(uploaded it to file hosting site, 4.7MB)
https://ufile.io/pqaao2vj

=

Code: [Select]
2019-05-08 04:50:28  ABN OK: 1.000000 LoadExternalBlockFile: Processing out of order child 7d37aaa250a86221b5ba434365aec3dc127183af7ccbabdec9367b7e9fa14719 of 4e5bcad04e7082d25315cfc964b463c70f8053de1e68013e532ce38f43d78d95
2019-05-08 04:50:28 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at CBlockDiskPos(nFile=0, nPos=39353)
2019-05-08 04:50:28 *** Failed to read block
2019-05-08 04:50:28 Error: Error: A fatal internal error occurred, see debug.log for details
...
2019-05-08 04:50:28 Interrupting HTTP server
2019-05-08 04:50:28 Interrupting HTTP RPC server
2019-05-08 04:50:28 Interrupting RPC
2019-05-08 04:50:28 Exited http event loop
2019-05-08 04:50:28 addcon thread exit
2019-05-08 04:50:28 mncon thread exit
...
2019-05-08 04:50:28 PrepareShutdown: In progress...
2019-05-08 04:50:28 Stopping HTTP RPC server
2019-05-08 04:50:28 Unregistering HTTP handler for / (exactmatch 1)
2019-05-08 04:50:28 Stopping RPC
2019-05-08 04:50:28 RPC stopped.
2019-05-08 04:50:28 Stopping HTTP server
2019-05-08 04:50:28 Waiting for HTTP worker threads to exit
2019-05-08 04:50:28 Waiting for HTTP event thread to exit
2019-05-08 04:50:28 Stopped HTTP server
2019-05-08 04:50:28 CDBEnv::Flush: Flush(false)
2019-05-08 04:50:28 CDBEnv::Flush: wallet.dat checkpoint
2019-05-08 04:50:28 CDBEnv::Flush: wallet.dat detach
2019-05-08 04:50:28
BiblepayMiner -- terminated
 0CDBEnv::Flush: wallet.dat closed

Is this the culprit?
Code: [Select]
2019-05-08 04:50:28 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at CBlockDiskPos(nFile=0, nPos=39353)
2019-05-08 04:50:28 *** Failed to read block
2019-05-08 04:50:28 Error: Error: A fatal internal error occurred, see debug.log for details

=

From other logs it seems typically theres:
Code: [Select]
ThreadRPCServer method=stopor with GUI
Code: [Select]
GUI: requestShutdown : Requesting shutdown
GUI: shutdown : Running Shutdown in thread


Thanks, got it (downloaded the file and analyzed).
At least I can tell you what exactly happened (that its not a systemic problem preventing release).

So in your case, your node ran and flushed the blocks db correctly on the prior run.
You ran it with reindex and it made it to height 21598 when it ran into a bad serialized block (IE the length pointer was longer than the maximum allowed data) meaning to biblepay, it believed the blocks database was corrupted.  This obviously was probably not corrupted but something the reindex did to the file instead.  For one it was reading the blocks out of order since height 1100, which is not too good for biblepay because of our contextual checkblock rules.

I personally have had a lot of problems with -reindex, so much that I stopped doing it (I always just sync from the network now). 
My non-optimal solution is to create a blocks file download in prod weekly or monthly for our users who want high performance download of the initial blocks from biblepay.org/snapshot for example.  We can make that a possibility when we hit around block 150K. 

In this case, the program handled the exception but obviously exited and that left you with no choice but to resync the chain.
Note that -reindex does work when the blocks are read in sequentially, but they are not guaranteed to be sequential in berkeleydb.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: togoshigekata on May 08, 2019, 04:46:00 pm
Thank you for looking into it Rob!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: vuli on May 09, 2019, 02:48:47 am
 gen=0 is the first thing I did.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 09, 2019, 03:12:47 am
Hi Guys,

I've upgraded to 1.4.2.8. My sanc says the following:
Quote
10:07:01

masternode status


10:07:01

{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "84.29.XXX.XXX:40001",
  "state": "WAITING_FOR_PROTX",
  "status": "Waiting for ProTx to appear on-chain"
}


My controller wallet shows the Sanc in the DIP3 tab though, and I've been getting payments?

I'm sorry. I don't have much time to dive into the Dash documentation :(
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 09, 2019, 07:56:11 am
Hi Guys,

I've upgraded to 1.4.2.8. My sanc says the following:
My controller wallet shows the Sanc in the DIP3 tab though, and I've been getting payments?

I'm sorry. I don't have much time to dive into the Dash documentation :(

Yeah, the payments will start deterministically based on this new algo, and continue until your node is PosE banned.  PosE happens if your node is Off for a certain amount of time (and gets voted down), or if your node isnt participating in the new LLMQs (long living masternode quorums).

As far as the node itself, it cant find its own proreg tx on the chain.
Most likely because the masternodeblsprivkey is missing.

Please copy the key from the deterministic.conf to the node and reboot it and see?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 09, 2019, 07:59:31 am
gen=0 is the first thing I did.
Well you will know if that is the problem if your node syncs to a certain height and stops syncing (as it tries to prefer the block you solved).  If you get enough connections it will recover though.

Let us know if you still have a problem.  I can always check my logs for your ip if you provide it.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 09, 2019, 10:18:08 am
Yeah, the payments will start deterministically based on this new algo, and continue until your node is PosE banned.  PosE happens if your node is Off for a certain amount of time (and gets voted down), or if your node isnt participating in the new LLMQs (long living masternode quorums).

As far as the node itself, it cant find its own proreg tx on the chain.
Most likely because the masternodeblsprivkey is missing.

Please copy the key from the deterministic.conf to the node and reboot it and see?

Working! Somehow a wrong private-key ended up in my masternodeblsprivkey. Probably got something to do that I used some Dash documentation when setting everything up...
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 11, 2019, 10:09:34 am
Before I draft an upgrade plan to transition to Evo I thought I would share my idea here first.

Please comment if you have any questions concerns or possible enhancements.
Also, I haven't heard any negative comments on POG/Healing or the payment system, and I assume everyone is happy with the payments compared to the coin age and the tithe levels.

Upgrade to Evo Plan of Action:

Around June 2nd 2019 (this is after our May monthly superblock pays out in biblepay-classic): (Height approx 124000):
At this height, all Sanctuaries must upgrade to Evo, and re-lock 4.5MM in Legacy Sanc mode.
Notify entire network to upgrade to Evo (also at 124,000).  Note: The entire network will be running in classic mode in Evo, with non-deterministic sancs.
Notify exchanges to upgrade at height 124,000 (this is Optional, but I think for best practices, we will ask them to upgrade along with us at 124,000).
Pools upgrade at 124,000 also.

The goal from blocks 124,000 through blocks 131,000 will be to finish upgrading all sancs to non-deterministic sancs, and through this entire period we will be in POBH (classic mode) - this will also give a little extra time for late upgraders who are running classic.  This plan also ensures that we do not break biblepay classics block structure while we upgrade to non-deterministic.  (Note that sanctuary payments will start as soon as approx 10 sancs upgrade (this will most likely happen the first day - IE June 2nd).

At block 131,000 (after the June superblock budget is paid in Evo with non-deterministic sancs), we start upgrading to deterministic sancs (this should be a transparent change as we will not flip dip15 until block 138,000). 

At approx block 132,000, we will also enable GSCs, and QT.  ABN & Anti-GPU will be enabled around block 134,000 if the network is healthy in small phases.

After the July superblock (height 139,000) - we enable dip15 (which makes deterministic sancs permanent).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 11, 2019, 12:54:29 pm
We offer two beautiful things with GSCs: 

- We will be able to support orphan mining in the future without any major technical change.  I'm going to reach out to one of our vendors who said they are interested in evaluating this, and see if we can design this in as a possibility.  I think its feasible to offer this as our major replacement for PODC within a year (**only if this particular vendor is on-board with the DAP idea that anonymizes the identity of the sponsor).  This also aligns well with the DAC vision.

- Technically some day, we might be able to bring in PODC cancer mining again, as a GSC project on a smaller scale, just to flex our muscles (as GSCs support this technically).  However, I would ensure that we remove the Oracle first (as there is a way to accomplish that).  Realize this is a low priority (IE probably by 2021) since we have a larger and more exciting project coming by the end of this year that dwarfs PODC and consumes all of our resources.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 17, 2019, 03:48:56 pm
We are now in the final phases of testing.

I think at this time it would be prudent for us to do a dry run - testing the things that will happen soon in prod.

For one I am writing the scripts to build the 32 & 64 bit version for windows and deploy to our website for download.

So far we have been running the 32bit windows version.  Ill build a 64 bit version now, and post the link and lets ensure this 64bit runs on our windows machines against prod.

Oncoapp and I already tested both pool mining pools and HTTPS communication.

I suppose I can be the guinea pig to test a couple Production sancs (using 4.5MM each).
Im currently deleting all the files on a couple VMs readying these VMs for Evo, once this is ready, Ill take the plunge and set up an Evo sanc in prod (in non deterministic mode, btw).

NOTE:  It is very important we make it clear that we Do Not want any sancs in Prod to upgrade to Evo until the announcement and cutover height is posted, as I want our monthly superblock to pay out properly  ;).

MIP, do you think we will have a Mac build available by June 2nd?  It would be nice to give them an upgrade path.

Ive already confirmed with GIN that they are ready to upgrade to Evo.

EDIT:

Ok, if anyone wants to test the 64 bit build on windows:
https://biblepay.org/biblepayevo64.exe

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 18, 2019, 07:29:05 am
The 64-bit version seems to be running fine on my end thus far :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 18, 2019, 08:14:46 am
The 64-bit version seems to be running fine on my end thus far :)

Thanks, I appreciate it!

Yea I'm testing it now on the pool server and it looks like we do need a couple more classic functions that I thought we could retire to be added to Evo.  They will be out in a couple hours for the pools to continue testing (but these do not need to be tested by users or sancs).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 18, 2019, 09:50:07 am
I'm running 1.4.2.9-Evo on pool.biblepay.org now.

I PM'ed Licht with the problems and change requests.

Note that I will revert Pool.biblepay back to Classic tomorrow as Evo governance is not compatible with classic governance (IE we need to finish this governance cycle and rely on the pool to see votes and proposals, etc).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on May 18, 2019, 12:01:45 pm
We are now in the final phases of testing.

I think at this time it would be prudent for us to do a dry run - testing the things that will happen soon in prod.

For one I am writing the scripts to build the 32 & 64 bit version for windows and deploy to our website for download.

So far we have been running the 32bit windows version.  Ill build a 64 bit version now, and post the link and lets ensure this 64bit runs on our windows machines against prod.

Oncoapp and I already tested both pool mining pools and HTTPS communication.

I suppose I can be the guinea pig to test a couple Production sancs (using 4.5MM each).
Im currently deleting all the files on a couple VMs readying these VMs for Evo, once this is ready, Ill take the plunge and set up an Evo sanc in prod (in non deterministic mode, btw).

NOTE:  It is very important we make it clear that we Do Not want any sancs in Prod to upgrade to Evo until the announcement and cutover height is posted, as I want our monthly superblock to pay out properly  ;).

MIP, do you think we will have a Mac build available by June 2nd?  It would be nice to give them an upgrade path.

Ive already confirmed with GIN that they are ready to upgrade to Evo.

EDIT:

Ok, if anyone wants to test the 64 bit build on windows:
https://biblepay.org/biblepayevo64.exe

Thank you for your acknowledgement! Glad to be part of this project and the community of believers in Jesus and hence happy to help in this small way!

The UI is great and, as far as I can tell, installs and runs on Windows 10 64-bit (I needed to addnode my own classic sancs for it to find the block source) and it took quite a while to load from scratch. I have currently got it mining on the pool
http://www.purepool.org/main/miner/BFwWN5ohJLcUAn1H9urqUqaA9oqPUBJtbh/

The first one (1.4.2.8 EVO on mainnet compiled in Ubuntu 18.04) is still crunching
http://www.purepool.org/main/miner/BD9gmJ5vmPJtDewo9NyqUT7fJQgV39AW7R/

There appears some typos under "JESUS' CONCISE COMMANDMENTS"
Pure and undefiled religion before our God and Father is to care for orphans and widows in their distress, and to keep oneself from being polluted by the world. (John 1:27) - ref is actually James 1:27

Do not Store up Treasures on Earth where moth and rust destroy, and where thieves break in and steal, but Store up treasures in heaven, For where your treasure is, there your heart will be also. (ref is missing - Matt 6:19,20a,21)

The "Help - About Biblepay" Tab has some unnecessary boxes at the bottom of the screen.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on May 18, 2019, 01:52:23 pm
Thank you for your acknowledgement! Glad to be part of this project and the community of believers in Jesus and hence happy to help in this small way!

The UI is great and, as far as I can tell, installs and runs on Windows 10 64-bit (I needed to addnode my own classic sancs for it to find the block source) and it took quite a while to load from scratch. I have currently got it mining on the pool
http://www.purepool.org/main/miner/BFwWN5ohJLcUAn1H9urqUqaA9oqPUBJtbh/

The first one (1.4.2.8 EVO on mainnet compiled in Ubuntu 18.04) is still crunching
http://www.purepool.org/main/miner/BD9gmJ5vmPJtDewo9NyqUT7fJQgV39AW7R/

There appears some typos under "JESUS' CONCISE COMMANDMENTS"
Pure and undefiled religion before our God and Father is to care for orphans and widows in their distress, and to keep oneself from being polluted by the world. (John 1:27) - ref is actually James 1:27

Do not Store up Treasures on Earth where moth and rust destroy, and where thieves break in and steal, but Store up treasures in heaven, For where your treasure is, there your heart will be also. (ref is missing - Matt 6:19,20a,21)

The "Help - About Biblepay" Tab has some unnecessary boxes at the bottom of the screen.
Testing some more relevant EVO commands on mainnet

11:15:57 exec cpk oncoapop2

11:15:58 {
  "Command": "cpk",
  "Results": true}

...

11:22:56 exec getcampaigns

11:22:56 {
  "List Of": "BiblePay Campaigns",
  "List Of": "BiblePay CPKs",
  "member [oncoapop2]": "BDpyRr2d9kWDD7MEyyJuAJxwvJpmLEGyqr",
  "member [[email protected]]": "BEv63xKxjAvZpQMCG2dzpLU7wTCcUhpRYd",
  "List Of": "Campaign Participants"}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 18, 2019, 02:02:25 pm
Thank you for your acknowledgement! Glad to be part of this project and the community of believers in Jesus and hence happy to help in this small way!

The UI is great and, as far as I can tell, installs and runs on Windows 10 64-bit (I needed to addnode my own classic sancs for it to find the block source) and it took quite a while to load from scratch. I have currently got it mining on the pool
http://www.purepool.org/main/miner/BFwWN5ohJLcUAn1H9urqUqaA9oqPUBJtbh/

The first one (1.4.2.8 EVO on mainnet compiled in Ubuntu 18.04) is still crunching
http://www.purepool.org/main/miner/BD9gmJ5vmPJtDewo9NyqUT7fJQgV39AW7R/

There appears some typos under "JESUS' CONCISE COMMANDMENTS"
Pure and undefiled religion before our God and Father is to care for orphans and widows in their distress, and to keep oneself from being polluted by the world. (John 1:27) - ref is actually James 1:27

Do not Store up Treasures on Earth where moth and rust destroy, and where thieves break in and steal, but Store up treasures in heaven, For where your treasure is, there your heart will be also. (ref is missing - Matt 6:19,20a,21)

The "Help - About Biblepay" Tab has some unnecessary boxes at the bottom of the screen.
Wow, well thank you very much kind sir!  I'm also impressed that you have created your own domain with notes.
Do I know you from anywhere or did you just recently find BiblePay?

Thats great the build is working on Win10; thanks goes to Dash for ensuring the base is cross-windows compatible (I mean registry and c++ pinvoke calls etc).

Thats awesome the two miners are still working, I did look at your first miner a couple times and that was very valuable for us.

Ok, let me fix these typos right now.  Good catch on the John 1:27, interesting.

I'll look at the unecessary boxes now also.

Thanks a lot for all your help btw, it was instrumental in creating a quality product!

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 18, 2019, 02:37:46 pm
************************************************************************

                      THANK YOU ALL FOR TESTING BIBLEPAY - EVOLUTION

************************************************************************


Let us pray this version is the most stable and beneficial version for our Orphans and God's Kingdom.


Testing is not completely over, but I wanted to send a warm thank you to everyone who contributed in any way in this TestNet thread!



God Bless you All!

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 18, 2019, 02:53:05 pm
Loading from scratch, and seed node not found in prod-evo.


So I thought I would address these two issues separately:

1.  The loading from scratch is a little slow right now, but Evos block loader is different than classic.  Note that once the supermajority is on evo, Evo will actually transmit compact blocks (compressed) using more than one thread, so that should speed up the time for people syncing from zero at that time.

2.  Regarding being unable to find the seed node, I confirm that due to my current Evo expirimentation being on dns1-dns3, Ive caused most of the prod evo seed nodes to be down - it should not be affecting biblepay-classic however because we have more in classic.  Im currently fixing the problem, once we have those 3 up again this will be mitigaged - note that as long as an Evo node can find 1 node, it will immediately pull in the other "friends" and start syncing, so Im sure this will be resolved also.

3.  In the near future, probably around Thanksgiving, we can also create snapshots.  This will allow someone to sync in about 5 mins using a zip file and a couple clicks to get it bootstrapped (we might need a button in the wallet to make it easy to download the snapshot).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 18, 2019, 03:25:38 pm
Thank you for your acknowledgement! Glad to be part of this project and the community of believers in Jesus and hence happy to help in this small way!

The UI is great and, as far as I can tell, installs and runs on Windows 10 64-bit (I needed to addnode my own classic sancs for it to find the block source) and it took quite a while to load from scratch. I have currently got it mining on the pool
http://www.purepool.org/main/miner/BFwWN5ohJLcUAn1H9urqUqaA9oqPUBJtbh/

The first one (1.4.2.8 EVO on mainnet compiled in Ubuntu 18.04) is still crunching
http://www.purepool.org/main/miner/BD9gmJ5vmPJtDewo9NyqUT7fJQgV39AW7R/

There appears some typos under "JESUS' CONCISE COMMANDMENTS"
Pure and undefiled religion before our God and Father is to care for orphans and widows in their distress, and to keep oneself from being polluted by the world. (John 1:27) - ref is actually James 1:27

Do not Store up Treasures on Earth where moth and rust destroy, and where thieves break in and steal, but Store up treasures in heaven, For where your treasure is, there your heart will be also. (ref is missing - Matt 6:19,20a,21)

The "Help - About Biblepay" Tab has some unnecessary boxes at the bottom of the screen.

Ok, I fixed the bad bible reference and added the other reference.  Good find on the About page, that was pretty ugly.  Fixed.
These changes will be in the next release (probably tomorrows release).



Good point on setting up the POG & Healing campaigns in prod; I will set those up ASAP and we can at least join and see if they appear to be initialized.  We cant really test more on that yet until the GSC height passes (123,200) and we have some 4.5MM sancs running in prod (more than the min_quorum of 10 set up).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on May 20, 2019, 12:08:41 pm
************************************************************************

                      THANK YOU ALL FOR TESTING BIBLEPAY - EVOLUTION

************************************************************************


Let us pray this version is the most stable and beneficial version for our Orphans and God's Kingdom.


Testing is not completely over, but I wanted to send a warm thank you to everyone who contributed in any way in this TestNet thread!



God Bless you All!

Thank you for all your hard work Rob :D
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on May 20, 2019, 04:42:07 pm
Hi,
after few days I'm back and I'm testing 64bit WIN version.
It's working good, but I've had problems with install.
My antivirus report it as Dyna:BitcoinMiner-CR [PUP]||mul and moved it to Virus vault.
But after set it as "trusted" it works good, mining and GSC is working good.

And maybe I found some bug.
There are Book and Chapter option in "About Biblepay Core" window, but they aren't working.
I cannot choose anything from it and it's empty.

And Rob you still didn't remove those old March debug.log from WIN install file and it's still more than 60MB big :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on May 20, 2019, 04:49:44 pm
Hi,
after few days I'm back and I'm testing 64bit WIN version.
It's working good, but I've had problems with install.
My antivirus report it as Dyna:BitcoinMiner-CR [PUP]||mul and moved it to Virus vault.
But after set it as "trusted" it works good, mining and GSC is working good.

And maybe I found some bug.
There are Book and Chapter option in "About Biblepay Core" window, but they aren't working.
I cannot choose anything from it and it's empty.

And Rob you still didn't remove those old March debug.log from WIN install file and it's still more than 60MB big :)

A) Testing the latest version, I click Bible | Read Bible, click a book and chapter and I see the contents, so I do not see a bug here.  Please be sure you are testing 1.4.3.1.  EDIT: 1.4.3.1 has no extra boxes in the About page - please re-test.

B)  Antivirus:  This is common with cryptos that have miners - the algorithm makes a false positive for that section, however the scan will eventually return negative once we have more than 100 downloads, so this should be solved (just like our prior versions of biblepaycore.exe).

C) On the log, I don't believe we copy the installer contents to %appdata%, are you sure this debug.log is not your log, could you please delete it and reinstall our EXE and see if we write it again?  If we do, Ill do a more in-depth search to see how we could have left that in our build process - Im 50-50 on this, could you help us by checking?  EDIT:  Please be sure this installer is the 1.4.3.1 installer.  I cleaned up the build directory before building 1.4.3.1. 
    EDIT:  I just tested 1.4.3.1 windows install - we don't write the debug.log to the %appdata% directory - please test again.


EDIT:  One thing I didn't explain, I've been deploying the 1.4.3.0+ versions to:
https://www.biblepay.org | See the top level Downloads Menu | Evolution downloads

This might be the problem.




Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: orbis on May 21, 2019, 10:59:33 am
A) Testing the latest version, I click Bible | Read Bible, click a book and chapter and I see the contents, so I do not see a bug here.  Please be sure you are testing 1.4.3.1.  EDIT: 1.4.3.1 has no extra boxes in the About page - please re-test.

B)  Antivirus:  This is common with cryptos that have miners - the algorithm makes a false positive for that section, however the scan will eventually return negative once we have more than 100 downloads, so this should be solved (just like our prior versions of biblepaycore.exe).

C) On the log, I don't believe we copy the installer contents to %appdata%, are you sure this debug.log is not your log, could you please delete it and reinstall our EXE and see if we write it again?  If we do, Ill do a more in-depth search to see how we could have left that in our build process - Im 50-50 on this, could you help us by checking?  EDIT:  Please be sure this installer is the 1.4.3.1 installer.  I cleaned up the build directory before building 1.4.3.1. 
    EDIT:  I just tested 1.4.3.1 windows install - we don't write the debug.log to the %appdata% directory - please test again.


EDIT:  One thing I didn't explain, I've been deploying the 1.4.3.0+ versions to:
https://www.biblepay.org | See the top level Downloads Menu | Evolution downloads

This might be the problem.
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.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews 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.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop 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 [[email protected]]": "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 [[email protected]]": "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
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop 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

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews 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.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop 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!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop 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%"
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop 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
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews 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.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews 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 [[email protected]]": "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 [[email protected]]": "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.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop 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.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews 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.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews 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.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews 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.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 18, 2019, 09:24:23 pm
Things to test in 1.4.3.5+ (0.14.0 branch features):

- Ability to Mine
- ABN
- ChainLocks
- Sanctuary Payments
- GSC quorums
- LLMQs
- Instant Send



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 18, 2019, 09:26:47 pm
Hello all, welcome baaack!

We are ready to test 1.4.5.1-develop.  This release primarily adds all of the things Dash added in the 0.14.0 branch recently (IE March 2019 through June 2019), things including ChainLocks and LLMQs.

We need to regression test everything we tested in BiblePay-Evo, such as GSCs and ABNs, since a lot has changed under the hood.

Lets also test watchman on the wall.

The Windows download link has changed; please see the OP post.

MIP, can you build us a Mac and please tell me if I need a new updated link?

Github source:
https://github.com/biblepay/biblepay-evolution
branch: develop

PS  -  Please verify you are testing v1.4.5.1+

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on June 19, 2019, 10:02:04 am
Hello all, welcome baaack!

We are ready to test 1.4.5.1-develop.  This release primarily adds all of the things Dash added in the 0.14.0 branch recently (IE March 2019 through June 2019), things including ChainLocks and LLMQs.

We need to regression test everything we tested in BiblePay-Evo, such as GSCs and ABNs, since a lot has changed under the hood.

Lets also test watchman on the wall.

The Windows download link has changed; please see the OP post.

MIP, can you build us a Mac and please tell me if I need a new updated link?

Github source:
https://github.com/biblepay/biblepay-evolution
branch: develop

PS  -  Please verify you are testing v1.4.5.1+

Just a question: are we testing first the activation of DIP0003 testnet sancs with current version (1.4.3.5) , then upgrade them to 1.4.5.1 ?
Or are we directly starting from brand new testnet sancs using 1.4.5.1 ?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on June 19, 2019, 01:24:48 pm
Testnet downloads

Linux PC 32bits
Daemon: https://biblepay.org/biblepayd-evo-testnet-i686-pc-linux-gnu.tar.gz
QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

Linux PC 64bits
Daemon: https://biblepay.org/biblepayd-evo--testnet-x86_64-pc-linux-gnu.tar.gz
QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

Linux ARM64 daemon: https://biblepay.org/biblepayd-evo-testnet-aarch64-linux-gnu.tar.gz
Linux ARM32 daemon: https://biblepay.org/biblepayd-evo-testnet-arm-linux-gnueabihf.tar.gz

MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 19, 2019, 02:08:30 pm
Just a question: are we testing first the activation of DIP0003 testnet sancs with current version (1.4.3.5) , then upgrade them to 1.4.5.1 ?
Or are we directly starting from brand new testnet sancs using 1.4.5.1 ?

Although our sancs are dip3 deterministic already in testnet as of our last leg of testing, we definitely need to upgrade our sancs to 1.4.5.1 and our home controller to 1.4.5.1 first; this way we will have coverage of all the code.  (As even our old code is being a hit a completely different way in 1.4.5.1 :).

Thanks....

HEY ALL:  Please don't upgrade yet - I have some news coming in from Cameroon One, and I believe we will need to release a GSC feature today into testnet, so lets hold off and get 1.4.5.2 out so we can test all this at the same time.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on June 19, 2019, 03:07:10 pm
Good, I will create a new sanc from scratch then. I will ask for tBBP coins when it’s ready.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 19, 2019, 03:09:23 pm
Good, I will create a new sanc from scratch then. I will ask for tBBP coins when it’s ready.

I believe you can just upgrade the sancs software, because remember during the last phase of testnet, we all ran the 'upgradesanc' command, so your sanc is probably already a deterministic sanc (if it was in the determistic dip3 list).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on June 19, 2019, 03:15:23 pm
I believe you can just upgrade the sancs software, because remember during the last phase of testnet, we all ran the 'upgradesanc' command, so your sanc is probably already a deterministic sanc (if it was in the determistic dip3 list).

Well the fact is that I dismantled the VPS so I will try starting all over again.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 19, 2019, 03:17:08 pm
Well the fact is that I dismantled the VPS so I will try starting all over again.
Yeah, that would do it!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 20, 2019, 05:34:52 pm
Good, I will create a new sanc from scratch then. I will ask for tBBP coins when it’s ready.

Let me know if you can sync to 108174 on the latest and Ill send you tbbp, what address?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on June 21, 2019, 07:43:11 am
Let me know if you can sync to 108174 on the latest and Ill send you tbbp, what address?

I think I have problems, I am in block 65397 and mining alone. I see these 2 peers
dns1.biblepay.org
dns3.biblepay.org

Both BiblePay Core:1.4.5.1/

I compiled using the latest changes you committed to origin/develop
How would I reach the right chain?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on June 21, 2019, 07:54:34 am
I tried to restart with reindex and then I get a fatal error after startup, then it shuts down.

debug.log
Code: [Select]
2019-06-21 12:50:23 Biblepay Core version 1.4.5.1
2019-06-21 12:50:23 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-06-21 12:50:24 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-06-21 12:50:24 GUI: QCssParser::parseHexColor: Unknown color name '#yellow'
2019-06-21 12:50:24 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-06-21 12:50:24 ***************************************** BIBLEPAY  ***************************************************
2019-06-21 12:50:24 ProdMode: Prod 0.000000BiblePayVersion 1.4.5.1 (BiblePay Core)
2019-06-21 12:50:24 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2019-06-21 12:50:24 Assuming ancestors of block 0000000005ae4db9746d6cad8e0ccebdef1e05afec9c40809f31457fdaf7d843 have valid signatures.
2019-06-21 12:50:24 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-06-21 12:50:24 GUI: QCssParser::parseHexColor: Unknown color name '#yellow'
2019-06-21 12:50:24 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-06-21 12:50:24 Default data directory /Users/mippl/Library/Application Support/BiblepayEvolution
2019-06-21 12:50:24 Using data directory /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3
2019-06-21 12:50:24 Using config file /Users/mippl/Library/Application Support/BiblepayEvolution/biblepay.conf
2019-06-21 12:50:24 Using at most 125 automatic connections (2560 file descriptors available)
2019-06-21 12:50:24 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2019-06-21 12:50:24 Using 2 threads for script verification
2019-06-21 12:50:24 scheduler thread start
2019-06-21 12:50:24 Creating backup of /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/wallet.dat -> /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/backups/wallet.dat.2019-06-21-12-50
2019-06-21 12:50:24 init message: Verifying wallet...
2019-06-21 12:50:24 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-06-21 12:50:24 Using wallet wallet.dat
2019-06-21 12:50:24 CDBEnv::Open: LogDir=/Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/database ErrorFile=/Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/db.log
2019-06-21 12:50:24 Bound to [::]:40001
2019-06-21 12:50:24 Bound to 0.0.0.0:40001
2019-06-21 12:50:24 init message: Loading KJV Bible...
2019-06-21 12:50:24 fLiteMode 0
2019-06-21 12:50:24 init message: Loading sporks cache...
2019-06-21 12:50:24 Reading info from sporks.dat...
2019-06-21 12:50:24 Loaded info from sporks.dat  1ms
2019-06-21 12:50:24      Sporks: 6
2019-06-21 12:50:24 Read: Cleaning....
2019-06-21 12:50:24      Sporks: 6
2019-06-21 12:50:24 Cache configuration:
2019-06-21 12:50:24 * Using 37.5MiB for block index database
2019-06-21 12:50:24 * Using 8.0MiB for chain state database
2019-06-21 12:50:24 * Using 254.5MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2019-06-21 12:50:24 init message: Loading block index...
2019-06-21 12:50:24 Opening LevelDB in /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/evodb
2019-06-21 12:50:24 Opened LevelDB successfully
2019-06-21 12:50:24 Using obfuscation key for /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/evodb: 0000000000000000
2019-06-21 12:50:24 Opening LevelDB in /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/blocks/index
2019-06-21 12:50:25 Opened LevelDB successfully
2019-06-21 12:50:25 Using obfuscation key for /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/blocks/index: 0000000000000000
2019-06-21 12:50:25 Opening LevelDB in /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/chainstate
2019-06-21 12:50:25 Opened LevelDB successfully
2019-06-21 12:50:25 Using obfuscation key for /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/chainstate: aeb0dfd04bd0e95c
2019-06-21 12:50:25 Opening LevelDB in /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/llmq
2019-06-21 12:50:25 Opened LevelDB successfully
2019-06-21 12:50:25 Using obfuscation key for /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/llmq: 0000000000000000
2019-06-21 12:50:25  Last Checkpoint Height 60000 LoadBlockIndexDB: last block file = 0
2019-06-21 12:50:26 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=56456, size=95047122, heights=0...56450, time=2017-06-01...2019-06-21)
2019-06-21 12:50:26 Checking all blk files are present...
2019-06-21 12:50:26 LoadBlockIndexDB: transaction index enabled
2019-06-21 12:50:26 LoadBlockIndexDB: address index disabled
2019-06-21 12:50:26 LoadBlockIndexDB: timestamp index disabled
2019-06-21 12:50:26 LoadBlockIndexDB: spent index disabled
2019-06-21 12:50:26 LoadBlockIndexDB: hashBestChain=3cce38b13a313242f075275416e6ec300a6692dc7e25a64bff6d8e51c25e6a7b height=97 date=2019-03-30 16:47:51 progress=0.001010
2019-06-21 12:50:26 init message: Verifying blocks...
2019-06-21 12:50:26 Verifying last 6 blocks at level 3
2019-06-21 12:50:26 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2019-06-21 12:50:26 No coin database inconsistencies in last 7 blocks (7 transactions)
2019-06-21 12:50:26  block index            1214ms
2019-06-21 12:50:26 init message: Loading wallet...
2019-06-21 12:50:26 nKeysLeftSinceAutoBackup: 999
2019-06-21 12:50:26 nFileVersion = 1040501
2019-06-21 12:50:26 Keys: 1003 plaintext, 0 encrypted, 1003 w/ metadata, 1003 total
2019-06-21 12:50:26  wallet                   68ms
2019-06-21 12:50:26 setExternalKeyPool.size() = 999
2019-06-21 12:50:26 setInternalKeyPool.size() = 0
2019-06-21 12:50:26 mapWallet.size() = 20
2019-06-21 12:50:26 mapAddressBook.size() = 1
2019-06-21 12:50:26 PrivateSend liquidityprovider: 0
2019-06-21 12:50:26 PrivateSend rounds: 2
2019-06-21 12:50:26 PrivateSend amount: 25000
2019-06-21 12:50:26 PrivateSend denoms: 3000
2019-06-21 12:50:26 sigshares thread start
2019-06-21 12:50:26 mapBlockIndex.size() = 56456
2019-06-21 12:50:26 chainActive.Height() = 97
2019-06-21 12:50:26 instantsend thread start
2019-06-21 12:50:26 Reindexing block file blk00000.dat...
2019-06-21 12:50:26 init message: Memorizing Prayers...
2019-06-21 12:50:26 torcontrol thread start
2019-06-21 12:50:26
Deserializing prayers from file 1561121426 Processed 67 prayer rows - 1561121426
2019-06-21 12:50:26  Chain Height 97, Loading entire prayer index
2019-06-21 12:50:26 Memorizing prayers tip height 97 @ time 1561121426 deserialized height 0 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: unspecified iostream_category error at CBlockDiskPos(nFile=0, nPos=20577)
2019-06-21 12:50:26 *** Failed to read block
2019-06-21 12:50:26 ...Finished MemorizeBlockChainPrayers @ 1561121426 init message: Discovering Peers...
2019-06-21 12:50:26 init message: Loading P2P addresses...
2019-06-21 12:50:26 Loaded 47 addresses from peers.dat  1ms
2019-06-21 12:50:26 init message: Loading banlist...
2019-06-21 12:50:26 init message: Starting network threads...
2019-06-21 12:50:26 net thread start
2019-06-21 12:50:26 dnsseed thread start
2019-06-21 12:50:26 opencon thread start
2019-06-21 12:50:26 addcon thread start
2019-06-21 12:50:26 mncon thread start
2019-06-21 12:50:26 msghand thread start
2019-06-21 12:50:26 init message: Starting Miner...
2019-06-21 12:50:26 BibleMiner -- started thread 0.000000
2019-06-21 12:50:26  MinerSleep 325.000000
2019-06-21 12:50:26  ** Started 1.000000 BibleMiner threads. **
2019-06-21 12:50:26 init message: Done loading
2019-06-21 12:50:26 keypool added key 1004, size=1000, internal=0
2019-06-21 12:50:26 init message: Loading wallet... (100.30 %)
2019-06-21 12:50:26 keypool reserve 5
2019-06-21 12:50:28 Reindexing finished
2019-06-21 12:50:28
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.{PNB}: ACC  Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired
2019-06-21 12:50:28 tor: Thread interrupt
2019-06-21 12:50:28 torcontrol thread exit
2019-06-21 12:50:28 sigshares thread exit
2019-06-21 12:50:28 dnsseed thread exit
2019-06-21 12:50:28 mncon thread exit
2019-06-21 12:50:28 addcon thread exit
2019-06-21 12:50:28 opencon thread exit
2019-06-21 12:50:28 instantsend thread exit
2019-06-21 12:50:28 scheduler thread interrupt
2019-06-21 12:50:28 PrepareShutdown: In progress...
2019-06-21 12:50:28 keypool return 5
2019-06-21 12:50:28 net thread exit
2019-06-21 12:50:28 msghand thread exit
2019-06-21 12:50:28 Verifying mncache.dat format...
2019-06-21 12:50:28 Loaded info from mncache.dat  1ms
2019-06-21 12:50:28      Masternodes: meta infos object count: 0, deterministic masternode count: 0, nDsqCount: 0
2019-06-21 12:50:28 Writing info to mncache.dat...
2019-06-21 12:50:28 Written info to mncache.dat  1ms
2019-06-21 12:50:28      Masternodes: meta infos object count: 0, deterministic masternode count: 0, nDsqCount: 0
2019-06-21 12:50:28 mncache.dat dump finished  2ms
2019-06-21 12:50:28 Verifying governance.dat format...
2019-06-21 12:50:28 Loaded info from governance.dat  1ms
2019-06-21 12:50:28      Governance Objects: 0 (Proposals: 0, Triggers: 0, Other: 0; Erased: 0), Votes: 0
2019-06-21 12:50:28 Writing info to governance.dat...
2019-06-21 12:50:28 Written info to governance.dat  0ms
2019-06-21 12:50:28      Governance Objects: 0 (Proposals: 0, Triggers: 0, Other: 0; Erased: 0), Votes: 0
2019-06-21 12:50:28 governance.dat dump finished  2ms
2019-06-21 12:50:28 Verifying netfulfilled.dat format...
2019-06-21 12:50:28 Loaded info from netfulfilled.dat  0ms
2019-06-21 12:50:28      Nodes with fulfilled requests: 2
2019-06-21 12:50:28 Writing info to netfulfilled.dat...
2019-06-21 12:50:28 Written info to netfulfilled.dat  1ms
2019-06-21 12:50:28      Nodes with fulfilled requests: 0
2019-06-21 12:50:28 netfulfilled.dat dump finished  1ms
2019-06-21 12:50:28 Verifying instantsend.dat format...
2019-06-21 12:50:28 Loaded info from instantsend.dat  0ms
2019-06-21 12:50:28      Lock Candidates: 0, Votes 0
2019-06-21 12:50:28 Writing info to instantsend.dat...
2019-06-21 12:50:28 Written info to instantsend.dat  0ms
2019-06-21 12:50:28      Lock Candidates: 0, Votes 0
2019-06-21 12:50:28 instantsend.dat dump finished  1ms
2019-06-21 12:50:28 Verifying sporks.dat format...
2019-06-21 12:50:28 Loaded info from sporks.dat  0ms
2019-06-21 12:50:28      Sporks: 6
2019-06-21 12:50:28 Writing info to sporks.dat...
2019-06-21 12:50:28 Written info to sporks.dat  0ms
2019-06-21 12:50:28      Sporks: 6
2019-06-21 12:50:28 sporks.dat dump finished  0ms
2019-06-21 12:50:28 Shutdown: done

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 21, 2019, 08:01:54 am
I tried to restart with reindex and then I get a fatal error after startup, then it shuts down.

debug.log
Code: [Select]
2019-06-21 12:50:23 Biblepay Core version 1.4.5.1
2019-06-21 12:50:23 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-06-21 12:50:24 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-06-21 12:50:24 GUI: QCssParser::parseHexColor: Unknown color name '#yellow'
2019-06-21 12:50:24 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-06-21 12:50:24 ***************************************** BIBLEPAY  ***************************************************
2019-06-21 12:50:24 ProdMode: Prod 0.000000BiblePayVersion 1.4.5.1 (BiblePay Core)
2019-06-21 12:50:24 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2019-06-21 12:50:24 Assuming ancestors of block 0000000005ae4db9746d6cad8e0ccebdef1e05afec9c40809f31457fdaf7d843 have valid signatures.
2019-06-21 12:50:24 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-06-21 12:50:24 GUI: QCssParser::parseHexColor: Unknown color name '#yellow'
2019-06-21 12:50:24 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-06-21 12:50:24 Default data directory /Users/mippl/Library/Application Support/BiblepayEvolution
2019-06-21 12:50:24 Using data directory /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3
2019-06-21 12:50:24 Using config file /Users/mippl/Library/Application Support/BiblepayEvolution/biblepay.conf
2019-06-21 12:50:24 Using at most 125 automatic connections (2560 file descriptors available)
2019-06-21 12:50:24 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2019-06-21 12:50:24 Using 2 threads for script verification
2019-06-21 12:50:24 scheduler thread start
2019-06-21 12:50:24 Creating backup of /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/wallet.dat -> /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/backups/wallet.dat.2019-06-21-12-50
2019-06-21 12:50:24 init message: Verifying wallet...
2019-06-21 12:50:24 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-06-21 12:50:24 Using wallet wallet.dat
2019-06-21 12:50:24 CDBEnv::Open: LogDir=/Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/database ErrorFile=/Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/db.log
2019-06-21 12:50:24 Bound to [::]:40001
2019-06-21 12:50:24 Bound to 0.0.0.0:40001
2019-06-21 12:50:24 init message: Loading KJV Bible...
2019-06-21 12:50:24 fLiteMode 0
2019-06-21 12:50:24 init message: Loading sporks cache...
2019-06-21 12:50:24 Reading info from sporks.dat...
2019-06-21 12:50:24 Loaded info from sporks.dat  1ms
2019-06-21 12:50:24      Sporks: 6
2019-06-21 12:50:24 Read: Cleaning....
2019-06-21 12:50:24      Sporks: 6
2019-06-21 12:50:24 Cache configuration:
2019-06-21 12:50:24 * Using 37.5MiB for block index database
2019-06-21 12:50:24 * Using 8.0MiB for chain state database
2019-06-21 12:50:24 * Using 254.5MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2019-06-21 12:50:24 init message: Loading block index...
2019-06-21 12:50:24 Opening LevelDB in /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/evodb
2019-06-21 12:50:24 Opened LevelDB successfully
2019-06-21 12:50:24 Using obfuscation key for /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/evodb: 0000000000000000
2019-06-21 12:50:24 Opening LevelDB in /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/blocks/index
2019-06-21 12:50:25 Opened LevelDB successfully
2019-06-21 12:50:25 Using obfuscation key for /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/blocks/index: 0000000000000000
2019-06-21 12:50:25 Opening LevelDB in /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/chainstate
2019-06-21 12:50:25 Opened LevelDB successfully
2019-06-21 12:50:25 Using obfuscation key for /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/chainstate: aeb0dfd04bd0e95c
2019-06-21 12:50:25 Opening LevelDB in /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/llmq
2019-06-21 12:50:25 Opened LevelDB successfully
2019-06-21 12:50:25 Using obfuscation key for /Users/mippl/Library/Application Support/BiblepayEvolution/testnet3/llmq: 0000000000000000
2019-06-21 12:50:25  Last Checkpoint Height 60000 LoadBlockIndexDB: last block file = 0
2019-06-21 12:50:26 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=56456, size=95047122, heights=0...56450, time=2017-06-01...2019-06-21)
2019-06-21 12:50:26 Checking all blk files are present...
2019-06-21 12:50:26 LoadBlockIndexDB: transaction index enabled
2019-06-21 12:50:26 LoadBlockIndexDB: address index disabled
2019-06-21 12:50:26 LoadBlockIndexDB: timestamp index disabled
2019-06-21 12:50:26 LoadBlockIndexDB: spent index disabled
2019-06-21 12:50:26 LoadBlockIndexDB: hashBestChain=3cce38b13a313242f075275416e6ec300a6692dc7e25a64bff6d8e51c25e6a7b height=97 date=2019-03-30 16:47:51 progress=0.001010
2019-06-21 12:50:26 init message: Verifying blocks...
2019-06-21 12:50:26 Verifying last 6 blocks at level 3
2019-06-21 12:50:26 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2019-06-21 12:50:26 No coin database inconsistencies in last 7 blocks (7 transactions)
2019-06-21 12:50:26  block index            1214ms
2019-06-21 12:50:26 init message: Loading wallet...
2019-06-21 12:50:26 nKeysLeftSinceAutoBackup: 999
2019-06-21 12:50:26 nFileVersion = 1040501
2019-06-21 12:50:26 Keys: 1003 plaintext, 0 encrypted, 1003 w/ metadata, 1003 total
2019-06-21 12:50:26  wallet                   68ms
2019-06-21 12:50:26 setExternalKeyPool.size() = 999
2019-06-21 12:50:26 setInternalKeyPool.size() = 0
2019-06-21 12:50:26 mapWallet.size() = 20
2019-06-21 12:50:26 mapAddressBook.size() = 1
2019-06-21 12:50:26 PrivateSend liquidityprovider: 0
2019-06-21 12:50:26 PrivateSend rounds: 2
2019-06-21 12:50:26 PrivateSend amount: 25000
2019-06-21 12:50:26 PrivateSend denoms: 3000
2019-06-21 12:50:26 sigshares thread start
2019-06-21 12:50:26 mapBlockIndex.size() = 56456
2019-06-21 12:50:26 chainActive.Height() = 97
2019-06-21 12:50:26 instantsend thread start
2019-06-21 12:50:26 Reindexing block file blk00000.dat...
2019-06-21 12:50:26 init message: Memorizing Prayers...
2019-06-21 12:50:26 torcontrol thread start
2019-06-21 12:50:26
Deserializing prayers from file 1561121426 Processed 67 prayer rows - 1561121426
2019-06-21 12:50:26  Chain Height 97, Loading entire prayer index
2019-06-21 12:50:26 Memorizing prayers tip height 97 @ time 1561121426 deserialized height 0 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: unspecified iostream_category error at CBlockDiskPos(nFile=0, nPos=20577)
2019-06-21 12:50:26 *** Failed to read block
2019-06-21 12:50:26 ...Finished MemorizeBlockChainPrayers @ 1561121426 init message: Discovering Peers...
2019-06-21 12:50:26 init message: Loading P2P addresses...
2019-06-21 12:50:26 Loaded 47 addresses from peers.dat  1ms
2019-06-21 12:50:26 init message: Loading banlist...
2019-06-21 12:50:26 init message: Starting network threads...
2019-06-21 12:50:26 net thread start
2019-06-21 12:50:26 dnsseed thread start
2019-06-21 12:50:26 opencon thread start
2019-06-21 12:50:26 addcon thread start
2019-06-21 12:50:26 mncon thread start
2019-06-21 12:50:26 msghand thread start
2019-06-21 12:50:26 init message: Starting Miner...
2019-06-21 12:50:26 BibleMiner -- started thread 0.000000
2019-06-21 12:50:26  MinerSleep 325.000000
2019-06-21 12:50:26  ** Started 1.000000 BibleMiner threads. **
2019-06-21 12:50:26 init message: Done loading
2019-06-21 12:50:26 keypool added key 1004, size=1000, internal=0
2019-06-21 12:50:26 init message: Loading wallet... (100.30 %)
2019-06-21 12:50:26 keypool reserve 5
2019-06-21 12:50:28 Reindexing finished
2019-06-21 12:50:28
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.{PNB}: ACC  Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired
2019-06-21 12:50:28 tor: Thread interrupt
2019-06-21 12:50:28 torcontrol thread exit
2019-06-21 12:50:28 sigshares thread exit
2019-06-21 12:50:28 dnsseed thread exit
2019-06-21 12:50:28 mncon thread exit
2019-06-21 12:50:28 addcon thread exit
2019-06-21 12:50:28 opencon thread exit
2019-06-21 12:50:28 instantsend thread exit
2019-06-21 12:50:28 scheduler thread interrupt
2019-06-21 12:50:28 PrepareShutdown: In progress...
2019-06-21 12:50:28 keypool return 5
2019-06-21 12:50:28 net thread exit
2019-06-21 12:50:28 msghand thread exit
2019-06-21 12:50:28 Verifying mncache.dat format...
2019-06-21 12:50:28 Loaded info from mncache.dat  1ms
2019-06-21 12:50:28      Masternodes: meta infos object count: 0, deterministic masternode count: 0, nDsqCount: 0
2019-06-21 12:50:28 Writing info to mncache.dat...
2019-06-21 12:50:28 Written info to mncache.dat  1ms
2019-06-21 12:50:28      Masternodes: meta infos object count: 0, deterministic masternode count: 0, nDsqCount: 0
2019-06-21 12:50:28 mncache.dat dump finished  2ms
2019-06-21 12:50:28 Verifying governance.dat format...
2019-06-21 12:50:28 Loaded info from governance.dat  1ms
2019-06-21 12:50:28      Governance Objects: 0 (Proposals: 0, Triggers: 0, Other: 0; Erased: 0), Votes: 0
2019-06-21 12:50:28 Writing info to governance.dat...
2019-06-21 12:50:28 Written info to governance.dat  0ms
2019-06-21 12:50:28      Governance Objects: 0 (Proposals: 0, Triggers: 0, Other: 0; Erased: 0), Votes: 0
2019-06-21 12:50:28 governance.dat dump finished  2ms
2019-06-21 12:50:28 Verifying netfulfilled.dat format...
2019-06-21 12:50:28 Loaded info from netfulfilled.dat  0ms
2019-06-21 12:50:28      Nodes with fulfilled requests: 2
2019-06-21 12:50:28 Writing info to netfulfilled.dat...
2019-06-21 12:50:28 Written info to netfulfilled.dat  1ms
2019-06-21 12:50:28      Nodes with fulfilled requests: 0
2019-06-21 12:50:28 netfulfilled.dat dump finished  1ms
2019-06-21 12:50:28 Verifying instantsend.dat format...
2019-06-21 12:50:28 Loaded info from instantsend.dat  0ms
2019-06-21 12:50:28      Lock Candidates: 0, Votes 0
2019-06-21 12:50:28 Writing info to instantsend.dat...
2019-06-21 12:50:28 Written info to instantsend.dat  0ms
2019-06-21 12:50:28      Lock Candidates: 0, Votes 0
2019-06-21 12:50:28 instantsend.dat dump finished  1ms
2019-06-21 12:50:28 Verifying sporks.dat format...
2019-06-21 12:50:28 Loaded info from sporks.dat  0ms
2019-06-21 12:50:28      Sporks: 6
2019-06-21 12:50:28 Writing info to sporks.dat...
2019-06-21 12:50:28 Written info to sporks.dat  0ms
2019-06-21 12:50:28      Sporks: 6
2019-06-21 12:50:28 sporks.dat dump finished  0ms
2019-06-21 12:50:28 Shutdown: done



-reindex does not work on any version of Evo properly.  Lets see if we can debug that root cause. 

(I have been deleting the chain files in contrast to reindexing).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on June 21, 2019, 08:04:09 am

-reindex does not work on any version of Evo properly.  Lets see if we can debug that root cause. 

(I have been deleting the chain files in contrast to reindexing).

Sure I'll go for it and inform back
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 21, 2019, 08:15:34 am
I think I have problems, I am in block 65397 and mining alone. I see these 2 peers
dns1.biblepay.org
dns3.biblepay.org

Both BiblePay Core:1.4.5.1/

I compiled using the latest changes you committed to origin/develop
How would I reach the right chain?

I committed again a couple hours ago, its been a volatile day trying to get this last issue working.

I cant guarantee we are ready for a compile, but please try now - I am synced on 3 nodes and syncing from 0 works now.

Still need to test the actual sanctuary GSC voter though.

For now you have to : Delete evodb, blocks, chainstate, and the gov* and mnc* and mnp* files before resyncing (Important to delete those .dat files as the evodb caches must be clean).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 22, 2019, 09:46:23 am
Testnet downloads

Linux PC 32bits
Daemon: https://biblepay.org/biblepayd-evo-testnet-i686-pc-linux-gnu.tar.gz
QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

Linux PC 64bits
Daemon: https://biblepay.org/biblepayd-evo--testnet-x86_64-pc-linux-gnu.tar.gz
QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

Linux ARM64 daemon: https://biblepay.org/biblepayd-evo-testnet-aarch64-linux-gnu.tar.gz
Linux ARM32 daemon: https://biblepay.org/biblepayd-evo-testnet-arm-linux-gnueabihf.tar.gz

MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg

Thanks, I added these to the OP post.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 22, 2019, 09:47:22 am
Ok all, it appears 'relatively safe' to start a round of testing.

Last night I unit tested most of the normal features in Evo and they appear to be working now (and we are syncing), so lets test this on a bigger scale.

The version is now 1.4.5.2.

Please see the OP post for download info.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 22, 2019, 04:59:44 pm
1.4.5.3 - Mandatory upgrade for TestNet

- Fix bug not allowing GSC contracts to create in 0.14 branch
- Reward 0 for unlocked sanctuary VIN coinage

Windows, linux, and Mac have been deployed.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 22, 2019, 09:51:21 pm
1.4.5.4 - Mandatory upgrade for TestNet

- Cement cameroon-one daily sponsorship cap using sporks
- Fix bug in listchildren all (to show multiple sponsorships per CPK)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: jaapgvk on June 23, 2019, 01:03:48 am
I'll spin up some nodes in the coming week :)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 23, 2019, 09:07:23 am
I'll spin up some nodes in the coming week :)

Thanks!

I have 3 sancs running now.  This last version emitted a GSC. 

I will test Cameroon One next.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 23, 2019, 09:09:26 am
Is everyone else in sync, I have 3 sancs + 1 home node running with this hash:


09:08:34

getblockhash 112120


09:08:34

ea3ec1fa2ba94dbfd54e34d6de99217ee12b1a3bed715b78c9498bb3e45d30c6



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 23, 2019, 12:39:43 pm
I just got paid for a Cameroon One orphan in my home testnet wallet!  This has got to be one of the most exciting times ever for BiblePay for me...


I'm excited.  I received 2388 bbp (this was the capped amount) for an orphan.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on June 25, 2019, 04:42:49 am
Is everyone else in sync, I have 3 sancs + 1 home node running with this hash:


09:08:34

getblockhash 112120


09:08:34

ea3ec1fa2ba94dbfd54e34d6de99217ee12b1a3bed715b78c9498bb3e45d30c6


I am finally here with a Sanc.

BTW the setup for 0.14.x (our 1.5) is slightly different as masternode key changes. I will reflect this in the masternode-install.sh script.

v1.4.x (before DIP3, our mainnet now)
mnkey=$(biblepay-cli masternode genkey)

then in biblepay.conf
masternodeprivkey=$(mnkey)

v1.5.x (after DIP3, our testnet now)
mnkey=$(biblepay-cli bls generate | jq '.secret' -r)

then in biblepay.conf
masternodeblsprivkey=$(mnkey)

Being jq a JSON tool that parses the "secret" variable from the bls generate RPC command.

Could you please send tBBP for the test Sanc?
ycVHVvJs64u7DzvPsEFRjSksUj7h7k8qQo
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 25, 2019, 11:23:05 pm
I am finally here with a Sanc.

BTW the setup for 0.14.x (our 1.5) is slightly different as masternode key changes. I will reflect this in the masternode-install.sh script.

v1.4.x (before DIP3, our mainnet now)
mnkey=$(biblepay-cli masternode genkey)

then in biblepay.conf
masternodeprivkey=$(mnkey)

v1.5.x (after DIP3, our testnet now)
mnkey=$(biblepay-cli bls generate | jq '.secret' -r)

then in biblepay.conf
masternodeblsprivkey=$(mnkey)

Being jq a JSON tool that parses the "secret" variable from the bls generate RPC command.

Could you please send tBBP for the test Sanc?
ycVHVvJs64u7DzvPsEFRjSksUj7h7k8qQo

Sent 20 MM.

Ill have to comment on the rest tomorrow, its getting late.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 27, 2019, 07:58:32 pm
Sent 20 MM.

Ill have to comment on the rest tomorrow, its getting late.

So, commenting on this:

Code: [Select]

I am finally here with a Sanc.

BTW the setup for 0.14.x (our 1.5) is slightly different as masternode key changes. I will reflect this in the masternode-install.sh script.

v1.4.x (before DIP3, our mainnet now)
mnkey=$(biblepay-cli masternode genkey)

then in biblepay.conf
masternodeprivkey=$(mnkey)

v1.5.x (after DIP3, our testnet now)
mnkey=$(biblepay-cli bls generate | jq '.secret' -r)

then in biblepay.conf
masternodeblsprivkey=$(mnkey)

Being jq a JSON tool that parses the "secret" variable from the bls generate RPC command.

Could you please send tBBP for the test Sanc?
ycVHVvJs64u7DzvPsEFRjSksUj7h7k8qQo



Thats good to know, and I will be using Dashs method to start a new sanc (eventually), but just in case everyone didnt forget the BiblePay way (this was really created to make it easy to upgrade a non deterministic to a deterministic), here is how you can make a sanc the "old" way in this version.  I just did this purposefully to make sure we didnt break anything:

- Send collateral out to yourself in your controller wallet
- Double click the Tx, and copy the txid and remember the output vout # (IE 0 or 1)
- Add this to your masternode.conf the old way:  the Name, IP:Port, 1 for the MNP Key, TXID, and VOUT #

From biblepay type:

exec upgradesanc sanc_name 1

I have created a new one today using this method and it worked.

! NOTE !  Do make a backup of your deterministic.conf file!  This is important because it has your BLS private key in it!  Then you can use it to recreate your cold sanc if you erase your sanc.





Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 27, 2019, 07:59:05 pm
Has anyone synced yet?

I'm about ready to test Cameroon One.

I need to know if any other sancs are started and syced?  If so what IPs?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on June 29, 2019, 01:09:03 am
I am not sure I am on the right testnet chain now.
Btw I'm compiling testnet binaries now:

Code: [Select]
getinfo
{
  "version": 1040504,
  "protocolversion": 70734,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 119723,
  "timeoffset": 0,
  "connections": 4,
  "proxy": "",
  "difficulty": 0.0238397584092306,
  "testnet": true,
  "keypoololdest": 1561125575,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 0.01000000,
  "errors": ""
}

getblockhash 112120
9e556a5ddd29a1d0b6a01fca08b1d10ecfda29d6960acb389b2a7427936a070a
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 29, 2019, 09:38:40 am
I am not sure I am on the right testnet chain now.
Btw I'm compiling testnet binaries now:

Code: [Select]
getinfo
{
  "version": 1040504,
  "protocolversion": 70734,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 119723,
  "timeoffset": 0,
  "connections": 4,
  "proxy": "",
  "difficulty": 0.0238397584092306,
  "testnet": true,
  "keypoololdest": 1561125575,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 0.01000000,
  "errors": ""
}

getblockhash 112120
9e556a5ddd29a1d0b6a01fca08b1d10ecfda29d6960acb389b2a7427936a070a

Yeah, I think you are on the chain.  How many sancs u have?  Can you please give me an IP of a deterministic sanc in your list u created?

Also what kind of exec health, do you show?  We should see a few votes in exec health.


Btw - I re-sent the 20MM.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on June 29, 2019, 06:50:35 pm
So here it is

IP: 155.138.196.75:40001
Tell me if you need anything else and I'll check tomorrow (now it's 2am here gotta sleep)

Code: [Select]
01:47:53

exec health


01:47:55

{
  "Command": "health",
  "pam_hash": "000000000000000000000000000000009ee4308db3b4748771f487176878ea62",
  "pam_hash_internal": "000000000000000000000000000000009ee4308db3b4748771f487176878ea62",
  "govobjhash": "2f5a6716533f0d84e4b0422b36e749b7256164a6ad25c519826e2ca325b06ead",
  "Amounts": "614340.00",
  "Addresses": "yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe",
  "votes": 4,
  "required_votes": 3,
  "last_superblock": 120970,
  "next_superblock": 121175,
  "next_superblock_triggered": true,
  "Healthy": true,
  "GSC_Voted_In": true
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on June 29, 2019, 06:58:42 pm
So here it is

IP: 155.138.196.75:40001
Tell me if you need anything else and I'll check tomorrow (now it's 2am here gotta sleep)

Code: [Select]
01:47:53

exec health


01:47:55

{
  "Command": "health",
  "pam_hash": "000000000000000000000000000000009ee4308db3b4748771f487176878ea62",
  "pam_hash_internal": "000000000000000000000000000000009ee4308db3b4748771f487176878ea62",
  "govobjhash": "2f5a6716533f0d84e4b0422b36e749b7256164a6ad25c519826e2ca325b06ead",
  "Amounts": "614340.00",
  "Addresses": "yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe",
  "votes": 4,
  "required_votes": 3,
  "last_superblock": 120970,
  "next_superblock": 121175,
  "next_superblock_triggered": true,
  "Healthy": true,
  "GSC_Voted_In": true
}

Yes, things are looking pretty good in testnet now, I see your sanc in my Dip3 list, and I see that you voted on the latest contract.

So, before we get deep into Cameroon, lets try a couple basic things for sanity sake.

Please join POG and create a CPK, then please type 'exec sendgscc'. 
Lets make sure you appear in the leaderboard and receive a GSC reward.

Remember when you create your cpk to set your nickname so we can see you 'exec cpk nick'

Thanks.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 01, 2019, 10:12:34 am
Is anyone having trouble getting started?  The version should be 1.4.5.4 - please see if you are running the latest.

So far, we have one tester: MIP, and he is on a road trip.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 01, 2019, 04:22:50 pm
I got the GSC reward after yesterday's exec sendgscc so that part went great.

I will be around for a while for more tests
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 01, 2019, 04:29:48 pm
I got the GSC reward after yesterday's exec sendgscc so that part went great.

I will be around for a while for more tests

OK, I see you in the leaderboard now; it says you have 558,360 owed.

Ok let me see what else we need to test.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 01, 2019, 04:31:03 pm
OK, I see you in the leaderboard now; it says you have 558,360 owed.

Ok let me see what else we need to test.
Can you paste your exec health?  We should see no errors and 4 votes.

Also, please turn on your miner, are you mining successfully with > HPS than 100?

Lets try turning on ABN - I will set it to 1000 now.



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 01, 2019, 04:38:46 pm
I got the GSC reward after yesterday's exec sendgscc so that part went great.

I will be around for a while for more tests

So lets try sponsoring a child with cameroon.

MIP, can you please type 'sponsorchild' then add 'authorize' to it when you are ready to spend 50K to sponsor the child.
Then wait 6 confirms and type 'listchildren' and see if the child is listed.  If so, please paste the child hex ID, so we can simulate a sponsorship payment.  Also let me know how much you want to apply to the childs balance (via fake paypal or fake check #).  The first charge is always $40.00 US.

Note that we might want to do this on one of your nodes that isnt sending big POG gsc updates - IE please see if you can reverse engineer the reward for cameroon from the POG reward (or set up POG so you make a tiny donation).

Actually, now that I remember this, we can do the exec analyze on your nickname, and see the Cameroon One amount, so dont worry about reverse engineering or POG, as we should see a row for POGs reward and a row for Cameroons reward.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 01, 2019, 04:46:10 pm
Can you paste your exec health?  We should see no errors and 4 votes.

Also, please turn on your miner, are you mining successfully with > HPS than 100?

Lets try turning on ABN - I will set it to 1000 now.


23:45:19

exec health


23:45:21

{
  "Command": "health",
  "pam_hash": "000000000000000000000000000000004fa0d3cb92b2b914227690996590c9c8",
  "pam_hash_internal": "000000000000000000000000000000004fa0d3cb92b2b914227690996590c9c8",
  "govobjhash": "adac147312f3fe4f2284f2a9ded1237096162cff8a594b616e016cce2f7e65ba",
  "Amounts": "149585.00|455377.00",
  "Addresses": "yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
  "votes": 4,
  "required_votes": 3,
  "last_superblock": 124865,
  "next_superblock": 125070,
  "next_superblock_triggered": true,
  "Healthy": true,
  "GSC_Voted_In": true
}


23:45:12

getmininginfo


23:45:12

{
  "blocks": 124966,
  "currentblocksize": 15260,
  "currentblocktx": 5,
  "difficulty": 0.174020205303215,
  "errors": "",
  "pooledtx": 4,
  "chain": "test",
  "genproclimit": 1,
  "networkhashps": 343.5861770010965,
  "hashps": 339.6838113307749,
  "minerstarttime": "07-01-2019 21:18:39",
  "hashcounter": 299345,
  "pooledtx": 4,
  "chain": "test",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "abninfo": "[1000 ABN OK] Amount=7671.00, Weight=7365.08; ",
  "gsc_errors": "",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 1000
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 01, 2019, 04:49:00 pm
So lets try sponsoring a child with cameroon.

MIP, can you please type 'sponsorchild' then add 'authorize' to it when you are ready to spend 50K to sponsor the child.
Then wait 6 confirms and type 'listchildren' and see if the child is listed.  If so, please paste the child hex ID, so we can simulate a sponsorship payment.  Also let me know how much you want to apply to the childs balance (via fake paypal or fake check #).  The first charge is always $40.00 US.

Note that we might want to do this on one of your nodes that isnt sending big POG gsc updates - IE please see if you can reverse engineer the reward for cameroon from the POG reward (or set up POG so you make a tiny donation).

Actually, now that I remember this, we can do the exec analyze on your nickname, and see the Cameroon One amount, so dont worry about reverse engineering or POG, as we should see a row for POGs reward and a row for Cameroons reward.


23:46:52

sponsorchild authorize


23:46:52

{
  "Results": true,
  "Notes 0": "Thank you for sponsoring a child through Cameroon One. ",
  "Notes 1": "Your new child ID is: abaad3ec",
  "Notes 2": "NOTE: You will not receive rewards for this child until Cameroon One posts a credit to your account for this child.  ",
  "Notes 3": "It can take 7-14 days to provision a new child, receive and post your payment, so please, be patient. ",
  "Notes 4": "To check the status of your child, type 'listchildren' into the RPC.",
  "Notes 5": "Option 1:  Please mail a check for $40.00 (this is a tax deductible donation) to:",
  "Notes 6": "Cameroon One A/R",
  "Notes 7": "28 Hawthorne St Unit 1",
  "Notes 8": "Boston, MA 02119 USA",
  "Notes 9": "!NOTE! You must write Child ID #abaad3ec on your check.",
  "Notes 10": "Option 2: [Preferred] For the most efficient/fastest credit use PayPal (accepting Credit Cards and international payments):",
  "Notes 11": "PayPal: Send money to https://PayPal.Me/CameroonONE ",
  "Notes 12": "NOTE: Please paste the BiblePay hex child ID #abaad3ec in the Paypal NOTES textbox before submitting the payment.",
  "Notes 13": "Option 3:  GlobalGiving Match:",
  "Notes 14": "To use Global Giving, see this page https://www.globalgiving.org/recurring-donations-matched/ and set up a recurring donation, then notify Anna with CameroonONE <[email protected]> with your ChildID and verify the recurring donation is set up.",
  "Notes 15": ""
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 01, 2019, 05:10:42 pm
Now I think I don't have enough ABN weight so I'm not mining and no blocks are being mined.


00:09:27

exec getabnweight


00:09:27

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 26756016.61004648,
  "total_required": 17733092
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 01, 2019, 08:49:43 pm
Now I think I don't have enough ABN weight so I'm not mining and no blocks are being mined.


00:09:27

exec getabnweight


00:09:27

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 26756016.61004648,
  "total_required": 17733092
}


Hmm, actually no one is mining right now due to some very strange error in the log.  Checking.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 02, 2019, 11:43:12 am

Hmm, actually no one is mining right now due to some very strange error in the log.  Checking.

Ok, the problem in testnet turned out to be a division error in our branch only.  It was not a Dash or Biblepay development error, its an error rooted in floating point math that is only exploited in a chain with very high Satoshi scale like us.


The new version will be out in an hour.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 02, 2019, 03:45:09 pm
All linux & mac binaries are ready. I am back mining again.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 02, 2019, 04:37:32 pm
BiblePay
1.4.5.5 - Mandatory upgrade for TestNet

- Require proto_version 70735 in testnet
- Remove log spam
- Dont allow people to tithe more than 500 inputs
- Fix bug in Deterministic Payment comparison (appears to be confined to coins with very high satoshi scales - like us)
- Make govobj ddos more unique (allows devs to debug govobj propagation issues)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 02, 2019, 07:18:53 pm
BiblePay
1.4.5.5 - Mandatory upgrade for TestNet

- Require proto_version 70735 in testnet
- Remove log spam
- Dont allow people to tithe more than 500 inputs
- Fix bug in Deterministic Payment comparison (appears to be confined to coins with very high satoshi scales - like us)
- Make govobj ddos more unique (allows devs to debug govobj propagation issues)


Hey all - please don't upgrade yet - I see one more problem that needs addressed.

Im working on it.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 02, 2019, 08:54:18 pm
BiblePay
1.4.5.6 - Mandatory Upgrade for TestNet

- Fix sanctuary split issue (Require ABN fees to be added into total block fees)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 03, 2019, 10:12:16 am
Does everyone agree with this hash:

10:11:38

getblockhash 124999


10:11:38

250787d6b1cf87b15f69bf3009eccc56017270b7142d7d4960b6a1281350a3b2


* Note that you may have to resync as we are now in pure dip3 mode.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 03, 2019, 11:37:32 am
All linux & mac binaries are ready. I am back mining again.

And on Cameroon-One, I forgot to mention, and its OK you have already sponsored a child (we will add a test to ensure this is in order for the next version), but please also do this MIP:

exec join cameroon-one

You must be a member of the campaign for the sancs to "see you" in the campaign.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 03, 2019, 01:31:42 pm
I am back to help. Resurrected old wallet from previous testnet and everything was as before. Upgraded to latest version and synced to the current block and agrees with published blockhash.

Tried the following which can be verified on blockchain:
Exec cpk oncoapop1 true
Exec join cameroon-one
Sponsorchild authorize ( 3 times)
And they appear in listchildren
Also exec sendgscc
Exec sendgscc “diary entry”
Both appear on leaderboard but % does not appear on Healing (too small fraction?).
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 03, 2019, 01:38:45 pm
Old sanc that I resurrected  is 45.62.239.400. Same exact server.

Strange, it was on the blockchain even though the server was off or running something else and once on didn’t need the controller wallet at all.

Maybe you can verify if it was receiving rewards previously since as far as i know the same server was deployed on mainchain.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 03, 2019, 02:27:39 pm
Old sanc that I resurrected  is 45.62.239.400. Same exact server.

Strange, it was on the blockchain even though the server was off or running something else and once on didn’t need the controller wallet at all.

Maybe you can verify if it was receiving rewards previously since as far as i know the same server was deployed on mainchain.

Great to have you join; So I do see the 45.62.239.200 (not 400) but I see this 200 was paid @ 125356.
Yes I do see oncoapop1 owed 65% of the kitty in the leaderboard.

If you want to help me test cameroonone, please join the 'cameroon-one' exec join cameroon-one, then 'sponsorchild authorize' then send me the child ID and the amount you want to send a fake check in for and Ill credit your cameroon one account in testnet. 

EDIT: Actually could you go ahead and sponsor 3 children?  This way we can see if MIP gets 1 payment, randrews2 gets 2 payments and oncoapop1 gets 3 payments?

PS:  Yeah, I think you made it through without resyncing because since you were off, you didnt violate any consensus rules and after you upgraded, you synced as normal forward.  Btw, the reason you didnt need to restart the server is the other sancs didnt POSE ban you yet (plus, in dip3 mode, they restart automatically - the dash devs removed the start button etc and integrated the auto-start logic into dip3).  But Ive seen some of our sancs get POSE banned in Prod - I had to restart some of mine a few times.  The main difference should be that we wont have to manually click start, they will go down, we will fix the sancs problem, then they will autostart in this version (in prod).



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 03, 2019, 02:50:32 pm
Great!
Sorry typo 45.62.239.200

Yes, actually done those commands which can be verified on the blockchain.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 03, 2019, 02:52:50 pm
Listchildren shows the 3 are “not provisioned yet”.....

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 03, 2019, 04:27:40 pm
Listchildren shows the 3 are “not provisioned yet”.....

Ok, good.  Please paste the 3 hex-child-id codes for your children (this simulates you notifying cameroon by paying by paypal or check) and give me an amount you want credited to your cameroon account in USD?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 03, 2019, 04:51:36 pm
  "Child ID": "2c587757",100
  "Child ID": "576df3e6",50
  "Child ID": "62021cdb",25

Thx
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 03, 2019, 05:02:27 pm
  "Child ID": "2c587757",100
  "Child ID": "576df3e6",50
  "Child ID": "62021cdb",25

Thx

Ok good; I have credited your 3 balances as per your payments, now when you type listchildren, you should see the actual outstanding balance as if Cameroon charged you $40.00 for each child on July 1st (its $40 per month).

So notice that your 3rd child is not fully paid.
The way this works is the API will return -999 if the child is not provisioned (that means Cameroon has not actually assigned the hex ID to a real child).  Those, whether they have negative balances or not do not get rewarded in BBP.

Next, only the people with negative balances (and provisioned children) get rewarded BBP.

So, if you do an exec sendgscc, what should technically happen is we should send a GSC tx (one tx) with 3 children in it, and, you should only be rewarded for 2 of the children (the 2 with credit balances).

So, to check the payment, check the exec leaderboard, or look in the UI leaderboard, and look in the "details" for the actual Cameroon one detail rows.  You should end up with 2,666 points (because cameroon charges us $1.33 per day).

Now heres where it gets tricky.  We never reward a user more than $1.33 per day even if we have only a partial superblock.
So knowing the output of exec price yields a BBP price of $.000507 per USD, the wallet will automatically arrive at what is called a daily sponsorship cap.
You can get this value by typing exec dailysponsorshipcap.

Knowing the sponsorshipcap, it will reward you about 2500 bbp or so (I forget the exact #) in rewards per child.

So once you get your rewards, please do the math and see if your two children paid you $2.66 today? 
Remember in testnet, we have 4 blocks per day, so you will end up with 4* the amount in 24 hours.

I believe people who leave their miner off will end up being shorted (so they have to actually mine) in order for a gsc transmission to go out every day and get the daily reward back.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 03, 2019, 05:07:23 pm
One more thing, to test:

1) You should see -60, -10, and +15 balances for the children, since they were debited $40 to start and all 3 are provisioned now.

2)  This will be verrry tricky.  Rule 2a) Regardless of sending more than one exec sendgscc in a given superblock interval, you should only receive *one* payment per child (per superblock interval). 
Rule 2b)  If you participated in homogenized POG and or Healing, you should also receive the same regression tested amount you are used to (we should do an exec analyze height nickname, and verify the actual points->reward didn't change after adding Cameroon) (This is basically a Cameroon one regression test, to ensure we did not break Prod's POG point allocation amounts or payment amounts).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 03, 2019, 05:07:57 pm
Code: [Select]
{
  "List Of": "Cameroon-One Children",
  "Child ID": "2c587757",
  "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
  "Biography": "https://cameroonone.org/biblepay/2c587757.htm",
  "Balance": -999,
  "Notes": "This child is not provisioned yet.",
  "Nickname": "oncoapop1",
  "Child ID": "576df3e6",
  "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
  "Biography": "https://cameroonone.org/biblepay/576df3e6.htm",
  "Balance": -999,
  "Notes": "This child is not provisioned yet.",
  "Nickname": "oncoapop1",
  "Child ID": "62021cdb",
  "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
  "Biography": "https://cameroonone.org/biblepay/62021cdb.htm",
  "Balance": -999,
  "Notes": "This child is not provisioned yet.",
  "Nickname": "oncoapop1"
}
$ cli listchildren | grep ID
  "Child ID": "2c587757",100
  "Child ID": "576df3e6",50
  "Child ID": "62021cdb",25
{
  "List Of": "Cameroon-One Children",
  "Child ID": "2c587757",
  "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
  "Biography": "https://cameroonone.org/biblepay/2c587757.htm",
  "Balance": -60,
  "Nickname": "oncoapop1",
  "Child ID": "576df3e6",
  "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
  "Biography": "https://cameroonone.org/biblepay/576df3e6.htm",
  "Balance": -10,
  "Nickname": "oncoapop1",
  "Child ID": "62021cdb",
  "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
  "Biography": "https://cameroonone.org/biblepay/62021cdb.htm",
  "Balance": 15,
  "Nickname": "oncoapop1"
}

Ok. The math is a bit more involved so i will have to calculate it later...
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 03, 2019, 05:35:19 pm


What I want to point out is that the …200 sanc is my current sanc. The other one is the IP of my router which I have just checked that NONE of my machines (at that address) are running biblepayd and yet BOTH are enabled on the blockchain… The port 40001 isn’t even reachable for .238 and yet it appears to be still getting paid even more recently than my current .200 sanc....

Code: [Select]
$ sanc list
{
...
 },
 "51a7d0cdb93fb3377d274f1b448af3c260618eb23c145a52c6c2fc081192b4dc-1": {
   "proTxHash": "3fdfa35533185427856e07d7a966714d118c7434994b5d6a349c11558e79e290",
   "address": "45.62.239.200:40001",
   "payee": "yRKdex8fFcDyjqx618Cz4hsQcQFjp55jRg",
   "status": "ENABLED",
   "lastpaidtime": 1562191975,
   "lastpaidblock": 125601,
   "owneraddress": "yhDJCUZq19CVLiuDa4wEoY4PxWg17bZuTx",
   "votingaddress": "yhDJCUZq19CVLiuDa4wEoY4PxWg17bZuTx",
   "collateraladdress": "yMm52BQvFgjtSjHLhohQbF5zmTYkBc4JWb",
   "pubkeyoperator": "05f58c1b79e898cf31a0375ded7a8e5bb6b0e5aacb48dc79f7c87e38eb0533bdf85c610cee5cf94b79c425c20f423cc4"
 },
 "0df4d38dee8b4233d250b05dd8773ec320292d16a6b2e7c008ffb58d976a259e-1": {
   "proTxHash": "7b5c9e029fd9d220e244ab9516a6196ec98a6a5a22fab6890da2f20a80cc971c",
   "address": "64.180.194.238:40001",
   "payee": "yeVEt6ivbyJnhR96Uh7ckt9j3gy3MRDaKF",
   "status": "ENABLED",
   "lastpaidtime": 1562191896,
   "lastpaidblock": 125598,
   "owneraddress": "yfu6HiZiEEUvwd5Bt6BEzvCP2heSgguCZE",
   "votingaddress": "yfu6HiZiEEUvwd5Bt6BEzvCP2heSgguCZE",
   "collateraladdress": "yc5iiRK3bxSDRqziqMPNZ7qEHxnYzvckkH",
   "pubkeyoperator": "0bd2ef8af156182399cac5d63e6e4f79a8877d79b514791178a9ffdd54e5378f31a28522033ec0e2519027845a15ef37"
 }
}
[email protected]:~/charity/Sanctuary$ telnet 64.180.194.238 40001
Trying 64.180.194.238...
telnet: Unable to connect to remote host: Connection refused
..
[email protected]:~/charity/Sanctuary$ telnet 45.62.239.200 40001
Trying 45.62.239.200...
Connected to 45.62.239.200.






Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 04, 2019, 10:43:48 am
And on Cameroon-One, I forgot to mention, and its OK you have already sponsored a child (we will add a test to ensure this is in order for the next version), but please also do this MIP:

exec join cameroon-one

You must be a member of the campaign for the sancs to "see you" in the campaign.

Done!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 04, 2019, 12:20:38 pm

What I want to point out is that the …200 sanc is my current sanc. The other one is the IP of my router which I have just checked that NONE of my machines (at that address) are running biblepayd and yet BOTH are enabled on the blockchain… The port 40001 isn’t even reachable for .238 and yet it appears to be still getting paid even more recently than my current .200 sanc....

Code: [Select]
$ sanc list
{
...
 },
 "51a7d0cdb93fb3377d274f1b448af3c260618eb23c145a52c6c2fc081192b4dc-1": {
   "proTxHash": "3fdfa35533185427856e07d7a966714d118c7434994b5d6a349c11558e79e290",
   "address": "45.62.239.200:40001",
   "payee": "yRKdex8fFcDyjqx618Cz4hsQcQFjp55jRg",
   "status": "ENABLED",
   "lastpaidtime": 1562191975,
   "lastpaidblock": 125601,
   "owneraddress": "yhDJCUZq19CVLiuDa4wEoY4PxWg17bZuTx",
   "votingaddress": "yhDJCUZq19CVLiuDa4wEoY4PxWg17bZuTx",
   "collateraladdress": "yMm52BQvFgjtSjHLhohQbF5zmTYkBc4JWb",
   "pubkeyoperator": "05f58c1b79e898cf31a0375ded7a8e5bb6b0e5aacb48dc79f7c87e38eb0533bdf85c610cee5cf94b79c425c20f423cc4"
 },
 "0df4d38dee8b4233d250b05dd8773ec320292d16a6b2e7c008ffb58d976a259e-1": {
   "proTxHash": "7b5c9e029fd9d220e244ab9516a6196ec98a6a5a22fab6890da2f20a80cc971c",
   "address": "64.180.194.238:40001",
   "payee": "yeVEt6ivbyJnhR96Uh7ckt9j3gy3MRDaKF",
   "status": "ENABLED",
   "lastpaidtime": 1562191896,
   "lastpaidblock": 125598,
   "owneraddress": "yfu6HiZiEEUvwd5Bt6BEzvCP2heSgguCZE",
   "votingaddress": "yfu6HiZiEEUvwd5Bt6BEzvCP2heSgguCZE",
   "collateraladdress": "yc5iiRK3bxSDRqziqMPNZ7qEHxnYzvckkH",
   "pubkeyoperator": "0bd2ef8af156182399cac5d63e6e4f79a8877d79b514791178a9ffdd54e5378f31a28522033ec0e2519027845a15ef37"
 }
}
[email protected]:~/charity/Sanctuary$ telnet 64.180.194.238 40001
Trying 64.180.194.238...
telnet: Unable to connect to remote host: Connection refused
..
[email protected]:~/charity/Sanctuary$ telnet 45.62.239.200 40001
Trying 45.62.239.200...
Connected to 45.62.239.200.


Diagnosing the problem...


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 04, 2019, 02:46:50 pm
POG calculation
CoinAge x (tithe)^1/3
4,021,756 x (1,300)^1/3 = 4,021,756 x 10.9139288 = 43,893,155
plus 2,666=43,895,821 (close enough)

Within superblock (height 127415-127256 = 159 blocks), send another gscc +2666 points
Usertotal = 43,898,493

Perhaps I didn’t understand it but this means that I was awarded points TWICE WITHIN the same superblock….

also the price function does not appear to work and I cannot see if the fiat is correct.


Code: [Select]

cli exec analyze 127426 oncoapop1
{
 "Command": "analyze",
 "Totals": "CAMEROON-ONE|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|2667|0.00687494|oncoapop1|2668\nPOG|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|43893160|0.64629026|oncoapop1|44145110\n",
 "0": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127256.00, TXID: cd1a328f8316753e2899b8447db915c74f49105971f1cea144afba924115d64c, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 34196721.3301, Donation: 0.0000, UserTotal: 2666.67",
 "1": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127399.00, TXID: ab31c0f4818188b1dd8e3ae9ad8d76514dd8750401ba603f2d45c3000f33b240, NickName: oncoapop1, Points: 43893160.43, Campaign: POG, CoinAge: 4021756.1531, Donation: 1300.0000, UserTotal: 43895827.10",
 "2": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127415.00, TXID: 3c99a32dfc1d984f2030bcfe21fb6cf9344a79d9b1243ead698e3947c580a99c, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 4711.9792, Donation: 0.0000, UserTotal: 43898493.76",
 "3": ""
}

cli listchildren
{
 "List Of": "Cameroon-One Children",
 "Child ID": "2c587757",
 "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
 "Biography": "https://cameroonone.org/biblepay/2c587757.htm",
 "Balance": -60,
 "Nickname": "oncoapop1",
 "Child ID": "576df3e6",
 "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
 "Biography": "https://cameroonone.org/biblepay/576df3e6.htm",
 "Balance": -10,
 "Nickname": "oncoapop1",
 "Child ID": "62021cdb",
 "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
 "Biography": "https://cameroonone.org/biblepay/62021cdb.htm",
 "Balance": 15,
 "Nickname": "oncoapop1"
}

Cameroon points  - only count negative balances (ie we are up-to-date with the payments?) = 2
points awarded = 2,666 (CORRECT)

exec dailysponsorshipcap
{
 "Command": "dailysponsorshipcap",
 "cap": 0.003436608621582211
}

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

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 04, 2019, 03:52:35 pm
POG calculation
CoinAge x (tithe)^1/3
4,021,756 x (1,300)^1/3 = 4,021,756 x 10.9139288 = 43,893,155
plus 2,666=43,895,821 (close enough)

Within superblock (height 127415-127256 = 159 blocks), send another gscc +2666 points
Usertotal = 43,898,493

Perhaps I didn’t understand it but this means that I was awarded points TWICE WITHIN the same superblock….

also the price function does not appear to work and I cannot see if the fiat is correct.


Code: [Select]

cli exec analyze 127426 oncoapop1
{
 "Command": "analyze",
 "Totals": "CAMEROON-ONE|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|2667|0.00687494|oncoapop1|2668\nPOG|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|43893160|0.64629026|oncoapop1|44145110\n",
 "0": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127256.00, TXID: cd1a328f8316753e2899b8447db915c74f49105971f1cea144afba924115d64c, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 34196721.3301, Donation: 0.0000, UserTotal: 2666.67",
 "1": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127399.00, TXID: ab31c0f4818188b1dd8e3ae9ad8d76514dd8750401ba603f2d45c3000f33b240, NickName: oncoapop1, Points: 43893160.43, Campaign: POG, CoinAge: 4021756.1531, Donation: 1300.0000, UserTotal: 43895827.10",
 "2": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127415.00, TXID: 3c99a32dfc1d984f2030bcfe21fb6cf9344a79d9b1243ead698e3947c580a99c, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 4711.9792, Donation: 0.0000, UserTotal: 43898493.76",
 "3": ""
}

cli listchildren
{
 "List Of": "Cameroon-One Children",
 "Child ID": "2c587757",
 "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
 "Biography": "https://cameroonone.org/biblepay/2c587757.htm",
 "Balance": -60,
 "Nickname": "oncoapop1",
 "Child ID": "576df3e6",
 "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
 "Biography": "https://cameroonone.org/biblepay/576df3e6.htm",
 "Balance": -10,
 "Nickname": "oncoapop1",
 "Child ID": "62021cdb",
 "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
 "Biography": "https://cameroonone.org/biblepay/62021cdb.htm",
 "Balance": 15,
 "Nickname": "oncoapop1"
}

Cameroon points  - only count negative balances (ie we are up-to-date with the payments?) = 2
points awarded = 2,666 (CORRECT)

exec dailysponsorshipcap
{
 "Command": "dailysponsorshipcap",
 "cap": 0.003436608621582211
}

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



1) I am still working on the POSE issue (regarding the nodes that were non-reachable) - we will have a release to analyze and mitigate.

2) Regarding exec price, there was a missing spork; fixed.  Now you can do the exec price.

3)  Regarding your exec analyze 127426 oncoapop1 results, I see you were paid only once per orphan (1333 points * 2 active orphans = 2666 points) in superblock for 127426.  I like how your points analysis almost matches exactly for the legacy POG point rewards compared to actual rewards, I believe that confirms the POG points, but please lets check the next superblock with that formula also.
  As far as double payments,  we have a superblock once every 6 hours in Testnet, so when you receive your *next* 2666 points it should be at *a higher height*.  You should be able to see this in exec analyze, because the cutoff will be clear, each new superblock height should reward you with payments for 2 children.

EDIT:  Oh, sorry, I see you do have two rows for one height... Interesting.  We specifically coded against that scenario.  OK, I will check this out now.

Thanks.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 04, 2019, 08:12:11 pm
1. Tithe normally via Cameroon-One

Code: [Select]
{
 "Prominence": "Details",
 "CAMEROON-ONE: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 1333.00": "0.27%",
 "CAMEROON-ONE: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.55%",
 "POG: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 3022707.00": "53.72%",
 "POG: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 634626.00": "11.28%",
 "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 0.00": "0.00%",
 "Healing": "Diary Entries",
 "Prominence": "Totals",
 "ALL: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 3024040.00, Reward: 502530.690": "53.990%",
 "ALL: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 634626.00, Reward: 104974.110": "11.280%",
 "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00, Reward: 5083.390": "0.550%”
}

2. spam exec sendgscc

3. cli exec analyze 127852 oncoapop1

Code: [Select]
{
 "Command": "analyze",
 "Totals": "CAMEROON-ONE|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|2667|0.00546183|oncoapop1|2668\nPOG|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|0|0.00000000|oncoapop1|664505\n",
 "0": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127747.00, TXID: 48e194fa86c3c3765b8e99d21a7817265ad2178174c3af2fd2ec4481953f0240, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 436515.4894, Donation: 0.0000, UserTotal: 2666.67",
 "1": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127829.00, TXID: 60e6383ad2a46c1562b22bc8f363ad48c51be907b20f1ce8b6b3a5329b0285d8, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 472618.7650, Donation: 0.0000, UserTotal: 5333.33",
 "2": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127831.00, TXID: 09bdcb818fb26f7889730feb9af7a3be49f119cb822f885525d9cdecc76ec13d, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 1170573.1598, Donation: 0.0000, UserTotal: 8000.00",
 "3": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127831.00, TXID: e643dcf61c8666ec77f481f32041e98bec0f0357005599f1dffddfe7c089661d, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 244234.6203, Donation: 0.0000, UserTotal: 10666.67",
 "4": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127831.00, TXID: ba5dbc1954e23ca44c821317515c55d895dbe117a97f19fa8260ac276bed23d1, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 16135.2207, Donation: 0.0000, UserTotal: 13333.33",
 "5": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127831.00, TXID: 60b7a3124d9d75aa2024a67ce4a29bcecd2d7e8adb55014227c88acb89c5b7fa, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 495451.5158, Donation: 0.0000, UserTotal: 16000.00",
 "6": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127832.00, TXID: 9884b452e0d6cabd512b82ba0a01d6aeebd434d5ee5be4d5bed9577d7ff6e5e3, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 815893.8629, Donation: 0.0000, UserTotal: 18666.67",
 "7": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127832.00, TXID: 4ea1df741b02ec30a16cf8fdce9b4c8ade28d7b4558b9289b0864014092b5c58, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 637133.8471, Donation: 0.0000, UserTotal: 21333.33",
 "8": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127835.00, TXID: 1aa871659405b4a96e3d747d2da820b974d5e9d59d474ca787b67d5a259797ac, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 1163778.4370, Donation: 0.0000, UserTotal: 24000.00"
}

4. now after spamming, I check leaderboard

Code: [Select]
{
 "Prominence": "Details",
 "CAMEROON-ONE: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 1333.00": "0.27%",
 "CAMEROON-ONE: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.55%",
 "POG: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 3022707.00": "53.72%",
 "POG: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 634626.00": "11.28%",
 "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 0.00": "0.00%",
 "Healing": "Diary Entries",
 "Prominence": "Totals",
 "ALL: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 3024040.00, Reward: 502530.690": "53.990%",
 "ALL: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 634626.00, Reward: 104974.110": "11.280%",
 "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 24000.00, Reward: 5083.390": "0.550%”
}

5. great - i accumulate points but the rewards are capped as intended to 5083.90 BBP

6. Now I POG

Code: [Select]
"41": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127843.00, TXID: ff01da633701ff62bd850a5958969c51170a0921bbc72656b1c40c1966f08e5e, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 102796.3848, Donation: 0.0000, UserTotal: 112000.00",
 "42": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127856.00, TXID: e92787cdc0a272fa2fb0a6583aba692a90c85f9b1d8de5efb846dbeeac3ef110, NickName: oncoapop1, Points: 6944111.09, Campaign: POG, CoinAge: 322317.0851, Donation: 10000.0000, UserTotal: 7056111.09",
 "43": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127856.00, TXID: ec831148c8372acf8dbd9ff85b85ab4071537fd157d37b546f7bf40e714d1047, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 82046.5779, Donation: 0.0000, UserTotal: 7058777.76”,

7. POG calculation

CoinAge x (tithe)^1/3
322,317 x (10,000)^1/3 = 322,317 x 21.5443469003 = 6,944,108
6,944,108 /  7,608,615 (ie total POG points, add POG from leaderboard) = 91.2% of POG reward ( 617671.74 BBP) = 563,726.68 BBP
plus CAMEROON ONE 5083.90

Total 568,810.58 BBP

Code: [Select]
{
 "Prominence": "Details",
 "CAMEROON-ONE: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.55%",
 "POG: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 615907.00": "5.30%",
 "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 6944111.00": "59.70%",
 "Healing": "Diary Entries",
 "Prominence": "Totals",
 "ALL: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 615907.00, Reward: 49285.700": "5.300%",
 "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 7058778.00, Reward: 560760.880": "60.250%"
}

8. Well = 568,810 BBP (calculated as in (7), based on my understanding) vs 560,760 BBP (reported by leadboard)- that 8,050 BBP difference is more than my Cameroon reward!

Issues
A. points in exec analyze are incorrect for Cameroon one as it is not supposed to accumulate, it is correct on leaderboard for Cameroon-one but NOT total (see 2, this is may be confusing)
B. points in leaderboard Totals are not accurate since it sums incorrectly accumulating Cameroon-One points and hence no value above the cap.
C. There appears to be a discordance in manually calculated vs leaderboard reported rewards which may be significant, if my understanding is correct.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 04, 2019, 08:58:00 pm
Fiat calculations

1. $1.33 per child per day = $2.66 for two children
2. BBP = 2.66 / 0.000502405947 = 5,294 BBP (we used 5083.90 in last calculation but it is close enough)
3. Sorry I do not understand what the dailysponsorshipcap is and how to apply it in this case.

Values used to calculate the points received:

Code: [Select]
exec dailysponsorshipcap
{
 "Command": "dailysponsorshipcap",
 "cap": 0.00273612097317169
}
exec price
{
 "Command": "price",
 "consensus_price": 0,
 "qt_phase": 0,
 "qt_prior_phase": 0,
 "qt_future_phase": 0,
 "qt_enabled": true,
 "cur_price": "0.000502405947",
 "BBP/BTC": "0.000000045000",
 "BTC/USD": 11164.5766
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 04, 2019, 09:37:01 pm
Fiat calculations

1. $1.33 per child per day = $2.66 for two children
2. BBP = 2.66 / 0.000502405947 = 5,294 BBP (we used 5083.90 in last calculation but it is close enough)
3. Sorry I do not understand what the dailysponsorshipcap is and how to apply it in this case.

Values used to calculate the points received:

Code: [Select]
exec dailysponsorshipcap
{
 "Command": "dailysponsorshipcap",
 "cap": 0.00273612097317169
}
exec price
{
 "Command": "price",
 "consensus_price": 0,
 "qt_phase": 0,
 "qt_prior_phase": 0,
 "qt_future_phase": 0,
 "qt_enabled": true,
 "cur_price": "0.000502405947",
 "BBP/BTC": "0.000000045000",
 "BTC/USD": 11164.5766
}

Excellent summary above;  luckily, we are in agreement in all points, so the code I checked in for the next version addresses exactly those things.  Ill comment deeper on it.

As far as fiat,  so the wallet converts the $1.33 into a corresponding maximum Prominence % level, in reference to the entire total contract for the day.  So, since our GSC contract is about 950K per day, it converts $1.33 to a prominence cap level in percentage terms, so that you can take the daily sponsorship cap %, and multiply it * the daily superblock value like this:

950,000 (daily superblock GSC contract value ) * .00273 (sponsorship cap) = 2593 bbp.
This is the amount the wallet will reward for one child (about $1.33 per day).

So yes you got that one and it seems to be working correctly.  We should see about 5200 bbp for 2 children at this price level and contract level.  Of course QT and deflation in the future will lower this figure, but we will know as it happens, as our getgovernanceinfo will show the next daily budget etc.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 04, 2019, 09:42:44 pm
1. Tithe normally via Cameroon-One

Code: [Select]
{
 "Prominence": "Details",
 "CAMEROON-ONE: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 1333.00": "0.27%",
 "CAMEROON-ONE: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.55%",
 "POG: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 3022707.00": "53.72%",
 "POG: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 634626.00": "11.28%",
 "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 0.00": "0.00%",
 "Healing": "Diary Entries",
 "Prominence": "Totals",
 "ALL: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 3024040.00, Reward: 502530.690": "53.990%",
 "ALL: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 634626.00, Reward: 104974.110": "11.280%",
 "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00, Reward: 5083.390": "0.550%”
}

2. spam exec sendgscc

3. cli exec analyze 127852 oncoapop1

Code: [Select]
{
 "Command": "analyze",
 "Totals": "CAMEROON-ONE|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|2667|0.00546183|oncoapop1|2668\nPOG|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|0|0.00000000|oncoapop1|664505\n",
 "0": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127747.00, TXID: 48e194fa86c3c3765b8e99d21a7817265ad2178174c3af2fd2ec4481953f0240, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 436515.4894, Donation: 0.0000, UserTotal: 2666.67",
 "1": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127829.00, TXID: 60e6383ad2a46c1562b22bc8f363ad48c51be907b20f1ce8b6b3a5329b0285d8, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 472618.7650, Donation: 0.0000, UserTotal: 5333.33",
 "2": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127831.00, TXID: 09bdcb818fb26f7889730feb9af7a3be49f119cb822f885525d9cdecc76ec13d, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 1170573.1598, Donation: 0.0000, UserTotal: 8000.00",
 "3": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127831.00, TXID: e643dcf61c8666ec77f481f32041e98bec0f0357005599f1dffddfe7c089661d, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 244234.6203, Donation: 0.0000, UserTotal: 10666.67",
 "4": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127831.00, TXID: ba5dbc1954e23ca44c821317515c55d895dbe117a97f19fa8260ac276bed23d1, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 16135.2207, Donation: 0.0000, UserTotal: 13333.33",
 "5": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127831.00, TXID: 60b7a3124d9d75aa2024a67ce4a29bcecd2d7e8adb55014227c88acb89c5b7fa, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 495451.5158, Donation: 0.0000, UserTotal: 16000.00",
 "6": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127832.00, TXID: 9884b452e0d6cabd512b82ba0a01d6aeebd434d5ee5be4d5bed9577d7ff6e5e3, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 815893.8629, Donation: 0.0000, UserTotal: 18666.67",
 "7": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127832.00, TXID: 4ea1df741b02ec30a16cf8fdce9b4c8ade28d7b4558b9289b0864014092b5c58, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 637133.8471, Donation: 0.0000, UserTotal: 21333.33",
 "8": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127835.00, TXID: 1aa871659405b4a96e3d747d2da820b974d5e9d59d474ca787b67d5a259797ac, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 1163778.4370, Donation: 0.0000, UserTotal: 24000.00"
}

4. now after spamming, I check leaderboard

Code: [Select]
{
 "Prominence": "Details",
 "CAMEROON-ONE: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 1333.00": "0.27%",
 "CAMEROON-ONE: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.55%",
 "POG: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 3022707.00": "53.72%",
 "POG: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 634626.00": "11.28%",
 "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 0.00": "0.00%",
 "Healing": "Diary Entries",
 "Prominence": "Totals",
 "ALL: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 3024040.00, Reward: 502530.690": "53.990%",
 "ALL: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 634626.00, Reward: 104974.110": "11.280%",
 "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 24000.00, Reward: 5083.390": "0.550%”
}

5. great - i accumulate points but the rewards are capped as intended to 5083.90 BBP

6. Now I POG

Code: [Select]
"41": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127843.00, TXID: ff01da633701ff62bd850a5958969c51170a0921bbc72656b1c40c1966f08e5e, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 102796.3848, Donation: 0.0000, UserTotal: 112000.00",
 "42": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127856.00, TXID: e92787cdc0a272fa2fb0a6583aba692a90c85f9b1d8de5efb846dbeeac3ef110, NickName: oncoapop1, Points: 6944111.09, Campaign: POG, CoinAge: 322317.0851, Donation: 10000.0000, UserTotal: 7056111.09",
 "43": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127856.00, TXID: ec831148c8372acf8dbd9ff85b85ab4071537fd157d37b546f7bf40e714d1047, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 82046.5779, Donation: 0.0000, UserTotal: 7058777.76”,

7. POG calculation

CoinAge x (tithe)^1/3
322,317 x (10,000)^1/3 = 322,317 x 21.5443469003 = 6,944,108
6,944,108 /  7,608,615 (ie total POG points, add POG from leaderboard) = 91.2% of POG reward ( 617671.74 BBP) = 563,726.68 BBP
plus CAMEROON ONE 5083.90

Total 568,810.58 BBP

Code: [Select]
{
 "Prominence": "Details",
 "CAMEROON-ONE: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.55%",
 "POG: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 615907.00": "5.30%",
 "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 6944111.00": "59.70%",
 "Healing": "Diary Entries",
 "Prominence": "Totals",
 "ALL: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 615907.00, Reward: 49285.700": "5.300%",
 "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 7058778.00, Reward: 560760.880": "60.250%"
}

8. Well = 568,810 BBP (calculated as in (7), based on my understanding) vs 560,760 BBP (reported by leadboard)- that 8,050 BBP difference is more than my Cameroon reward!

Issues
A. points in exec analyze are incorrect for Cameroon one as it is not supposed to accumulate, it is correct on leaderboard for Cameroon-one but NOT total (see 2, this is may be confusing)
B. points in leaderboard Totals are not accurate since it sums incorrectly accumulating Cameroon-One points and hence no value above the cap.
C. There appears to be a discordance in manually calculated vs leaderboard reported rewards which may be significant, if my understanding is correct.


Issues
A. points in exec analyze are incorrect for Cameroon one as it is not supposed to accumulate, it is correct on leaderboard for Cameroon-one but NOT total (see 2, this is may be confusing)
->  Great, correct, this was a bug, the Cameroon points were accumulating.  Fixed in next version.



B. points in leaderboard Totals are not accurate since it sums incorrectly accumulating Cameroon-One points and hence no value above the cap.
->  Correct, Bug.  Fixed in next version.

C. There appears to be a discordance in manually calculated vs leaderboard reported rewards which may be significant, if my understanding is correct.
->  As long as the discord affects Cameroon One only, as what I observed in unit test earlier was POG was still correct - but Cameroon was accumulating.  So lets test again tomorrow and spam it again, and see if we got it.




The next version also addresses POSE bans (for penalizing offline sancs).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 04, 2019, 10:03:56 pm
BiblePay
1.4.5.7 - Mandatory Upgrade for TestNet

- Fix bug in Cameroon-One reward (restrict reward to one payment per day)
- Add Sanctuary POSE ban punishment on Sancs who are offline (see masternodelist : posescore column for POSE ban level; when service level drops below .50, node moves to POSE_BAN state and stops receiving payments)
- Add BBPSocket class (this is for a non-blocking TCP connection with timeout for future use)
- Added notes to getchaintips function explaining our unique situation on DIP1 & CSV bits states
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 05, 2019, 02:08:20 pm
BiblePay
1.4.5.7 - Mandatory Upgrade for TestNet

- Fix bug in Cameroon-One reward (restrict reward to one payment per day)
- Add Sanctuary POSE ban punishment on Sancs who are offline (see masternodelist : posescore column for POSE ban level; when service level drops below .50, node moves to POSE_BAN state and stops receiving payments)
- Add BBPSocket class (this is for a non-blocking TCP connection with timeout for future use)
- Added notes to getchaintips function explaining our unique situation on DIP1 & CSV bits states

The binaries appear not to have been complied yet? What is the proper command to pull from the develop branch on github? The usual command errors out.

Sorry but I’m not a coder and not familiar with these basic commands....
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 05, 2019, 02:30:42 pm
The binaries appear not to have been complied yet? What is the proper command to pull from the develop branch on github? The usual command errors out.

Sorry but I’m not a coder and not familiar with these basic commands....

I released Windows last night, but MIP is in the mountains and he releases linux, but I have received word the binaries are now deployed.

Regarding manual pull, try this:
cd ~/biblepay-evolution-develop (or where your develop branch is)
cd src
git pull origin develop
make

(This assumes you built it once before from source).

If not you have to do this whole thing first including building depends:
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

Then just pull the develop branch (with the above git commands) and recompile develop.

(I keep develop in a separate directory so I can have both in separate states).


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 05, 2019, 09:36:18 pm
Thank you, both.

Wallets currently syncing....
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 08, 2019, 12:20:58 pm
Thank you, both.

Wallets currently syncing....


I have an update on the POSE issue (this is the unreachable sanc being paid issue).

So I have fully researched this.  In our prod environment (non-deterministic sancs, running in the .13 branch), the POSE (proof of service) is achieved by having sanctuaries send MNPINGs around the network.  This is similar to the bitcoin PING packet, meaning that our network knows when a sanctuary fails to reply to MNPINGS, they start falling behind in the payment queue and start getting POSE banned.  I know in prod, if I stop a sanc for over a couple hours, my sanc will move to NEW_START_REQUIRED (I just had to restart two in that state today).

However, you rightly point out that in the .14 branch, our sancs just keep getting paid.  So the reason for this is Dash is retiring all non-deterministic-messages to simplify the codebase.  We are running in a state where we are expected to turn on LLMQ soon.

In .14, when LLMQ is off, sancs constantly get rewarded.  When LLMQ is enabled, each sanc is required to participate in a quorum within a certain amount of time (IE about 1-24 hours depending on the size of the quorum).

So the answer to this concern is for now lets overlook it until we enable LLMQ.  Then let us regroup and test this POSE ban functionality to ensure your non reachable sancs do get POSE banned.

Moving on to Cameroon One, Im still very excited about this feature.  Lets see if this latest version fixed the payment issue?



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 08, 2019, 12:23:37 pm
So I just sent a few gsccs.

Clicking on GUI leaderboard, clicking on DETAILS, check out randrews3.  I have two cameroon one orphans.  I am being paid 5550.46 (two children of 1334 points each).  So far this version looks good.  (Even though I sent out 10 gsccs).  My pog is 607,553.  Ill do exec analyze.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 12, 2019, 05:17:11 pm
I am ready to do some tests but I don't know if I'm doing something wrong

Code: [Select]
00:16:32

exec sendgscc


00:16:32

{
  "Command": "sendgscc",
  "Error!": "CreateGSCTransmission::Fail::(Create Transaction) Insufficient funds.CreateGSCTransmission::Fail::(Create Transaction) Insufficient funds."
}

I have like 27M so plenty of funds.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 12, 2019, 05:20:04 pm
I am ready to do some tests but I don't know if I'm doing something wrong

Code: [Select]
00:16:32

exec sendgscc


00:16:32

{
  "Command": "sendgscc",
  "Error!": "CreateGSCTransmission::Fail::(Create Transaction) Insufficient funds.CreateGSCTransmission::Fail::(Create Transaction) Insufficient funds."
}

I have like 27M so plenty of funds.

Please check your coin control, and see if select all results in a tx size > 100K.  If so, unselect all, then select some repeatedly - and send them to yourself.
Repear until your total stash < 100K in size.

Then wait 6 confirms then do exec sendgscc.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 12, 2019, 10:52:53 pm
Please check your coin control, and see if select all results in a tx size > 100K.  If so, unselect all, then select some repeatedly - and send them to yourself.
Repear until your total stash < 100K in size.

Then wait 6 confirms then do exec sendgscc.

I see we made this automatic in our prod branch, and somehow, this got borked in testnet; I will have a commit within 24 hours to fix this issue.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 13, 2019, 11:13:16 am
BiblePay
1.4.5.8-Leisure Upgrade

- Merge in 1.4.4.1 prod changes -> develop
- Fix ABN create error (insufficient funds)
- Fix BiblePay Miner ABN crash-windows 64 crash issue
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 13, 2019, 06:17:47 pm
I'm back here with latest testnet in MacOS.

I see this


Code: [Select]
01:10:30

listchildren


01:10:31

{
  "List Of": "Cameroon-One Children",
  "Child ID": "abaad3ec",
  "CPK": "yWK9ckFhU1ihDSDLAZggNFTwypg6Bi3C23",
  "Biography": "https://cameroonone.org/biblepay/abaad3ec.htm",
  "Balance": -999,
  "Notes": "This child is not provisioned yet.",
  "Nickname": "MIP"
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 13, 2019, 08:16:02 pm
I'm back here with latest testnet in MacOS.

I see this


Code: [Select]
01:10:30

listchildren


01:10:31

{
  "List Of": "Cameroon-One Children",
  "Child ID": "abaad3ec",
  "CPK": "yWK9ckFhU1ihDSDLAZggNFTwypg6Bi3C23",
  "Biography": "https://cameroonone.org/biblepay/abaad3ec.htm",
  "Balance": -999,
  "Notes": "This child is not provisioned yet.",
  "Nickname": "MIP"
}

OK, and as you know, in Testnet I am running the mock API to apply debits and credits to the childs balances, but in Prod, CameroonOne will be running the API (from their own domain).

So I posted a $50.00 payment for child abaad3ec. 

Go ahead and do a listchildren now and see if you have a -10$ balance (this is because you have a debit of $40 for July orphanage charges minus a $50 payment).

Then do an execgscc and wait 6 blocks and see if the child payment is showing in your leaderboard "details".

Do you understand the 'exec dailysponsorshipcap'?  This shows the max amount we pay per child per day in the GSC contract (we use the daily BBP price quote - found in exec price - and of course the daily GSC paymentlimit - to calculate the quorums dailysponsorshipcap).

Oncoapp has 3 children, you have 1 and I have 2.  So Ill do an exec sendgscc, and we should see 6 children over 3 participants in the leaderboard we can reverse engineer. (Click Details).

OK, I sent an exec gscc, I see Oncoapp & I in there, now we need you.  Btw, the reason you are not in cameroon one as of yet today is because your child was not provisions (nor had a credit balance - until Cameroon receives the check or the paypal making your balance a credit balance!).


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 14, 2019, 04:14:27 pm

Code: [Select]
23:05:00

listchildren


23:05:01

{
  "List Of": "Cameroon-One Children",
  "Child ID": "abaad3ec",
  "CPK": "yWK9ckFhU1ihDSDLAZggNFTwypg6Bi3C23",
  "Biography": "https://cameroonone.org/biblepay/abaad3ec.htm",
  "Balance": -10,
  "Nickname": "MIP",
  "Child ID": "0f83ef0c",
  "CPK": "yWK9ckFhU1ihDSDLAZggNFTwypg6Bi3C23",
  "Biography": "https://cameroonone.org/biblepay/0f83ef0c.htm",
  "Balance": -999,
  "Notes": "This child is not provisioned yet.",
  "Nickname": "MIP"
}

Executed the sendgscc
And I see myself in the leaderboard
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 15, 2019, 12:43:33 pm
Code: [Select]
23:05:00

listchildren


23:05:01

{
  "List Of": "Cameroon-One Children",
  "Child ID": "abaad3ec",
  "CPK": "yWK9ckFhU1ihDSDLAZggNFTwypg6Bi3C23",
  "Biography": "https://cameroonone.org/biblepay/abaad3ec.htm",
  "Balance": -10,
  "Nickname": "MIP",
  "Child ID": "0f83ef0c",
  "CPK": "yWK9ckFhU1ihDSDLAZggNFTwypg6Bi3C23",
  "Biography": "https://cameroonone.org/biblepay/0f83ef0c.htm",
  "Balance": -999,
  "Notes": "This child is not provisioned yet.",
  "Nickname": "MIP"
}

Executed the sendgscc
And I see myself in the leaderboard

Are you happy with the amount you are receiving per day (for Cameroon), and non Cameroon POG rewards?

Next, we need to test non abn and abn and pool and non-pool mining (I think it would be prudent to test all the combinations).

Can we please sync to prod in .14, and have a few of us test against the pool in PROD (as testnet doesn't have a pool setup currently).

We have develop version 1.4.5.9 coming out now; lets build this version first, release it, then continue testing the mining.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 15, 2019, 05:47:41 pm
BiblePay
1.4.5.9 - Leisure Upgrade

- Commit 1441-1442 prod changes to Develop
- Miner now has all the abn/turnkey features prod does - please test mining against Prod

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 17, 2019, 01:11:05 pm
Are you happy with the amount you are receiving per day (for Cameroon), and non Cameroon POG rewards?

I see these ones, they look correct:

Code: [Select]
Status: 5770 confirmations
Date: 15/07/2019 00:16
Source: Smart-Contract-Payment
Credit: 229 665.00000000 tBBP
Net amount: +229 665.00000000 tBBP
Transaction ID: 7f22891454dec468ce5418ef1461680027a870d47f435f635759eef0162c0bf5
Output index: 4
Transaction total size: 435 bytes

Status: 5566 confirmations
Date: 17/07/2019 19:56
Source: Smart-Contract-Payment
Credit: 155 567.00000000 tBBP
Net amount: +155 567.00000000 tBBP
Transaction ID: 29bc6f382acf46205ddebb8fd14426c081e75b0e2bc0824dff8b6643f6a3f186
Output index: 3
Transaction total size: 435 bytes

Status: 5158 confirmations
Date: 17/07/2019 19:56
Source: Smart-Contract-Payment
Credit: 3583.25212411 tBBP
Net amount: +3583.25212411 tBBP
Transaction ID: 1eb5c212896475c11c400fb7952f310a72ac057702c632987f380fe2236bdf51
Output index: 1
Transaction total size: 400 bytes

Status: 3723 confirmations
Date: 17/07/2019 19:57
Source: Smart-Contract-Payment
Credit: 3584.49712411 tBBP
Net amount: +3584.49712411 tBBP
Transaction ID: 8bcf427f6affcc6fe183481dd74bbd3f8bdc161fec0ff221d98f2b5ac1d41745
Output index: 1
Transaction total size: 400 bytes

Status: 3724 confirmations
Date: 17/07/2019 19:57
Source: Smart-Contract-Payment
Credit: 3584.49712411 tBBP
Net amount: +3584.49712411 tBBP
Transaction ID: 8bcf427f6affcc6fe183481dd74bbd3f8bdc161fec0ff221d98f2b5ac1d41745
Output index: 1
Transaction total size: 400 bytes

I will now try mining against prod
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 17, 2019, 01:38:48 pm
mining in prod... I see weird stuff in abninfo and poolinfo5:

Code: [Select]
20:37:10

getmininginfo


20:37:10

{
  "blocks": 132344,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 5764.798569706667,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 1,
  "networkhashps": 554920.0413722472,
  "hashps": 0,
  "minerstarttime": "07-17-2019 18:19:34",
  "hashcounter": 0,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
[b]  "abninfo": "No block to mine... Please wait... 1563388615; ",
  "poolinfo5": "Internal ABN: Invalid 1563388480; ",
[/b]  "gsc_errors": "low abn weight 0",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 125000
}

While 1.4.4.3 says "Unable to create ABN..."
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 17, 2019, 01:54:11 pm
mining in prod... I see weird stuff in abninfo and poolinfo5:

Code: [Select]
20:37:10

getmininginfo


20:37:10

{
  "blocks": 132344,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 5764.798569706667,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 1,
  "networkhashps": 554920.0413722472,
  "hashps": 0,
  "minerstarttime": "07-17-2019 18:19:34",
  "hashcounter": 0,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
[b]  "abninfo": "No block to mine... Please wait... 1563388615; ",
  "poolinfo5": "Internal ABN: Invalid 1563388480; ",
[/b]  "gsc_errors": "low abn weight 0",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 125000
}

While 1.4.4.3 says "Unable to create ABN..."

So if you send a big GSC out, sometimes you have to wait 5 confirms to get your ABN weight back.
Could you please paste your exec getabnweight 125000?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 17, 2019, 03:23:59 pm
BiblePay
1.4.5.9 - Leisure Upgrade

- Commit 1441-1442 prod changes to Develop
- Miner now has all the abn/turnkey features prod does - please test mining against Prod

Getmininginfo dev 1.4.5.9 on mainnet

Code: [Select]
{
 "blocks": 132361,
 "currentblocksize": 1000,
 "currentblocktx": 0,
 "difficulty": 10360.99487125054,
 "errors": "",
 "pooledtx": 0,
 "chain": "main",
 "genproclimit": 1,
 "networkhashps": 619612.9706705563,
 "hashps": 7892.611994219653,
 "minerstarttime": "07-17-2019 20:13:41",
 "hashcounter": 2097288,
 "pooledtx": 0,
 "chain": "main",
 "biblepay-generate": true,
 "poolinfo1": "Pool mining with sam2_funded; ",
 "poolinfo2": "Submitting Solution 07-17-2019 20:17:23; ",
 "poolinfo3": "",
 "abninfo": "Mining with funded Valid ABN 36ad1fbdb62e2c7775e3000c29f4f87d59a4aa660277bef2271cdf94e96e4137; ",
 "poolinfo5": "Internal ABN: Invalid 1563394642; ",
 "gsc_errors": "",
 "poolmining": true,
 "pool_url": "https://pool.biblepay.org",
 "required_abn_weight": 125000
}
cli -version
BiblePay Core RPC client version 1.4.5.9


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 17, 2019, 04:02:01 pm
So if you send a big GSC out, sometimes you have to wait 5 confirms to get your ABN weight back.
Could you please paste your exec getabnweight 125000?

Code: [Select]

22:56:00

exec getabnweight 125000


22:56:00

{
  "Command": "getabnweight",
  "version": 2.6,
  "weight": 1253818517.638646,
  "total_required": 28852642,
  "weight 125000.00": 132255.1786689815,
  "total_required 125000.00": 67455
}


I'm using my "normal" mainnet mining wallet but this is different to what I see using 1.4.4.3

Code: [Select]
22:56:24

exec getabnweight 125000


22:56:24

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 23305003.67273147,
  "total_required": 1861636,
  "weight 125000.00": 146982.5912037037,
  "total_required 125000.00": 23121
}
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 17, 2019, 04:16:17 pm
Code: [Select]

22:56:00

exec getabnweight 125000


22:56:00

{
  "Command": "getabnweight",
  "version": 2.6,
  "weight": 1253818517.638646,
  "total_required": 28852642,
  "weight 125000.00": 132255.1786689815,
  "total_required 125000.00": 67455
}


I'm using my "normal" mainnet mining wallet but this is different to what I see using 1.4.4.3

Code: [Select]
22:56:24

exec getabnweight 125000


22:56:24

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 23305003.67273147,
  "total_required": 1861636,
  "weight 125000.00": 146982.5912037037,
  "total_required 125000.00": 23121
}

v1.2 didnt have the 500 tx limit, but 2.6 does; 2.6 sorts by coin-age.

Lets see if these two things shed light on it:

exec getabnweight 125000 1

And

exec createabn 125000


See if they use the coins as expected.  If no error occurs in exec createabn, you should be able to abn mine.


If you really want to see if 2.6 is accurate, try this:

exec createabn 10000000
See if it makes an ABN with a weight of 10 million?

(audited_weight: 10mm)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 17, 2019, 07:25:10 pm
Getmininginfo dev 1.4.5.9 on mainnet

Code: [Select]
{
 "blocks": 132361,
 "currentblocksize": 1000,
 "currentblocktx": 0,
 "difficulty": 10360.99487125054,
 "errors": "",
 "pooledtx": 0,
 "chain": "main",
 "genproclimit": 1,
 "networkhashps": 619612.9706705563,
 "hashps": 7892.611994219653,
 "minerstarttime": "07-17-2019 20:13:41",
 "hashcounter": 2097288,
 "pooledtx": 0,
 "chain": "main",
 "biblepay-generate": true,
 "poolinfo1": "Pool mining with sam2_funded; ",
 "poolinfo2": "Submitting Solution 07-17-2019 20:17:23; ",
 "poolinfo3": "",
 "abninfo": "Mining with funded Valid ABN 36ad1fbdb62e2c7775e3000c29f4f87d59a4aa660277bef2271cdf94e96e4137; ",
 "poolinfo5": "Internal ABN: Invalid 1563394642; ",
 "gsc_errors": "",
 "poolmining": true,
 "pool_url": "https://pool.biblepay.org",
 "required_abn_weight": 125000
}
cli -version
BiblePay Core RPC client version 1.4.5.9
as pleiades2 on pool.biblepay.org with own abnweight

cli -version
BiblePay Core RPC client version 1.4.5.9

Code: [Select]
{
 "blocks": 132394,
 "currentblocksize": 1675,
 "currentblocktx": 1,
 "difficulty": 2117.634585042601,
 "errors": "",
 "pooledtx": 0,
 "chain": "main",
 "genproclimit": 240,
 "networkhashps": 645828.9771104221,
 "hashps": 26917.51935300097,
 "minerstarttime": "07-18-2019 00:04:48",
 "hashcounter": 19277466,
 "pooledtx": 0,
 "chain": "main",
 "biblepay-generate": true,
 "poolinfo1": "",
 "poolinfo2": "",
 "poolinfo3": "",
 "abninfo": "ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN:  OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ",
 "poolinfo5": "",
 "gsc_errors": "",
 "poolmining": true,
 "pool_url": "https://pool.biblepay.org",
 "required_abn_weight": 125000
}

cli exec getabnweight
{
 "Command": "getabnweight",
 "version": 2.6,
 "weight": 240718.600324074,
 "total_required": 1212742
}

cli exec createabn 125000

{
 "Command": "createabn",
 "xml": "<MT>ABN</MT><abnmsg><nonce>801c96dc35b4b9921a9369190810b604a9666f6e839c2a981b2fdb28d515fcc4</nonce><ppk>ppk</ppk></abnmsg><abnsig>IJCU2Sb5KlNsigrnJhP+W/JMt/mTx0KN65JV2zm4e8fDbQX1n3CznlyiL4dKI/MA2b9YjjRS/9W57RTRnr/ALAw=</abnsig><abncpk>BLpAqYhjuxJAfTC9yJBUxzUyNfDFfiduip</abncpk><abnwgt>125000</abnwgt>",
 "err": "",
 "coin_age_data_selected": "2341.7357(0.63)=[1468.27] depth=136,  <ROW>1210401.1106(0.20)=[239250.33] depth=42,  <ROW><TOTALREQ>1212742.85</TOTALREQ><TOTALAGE>240719</TOTALAGE>",
 "success": "d148d565157bb7fecee7e3f14698f0431114293d2de7c489de6295cf30d128ef",
 "coin_age_data_pre_select": "2341.7357(0.63)=[1468.27] depth=136,  <ROW>1210401.1106(0.20)=[239250.33] depth=42,  <ROW><TOTALREQ>1212742.85</TOTALREQ><TOTALAGE>240719</TOTALAGE>",
 "audited_weight": 241855.5179565373,
 "vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 1470.47, Age: 0.63, Amount: 2341.00, TxTime: 1563354656...Output #1, Weight: 240385.05, Age: 0.20, Amount: 1210401.00, TxTime: 1563391768..."
}


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 17, 2019, 07:54:22 pm
as pleiades2 on pool.biblepay.org with own abnweight

cli -version
BiblePay Core RPC client version 1.4.5.9

Code: [Select]
{
 "blocks": 132394,
 "currentblocksize": 1675,
 "currentblocktx": 1,
 "difficulty": 2117.634585042601,
 "errors": "",
 "pooledtx": 0,
 "chain": "main",
 "genproclimit": 240,
 "networkhashps": 645828.9771104221,
 "hashps": 26917.51935300097,
 "minerstarttime": "07-18-2019 00:04:48",
 "hashcounter": 19277466,
 "pooledtx": 0,
 "chain": "main",
 "biblepay-generate": true,
 "poolinfo1": "",
 "poolinfo2": "",
 "poolinfo3": "",
 "abninfo": "ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN:  OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ",
 "poolinfo5": "",
 "gsc_errors": "",
 "poolmining": true,
 "pool_url": "https://pool.biblepay.org",
 "required_abn_weight": 125000
}

cli exec getabnweight
{
 "Command": "getabnweight",
 "version": 2.6,
 "weight": 240718.600324074,
 "total_required": 1212742
}

cli exec createabn 125000

{
 "Command": "createabn",
 "xml": "<MT>ABN</MT><abnmsg><nonce>801c96dc35b4b9921a9369190810b604a9666f6e839c2a981b2fdb28d515fcc4</nonce><ppk>ppk</ppk></abnmsg><abnsig>IJCU2Sb5KlNsigrnJhP+W/JMt/mTx0KN65JV2zm4e8fDbQX1n3CznlyiL4dKI/MA2b9YjjRS/9W57RTRnr/ALAw=</abnsig><abncpk>BLpAqYhjuxJAfTC9yJBUxzUyNfDFfiduip</abncpk><abnwgt>125000</abnwgt>",
 "err": "",
 "coin_age_data_selected": "2341.7357(0.63)=[1468.27] depth=136,  <ROW>1210401.1106(0.20)=[239250.33] depth=42,  <ROW><TOTALREQ>1212742.85</TOTALREQ><TOTALAGE>240719</TOTALAGE>",
 "success": "d148d565157bb7fecee7e3f14698f0431114293d2de7c489de6295cf30d128ef",
 "coin_age_data_pre_select": "2341.7357(0.63)=[1468.27] depth=136,  <ROW>1210401.1106(0.20)=[239250.33] depth=42,  <ROW><TOTALREQ>1212742.85</TOTALREQ><TOTALAGE>240719</TOTALAGE>",
 "audited_weight": 241855.5179565373,
 "vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 1470.47, Age: 0.63, Amount: 2341.00, TxTime: 1563354656...Output #1, Weight: 240385.05, Age: 0.20, Amount: 1210401.00, TxTime: 1563391768..."
}


Thats great to know we didnt break compatibility in prod.
It tests pool mining, ABNs, Funded ABNs, syncing to the top, etc.

Thanks!

MIP can you please confirm you had insufficient funds the first try because you had recently sent a GSC in prod, or something?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 18, 2019, 01:42:14 am
v1.2 didnt have the 500 tx limit, but 2.6 does; 2.6 sorts by coin-age.

Lets see if these two things shed light on it:

exec getabnweight 125000 1

And

exec createabn 125000


See if they use the coins as expected.  If no error occurs in exec createabn, you should be able to abn mine.


If you really want to see if 2.6 is accurate, try this:

exec createabn 10000000
See if it makes an ABN with a weight of 10 million?

(audited_weight: 10mm)

Code: [Select]
08:34:12

exec getabnweight 125000 1


08:34:12

{
  "Command": "getabnweight",
  "version": 2.6,
  "weight": 1265474159.938079,
  "total_required": 28859592,
  "coin_age_data_pre_select": "1.0000(13.86)=[13.86] depth=2931,  <ROW>1.0000(13.86)=[13.86] depth=2931,  <ROW>1.0000(14.38)=[14.38] depth=3042,  <ROW>12.4022(14.38)=[172.58] depth=3042,  <ROW>50.0000(15.94)=[796.95] depth=3367,  <ROW>2301.8849(0.51)=[1178.22] depth=111,  <ROW>2342.2185(0.53)=[1229.74] depth=114,  <ROW>2305.9676(0.73)=[1683.32] depth=159,  <ROW>2341.7357(0.88)=[2055.09] depth=191,  <ROW>2314.7290(1.07)=[2472.63] depth=231,  <ROW>127.1195(21.61)=[2743.90] depth=4532,  <ROW>1387.3182(2.15)=[2977.43] depth=459,  <ROW>2385.4458(1.28)=[3052.97] depth=276,  <ROW>2364.4107(1.32)=[3114.93] depth=287,  <ROW>2391.2520(1.41)=[3374.94] depth=305,  <ROW>2392.9768(1.54)=[3677.12] depth=330,  <ROW>2224.1720(1.77)=[3937.28] depth=381,  <ROW>2374.1741(1.77)=[4202.83] depth=381,  <ROW>2391.4955(1.89)=[4507.67] depth=405,  <ROW>2290.6961(1.97)=[4510.56] depth=422,  <ROW>2415.3781(1.88)=[4549.62] depth=404,  <ROW>2933.1573(1.61)=[4712.42] depth=344,  <ROW>2743.5920(1.85)=[5086.68] depth=397,  <ROW>2385.0204(2.15)=[5119.80] depth=459,  <ROW>2416.9292(2.18)=[5272.22] depth=465,  <ROW>2378.6192(2.22)=[5289.95] depth=475,  <ROW>2360.2759(2.25)=[5309.21] depth=480,  <ROW>2427.7336(2.36)=[5728.31] depth=503,  <ROW>2394.7174(2.69)=[6432.30] depth=573,  <ROW>2375.3487(2.85)=[6780.52] depth=610,  <ROW>2472.8851(2.99)=[7388.68] depth=642,  <ROW>2436.6841(3.12)=[7594.74] depth=667,  <ROW>2447.7713(3.12)=[7625.80] depth=666,  <ROW>2476.7250(3.13)=[7754.55] depth=671,  <ROW><TOTALREQ>66665.84</TOTALREQ><TOTALAGE>130375</TOTALAGE>",
  "weight 125000.00": 130375.0482986111,
  "total_required 125000.00": 66665
}


08:35:52

exec createabn 125000


08:35:52

{
  "Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg><nonce>a99f03a42c8637771177f773abbdb341303b51a28770440f5a67d68c640071de</nonce><ppk>ppk</ppk></abnmsg><abnsig>HxDfcaodxc9tiR0D+WUOy4j9SCZH8jWfmAkS7mTHQ70kPDwfH/Ca+7p69ynN7oI33Y17jqDGsbz9oDDkW7tytLU=</abnsig><abncpk>B7o7cD5otiaNeqnMyV5khw2CFNJLTeqh6L</abncpk><abnwgt>125000</abnwgt>",
  "err": "",
  "coin_age_data_selected": "1.0000(13.86)=[13.86] depth=2931,  <ROW>1.0000(13.86)=[13.86] depth=2931,  <ROW>1.0000(14.38)=[14.38] depth=3042,  <ROW>12.4022(14.38)=[172.58] depth=3042,  <ROW>50.0000(15.94)=[796.95] depth=3367,  <ROW>2301.8849(0.51)=[1178.22] depth=111,  <ROW>2342.2185(0.53)=[1229.74] depth=114,  <ROW>2305.9676(0.73)=[1683.32] depth=159,  <ROW>2341.7357(0.88)=[2055.09] depth=191,  <ROW>2314.7290(1.07)=[2472.63] depth=231,  <ROW>127.1195(21.61)=[2743.90] depth=4532,  <ROW>1387.3182(2.15)=[2977.43] depth=459,  <ROW>2385.4458(1.28)=[3052.97] depth=276,  <ROW>2364.4107(1.32)=[3114.93] depth=287,  <ROW>2391.2520(1.41)=[3374.94] depth=305,  <ROW>2392.9768(1.54)=[3677.12] depth=330,  <ROW>2224.1720(1.77)=[3937.28] depth=381,  <ROW>2374.1741(1.77)=[4202.83] depth=381,  <ROW>2391.4955(1.89)=[4507.67] depth=405,  <ROW>2290.6961(1.97)=[4510.56] depth=422,  <ROW>2415.3781(1.88)=[4549.62] depth=404,  <ROW>2933.1573(1.61)=[4712.42] depth=344,  <ROW>2743.5920(1.85)=[5086.68] depth=397,  <ROW>2385.0204(2.15)=[5119.80] depth=459,  <ROW>2416.9292(2.18)=[5272.22] depth=465,  <ROW>2378.6192(2.22)=[5289.95] depth=475,  <ROW>2360.2759(2.25)=[5309.21] depth=480,  <ROW>2427.7336(2.36)=[5728.31] depth=503,  <ROW>2394.7174(2.69)=[6432.30] depth=573,  <ROW>2375.3487(2.85)=[6780.52] depth=610,  <ROW>2472.8851(2.99)=[7388.68] depth=642,  <ROW>2436.6841(3.12)=[7594.74] depth=667,  <ROW>2447.7713(3.12)=[7625.80] depth=666,  <ROW>2476.7250(3.13)=[7754.55] depth=671,  <ROW><TOTALREQ>66665.84</TOTALREQ><TOTALAGE>130375</TOTALAGE>",
  "success": "83b818755bec72d8113a38882ec029c7efa9edc64bd944f58560dce74b92f3cd",
  "coin_age_data_pre_select": "1.0000(13.86)=[13.86] depth=2931,  <ROW>1.0000(13.86)=[13.86] depth=2931,  <ROW>1.0000(14.38)=[14.38] depth=3042,  <ROW>12.4022(14.38)=[172.58] depth=3042,  <ROW>50.0000(15.94)=[796.95] depth=3367,  <ROW>2301.8849(0.51)=[1178.22] depth=111,  <ROW>2342.2185(0.53)=[1229.74] depth=114,  <ROW>2305.9676(0.73)=[1683.32] depth=159,  <ROW>2341.7357(0.88)=[2055.09] depth=191,  <ROW>2314.7290(1.07)=[2472.63] depth=231,  <ROW>127.1195(21.61)=[2743.90] depth=4532,  <ROW>1387.3182(2.15)=[2977.43] depth=459,  <ROW>2385.4458(1.28)=[3052.97] depth=276,  <ROW>2364.4107(1.32)=[3114.93] depth=287,  <ROW>2391.2520(1.41)=[3374.94] depth=305,  <ROW>2392.9768(1.54)=[3677.12] depth=330,  <ROW>2224.1720(1.77)=[3937.28] depth=381,  <ROW>2374.1741(1.77)=[4202.83] depth=381,  <ROW>2391.4955(1.89)=[4507.67] depth=405,  <ROW>2290.6961(1.97)=[4510.56] depth=422,  <ROW>2415.3781(1.88)=[4549.62] depth=404,  <ROW>2933.1573(1.61)=[4712.42] depth=344,  <ROW>2743.5920(1.85)=[5086.68] depth=397,  <ROW>2385.0204(2.15)=[5119.80] depth=459,  <ROW>2416.9292(2.18)=[5272.22] depth=465,  <ROW>2378.6192(2.22)=[5289.95] depth=475,  <ROW>2360.2759(2.25)=[5309.21] depth=480,  <ROW>2427.7336(2.36)=[5728.31] depth=503,  <ROW>2394.7174(2.69)=[6432.30] depth=573,  <ROW>2375.3487(2.85)=[6780.52] depth=610,  <ROW>2472.8851(2.99)=[7388.68] depth=642,  <ROW>2436.6841(3.12)=[7594.74] depth=667,  <ROW>2447.7713(3.12)=[7625.80] depth=666,  <ROW>2476.7250(3.13)=[7754.55] depth=671,  <ROW><TOTALREQ>66665.84</TOTALREQ><TOTALAGE>130375</TOTALAGE>",
  "audited_weight": 130866.3395988033,
  "vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 1247.01, Age: 0.53, Amount: 2342.00, TxTime: 1563385137...Output #1, Weight: 3953.67, Age: 1.78, Amount: 2224.00, TxTime: 1563277545...Output #2, Weight: 3694.75, Age: 1.54, Amount: 2392.00, TxTime: 1563297685...Output #3, Weight: 5326.61, Age: 2.26, Amount: 2360.00, TxTime: 1563236133...Output #4, Weight: 1700.31, Age: 0.74, Amount: 2305.00, TxTime: 1563367407...Output #5, Weight: 4220.33, Age: 1.78, Amount: 2374.00, TxTime: 1563277545...Output #6, Weight: 2072.35, Age: 0.89, Amount: 2341.00, TxTime: 1563354656...Output #7, Weight: 7643.84, Age: 3.12, Amount: 2447.00, TxTime: 1563161248...Output #8, Weight: 7772.81, Age: 3.14, Amount: 2476.00, TxTime: 1563159909...Output #9, Weight: 5290.03, Age: 2.19, Amount: 2416.00, TxTime: 1563241961...Output #10, Weight: 5746.20, Age: 2.37, Amount: 2427.00, TxTime: 1563226579...Output #11, Weight: 13.87, Age: 13.87, Amount: 1.00, TxTime: 1562232591...Output #12, Weight: 4734.04, Age: 1.61, Amount: 2933.00, TxTime: 1563291686...Output #13, Weight: 2489.69, Age: 1.08, Amount: 2314.00, TxTime: 1563338181...Output #14, Weight: 172.67, Age: 14.39, Amount: 12.00, TxTime: 1562187897...Output #15, Weight: 4525.30, Age: 1.89, Amount: 2391.00, TxTime: 1563267617...Output #16, Weight: 3070.55, Age: 1.29, Amount: 2385.00, TxTime: 1563319906...Output #17, Weight: 2987.65, Age: 2.15, Amount: 1387.00, TxTime: 1563245032...Output #18, Weight: 2744.83, Age: 21.61, Amount: 127.00, TxTime: 1561563790...Output #19, Weight: 6449.95, Age: 2.69, Amount: 2394.00, TxTime: 1563198361...Output #20, Weight: 3392.48, Age: 1.42, Amount: 2391.00, TxTime: 1563308552...Output #21, Weight: 13.87, Age: 13.87, Amount: 1.00, TxTime: 1562232591...Output #22, Weight: 5106.90, Age: 1.86, Amount: 2743.00, TxTime: 1563270282...Output #23, Weight: 6798.02, Age: 2.86, Amount: 2375.00, TxTime: 1563183836...Output #24, Weight: 4567.42, Age: 1.89, Amount: 2415.00, TxTime: 1563267735...Output #25, Weight: 3132.35, Age: 1.33, Amount: 2364.00, TxTime: 1563316659...Output #26, Weight: 4527.44, Age: 1.98, Amount: 2290.00, TxTime: 1563260324...Output #27, Weight: 5137.38, Age: 2.15, Amount: 2385.00, TxTime: 1563245032...Output #28, Weight: 5307.48, Age: 2.23, Amount: 2378.00, TxTime: 1563238304...Output #29, Weight: 797.32, Age: 15.95, Amount: 50.00, TxTime: 1562053371...Output #30, Weight: 7612.70, Age: 3.13, Amount: 2436.00, TxTime: 1563161134...Output #31, Weight: 14.39, Age: 14.39, Amount: 1.00, TxTime: 1562187897...Output #32, Weight: 1195.19, Age: 0.52, Amount: 2301.00, TxTime: 1563386263...Output #33, Weight: 7406.90, Age: 3.00, Amount: 2472.00, TxTime: 1563172259..."
}


exec createabn 10000000 also succeeds.

But getmininginfo still returns

  "abninfo": "No block to mine... Please wait... 1563388615; ",
  "poolinfo5": "Internal ABN: Invalid 1563388480; ",
  "gsc_errors": "low abn weight 0",

And I haven't  created any GSC tx lately in prod. Also I tried to restart but I get the same.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 18, 2019, 09:47:49 am
Code: [Select]
08:34:12

exec getabnweight 125000 1


08:34:12

{
  "Command": "getabnweight",
  "version": 2.6,
  "weight": 1265474159.938079,
  "total_required": 28859592,
  "coin_age_data_pre_select": "1.0000(13.86)=[13.86] depth=2931,  <ROW>1.0000(13.86)=[13.86] depth=2931,  <ROW>1.0000(14.38)=[14.38] depth=3042,  <ROW>12.4022(14.38)=[172.58] depth=3042,  <ROW>50.0000(15.94)=[796.95] depth=3367,  <ROW>2301.8849(0.51)=[1178.22] depth=111,  <ROW>2342.2185(0.53)=[1229.74] depth=114,  <ROW>2305.9676(0.73)=[1683.32] depth=159,  <ROW>2341.7357(0.88)=[2055.09] depth=191,  <ROW>2314.7290(1.07)=[2472.63] depth=231,  <ROW>127.1195(21.61)=[2743.90] depth=4532,  <ROW>1387.3182(2.15)=[2977.43] depth=459,  <ROW>2385.4458(1.28)=[3052.97] depth=276,  <ROW>2364.4107(1.32)=[3114.93] depth=287,  <ROW>2391.2520(1.41)=[3374.94] depth=305,  <ROW>2392.9768(1.54)=[3677.12] depth=330,  <ROW>2224.1720(1.77)=[3937.28] depth=381,  <ROW>2374.1741(1.77)=[4202.83] depth=381,  <ROW>2391.4955(1.89)=[4507.67] depth=405,  <ROW>2290.6961(1.97)=[4510.56] depth=422,  <ROW>2415.3781(1.88)=[4549.62] depth=404,  <ROW>2933.1573(1.61)=[4712.42] depth=344,  <ROW>2743.5920(1.85)=[5086.68] depth=397,  <ROW>2385.0204(2.15)=[5119.80] depth=459,  <ROW>2416.9292(2.18)=[5272.22] depth=465,  <ROW>2378.6192(2.22)=[5289.95] depth=475,  <ROW>2360.2759(2.25)=[5309.21] depth=480,  <ROW>2427.7336(2.36)=[5728.31] depth=503,  <ROW>2394.7174(2.69)=[6432.30] depth=573,  <ROW>2375.3487(2.85)=[6780.52] depth=610,  <ROW>2472.8851(2.99)=[7388.68] depth=642,  <ROW>2436.6841(3.12)=[7594.74] depth=667,  <ROW>2447.7713(3.12)=[7625.80] depth=666,  <ROW>2476.7250(3.13)=[7754.55] depth=671,  <ROW><TOTALREQ>66665.84</TOTALREQ><TOTALAGE>130375</TOTALAGE>",
  "weight 125000.00": 130375.0482986111,
  "total_required 125000.00": 66665
}


08:35:52

exec createabn 125000


08:35:52

{
  "Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg><nonce>a99f03a42c8637771177f773abbdb341303b51a28770440f5a67d68c640071de</nonce><ppk>ppk</ppk></abnmsg><abnsig>HxDfcaodxc9tiR0D+WUOy4j9SCZH8jWfmAkS7mTHQ70kPDwfH/Ca+7p69ynN7oI33Y17jqDGsbz9oDDkW7tytLU=</abnsig><abncpk>B7o7cD5otiaNeqnMyV5khw2CFNJLTeqh6L</abncpk><abnwgt>125000</abnwgt>",
  "err": "",
  "coin_age_data_selected": "1.0000(13.86)=[13.86] depth=2931,  <ROW>1.0000(13.86)=[13.86] depth=2931,  <ROW>1.0000(14.38)=[14.38] depth=3042,  <ROW>12.4022(14.38)=[172.58] depth=3042,  <ROW>50.0000(15.94)=[796.95] depth=3367,  <ROW>2301.8849(0.51)=[1178.22] depth=111,  <ROW>2342.2185(0.53)=[1229.74] depth=114,  <ROW>2305.9676(0.73)=[1683.32] depth=159,  <ROW>2341.7357(0.88)=[2055.09] depth=191,  <ROW>2314.7290(1.07)=[2472.63] depth=231,  <ROW>127.1195(21.61)=[2743.90] depth=4532,  <ROW>1387.3182(2.15)=[2977.43] depth=459,  <ROW>2385.4458(1.28)=[3052.97] depth=276,  <ROW>2364.4107(1.32)=[3114.93] depth=287,  <ROW>2391.2520(1.41)=[3374.94] depth=305,  <ROW>2392.9768(1.54)=[3677.12] depth=330,  <ROW>2224.1720(1.77)=[3937.28] depth=381,  <ROW>2374.1741(1.77)=[4202.83] depth=381,  <ROW>2391.4955(1.89)=[4507.67] depth=405,  <ROW>2290.6961(1.97)=[4510.56] depth=422,  <ROW>2415.3781(1.88)=[4549.62] depth=404,  <ROW>2933.1573(1.61)=[4712.42] depth=344,  <ROW>2743.5920(1.85)=[5086.68] depth=397,  <ROW>2385.0204(2.15)=[5119.80] depth=459,  <ROW>2416.9292(2.18)=[5272.22] depth=465,  <ROW>2378.6192(2.22)=[5289.95] depth=475,  <ROW>2360.2759(2.25)=[5309.21] depth=480,  <ROW>2427.7336(2.36)=[5728.31] depth=503,  <ROW>2394.7174(2.69)=[6432.30] depth=573,  <ROW>2375.3487(2.85)=[6780.52] depth=610,  <ROW>2472.8851(2.99)=[7388.68] depth=642,  <ROW>2436.6841(3.12)=[7594.74] depth=667,  <ROW>2447.7713(3.12)=[7625.80] depth=666,  <ROW>2476.7250(3.13)=[7754.55] depth=671,  <ROW><TOTALREQ>66665.84</TOTALREQ><TOTALAGE>130375</TOTALAGE>",
  "success": "83b818755bec72d8113a38882ec029c7efa9edc64bd944f58560dce74b92f3cd",
  "coin_age_data_pre_select": "1.0000(13.86)=[13.86] depth=2931,  <ROW>1.0000(13.86)=[13.86] depth=2931,  <ROW>1.0000(14.38)=[14.38] depth=3042,  <ROW>12.4022(14.38)=[172.58] depth=3042,  <ROW>50.0000(15.94)=[796.95] depth=3367,  <ROW>2301.8849(0.51)=[1178.22] depth=111,  <ROW>2342.2185(0.53)=[1229.74] depth=114,  <ROW>2305.9676(0.73)=[1683.32] depth=159,  <ROW>2341.7357(0.88)=[2055.09] depth=191,  <ROW>2314.7290(1.07)=[2472.63] depth=231,  <ROW>127.1195(21.61)=[2743.90] depth=4532,  <ROW>1387.3182(2.15)=[2977.43] depth=459,  <ROW>2385.4458(1.28)=[3052.97] depth=276,  <ROW>2364.4107(1.32)=[3114.93] depth=287,  <ROW>2391.2520(1.41)=[3374.94] depth=305,  <ROW>2392.9768(1.54)=[3677.12] depth=330,  <ROW>2224.1720(1.77)=[3937.28] depth=381,  <ROW>2374.1741(1.77)=[4202.83] depth=381,  <ROW>2391.4955(1.89)=[4507.67] depth=405,  <ROW>2290.6961(1.97)=[4510.56] depth=422,  <ROW>2415.3781(1.88)=[4549.62] depth=404,  <ROW>2933.1573(1.61)=[4712.42] depth=344,  <ROW>2743.5920(1.85)=[5086.68] depth=397,  <ROW>2385.0204(2.15)=[5119.80] depth=459,  <ROW>2416.9292(2.18)=[5272.22] depth=465,  <ROW>2378.6192(2.22)=[5289.95] depth=475,  <ROW>2360.2759(2.25)=[5309.21] depth=480,  <ROW>2427.7336(2.36)=[5728.31] depth=503,  <ROW>2394.7174(2.69)=[6432.30] depth=573,  <ROW>2375.3487(2.85)=[6780.52] depth=610,  <ROW>2472.8851(2.99)=[7388.68] depth=642,  <ROW>2436.6841(3.12)=[7594.74] depth=667,  <ROW>2447.7713(3.12)=[7625.80] depth=666,  <ROW>2476.7250(3.13)=[7754.55] depth=671,  <ROW><TOTALREQ>66665.84</TOTALREQ><TOTALAGE>130375</TOTALAGE>",
  "audited_weight": 130866.3395988033,
  "vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 1247.01, Age: 0.53, Amount: 2342.00, TxTime: 1563385137...Output #1, Weight: 3953.67, Age: 1.78, Amount: 2224.00, TxTime: 1563277545...Output #2, Weight: 3694.75, Age: 1.54, Amount: 2392.00, TxTime: 1563297685...Output #3, Weight: 5326.61, Age: 2.26, Amount: 2360.00, TxTime: 1563236133...Output #4, Weight: 1700.31, Age: 0.74, Amount: 2305.00, TxTime: 1563367407...Output #5, Weight: 4220.33, Age: 1.78, Amount: 2374.00, TxTime: 1563277545...Output #6, Weight: 2072.35, Age: 0.89, Amount: 2341.00, TxTime: 1563354656...Output #7, Weight: 7643.84, Age: 3.12, Amount: 2447.00, TxTime: 1563161248...Output #8, Weight: 7772.81, Age: 3.14, Amount: 2476.00, TxTime: 1563159909...Output #9, Weight: 5290.03, Age: 2.19, Amount: 2416.00, TxTime: 1563241961...Output #10, Weight: 5746.20, Age: 2.37, Amount: 2427.00, TxTime: 1563226579...Output #11, Weight: 13.87, Age: 13.87, Amount: 1.00, TxTime: 1562232591...Output #12, Weight: 4734.04, Age: 1.61, Amount: 2933.00, TxTime: 1563291686...Output #13, Weight: 2489.69, Age: 1.08, Amount: 2314.00, TxTime: 1563338181...Output #14, Weight: 172.67, Age: 14.39, Amount: 12.00, TxTime: 1562187897...Output #15, Weight: 4525.30, Age: 1.89, Amount: 2391.00, TxTime: 1563267617...Output #16, Weight: 3070.55, Age: 1.29, Amount: 2385.00, TxTime: 1563319906...Output #17, Weight: 2987.65, Age: 2.15, Amount: 1387.00, TxTime: 1563245032...Output #18, Weight: 2744.83, Age: 21.61, Amount: 127.00, TxTime: 1561563790...Output #19, Weight: 6449.95, Age: 2.69, Amount: 2394.00, TxTime: 1563198361...Output #20, Weight: 3392.48, Age: 1.42, Amount: 2391.00, TxTime: 1563308552...Output #21, Weight: 13.87, Age: 13.87, Amount: 1.00, TxTime: 1562232591...Output #22, Weight: 5106.90, Age: 1.86, Amount: 2743.00, TxTime: 1563270282...Output #23, Weight: 6798.02, Age: 2.86, Amount: 2375.00, TxTime: 1563183836...Output #24, Weight: 4567.42, Age: 1.89, Amount: 2415.00, TxTime: 1563267735...Output #25, Weight: 3132.35, Age: 1.33, Amount: 2364.00, TxTime: 1563316659...Output #26, Weight: 4527.44, Age: 1.98, Amount: 2290.00, TxTime: 1563260324...Output #27, Weight: 5137.38, Age: 2.15, Amount: 2385.00, TxTime: 1563245032...Output #28, Weight: 5307.48, Age: 2.23, Amount: 2378.00, TxTime: 1563238304...Output #29, Weight: 797.32, Age: 15.95, Amount: 50.00, TxTime: 1562053371...Output #30, Weight: 7612.70, Age: 3.13, Amount: 2436.00, TxTime: 1563161134...Output #31, Weight: 14.39, Age: 14.39, Amount: 1.00, TxTime: 1562187897...Output #32, Weight: 1195.19, Age: 0.52, Amount: 2301.00, TxTime: 1563386263...Output #33, Weight: 7406.90, Age: 3.00, Amount: 2472.00, TxTime: 1563172259..."
}


exec createabn 10000000 also succeeds.

But getmininginfo still returns

  "abninfo": "No block to mine... Please wait... 1563388615; ",
  "poolinfo5": "Internal ABN: Invalid 1563388480; ",
  "gsc_errors": "low abn weight 0",

And I haven't  created any GSC tx lately in prod. Also I tried to restart but I get the same.


So, Im trying to reproduce this - and so far I cant break 1.4.5.9.
First, are you running 1.4.5.9 (this is the last one you built for develop)?

Ive tried ABN mining in testnet and Prod, both successfully.
Btw, do you have pool mining credentials in, or are you running solo?  (I assumed we are running solo in this first set of tests).

Finally, could you please try abn mining solo in testnet, and see if there is a difference?

(Im solo mining in testnet with a 1000 abn, and solo mining in prod with a 1000 abn).

I forgot to ask, btw did you ensure your wallet was unlocked and you waited over 10 minutes for mining to start If you locked it?
Try unlocking it, then do a new 'setgenerate true N" *after* that.  See if it clears the errors?

(You can look in the log and see if you had any testblockvaliditylite errors; if so paste them here).

Please erase the log before starting all this - that way we can hone in on the problem quickly.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 18, 2019, 10:16:52 am

So, Im trying to reproduce this - and so far I cant break 1.4.5.9.
First, are you running 1.4.5.9 (this is the last one you built for develop)?

Ive tried ABN mining in testnet and Prod, both successfully.
Btw, do you have pool mining credentials in, or are you running solo?  (I assumed we are running solo in this first set of tests).

Finally, could you please try abn mining solo in testnet, and see if there is a difference?

(Im solo mining in testnet with a 1000 abn, and solo mining in prod with a 1000 abn).

I forgot to ask, btw did you ensure your wallet was unlocked and you waited over 10 minutes for mining to start If you locked it?
Try unlocking it, then do a new 'setgenerate true N" *after* that.  See if it clears the errors?

(You can look in the log and see if you had any testblockvaliditylite errors; if so paste them here).

Please erase the log before starting all this - that way we can hone in on the problem quickly.

I came back a couple of hours later and it said "Internal ABN: OK"
So maybe it was a matter of waiting a while for this to fix by itself.

Sorry for the headaches.

Now I am solo mining fine.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 18, 2019, 10:57:47 am
I came back a couple of hours later and it said "Internal ABN: OK"
So maybe it was a matter of waiting a while for this to fix by itself.

Sorry for the headaches.

Now I am solo mining fine.


Can you try it all over again, and see what the total lag is?  Also could you check the log and see what the timestamp difference is and how long it took to recover?

This way we can modify the code to remove that situation.

Also, you didn't explain if it was a locked wallet; was it because the wallet was locked and then you unlocked it and the problem goes away after a certain amount of time?  (The error in the log would be telling).

I wonder if we should design the wallet to be able to mine without being unlocked.  Maybe this is a hurdle for newbies.

Again, is this 1.4.5.9 that is being tested (cause I think 1.2 in prod was a few months ago).



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 18, 2019, 11:10:22 am
Getmininginfo dev 1.4.5.9 on mainnet

Code: [Select]
{
 "blocks": 132361,
 "currentblocksize": 1000,
 "currentblocktx": 0,
 "difficulty": 10360.99487125054,
 "errors": "",
 "pooledtx": 0,
 "chain": "main",
 "genproclimit": 1,
 "networkhashps": 619612.9706705563,
 "hashps": 7892.611994219653,
 "minerstarttime": "07-17-2019 20:13:41",
 "hashcounter": 2097288,
 "pooledtx": 0,
 "chain": "main",
 "biblepay-generate": true,
 "poolinfo1": "Pool mining with sam2_funded; ",
 "poolinfo2": "Submitting Solution 07-17-2019 20:17:23; ",
 "poolinfo3": "",
 "abninfo": "Mining with funded Valid ABN 36ad1fbdb62e2c7775e3000c29f4f87d59a4aa660277bef2271cdf94e96e4137; ",
 "poolinfo5": "Internal ABN: Invalid 1563394642; ",
 "gsc_errors": "",
 "poolmining": true,
 "pool_url": "https://pool.biblepay.org",
 "required_abn_weight": 125000
}
cli -version
BiblePay Core RPC client version 1.4.5.9

So just to confirm:

1) You tested solo mining, I tested solo mining, MIP tested solo mining and that worked with internal ABNs fine.

2) You tested both funded and non funded mining against pool.biblepay.org with pleaides, and a non-funded miner.

3) Can you please send a GSC and verify the Cameroon is no longer compounding?  For me they are no longer compounding.

4) We are waiting to turn on LLMQ's before checking the POSE banned states.

5) Did I miss anything?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 18, 2019, 12:00:25 pm
So just to confirm:

1) You tested solo mining, I tested solo mining, MIP tested solo mining and that worked with internal ABNs fine.

It is a bit hard to capture all the scenarios, as on mainnet, i am limited by ABN. But it starts ok. Using a common wallet, i cannot confirm which machine and hence client solved the block.

2) You tested both funded and non funded mining against pool.biblepay.org with pleaides, and a non-funded miner.

It works initially and sometimes i get this error of a stale block. Don’t know if it specific to 1459. But the wallet is empty and not encrypted.

Code: [Select]
{
  "blocks": 132449,
  "currentblocksize": 24911,
  "currentblocktx": 38,
  "difficulty": 8470.190872573861,
  "errors": "",
  "pooledtx": 38,
  "chain": "main",
  "genproclimit": 3,
  "networkhashps": 558664.7160105165,
  "hashps": 20949.85006229456,
  "minerstarttime": "07-18-2019 05:04:56",
  "hashcounter": 126449943,
  "pooledtx": 38,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "Pool mining with proteus_funded; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
  "poolinfo2": "RM_07-18-2019 16:51:35; RM_07-18-2019 16:51:44; RM_07-18-2019 16:51:50; ",
  "poolinfo3": "",
  "abninfo": "Received a stale block from the pool... Please wait... ; Received a stale block from the pool... Please wait... ; Received a stale block from the pool... Please wait... ; ",
  "poolinfo5": "Internal ABN: Invalid 1563468695; ",
  "gsc_errors": "",
  "poolmining": true,
  "pool_url": "https://pool.biblepay.org",
  "required_abn_weight": 125000
}
cli -version
BiblePay Core RPC client version 1.4.5.9



3) Can you please send a GSC and verify the Cameroon is no longer compounding?  For me they are no longer compounding.

I cannot see any sancs? Is GSC testing DIP3 sanc dependent?

4) We are waiting to turn on LLMQ's before checking the POSE banned states.

5) Did I miss anything?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 18, 2019, 12:15:48 pm

1.It is a bit hard to capture all the scenarios, as on mainnet, i am limited by ABN. But it starts ok. Using a common wallet, i cannot confirm which machine and hence
  client solved the block.
   It works initially and sometimes i get this error of a stale block. Don’t know if it specific to 1459. But the wallet is empty and not encrypted.

2) Can you please send a GSC and verify the Cameroon is no longer compounding?  For me they are no longer compounding.

I cannot see any sancs? Is GSC testing DIP3 sanc dependent?


So on #1, I do know about the stale block error; that is expected; its the pool sometimes has trouble finding an ABN to give to you (but it usually finds one within 15 secs, so thats OK) it just keeps trying and eventually gets one.

On the sancs, my machine is tied up, but I have not had that problem.  We dont have to wait til LLMQ is turned on in 1.4.5.9 - sancs should already be up and running and in deterministics mode now-  we have about 6 sancs running.

It might be your data is corrupted;  When you boot, ensure litemode is Off (litemode=0 or not in the config).
Then ensure your mnsync 'mnsync status' has reached 999.
You should see 6 sancs in the Sancs list then.

If not, try deleting your mncache*, mnp*, and gov*.dat, and retry again with a cold boot (you might have a bad sanc cache).

Then let me know if 'exec health' shows votes > 4, etc.

Then we can test cameroon again.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 18, 2019, 03:26:54 pm
1. cli -version
BiblePay Core RPC client version 1.4.5.9 (downloaded binaries)

2. both wallets are fresh unencrypted and empty wallets (deleted whole .biblepayevolution dir)

3. both wallets sync to the top - block height 132570
449c1b5de627362f8369836ab8497720ff36aab9ba45e3bc93d3f65a9c654566

4. They appear to mine on the pool (mainnet) as
a. proteus_funded (Ubuntu 16.04 kernel 4.4.0-154-generic)
b. sam2_funded (Ubuntu 18.04 kernel 4.15.0-54-generic)

5. sanc list of both miners are empty
{
}

6. cli exec health
Code: [Select]
{
 "Command": "health",
 "pam_hash": "0000000000000000000000000000000000000000000000000000000000000000",
 "pam_hash_internal": "00000000000000000000000000000000c52798b5da1155a10e047b781f1a45ba",
 "WARNING": "Our internal PAM hash disagrees with the network. ",
 "govobjhash": "0000000000000000000000000000000000000000000000000000000000000000",
 "Amounts": "",
 "Addresses": "",
 "votes": 0,
 "required_votes": 10,
 "last_superblock": 132450,
 "next_superblock": 132655,
 "next_superblock_triggered": false,
 "Healthy": false,
 "GSC_Voted_In": false
}

Can you kindly provide me a list of DIP3 sancs so that I can just add them into my conf file, please?

Thank you.





Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 18, 2019, 03:38:47 pm

Can you try it all over again, and see what the total lag is?  Also could you check the log and see what the timestamp difference is and how long it took to recover?

This way we can modify the code to remove that situation.

Also, you didn't explain if it was a locked wallet; was it because the wallet was locked and then you unlocked it and the problem goes away after a certain amount of time?  (The error in the log would be telling).

I wonder if we should design the wallet to be able to mine without being unlocked.  Maybe this is a hurdle for newbies.

Again, is this 1.4.5.9 that is being tested (cause I think 1.2 in prod was a few months ago).




I am on 1.4.5.9 against mainnet
The wallet was locked but I unlocked and this message was there for several hours after unlocking.
However I repeated the same steps now and I can't reproduce the same message, it behaves as normal.

So maybe it was a glitch on my end.

About unlocking the wallet, I think it would be user friendly to detect that user has setgenerate=true and then, if wallet is locked, show some red message on the Overview screen to unlock it.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 18, 2019, 05:41:02 pm
1. cli -version
BiblePay Core RPC client version 1.4.5.9 (downloaded binaries)

2. both wallets are fresh unencrypted and empty wallets (deleted whole .biblepayevolution dir)

3. both wallets sync to the top - block height 132570
449c1b5de627362f8369836ab8497720ff36aab9ba45e3bc93d3f65a9c654566

4. They appear to mine on the pool (mainnet) as
a. proteus_funded (Ubuntu 16.04 kernel 4.4.0-154-generic)
b. sam2_funded (Ubuntu 18.04 kernel 4.15.0-54-generic)

5. sanc list of both miners are empty
{
}

6. cli exec health
Code: [Select]
{
 "
 "votes": 0,
 "required_votes": 10,
 "last_superblock": 132450,
 "next_superblock": 132655,
 "next_superblock_triggered": false,
 "Healthy": false,
 "GSC_Voted_In": false
}

Can you kindly provide me a list of DIP3 sancs so that I can just add them into my conf file, please?

Thank you.
1) I just wanted to test mining on mainnet, just to ensure syncing and mining worked, but I wanted us to revert back to Testnet for testing cameroon one and GSCs.  Sorry for the confusion. 
  1b) So, yes, This 1.4.5.9 Testnet branch is called our 0.14 develop branch, and its protocol version is not at all compatible with non deterministic sancs.  Prod (mainnet) is running in non-deterministic (IE non dip 3 mode).  So correct, you will not be able to see any prod sancs in Prod mode on 1.4.5.9.  However, when Prod starts upgrading to dip3 (deterministic), you Will start seeing them on this version.  As a matter of fact, that is something of dire importance we need to test in about a week, once we start pushing that in prod (we are waiting in prod for a Bit to flip over called Dip3-Active, I believe it will flip in about 7 days).
1c)  You can not manually add sancs to the config, (except your own), but in dip3 mode (IE 0.14 branch mode) you cannot manually add any - they all must be sent with ProReg Tx's.  So for all intents and purposes, you cant add them.
2) In Testnet mode however, you should see about 6 sancs right now.  I just booted up in testnet mode and I do see the 6 sancs.  I see exec health has 3 votes.  Does yours agree with the votes count?
3) The other info you posted looks good, on the mining info.
4) Now it would be cool for us to test cameroon again in Testnet mode - just to verify you are no longer seeing the compounded rewards?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 18, 2019, 05:43:27 pm
Dear Rob,

There appears to be unexplained behaviour when funded and unfunded miner are in one account on the pool.

Pollux     unfunded 135,484 hps 1443
Sam2_funded              7,571 hps 1459
Proteus_funded        32,864 hps 1459

Leaderboard
 oncoapop            17,916.11 hps

Thanks

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 18, 2019, 05:45:10 pm
I am on 1.4.5.9 against mainnet
The wallet was locked but I unlocked and this message was there for several hours after unlocking.
However I repeated the same steps now and I can't reproduce the same message, it behaves as normal.

So maybe it was a glitch on my end.

About unlocking the wallet, I think it would be user friendly to detect that user has setgenerate=true and then, if wallet is locked, show some red message on the Overview screen to unlock it.

Ok great, glad it could not be reproduced again; as I have an encrypted mainnet wallet also, and I am aware of it going to Low ABN weight 0 when it switches, and then the miner being stuck until the ABN expires; but just for ease of use sake, I went ahead and added a line of code to handle this-   so in the next version, when the wallet is locked then unlocked and the miner is in the "0 abn state", it will recover within 15 secs.  That should help cut down the complaints too.

Great idea on the setgenerate=true and the locked wallet.  Ill check this:
If miner is Not funded, and locked, and generating, then we will make a warning appear on the overview page And in the getmininginfo.  Ill do that right now, thanks for the advice!



Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 18, 2019, 05:49:29 pm
On a side note, the next wallet version is going to have a new procotol that will allow faster transition and more accurate and quicker comm, but for now, I believe the pool will take this into account after a 1-7 minute lag.

Can you confirm if the HPS settles down properly after 5 mins?

If not, what discrepency remains?

Whoops, Im not giving enough info.

The pool can only handle One miner funding type per USER at a time for the time being (Funded or non funded).
It does allow switching however, but not a conflict per miner (all must be either non funded or funded at the same time).
You can accomplish this by copying the same wallet.dat out to the miners.

This limitation will be removed after people upgrade to the new protocol version - but its not released yet.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 19, 2019, 02:24:11 pm
I am trying to test pool mining, but after 15 minutes the Core client is stuck in “Connecting to peers” and it does not sync. I just set up:

pool=https://pool.biblepay.org
workerid=MIP
minersleep=0
generate=1

There are 20 banned peers and around 10 working ones too.
I will wait a few more minutes to see if it fixes

PS: I see this in debug.log
Code: [Select]
2019-07-19 19:07:26 ERROR: AcceptBlockHeader: block 6e6f1676585e16959bb1dc81fcc79a60932ee29cd8681504f4295a97547fd92b is marked invalid
2019-07-19 19:07:26 ERROR: invalid header received
2019-07-19 19:07:26 ProcessMessages(headers, 26409 bytes) FAILED peer=0
2019-07-19 19:07:32 ERROR: AcceptBlockHeader: block 6e6f1676585e16959bb1dc81fcc79a60932ee29cd8681504f4295a97547fd92b is marked invalid
2019-07-19 19:07:32 ERROR: invalid header received
2019-07-19 19:07:32 ProcessMessages(headers, 26409 bytes) FAILED peer=1
2019-07-19 19:07:35 Loading addresses from DNS seeds (could take a while)
2019-07-19 19:07:35 1 addresses found from DNS seeds
2019-07-19 19:07:35 dnsseed thread exit
2019-07-19 19:10:13 ERROR: AcceptBlockHeader: block 6e6f1676585e16959bb1dc81fcc79a60932ee29cd8681504f4295a97547fd92b is marked invalid
2019-07-19 19:10:13 ERROR: invalid header received
2019-07-19 19:10:13 ProcessMessages(headers, 26409 bytes) FAILED peer=1
2019-07-19 19:18:02 ERROR: AcceptBlockHeader: block 6e6f1676585e16959bb1dc81fcc79a60932ee29cd8681504f4295a97547fd92b is marked invalid
2019-07-19 19:18:02 ERROR: invalid header received
2019-07-19 19:18:02 ProcessMessages(headers, 26490 bytes) FAILED peer=1
2019-07-19 19:22:32 Timeout downloading headers from peer=1, disconnecting
2019-07-19 19:22:33 ERROR: AcceptBlockHeader: block 6e6f1676585e16959bb1dc81fcc79a60932ee29cd8681504f4295a97547fd92b is marked invalid
2019-07-19 19:22:33 ERROR: invalid header received
2019-07-19 19:22:33 ProcessMessages(headers, 26571 bytes) FAILED peer=2

The only thing I've been doing in this Mac lately is solo mining.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 19, 2019, 02:52:44 pm
Dear Rob,

Please be aware that both my 1.4.5.9 miners appear to constantly drift off by themselves.

The following machines are running 1.4.5.9 on mainnet

XXX.XXX.098.201
XXX.XXX.108.063

cli -version
BiblePay Core RPC client version 1.4.5.9
block
132761
hash
20d6e3054e7b0c6d957e0884e02141e9e70d8c54758c02b95fc87e2b289a7238


All my other machines are on

BiblePay Core RPC client version 1.4.4.3
getblockhash 132761
960755cefc3ded480ac454ea03a264c8279c9f68b8fada228cd8147046e3f1b5

This can be verified in real time from my monitoring web page
https://oncoapop.sdf.org/biblepaymain/biblepay_chainstate.shtml

getblockhash 132778
02e667e874569ed6000160a6e05bafe7f3a09379da6d529c2d403a1cd32bf6af
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 19, 2019, 03:35:54 pm
I reindexed and everything seems fine. I am with funded mining. I will leave it for a while then try unfunded (unless you instruct me otherwise)
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 19, 2019, 05:57:12 pm
Dear Rob,

Please be aware that both my 1.4.5.9 miners appear to constantly drift off by themselves.

The following machines are running 1.4.5.9 on mainnet

XXX.XXX.098.201
XXX.XXX.108.063

cli -version
BiblePay Core RPC client version 1.4.5.9
block
132761
hash
20d6e3054e7b0c6d957e0884e02141e9e70d8c54758c02b95fc87e2b289a7238


All my other machines are on

BiblePay Core RPC client version 1.4.4.3
getblockhash 132761
960755cefc3ded480ac454ea03a264c8279c9f68b8fada228cd8147046e3f1b5

This can be verified in real time from my monitoring web page
https://oncoapop.sdf.org/biblepaymain/biblepay_chainstate.shtml

getblockhash 132778
02e667e874569ed6000160a6e05bafe7f3a09379da6d529c2d403a1cd32bf6af

These two 1.4.5.9 miners:

1. Tried exec reassesschains 5 times to no avail.

2. Re-Started wallet with -erasechain=1

3. Currently on main chain at height of other machines running 1.4.4.3

4. Will put them on the pool using workerids “sam2” and “proteus” with “_funded” for funded workerids respectively. They have the same wallet as other miners running 1.4.4.3

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 19, 2019, 08:04:48 pm
I reindexed and everything seems fine. I am with funded mining. I will leave it for a while then try unfunded (unless you instruct me otherwise)

Ok, I just realized something.
First let me clarify - so in TESTNET against Develop branch (1.4.5.9), I just checked my 3 sancs and my dev node and they are all in sync.  So I think we can all agree, we didnt go off the rails in TESTNET.

I asked MIP and Oncoapop to test POOL mining in PROD (Mainnet) against 1.4.5.9.  So MIP uses an existing blockchain, and goes off the rails, and so does Oncoapop.

So, heres what I think we need to do.  I think we need to wait on testing Mainnet until Mainnet enables dip3.  Because there are 2 places in the code in 1.4.5.9 that make deterministic calls, assuming DIP3 is always on - for example, if it sees a non-fin-tx, it will handle that differently than mainnet currently does.

So lets go back to Testnet for a while, and once we enable the dip3 sancs in mainnet, Ill jump in testnet and try to mine for a day or two and join you guys and see if we stay on track.

As you both might know, 1.4.5.9 has no sancs to load gov data from either (from mainnet), so its probably banning sancs too.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 19, 2019, 08:06:00 pm
Dear Rob,

Please be aware that both my 1.4.5.9 miners appear to constantly drift off by themselves.

The following machines are running 1.4.5.9 on mainnet

XXX.XXX.098.201
XXX.XXX.108.063

cli -version
BiblePay Core RPC client version 1.4.5.9
block
132761
hash
20d6e3054e7b0c6d957e0884e02141e9e70d8c54758c02b95fc87e2b289a7238


All my other machines are on

BiblePay Core RPC client version 1.4.4.3
getblockhash 132761
960755cefc3ded480ac454ea03a264c8279c9f68b8fada228cd8147046e3f1b5

This can be verified in real time from my monitoring web page
https://oncoapop.sdf.org/biblepaymain/biblepay_chainstate.shtml

getblockhash 132778
02e667e874569ed6000160a6e05bafe7f3a09379da6d529c2d403a1cd32bf6af


Well, thanks for trying.  Yeah, lets hold off on testing 1.4.5.9 against mainnet for a little while.

I make the assumption that we are banning other nodes in prod.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 19, 2019, 08:07:53 pm
These two 1.4.5.9 miners:

1. Tried exec reassesschains 5 times to no avail.

2. Re-Started wallet with -erasechain=1

3. Currently on main chain at height of other machines running 1.4.4.3

4. Will put them on the pool using workerids “sam2” and “proteus” with “_funded” for funded workerids respectively. They have the same wallet as other miners running 1.4.4.3

I assume it will drift off, but Im not sure at what point.  Probably at the point of the next superblock if I were to make a wild guess.

One thing that might work is running 1.4.5.9 in 'litemode=1', if you really want to, but I think its probably futile until we lock in dip 3 in prod.

Can you please check on cameroon 1 in testnet again also?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 21, 2019, 02:28:17 am

So lets go back to Testnet for a while, and once we enable the dip3 sancs in mainnet, Ill jump in testnet and try to mine for a day or two and join you guys and see if we stay on track.

As you both might know, 1.4.5.9 has no sancs to load gov data from either (from mainnet), so its probably banning sancs too.

Ok understood. Tell us if you need to check anything else in testnet.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 21, 2019, 09:30:41 am
Ok understood. Tell us if you need to check anything else in testnet.

Lets check:
1) Have you received a regular single cameroon payment per superblock cycle (not more than one payment per cycle), and at least 1 (as long as you send at least 1 gsc per cycle)?

2) Send me a new child ID and an amount you want to pay and lets ensure you can kick another one in?
3) Lets ensure you get kicked out when you fail to pay also.

EDIT:  After church Ill check into the LLMQ punchlist.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 23, 2019, 07:41:00 pm
In the mean time you guys can read this about LLMQs:

https://blog.dash.org/product-brief-dash-core-release-v0-14-0-now-on-testnet-8f5f4ad45c96

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 23, 2019, 07:55:08 pm
One thing that is very dissapointing in testnet, is I see exec health shows '3' votes.  (I have 3 sancs).

Do we have anyone testing other than me?

We need at least 4 to test LLMQs.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 23, 2019, 08:36:34 pm
Dip0008 is now enabled in TestNet and Spork_17 (DKG's for LLMQs) are now enabled.

This means the 3 existing sancs will now start making hourly (and daily) quorums.  They should technically cause quorum info to be written in the coinbase transaction.

We will be able to see the effects of this by monitoring POSE scores per sanctuary.  Technically, the sancs who are offline should start receiving POSE bans.

We may be able to barely make a quorum with 3 nodes in testnet as testnet requires > 50% participation of 5 (so that means 2.5 = 50%) and that means the hourly quorums would succeed, but I would still like to see a couple more sancs online in testnet for LLMQs and Chainlocks for quality testing.

Now we just need to verify the quorum data is written, the non participating nodes are banned (for a few days) then we can enable chainlocks.


From the Dash TestNet thread, testing chainlocks:

https://www.dash.org/forum/threads/dash-core-v0-14-on-mainnet.45821/

EDIT:  After reading all that I must say I feel a breath of fresh air here in our community as we have less infighting :), I'm glad Camosoul hasn't been posting here in testnet!


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 24, 2019, 05:27:20 am
cli -version
BiblePay Core RPC client version 1.4.5.9

1.   Begin experiment: Not in leaderboard
Code: [Select]
{
  "Prominence": "Details",
  "Healing": "Diary Entries",
  "Prominence": "Totals"
}
2.   Tithe normally
Code: [Select]

{
  "Command": "sendgscc"
}
3.   Leaderboard true
Code: [Select]
{
  "Prominence": "Details",
  "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.70%",
  "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 458746647.00": "64.03%",
  "Healing": "Diary Entries",
  "Prominence": "Totals",
  "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 458749314.00, Reward: 535266.400": "64.730%"
}

3. exec analyze 167447 oncoapop1
[code]
{
  "Command": "analyze",
  "Totals": "CAMEROON-ONE|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|2667|0.00698158|oncoapop1|2668\nPOG|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|458746647|0.64029122|oncoapop1|465702655\n",
  "0": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 167444.00, TXID: 6f6a7d7a447e8788ccce7b5fea3a1bc0dfcb844698afdc2f9b3a1d7c38f4049d, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 130279453.0504, Donation: 0.0000, UserTotal: 2666.67",
  "1": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 167445.00, TXID: 58e8fc4456674bb74ac30f7854fb6d73cf84ad7a74786e55cb499560ef16699e, NickName: oncoapop1, Points: 458746647.36, Campaign: POG, CoinAge: 239813460.8751, Donation: 7.0000, UserTotal: 458749314.02",
  "2": ""
}

4. POG + Cameroon1 calculation

CoinAge x (tithe)^1/3
239813460.8751 x (7)^1/3 = 239813460.8751 x 1.91293118= 458,746,646.6916889
Cameroon-one = 2666.67
Total = 458,749,314.02 (from leaderboard)
Total =458,749,313.36(calculated manually)

5.   cli exec sendgscc
Code: [Select]
{
 "Command": "sendgscc"
}
cli exec analyze 167474 oncoapop1
Code: [Select]
{
  "Command": "analyze",
  "Totals": "CAMEROON-ONE|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|2667|0.00698158|oncoapop1|2668\nPOG|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|476191731|0.64515645|oncoapop1|479766771\n",
  "0": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 167444.00, TXID: 6f6a7d7a447e8788ccce7b5fea3a1bc0dfcb844698afdc2f9b3a1d7c38f4049d, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 130279453.0504, Donation: 0.0000, UserTotal: 2666.67",
  "1": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 167445.00, TXID: 58e8fc4456674bb74ac30f7854fb6d73cf84ad7a74786e55cb499560ef16699e, NickName: oncoapop1, Points: 458746647.36, Campaign: POG, CoinAge: 239813460.8751, Donation: 7.0000, UserTotal: 458749314.02",
  "2": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 167474.00, TXID: 88d8da4b97b2d11feb482dc5a026b619c4bde8c14a0379cbc9f662c9e557442c, NickName: oncoapop1, Points: 17445083.35, Campaign: POG, CoinAge: 9119556.1576, Donation: 7.0000, UserTotal: 476194397.37",
  "3": ""
}

6.   It appears that Cameroon-one tithe exhibits intended behaviour of not accumulating whereas POG does


7.   Fiat calculations (two commands instead of one previously)
Code: [Select]
cli exec dailysponsorshipcap
{
  "Command": "dailysponsorshipcap",
  "cap": 0.003489919543713683
}
cli exec price
{
  "Command": "price",
  "consensus_price": 0.000452465678,
  "qt_phase": 0,
  "qt_prior_phase": 0,
  "qt_future_phase": 0,
  "qt_enabled": true,
  "cur_price": "0.000437166531",
  "BBP/BTC": "0.000000045000",
  "BTC/USD": 9714.811799999999
}
1. $1.33 per child per day = $2.66 for two children =  2.66 / 0.000437 = 6,084 BBP
2. 950,000 (assumed daily superblock GSC contract value ) * 0.00349 (sponsorship cap) = 3,315 BBP per child (should be a bit less as I don’t know how QT affects the daily superblock – where can one find this out easily).
4.   POG calculations
a.   Total emission (from exec roi) = 537521.64
b.   My points = 476,191,731/479,766,770 = ‬0.99254 of POG
c.   0.99254 x 537521.64 = 533,516.2337349017
5.   My reward from leaderboard = 539289.730
6.   Therefore reward from Cameroon-One = 539289.730 - 533,516.2337349017 = 5,773 BBP

Sorry but it is still a bit off. I don’t know what I missed. Shouldn’t (6) =(1) = 2 * (2)?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 24, 2019, 02:58:43 pm
cli -version
BiblePay Core RPC client version 1.4.5.9

1.   Begin experiment: Not in leaderboard
Code: [Select]
{
  "Prominence": "Details",
  "Healing": "Diary Entries",
  "Prominence": "Totals"
}
2.   Tithe normally
Code: [Select]

{
  "Command": "sendgscc"
}
3.   Leaderboard true
Code: [Select]
{
  "Prominence": "Details",
  "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.70%",
  "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 458746647.00": "64.03%",
  "Healing": "Diary Entries",
  "Prominence": "Totals",
  "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 458749314.00, Reward: 535266.400": "64.730%"
}

3. exec analyze 167447 oncoapop1
[code]
{
  "Command": "analyze",
  "Totals": "CAMEROON-ONE|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|2667|0.00698158|oncoapop1|2668\nPOG|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|458746647|0.64029122|oncoapop1|465702655\n",
  "0": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 167444.00, TXID: 6f6a7d7a447e8788ccce7b5fea3a1bc0dfcb844698afdc2f9b3a1d7c38f4049d, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 130279453.0504, Donation: 0.0000, UserTotal: 2666.67",
  "1": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 167445.00, TXID: 58e8fc4456674bb74ac30f7854fb6d73cf84ad7a74786e55cb499560ef16699e, NickName: oncoapop1, Points: 458746647.36, Campaign: POG, CoinAge: 239813460.8751, Donation: 7.0000, UserTotal: 458749314.02",
  "2": ""
}

4. POG + Cameroon1 calculation

CoinAge x (tithe)^1/3
239813460.8751 x (7)^1/3 = 239813460.8751 x 1.91293118= 458,746,646.6916889
Cameroon-one = 2666.67
Total = 458,749,314.02 (from leaderboard)
Total =458,749,313.36(calculated manually)

5.   cli exec sendgscc
Code: [Select]
{
 "Command": "sendgscc"
}
cli exec analyze 167474 oncoapop1
Code: [Select]
{
  "Command": "analyze",
  "Totals": "CAMEROON-ONE|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|2667|0.00698158|oncoapop1|2668\nPOG|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|476191731|0.64515645|oncoapop1|479766771\n",
  "0": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 167444.00, TXID: 6f6a7d7a447e8788ccce7b5fea3a1bc0dfcb844698afdc2f9b3a1d7c38f4049d, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 130279453.0504, Donation: 0.0000, UserTotal: 2666.67",
  "1": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 167445.00, TXID: 58e8fc4456674bb74ac30f7854fb6d73cf84ad7a74786e55cb499560ef16699e, NickName: oncoapop1, Points: 458746647.36, Campaign: POG, CoinAge: 239813460.8751, Donation: 7.0000, UserTotal: 458749314.02",
  "2": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 167474.00, TXID: 88d8da4b97b2d11feb482dc5a026b619c4bde8c14a0379cbc9f662c9e557442c, NickName: oncoapop1, Points: 17445083.35, Campaign: POG, CoinAge: 9119556.1576, Donation: 7.0000, UserTotal: 476194397.37",
  "3": ""
}

6.   It appears that Cameroon-one tithe exhibits intended behaviour of not accumulating whereas POG does


7.   Fiat calculations (two commands instead of one previously)
Code: [Select]
cli exec dailysponsorshipcap
{
  "Command": "dailysponsorshipcap",
  "cap": 0.003489919543713683
}
cli exec price
{
  "Command": "price",
  "consensus_price": 0.000452465678,
  "qt_phase": 0,
  "qt_prior_phase": 0,
  "qt_future_phase": 0,
  "qt_enabled": true,
  "cur_price": "0.000437166531",
  "BBP/BTC": "0.000000045000",
  "BTC/USD": 9714.811799999999
}
1. $1.33 per child per day = $2.66 for two children =  2.66 / 0.000437 = 6,084 BBP
2. 950,000 (assumed daily superblock GSC contract value ) * 0.00349 (sponsorship cap) = 3,315 BBP per child (should be a bit less as I don’t know how QT affects the daily superblock – where can one find this out easily).
4.   POG calculations
a.   Total emission (from exec roi) = 537521.64
b.   My points = 476,191,731/479,766,770 = ‬0.99254 of POG
c.   0.99254 x 537521.64 = 533,516.2337349017
5.   My reward from leaderboard = 539289.730
6.   Therefore reward from Cameroon-One = 539289.730 - 533,516.2337349017 = 5,773 BBP

Sorry but it is still a bit off. I don’t know what I missed. Shouldn’t (6) =(1) = 2 * (2)?

Please dont hesitate to ask if I missed something.
1) It appears you are out of sync (and that is understandable considering our last releases issue), but know that we have a mandatory upgrade now anyway (addressing LLMQ changes and prod->testnet changes, and a liesure feature), so dont worry about it.

2) Very excellent calculations!  I believe you are spot on the POG and Cameroon!  And that makes me feel good about our regression testing, that we did not break pog by adding cameroon.

3)  Yes, $1.33 per day for one child, always equals 2,666 points for two kids because Cameroon points are denominated in USD cents (thats just a feature to make it easier for us to quickly see how many children a participant is sponsoring when we see the future leaderboard).  Not sure if you know this but if you go to the UI, and click Summary, you can see just Cameroon totals. 

4) To see the governance superblock daily limit , type 'exec getgovlimit height' where height must be a correct %205 height (you can find a height from exec health).  For this example im doing a getgovlimit 166685, and seeing the daily emission is 872356.  The daily emission Is affected by QT, but note that in TestNet we temporarily have QT turned Off so it is 0% - However, note in testnet, since its deflation is far ahead of Prod (we have a 19.5% annual deflation), its daily emission is down to 872356 *without* QT while prod is something like 930K or so.

5)  You can actually calculate the owed amounts by multiplying the prominence % Owed * the Superblock gov limit, but note that in the version you were running, its very hard to see that prominence level without going to the leaderboard UI.  I fixed this in the next release.  In the next release when you type 'exec analyze
 height nickname' you will see a Totals section with prominence % per row.  In your case above, your cameroon was .0069% - so you got 872356*.0069 = 6019 reward.  You got 872356 * .64515 for POG = 562800  (Note that I might be off a little from your leaderboard figure above because I used a different payment limit height) but  - thats Not a problem because the numbers you posted above - the prominence totals do add up to 65% (why 65%) its because 30% is set up for Cameroon in testnet (50% in prod), 5% for healing, and the remaining 65% for POG.  The reason you capped out at 65% is because of our Cameroon Cap.  And you were the only participant on the fork so that means we know for certain you added up to the entire contract (because .64515 + cameroons .0069) added up to the pog cap + capped child amount.

6) The child emission rate of 6019 or 3010 per child is good - its a reverse engineered exec price to arrive at the BBP * satoshi midpoint to recoup $1.33 per day.

7) Yes, on your question, the #6, should 1 = 2 * 2, Yes, but only if we know the actual daily emission rate for that height; From your figs I think you got it - being off only by 100 bbp, but to make sure, in the next version lets do another one and all you have to really do to see that is click in "Details" in the leaderboard UI (if you run QT?) and just ensure you have 6020 bbp for the kids and the remaining amount in POG rewards.   

 
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 24, 2019, 04:27:35 pm
Please dont hesitate to ask if I missed something.
1) It appears you are out of sync (and that is understandable considering our last releases issue), but know that we have a mandatory upgrade now anyway (addressing LLMQ changes and prod->testnet changes, and a liesure feature), so dont worry about it.

2) Very excellent calculations!  I believe you are spot on the POG and Cameroon!  And that makes me feel good about our regression testing, that we did not break pog by adding cameroon.

3)  Yes, $1.33 per day for one child, always equals 2,666 points for two kids because Cameroon points are denominated in USD cents (thats just a feature to make it easier for us to quickly see how many children a participant is sponsoring when we see the future leaderboard).  Not sure if you know this but if you go to the UI, and click Summary, you can see just Cameroon totals. 

4) To see the governance superblock daily limit , type 'exec getgovlimit height' where height must be a correct %205 height (you can find a height from exec health).  For this example im doing a getgovlimit 166685, and seeing the daily emission is 872356.  The daily emission Is affected by QT, but note that in TestNet we temporarily have QT turned Off so it is 0% - However, note in testnet, since its deflation is far ahead of Prod (we have a 19.5% annual deflation), its daily emission is down to 872356 *without* QT while prod is something like 930K or so.

5)  You can actually calculate the owed amounts by multiplying the prominence % Owed * the Superblock gov limit, but note that in the version you were running, its very hard to see that prominence level without going to the leaderboard UI.  I fixed this in the next release.  In the next release when you type 'exec analyze
 height nickname' you will see a Totals section with prominence % per row.  In your case above, your cameroon was .0069% - so you got 872356*.0069 = 6019 reward.  You got 872356 * .64515 for POG = 562800  (Note that I might be off a little from your leaderboard figure above because I used a different payment limit height) but  - thats Not a problem because the numbers you posted above - the prominence totals do add up to 65% (why 65%) its because 30% is set up for Cameroon in testnet (50% in prod), 5% for healing, and the remaining 65% for POG.  The reason you capped out at 65% is because of our Cameroon Cap.  And you were the only participant on the fork so that means we know for certain you added up to the entire contract (because .64515 + cameroons .0069) added up to the pog cap + capped child amount.

6) The child emission rate of 6019 or 3010 per child is good - its a reverse engineered exec price to arrive at the BBP * satoshi midpoint to recoup $1.33 per day.

7) Yes, on your question, the #6, should 1 = 2 * 2, Yes, but only if we know the actual daily emission rate for that height; From your figs I think you got it - being off only by 100 bbp, but to make sure, in the next version lets do another one and all you have to really do to see that is click in "Details" in the leaderboard UI (if you run QT?) and just ensure you have 6020 bbp for the kids and the remaining amount in POG rewards.   

Thank you, Rob, for the detailed explanation which is greatly appreciated.

As for #1 - I meant : the command supplied was leaderboard true which just showed that I stopped all POG/gsc (and hence did not appear on the leaderboard) to ensure a clean slate for the testing...
 
A fork? Hmm, I waited to get both wallets to sync for a week and I checked to see that this chain had all 7 DIP3 sancs. I was pretty sure this was the main testnet chain. Anyway, the reason I have not been able to contribute any sancs is that my old DIP3 sancs could never sync on the same chain as the other sancs or my wallets so I gave up trying...

If desperately needed, I will have to set one up from scratch after you have determined the current issues have been addressed and it is time to test again.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 24, 2019, 05:01:08 pm
BiblePay
1.4.6.0 - Mandatory Upgrade for TestNet

- Update LLMQ settings to account for our network settings
- Add one totals row per project to 'exec analyze height nickname' report to show total prominence % per project per user per day
- Merge Prod -> develop ratelimiter changes to guarantee gobject replication
- Add key 'changequantity=n' allowing the user to adjust the change output quantity
- Increment mandatory protocol version upgrade to force a mandatory upgrade on Sancs in testnet
- Add dip8 and chainlocks active flag to getblockchaininfo

** Mac and Linux still building **
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 24, 2019, 05:31:17 pm
Thank you, Rob, for the detailed explanation which is greatly appreciated.

As for #1 - I meant : the command supplied was leaderboard true which just showed that I stopped all POG/gsc (and hence did not appear on the leaderboard) to ensure a clean slate for the testing...
 
A fork? Hmm, I waited to get both wallets to sync for a week and I checked to see that this chain had all 7 DIP3 sancs. I was pretty sure this was the main testnet chain. Anyway, the reason I have not been able to contribute any sancs is that my old DIP3 sancs could never sync on the same chain as the other sancs or my wallets so I gave up trying...

If desperately needed, I will have to set one up from scratch after you have determined the current issues have been addressed and it is time to test again.

On #1, yes, thats what I thought you meant.

Well on my end, I did see 7 sancs, but I was under the impression only 3 were really online (due to the exec health vote level), and Ive been synchronized with the 3 I hosted - as compared to my local node.

Lets try this, could you please upgrade and see if you agree with this hash:
getblockhash 166762
630a5075****  ?


If not we will have to figure out where the bridge is broken.
Since we know we had gobject propagation problems in prior versions, the bridge should mend after everyone deletes the banlist.dat.

I could see MIPs children when he did his exec sendgscc, so Im still thinking you were on a fork.

As far as more sancs, as long as we have 1 more join in we will be fine - lets hope when everyone upgrades we see 4.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 24, 2019, 05:41:25 pm
On #1, yes, thats what I thought you meant.

Well on my end, I did see 7 sancs, but I was under the impression only 3 were really online (due to the exec health vote level), and Ive been synchronized with the 3 I hosted - as compared to my local node.

Lets try this, could you please upgrade and see if you agree with this hash:
getblockhash 166762
630a5075****  ?


If not we will have to figure out where the bridge is broken.
Since we know we had gobject propagation problems in prior versions, the bridge should mend after everyone deletes the banlist.dat.

I could see MIPs children when he did his exec sendgscc, so Im still thinking you were on a fork.

As far as more sancs, as long as we have 1 more join in we will be fine - lets hope when everyone upgrades we see 4.

Ok. I’ll upgrade and resync.

Before upgrade :
Block=168323
sa1-onc1.106.010=54875194410ba41d69b380a9537d9a77f22f0887ef2c1a807589ff412f87ac7f
sa2-onc1.239.200=54875194410ba41d69b380a9537d9a77f22f0887ef2c1a807589ff412f87ac7f
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 24, 2019, 05:44:13 pm
Ok. I’ll upgrade and resync.

Before upgrade :
Block=168323
sa1-onc1.106.010=54875194410ba41d69b380a9537d9a77f22f0887ef2c1a807589ff412f87ac7f
sa2-onc1.239.200=54875194410ba41d69b380a9537d9a77f22f0887ef2c1a807589ff412f87ac7f

Oh cool, well you actually agree with me (so the hash I posted in the last post should be correct for you also).

So the issue is we just need to see where your sendgscc went;  after you do a new one please post your new analyze height and Ill ensure I can see it.

EDIT:
Btw, you wont need to resync then.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 24, 2019, 09:38:24 pm
cli -version
BiblePay Core RPC client version 1.4.6.0

cli getblockhash 168736
c317c3de030df7c215f39b8568e9065b71a9e8e16af8d1fff5a09809e1ad18cd

leaderboard
Code: [Select]
{
 "Prominence": "Details",
 "CAMEROON-ONE: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.67%",
 "HEALING: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "HEALING: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 111670149.00": "0.00%",
 "POG: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 596289318.00": "65.00%",
 "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 0.00": "0.00%",
 "Healing": "Diary Entries",
 "oncoapop1": "Prayed for the salvation of the saints.",
 "Prominence": "Totals",
 "ALL: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 596289318.00, Reward: 537521.670": "65.000%",
 "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 111672816.00, Reward: 5553.030": "0.670%"
}

(my VPS is too small for GUI, so have to reply on cli, sorry)
cli exec analyze 168736 oncoapop1
Code: [Select]
{
 "Command": "analyze",
 "Campaign": "Totals",
 "0": "CAMEROON-ONE|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|2667|0.00671502|oncoapop1|2668",
 "1": "HEALING|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|111670149|0.00000000|oncoapop1|111670150",
 "2": "POG|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|0|0.00000000|oncoapop1|596289319",
 "3": "",
 "Campaign": "Points",
 "0": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 168733.00, TXID: fba1f5a89c130c8a1b20b822261c3bca93c732ced1b96c1e2d692c9f99bdec09, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 56159643.2778, Donation: 0.0000, UserTotal: 2666.67",
 "1": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: Prayed for the salvation of the saints., Height: 168733.00, TXID: 82758735ba9c7f2b63a477f15f1bdb98b245ae1e61e20ca1fef8b982e572af91, NickName: oncoapop1, Points: 111670149.47, Campaign: HEALING, CoinAge: 111670149.4654, Donation: 0.0000, UserTotal: 111672816.13",
 "2": ""
}






Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 24, 2019, 10:56:53 pm
cli -version
BiblePay Core RPC client version 1.4.6.0

cli getblockhash 168736
c317c3de030df7c215f39b8568e9065b71a9e8e16af8d1fff5a09809e1ad18cd

leaderboard
Code: [Select]
{
 "Prominence": "Details",
 "CAMEROON-ONE: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.67%",
 "HEALING: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "HEALING: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 111670149.00": "0.00%",
 "POG: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 596289318.00": "65.00%",
 "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 0.00": "0.00%",
 "Healing": "Diary Entries",
 "oncoapop1": "Prayed for the salvation of the saints.",
 "Prominence": "Totals",
 "ALL: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 596289318.00, Reward: 537521.670": "65.000%",
 "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 111672816.00, Reward: 5553.030": "0.670%"
}

(my VPS is too small for GUI, so have to reply on cli, sorry)
cli exec analyze 168736 oncoapop1
Code: [Select]
{
 "Command": "analyze",
 "Campaign": "Totals",
 "0": "CAMEROON-ONE|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|2667|0.00671502|oncoapop1|2668",
 "1": "HEALING|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|111670149|0.00000000|oncoapop1|111670150",
 "2": "POG|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|0|0.00000000|oncoapop1|596289319",
 "3": "",
 "Campaign": "Points",
 "0": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 168733.00, TXID: fba1f5a89c130c8a1b20b822261c3bca93c732ced1b96c1e2d692c9f99bdec09, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 56159643.2778, Donation: 0.0000, UserTotal: 2666.67",
 "1": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: Prayed for the salvation of the saints., Height: 168733.00, TXID: 82758735ba9c7f2b63a477f15f1bdb98b245ae1e61e20ca1fef8b982e572af91, NickName: oncoapop1, Points: 111670149.47, Campaign: HEALING, CoinAge: 111670149.4654, Donation: 0.0000, UserTotal: 111672816.13",
 "2": ""
}


Ok, I see you in the leaderboard now.  (See pic).  Both of us look OK.

Yes, I see your exec analyze 168736.  The issue earlier was my machine was stopped on a bad llmq block before your block so it was actually me that was out.  (I just checked in a new patch that allows us to sync from zero with llmq activated).

Looks like we still need another sanc, I think MIP had one, MIP is yours down?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 25, 2019, 08:38:24 am
As a side tip for anyone who is upgrading, remember you can do the 'exec reassesschains' if you end up at a lower height than us (it worked for me) due to LLMQ errors.

In the latest version I increased the LLMQ start height to 170,000.

Starting up LLMQ is much trickier (and dangerous) than I expected.

Since LLMQ drives chainlocks, the wallet is going to throw a bad block error, mark the block as dirty and put the wallet in a non recoverable state if it finds any block greater than 170,000 that is not in a quorum.

What this means is either the network has a lot of sancs, and a healthy quorum environment, or absolutely fails with a nightmare scenario.

This is obviously a decision Dash made to ensure there are no exceptions to the quorums once they are up and running. 

So in the current state of testnet, we would need to try to bring one more sanc on before 170,000 and see if a quorum forms, otherwise we need to keep increasing the LLMQ height.

What frightens me is if we start the quorums and then take down 70% of the nodes.  I think that means, we will need to regroup and bring the sancs back online. 

But from what I see, if lets say we lose those sancs VMs, and recreate them all, then the sigs will be new and the old quorums will be invalid (and I think that means a chain rollback).  We will cross that bridge when we come to it as our prod environment should be OK, as its always going to have for the most part more than 100 reliable sancs, so theoretically the quorums will never fail.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 26, 2019, 04:16:34 am
As a side tip for anyone who is upgrading, remember you can do the 'exec reassesschains' if you end up at a lower height than us (it worked for me) due to LLMQ errors.

In the latest version I increased the LLMQ start height to 170,000.

Starting up LLMQ is much trickier (and dangerous) than I expected.

Since LLMQ drives chainlocks, the wallet is going to throw a bad block error, mark the block as dirty and put the wallet in a non recoverable state if it finds any block greater than 170,000 that is not in a quorum.

What this means is either the network has a lot of sancs, and a healthy quorum environment, or absolutely fails with a nightmare scenario.

This is obviously a decision Dash made to ensure there are no exceptions to the quorums once they are up and running. 

So in the current state of testnet, we would need to try to bring one more sanc on before 170,000 and see if a quorum forms, otherwise we need to keep increasing the LLMQ height.

What frightens me is if we start the quorums and then take down 70% of the nodes.  I think that means, we will need to regroup and bring the sancs back online. 

But from what I see, if lets say we lose those sancs VMs, and recreate them all, then the sigs will be new and the old quorums will be invalid (and I think that means a chain rollback).  We will cross that bridge when we come to it as our prod environment should be OK, as its always going to have for the most part more than 100 reliable sancs, so theoretically the quorums will never fail.

Dear Rob,

Given your stressing the importance in testnet of the sancs testing of LLMQ (kindly remind me what this is again?), I have (surprisingly) resurrected one of my initial DIP3 sancs (just using old biblepay.conf and masternode.conf files left on the server WITHOUT the controlling wallet which I may have destroyed....), so I am hoping that it will be okay.

Let's test this to ensure, as far as we are able with a fraction of the network in testnet, we roll out a stable product in mainnet. Could you kindly help us to assist you in this by providing a checklist  (in simple layman's terms, please. Thanks  :) )  so that we can test specific aspects and report on.

Blessings,
oncoapop


Code: [Select]
{
  "outpoint": "51a7d0cdb93fb3377d274f1b448af3c260618eb23c145a52c6c2fc081192b4dc-1",
  "service": "45.62.239.200:40001",
  "proTxHash": "3fdfa35533185427856e07d7a966714d118c7434994b5d6a349c11558e79e290",
  "collateralHash": "51a7d0cdb93fb3377d274f1b448af3c260618eb23c145a52c6c2fc081192b4dc",
  "collateralIndex": 1,
  "dmnState": {
    "service": "45.62.239.200:40001",
    "registeredHeight": 65387,
    "lastPaidHeight": 171297,
    "PoSePenalty": 0,
    "PoSeRevivedHeight": -1,
    "PoSeBanHeight": -1,
    "revocationReason": 0,
    "ownerAddress": "yhDJCUZq19CVLiuDa4wEoY4PxWg17bZuTx",
    "votingAddress": "yhDJCUZq19CVLiuDa4wEoY4PxWg17bZuTx",
    "payoutAddress": "yRKdex8fFcDyjqx618Cz4hsQcQFjp55jRg",
    "pubKeyOperator": "05f58c1b79e898cf31a0375ded7a8e5bb6b0e5aacb48dc79f7c87e38eb0533bdf85c610cee5cf94b79c425c20f423cc4"
  },
  "state": "READY",
  "status": "Ready"
}

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 26, 2019, 04:29:24 am
Dear Rob,

Given your stressing the importance in testnet of the sancs testing of LLMQ (kindly remind me what this is again?), I have (surprisingly) resurrected one of my initial DIP3 sancs (just using old biblepay.conf and masternode.conf files left on the server WITHOUT the controlling wallet which I may have destroyed....), so I am hoping that it will be okay.

Let's test this to ensure, as far as we are able with a fraction of the network in testnet, we roll out a stable product in mainnet. Could you kindly help us to assist you in this by providing a checklist  (in simple layman's terms, please. Thanks  :) )  so that we can test specific aspects and report on.

Blessings,
oncoapop


Code: [Select]
{
  "outpoint": "51a7d0cdb93fb3377d274f1b448af3c260618eb23c145a52c6c2fc081192b4dc-1",
  "service": "45.62.239.200:40001",
  "proTxHash": "3fdfa35533185427856e07d7a966714d118c7434994b5d6a349c11558e79e290",
  "collateralHash": "51a7d0cdb93fb3377d274f1b448af3c260618eb23c145a52c6c2fc081192b4dc",
  "collateralIndex": 1,
  "dmnState": {
    "service": "45.62.239.200:40001",
    "registeredHeight": 65387,
    "lastPaidHeight": 171297,
    "PoSePenalty": 0,
    "PoSeRevivedHeight": -1,
    "PoSeBanHeight": -1,
    "revocationReason": 0,
    "ownerAddress": "yhDJCUZq19CVLiuDa4wEoY4PxWg17bZuTx",
    "votingAddress": "yhDJCUZq19CVLiuDa4wEoY4PxWg17bZuTx",
    "payoutAddress": "yRKdex8fFcDyjqx618Cz4hsQcQFjp55jRg",
    "pubKeyOperator": "05f58c1b79e898cf31a0375ded7a8e5bb6b0e5aacb48dc79f7c87e38eb0533bdf85c610cee5cf94b79c425c20f423cc4"
  },
  "state": "READY",
  "status": "Ready"
}

Again I notice that all the sancs appear to be "valid" although I know that only one of my sancs (45.62.239.200) is online and the other (64.180.194.238) is  not (see below). Would this affect the quorum if we have zombie sancs?

Code: [Select]
telnet 45.62.239.200 40001
Trying 45.62.239.200...
Connected to 45.62.239.200.

telnet 64.180.194.238 40001
Trying 64.180.194.238...
telnet: Unable to connect to remote host: Connection refused
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 27, 2019, 10:42:27 am
Again I notice that all the sancs appear to be "valid" although I know that only one of my sancs (45.62.239.200) is online and the other (64.180.194.238) is  not (see below). Would this affect the quorum if we have zombie sancs?

Code: [Select]
telnet 45.62.239.200 40001
Trying 45.62.239.200...
Connected to 45.62.239.200.

telnet 64.180.194.238 40001
Trying 64.180.194.238...
telnet: Unable to connect to remote host: Connection refused

Well actually POSE gets enabled in tandem with LLMQ (long living masternode quorums).  So technically, when the 4 good sancs start forming quorums, they will start d-dossing the other sancs.  This will cause the other sancs POSE scores to increase.  Once they move to 100%, they will be banned and wont get paid.

The reason you see 0 for every sancs pose score is the LLMQs havent been forming yet.
I did ensure both the Dip and the LLMQ height were activated in testnet; so next I need to do some deeper analysis; Ill look today.

Let me know if you need more info on LLMQ other than this; you can read this and this should give you most of the info:
https://blog.dash.org/mitigating-51-attacks-with-llmq-based-chainlocks-7266aa648ec9

This too:
https://github.com/dashpay/dips/blob/master/dip-0006.md
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 27, 2019, 10:46:48 am
Dear Rob,

Given your stressing the importance in testnet of the sancs testing of LLMQ (kindly remind me what this is again?), I have (surprisingly) resurrected one of my initial DIP3 sancs (just using old biblepay.conf and masternode.conf files left on the server WITHOUT the controlling wallet which I may have destroyed....), so I am hoping that it will be okay.

Let's test this to ensure, as far as we are able with a fraction of the network in testnet, we roll out a stable product in mainnet. Could you kindly help us to assist you in this by providing a checklist  (in simple layman's terms, please. Thanks  :) )  so that we can test specific aspects and report on.

Blessings,
oncoapop


Code: [Select]
{
  "outpoint": "51a7d0cdb93fb3377d274f1b448af3c260618eb23c145a52c6c2fc081192b4dc-1",
  "service": "45.62.239.200:40001",
  "proTxHash": "3fdfa35533185427856e07d7a966714d118c7434994b5d6a349c11558e79e290",
  "collateralHash": "51a7d0cdb93fb3377d274f1b448af3c260618eb23c145a52c6c2fc081192b4dc",
  "collateralIndex": 1,
  "dmnState": {
    "service": "45.62.239.200:40001",
    "registeredHeight": 65387,
    "lastPaidHeight": 171297,
    "PoSePenalty": 0,
    "PoSeRevivedHeight": -1,
    "PoSeBanHeight": -1,
    "revocationReason": 0,
    "ownerAddress": "yhDJCUZq19CVLiuDa4wEoY4PxWg17bZuTx",
    "votingAddress": "yhDJCUZq19CVLiuDa4wEoY4PxWg17bZuTx",
    "payoutAddress": "yRKdex8fFcDyjqx618Cz4hsQcQFjp55jRg",
    "pubKeyOperator": "05f58c1b79e898cf31a0375ded7a8e5bb6b0e5aacb48dc79f7c87e38eb0533bdf85c610cee5cf94b79c425c20f423cc4"
  },
  "state": "READY",
  "status": "Ready"
}

Great on adding another sanc!

Yes, I will make a list; but know that I have no intention of moving towards prod til after we fully believe testnet and chainlocks are tested in and out :).

There are so many things we need to test after Prod transitions to deterministic sancs in 0.14 against prod.  We definitely need a list, and it will make me feel better when we not only test chainlocks in testnet, but LLMQs against the deterministic sancs in prod.

We will see the GSC gov data and votes in testnet after prod upgrades to determistic.  LLMQ will also be enabled in .13 in prod, but won't be enforced like it is in testnet.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 27, 2019, 02:45:50 pm
Again I notice that all the sancs appear to be "valid" although I know that only one of my sancs (45.62.239.200) is online and the other (64.180.194.238) is  not (see below). Would this affect the quorum if we have zombie sancs?

Code: [Select]
telnet 45.62.239.200 40001
Trying 45.62.239.200...
Connected to 45.62.239.200.

telnet 64.180.194.238 40001
Trying 64.180.194.238...
telnet: Unable to connect to remote host: Connection refused

So I took at look at the "bottleneck" in TestNet (with POSE not working) - IE in laymans terms, Sancs are not banning each other.
Also we have an issue in TestNet where LLMQs are failing.

So, the problem is our LLMQ in TestNet is pointing to params that are for the wrong quorum.  (I did update them at one point, and triple checked them, but Dash's testnet is bigger than ours, and that led me to believe we were using RegTest in TestNet and they were using 5_60 in TestNet but in reality, Dash was requiring 7 masternodes in TestNet minimum, and our RegTest params were only being used in RegTest LOL).  So thats good this was discovered and makes sense, and explains why our LLMQ quorums have all failed so far.

So, we will need a mandatory in TestNet (I need to force a protocol version increase) in order to release this next test.

So MIP, lets build a new testnet release.

We will announce asap.

EDIT:  Please remember to erase your debug.log before starting the new version.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 28, 2019, 02:26:45 pm
BiblePay
1.4.6.1-Mandatory Upgrade for TestNet

- Bump protocol version up to 70740 for Sancs (to force upgrade)
- Modify minimum LLMQ for testnet to be a size of 3 with a threshhold of 2
- Use Testnet LLMQ for instantsend and for ChainLocks
- Increase LLMQ height to 175000 in testnet
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 28, 2019, 06:56:44 pm
Great news!

It looks like the latest version is POSE banning people!

POSE, here we come!

EDIT:  Wait, one of my own sancs got POSE banned.
Guys, please ensure your Masternodeblsprivkey is set correctly btw.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 28, 2019, 07:35:41 pm
Great news!

It looks like the latest version is POSE banning people!

POSE, here we come!

EDIT:  Wait, one of my own sancs got POSE banned.
Guys, please ensure your Masternodeblsprivkey is set correctly btw.

In my case it was not the masternodeblsprivkey (but that is still the most common cause of POSE bans).
In my case I had the externalip= set (to the correct IP) but for some reason the other nodes didnt like that, so I recreated my sanc. (without an externalip).

Now Im back in the list with 0 pose ban.

Im interested in seeing who else gets POSE banned.

LLMQ is enabled now.

MIP do you have a sanc also?  I know Oncoapop just added one so we should have 5 total if MIP has one.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on July 29, 2019, 03:57:34 pm
In my case it was not the masternodeblsprivkey (but that is still the most common cause of POSE bans).
In my case I had the externalip= set (to the correct IP) but for some reason the other nodes didnt like that, so I recreated my sanc. (without an externalip).

Now Im back in the list with 0 pose ban.

Im interested in seeing who else gets POSE banned.

LLMQ is enabled now.

MIP do you have a sanc also?  I know Oncoapop just added one so we should have 5 total if MIP has one.

I had one, I just updated but I think I may be in the wrong chain, I will resync.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 29, 2019, 03:59:02 pm
I had one, I just updated but I think I may be in the wrong chain, I will resync.

Im writing a script now to do a one-click sync, but it wont be ready til next version as I have to upload a file into github.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 30, 2019, 02:06:51 pm
** Low hassle Syncing from Zero **

As our blockchain gets bigger it will be useful for us to release utilities to allow one click syncing from zero.
This first version is only for testnet and linux.  Later, I will extend this to windows and prod.

Is anyone interested in testing?  I just tested this from my ubuntu remote box and I was able to sync in a couple minutes.

I will check this into github later, but for now, let me give manual instructions to use the script:

From your linux box:

cd ~/biblepay-evolution
(This is where your source starts, ie /src is one folder down)
wget biblepay.org/syncblocks_testnet.sh
chmod 777 syncblocks_testnet.sh

Now to get in sync for TestNet only, the script automatically deletes just the data files (dont worry, it wont delete anything else), then it pulls down the snapshot of the blocks gzipped and unzips them into the correct places (including the llmq and all necessary governance files), then its up to you re-launch the wallet.  The script does close biblepay as long as your machine supports pkill.

To sync from 0 type:
./syncblocks_testnet.sh

EDIT:

I just created a windows version and tested it on windows 7 and it works.  Will check-in during the next Develop release.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 30, 2019, 05:07:37 pm
So can we get a little update from everyone on testnet, do you all agree:


getblockhash 180650
28383ec96296dbee95f45a0240cae97ef8ef06ff8fd3fe4e90552eb2cbe72d6e

Id like to see all 5 of our sancs in agreement before we talk about testing chainlocks.
I see my 3 non-pose banned sancs are in agreement.

MIP, Oncoapop we could use feedback - and anyone else that wants to test chainlocks.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 30, 2019, 07:17:37 pm
So can we get a little update from everyone on testnet, do you all agree:


getblockhash 180650
28383ec96296dbee95f45a0240cae97ef8ef06ff8fd3fe4e90552eb2cbe72d6e

Id like to see all 5 of our sancs in agreement before we talk about testing chainlocks.
I see my 3 non-pose banned sancs are in agreement.

MIP, Oncoapop we could use feedback - and anyone else that wants to test chainlocks.
Dear Rob,

I just have three VPS running in TESTNET. I did have one sanc but it is now banned, I have no idea how to get it unbanned. I restarted it to no avail. How does one get banned, other than not running bbp daemon?

Code: [Select]
{
 "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
 "service": "45.62.239.200:40001",
 "state": "POSE_BANNED",
 "status": "Masternode was PoSe banned"
}

The VPS is up and running and port appears to be open
Code: [Select]
telnet 45.62.239.200 40001
Trying 45.62.239.200...
Connected to sanc2.myseqtools.com<http://sanc2.myseqtools.com>.

mnsync status
{
 "AssetID": 999,
 "AssetName": "MASTERNODE_SYNC_FINISHED",
 "AssetStartTime": 1564531134,
 "Attempt": 0,
 "IsBlockchainSynced": true,
 "IsSynced": true,
 "IsFailed": false
}

If you want to check my machines, you can see the automatically polled hashes of my three machines at any time on:
http://oncoapop.sdf.org/biblepaytest/testnet_chainstate.shtml

They are pretty puny VPS  so one or more may be offline syncing or updating…

Cheers,
Oncoapop


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 30, 2019, 08:31:35 pm
Dear Rob,

I just have three VPS running in TESTNET. I did have one sanc but it is now banned, I have no idea how to get it unbanned. I restarted it to no avail. How does one get banned, other than not running bbp daemon?

Code: [Select]
{
 "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
 "service": "45.62.239.200:40001",
 "state": "POSE_BANNED",
 "status": "Masternode was PoSe banned"
}

The VPS is up and running and port appears to be open
Code: [Select]
telnet 45.62.239.200 40001
Trying 45.62.239.200...
Connected to sanc2.myseqtools.com<http://sanc2.myseqtools.com>.

mnsync status
{
 "AssetID": 999,
 "AssetName": "MASTERNODE_SYNC_FINISHED",
 "AssetStartTime": 1564531134,
 "Attempt": 0,
 "IsBlockchainSynced": true,
 "IsSynced": true,
 "IsFailed": false
}

If you want to check my machines, you can see the automatically polled hashes of my three machines at any time on:
http://oncoapop.sdf.org/biblepaytest/testnet_chainstate.shtml

They are pretty puny VPS  so one or more may be offline syncing or updating…

Cheers,
Oncoapop

Hi Oncoa,

Nice hashes, so it looks like we are in agreement on that block hash (for your 3) plus mine.

As far as getting pose banned, you can get banned if:  Your masternodeblsprivkey does not match your deterministic.conf private key, or if you transmitted the same IP on more than one pro-tx, or if you are using the 'externalip=' setting in your wallet, or if your node is out of sync and acting strange in the quorums.  You would have to defer to the dash docs I pasted above for the rest of the reasons (as I am not familiar with the others yet).

If your not sure after reading this, I have found it is very easy to do this to recover:

Spent your collateral Tx in the controller wallet
Create a new public key for a new sanc
Create a new legacy sanc using the new address
Perform the upgradesanc command on it

I did that and Im chugging fine.

You can use the same address as long as you spend the old sanc funds first.  (Unlock them to spend them, spend them, then spend a new amount for the new sanc).


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 31, 2019, 12:39:39 pm
Hi Oncoa,

Nice hashes, so it looks like we are in agreement on that block hash (for your 3) plus mine.

As far as getting pose banned, you can get banned if:  Your masternodeblsprivkey does not match your deterministic.conf private key, or if you transmitted the same IP on more than one pro-tx, or if you are using the 'externalip=' setting in your wallet, or if your node is out of sync and acting strange in the quorums.  You would have to defer to the dash docs I pasted above for the rest of the reasons (as I am not familiar with the others yet).

If your not sure after reading this, I have found it is very easy to do this to recover:

Spent your collateral Tx in the controller wallet
Create a new public key for a new sanc
Create a new legacy sanc using the new address
Perform the upgradesanc command on it

I did that and Im chugging fine.

You can use the same address as long as you spend the old sanc funds first.  (Unlock them to spend them, spend them, then spend a new amount for the new sanc).

This would only happen in testnet but i lost / destroyed my controller wallet with my VPS and hence the collateral is locked and hence I cannot recreate the sancs using the same IP as you mentioned without spending the collateral which is not possible without the wallet!

I’ll have to destroy the VPS and recreate it with new A fresh IP and start from scratch. This might take awhile... sorry.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 31, 2019, 01:34:26 pm
This would only happen in testnet but i lost / destroyed my controller wallet with my VPS and hence the collateral is locked and hence I cannot recreate the sancs using the same IP as you mentioned without spending the collateral which is not possible without the wallet!

I’ll have to destroy the VPS and recreate it with new A fresh IP and start from scratch. This might take awhile... sorry.

Oh ok, yeah you can't spend the collateral then, so you cant free that node the easy way, right.

Well, anyway, the other way to do it is if you have the deterministic.conf file (this has the bls private and public key in it and the original pro-tx-txid), you could send a  ProUpServTx, (because sending a new pro-register-tx with the same IP results in bad-protx-dup-key error), but you could only do this if you had all the pieces saved from deterministic.conf (proTxHash, blsPrivKey) - see this section for future reference :  https://docs.dash.org/en/stable/masternodes/maintenance.html#updating-masternode-information


Well anyway I hope you have a Vultr Snapshot then you can rebuild without all that work.  Good luck.


PS: Can you please try the quick sync from zero when you rebuild so we can test that?


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 31, 2019, 01:37:02 pm
I just updated the OP with "low hassle sync from zero". 

I also got windows to sync with this method last night, so it will be trivial to make a prod snapshot soon.


Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 31, 2019, 06:26:12 pm
Oh ok, yeah you can't spend the collateral then, so you cant free that node the easy way, right.

Well, anyway, the other way to do it is if you have the deterministic.conf file (this has the bls private and public key in it and the original pro-tx-txid), you could send a  ProUpServTx, (because sending a new pro-register-tx with the same IP results in bad-protx-dup-key error), but you could only do this if you had all the pieces saved from deterministic.conf (proTxHash, blsPrivKey) - see this section for future reference :  https://docs.dash.org/en/stable/masternodes/maintenance.html#updating-masternode-information


Well anyway I hope you have a Vultr Snapshot then you can rebuild without all that work.  Good luck.


PS: Can you please try the quick sync from zero when you rebuild so we can test that?

Set it up using the binaries from MIP and the quick sync script and it was fast and effortless! Used the Dash method from scratch (bit more complicated) and here it is...
 
Code: [Select]
"33ff087061fad94af7e4f1f73ff56af47f9b34e802cd845f5cf765b13944d453-1": {
   "proTxHash": "520ebc4e8fb36d335e89d3527c88e0096bb605983efbd339f78d17be12ce453e",
   "address": "104.167.113.181:40001",
   "payee": "yXhRHuA2YsV44K5VZJyQSxZurQ8s7diKbq",
   "status": "ENABLED",
   "posescore": 100,
   "posescoretries": 0,
   "posescoresuccesscount": 0,
   "lastpaidtime": 1564615177,
   "lastpaidblock": 182751,
   "owneraddress": "ygXsP7NRxDJtKKqRc2i1JXvxKZmXysYf76",
   "votingaddress": "ya5TqeZC7GRbibSzT8jbfHCLEQNTKT6LDL",
   "collateraladdress": "ydbZ7ppEEbq28Awyt2iQXTnM3JSn5fxKHF",
   "pubkeyoperator": "90856729abbe57866ec136e1505b59bf2fb5c399e04581df8264ba0ce49709cccd8c3e74c45ea1815e71572d602110c0"
 }
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 31, 2019, 06:32:57 pm
Set it up using the binaries from MIP and the quick sync script and it was fast and effortless! Used the Dash method from scratch (bit more complicated) and here it is...
 
Code: [Select]
"33ff087061fad94af7e4f1f73ff56af47f9b34e802cd845f5cf765b13944d453-1": {
   "proTxHash": "520ebc4e8fb36d335e89d3527c88e0096bb605983efbd339f78d17be12ce453e",
   "address": "104.167.113.181:40001",
   "payee": "yXhRHuA2YsV44K5VZJyQSxZurQ8s7diKbq",
   "status": "ENABLED",
   "posescore": 100,
   "posescoretries": 0,
   "posescoresuccesscount": 0,
   "lastpaidtime": 1564615177,
   "lastpaidblock": 182751,
   "owneraddress": "ygXsP7NRxDJtKKqRc2i1JXvxKZmXysYf76",
   "votingaddress": "ya5TqeZC7GRbibSzT8jbfHCLEQNTKT6LDL",
   "collateraladdress": "ydbZ7ppEEbq28Awyt2iQXTnM3JSn5fxKHF",
   "pubkeyoperator": "90856729abbe57866ec136e1505b59bf2fb5c399e04581df8264ba0ce49709cccd8c3e74c45ea1815e71572d602110c0"
 }

Thats awesome.  I see .181 in my sanc list now also, with 0 POSE.
Just a guess, but maybe it was your masternodeblsprivkey on the old one, not matching?  In both of my cases it was using externalip=.  I found after I recreated without that, they stay up. 

Yes, good to know you were able to use the Dash method.  The pro for the dash method is you have more control over the operator and voting keys (which, we can expose in the future in our upgradesanc command, for more versatility).  The con is you have to remember to save those private keys in a file by yourself.  (In the case of a person who has a lot of sancs, the deterministic.conf might be convenient.  In my case, the deterministic was more useful for me to write a monitoring program to manage the sancs later - I need to loop through them and control them, etc.)

Great, we have 5 sancs now enabled!  We can start testing chainlocks pretty soon.
MIP, is yours up?

Have I forgotten to answer any questions about .14 other than making a test-list?

Btw, how did you lose your testnet controller wallet, was it a rabid animal, or a mad family member?

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on July 31, 2019, 08:42:40 pm
Thats awesome.  I see .181 in my sanc list now also, with 0 POSE.
Just a guess, but maybe it was your masternodeblsprivkey on the old one, not matching?  In both of my cases it was using externalip=.  I found after I recreated without that, they stay up. 

Yes, good to know you were able to use the Dash method.  The pro for the dash method is you have more control over the operator and voting keys (which, we can expose in the future in our upgradesanc command, for more versatility).  The con is you have to remember to save those private keys in a file by yourself.  (In the case of a person who has a lot of sancs, the deterministic.conf might be convenient.  In my case, the deterministic was more useful for me to write a monitoring program to manage the sancs later - I need to loop through them and control them, etc.)

Great, we have 5 sancs now enabled!  We can start testing chainlocks pretty soon.
MIP, is yours up?

Have I forgotten to answer any questions about .14 other than making a test-list?

Btw, how did you lose your testnet controller wallet, was it a rabid animal, or a mad family member?

Hmm, my sanc has the external IP in the biblepay.conf:

Code: [Select]
addnode=testnet.biblepay.org
addnode=dns1.biblepay.org
addnode=dns2.biblepay.org
addnode=dns3.biblepay.org

rpcuser=XXX
rpcpassword=XXX
rpcallowip=127.0.0.1
rpcport=9998
daemon=1
listen=1
server=1
daemon=1
externalip=104.167.113.181
maxconnections=256
masternode=1
masternodeblsprivkey=XXXX

Not that exciting, I’m afraid. I thought each time in testnet we start from scratch so I didn’t pay much attention to the wallets. Anyway, I managed to resurrect the 239.200 as the VPS was still around.
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on July 31, 2019, 09:04:53 pm
Hmm, my sanc has the external IP in the biblepay.conf:

Code: [Select]
addnode=testnet.biblepay.org
addnode=dns1.biblepay.org
addnode=dns2.biblepay.org
addnode=dns3.biblepay.org

rpcuser=XXX
rpcpassword=XXX
rpcallowip=127.0.0.1
rpcport=9998
daemon=1
listen=1
server=1
daemon=1
externalip=104.167.113.181
maxconnections=256
masternode=1
masternodeblsprivkey=XXXX

Not that exciting, I’m afraid. I thought each time in testnet we start from scratch so I didn’t pay much attention to the wallets. Anyway, I managed to resurrect the 239.200 as the VPS was still around.

Oh good on the reason :), haha, OK.
Yes, I remember the two I had trouble with had the port in there also and yours does not.
It makes me think you could comment out yours, as it might not be used.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on August 17, 2019, 08:38:21 am
** TestNet Update **

Just to give everyone an update as to what is going on:
Of course our TestNet testing is vital and is not being deprioritized by any means.

We still want to shoot for roughly an end of October timeline to at least have our next codebase ready for deployment (in case something accelerates the need for the release, as its important to be safe and on the ball).

The reason for the recent lack of posts is I've been in 'programming hermit' mode working on some of the promised features for EOQ 3.  For example BIPFS (BiblePay IPFS).

I will be posting a wiki very soon explaining all of this.

The schedule is on-track for an on-time release, so I feel confident we can begin testing chainlocks very soon and get back to more testnet as well.

Some of the code in BIPFS requires some code changes in the core in testnet btw (leisure changes).

Note that Dash recently had to tweak .14 in Prod due to some hackers spamming prod transactions.  We will pull these things in ASAP and ensure we are up to date.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on September 03, 2019, 03:01:25 pm
1.4.6.2 - Mandatory Upgrade for TestNet

- Merge in Prod changes up to 1.4.4.6
- Merge in Reindex fix (MIP)
- Add feature to slow mining of empty blocks in TestNet only
- Add feature to upload nested folder into BIPFS
- Add transparent background image for windows toolbar
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on September 03, 2019, 04:07:18 pm
Let me know when our sancs have upgraded, because I would like to set the spork to slow the testnet chain down to keep the testnet chain from generating thousands of empty one minute blocks (causing longer sync times in the future).

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on September 03, 2019, 04:21:38 pm
Let me know when our sancs have upgraded, because I would like to set the spork to slow the testnet chain down to keep the testnet chain from generating thousands of empty one minute blocks (causing longer sync times in the future).

I believe Im the only 2 sancs left; MIP & Oncoapop are you guys still participating?

Jaap said he would, but we havent heard back from him after that.  I havent seen Togo here either despite coming back on the payroll.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: MIP on September 04, 2019, 10:47:50 am
I believe Im the only 2 sancs left; MIP & Oncoapop are you guys still participating?

Jaap said he would, but we havent heard back from him after that.  I havent seen Togo here either despite coming back on the payroll.

I switched off mine in the Vultr VPS. I made a snapshot so maybe I can take it back again.

Apart from that, what else do you need from me to test?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on September 04, 2019, 04:40:58 pm
I believe Im the only 2 sancs left; MIP & Oncoapop are you guys still participating?

Jaap said he would, but we havent heard back from him after that.  I havent seen Togo here either despite coming back on the payroll.

I have the following machines on testnet but all my sancs have been pose banned so i need to reactivate them but this back-to-school week is a bit busy for me.

http://oncoapop.sdf.org/biblepaytest/testnet_chainstate.shtml
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on September 05, 2019, 09:10:14 am
I have the following machines on testnet but all my sancs have been pose banned so i need to reactivate them but this back-to-school week is a bit busy for me.

http://oncoapop.sdf.org/biblepaytest/testnet_chainstate.shtml

Thanks guys!

Yeah, one of my 3 was pose banned too.  I have been deliberately waiting to see if it revives by itself.

As the Dash-Evo code hints at an automatic revival process; but - when I read about people who were POSE banned, they generally recreate their nodes.  But that doesnt make too much sense to me, because there is a strict control on not being able to re-use the same IP.

I have one well known working method to undo a POSE ban - but its like using a cannon - you can spend the output and recreate the sanc using upgradesanc - and that is allowed - because the network sees it as spent and undoes the lock on it first - and allows recreation.

Before I recreate my third sanc, let me do some more expirimentation.

Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on September 05, 2019, 09:13:39 am
I switched off mine in the Vultr VPS. I made a snapshot so maybe I can take it back again.

Apart from that, what else do you need from me to test?

We need to have a reliable network of sanctuaries online to test LLMQs and Chainlocks. 




Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: fenin0018 on September 05, 2019, 10:08:33 am
Hi everyone! I'm having a problem that I think It was been talked here but I can't get fix.
I'm solo mining and the issue is that just after mining a block, my wallet goes into invlaid ABN error and stops mining using 0%CPU. I dont know it wallet stops mining after mining one block for a period of time but it has been 17hours since ABN weight error and I have more than 125K o balance...
Could please someone clarify this matter to me.
Thanks!
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: fenin0018 on September 05, 2019, 10:13:04 am
Hi everyone! I'm having a problem that I think It was been talked here but I can't get fix.
I'm solo mining and the issue is that just after mining a block, my wallet goes into invlaid ABN error and stops mining using 0%CPU. I dont know it wallet stops mining after mining one block for a period of time but it has been 17hours since ABN weight error and I have more than 125K o balance...
Could please someone clarify this matter to me.
Thanks!

"blocks": 142961,
  "currentblocksize": 1342,
  "currentblocktx": 1,
  "difficulty": 2441.634648969612,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 32,
  "networkhashps": 490250.214518697,
  "hashps": 0,
  "minerstarttime": "09-05-2019 14:56:46",
  "hashcounter": 0,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "poolinfo5": "Internal ABN: Invalid 1567696257; ",
  "abninfo": "No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; ",
  "gsc_errors": "low abn weight 0",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 125000
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on September 05, 2019, 11:33:12 am
Thanks guys!

Yeah, one of my 3 was pose banned too.  I have been deliberately waiting to see if it revives by itself.

As the Dash-Evo code hints at an automatic revival process; but - when I read about people who were POSE banned, they generally recreate their nodes.  But that doesnt make too much sense to me, because there is a strict control on not being able to re-use the same IP.

I have one well known working method to undo a POSE ban - but its like using a cannon - you can spend the output and recreate the sanc using upgradesanc - and that is allowed - because the network sees it as spent and undoes the lock on it first - and allows recreation.

Before I recreate my third sanc, let me do some more expirimentation.

Thank you. Initially, the testnet sancs were enabled even when the entire VPS was off for extended periods of time; now when they temporarily drop connection, all of the sancs appear to be banned and none appear to gave recovered without intervention.

 sanc count
{
  "total": 6,
  "enabled": 0
}

Am I on the same chain as you, as all the sancs on this testnet chain appear banned?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: oncoapop on September 05, 2019, 12:23:41 pm
Dear Rob,

Based on published data Ref: http://wiki.biblepay.org/Emission_Schedule
And the approx current output, I have calculated the approx BBP allocation based on current QT, can you please confirm? Thank you.

Planned emission   

                %                BBP
Total monthly    51,914,467.00
Per day                  1,730,482.23
Curr QT    0.6        1,038,289.34

Sanc          0.25         259,572.34
PoBHv2    0.25         259,572.34
SB(?)         0.10         103,828.93
GSC           0.40          415,315.74

GSC breakdown:
POG            0.475     197,274.97
POOM        0.475     197,274.97
HEALING    0.050      20,765.79
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: fenin0018 on September 06, 2019, 04:05:30 pm
"blocks": 142961,
  "currentblocksize": 1342,
  "currentblocktx": 1,
  "difficulty": 2441.634648969612,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 32,
  "networkhashps": 490250.214518697,
  "hashps": 0,
  "minerstarttime": "09-05-2019 14:56:46",
  "hashcounter": 0,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "poolinfo5": "Internal ABN: Invalid 1567696257; ",
  "abninfo": "No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696336; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; No block to mine...  Please wait... 1567696335; ",
  "gsc_errors": "low abn weight 0",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 125000

Does anyone understand this problem?
Title: Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
Post by: Rob Andrews on September 15, 2019, 01:15:44 pm
Thank you. Initially, the testnet sancs were enabled even when the entire VPS was off for extended periods of time; now when they temporarily drop connection, all of the sancs appear to be banned and none appear to gave recovered without intervention.

 sanc count