BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[slovakia]

POOL GOT THIS BUG

multiple users "solved" same blocks in the pool

[joelles]

POOL GOT THIS BUG

multiple users "solved" same blocks in the pool

How do u know

[Lichtsucher]

After long hours of hard work and not enough sleep, I just finished the version of a set of unofficial Biblepay Ubuntu Deb files, available via Launchpad PPA:
https://launchpad.net/~lichtsucher/+archive/ubuntu/biblepay

There is also a wiki page for that:
http://wiki.biblepay.org/Ubuntu_Packages

I hope many users will find them useful

If you want to learn more about how to build these files for your own, please visit my github project for the "Biblepay deb builder":
https://github.com/Lichtsucher/biblepay-deb-builder

There is a proposal for that, too:
http://forum.biblepay.org/index.php?topic=88.0

[DayTripperSimon]

After long hours of hard work and not enough sleep, I just finished the version of a set of unofficial Biblepay Ubuntu Deb files, available via Launchpad PPA:
https://launchpad.net/~lichtsucher/+archive/ubuntu/biblepay

There is also a wiki page for that:
http://wiki.biblepay.org/Ubunut_Packages

I hope many users will find them useful

If you want to learn more about how to build these files for your own, please visit my github project for the "Biblepay deb builder":
https://github.com/Lichtsucher/biblepay-deb-builder

There is a proposal for that, too:
http://forum.biblepay.org/index.php?topic=88.0

Great, thank you!
I was also thinking of making packages, so I am very thankful for this.

Did you get the version right - I see on https://launchpad.net/~lichtsucher/+archive/ubuntu/biblepay
Package ▴    Version    Uploaded by
biblepay    1.8.0.2-xenial1    Lichtsucher (3 hours ago)
biblepay    1.8.0.2-trusty1    Lichtsucher (3 hours ago)

Version should be 1.0.8.2 ?

Best regards,
Simon

[Lichtsucher]

Did you get the version right - I see on https://launchpad.net/~lichtsucher/+archive/ubuntu/biblepay
Package ▴    Version    Uploaded by
biblepay    1.8.0.2-xenial1    Lichtsucher (3 hours ago)
biblepay    1.8.0.2-trusty1    Lichtsucher (3 hours ago)

Version should be 1.0.8.2 ?

Oh, you are right! I made that mistake yesterday night and hadn't seen it. Never write down version numbers when you are tired
I'm uploading a fixed version.

[capulo]

   Blocks Mined (24 hour period):   42 (21%)
nice...

i'm mining also xdag - some new cpu mineable coin... but yesterday there was huge increase of nethash... maybe our lovely botnet was moved there

[bible_pay]

POOL GOT THIS BUG

multiple users "solved" same blocks in the pool

The pool users solve Shares, not blocks.

The pool users are required to solve distinct nonces, so that cant be happening either.

Please elaborate what you are talking, or did you make this up because it felt good?

[slovakia]

After long hours of hard work and not enough sleep, I just finished the version of a set of unofficial Biblepay Ubuntu Deb files, available via Launchpad PPA:
https://launchpad.net/~lichtsucher/+archive/ubuntu/biblepay

There is also a wiki page for that:
http://wiki.biblepay.org/Ubuntu_Packages

I hope many users will find them useful

If you want to learn more about how to build these files for your own, please visit my github project for the "Biblepay deb builder":
https://github.com/Lichtsucher/biblepay-deb-builder

There is a proposal for that, too:
http://forum.biblepay.org/index.php?topic=88.0

whats different between your and this sudo add-apt-repository -y ppa:bitcoin/bitcoin

[bible_pay]

Did you get the version right - I see on https://launchpad.net/~lichtsucher/+archive/ubuntu/biblepay
Package ▴    Version    Uploaded by
biblepay    1.8.0.2-xenial1    Lichtsucher (3 hours ago)
biblepay    1.8.0.2-trusty1    Lichtsucher (3 hours ago)

Version should be 1.0.8.2 ?

