 Show Posts
|
|
Pages: [1]
|
On one of my miners wallet not updating, stuck at 0 hours.
Had the same problem for arround 30 min. After that it works. |
|
|
|
Hi all, is there a way to mine Biblepay on a Raspberry Pi 3 please?
Great question. I tried for quite a while to get the source to compile on my Pi 3 before finally giving up. This does not mean that its not possible, just that I got lazy before finding the answer. I believe at least 1-2 person in this thread got it working: https://www.reddit.com/r/BiblePay/comments/7iuyst/raspberry_pi_and_biblepay/Please ping/message them and see if they will write a guide/steps  I got it working.. You have to use Ubuntu mate. Make all the stuff from the Linux guide. Before you start the make process of the wallet, you have to make a big swap partition. Make something like 4GB. The 1 GB of the RAM is not enough for the build process. The process needs arround 3 hours with one thread. The hash rate is arround 110 Hash/s and the amount in the pool something between 0.6 and 1 BBP. Thank you sir! So after you build it on Ubuntu you can just transfer the files on a RPI ? You have to use Ubuntu Mate as OS for the raspi. |
|
|
|
Hi all, is there a way to mine Biblepay on a Raspberry Pi 3 please?
Great question. I tried for quite a while to get the source to compile on my Pi 3 before finally giving up. This does not mean that its not possible, just that I got lazy before finding the answer. I believe at least 1-2 person in this thread got it working: https://www.reddit.com/r/BiblePay/comments/7iuyst/raspberry_pi_and_biblepay/Please ping/message them and see if they will write a guide/steps I got it working.. You have to use Ubuntu mate. Make all the stuff from the Linux guide. Before you start the make process of the wallet, you have to make a big swap partition. Make something like 4GB. The 1 GB of the RAM is not enough for the build process. The process needs arround 3 hours with one thread. The hash rate is arround 110 Hash/s and the amount in the pool something between 0.6 and 1 BBP. |
|
|
|
Changes to the Pool to help investigate the percentage of blocks Solved by the Pool miners:
I've been investigating the distinct solved blocks by the pool over 24 hours and see that the pools percent dropped to 17% from approx. 45% two weeks ago, despite having an increase in hashpower and an increase in distinct miner count.
Looking at the mining template that is given to every miner, I came to the conclusion that one possibility is everyone together is trying to solve the same block (since the pool only has one address, and our distinct transaction count in the block is relatively low). I was thinking maybe everyone is doing the same work without realizing it, and that means as we increase the load on the pool, the problem actually gets worse (as diff increases, more miners do exactly the same work).
So to investigate this I analyzed the top 1000 solutions in the last 15 minutes and sure enough, about 15% of the solutions appear to be exactly the same.
So in light of this I am adding two new features to the pool to attempt to "potentially" measure and or solve this problem:
#1: We now require unique solutions for every miner. So any miner who sends the same solution as another miner, the early bird gets the share, the later solution gets marked as SOLUTION_STALE and then the core asks the pool for a new piece of work. (This will probably cause the big dogs in the pool to lose some shares, relatively speaking compared to small dogs, but we'll see).
#2: Since I want to eliminate the possibility of a duplicated block template across the pool, I have requested the pool to have 7 receiving addresses, starting now. Now, the pool will check its receive address list whenever doing block checking. It will also issue a random receiving address in the block template, thereby creating a more unique template per miner. This is now in prod.
Let us monitor the pool for the next 24 hours and see if we have an uptick in pool based solutions.
That sounds like a very possible cause. Right now I'm seeing quite the effect on the shares: overall I think shares dropped a little bit, but the more significant change is that my small miners (genproclimit=1) have completely disappeared from the list (despite still mining and showing hashps>200 in "getmininginfo"). So it seems that the slow machines currently drop out completely from time to time because they don't hit legit shares fast enough? Let's see how it all works out in a couple of hours or tomorrow.  I am having the same problem Same here... |
|
|
|
still dont want to believe that POOL with 2.3MHs got only Blocks Mined (24 hour period): 51 (25%) = this numbers is last 8 days and diff changed  something is wrong with pool´s setup biblepay: can you to change pool fees from 15% to back 2% its no need to get so much BBP for you Is there maybe another bigger pool? |
|
|
|
It's time to buy AMD stocks |
|
|
|
BiblePay - 1.0.7.5
Leisure Upgrade
- Competetive mining feature:
The idea behind competetive mining, is for those with fast processors who mine so fast that they run out of nonces,
this feature automatically adds a tithe for the orphan foundation for a miniscule amount (IE 1 satoshi or .000001 bbp)
IF you run out of mining nonces, and only increments to 2 satoshi again if you run out. However, when the block changes,
the amount is reset to 0 again. Alex and I have tested this and it appears to give a 5% mining edge. Therefore I wanted
to release this as quickly as possible for general consumption. Since it gives a mining edge, I made the feature ON by default.
To turn it off add the key: competetivemining=false to your biblepay.conf file.
- Pool SSL Support (change pool=http:// to pool=https:// and remove poolport=80 in biblepay.conf file to use SSL).
Is it have a problem?I found some upgraded PC can't running bbp process , but old version still running normal.... I tried to reboot or change dns, and changed back to port80 but it seem not work.. quote: # Error: Error: A fatal internal error occurred, see debug.log for details Error: Failed to connect best block I just got the same error. I am reindexing now... EDIT: Re-indexing seemed to work 1.0.7.5 version seem have problem. It is the second times occurred , I am re-indexing again. I worry it will happen again.... Yes, well let's see how it goes over the next 24 hours. See if anyone else has these issues Same problem here |
|
|
|
|
That is really nice!! (That Biblepay is listed on masternode.online)
|
|
|
|
|
Ich würde hinter IOTA stehen. Allerdings mit der Bedingung, dass das ganze mehr ausgereift ist. Sprich zuverlässige Wallet + Infrastruktur.
Bitcoin ist in meinen Augen zu ineffizient und teuer (Transaktionskosten). Eine Menge andere Coins haben auch keinerlei nutzen und somit in meinen Augen auch keinen berechtigten Wert.
|
|
|
|
|
I would hold the coin. If there was only good news the whole time and it is not a Shitcoin, then the price should rise again.
|
|
|
|
It's illegal here  |
|
|
|
Ich setze das Jahr auf IOTA Potential ist Definitiv da. |
|
|
|
Ich würde nach Thailand gehen. Da ist es wenigsten warm und günstig Sollte es dann mal nicht so gut laufen, dann hat man wenigsten keine hohen Ausgaben vor Ort. |
|
|
|
zer01112 investor358 wrote here 10% mandantory+17%pool fees 27%  he lost our coins then setuped this fees,cos hacker stole all our coins from his pool Hope they will be reduced again soon.... Thank you! |
|
|
|
|
What is the current pool fee in robs pool?
|
|
|
|
|
