BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

[Rob Andrews]

Im compiling 1095c for windows now.

For existing testers: No need to upgrade, this next version just removes the logging and adds the exec racdecay function that matches T-Mikes spreadsheet.

[Rob Andrews]

Im compiling 1095c for windows now.

For existing testers: No need to upgrade, this next version just removes the logging and adds the exec racdecay function that matches T-Mikes spreadsheet.

Ok, windows 1095c is now out there  -   so now everyone can test the most recent version!


Lets Go PODC!

[orbis]

Any concerns by anyone, or anything anyone wants to ask, or double check, or any reservations to going live on March 20th?

I was thinking about that and I remembered that we wrote about these thing later:
1. have PoDC only wallet unlock option
2. auto setgenerate true 1 on PoDC (maybe both can be cumulated in 1 command or settings option)
3. and those different icons for different tx

[Rob Andrews]

I was thinking about that and I remembered that we wrote about these thing later:
1. have PoDC only wallet unlock option
2. auto setgenerate true 1 on PoDC (maybe both can be cumulated in 1 command or settings option)
3. and those different icons for different tx

I like #2 and #3, but on #1, I dont really like the way the POS coins implement that checkbox.
The problem with the implementation is it gives the user a false sense of security (when there is none).
If we add the option to unlock for staking only, then the user thinks their funds are secure (just because *they* cant spend them).
But in reality the whole point of making an encrypted wallet is to keep a hacker from stealing it.

So what you have in that case is someone moving 2 million biblepay to the controller , encrypting the wallet, clicking "unlock for staking only" and thinking they are secure.  Then when they get hacked, the hacker sends the whole 2 million out.

Otoh, when we just leave it the way it is, the user is forced to store the 2million in a cold wallet and leave only 50K on the controller.  OR manually take the risk and unlock the wallet.  This is far better , the way it is, imo.

I have not been able to think of a better solution to this.  It is possible to pull a hash from somewhere any make biblepay unlock the wallet, send the podc, and lock the wallet, but where is it going to pull the hash from if it does not open up a hole for a hacker to be able to see the file to find the hash?  Its not an easy issue to solve.

[orbis]

OK. I understand.
I didn't know that it is only "false sense of security".
So why we have "Only for mixing via PrivateSend" option?
Is it diffent?
And is there option to unlock wallet via command walletpassphrase for "infinity" not only for written time?

[Rob Andrews]

OK. I understand.
I didn't know that it is only "false sense of security".
So why we have "Only for mixing via PrivateSend" option?
Is it diffent?
And is there option to unlock wallet via command walletpassphrase for "infinity" not only for written time?

Only for mixing is the same : Only a boolean in the code protects the funds from being stolen.

Option to unlock forever:  just the option of 9999999 currently.

So I still cant think of anything better than asking the user for the password on bootup, we could say "Enter your password for PODC Updates if you wish>" (if the wallet is encrypted), not unlock the wallet, store the password in an encrypted memory variable using Secure String (thats suppoedly a way to be unable to read the memory by a hacker), then in PODC update we unlock send and lock.     Semi secure..... possibly... 

[orbis]

Only for mixing is the same : Only a boolean in the code protects the funds from being stolen.

Option to unlock forever:  just the option of 9999999 currently.

So I still cant think of anything better than asking the user for the password on bootup, we could say "Enter your password for PODC Updates if you wish>" (if the wallet is encrypted), not unlock the wallet, store the password in an encrypted memory variable using Secure String (thats suppoedly a way to be unable to read the memory by a hacker), then in PODC update we unlock send and lock.     Semi secure..... possibly...

Yes it would be good option but it can be annoying for some users. E.g. if you run your wallet on different PC.
I want to have it secure, because those 50k is all what I have now but it looks, that best solution is to leave it as it is.
And after unlock command just clear bash history. In windows wallets there is no that risk to "read" it so easy.

[Rob Andrews]

Yes it would be good option but it can be annoying for some users. E.g. if you run your wallet on different PC.
I want to have it secure, because those 50k is all what I have now but it looks, that best solution is to leave it as it is.
And after unlock command just clear bash history. In windows wallets there is no that risk to "read" it so easy.

