Topic: BiblePay - New Coin Launch - Official Thread - page 115. (Read 119834 times)

Right now, every block mined produces 20,000 BBP, 18,000 BBP or 90% goes to the miner (or pool of miners) and 2000 BBP or 10% goes towards the "Orphan fund" which currently is set to support Compassion.com by sponsoring children there via a monthly sale from the "Orphan fund".  Around the first of the year, the block reward drops to 18,000, which will be split 80% miner/pool (14,400 BBP), 10% "Orphan fund" (1800 BBP) and 10% Santuaries, i.e. Masternodes (1800 BBP).  The Santuaries will then administer the "Orphan fund"

>>Deflationary
>> 10% goes to high efficiency charities


can you explain what this means ?    is it 10 % deducted  yearly from all wallets balances for charity ?

Ahh, didn't realize they were unique, guess I shouldn't get rid of laptop01 and desktop01 for more descriptive names then   Thanks for the education, that should save a lot of grief when I set up another box!

I'll start a CPU database if anyone wants to send me a PM with their stats I'll add them...

https://docs.google.com/spreadsheets/d/19OY0oFdlqrGIxdPIx-qMKnSk-rzGcpAupsxN-is0nlc/edit?usp=sharing

At the beginning i mined several blocks. I had 100,000 coins. I've already sold them at c-cex.com. I was lucky mined solo. What are your experiences with pool.biblepay.org? I have a i7 920 cpu (x5650 I can use) Now it's already hard to get blocks from solo mining and that's why I want to try to use the pool. How much coins do you mine per day and and which CPU you use ?

Maybe safer wasn't the right word. I just mean that if you have dozens of workers, it'd be a pain to go through each one in the event that the pool went down and check them for balances. It's the same in terms of private key safety either way, since the wallet on all your mining rigs would be encrypted (you can mine on a locked wallet just fine, only have to unlock to send).

The pool is a little different from most pools. Worker ids are unique. So, if you created a worker id "worker1", nobody else could have a worker named "worker1", thus just by using that worker name it's possible to link a mining rig to your account.

Ok, but that's not what 616 was talking about at all. I was simply referring to the parts in their quote I bolded here. That simply isn't true and I thought it would be beneficial to clear things up so that people don't get misinformed.

Also, I don't think it's bad to have different wallets on multiple pool mining computers. I actually consider that much safer, because I think a greater chance could be someone stealing your funds from a computer you're not physically supervising all the time (cloud vps, friend's computer etc.), especially if the wallet is not encrypted. But for your scenario, first the small chance to revert to solo mining needs to happen, then probably even a smaller chance to solo find a block nowadays, then to not notice that you're not pool mining anymore (not see that you are not in the leaderboard, not check the mininginfo), and to never check the balance of the wallet.


Workerids are unique, you can't register my registered workerid to your pool account. But you can mine for someone else's worker, which I think may be a huge problem now when the threads are limited, because someone could just kick out of the pool anyone not anonymous by simply mining with a few more threads on their workerid and cause them to go over the limit which will have them revert to solo mining.

This is why I just changed to anonymous and changed my workerids.

Maybe I'm incorrect but unless you make a different user log in and associate it with a different wallet, how would the mining software know that my laptop01 is not your laptop01?

You can have multiple workers under the same user name on the pool if you have the same wallet, but I don't see how else it would be possible as the config file has no reference to your wallet id.

74 Orphans were sponsored! That's amazing!!! 

Log into pool http://pool.biblepay.org and go to link: "Active Sponsored Orphan Report"   

Technically true, but in the off chance that the pool goes down and your miner reverts to solo mining, it'd probably be safer to have them all on the same wallet.

No block as solo miner for few days on a good CPU. Looks like I need to join a pool

It doesn't matter which wallet is on the mining computers if they are pool mining. Identification is only done through the workerid afaik.

Once the bugs are out, I'd suggest the official pool begin charging a fee, like 0.5% to 0.9% then use that to defray the costs of running the pool to improve pool services.  For that matter, I'd be inclined to host a pool if Dev opens that door up and my technical skills are sufficient.

Once the bugs are out, I'd suggest the official pool begin charging a fee, like 0.9% then use that to defray the costs of running the pool to improve pool services.  For that matter, I'd be inclined to host a pool if Dev opens that door up.
You must go to pool.biblepay.org, register a new user account there, add your workerid (not your user id at the pool) specified to workers and then reboot the BiblepayQT.

If you run the QT on another computer, you must export your wallet to that computer so the pool knows who you are, then alter your conf file to a new workerid and add the new workerid on the pool.

tonnes of information and i still can't get a clear set of instructions on how to mine this..

1. I have downloaded the wallet
2. I have modified biblepay.conf as below:

addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1
genproclimit=1
poolport=80
pool=http://pool.biblepay.org
workerid=******

Ok. Please, please, in a step by step fashion, tell me, I beg you:

How Can I Mine This Coin?

Thank you.

If someone had enough hash power that they're consistently getting blocks without joining the pool (say, 10% of the true network hash), there wouldn't really be any advantage for them in joining the pool. In that case they would probably elect to solo mine and not risk the possibility of an issue with the pool interrupting their mining.

There's also probably a lot of miners who are waiting for the pool to officially release since it's in testing, as well as miners who aren't following the project closely and aren't aware of the pool, or aren't aware of the pool or are having trouble setting it up due to language barriers (the majority of network connections were originating in China when I was tracking them).

Pool Testing Thread: https://bitcointalksearch.org/topic/biblepay-testnet-thread-pool-testing-for-proof-of-bible-hash-pool-pobh-2070177

How to Join Pool:

1. Go to pool website ---> http://pool.biblepay.org
  A. Create an account
  B. Create worker ID(s)

2. On windows, navigate to %appdata%\biblepaycore.  On linux, navigate to ~/.biblepaycore.

3. Edit the biblepay.conf file, and make sure to have the following lines in the config (specifically the last 3 dealing with the pool):

addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1
genproclimit=1
poolport=80
pool=http://pool.biblepay.org
workerid=insertWorkerNameHere

4. Restart BiblePay

Note:
- Pool is still in testing ----> https://bitcointalksearch.org/topic/biblepay-testnet-thread-pool-testing-for-proof-of-bible-hash-pool-pobh-2070177

Is the pool having some issues? pool.biblepay.org was timing out for me earlier, and I think the wallet also stopped mining intermittently...

I mean the extra data and a block tank used to carry order data for a company, can be used to carry receipt data, use your data, pretty much anything you want and it could even be stored at Json format to be accessed by another program. I've always been one of those days pushed very heavily for the use of this data and I just find it interesting that it's come down to where it's being used in a religious sect.

I cannot see the advantage at this stage to not join the pool. The only reason I can think of is that there are botnets and the botmaster does not want to point the bots to the pool.