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

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

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
}

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.

I cleaned wallet and reindexed, and restarted masternode

getblockhash 58859
6a0005b2*

Do I match?

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

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.

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.

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.

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

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

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.

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.

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

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.