Well Im not too worried about annoying the user.  Its only when they reboot the wallet.  Once per session.
We can add a flag that turns off the feature (like disablepodcunlock=true in the config).

Anyway I went ahead and made the wallet prompt you for your password when you boot, if its locked, encrypted and running in PODC mode.

Im not done with the feature yet - I still need to store it in encrypted memory and make it actually perform the auto unlock when a PODC occurs.

On bash though, does bash record keys typed into a password box on the GUI?  This is a qt feature only so it should not go into bash history.

I havent even thought about headless.  On headless you can write a script.

[Damian]

Hi all,
    I've no idea on setting up a MN for testnet, but I can put my laptop in testnet as a miner if that helps??
I've dloaded bionc and joined the BBP team, so wouldn't take much (dload new wallet). Let me know if I can be of any use?
   Damian

[togoshigekata]

Just confirming, for PODC UTXO Reward Chart (Staking),
where you need 50,000 BBP in a wallet to receive 100% rewards from PODC
Chart here: http://wiki.biblepay.org/index.php?title=Distributed_Computing#Proof-of-Distributed-Computing

The coins have to be in an unlocked wallet? (specifically the wallet that has the CPID/Burn with 1 mining thread running)

Thats not toooo bad, just a little extra work to secure your coins,
could just use another PC or $5/month cloud machine and periodically send rewards to your main encrypted wallet.

[T-Mike]

Hi all,
    I've no idea on setting up a MS for testnet, but I can put my laptop in testnet as a miner if that helps??
I've dloaded bionc and joined the BBP team, so wouldn't take much (dload new wallet). Let me know if I can be of any use?
   Damian

If you have BOINC set up, download the wallet and start mining by going into the debug tool and typing "setgenerate true 1". Once you have some test BBP, go to the Distributed Computing tab and associate your BOINC account with the Biblepay network.

[Damian]

Hi T-Mike,
  I've dloaded the latest wallet, and "setgenerate true 1", I'm not sure where the DC tab is?? is it in Bionc?
Also is the config I'm using suitable?

addnode=node.biblepay.org
gen=1
genproclimit=3
pool=https://pool.biblepay.org
workerid=bananaboyjoe

Thanks,
    Damian

[jaapgvk]

I'm getting my first 'unbanked' transactions 

Code Select Expand


10:18:16

exec getboincinfo


10:18:19

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "ybojKjcfCMPpoD1S97NPdVUdbbcsk6k5Lv",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 422217,
  "NextSuperblockHeight": 12969,
  "NextSuperblockBudget": 1339285,
  "c852da1a620ad630b70c8ec1ccdee366_RAC": 57.44,
  "c852da1a620ad630b70c8ec1ccdee366_TEAM": 15044,
  "c852da1a620ad630b70c8ec1ccdee366_TaskWeight": 100,
  "c852da1a620ad630b70c8ec1ccdee366_UTXOWeight": 100,
  "Total_RAC": 57.44,
  "Total Payments (One Day)": 10465,
  "Total Payments (One Week)": 15780,
  "Total Budget (One Day)": 13474430,
  "Total Budget (One Week)": 85599588,
  "Superblock Count (One Week)": 72,
  "Superblock Hit Count (One Week)": 64,
  "Superblock List": "12870,12771,12672,12573,12474,12375,12276,12177,12078,11979,11880,11781,11682,11583,11484,11385,11286,11187,11088,10989,10890,10791,10494,10395,10296,10197,10098,9999,9900,9801,9702,9603,9306,9207,8910,8811,8712,8514,8415,8217,8118,8019,7920,7821,7722,7623,7524,7425,7326,7227,7128,7029,6930,6831,6732,6633,6534,6435,6336,6237,6138,6039,5940,5841",
  "Last Superblock Height": 12870,
  "Last Superblock Budget": 1339285,
  "Last Superblock Payment": 2606,
  "Magnitude (One-Day)": 0.7766562296141655,
  "Magnitude (One-Week)": 0.184346681668608
}


