February 2021 Testnet Thread (Tribulation)

Indeed it worked, i received both e-mails and the picture to.  Looks all good now Rob.

** UTXO Staking Enhancement Coming **


So lately I've been trying to come up with an idea to make the utxo staking idea easier for mainstream users.  Its obviously hard to get any kind of adoption in our wallet if its hard to use, and of course, if they have to boot another wallet, send a stake, sign a key with an RPC command and then somehow jump through one clipboard to another to paste the 'signature' its asking them to jump a pretty high bar. 

So fortunately, I think I have a solution that will enable us to make this very easy and still give us high security.  UTXO Staking 2.0:

Let us require the bitcoin user to send a specific value in the suffix (determined by a BiblePay checksum), from any exchange to any wallet online or offline in bitcoin.  So this obviously sounds pretty easy.  The go to biblepay, biblepay automatically creates a CPK (we do that already that we use for the user record for RSA and also for staking rewards).  BiblePay will give them a 6 digit pin right on the overview page (or on the rpc, maybe they type 'get stake pin').  This is easy too.  Now they send BTC with that pin suffix from anywhere to anywhere. 

Then they go back to BIBLEPAY, and they type 'stake BTC_ADDRESS'.  Where BTC_ADDRESS is the place they send the stake to.

Then the sanctuaries monitor this, and induct the stake into the leaderboard.  Of course they have to match the stake with the same amount of BBP (as we already require) otherwise they get very very tiny rewards, etc.  But as you can see this makes it super easy to work with BTC or DASH.

So heres a live example:

User one enter the biblepay wallet, and gets their pin 123456.
Then they go to their bitcoin wallet or their favorite exchange, and send 1.00123456 btc to themselves.
Then they come back to biblepay and paste their destinatetion BTC address in the stake command as above.
Now they are in the leaderboard with $30,000 of BTC stake value (as long as they staked $30K of BBP) for example.
This entry stays in the leaderboard until the BTC is actually spent.  Once they spend it, the UTXO is spent.

Do you guys like this?

If so, I will revamp UTXO staking to utilize this new idea so we can test it.
I feel that it will be much easier to test also right?

The idea is to appeal to the mainstream who want to hold long positions, and we can be their portfolio manager.
We always wanted to be the 'deflationary' coin of choice, but without users, we could not get there.

I understand people will be ticked off about losing PODC, but we only have 39 PODC users.  At this point we've given PODC a long test and the users have not flown in droves, unfortunately.  We have a good partner with GRC  who can handle that side of the house.  We have to be known for something of our own.  And that can be freedom related anti censorship features.

It sounds like a superb idea if i understand it correctly.
Correct me if im wrong Rob, but this would make it possible to utilize a wallet like ledger live right?
If so not bad not bad

It sounds like a superb idea if i understand it correctly.
Correct me if im wrong Rob, but this would make it possible to utilize a wallet like ledger live right?
If so not bad not bad

Yes sir, I was just thinking of electrum myself cause someone asked about enhancing it with a signature feature at one point; but yes, you could then use SouthXChange even (generate receive address, send to yourself on the exchange, do not spend it), Ledger Live, an external hardware key, or anything actually.  You could even make flash drives with one wallet.dat and one stake on it per flash drive and call it a 'security', lol.

Yeah, sounds pretty interesting so far.  I think this might work.

We have to be known for something of our own.  And that can be freedom related anti censorship features.

Yes, THIS! Please and Thank you.
However I can help support, I am happy to do so!

-R

Yes, THIS! Please and Thank you.
However I can help support, I am happy to do so!

-R

Absolutely, thanks for the energy, well so far, we have the idea to send and receive private pop3 emails using BiblePay as the backbone.  We can also encrypt e-mails for privacy.  We can also support sending to "all" (not implement yet but coming soon) - this might be useful for a massive update or message to a Christian group.

Anyway its kind of obvious to me that we need a decentralized type facebook also that the government cant censor, but that is a big animal in itself - basically an entire side project that needs owned by another dev or set of devs.  I think I can help make the transactions work and talk about decentralized storage ideas.  Or, does that already exist, I havent done any research on that yet - is there a decentralized facebook already?