Oh, you are right! I made that mistake yesterday night and hadn't seen it. Never write down version numbers when you are tired
I'm uploading a fixed version.

Wow, I think this is amazing... Does this mean its OK for me to have a daily release now for all linux users?  (Just kidding)...

So youve created a PPA for BiblePay??

This is awesome!

So, how much work do you have to go through when I push a release, or is it all automated?

[bible_pay]

Maybe you don't get my point. I think 3000+ users double check same hash numbers. I do not pretend I'm correct or that I understand. I just remember an old post of ByblePay saying multiple users "solved" same blocks in the pool.
Whatever is that botnet I think they use unique hash check code - it's open source. By my assumptions 100-200k unique hashes can beat our pool with 1 850 000 total hps. Anyway I continue to hoDL that machine in background HT cores with about 3100 hps. At some moment I'll hit 7000+ coins. Positive expectancy is because I'll not have fees and competitors aren't doing unique hash checks. If this is so then the most effective miner is solo machine. If I put 10 solo, then I'll increase the income by let's say 7 times not 10 (related to double hash checks between nodes).

Thanks!  Thats what I want to talk about- I didnt want people to get the impression you did technical testing and proved the pool was worthless.

So about 20 days ago, I did an actual SQL test, because I save all solutions in the database for a period of time (every hash solution, every nonce, every exec biblehash constuent, so I can replay the solution if I want), and I did find about 15% of the solutions were being repeated.

To fix that, I added the 14 pool addresses, and started enforcing distinct nonce solutions.  So now 100% of the solutions are distinct.

So no- no one is being awarded for the same solution anymore as anyone else.  If miner X solves share Z with nonce 150, no one else in that round is allowed to solve a share with nonce 150 (work is rejected and then they receive a new share).

[MIP]

I might put my hands on some cheap older hardware. What kind of CPUs do you judge better for mining BBP?

Xeons with high cache RAM?
Dual CPU Boards?
The more cores the better?
...?

Can you share your experiences?

So no- no one is being awarded for the same solution anymore as anyone else.  If miner X solves share Z with nonce 150, no one else in that round is allowed to solve a share with nonce 150 (work is rejected and then they receive a new share).

Nice work, thanks for your efforts. Let's hope things improve in the coming days.

[ride22]

I might put my hands on some cheap older hardware. What kind of CPUs do you judge better for mining BBP?

Xeons with high cache RAM?
The more cores the better?
...?

Can you share your experiences?

So no- no one is being awarded for the same solution anymore as anyone else.  If miner X solves share Z with nonce 150, no one else in that round is allowed to solve a share with nonce 150 (work is rejected and then they receive a new share).

Nice work, thanks for your efforts. Let's hope things improve in the coming days.

Hey,
I am compiling a list of CPUs and hash rates.  Let me know what you have and what you are getting.

[MIP]

Hey,
I am compiling a list of CPUs and hash rates.  Let me know what you have and what you are getting.

Sure, do you have plans to publish that compilation?

[slovakia]

ride22 do you know that results for solo and pool is different? 

[joelles]

I might put my hands on some cheap older hardware. What kind of CPUs do you judge better for mining BBP?

Xeons with high cache RAM?
The more cores the better?
...?

Can you share your experiences?

So no- no one is being awarded for the same solution anymore as anyone else.  If miner X solves share Z with nonce 150, no one else in that round is allowed to solve a share with nonce 150 (work is rejected and then they receive a new share).

Nice work, thanks for your efforts. Let's hope things improve in the coming days.

Hey,
I am compiling a list of CPUs and hash rates.  Let me know what you have and what you are getting.

Two of these


root@pfsense:~# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 60
model name      : Intel(R) Xeon(R) CPU E3-1246 v3 @ 3.50GHz
stepping        : 3
microcode       : 0x1d
cpu MHz         : 3699.882
cache size      : 8192 KB

----------------------------------------------------------------------------------------------


