Pages:
Author

Topic: BiblePay - New Coin Launch - Official Thread - page 33. (Read 119845 times)

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
The script is from 2010. Maybe even earlier. It has good security, but it's not a script for multithreading. I'm working 10 years on multithreading windows and ubuntu. You destroy people who help BBP.
Not sure what you are referring to, but BiblePay was just started this year.  Our algorithm is not a copy of any other algorithm.


You know exactly what this script is based on. Let's make a team, let's do something positive. Too much anger, it is not needed. Inblue showed something. This script is old. On windows you can fix it x times. Your annoyance is bad. You can not do it yourself, because you do not have time. Everyone will go away with this attitude ...
Listen, I said it earlier and I meant it: the algorithm is NEW, its multi-threaded, and when we launched with X11 originally, it did use all of the processor.  It was not until it became a node based algorithm (f7000) when that changed.

You said something about a script being from 2010.  First of all, we have 3 platforms and 3 languages, so again, I dont even know what you are talking about when you say Script.  Even bitcoins tx are a script.  We have scripts in the command shell, we have scripts in the pool, we have c# scripts.  So your ambiguous comment makes no sense here.

Explain exactly what you mean before making a baseless negative comment.





full member
Activity: 126
Merit: 100
Thanks for sharing. A really mysterious coin. Roll Eyes
Rule change without any notice is really bad.



The only thing I did was restrict heavy pool users from sending in more than 200 solutions per IP per 10 minutes, which technically didnt change anything yet
It changed a lot... multicore cpu are useless now again... you didnt see this? And if it didn't changed anything so why hps2 droped?
P.S. can you explain to diffrent things you said about running multi-deamon? What changed that you change you mind?

What part of biblepay have you contributed to that provides value Oliwer?

