Messages

91

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 05, 2018, 03:30:54 PM »

Are you on the same chain as the 1.0.9.8. wallets? And if so, could we have your ip-adres so we can connect to your node?

How do I check which chain I am on? How can I find IP in BBP?

92

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 05, 2018, 03:18:26 PM »

So I guess the failed to sign CPID will sort itself out in some number of blocks?

I am not sure if in prod I should have taskweight and uxto both =0 still?

OK my wallet just did a transaction, sent some tiny amount of BBP to itself.

Now the failed to sign cpid is fixed.
Now my taskweight =100
Now I wait for my uxto!

(edit: transaction was automatic, not by me)

93

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 05, 2018, 03:09:23 PM »

OK. I upgraded in prod (on linux) to 1099. I am synched and all my BBP are there!
My wallet is unlocked and I have enough stake in there with a 50% stake percentage in config.

Just wanted to show you my outputs

"getinfo"

Code: [Select]

"version": 1000909,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.9",
  "balance": 110009.05571073,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33152,
  "timeoffset": 0,
  "connections": 1,
  "proxy": "",
  "difficulty": 1982.185198022292,
  "testnet": false,
  "keypoololdest": 1507790364,
  "keypoolsize": 1006,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
"getmininginfo"

Code: [Select]

"blocks": 33152,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 0,
  "difficulty_pow": 19821.85198022292,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 126738296153.7337,
  "hashps": 17.58459997091422,
  "minerstarttime": "03-05-2018 20:27:46",
  "hashcounter": 41474,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
[b]  "poolinfo1": "Failed to sign CPID signature (unlock wallet)?; ",[/b]
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 73,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false
exec getboincinfo

Code: [Select]

"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422301,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "8f273b30f8e0a298ed26e242762df701_ADDRESS": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "8f273b30f8e0a298ed26e242762df701_RAC": 28509.17,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
[b]  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,[/b]
  "Total_RAC": 28509.17,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0

So I guess the failed to sign CPID will sort itself out in some number of blocks?

I am not sure if in prod I should have taskweight and uxto both =0 still?

94

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 05, 2018, 02:47:03 PM »

Its most likely due to node.biblepay.org (the main seed node being on the old version).

Ill go ahead and upgrade it right now, now that windows is out.

Thanks Rob.
BTW we are now top 10 Rosetta

95

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 05, 2018, 02:42:04 PM »

I have 0 connection in prod...
clean install and now without connection

I also have no connection in 1099 in prod.
No block source

96

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 05, 2018, 03:29:51 AM »

I would always backup your wallet.dat, just in case
Don't know about your other questions...

thanks

97

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 04, 2018, 11:30:07 PM »

Ok I'm about to upgrade my wallet (in prod) to newest version.
Do I need to backup wallet.dat every time I upgrade wallet?

After I upgrade successfully I will transfer the stake to my wallet. Then is it true that my UXTO should be greater than 0?
Is it true that my taskweight will stay 0 until  the first superblock payout?

Thanks

98

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 04, 2018, 10:08:31 PM »

Hi,

One of the Slovakian guys messaged me with an issue. i wonder if we can help. So I think this is the issue he is having:

Linux, commandline

1. He associated CPID to Wallet #1 (W1), he had receiving address RA1.
2. He wanted to change to wallet 2 (W2) with receiving address RA2. He typed
"exec associate mail pass true"
He received the message about welcome to cancer mining
3. The URL on this website https://boinc.bakerlab.org/rosetta/home.php
should be the wallet receiving address.
The URL matched RA2. Perfect!
4. He wasn't sure it had worked so he associated his CPID with wallet 2 again. This time there was a new address created and shown in the  https://boinc.bakerlab.org/rosetta/home.php site.
But he does not recognize the address. It is not RA1 or RA2. I checked, it is also not a mining address.
The question is, should this address on the boinc site be your receiving address of the wallet? Is there an error here?

5. He tried associating it again on another machine in QT mode. It worked fine and the address changed to his receiving address.


Seems that people may have issues if they associate CPID to the same wallet twice (by accident)

99

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 04, 2018, 09:10:57 PM »

The staking percentage command is suppose to be in the controller wallet config file right?

I have this as my config file for my PoDC wallet (not Sanctuary)

addnode=node.biblepay.org:40000
addnode=biblepay.inspect.network
gen=1
genproclimit=1
polpercentage=50

100

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 04, 2018, 09:07:48 PM »

So this is a very, very good guinea pig test.  After 6 blocks could you please do an 'exec datalist dcc', this is a secret command, see if your CPID is in the list.  I believe the "FAILED TO SIGN CPID Error" is occuring, because you just associated yourself.  Once its in the list try a reboot then check getmininginfo again just to see that the error cleared?

Yes if you are not encrypted, your not locked (lock on the front bottom right GUI overview should be Open), so no it should not be a lock issue....

OK here we go "exec datalist dcc"

Code: [Select]

"DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-05-2018 00:24:09)": "04fba56d89a5eb38b1b82f8a6240132c;BHUyNiVgRcW4ZudFmyyzJydL9t2QW8fdWD;BHUyNiVgRcW4ZudFmyyzJydL9t2QW8fdWD;1981529;H1MouWGO6yWBk/fQBKp0OTEGApw9FZY5Tnbf8BQz1LujYjQnY/PyPhpd+tjce2vpUhIYaQ/4cxrMF0lfYwg9wSU=;0",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-04-2018 23:17:49)": "6785ded1f65063ef8f01f42deb31cf1d;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;1981965;IHbjBdincaH8YS/XL7k6VR9n8dHysachVwo63vwZk732SkG4+Q4qx/qObz2VsYPdBL8RtBpxv5pv3/gmmqtGFPY=;0",
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
  "8F273B30F8E0A298ED26E242762DF701 (03-05-2018 02:22:28)": "8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0",
  "E94C1704C75F731F8BFDE303F08408EE (03-05-2018 02:22:28)": "e94c1704c75f731f8bfde303f08408ee;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;1981209;IG2r+VxRlr+3ceKJhbLnldsMVoZv/uoKgx4SukL9Z+bJdIjpjCMaoceE1Aog7hFOSGJd70eU6bgLJM56hCRwV1k=;0"
}
I'm sorry, to me it is gibberish.


"getmininginfo"

Code: [Select]

{
  "blocks": 33045,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 0,
  "difficulty_pow": 33728.72968180398,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 228922584200.2176,
  "hashps": 88.14359163965726,
  "minerstarttime": "03-05-2018 01:58:23",
  "hashcounter": 354736,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 614,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false
}
That error has gone...


"exec getboincinfo"

Code: [Select]

"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422283,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "8f273b30f8e0a298ed26e242762df701_RAC": 24261.07,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,
  "Total_RAC": 24261.07,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
So it looks to be working fine!

Should I upgrade my prod wallet to 1098?

My UXTO weight is zero, but I have only a few BBP (I need to backup wallet first)

101

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 04, 2018, 08:49:44 PM »

So this is a very, very good guinea pig test.  After 6 blocks could you please do an 'exec datalist dcc', this is a secret command, see if your CPID is in the list.  I believe the "FAILED TO SIGN CPID Error" is occuring, because you just associated yourself.  Once its in the list try a reboot then check getmininginfo again just to see that the error cleared?

Yes if you are not encrypted, your not locked (lock on the front bottom right GUI overview should be Open), so no it should not be a lock issue....

Awesome, I will do once 6 blocks are gone.
I will not upgrade to new version just yet then

102

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 04, 2018, 08:19:53 PM »

Ok I set up a wallet running in qt mode in prod.
I have associated my cpid and it seemed happy.

getinfo gives me

Code: [Select]

"version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 9.05762053,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33038,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 3207.285566212733,
  "testnet": false,
  "keypoololdest": 1507790364,
  "keypoolsize": 1007,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
getmininginfo gives me

Code: [Select]

"blocks": 33038,
  "currentblocksize": 2034,
  "currentblocktx": 2,
  "difficulty_podc": 0,
  "difficulty_pow": 32072.85566212733,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 206993854304.6948,
  "hashps": 86.77371370534651,
  "minerstarttime": "03-05-2018 01:58:23",
  "hashcounter": 96544,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "Failed to sign CPID signature (unlock wallet)?; ",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 169,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false

Are there other commands I should be checking to see weights etc?

EDIT: By the way, my wallet does not yet have a password on it. Is this OK? I assumed this means it is always unlocked for staking...

103

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 04, 2018, 07:55:16 PM »

Please set :
polpercentage=50

For 50% of your coins to be staked once every ~12 hours.  The default in the wallet is 10% of the coins.

Awesome! thanks

104

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 04, 2018, 07:43:51 PM »

Hi all, can I please clarify what is needed in the config file.
What is the command to set my percentage of coins for stake?

So far my config file is:

Code: [Select]

addnode=node.biblepay.org:40000
addnode=biblepay.inspect.network
gen=1
genproclimit=1

Thanks

105

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 04, 2018, 07:33:34 PM »

You can always do the former, without the force=true, unless you are moving an already associated CPID to a new wallet.

Besides, if that happens it will throw the error "ALREADY_IN_CHAIN", then you can do force=true.

Thanks Rob and Orbis!