Bible Pay

Read 96301 times

  • Damian
  • Newbie

    • 3


    • 0
    • March 01, 2018, 09:36:40 am
    more
Thanks Jaapgvk   
  I'll get on to it within the hour, if I've any problems I'll let you know,
    Damian


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
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.

Yes, correct, the issue is in order to exercise ones UTXOWeight, the core must be able to "stake" up to 50K in a coinstake, at least once per day to associate its tasks with its UTXO coins.  So of course that means if the wallet is encrypted and locked, the core cant create a coinstake, and cant sign CPIDs either.

So let me cover the most Dangerous aspect of this so you can get a feel for the attack vectors:
Lets pretend you have 6.5 MILLION BBP, and 4 cold sanctuaries and you want to stake from the controller wallet on your home PC.
So you encrypted and locked the home wallet. 
Now you unlock the wallet with a passphrase for 9999 seconds so that PODC update can work.
The attack vectors are:

- Physical security - an intruder - a Wife, Husband, Sister, Brother, Or physical break in gains access to the machine and Sends coins out of the machine while the machine is unlocked
- Firewall security - a hacker breaches the firewall, compromises the password of the RPC port - and sends coins out with an RPC command
- Compromised Machine - Virus - A virus or botnet compromises the machine, and sends coins out of the running wallet - This type of attack could also copy the entire wallet.dat off the machine
- Fradulent Software Copy - A Very advanced virus, designed to mutate memory, is embedded on the machine altering the running state of the code - forcing the wallet to send out BBP
- Fraudulent Memory Reader - A Very advanced virus, copies the running memory of the machine and attempts to scan it for private keys in memory

As you can see with these attack vectors, a locked wallet would have prevented : Physical security, Firewall Security, Compromised Machine, Fraudulent Software and Fraudulent Memory Reader.   A locked for Staking wallet would prevent: physical security, firewall, compromised machine, but possibly would fail on the last two.

I ended up going with a feature that pops up when the user boots - asking for their wallet password (if they desire) and can be disabled with a config setting.  It stores the wallet password in a SecureString in memory (thats sort of like a non readable encrypted string that prevents reading the string from memory since it is not clear text), then when the wallet needs to Sign a CPID OR send a PODCUpdate, If that string is populated with a value, it unlocks the wallet, does the operation then locks the wallet again.

So this is as strong as I can make it with as much convenience as I can imagine, then for those who do not wish to break up the controller wallet into two pieces can still feel relatively at ease as long as they are running the binary.  In my case myself Ill probably use it, for my sanctuary set up on my home windows wallet, since I still need the ability to easily vote with the locked funds, maintain my start-stop of my sancs, its of higher security for me to keep that wallet available at home than on any rented VPS service. 

But yes if you sent the 50K out to a VPS, you would need your CPID rewards to go to that VPS, and then you could leave the wallet unencrypted/unlocked in the VPS.



  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
I have 5 CPIDs attached to my wallet, one of them is showing 0 for both weights.

"95a79cd5829e8315b0b946709930df18_RAC": 527.11,
"95a79cd5829e8315b0b946709930df18_TEAM": 15044,
"95a79cd5829e8315b0b946709930df18_TaskWeight": 0,
"95a79cd5829e8315b0b946709930df18_UTXOWeight": 0,


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
I have 5 CPIDs attached to my wallet, one of them is showing 0 for both weights.

"95a79cd5829e8315b0b946709930df18_RAC": 527.11,
"95a79cd5829e8315b0b946709930df18_TEAM": 15044,
"95a79cd5829e8315b0b946709930df18_TaskWeight": 0,
"95a79cd5829e8315b0b946709930df18_UTXOWeight": 0,


I dont see how thats happening - can you please double check your synced?  After that run this first, log output then restart client and log output?

From my node I see your 95a utxoweight @ 13:59, wait thats just 30 minutes ago:
exec datalist utxoweight:

"95A79CD5829E8315B0B946709930DF18 (03-02-2018 13:59:34)": "100"


I think what happened is you ran the command when your utxo weight ran out, then it synced within 6 blocks after....

You can find out by looking for your last PODC Update Before 3-2-2018 @ 13:59 UTC, But it must contain the XML for the CPID: 95A.

Meaning you would have to look at the showblock blocknumber, then the coinbase transaction vout 0.


If its showing up now in exec datalist utxoweight, then I think we just had a 24 hour lag between PODC update for that One CPID.

EDIT:  I forcefully created a contract on my hot sanc to see your 95a status, and it did pick up 100% for both weights. 



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
I'm getting my first 'unbanked' transactions  8)

Code: [Select]
10:18:16

exec getboincinfo


10:18:19

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "ybojKjcfCMPpoD1S97NPdVUdbbcsk6k5Lv",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 422217,
  "Next
  "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":
  "Magnitude (One-Day)": 0.7766562296141655,
  "Magnitude (One-Week)": 0.184346681668608
}