But first could you share if you see any other groundbreaking needs in the world and what area of expertise you are in?  (IE are you a c++ dev by any chance?)

** TestNet update **

So we have been doing really good with testing up to 1.5.3.6, and so far we have accomplished some testing with non-private pop3/smtp, and got that to work in windows.  It appears the e-mails flow to and from the [external nodes] and the network fills in the holes (for missing e-mail hashed files) properly, and purges them when they expire. 

We started testing dacengine, but I have not received feedback on that here yet - (or gettxoutsetinfo), but I look forward to that.

I wanted to mention, once we started speaking about the enhanced hybrid-utxo mining (mining with foreign pair + BBP using PIN's instead of Signing) I got pretty excited about that idea, and I am trying to squeeze that in now for a 1.5.3.7 release, because it should theoretically make it easy for new users.  We are also adding in LTC and DOGE support while we are at it, so we can launch with BTC, DASH, LTC and DOGE utxo mining.

Im also adding in the Bible Verse memorizer tool for the next release!

So realize a lot is still happening in the mean time.

We should a new testnet released by this weekend.

In the very very near future I plan on adding biblepay-university 1.0 (this is the teaching module for Christianity).  I feel the way things are slotted this may also make it into the next mandatory upgrade.

** Tackling the DAC Donation Test Case **

So lets go ahead and tackle the test cases for 'giving to the decentralized autonomous charity' through the UI and the RPC.

Method 1:  Give from the UI (Send Money):
Click into Send Money, check Donate to DAC.  Enter amount.  Click Send.

Testing method 1 i sent 1 000 000MM tBBP
In terminal i wrote: 'getrawtransaction txid 1 and got this:

Code: [Select]

      "value": 238083.90076663,
      "valueSat": 23808390076663,
      "n": 1,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 9f0c767b559a0a5a61c82482460aa9ad75000c30 OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9149f0c767b559a0a5a61c82482460aa9ad75000c3088ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yapRDdqegPmQrTJi37Bmi7fE6RUHi1sxSo"
        ]
      },
      "message": ""
    },
    {
      "value": 761868.48245321,
      "valueSat": 76186848245321,
      "n": 2,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 4a916a34b0ca0d6a7d44df479423d24515b22cff OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9144a916a34b0ca0d6a7d44df479423d24515b22cff88ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yT7j3zz8qGYumBAVN4ywJPYvFkRWWjNmVh"
        ]
      },
      "message": ""
    }
Then i wrote in terminal : "exec dacengine"   and got:

Code: [Select]


{
  "Command": "dacengine",
  "Allocated Charity": "yT7j3zz8qGYumBAVN4ywJPYvFkRWWjNmVh",
  "Percentage": 0.7618684824532166,
  "Allocated Charity": "yapRDdqegPmQrTJi37Bmi7fE6RUHi1sxSo",
  "Percentage": 0.2380839007666302,
  "004C4566": "Name: Junior F, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/004c4566.htm, Charity: cameroon-one",
  "01DDA520": "Name: Ferdinand N, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/01dda520.htm, Charity: cameroon-one",
  "03602406": "Name: Christable S, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/03602406.htm, Charity: cameroon-one",
  "0954C3FF": "Name: Harison N, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/0954c3ff.htm, Charity: cameroon-one",
  "321809AC": "Name: Pepe Gabriel, Amount: 25.00, URL: https://kairoschildrensfund.com/bios/pepe-gabriel/, Charity: kairos",
  "72822DF2": "Name: Princess Cabugnasan, Amount: 25.00, URL: https://kairoschildrensfund.com/bios/princess-cabugnasan/, Charity: kairos",
  "Expense Total (USD)": 1400,
  "Revenue Total (USD)": 300
}

Percentages looks ok to me.
I will test out Method number 2 tomorrow and will give an update.

Method 2: From the RPC:
From the RPC, type 'exec give amount' (TODO: Rob will remove the word exec ASAP).

Copy the TXID to the clipboard.
To see how it was distributed type 'getrawtransaction txid 1'.  Note that the tx went out to multiple partners based on a smart allocation.  The allocation has to do with how much we are currently paying monthly for our orphan commitments.

