Topic: BiblePay - New Coin Launch - Official Thread - page 46. (Read 119854 times)

More info is needed but I actually think the hps1 is what your miner reports your hashrate as being and hps2 is what the pool calculates your hashrate as being.  In normal pools its not uncommon for the numbers to be different as the pool is calculating it based on how quickly you are submitting shares.  Generally though there shouldn't be such a huge difference in the numbers.  If this pool operates like others then your hashrate is really irrelevent;  When it comes to payouts all that should matter is the number of shares you have submitted.  No clue if this pool operates like others though as it appears to be homemade.

Hps is your comp hash, hps2 is that what you report on pool.
How they are connected? Bible_pay dont want to tell us;)
For me hps means nothing(or it's caluclated wrong) cuz you can have 20k of hps and only 3 k hps2. Or have hps 15k and hps2 over 26k. On same rig.

Any plans on getting listed on more exchanges now?

The pool and the wallet seems to be stable, so now we just need to spread the word about this coin...

What is the difference between hps and hps2 on the pool?

Exactly, but I like 50% even more. Your post reminded me of this post on Dash masternodes. Here's the relevant quote:

++ I like your thinking.
On the POS, I dont think we want to go that route as then it would diminish our PoBh algorithm, but, I think that giving half of the block to the sanctuary is actually another 'form' of POS - as those invested in a sanctuary are similar in form to a POS holder.  Besides with half going to the miner, we can still attract the excitement of mining also.  And make the PoBh better until its stronger.  The masternode could potentially in the future help enforce the POBH possibly by handing out some type of mining voucher to CPUs.

Oh but one more very important thing, while we are finalizing the settings, I think we should update our deflationary setting to give it just a little more impact on the market when sactuaries go live.

Lets change the deflation level to 1.5% deflation compounded monthly, instead of 10% compounded annually as it is now.  That should give the investor a little more incentive to hold dollars in BBP vs native currency, and still show our commitment to be in this for the long term. 

And then we have to make sure after that mandatory, we are committed to service and carving out our niche.  I just thought of a Huge idea today, but it will take a while to create a technical document to share it in order to explain it.

No need to make any changes for such a short time period - we are going live towards the end of year.

What we need is more buyers.

Btw, we do sell the orphan wallet every week now.

Lets focus on the big issues now, ideas that carve out a niche for us. 

Im going to start inviting members into the slack team tonight.   So far, I know we need:

- General Cryptocoin c++ Developers
- Developer that has zeal for finding security bugs in BBP and BTC. 
- Developer that wants to take Dash and BTC recent commits, and merge them into BBP.  This is a highly technical position requiring BTC or crypto experience.
- Web developer to make Biblepay web presence better (The web site, Not the pool, I can handle the pool myself for now)
- PR Manager, launching PR campaigs, faucet, etc
- Twitter, Facebook / Social Media Manager
- Operations & Charity management
- Tech Support (Helps resolve users issues with mining, wallet setup, etc)
- Technical Writer for documents

Would that still be an issue if the coins were sold every week or even every day?

I would think splitting between miners and masternodes would be equitable.  42.5% miner, 42.5% masternode, 10% Charity DAO, 5% IT DAO.  Regardless of what you decide, making the decision this far in advance should be fair to everyone.  It gives miners the chance to realize rewards will be reduced far more than they originally thought, give potential masternoder's time to start preparing for the larger duties and share.

One other thought that I did have regards the Orphan Fund.  With the Orphan Fund being such a big amount of coins sold at once, it creates tremendous waves in the market.  I believe until the Charity DAO is able to fully vote on things, you cap the number of sponsored orphans and then only sell enough to cover their sponsorship and not expand until after the first of the year.

For others, I had an idea about the block history page - would it be possible to display just a small table of blocks where the rows would open a modal window on click (like the others you use on the site) where you can see more details and a full list of miners for that block, like know.

So basically, the small table would only have one row per one block, and it would contain the following columns: height, subsidy, PPH and time. This data is anyway always the same for one block and now it's being repeated a lot in the big table, needlessly. Then when you click on a row of a certain block, you would see the list of miners with all the other data.

This way the page would be much smaller and faster to load, assuming the modal windows are only loaded on request (click on row). Especially because a lot of the times for example I want to take a quick look only at the last mined block details.

https://pasteboard.co/GMW0PJQ.png

from 10k bug.

Few coins doesn`t matter, important is that the pool is working propably.

Yes, Happy labeled it labeled here:

http://biblepay.inspect.network/richlist

#39 on the list.

BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM is the Orphan Foundations wallet?

Regarding Sanctuaries at Christmas:

Ive been thinking of the economics for the sanctuary reward, and Id like to make one final change before Christmas to the parameters so there are no surprises:

Id like to give masternodes 50% of the block reward, 10% to our sactuary DAO budget for charity items, and 5% to our DAO IT budget, leaving 35% for the miner who mined the block.

This decision was based on the spirit that we are not a mining organization we are a DAC - Decentralized Autonomous Charitable Org, seeking a place in the Top 5 on coinmarketcap, once we establish our "VAR" for the blockchain.  Another words, this coin is not promoting a larger mining rat-race, its trying to place the onus on service.  With a lower mining reward and higher sactuary reward, more serious partners will invest in the idea and have a true stake in the outcome of biblepay, and be more committed to running a sanctuary and keeping up with its duties (rather than be in this for profit and to jump ship when the price goes up).

I think that we can then focus on adding more features and services to our masternode codebase, that make a niche for BiblePay.  Something along the lines of a built in bitcoin blockchain (in the masternodes only) that offers a payment gateway, or an exchange gateway for example, or a c# gateway (IE port Stratis into biblepay or biblepay to stratis).  The payment gateway might handle debits/credits for storefronts or credit cards while the instant exchange allows in-wallet bitcoin-biblepay exchanges, or possibly in wallet trading, etc.  We need something that propels biblepay to the top 50 and allows us to rise to the top 5.

Btw all, to see the Mining_Credit click "Reports | Transaction History" and search the page for "BLOCK_10K".

Never mind, got them now. Just a unusual delay...

Anything wrong with the payout from http://pool.biblepay.org/ ?

I did a withdraw 15minutes ago, still haven't arrived at my wallet. This usualy goes asap...

Yes, everything is ok.

Good job Bible_pay

It looks like what happened was at block 10,000, the pool started treating 90% of the shares submitted as stale due to a bug.

The bug has been resolved.

This affected 14 paid blocks.


I credited every pool miner with 20* the estimated shortpay amount.  You can see the credit in the Transaction Log report.