Messages

151

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

« on: March 04, 2018, 02:38:01 PM »

1.0.9.7 has been deployed for windows.

Note, the hot sanctuaries will say "unable to start" until we start getting the other peers connected on 1.0.9.7.
You can try deleting your peers.dat, and restarting the hot sanc after you upgrade.

Also, if some people could please upgrade their Prod instance and just verify everything works.  I realize this is going to be a little messy.

I will be gone for about 6 hours...

Hi,
Rob I'm thinking that something is wrong with it.
I am on 1097. Win and Linux.
In linux headless it is normal. Starts with setgenerate true 1 and you must just unlock it.
But in Win it didn't work for me.
On boot it asks for PWD and after inserting it does nothing.
Wallet is locked and not generating BBP. When I do it manually it works, but not automatically.
getinfo:

  "version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 7332481.00093010,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 15388,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 0.02513946871654256,
  "testnet": true,
  "keypoololdest": 1506015302,
  "keypoolsize": 1012,
  "unlocked_until": 0,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

and getmininginfo

  "blocks": 15388,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 28.7044849880676,
  "difficulty_pow": 0.2513946871654256,
  "difficulty": 28.7044849880676,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 19290821.32796781,
  "hashps": 75.48933921421167,
  "minerstarttime": "03-04-2018 20:02:50",
  "hashcounter": 7428,
  "pooledtx": 0,
  "testnet": true,
  "chain": "test",
  "biblepay-generate": false,
  "poolinfo1": "Failed to sign CPID signature (unlock wallet)?; ",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 14,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false

And using genproclimit more than 1 is working for me. When I use e.g. setgenerate true 12 cpu is "heating" more.

In prod version is asking for PODC pwd on boot and PODC tab is there too.
So can we try associate in prod? is it live now?

152

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

« on: March 04, 2018, 01:00:12 AM »

Same for me. Didn't get tasks on android for 2 days. I reinstalled boinc on my phone but didn't helped. It looks that we just must wait. But that's bad for me, because my Nexus 4 was my best "computer"

I've received two tasks on one of my mobile phones since yesterday. It looks they're slowly releasing them.
Edit: I've found that these new tasks are 4 hours. Old tasks on this phone was 2 hours.

153

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

« on: March 04, 2018, 12:53:00 AM »

Where do I find this new version?  The new website only has up to 1.0.9.2b.

It look, that it is just bad "label". It is still not corrected, but after download it is the newest version.

154

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

« on: March 03, 2018, 01:56:33 PM »

I can't get new tasks from rosetta@home on my Android phone.  I tried seti@home and from them I do get tasks, so I think it's related to rosetta and not Boinc.

Does anyone else have the same problem? Maybe they don't always have tasks for Android phones?

About their server: I looked at this page: 

I see now that it says that for 'Rosetta for Android' there are 0 'not sent tasks'. So that means that they are 'empty' at the moment regarding Android tasks I guess?

Same for me. Didn't get tasks on android for 2 days. I reinstalled boinc on my phone but didn't helped. It looks that we just must wait. But that's bad for me, because my Nexus 4 was my best "computer"

155

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

« on: March 03, 2018, 01:52:44 PM »

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.

Wau. Thanks Rob. I was tried it right now and all works fine. (Windows, 1.0.9.5f)
And that pool unbanked function is great. Nice work.

156

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

« on: March 01, 2018, 04:29:10 PM »

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.

157

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

« on: March 01, 2018, 03:38:43 PM »

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?

158

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

« on: March 01, 2018, 02:50:54 PM »

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

159

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

« on: February 28, 2018, 02:02:37 PM »

Wow this is awesome, Thanks!!!!

Payout from last superblock without problem in old wallet with old magnitude... nice

160

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

« on: February 28, 2018, 01:01:29 PM »

Ok cool, we will see.


Who wants to test exec associate?  To refresh everyones memory it used to allow you to know if INVALID_CREDENTIALS works, Or ALREADY_IN_CHAIN, or the ability to re-associate with a new wallet. Could someone please thoroughly test those at least those 3 things?