To see the projected breakdown, type 'exec dacengine'.
Right now in testnet, we only have 2 charities:  Cameroon-One and KAIROS.  The cameroon one % is currently 76%, and the kairos is 23%.

Verify that your donation went to the two charity addresses and that the percentages are correct?

I will also explain how the DAC reports each orphan and the monthly amount in a separate post.

Tested out method 2 today.

Ran command:

Code: [Select]

16:21:47

exec give 1000000


16:21:48

{
  "Command": "give",
  "Allocated Charity": "yT7j3zz8qGYumBAVN4ywJPYvFkRWWjNmVh",
  "Amount": 761868,
  "Allocated Charity": "yapRDdqegPmQrTJi37Bmi7fE6RUHi1sxSo",
  "Amount": 238083,
  "txid": "074f30dafd6c280e07126fb38cfd246ac69e8c7f5fece6581d6c84f70a9cf150",
  "Thank You": "May your family be blessed with the richest blessings of Abraham, Isaac and Jacob. "
}

then i ran command 

Code: [Select]

exec dacengine
and got:

Code: [Select]

16:28:54

exec dacengine


16:28:54

{
  "Command": "dacengine",
  "Allocated Charity": "yT7j3zz8qGYumBAVN4ywJPYvFkRWWjNmVh",
  "Percentage": 0.7618684824532166,
  "Allocated Charity": "yapRDdqegPmQrTJi37Bmi7fE6RUHi1sxSo",
  "Percentage": 0.2380839007666302,
  "004C4566": "Name: Junior F, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/004c4566.htm, Charity: cameroon-one",
  "01DDA520": "Name: Ferdinand N, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/01dda520.htm, Charity: cameroon-one",
  "03602406": "Name: Christable S, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/03602406.htm, Charity: cameroon-one",
  "0954C3FF": "Name: Harison N, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/0954c3ff.htm, Charity: cameroon-one",
  "321809AC": "Name: Pepe Gabriel, Amount: 25.00, URL: https://kairoschildrensfund.com/bios/pepe-gabriel/, Charity: kairos",
  "72822DF2": "Name: Princess Cabugnasan, Amount: 25.00, URL: https://kairoschildrensfund.com/bios/princess-cabugnasan/, Charity: kairos",
  "Expense Total (USD)": 1400,
  "Revenue Total (USD)": 300
}

It looks all good to me Rob , just diffrent ways of giving i suppose.

Tested out method 2 today.

Ran command:

Code: [Select]

16:21:47

exec give 1000000


16:21:48

{
  "Command": "give",
  "Allocated Charity": "yT7j3zz8qGYumBAVN4ywJPYvFkRWWjNmVh",
  "Amount": 761868,
  "Allocated Charity": "yapRDdqegPmQrTJi37Bmi7fE6RUHi1sxSo",
  "Amount": 238083,
  "txid": "074f30dafd6c280e07126fb38cfd246ac69e8c7f5fece6581d6c84f70a9cf150",
  "Thank You": "May your family be blessed with the richest blessings of Abraham, Isaac and Jacob. "
}

then i ran command 

Code: [Select]

exec dacengine
and got:

Code: [Select]

16:28:54

exec dacengine


16:28:54

{
  "Command": "dacengine",
  "Allocated Charity": "yT7j3zz8qGYumBAVN4ywJPYvFkRWWjNmVh",
  "Percentage": 0.7618684824532166,
  "Allocated Charity": "yapRDdqegPmQrTJi37Bmi7fE6RUHi1sxSo",
  "Percentage": 0.2380839007666302,
  "004C4566": "Name: Junior F, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/004c4566.htm, Charity: cameroon-one",
  "01DDA520": "Name: Ferdinand N, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/01dda520.htm, Charity: cameroon-one",
  "03602406": "Name: Christable S, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/03602406.htm, Charity: cameroon-one",
  "0954C3FF": "Name: Harison N, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/0954c3ff.htm, Charity: cameroon-one",
  "321809AC": "Name: Pepe Gabriel, Amount: 25.00, URL: https://kairoschildrensfund.com/bios/pepe-gabriel/, Charity: kairos",
  "72822DF2": "Name: Princess Cabugnasan, Amount: 25.00, URL: https://kairoschildrensfund.com/bios/princess-cabugnasan/, Charity: kairos",
  "Expense Total (USD)": 1400,
  "Revenue Total (USD)": 300
}