Code: [Select]
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




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, sc
    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]
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



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, scriptP2)
    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=76

[code]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



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=31464

Inputs:



Thanks Jaap!  So far everything looks good... Checking more ....



  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more

I dont see how thats happening - can you please double check your synced?  After that run this first, log output then restart client and log output?

From my node I see your 95a utxoweight @ 13:59, wait thats just 30 minutes ago:
exec datalist utxoweight:

"95A79CD5829E8315B0B946709930DF18 (03-02-2018 13:59:34)": "100"


I think what happened is you ran the command when your utxo weight ran out, then it synced within 6 blocks after....

You can find out by looking for your last PODC Update Before 3-2-2018 @ 13:59 UTC, But it must contain the XML for the CPID: 95A.

Meaning you would have to look at the showblock blocknumber, then the coinbase transaction vout 0.


If its showing up now in exec datalist utxoweight, then I think we just had a 24 hour lag between PODC update for that One CPID.

EDIT:  I forcefully created a contract on my hot sanc to see your 95a status, and it did pick up 100% for both weights.

I ran getboincinfo and it's fine now. This CPID has been associated and running continuously for a few days now.


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
I ran getboincinfo and it's fine now. This CPID has been associated and running continuously for a few days now.

Good, but just to clarify, once associated, the CPID wont lose association (for one year).  I think we will need to ask researchers to reassociate once per year, once they fall out of the chain.

But if you want to search your PODC Update transactions for the Last transmission you should see a 24.01 hour lag, to know why your weight dropped to zero for 6 blocks.




  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
I'm getting my first 'unbanked' transactions  8)

Code: [Select]
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]
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]
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]
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:

Jaap, after doing an exec dcc on my sanc (that forces a pretend morning quorum), and cd into the /SAN directory I can see your cpid is unbanked:
cat filtered | grep c852 -A10 -B10


Looking at the XML field for <unbanked>, it appears to be working correctly.




  • jaapgvk
  • Hero Member

    • 617


    • 31
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Jaap, after doing an exec dcc on my sanc (that forces a pretend morning quorum), and cd into the /SAN directory I can see your cpid is unbanked:
cat filtered | grep c852 -A10 -B10


Looking at the XML field for <unbanked>, it appears to be working correctly.

Cool :) I saw the 'Associate Unbanked CPID' option in the pool. Awesome! Unfortunately I don't have a spare phone, so I can't test that function right now...


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Cool :) I saw the 'Associate Unbanked CPID' option in the pool. Awesome! Unfortunately I don't have a spare phone, so I can't test that function right now...

Yeah, its not quite ready to test, it needs a windows upgrade also.



  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
Good, but just to clarify, once associated, the CPID wont lose association (for one year).  I think we will need to ask researchers to reassociate once per year, once they fall out of the chain.

But if you want to search your PODC Update transactions for the Last transmission you should see a 24.01 hour lag, to know why your weight dropped to zero for 6 blocks.

Could you explain how to look that up? Thank you.


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Could you explain how to look that up? Thank you.
Best way is to have you launch in -qt mode, then go to the transactions list, and scan for PODC Update.  Double click it.
Grab the Block Hash to the clipboard.
Type 'getblock blockhash' or 'showblock blocknumber'.
Then Copy the coinbase transaction #0 (the first tx) to the clipboard) - just the txid.
Then type 'getrawtransaction TXID 1', and look in the <XML> near the bottom for a CPID signature. Find the TXID corresponding to the CPID that was missing its weight over 1 day.

Once you get that TXID, take a look at its mother block timestamp (the timestamp is called HR Time in showblock).




Oh btw guys:  I added Orbis's 3 suggestions last night:  Icon for PODC Update and PODC Payment, Automatic Unlock for encrypted wallets, and support for the unbanked command from the pool.  (I think there was one more thing, that was added also).



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
If anyone needs the latest windows, to test the PODC Payment and Update icons and the auto-unlock feature windows is now available for download.

PS I think we are close to being ready to go live on the 20th or so. 



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
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

Ok, these have been added and ready for testing.  Windows is ready for download.
The wallet defaults to automatic mining now (in PODC mode only) on one thread, with setgenerate=true automatically.



  • jaapgvk
  • Hero Member

    • 617


    • 31
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Ok, these have been added and ready for testing.  Windows is ready for download.
The wallet defaults to automatic mining now (in PODC mode only) on one thread, with setgenerate=true automatically.

Icons and automatic-mining work as expected, but the automatic lock gives me a runtime error:



This is Windows btw.

I've tried a reindex, deleting the testnet3 folder, a complete reinstall with the backuped wallet.dat and with a new wallet.dat.
I've tried different passwords, but they all give me the same screen.

I don't even have to type in a password, If I start the wallet it gives me this error after about 10 seconds or so

I'm gonna try on a different PC now. If you need some debugging, I need some instructions on how to provide that :)
« Last Edit: March 03, 2018, 03:15:07 am by jaapgvk »