TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

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

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.

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!

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.

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).

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.

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)

bbpd@testnet:~/.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"
}

bbpd@testnet:~/.biblepaycore/testnet3$ cli getblockcount
2685
bbpd@testnet:~/.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>"
}

bbpd@testnet:~$ cli getrawtransaction 3f386f615e535e25135b41ac85ff8b3ce7396fd0b0437954bc987887b6d354c4
010000000104fe28f332170dd410eff63539bb631a156ea96d011a69a5e5d741624e58a4d6010000006a4730440220141fb61848dc814528921322f9320485de43a29b11bed4cc089df8438df5970002204f25e13b8aa614b96a541dab8e344d830a3338d3e2b9aa66e21235676931ed92012102ab6ec2ed3d0dcdf40bde8cb2d3d9515af77ff8cde5d168cc582b683d92876d47feffffff0200e1f505000000001976a914529b518f59a0f45beb1e15541983bb74eed9715c88acfd29013c4d543e43504b3c2f4d543e3c4d4b3e5959503659524a504f4252545044514f5748544647504d47384e4e454a575942534f3c2f4d4b3e3c4d563e7959703679726a706f6252545064716f7748544647704d47386e6e454a775942536f7c6f6e636f61706f707c313535333535303433377c376637396131386534346162346334643534323431306331376530383036343562336662353034373433646231663532313532396639303534653932336233377c4878503450633471633479505a71714e794751666f69566e6546732f362f6e50336b545a76493755737051354357425457434c335a443449596e664c765237302f4c2f674c2b4a786a4846447572666d47503361474a343d3c2f4d563e3c4e4f4e43453e313535333535303433373c2f4e4f4e43453e684452671cfa00001976a9149d2c3d461028c79253c038fb4dc62471ad86503288ac007a0a0000

bbpd@testnet:~$ 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
}

Associate cpk to nickname. Need to wait for 5 (?) confimations and can only do it once.

bbpd@testnet:~/.biblepaycore/testnet3$ cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": true
}

bbpd@testnet:~/.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."
}

bbpd@testnet:~$ cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": false,
  "Error": "ALREADY_IN_CHAIN"
}
.....
Try to associate with a new nickname - cannot.

bbpd@testnet:~/biblepay-evolution$ cli exec cpk new
{
  "Command": "cpk",
  "Results": false,
  "Error": "ALREADY_IN_CHAIN"
}

Associate cpk to nickname. Need to wait for 5 (?) confimations and can only do it once.

bbpd@testnet:~/.biblepaycore/testnet3$ cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": true
}

bbpd@testnet:~/.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."
}

bbpd@testnet:~$ cli exec cpk oncoapop
{
  "Command": "cpk",
  "Results": false,
  "Error": "ALREADY_IN_CHAIN"
}
.....
Try to associate with a new nickname - cannot.

bbpd@testnet:~/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.

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.

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?

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).

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?

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.