Code Select Expand

Status: 278 confirmations
Date: 02-03-18 03:54
Source: Generated
Credit: 2647.47000000 tBiblepay
Net amount: +2647.47000000 tBiblepay

Height: 12672
Difficulty: 32.423041
Time: 03-02-2018 02:54:07
Subsidy: 5820.7679

:
Transaction ID: dfd8e518f41e3063882790ff25fd164298a988ca746a9ccc4c38c9fec283c673-000

Generated coins must mature 102 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.



Debug information

Credit: 2647.47000000 tBiblepay

Transaction:
CTransaction(hash=dfd8e518f4, ver=1, vin.size=1, vout.size=13, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 0280310101)
    CTxOut(nValue=5820.76786500, scriptPubKey=21032833a45709cf01a2fd9db2c698)
    CTxOut(nValue=319900.42000000, scriptPubKey=76a914fd47980297aad2b9f0db4f1c)
    CTxOut(nValue=46162.74000000, scriptPubKey=76a914198bdbf43eebc1040e4b1752)
    CTxOut(nValue=28732.44000000, scriptPubKey=76a914fc40b74ca5caed7982895b2a)
    CTxOut(nValue=576463.14000000, scriptPubKey=76a9149eab0ec205faec29fe899807)
    CTxOut(nValue=87702.49000000, scriptPubKey=76a914d7098dd1f89cf8c9e36261b4)
    CTxOut(nValue=148849.65000000, scriptPubKey=76a914959c47d10a53bdbd3d2bb392)
    CTxOut(nValue=21582.93000000, scriptPubKey=76a9146038548bdd9aae1ac290560b)
    CTxOut(nValue=24270.72000000, scriptPubKey=76a914df719a02dce5ba09dc474f1d)
    CTxOut(nValue=23907.87000000, scriptPubKey=76a91496ae325295b168d695d9d43d)
    CTxOut(nValue=54696.47000000, scriptPubKey=76a91430559e379e13083e6f156678)
    CTxOut(nValue=4367.65000000, scriptPubKey=76a914ed283debf89b31661f8604b5)
    CTxOut(nValue=2647.47000000, scriptPubKey=76a914a9e3493c08aa06c3c31746f6)

Inputs:

Code Select Expand

Status: 181 confirmations
Date: 02-03-18 06:09
Source: Generated
Credit: 2606.94000000 tBiblepay
Net amount: +2606.94000000 tBiblepay

Height: 12771
Difficulty: 36.267757
Time: 03-02-2018 05:09:05
Subsidy: 5820.7679

:
Transaction ID: 1d831b71fae895a8d7fa169ed3429179e937116675a8ccb2cfcae4163b2d6022-000

Generated coins must mature 102 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.



Debug information

Credit: 2606.94000000 tBiblepay

Transaction:
CTransaction(hash=1d831b71fa, ver=1, vin.size=1, vout.size=14, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 02e3310101)
    CTxOut(nValue=5820.76786500, scriptPubKey=210334fe421aa9256e0bba14d9941e)
    CTxOut(nValue=314647.42000000, scriptPubKey=76a914fd47980297aad2b9f0db4f1c)
    CTxOut(nValue=45393.08000000, scriptPubKey=76a914198bdbf43eebc1040e4b1752)
    CTxOut(nValue=28259.81000000, scriptPubKey=76a914fc40b74ca5caed7982895b2a)
    CTxOut(nValue=566983.49000000, scriptPubKey=76a9149eab0ec205faec29fe899807)
    CTxOut(nValue=86257.60000000, scriptPubKey=76a914d7098dd1f89cf8c9e36261b4)
    CTxOut(nValue=146405.45000000, scriptPubKey=76a914959c47d10a53bdbd3d2bb392)
    CTxOut(nValue=21997.77000000, scriptPubKey=76a9146ec0f5e17278e46595ed1fb3)
    CTxOut(nValue=21231.81000000, scriptPubKey=76a9146038548bdd9aae1ac290560b)
    CTxOut(nValue=23879.07000000, scriptPubKey=76a914df719a02dce5ba09dc474f1d)
    CTxOut(nValue=23516.25000000, scriptPubKey=76a91496ae325295b168d695d9d43d)
    CTxOut(nValue=53805.18000000, scriptPubKey=76a91430559e379e13083e6f156678)
    CTxOut(nValue=4300.11000000, scriptPubKey=76a914ed283debf89b31661f8604b5)
    CTxOut(nValue=2606.94000000, scriptPubKey=76a914a9e3493c08aa06c3c31746f6)

