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

[slovakia]

by me main wallets is down

[1714508574]

1714508574

[dave_bbp]

Has anyone got the list of 15 or so pool addresses Rob created ? Then can check if it's miners connected to the pool doing the current blocks or not..

You can find the addresses here: https://www.reddit.com/r/BiblePay/comments/7s1tc7/multiple_pool_addresses_for_unique_hashing/

So a quick scan through those addresses, there's blocks being solved that are credited to the pools addresses, even though the pool says 27076 was the last block it mined, it has in fact apparently mined other blocks since then..
I think the pool is actually working, just the front end has hit a road block of some kind..

Thank you very much for your efforts, that is quite comforting. So we don't actually blow that hashpower in the wind after all.

[jaapgvk]

By the way,  a couple of days ago, I started to look into the possibility of using another, existing pool software with biblepay, like NOMP or MPOS.
I'm currently collecting all required information to write a bridge between MPOS and Biblepay, and it will most likely take another 1-2 weeks before a first usable result will be visible, but I'm optimistic that it can be done.

The problem of using an existing pool software is that Biblepay is not using the stratum mining protocol, the standard for most current pools. Plus maybe the custom Proof Of Biblehash, I'm currently looking into the codes to understand if that is something that MPOS needs to learn.

I hope that a second pool (with a different software) will help to solve some of the current problems, but it will take some time.

Great! I hope you can find a way to do this

[slovakia]

i hope too 

[svirusxxx2]

By the way,  a couple of days ago, I started to look into the possibility of using another, existing pool software with biblepay, like NOMP or MPOS.
I'm currently collecting all required information to write a bridge between MPOS and Biblepay, and it will most likely take another 1-2 weeks before a first usable result will be visible, but I'm optimistic that it can be done.

The problem of using an existing pool software is that Biblepay is not using the stratum mining protocol, the standard for most current pools. Plus maybe the custom Proof Of Biblehash, I'm currently looking into the codes to understand if that is something that MPOS needs to learn.

I hope that a second pool (with a different software) will help to solve some of the current problems, but it will take some time.

The biggest problem is it not using standard pice of code from bitcoin-core.
So we can't copy&paste mining code to another library and use it with exisitng minig software.

I develop MPOS few years ago, and there is not problem with stratum protocol, couse stratum is only between miner and pool.
We need to develop standalone miner (without biblepayd) and make library to use it with eg. https://github.com/zone117x/node-open-mining-portal
stratum pool can be connected with MPOS database and send there shares. MPOS is only for calculate shares diff and block payout, and send payout to users.

I have somewhere contact to main developer of https://github.com/zone117x/node-open-mining-portal (yeah I'am on credits ).
I will try ask him how hard is to implement biblepay kjv algorithm, but I think we need make some donation for this.
But still it will be 50% of all we need.

[joelles]

By the way,  a couple of days ago, I started to look into the possibility of using another, existing pool software with biblepay, like NOMP or MPOS.
I'm currently collecting all required information to write a bridge between MPOS and Biblepay, and it will most likely take another 1-2 weeks before a first usable result will be visible, but I'm optimistic that it can be done.

The problem of using an existing pool software is that Biblepay is not using the stratum mining protocol, the standard for most current pools. Plus maybe the custom Proof Of Biblehash, I'm currently looking into the codes to understand if that is something that MPOS needs to learn.

I hope that a second pool (with a different software) will help to solve some of the current problems, but it will take some time.

The biggest problem is it not using standard pice of code from bitcoin-core.
So we can't copy&paste mining code to another library and use it with exisitng minig software.

I develop MPOS few years ago, and there is not problem with stratum protocol, couse stratum is only between miner and pool.
We need to develop standalone miner (without biblepayd) and make library to use it with eg. https://github.com/zone117x/node-open-mining-portal
stratum pool can be connected with MPOS database and send there shares. MPOS is only for calculate shares diff and block payout, and send payout to users.

I have somewhere contact to main developer of https://github.com/zone117x/node-open-mining-portal (yeah I'am on credits ).
I will try ask him how hard is to implement biblepay kjv algorithm, but I think we need make some donation for this.
But still it will be 50% of all we need.

