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

1.4.2.6-Mandatory Upgrade for TestNet

- Prevent tithe spam in memory pool

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

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!

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

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.

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.

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. 

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 ?

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

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

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.

yfBWKnEBzhwGMK9cC6CAdgZuQJEP68mBKR

Sent, but Im not sure that we have enough sancs for this to work properly, but we will see.

Sent, but Im not sure that we have enough sancs for this to work properly, but we will see.

It didn't work :,(

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.

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.