Bible Pay

Recent Posts

Pages: 1 2 [3] 4 5 6 7 8 9 10
21
Icon's would definitely be nice.  That would be a nice cosmetic addition to the wallet.

Maybe you can reach out to Togo and see what kind of help he needs in recruiting a co-developer so we can have a dedicated testnet branch with features like that merged in for testing?
When we are talking about visual. I don't know if it is only my problem, but I'm not able to reduce wallet window size below some px (It is approx 90% of my screen height) And in testnet I'm unable to reduce it below maybe 110% of screen size, so I'm unable to see status bar and I must maximize my window to see everything. I have Win10. It is only my problem or it is common? Is possible to solve it?
22
Yes, I tried exec asssociate with and without force multiple times and it continued "INVALID_CREDENTIALS", both when manually typing and cut and paste from the original file I used as well as trying the form on the main wallet as well as debug.  I didn't understand what you meant by "retry association" on [email protected] site, didn't see a link that was similar to that which is why I tried Quit and Rejoin Team Biblepay.

The only solution was restoring an old wallet backup from my testnet backups I maintain, works fine.  So not sure if there is a bug out there or if doing what you intended with retry association would have been sufficient but thought you should know.
No wonder I was so confused!  I made the assumption the code was still working the way it was when I tested it last week.
So anyway when I added the podcupdate feature, it broke a couple of the return codes (or circumstances) inside the 'éxec  associate' feature.  So those are now fixed, and now people will see "ALREADY_IN_CHAIN" or "INVALID_CREDENTIALS" during the proper circumstances, in the next version.

Im checking in 1.0.9.4d now for linux if anyone wants to test that tonight.   Starting windows build over.

Lets check this out tomorrow when we have a chance to ensure reassociation works now.

Thanks for pointing out this bug!

23
Yes, I tried exec asssociate with and without force multiple times and it continued "INVALID_CREDENTIALS", both when manually typing and cut and paste from the original file I used as well as trying the form on the main wallet as well as debug.  I didn't understand what you meant by "retry association" on [email protected] site, didn't see a link that was similar to that which is why I tried Quit and Rejoin Team Biblepay.

The only solution was restoring an old wallet backup from my testnet backups I maintain, works fine.  So not sure if there is a bug out there or if doing what you intended with retry association would have been sufficient but thought you should know.

Oh your right, I just reproduced that with my cpid, something changed.

Let me debug that problem next...

24
That was actually one of my ARM single-board computers. Not an Android mobile or tablet. But since it is running Linux, although I was able to connect it to [email protected], I wasn't able to solve any task with it, since Rosetta does not support ARM on Linux (other boinc projects do). And I tried very hard :-)

In general, you cannot assume that any ARM processor is a mobile or tablet: there are very high-performance multicore ARM servers (e.g. https://cavium.com/product-thunderx-arm-processors.html), there is even a 99$ ARM notebook (https://www.pine64.org/?page_id=3707).

BUT, the fact that you cannot leverage Linux-based ARM machine in Rosetta protects us a bit.

Ok great, thanks!  Yeah, I added that ARM (with blank proc) to the list in a way that it wouldnt disqualify you as an unbanked individual.
Regarding someone with only arms, and running in high power mode with the benefit of no controller wallet, I think all they really gain is not having a controller wallet anyway, so big deal, as long as we get our 98% integrity rating for the rest of the farm, Im ok with that :).  But if you guys see any heinous advantage, please, raise it as an issue and we can then put a Magnitude limit on the ünbanked CPIDs.  Those ARM tablets still only receive the same compensation as the banked cpids, (except they arent staking any capital so they get a free 100% utxo weight).

25
Update on the next version - 1094c:

So I did a lot of expirimentation with the threading today, and have come to the conlcusion Jaap had a point, the wallet was using too much power even with the new settings in distributedcomputing mode.

So what I have done is in Distributed Computing mode the miner behaves slightly differently (in the next release).  It respects the CPU's thread priority meaning that it can run slower, and we now allow you to tweak the setting.

There will be a new setting called minersleep (the default is 0 for Prod and 250ms for Testnet).  If you set a numeric value you override it.
Now Im seeing about 10% proc usage by default, and when I raise the value, it does allow the machine to sleep more (down to more like 4% or so).

1094c is now out there for linux if anyone wants to expiriment.  This is a pretty minor change, so if you want to wait for the next release its no big deal.

Im compiling Windows now so we will have this to play with later tonight.

PS I did get the unbanked report working for the sanctuary validation system in unit test mode, but its not going to be ready til sometime tomorrow.

26
You won't have to ever quit Team Biblepay, it won't change any association business logic.
"The error continued", you mean Invalid Credentials?  - Answered Earlier.
If you change wallets, you should receive an "ALREADY IN CHAIN" message, once you enter the correct credentials.

Yes, I tried exec asssociate with and without force multiple times and it continued "INVALID_CREDENTIALS", both when manually typing and cut and paste from the original file I used as well as trying the form on the main wallet as well as debug.  I didn't understand what you meant by "retry association" on [email protected] site, didn't see a link that was similar to that which is why I tried Quit and Rejoin Team Biblepay.

The only solution was restoring an old wallet backup from my testnet backups I maintain, works fine.  So not sure if there is a bug out there or if doing what you intended with retry association would have been sufficient but thought you should know.
27
Rastiks I see your machine right above your other ARM has 1.9GB ram and a BLANK for the processor.  What machine is that?

That was actually one of my ARM single-board computers. Not an Android mobile or tablet. But since it is running Linux, although I was able to connect it to [email protected], I wasn't able to solve any task with it, since Rosetta does not support ARM on Linux (other boinc projects do). And I tried very hard :-)

In general, you cannot assume that any ARM processor is a mobile or tablet: there are very high-performance multicore ARM servers (e.g. https://cavium.com/product-thunderx-arm-processors.html), there is even a 99$ ARM notebook (https://www.pine64.org/?page_id=3707).

BUT, the fact that you cannot leverage Linux-based ARM machine in Rosetta protects us a bit.
28
One suggestion for the wallet to improve readability.  Could there be different mining categories?  So a Bible Icon for PoBH, a Church Icon for Sanctuaries and perhaps the atom (?) icon for PoDC?  And perhaps allow for these each to be shown  collectively under mining but also broken down by subcategory?

Icon's would definitely be nice.  That would be a nice cosmetic addition to the wallet.

Maybe you can reach out to Togo and see what kind of help he needs in recruiting a co-developer so we can have a dedicated testnet branch with features like that merged in for testing?

29
So I wasn't sure where"retry association" was, so I quit Team Biblepay, then rejoined.  But the error continued.  I was able to restore a previous wallet.dat file and it is correctly associated, but am unclear why the process would have failed on a new wallet (which is an unlikely situation to be in but...)

You won't have to ever quit Team Biblepay, it won't change any association business logic.
"The error continued", you mean Invalid Credentials?  - Answered Earlier.
If you change wallets, you should receive an "ALREADY IN CHAIN" message, once you enter the correct credentials.

30
One suggestion for the wallet to improve readability.  Could there be different mining categories?  So a Bible Icon for PoBH, a Church Icon for Sanctuaries and perhaps the atom (?) icon for PoDC?  And perhaps allow for these each to be shown  collectively under mining but also broken down by subcategory?
Pages: 1 2 [3] 4 5 6 7 8 9 10