Showing bugs on wallet/pool hps/hps2. But devs dont care about it...
And ofc you don answer simple question as always... because it's to.... ?
full member
Activity: 1179
Merit: 131
I think my pool is ready to go live, this might alleviate some of the arguing and complaints (or generate more if it doesn't work right!  Grin)   The problem with having only 1 pool for a coin is that the pool owner becomes a lightning rod for problems.  People automatically associate problems with pool with the coin, and vice versa.  My pool is in beta so mine at your own risk, but there is no hashrate or share limit.  Its running on AWS so I can adjust the resources as necessary but since I don't know what sort of load will be thrown on the server just keep in mind I might need to do some tweaking in the next day or so.  I got the open source code from Bible_Pay and implemented it via his instructions so it looks pretty much the exact same as his pool.  The only real difference is there is no letter writing to the orphans, so no fees associated with that, but there is a 2% mining fee to keep the lights on.  It might be beneficial to somehow implement some of the letter writing on my pool in the future but I will talk to Bible_Pay about that.

So without further ado, Jesus said “Come after me, and I will make you fishers of men."  Nsummy says, I will make you miners of men!

https://minersofmen.com

poolport=80  
pool=http://pool.minersofmen.com  
workerid=insertWorkerUsernameHere

Great job!  Thanks.



A couple of questions.

1. Is there a way to change how often the worker hashrate, shares, etc is updated?  It seems like its going hours between updates on my site.  Is that what the poolthreshold variable is? 

2.  What should be the default page for the site?  I have it set to pool.ashx but I don't think that is right, as it just takes me to the login screen instead of the main page.
newbie
Activity: 89
Merit: 0
The script is from 2010. Maybe even earlier. It has good security, but it's not a script for multithreading. I'm working 10 years on multithreading windows and ubuntu. You destroy people who help BBP.
Not sure what you are referring to, but BiblePay was just started this year.  Our algorithm is not a copy of any other algorithm.


You know exactly what this script is based on. Let's make a team, let's do something positive. Too much anger, it is not needed. Inblue showed something. This script is old. On windows you can fix it x times. Your annoyance is bad. You can not do it yourself, because you do not have time. Everyone will go away with this attitude ...
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
I think my pool is ready to go live, this might alleviate some of the arguing and complaints (or generate more if it doesn't work right!  Grin)   The problem with having only 1 pool for a coin is that the pool owner becomes a lightning rod for problems.  People automatically associate problems with pool with the coin, and vice versa.  My pool is in beta so mine at your own risk, but there is no hashrate or share limit.  Its running on AWS so I can adjust the resources as necessary but since I don't know what sort of load will be thrown on the server just keep in mind I might need to do some tweaking in the next day or so.  I got the open source code from Bible_Pay and implemented it via his instructions so it looks pretty much the exact same as his pool.  The only real difference is there is no letter writing to the orphans, so no fees associated with that, but there is a 2% mining fee to keep the lights on.  It might be beneficial to somehow implement some of the letter writing on my pool in the future but I will talk to Bible_Pay about that.

So without further ado, Jesus said “Come after me, and I will make you fishers of men."  Nsummy says, I will make you miners of men!

https://minersofmen.com

poolport=80  
pool=http://pool.minersofmen.com  
workerid=insertWorkerUsernameHere

Great job!  Thanks.

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
Thanks for sharing. A really mysterious coin. Roll Eyes
Rule change without any notice is really bad.



The only thing I did was restrict heavy pool users from sending in more than 200 solutions per IP per 10 minutes, which technically didnt change anything yet
It changed a lot... multicore cpu are useless now again... you didnt see this? And if it didn't changed anything so why hps2 droped?
P.S. can you explain to diffrent things you said about running multi-deamon? What changed that you change you mind?

What part of biblepay have you contributed to that provides value Oliwer?
newbie
Activity: 42
Merit: 0

https://minersofmen.com

poolport=80  
pool=http://pool.minersofmen.com  
workerid=insertWorkerUsernameHere

Thanks for this, will try it today. Please share yours or the pool's donation address.
I'm running tools for some other early coins as well, at my expense, I know the cost associated with it. Happy to contribute.
full member
Activity: 462
Merit: 103
@inblue I am sorry to see you go, you have been a valuable member of the forum, appreciate your help here so far.

@bible_pay I am sure there's a big misunderstanding here, inblue has been very active here and his/her hash probably helped the pool mine more blocks in which all of us smaller miners benefitted from. He/She could've kept the 'hack' to themselves but the whole experiment was posted here for all to see and also he/she has been more valuable than 80% of the accounts here including me.

Please reserve resorting to banning someone only if the account is malicious or useless, I personally don't see anything inblue posted here as disruptive to the community, inblue has every right to be on the forum. This is a decentralized project which will go autonomous come December, by casting away useful users, the community will only become worse.

If anyone's setting up a new pool, I am happy to distribute the hash to it.

- Live and Let Live

Thank you very much for the kind words, nananaminer. Stay awesome.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
The script is from 2010. Maybe even earlier. It has good security, but it's not a script for multithreading. I'm working 10 years on multithreading windows and ubuntu. You destroy people who help BBP.
Not sure what you are referring to, but BiblePay was just started this year.  Our algorithm is not a copy of any other algorithm.
newbie
Activity: 89
Merit: 0
Ryzen can give 700-1000 shares, tested. Even btc goes forward because someone is working on it.
full member
Activity: 1179
Merit: 131
I think my pool is ready to go live, this might alleviate some of the arguing and complaints (or generate more if it doesn't work right!  Grin)   The problem with having only 1 pool for a coin is that the pool owner becomes a lightning rod for problems.  People automatically associate problems with pool with the coin, and vice versa.  My pool is in beta so mine at your own risk, but there is no hashrate or share limit.  Its running on AWS so I can adjust the resources as necessary but since I don't know what sort of load will be thrown on the server just keep in mind I might need to do some tweaking in the next day or so.  I got the open source code from Bible_Pay and implemented it via his instructions so it looks pretty much the exact same as his pool.  The only real difference is there is no letter writing to the orphans, so no fees associated with that, but there is a 2% mining fee to keep the lights on.  It might be beneficial to somehow implement some of the letter writing on my pool in the future but I will talk to Bible_Pay about that.

So without further ado, Jesus said “Come after me, and I will make you fishers of men."  Nsummy says, I will make you miners of men!

https://minersofmen.com

poolport=80  
pool=http://pool.minersofmen.com  
workerid=insertWorkerUsernameHere
newbie
Activity: 42
Merit: 0
@inblue I am sorry to see you go, you have been a valuable member of the forum, appreciate your help here so far.

@bible_pay I am sure there's a big misunderstanding here, inblue has been very active here and his/her hash probably helped the pool mine more blocks in which all of us smaller miners benefitted from. He/She could've kept the 'hack' to themselves but the whole experiment was posted here for all to see and also he/she has been more valuable than 80% of the accounts here including me.

Please reserve resorting to banning someone only if the account is malicious or useless, I personally don't see anything inblue posted here as disruptive to the community, inblue has every right to be on the forum. This is a decentralized project which will go autonomous come December, by casting away useful users, the community will only become worse.

If anyone's setting up a new pool, I am happy to distribute the hash to it.

- Live and Let Live
full member
Activity: 126
Merit: 100
Thanks for sharing. A really mysterious coin. Roll Eyes
Rule change without any notice is really bad.



The only thing I did was restrict heavy pool users from sending in more than 200 solutions per IP per 10 minutes, which technically didnt change anything yet
It changed a lot... multicore cpu are useless now again... you didnt see this? And if it didn't changed anything so why hps2 droped?
P.S. can you explain to diffrent things you said about running multi-deamon? What changed that you change you mind?
newbie
Activity: 89
Merit: 0
The script is from 2010. Maybe even earlier. It has good security, but it's not a script for multithreading. I'm working 10 years on multithreading windows and ubuntu. You destroy people who help BBP.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
Thanks for sharing. A really mysterious coin. Roll Eyes
Rule change without any notice is really bad.

Wait a minute here- the entire algorithm is public.  There were NO rule changes.  

The only thing I did was restrict heavy pool users from sending in more than 200 solutions per IP per 10 minutes, which technically didnt change anything yet.
That was on the pool side, to ensure the pool is not overrun by linux hackers.

When I said I raised the Diff, I was referring to the minimum difficulty share the pool hands out, which is not a global rule change, its the pool owners business.

This community has been transparent from the beginning.  I hope everyone can see that.


full member
Activity: 462
Merit: 103
Thanks for sharing. A really mysterious coin. Roll Eyes
Rule change without any notice is really bad.

Welcome to BBP club, where 9 out of 10 times rules are changed without any notice, lol.

I thought you were leaving?  If you are going to continue to post trash here, Im going to have to recommend you to be banned.


Yeah I am leaving. But feel free to ban me. And what I said is truth, not trash, sorry.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
Thanks for sharing. A really mysterious coin. Roll Eyes
Rule change without any notice is really bad.

Welcome to BBP club, where 9 out of 10 times rules are changed without any notice, lol.

I thought you were leaving?  If you are going to continue to post trash here, Im going to have to recommend you to be banned.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
I don't get it, what did I say wrong? Or what am I doing wrong?

Um, I don't think you understand the concept of mining pools. My computers find blocks for which other pool miners get their share of the reward! And because of my computers, blocks are found more often by the pool! Having big miners can only benefit a pool!!!

But feel free to play an admin in a decentralized project, shut down my account if you want, I don't care. I think I have helped immensely in this project, but I am always getting bashed by you. I think it's time to say goodbye.

I'm sorry you feel that way, and don't want to see you go.  I know you are very helpful to the other users, and want to see the project succeed.

On my side of the fence, I have to create an algorithm that is solved fairly for the users and I can't have any gross advantages and we have to work together to remove them, otherwise we risk the integrity of this whole project.

I view this discrepancy as one that is not to be exploited but to be patched with an emergency patch. 
I am hoping I have everyone on board to work with me toward the common goal not against it.
We cant have a gross discrepancy in the pool for a select few who figure out how to exploit the algorithm by creating multiple running nodes per linux instance.
In the end we fool ourselves, because those nodes are weaker than the full sanctuaries (where ultimately we want to measure proof-of-service) and have them be external nodes servicing 3000 external connections.

So for now, I am going to limit shares solved by IP to 200 and lets work on a solution to this issue to make it fair for everyone to hash biblehashes.

Make it fair for everyone? How is it not fair now? All the instructions for setting up multiple daemons could be found in this thread, I posted it clearly, as well as someone else who was setting it up later. The instructions are at at a public disposal and they could be posted now again if needed. They could also be made into a wiki page.

It's not some hidden secret exploit; you first suggested us to try running multiple daemons on a machine and even helped with it. Actually this is the first time you refer to it as an exploit. Also the first time where you say you want to issue a patch for it. Earlier you were saying that it's fine and that it's how it's supposed to be, because it's better to have full nodes etc. Repeated many times. Exactly this was the reason I did it, because it was not going to change and that it was not an exploit, but a "feature", and also because it's simply easier to manage one bigger computer than 10 small ones, while giving notably better rewards. I would not intentionally do something bad to the coin or the pool, but I am being treated as a bad actor, accused of trying to "steal" others' money.

Also, as oliwer said, other pool miners are doing the same, so even though it's not all of them, that seems fair enough, because others probably didn't care enough to read the forum or have the trouble of setting it up. If someone reads this now and wants to setup multiple daemons, I would gladly instruct them on how to do that. I am not hiding anything or doing something sneaky, immoral etc. And because everyone can run multiple daemons (or already does), a fact is that there is mathematically no disadvantage to anyone while my computers are running, because I increase the pool block find frequency, while in turn I get a % of the rewards. Smaller reward per block for everyone, but more blocks found, so it all irons out to the same rewards for everyone, whether I am mining or not. The only difference is that the pool finds more blocks and that the pool has a lower luck factor, which are both advantages. Not to mention that I am barely even in the top 10 miners on the pool. You can see for yourself in the block distribution history.

That will force me to try solo mining.

Yeah, me too, I'm out. Btw, you will earn 6% more by solo mining. Smiley

Alright, thanks for sharing.  I dont have the bandwidth to continue arguing with you.  Id rather work on the positive aspects anyway.

We will work the kinks out over the long term. 

full member
Activity: 239
Merit: 250
Thanks for sharing. A really mysterious coin. Roll Eyes
Rule change without any notice is really bad.
full member
Activity: 462
Merit: 103
but I am being treated as a bad actor, accused of trying to "steal" others' money.
This was his word's, they are really strange, because as i remember he wanted to put your "way" how to run multi-deamon to wiki and now this... LOL

Yes, actually, here is the relevant quote and the wiki link:




RESULTS

All values are taken after about half an hour of mining. Type of computer: 10-CPU Xeon Skylake.
Note that for the pool to register more than one instance, every instance has to be a different worker.

Running 1 biblepayd at genproclimit 20:
HPS: 52k
HPS2: 29k


Running 2 biblepayd at genproclimit 10 each:
HPS: 29k + 28k = 57k
HPS2: 30k + 30k = 60k


Running 4 biblepayd at genproclimit 5 each:
HPS: 15k + 14.5k + 14.5k + 14.5k = 58.5k
HPS2: 19k + 22k + 19k + 20k = 80k


Running 10 biblepayd at genproclimit 2 each:
HPS: 6k x 10 = 60k
HPS2: 12k x 10 = 120k


So the conclusion is obvious - the HPS is about the same regardless of the number of daemons, but HPS2 rises considerably.



The next test I did was running 10 daemons on 10 separate 1-CPU machines (the CPU is the same as in the 10-CPU machine) and also genproclimit 2 as before.

This scenario gives:
HPS: 10k x 10 = 100k
HPS2: 17k x 10 = 170k


So this is even more than if you run 10 daemons on the same machine, which is 60k HPS and 120k HPS2, as noted above.



Summary

Solo mining
One 10-CPU machine with 1 miner gives 52k HPS.
One 10-CPU machine with 10 miners gives 60k HPS.
Ten 1-CPU machines with 1 miner each give 100k HPS.


Pool mining
One 10-CPU machine with 1 miner gives 29k HPS2.
One 10-CPU machine with 10 miners gives 120k HPS2.
Ten 1-CPU machines with 1 miner each give 170k HPS2.


Thank you so much for all that.    Smiley

Let me archive this on our wikipedia page.

Wiki Link:
http://wiki.biblepay.org/Multiple_Instances






Heh, you can see everything I went through to test different combinations and write down all results publicly and even format it nicely, and what do I get, lol.
Pages:
Jump to: