Bible Pay

Recent Posts

Pages: 1 2 3 4 5 6 [7] 8 9 10
61
We dont need a pool, because the boinc infrastructure is already pooling the RAC for us. 

Id rather simplify the infrastructure than make it more complicated.

Regarding the Gridcoin pool that T-mike mentioned, they have a pool because they dont have enough blocks per day to pay the researchers.  We dont need a pool, because we airdrop the payment once per day.

Regarding mobile devices, we may be able to add a feature to not require PODC updates on tablets and smartphones - but thats still in the wish list - I have not looked at that yet.

Jaap, regarding one thread using too much power, I already made it sleep 200ms between iterations, it could be that you are running this on a low power machine, I suppose I can put in more granular control over this to see if this can be improved.  Right now on my windows dev machine, Im running rosetta 6 tasks : taking 50% of the cpu, the plain vanilla biblepay on 1 thread is taking 13% of the cpu, and its hashing at 270hps in testnet.  So of course we have to consider the fact that we *do* want it hashing on 1 thread so we have a baseline level of average security.  But nevertheless, Ill add a setting to see if we can control the sleep better, and, have it actually attempt to sleep more often - there is also something that I need to look at for the miner process as far as CPU priority - it might be set to high and not normal, meaning that on certain machines its not listening to your wishes, ill check into all that today.

I think what will end up with the regular pool, is I have no intention on taking it down - I still want to make it a place for "Biblepay Central", for Reports, for Orphan related letter writing and functions, but the heat-mining pool might be removed.  If we keep compatibility with the heat mining side, which I believe we have done so far, I may let it run and see what kind of interest we have and what the numbers look like, but most likely with everyone running on one thread, it wont be necessary to have a pool for heat mining and I may end up shutting that feature down.

At that point we would be fully Rosetta decentralized, with no pools.

I mainly mentioned the pool because it allows you to perform DC without having to stake, in our case it allows you to not need a controller wallet on 24/7. But if you can exclude the UXTO validation for phones and tablets that would work too.
62
Hi.
I was fighting with this too :)
I have ordered "weak" linux based VPS for 24/7 wallet but I wanted to run boinc there too.
So, my solution is: run biblepay with setgenerate true 1. Of course it consumes more than 90% of CPU :) so rosetta won't work. But than I install "cpulimit" (apt-get install cpulimit). It is very useful for this. Than you can usse it with command like this: "cpulimit -b -l 15 -m -p 1607" what means allow PID nr 1607 to spend max 15% of CPU. After this my BBP process consumes 15-20% of CPU and rosetta eats rest to 100 ;)

And shared wallet was of my thought too. What about creating some Rosetta/BBP pool? Rob will it be possible to change pool to handle this?

We dont need a pool, because the boinc infrastructure is already pooling the RAC for us. 

Id rather simplify the infrastructure than make it more complicated.

Regarding the Gridcoin pool that T-mike mentioned, they have a pool because they dont have enough blocks per day to pay the researchers.  We dont need a pool, because we airdrop the payment once per day.

Regarding mobile devices, we may be able to add a feature to not require PODC updates on tablets and smartphones - but thats still in the wish list - I have not looked at that yet.

Jaap, regarding one thread using too much power, I already made it sleep 200ms between iterations, it could be that you are running this on a low power machine, I suppose I can put in more granular control over this to see if this can be improved.  Right now on my windows dev machine, Im running rosetta 6 tasks : taking 50% of the cpu, the plain vanilla biblepay on 1 thread is taking 13% of the cpu, and its hashing at 270hps in testnet.  So of course we have to consider the fact that we *do* want it hashing on 1 thread so we have a baseline level of average security.  But nevertheless, Ill add a setting to see if we can control the sleep better, and, have it actually attempt to sleep more often - there is also something that I need to look at for the miner process as far as CPU priority - it might be set to high and not normal, meaning that on certain machines its not listening to your wishes, ill check into all that today.

I think what will end up with the regular pool, is I have no intention on taking it down - I still want to make it a place for "Biblepay Central", for Reports, for Orphan related letter writing and functions, but the heat-mining pool might be removed.  If we keep compatibility with the heat mining side, which I believe we have done so far, I may let it run and see what kind of interest we have and what the numbers look like, but most likely with everyone running on one thread, it wont be necessary to have a pool for heat mining and I may end up shutting that feature down.

At that point we would be fully Rosetta decentralized, with no pools. 

63
Hi.
I was fighting with this too :)
I have ordered "weak" linux based VPS for 24/7 wallet but I wanted to run boinc there too.
So, my solution is: run biblepay with setgenerate true 1. Of course it consumes more than 90% of CPU :) so rosetta won't work. But than I install "cpulimit" (apt-get install cpulimit). It is very useful for this. Than you can usse it with command like this: "cpulimit -b -l 15 -m -p 1607" what means allow PID nr 1607 to spend max 15% of CPU. After this my BBP process consumes 15-20% of CPU and rosetta eats rest to 100 ;)

And shared wallet was of my thought too. What about creating some Rosetta/BBP pool? Rob will it be possible to change pool to handle this?

In testnet we use what's call hot sanctuaries where the controller wallet is on the same machine as the Sanctuary. Once in production, you should really have you wallet on your home computer, never run your wallet on the VPS!

@Rob: I think we will need something like the gridcoin pool for mobile devices or have it in the code if it sees an arm processor to drop the UXTO validation. But then I would check to see if more than 10 arm processors are coming from the same IP to stop people from abusing the lowered requirements.
64
Yeah, I'm using the latest wallet and BOINC on my windows pc now. But I can't mine and use BOINC at the same time, because the wallet will use too much of the cpu-cycles and BOINC stops processing.

I don't know how to tweak the settings so that I can use both.

That also brings me to an other question about poor people all over the world using their phone to mine BBP (which I think will be a great application for Biblepay). How would one go about this? Would one person have a wallet running somewhere 24/7, and other people (with phones and tablets) would be running BOINC, and the person with the wallet would divide the collected BBP? Just thinking out loud.

Because I always liked the idea of 'one-click-mining', especially in combination with mobile phones and tablets, because even though - for example - a lot of people in Afrika are poor, a lót of them have a phone (although I don't know how many have smartphones).

Are you using Windows or Linux? In Advanced View->Options->Usage Limits of BOINC Manager you can set the usage for BOINC. I think Rob can fix the wallet to mine less but it's ok for for now. You can also use Oribs's method to limit the cpu usage on linux.

You can also try this for windows: http://mion.faireal.net/BES/

I wouldn't worry about it too much though, Rob will most likely fix it in the next update.
65
Yeah, I'm using the latest wallet and BOINC on my windows pc now. But I can't mine and use BOINC at the same time, because the wallet will use too much of the cpu-cycles and BOINC stops processing.

I don't know how to tweak the settings so that I can use both.

That also brings me to an other question about poor people all over the world using their phone to mine BBP (which I think will be a great application for Biblepay). How would one go about this? Would one person have a wallet running somewhere 24/7, and other people (with phones and tablets) would be running BOINC, and the person with the wallet would divide the collected BBP? Just thinking out loud.

Because I always liked the idea of 'one-click-mining', especially in combination with mobile phones and tablets, because even though - for example - a lot of people in Afrika are poor, a lót of them have a phone (although I don't know how many have smartphones).
Hi.
I was fighting with this too :)
I have ordered "weak" linux based VPS for 24/7 wallet but I wanted to run boinc there too.
So, my solution is: run biblepay with setgenerate true 1. Of course it consumes more than 90% of CPU :) so rosetta won't work. But than I install "cpulimit" (apt-get install cpulimit). It is very useful for this. Than you can usse it with command like this: "cpulimit -b -l 15 -m -p 1607" what means allow PID nr 1607 to spend max 15% of CPU. After this my BBP process consumes 15-20% of CPU and rosetta eats rest to 100 ;)