It looks all good to me Rob , just diffrent ways of giving i suppose.

Thank you sir Earlz, this looks good to me - that is, both test methods and the output.


I'm upgrading the 'exec give' to an RPC 'give' command right now.

Im unit testing the LTC pin staking method right now. 

Last night I was able to get the Memorize UI working.

Ill post more test cases asap.  Hopefully by tomorrow we can release this pin staking feature so we can all get this working.

Thanks a lot.

1.5.3.6 - Mandatory Upgrade for TestNet

- Fix SMTP for Windows

MIP, will you please notify us when MAC is ready?

Ready. I'll around for the weekend so I will compile next version as soon as you announce it.

I will do some test cases now.

Donate to DAC

Method 1: (UI) created a transaction apparently as expected

Code: [Select]

11:19:07

getrawtransaction 2d12e6a85cc4a8e28b140e36d65c8fb680fed2d0770cbad46902a9f8d3ca8bc7 1


11:19:07

{
  "hex": "0100000001277871811de6acca93814ec1b36ed0682c16aa6c9229ca029be7434c89c21649010000006a473044022027ab0e0b97a8abfa48ebd19853506c989a0a23265bd3dda74a75da432b420abc02204a65221783a474601e4558d747a790498adc645185b82663c05ef911415d1bf3012103f47e7c8cdc6c158b7be6269bc9058cf1cb2681f212d63ac02874d09eec498da1feffffff03bc33178b050000001976a9149f0c767b559a0a5a61c82482460aa9ad75000c3088ac00f50b17bd110000001976a9144a916a34b0ca0d6a7d44df479423d24515b22cff88ac00b7d1a3f4140000001976a914771acc7513755f8029d10673996d3ade8e01bcb388ac0040ee0000",
  "txid": "2d12e6a85cc4a8e28b140e36d65c8fb680fed2d0770cbad46902a9f8d3ca8bc7",
  "size": 262,
  "version": 1,
  "type": 0,
  "locktime": 60992,
  "vin": [
    {
      "txid": "4916c2894c43e79b02ca29926caa162c68d06eb3c14e8193caace61d81717827",
      "vout": 1,
      "spent_amount": 1899.99224000,
      "spent_time": 1610885174,
      "scriptSig": {
        "asm": "3044022027ab0e0b97a8abfa48ebd19853506c989a0a23265bd3dda74a75da432b420abc02204a65221783a474601e4558d747a790498adc645185b82663c05ef911415d1bf3[ALL] 03f47e7c8cdc6c158b7be6269bc9058cf1cb2681f212d63ac02874d09eec498da1",
        "hex": "473044022027ab0e0b97a8abfa48ebd19853506c989a0a23265bd3dda74a75da432b420abc02204a65221783a474601e4558d747a790498adc645185b82663c05ef911415d1bf3012103f47e7c8cdc6c158b7be6269bc9058cf1cb2681f212d63ac02874d09eec498da1"
      },
      "sequence": 4294967294
    }
  ],
  "vout": [
    {
      "value": 238.08390076,
      "valueSat": 23808390076,
      "n": 0,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 9f0c767b559a0a5a61c82482460aa9ad75000c30 OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9149f0c767b559a0a5a61c82482460aa9ad75000c3088ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yapRDdqegPmQrTJi37Bmi7fE6RUHi1sxSo"
        ]
      },
      "message": ""
    },
    {
      "value": 761.86848245,
      "valueSat": 76186848245,
      "n": 1,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 4a916a34b0ca0d6a7d44df479423d24515b22cff OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9144a916a34b0ca0d6a7d44df479423d24515b22cff88ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yT7j3zz8qGYumBAVN4ywJPYvFkRWWjNmVh"
        ]
      },
      "message": ""
    },
    {
      "value": 900.03722679,
      "valueSat": 90003722679,
      "n": 2,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 771acc7513755f8029d10673996d3ade8e01bcb3 OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a914771acc7513755f8029d10673996d3ade8e01bcb388ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yXBDN2xNBUV28mrkqEiBjWy3TcQq3swZHq"
        ]
      },
      "message": ""
    }
  ],
  "instantlock": false,
  "instantlock_internal": false,
  "chainlock": false
}

