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

[Rob Andrews]

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

[togoshigekata]

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

[Rob Andrews]

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.

[orbis]

So, finally after upgrade I'm synced.
Mining is working and I'm waiting for GSC transmission

[jaapgvk]

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!

[togoshigekata]

Looks like I went on a lone fork, I reindexed and Im back in agreement

[togoshigekata]

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

[jaapgvk]

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

[vuli]

I send you some "change"

[Rob Andrews]

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.

[Rob Andrews]

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.

[togoshigekata]

Reporting back, I was able to run "exec sendgscc" with encrypted/locked GUI wallet,
Output:
{
"Command": "sendgscc",
"results": 1
}

[Rob Andrews]

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.

[Rob Andrews]

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.

[Rob Andrews]

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.