root@pfsense:~# ./biblepay/src/biblepay-cli getmininginfo
{
  "blocks": 26427,
  "currentblocksize": 7061,
  "currentblocktx": 21,
  "difficulty": 1066.92062028383,
  "errors": "",
  "genproclimit": 40,
  "networkhashps": 80315193138.7979,
  "hashps": 3981.752218012391,


pool

[DayTripperSimon]

root@pfsense:~# ./biblepay/src/biblepay-cli getmininginfo
{
  "blocks": 26427,
  "currentblocksize": 7061,
  "currentblocktx": 21,
  "difficulty": 1066.92062028383,
  "errors": "",
  "genproclimit": 40,
  "networkhashps": 80315193138.7979,
  "hashps": 3981.752218012391,


pool

40 threads! I wonder if would be better result with 8 (as you have 8 threads per cpu).
It's not clear do you have 1 machine with 2 x this cpu or 2 separate machines? If you have 1 dual machine, then I would set it to 16 threads.

[zthomasz]

Pool question ... what is the difference between a PhysicalMachine and a LogicalMachine?

I found some info online:

A physical machine is physical server, while a Logical Machine is a virtual machine/server - for example a VPS - that resides on a physical machine.

Another pool question ... what is "ElectricBill" ... and does it factor into the reward equation (hps/shares/etc = reward) for pool miners?

[bible_pay]

Pool question ... what is the difference between a PhysicalMachine and a LogicalMachine?

I found some info online:

A physical machine is physical server, while a Logical Machine is a virtual machine/server - for example a VPS - that resides on a physical machine.

Another pool question ... what is "ElectricBill" ... and does it factor into the reward equation (hps/shares/etc = reward) for pool miners?

All electric bill is, is a static calculation for fun that divides the logical hashing machines (in attempt to sum the total watts expended per month) by that factor to show the estimated electric bill (at 10 cents per kwh) per month for that number of logical miners.

Its not used for anything.

[bible_pay]

Please Everyone Read this:

http://wiki.biblepay.org/Proof_Of_Loyalty


This is what I am working on to stave off the botnet.

The idea here is to ensure we have the information explained in a clear manner that captures the essence of the two key algorithms, so they can be conveyed as an enhancement to PoBh, and that so everyone understands the algorithm.

The plan is to enhance PoBH to be a hybrid: PoBH/POL.  This will also help reward our loyal investors, those who help tithe the children, with the propensity for more rewards - and also, to help us make mobile mining on mobile phones a reality for the poor unbanked in the world.

My plan is to add the algorithm to testnet only, and to start testing this in a couple days in testnet.

Please if you have any concerns or questions lets discuss them so we can make this the best enhancement possible, and also regain our network back at the same time.

If we can test this over the next 30 days in testnet, we could potentially go live end of March with a mandatory.

Note, I do want 50 or so of us to start getting ready for testnet again, but a mandatory upgrade will be required for testnet so please ready machine but do not bother syncing.

PS Ill add Pool Effects to the wiki.

[Lichtsucher]

Wow, I think this is amazing... Does this mean its OK for me to have a daily release now for all linux users?  (Just kidding)...
So youve created a PPA for BiblePay??
This is awesome!
So, how much work do you have to go through when I push a release, or is it all automated?

Hi

Yes, I have created a PPA on my own account, but it is also possible to create a Team-PPA, so that not only one could handle it.

I created a proposal that explains a little bit more: http://forum.biblepay.org/index.php?topic=88.0
But I need your help in sending the Biblepay Counts to the pool to start the real proposal there

About the deployment: It require around 30-60 Minutes to setup, then only 1 or 2 minutes per release, it's really easy.
It is not automated yet, but we might change that later on, if all works well. But for an automated release, it would be better to use tags in git or something like that, so that the system could identify releases better

I wrote howto on creating a Team-PPA and setting up the process as part of the deb-builder (README): https://github.com/Lichtsucher/biblepay-deb-builder
It is written for developers, so I didn't explain how to checkout a git repo