Method 2:

Code: [Select]

11:15:44

exec give 1000


11:15:44

{
  "Command": "give",
  "Allocated Charity": "yT7j3zz8qGYumBAVN4ywJPYvFkRWWjNmVh",
  "Amount": 761,
  "Allocated Charity": "yapRDdqegPmQrTJi37Bmi7fE6RUHi1sxSo",
  "Amount": 238,
  "txid": "55c03c2c09c88749bb2416352becc7f1d13a2a02e191d5471a2b8f4a716706ec",
  "Thank You": "May your family be blessed with the richest blessings of Abraham, Isaac and Jacob. "
}

which is

Code: [Select]

11:21:20

getrawtransaction 55c03c2c09c88749bb2416352becc7f1d13a2a02e191d5471a2b8f4a716706ec 1


11:21:20

{
  "hex": "0100000001b68a2c81fba13a583a494e9aa13ff87e0a6abb97fc86024f9d38ebd2171c1bf30000000049483045022100a17582f7b416541aac7bbc7d9fc0160dcd333f70c25fc3c578f6fc9a55f8aafe02201c30b8f4b3f6c0e00aaeaf654c319cc9989f5a056f27b3d273b89aaf292ea2d501feffffff03bc33178b050000001976a9149f0c767b559a0a5a61c82482460aa9ad75000c3088ac00f50b17bd110000001976a9144a916a34b0ca0d6a7d44df479423d24515b22cff88ac253c676966743e3c616d6f756e743e313030302e30303c2f616d6f756e743e3c2f676966743e4659035c3e0000001976a91496818d94f17ac0948dd35534e02c1d7655bb0d3d88ac0040ee0000",
  "txid": "55c03c2c09c88749bb2416352becc7f1d13a2a02e191d5471a2b8f4a716706ec",
  "size": 266,
  "version": 1,
  "type": 0,
  "locktime": 60992,
  "vin": [
    {
      "txid": "f31b1c17d2eb389d4f0286fc97bb6a0a7ef83fa19a4e493a583aa1fb812c8ab6",
      "vout": 0,
      "spent_amount": 3678.27200007,
      "spent_time": 1610356937,
      "scriptSig": {
        "asm": "3045022100a17582f7b416541aac7bbc7d9fc0160dcd333f70c25fc3c578f6fc9a55f8aafe02201c30b8f4b3f6c0e00aaeaf654c319cc9989f5a056f27b3d273b89aaf292ea2d5[ALL]",
        "hex": "483045022100a17582f7b416541aac7bbc7d9fc0160dcd333f70c25fc3c578f6fc9a55f8aafe02201c30b8f4b3f6c0e00aaeaf654c319cc9989f5a056f27b3d273b89aaf292ea2d501"
      },
      "sequence": 4294967294
    }
  ],
  "vout": [
    {
      "value": 238.08390076,
      "valueSat": 23808390076,
      "n": 0,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 9f0c767b559a0a5a61c82482460aa9ad75000c30 OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9149f0c767b559a0a5a61c82482460aa9ad75000c3088ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yapRDdqegPmQrTJi37Bmi7fE6RUHi1sxSo"
        ]
      },
      "message": ""
    },
    {
      "value": 761.86848245,
      "valueSat": 76186848245,
      "n": 1,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 4a916a34b0ca0d6a7d44df479423d24515b22cff OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9144a916a34b0ca0d6a7d44df479423d24515b22cff88ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yT7j3zz8qGYumBAVN4ywJPYvFkRWWjNmVh"
        ]
      },
      "message": "<gift><amount>1000.00</amount></gift>"
    },
    {
      "value": 2678.31695686,
      "valueSat": 267831695686,
      "n": 2,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 96818d94f17ac0948dd35534e02c1d7655bb0d3d OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a91496818d94f17ac0948dd35534e02c1d7655bb0d3d88ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "ya3FQUtQQ8nEDD9nV1J3ZNjwAYG22DC2mD"
        ]
      },
      "message": ""
    }
  ],
  "instantlock": false,
  "instantlock_internal": false,
  "chainlock": false
}