Btw, to know if re-association works:  run exec datalist dcc first, copy the CPIDs row information to notepad.  Note how a certain BBP public address is associated with the CPID at that time.  Then reassociate the CPID with a new public biblepay key (by replacing wallet.dat with a new wallet).  Then wait 6 confirms, then type exec datalist dcc again.  Verify that Only One Row exists for the cpid (as last most recent row wins in BBP) also verify the new Address is now associated with the CPID.  Then if you want maybe put it back to your old wallet if its a good cpid.

Youll need 10 BBP in the new wallet to perform reassociations.

Ok. I've tested it.
First associate without force and it works: ALREADY ON CHAIN
Tan with force (at block 11320): Successfully advertised DC-Key. ....
after 6 blocks changed my address from yfvTaGZakXWsLqyTCSZRG3kqabY6WYhFym to yZYt9boPur9vMLC5CPrWuiwXQ2XzzpXMVJ
with exec podcupdate had UTXO and taskweight at 100 in a block
magnitude at 0.
checked with exec datalist dcc and looks OK.
BTW you can check your wallet easier in rosetass profile URL (it changed too)
Then jumped back to my old testnet wallet without problem. Thanks God it works without problem

161

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

« on: February 28, 2018, 12:04:52 PM »

Mini update on the Zotac vs the Ryzen:  Dont give up on the Zotac, its really starting to shine now, believe it or not.
Zotac RAC 460, Ryzen RAC 710!  That means zotac is doing 65% of the RAC of a ryzen, yet it costed less than half and its wattage is 1/10th that of the ryzen.  It may actually prove to be "the winner" in the end...

Rob i think that something is wrong with your Ryzen.
Look at e.g. Togos or Klondikes comupters. They have more Ryzens 1700 and theirs Ryzens RAC is a lot higher than yours. And it is not caused by time... because they starts to "compute" with them only few days ago. And it looks that you have more powerful CPU (1700x).

162

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

« on: February 27, 2018, 01:48:16 PM »

I have another idea though.  I can make the pool offer free associations for boinc users.  So if coinomi cant do it, we can do it from the pool.  The pool can pass the info into the rpc command and broadcast it and destroy the credentials, so that works!  Problem solved either way...

The GUI of the pool can just display the result of the burn, and the pool can pay the 1bbp fee.

Actually I think to accomodate the unbanked, Ill work on that before March 15th.

That would be great.
Many thing was done (thanks Rob) and it seems that everything is going well.
What else remains to do before March 15?

bottomline
Rob thanks for correcting the wallet window size. Now it's great.
And is somewhere a list of all exec commands? (someone asks about it here before)

163

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

« on: February 27, 2018, 01:26:41 PM »

Thats the main benefit of course.  You dont have to have a BBP balance, and you dont have to run the controller wallet.

Meaning a tiny ARM cell phone in Ethiopia could potentially buy a loaf of bread!  Once we have coinomi!

However I warn you, if anyone finds a way to exploit the unbanked feature, we will most certainly and quickly reward .75 to the unbanked side, and that will take care of the exploit in a jiffy.  For now its 1 * utxo weight * 1 * task weight * RAC = Magnitude for the unbanked.

Ok, but how do you join your rosetta acc to wallet in Coinomi (if it will be)? Is it enough to change your "web page" in rosettas acc? I see that there is my controller wallet written.
And I really hope, that no one will exploit it. It would be big disadvantage for "normal" users.

164

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

« on: February 27, 2018, 01:04:20 PM »

If you have a sufficient BBP balance (50K+) there is no benefit to dividing accounts.  In fact, it would hurt you since you'd then have to run two separate wallets to account for the different rosetta accounts (as I understand it).  But the first part I'm confident of, no reason to run "unbanked" if you have 50K+ BBP.

But other reason to be "unbanked" (even if you have 50k) is that you don't have  24/7 server for controller wallet

165

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

« on: February 27, 2018, 12:54:18 PM »

You just must not have any non-arm processors and non-blank processors on the same CPID, in order to not be disqualified.

OK. Are these my findings good?:
1. If I want to have ARM based devices unbanked and PC's normal I must have at least two rosettas accounts.
2. It is no problem to join two rosetta acc to one BBP wallet with exec associate. (I didn't try it)
3. My ARM based Galaxy S7 can't be in unbanked acc because it has blank CPU type. (So it will be safer to try every phone outside unbanked acc to not disqualify myself)