Inputs:

Code Select Expand

Status: 82 confirmations
Date: 02-03-18 08:33
Source: Generated
Credit: 2606.94000000 tBiblepay (matures in 20 more blocks)
Net amount: 0.00000000 tBiblepay

Height: 12870
Difficulty: 36.267757
Time: 03-02-2018 07:33:43
Subsidy: 5819.8947

:
Transaction ID: 70d0bb8c35c02ca805654e27fe8193fe04dbce63e10f8186a01016ba438d11bb-000

Generated coins must mature 102 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.



Debug information

Credit: 2606.94000000 tBiblepay

Transaction:
CTransaction(hash=70d0bb8c35, ver=1, vin.size=1, vout.size=14, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 0246320101)
    CTxOut(nValue=5819.89466250, scriptPubKey=2103272e1da0c3bb0196a37b6ebed0)
    CTxOut(nValue=314647.42000000, scriptPubKey=76a914fd47980297aad2b9f0db4f1c)
    CTxOut(nValue=45393.08000000, scriptPubKey=76a914198bdbf43eebc1040e4b1752)
    CTxOut(nValue=28259.81000000, scriptPubKey=76a914fc40b74ca5caed7982895b2a)
    CTxOut(nValue=566983.49000000, scriptPubKey=76a9149eab0ec205faec29fe899807)
    CTxOut(nValue=86257.60000000, scriptPubKey=76a914d7098dd1f89cf8c9e36261b4)
    CTxOut(nValue=146405.45000000, scriptPubKey=76a914959c47d10a53bdbd3d2bb392)
    CTxOut(nValue=21997.77000000, scriptPubKey=76a9146ec0f5e17278e46595ed1fb3)
    CTxOut(nValue=21231.81000000, scriptPubKey=76a9146038548bdd9aae1ac290560b)
    CTxOut(nValue=23879.07000000, scriptPubKey=76a914df719a02dce5ba09dc474f1d)
    CTxOut(nValue=23516.25000000, scriptPubKey=76a91496ae325295b168d695d9d43d)
    CTxOut(nValue=53805.18000000, scriptPubKey=76a91430559e379e13083e6f156678)
    CTxOut(nValue=4300.11000000, scriptPubKey=76a914ed283debf89b31661f8604b5)
    CTxOut(nValue=2606.94000000, scriptPubKey=76a914a9e3493c08aa06c3c31746f6)

Inputs:

[jaapgvk]

Hi T-Mike,
  I've dloaded the latest wallet, and "setgenerate true 1", I'm not sure where the DC tab is?? is it in Bionc?
Also is the config I'm using suitable?

addnode=node.biblepay.org
gen=1
genproclimit=3
pool=https://pool.biblepay.org
workerid=bananaboyjoe

Thanks,
    Damian

Hi Damian, thanks for helping

I think you are using your wallet/client in 'production mode' right now. You need to be in testnet mode to be able to see the DC-tab right now. If you're in Windows, to start your client in testnet mode, enter the following in your command-prompt :

cd c:\program files (x86)\biblepaycore
biblepay-qt -testnet

You can also start in testnet-mode by adding a command in your biblepay-conf, but I don't know what it is precisely.

Once your wallet is started, you are able to see the 'distributed computing' tab, where you can enter your rosetta@home credentials. You can then open tools->debug console and type 'setgenerate true 1'. This will make sure you're mining on the testnet.

I hope I'm clear enough. If not, just ask

[Damian]

Thanks Jaapgvk   
  I'll get on to it within the hour, if I've any problems I'll let you know,
    Damian