standalone miner is problem with proof of loyalty and botnets i think

[daemonko]

i think pool is stuck somewhere, miners are not updating stats, last block was 40+ blocks ago...

same problem here, no statistics updates, pool seems to be experiencing some issue

[Lichtsucher]

We need to develop standalone miner (without biblepayd) and make library to use it with eg. https://github.com/zone117x/node-open-mining-portal

As I understood the Proof Of Biblehash and the upcoming POL algorithm, a full client as biblepayd is required. The client might be smaller, but will it change a lot?
Plus, with the current rate of changes in the core code, maintaining a second miner seems a lot of hard work.

[Lichtsucher]

@Rob: The biblepay Homepage says there is a Version 1.0.8.6 available, but I can't find it in the git.
Should I build 1.0.8.5b for Ubuntu, or wait until 10.8.6 is in the git repo?

[seasonw]

Yes C-CEX seems to be having a lot of complaints I suggest we work on getting votes else where, C-CEX have even stopped tickets so I'm not quite sure what they are up to but silence is never good and refusing customers to express their issues. I think it's important to work on more exchanges so we are less dependable on just 1. Lets give this a push eveyone:
EXCHANGE VOTING

NEXT.Exchange:
https://nextexchange.featureupvote.com/suggestions/3384/biblepay-bbp

Altcoin.io Exchange:
https://feedback.altcoinexchange.com/suggestions/2114/pls-add-biblepay-bbp

I suggest we pay the 0.1btc for yobit it will do good for the coin price
Then next.exchange if someone can contact them I'm useless for specification technical

Forget about yobit. I know yobit exchange will bring some volumes, but I have heard alot of coin devs sent listing application but yobit just ignored. You should check yobit twitter, they are listed tokens and some bitcoin hardfork coins only since last month. And most importantly, I noticed yobit listed alot of their own bitcoin hardfork tokens to grab money, no idea what is the future of this exchange.

[svirusxxx2]

We need to develop standalone miner (without biblepayd) and make library to use it with eg. https://github.com/zone117x/node-open-mining-portal

As I understood the Proof Of Biblehash and the upcoming POL algorithm, a full client as biblepayd is required. The client might be smaller, but will it change a lot?
Plus, with the current rate of changes in the core code, maintaining a second miner seems a lot of hard work.

I don't know how exactly PoL works, I must see some documentation (any one have some link ? )

I make little mistake...
We can add some code to biblepayd to have stratum support, and standalone miner is not required.
Or we also can write some proxy between biblepay and exisiting protocol, and stratum/longpooling.
But still is some work to do with C++ (where my skills is very weak).

We exactly need three things
1/ write new option to biblepayd for reciving job and sending shares to node-open-mining-portal
2/ add library to this project: https://github.com/zone117x/node-multi-hashing
3/ add support to eg. https://github.com/zone117x/node-open-mining-portal


position 3 I can write, but 1,2 it's too hard for now C++ developer

[ALTJ1990]

Yes C-CEX seems to be having a lot of complaints I suggest we work on getting votes else where, C-CEX have even stopped tickets so I'm not quite sure what they are up to but silence is never good and refusing customers to express their issues. I think it's important to work on more exchanges so we are less dependable on just 1. Lets give this a push eveyone:
EXCHANGE VOTING

NEXT.Exchange:
https://nextexchange.featureupvote.com/suggestions/3384/biblepay-bbp

Altcoin.io Exchange:
https://feedback.altcoinexchange.com/suggestions/2114/pls-add-biblepay-bbp

I suggest we pay the 0.1btc for yobit it will do good for the coin price
Then next.exchange if someone can contact them I'm useless for specification technical

Forget about yobit. I know yobit exchange will bring some volumes, but I have heard alot of coin devs sent listing application but yobit just ignored. You should check yobit twitter, they are listed tokens and some bitcoin hardfork coins only since last month. And most importantly, I noticed yobit listed alot of their own bitcoin hardfork tokens to grab money, no idea what is the future of this exchange.