with regards to exec dacengine

Code: [Select]

11:22:05

exec dacengine

11:22:05

{
  "Command": "dacengine",
  "Allocated Charity": "yT7j3zz8qGYumBAVN4ywJPYvFkRWWjNmVh",
  "Percentage": 0.7618684824532166,
  "Allocated Charity": "yapRDdqegPmQrTJi37Bmi7fE6RUHi1sxSo",
  "Percentage": 0.2380839007666302,
  "004C4566": "Name: Junior F, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/004c4566.htm, Charity: cameroon-one",
  "01DDA520": "Name: Ferdinand N, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/01dda520.htm, Charity: cameroon-one",
  "03602406": "Name: Christable S, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/03602406.htm, Charity: cameroon-one",
  "0954C3FF": "Name: Harison N, Amount: 40.00, URL: https://biblepay.cameroonone.org/bios/0954c3ff.htm, Charity: cameroon-one",
  "321809AC": "Name: Pepe Gabriel, Amount: 25.00, URL: https://kairoschildrensfund.com/bios/pepe-gabriel/, Charity: kairos",
  "72822DF2": "Name: Princess Cabugnasan, Amount: 25.00, URL: https://kairoschildrensfund.com/bios/princess-cabugnasan/, Charity: kairos",
  "Expense Total (USD)": 1400,
  "Revenue Total (USD)": 300
}

So percentages look ok here.

By the way I am getting these messages on the terminal every now and then

ASIO::Bad file descriptor

which would mean that the variable where the socket is has gone out of scope. For what I see in the code both pop3 and smtp sockets are permanent (global) so I cannot find any other cause why this should be happening, but maybe it is worth further research on my side

I will come back if I find anything.

By the way I am getting these messages on the terminal every now and then

ASIO::Bad file descriptor

which would mean that the variable where the socket is has gone out of scope. For what I see in the code both pop3 and smtp sockets are permanent (global) so I cannot find any other cause why this should be happening, but maybe it is worth further research on my side

I will come back if I find anything.

Thanks MIP.
Yeah I did see that again on my end recently, that after Outlook queries my wallet every so often, the communication session gracefully ends with no errors when I send an email, or when I retrieve a pop3 email, so that part I believe is solid.  However some trailing bytes (possibly, Goodbye, thank you for contacting us, or \r\n) are still in the socket and trying to be relayed back to the mail client.

I did a little research on boost sockets and all I know so far, is since we are using async sockets, the write_handler (or read_handler) methods you see in the class could be getting called even after the socket closes.  For right now, I made that particular message not print to the console any more.  Which is not technically a hack, because there are a lot of system errors in the class not normally printed anyway with the socket (like hangups for instance), and, additionaly remember im the one who added the line to print to the console so Im not trying to "cover up" the error by not printing it just to make that clear to people. 

So if you think its worth doing more research as to how to clear the buffer for lingering bytes, imho its probably ok to leave it be unless you discover something more nefarious in there.  Im checking in the latest now!

Thanks.

** Test cases for Easy Stake **

This is going to be a doozy, so I'm going to attempt to write the test case here first rather than make a wiki page (in fear that this is our evolving process).  I will make a wiki for the mandatory release however so it is more concise.

So here goes.  We have the ability to stake BIBLEPAY alone, and that gets you in the leaderboard and the reward is Half of what you would get if you stake BIBLEPAY+ANOTHER_CURRENCY. 

We now support BTC, LTC, DOGE and DASH!  WOW!  That should be an amazing launch.

The great news is we are rolling out Pin staking.  Meaning that you no longer need to sign your coins on your foreign wallet!  All you need to do is get your BBP pin for the foreign currency address, which is 5 digits, and then send some foreign currency with the correct Amount suffix!

