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

[jaapgvk]

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:

bible@bible-GA-A55M-DS2:~/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:

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?

[Rob Andrews]

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)

[Rob Andrews]

Note:  A release is coming in approx 45 mins.

[Rob Andrews]

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

[Rob Andrews]

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.

[jaapgvk]

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

[orbis]

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

[oncoapop]

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
}

[orbis]

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.

[togoshigekata]

I cleaned wallet and reindexed, and restarted masternode

getblockhash 58859
6a0005b2*

Do I match?

[oncoapop]

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

[Rob Andrews]

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

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.

[Rob Andrews]

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.

[Rob Andrews]

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.

[Rob Andrews]

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.