Okay, thank you for sharing this information, I will make sure I keep focus on the two voting exchanges reminding folk and sharing it to get external votes. We are not that far from reaching a high position with NEXT I'm very excited about this! Can I ask, is it a good idea to limit how many we get added too for long term stability or does that not matter? I could do more ground work and try to find more that have a voting system. The back of my mind says we should wait for these 2, give it a small period and then try being added to 2 more. What do you all think?

[joelles]

Yes C-CEX seems to be having a lot of complaints I suggest we work on getting votes else where, C-CEX have even stopped tickets so I'm not quite sure what they are up to but silence is never good and refusing customers to express their issues. I think it's important to work on more exchanges so we are less dependable on just 1. Lets give this a push eveyone:
EXCHANGE VOTING

NEXT.Exchange:
https://nextexchange.featureupvote.com/suggestions/3384/biblepay-bbp

Altcoin.io Exchange:
https://feedback.altcoinexchange.com/suggestions/2114/pls-add-biblepay-bbp

I suggest we pay the 0.1btc for yobit it will do good for the coin price
Then next.exchange if someone can contact them I'm useless for specification technical

Forget about yobit. I know yobit exchange will bring some volumes, but I have heard alot of coin devs sent listing application but yobit just ignored. You should check yobit twitter, they are listed tokens and some bitcoin hardfork coins only since last month. And most importantly, I noticed yobit listed alot of their own bitcoin hardfork tokens to grab money, no idea what is the future of this exchange.

I think yobit is fine. We should at least send in the app

[bible_pay]

The pool did find 4 or so blocks through the night.

The issue is that bug I was talking about yesterday, where we now have a much larger solution being posted also affected the payment system (thats a service on the pool). 

Im debugging the issue now.

The pool will be fixed within an hour, from the looks of the problem it should be relatively easy to fix.

[zthomasz]

https://biblepay.eu/  - if anyone want to check status of node.

I will add today or tomorrow free notification service.

Excellent! ... when do you expect it to be ready?

[slovakia]

we need node multi hashing....

we can do proposal for it and paid for it €/$

owner of pool looks if he can add to his pools

[ALTJ1990]

I have upgraded my wallet just now to 1.0.8.6, I just want to say I am mining at my usual rate if it helps the guys working hard.

[joelles]

we need node multi hashing....

we can do proposal for it and paid for it €/$

owner of pool looks if he can add to his pools

I will receive answer tonight from the guy

[bible_pay]

The pool did find 4 or so blocks through the night.

The issue is that bug I was talking about yesterday, where we now have a much larger solution being posted also affected the payment system (thats a service on the pool). 

Im debugging the issue now.

The pool will be fixed within an hour, from the looks of the problem it should be relatively easy to fix.

Ok, pool is paying again now and back payments paid.  Sorry for the inconvenience,  the large headers were really an unexpected change that impacted the pool side.


So right now I am looking back at our initiative to find why the pool is finding less and less, the imitative to provide distinct block templates and ensure the pool users are all hashing distinct work.

I have added a feature into 1.0.8.5 that asks the miner to make a .01 cent BBP tx paid to yourself, in an attempt to make a distinct block template per miner.  I will be adding a field to getmininginfo in about 30 minutes to test this out.  I just wanted to make you all aware its there (when you receive a .01 cent tx to yourself when you find a block), it is to try to help us pool mine more efficiently.  

I am also going back to One pool address (BNvQ5Txs1riZvuKA5W7prbtwx7PuSXXBwL) for the time being.  I'm working hard to isolate the blockhash itself, to know for sure that each miner is doing unique work.  Once we know for sure this is happening we can focus on other aspects.

[bible_pay]

The pool did find 4 or so blocks through the night.

The issue is that bug I was talking about yesterday, where we now have a much larger solution being posted also affected the payment system (thats a service on the pool).  

Im debugging the issue now.

The pool will be fixed within an hour, from the looks of the problem it should be relatively easy to fix.

So basically more fraud on pool? Is that intended?

What do you mean by more fraud?

This is an ignoramous comment.