And shared wallet was of my thought too. What about creating some Rosetta/BBP pool? Rob will it be possible to change pool to handle this?
66
Yes, since we are not POS, I suppose we would need to program some things in to "unlock for staking only" etc, but for now, yes it has to be unlocked for PODC updates as not only is it sending you a coinstake with UTXO in it, but there is a transaction fee in that transaction for the Task Transmission.
So, that was my problem. It is a must-have to have option "unlock for PoDC only".
I am afraid to have my wallet on 24/7 server and if it should be unlocked it is even worst :)
Now I ordered VPS for testnet, but I am worried to unlock my wallet with command line. Ok there is option to delete bash history, but :)
It is possible to implement function "unlock for PoDC only" to options, or even better will be unlocked for PoDC everytime?
EDIT: maybe option "unlock for PoDC" may unlock wallet for PoDC without need to write password and run setgenerate true 1 automatically.

Next question :) Do I understand it correctly, that for now is 24/7 control wallet must-have even for mobile phone?
67
And have same question like jaapgvk.
****
One (minor) thing: the 'setgenerate 1' option makes the wallet hash at the old speed again (not 1%) on both the linux and windows wallets. I think it was also the case with the previous version.
So, to be clear: with the current wallet, when I do 'setgenerate 1 true', on my quadcore 4 thread system, I'm using about 25% of my CPU.
****
I am on linux and last two versions are back on 1 full thread (1.0.9.2 was 1% of all processor).

Thank and excuse my english. I beleve that you understand my question :).

Yeah, I'm using the latest wallet and BOINC on my windows pc now. But I can't mine and use BOINC at the same time, because the wallet will use too much of the cpu-cycles and BOINC stops processing.

I don't know how to tweak the settings so that I can use both.

That also brings me to an other question about poor people all over the world using their phone to mine BBP (which I think will be a great application for Biblepay). How would one go about this? Would one person have a wallet running somewhere 24/7, and other people (with phones and tablets) would be running BOINC, and the person with the wallet would divide the collected BBP? Just thinking out loud.

Because I always liked the idea of 'one-click-mining', especially in combination with mobile phones and tablets, because even though - for example - a lot of people in Afrika are poor, a lót of them have a phone (although I don't know how many have smartphones).
68
For example, if your first machine is running 10 tasks, and lets say WU 98651 was started at unix time 15345321, then your controller wallet will ask what time did that task start, once it receives 15345321 it will send that into the chain as a PODC update (along with a list of every other task it is working and timestamps to save size).  (It queries the timestamps from the Rosetta task themselves, not from the XML file). Then the Sanctuary will compare the XML sent_time, to that timestamp to ensure they agree.  This way if someone on the Rosetta side were to mass validate tasks or alter timestamps, or insert random records in the table to try to get someone paid, those would fail because we would have already sent our timestamps into our chain before the alteration.

Oh...I understand now. That's a great idea!
69
Ok. thanks. And the wallet must be unlocked?

Yes, since we are not POS, I suppose we would need to program some things in to "unlock for staking only" etc, but for now, yes it has to be unlocked for PODC updates as not only is it sending you a coinstake with UTXO in it, but there is a transaction fee in that transaction for the Task Transmission.

70
Rob, sorry, I'm still having difficulty understanding. I see the xml file, can you show exactly what your comparing? (I know it's the timestamp but which one to which one?)
For example, if your first machine is running 10 tasks, and lets say WU 98651 was started at unix time 15345321, then your controller wallet will ask what time did that task start, once it receives 15345321 it will send that into the chain as a PODC update (along with a list of every other task it is working and timestamps to save size).  (It queries the timestamps from the Rosetta task themselves, not from the XML file). Then the Sanctuary will compare the XML sent_time, to that timestamp to ensure they agree.  This way if someone on the Rosetta side were to mass validate tasks or alter timestamps, or insert random records in the table to try to get someone paid, those may fail (if we catch one of the circumstances) - because we would have already sent our timestamps into our chain before the alteration.

Pages: 1 2 3 4 5 6 [7] 8 9 10