Why 5 digits?  This keeps the maximum "testing/convenience" costs for the end user down to $22 for BTC (as you know you have to go three digits after the decimal point in scale on BTC to get down to the $22 level).  Note that the money is not wasted, it is sent back to you anyway, but again this is for convenience and affordability.  This way any of us can test no matter how little we have.  Besides, we can obviously go with LTC or DOGE now for testing anyway, but I still would like to get full coverage.

Let me break this guide up into two parts, staking BBP alone first:

How to stake BBP the easiest way (without knowing about UTXOs):
We covered the UI earlier - option 1 is going to Send Money and click "UTXO Stake".  However, this guide is about the new rpc commands.
Now you can go to the RPC and type "easybbpstake min_amount 0/1".  Where min_amount is the smallest amount of BBP you want to stake.
The wallet will search through your UTXOs finding one that is not locked that is bigger than that amount.
0 equals dry run.  A Dry Run is a test only.  The BBP will not be spent.  A 1 means do it for real.
This will place you in the leaderboard.  Your DWU (DWU is similar to ROI) is half for BBP only staking.

Please test this feature.

Next, let us move on to our UTXO staking with foreign currencies.  This draws the masses into BBP to receive rewards.  They still must buy a commensurate amount of BBP to perform this stake, otherwise it will reward them minimally (the reward is based on the lesser of the USD value of the two, each day, assessed by the sancs, *2).  However hybrid staking rewards you with double the reward, since you have two components.

Let our example go with a LTC stake.  Let us assume you have 1 LTC.  You may now do this from light wallets, electrum, or even SouthXChange.  For this test lets use SouthXChange since we are all familiar with SX.

First you need your BBP Pin for your foreign currency receive address.  Grab your LTC address from SouthXChange by clicking LTC | "Deposit", and Copy the LTC address down to the clipboard.

Then, From BBP type:
getpin LTC_ADDRESS
BBP responds with a 5 digit pin.

Now to send this collateral into a BBP Hybrid Stake, go to SX, go to the Withdraw Coins (for LTC).

Set the send_to address to your LTC Deposit Address (this is the address in the clipboard from the prior step -- this means SX will be sending the coins out from SX, but back into SX as a deposit back into your own account).  This keeps them safe as an unspent UTXO - UNTIL they do their next re-organization batch job. 

Here is the most critical part:  Your amount to SEND must end with a suffix of the BBP 5 digit pin:
Let me show you an example:
You have 1.25 LTC at SX.  You want to stake 1 LTC in bbp.  Your pin is 12345.

The amount you want to send is:
1.012345

Note that you can optionally send:  1.0012345 or 1.00012345.  But You cannot send "1.000012345" because the total digit count after decimal must be 8 or less! 
Second Example, how do I send .10 ltc as a stake?  Send .1012345.

Critical NOTE:  You MUST check "I pay the fees", otherwise the exchange will change the withdrawal amount.

Next Click Send.

Now from BBP, after a couple blocks in LTC have passed do this:

easystake min_bbp_amt ltc_address foreign_amount 0=test/1=real

Where min_bbp_amt is the quantity of BBP you would like to stake in the hybrid stake.  You will want to pick a number that gives you a good tie in total USD value with the foreign currency value in USD (for example, if you stake $50 of LTC you will want to try to stake at least $50 of BBP, to give you the $100 total stake value).  Where foreign_amount equals the amount you just staked in LTC (the number with the pin suffix).

Note, to make this as easy as possible for the masses, we also support "-1" for the foreign_amount.  If -1 is passed, we will scan the foreign currency chain for stakes from today that match your pin.  If one matches we will show it on the screen and use it.

Security:
To make this as secure as possible, the sanctuaries (who act as oracles) will check that the coin is not spent, each day.  It does this for both BBP coins and Foreign coins.  Only when the coins are verified, then those entries are added into the GSC contract (this is the same as what is shown in the leaderboard).  We also enforce the stake pin this way:  The RECEIVE address in the foreign currency resolves to a pin through our base58->pin algorithm, meaning that only the initiator of the pin could possibly know the coin amount suffix to send for the foreign address.  We additionally check the TIMESTAMP of the sent coins to ensure it is within the STAKE WINDOW.  This makes it impossible to do a stake harvesting attack for biblepay rewards.