BiblePay - New Coin Launch - Official Thread

[maarekelets]

One thing I've never completely understood is how sanctuaries will be implemented. When they are established, how exactly will selections be made on which nodes become Sanctuaries? Is it a matter of putting in a stake?

Yeah, like Togo shows, when you invest in a sanctuary, its sort of like renting a seat at the stock exchange.  As long as you hold the seat you receive the privilege of voting on governance issues and receiving a monthly reward (approx 10% of the cost of the seat comes back to you in revenue per month, roughly, depending on how many sanctuaries exist).  The escrow amount is still in the air, West is doing some simulations on that.  Its probably between 600,000 and 1 million BBP of escrow.  The escrow provides a useful service - to allow us to offer instantsend - that means coins can be sent from point a to point b instantly. 

Very nice... gotta keep on mining lol. Still working up to 100K, but time will see that happen.

Been reading the github in my (rare) spare time and am starting to get a few for the codebase.

[nananaminer]

@bible_pay Thanks for updating the pool.

There's one issue I'm encountering through multiple versions, where my miners reaches their peak hash rate and crashes close to zero before going back.
This makes the rewards erratic. What do you think the issue is?
I've tried different thread limits and both pools with no luck.

[m4tsby]

When i mined Verium, we had a google spreadsheet for documenting your hash / cpu/ ram / os, etc..
Was helpful to see where you could be with your hardware if a similar rig was outperforming you.
I will try to throw something together.

[nananaminer]

Also this error pops up occasionally and the daemon shuts down during mining.

Code:

*** Error in `./biblepayd': double free or corruption (f
asttop): 0x00007f2e14000b50 ***

 

[bible_pay]

Also this error pops up occasionally and the daemon shuts down during mining.

Code:

*** Error in `./biblepayd': double free or corruption (f
asttop): 0x00007f2e14000b50 ***

Does this only affect one mining thread or does it kill all the threads?  What OS, and biblepay version and bitness is it?

[nananaminer]

Also this error pops up occasionally and the daemon shuts down during mining.

Code:

*** Error in `./biblepayd': double free or corruption (f
asttop): 0x00007f2e14000b50 ***

Does this only affect one mining thread or does it kill all the threads?  What OS, and biblepay version and bitness is it?

It kills all the threads. Linux 14.04, Biblepay version: 1.0.3.9c

[ferohers]

I will invest in this coin each month periodically.I prepared a few feedbacks

Feedback for C-cex

Invested 120 $ and had to pay 128.7$ due to commissions.
More direct dollar sell orders required. Please think about investor who dont want to involve in bitcoin that much.

Maybe more exchange can be added?

Feedback for Dev


1) I liked the old fashion pool web design. However, people of flat design era will find it complicated.

2) Android and IOS wallets would be super!

3) You are doing great. Please remember that we, Christian folk come from very different backgrounds. I was a person who was against Christianity and Christians in some bad ways, and it was a rewarding a prestigious behavior. Now I am a Christian and once seeing Christians mentally challenged - is now a Christian. I also read the Jesus coin thing. It seems an internet troll created it. We should not be condemning people to hell that we are sinners.

[Iuliu]

I want to hear some predictions here. What do you think when this coin will pump up or what can influence to increase the price per BBP?

[PewPewGoesTheDuck]

Just bought up a million coins in anticipation of running a masternode. Still have high hopes for this coin.

[bible_pay]

Also this error pops up occasionally and the daemon shuts down during mining.

Code:

*** Error in `./biblepayd': double free or corruption (f
asttop): 0x00007f2e14000b50 ***

Does this only affect one mining thread or does it kill all the threads?  What OS, and biblepay version and bitness is it?

It kills all the threads. Linux 14.04, Biblepay version: 1.0.3.9c

Thanks, how many threads are you running?  Could you please set "debug=true" in the config, and see if it emits and more lines around the time it dies also?  And finally, I would suspect this started earlier after f7000 was released, do you have a guess as to what version this started dying for you?

Thanks.

PS If anyone is mining on linux and wants to help out could you run valgrind on the process for us?  In the mean time Ill still work on it with Nana.

[616westwarmoth]

I will invest in this coin each month periodically.I prepared a few feedbacks

Feedback for C-cex

Invested 120 $ and had to pay 128.7$ due to commissions.
More direct dollar sell orders required. Please think about investor who dont want to involve in bitcoin that much.

Maybe more exchange can be added?

The way I have see that is cheaper is more complicated by a small degree.  You buy BTC on another exchange (like gdax or coinbase).  Then transfer the BTC to C-Cex, then put your order in as normal (in the BTC-BBP market).

As for as more exchanges, the Dev has said a few times, it's unlikely until after the first of the year.  The rationale is because being on multiple exchanges reduces the volume each exchange handles.  Since right now the daily volume in BTC is pretty low, splitting that low volume over several exchanges would fragment the market.  It could cause a lot of market volatility (which is bad for the coin).  And some exchanges if your average daily volume falls to low, will "delist" you.  When that happens, users have a short period of time to remove their coins from the exchange wallet or they could lose them.  It becomes a very bad thing.

So, while it would be handy if BPP was at "my favorite exchange", it's far better it's doing well at one exchange that poorly at multiple.

[nananaminer]

Also this error pops up occasionally and the daemon shuts down during mining.

Code:

*** Error in `./biblepayd': double free or corruption (f
asttop): 0x00007f2e14000b50 ***

Does this only affect one mining thread or does it kill all the threads?  What OS, and biblepay version and bitness is it?

It kills all the threads. Linux 14.04, Biblepay version: 1.0.3.9c

Thanks, how many threads are you running?  Could you please set "debug=true" in the config, and see if it emits and more lines around the time it dies also?  And finally, I would suspect this started earlier after f7000 was released, do you have a guess as to what version this started dying for you?

Thanks.

PS If anyone is mining on linux and wants to help out could you run valgrind on the process for us?  In the mean time Ill still work on it with Nana.

Currently 32 threads, but I tried different combinations too. Now added debuf to conf, will update you on the error when it pops up again.
Would be 1.0.3.1 I suppose, the dropping off and coming back thing has been happening since I started at around 6800 blocks.

[616westwarmoth]

I want to hear some predictions here. What do you think when this coin will pump up or what can influence to increase the price per BBP?

I hope for great things for this coin but "pump" has a negative connotation (i.e., pump and dump, when only a few make money on the backs of a coin for no other reason than market manipulation).  What can influence price of BBP is several fold, one is a stable wallet and mining.  This isn't criticism, the Dev is very active and responsive.  Once the wallet does what is should and is stable for a month, that will send a sign.  The second is how Sanctuaries unfold.  A repeat of the block 7000 uncertainty will hurt the coin, but hopefully it'll have enough testing on Testnet to predict issues and head them off before the Mainnet goes live.  But in the next month or so, I'd expect a lot more certainty about Sanctuaries to come together and a successful launch in December (which is the last major tweak to the code base) would, in my mind, mean an increase in price stability (and likely an increase in price).

[m4tsby]

Agree with 616 - also thanks to 616, inblue, and togo.. all 3 guys have put in concerted effort to help, build, and test. Lets keep focus that its not the return on the coin that matters so much but the number of orphans we are helping! 

[calxibe]

Agree with 616 - also thanks to 616, inblue, and togo.. all 3 guys have put in concerted effort to help, build, and test. Lets keep focus that its not the return on the coin that matters so much but the number of orphans we are helping!  

You are absolutely right!

But with higher value on the coin there will be more people involved (that also have the right intensions regarding orphans), this will also make it easier to help more orphans.

Because like in all other cases, there is limited how much good (and how much you can help) without money involved.

[nananaminer]

Also this error pops up occasionally and the daemon shuts down during mining.

Code:

*** Error in `./biblepayd': double free or corruption (f
asttop): 0x00007f2e14000b50 ***

Does this only affect one mining thread or does it kill all the threads?  What OS, and biblepay version and bitness is it?

It kills all the threads. Linux 14.04, Biblepay version: 1.0.3.9c

Thanks, how many threads are you running?  Could you please set "debug=true" in the config, and see if it emits and more lines around the time it dies also?  And finally, I would suspect this started earlier after f7000 was released, do you have a guess as to what version this started dying for you?

Thanks.

PS If anyone is mining on linux and wants to help out could you run valgrind on the process for us?  In the mean time Ill still work on it with Nana.

The miner died again, This is the line emitted when it died with debug=true, nothing extra from the previous error.

Code:

*** Error in `./biblepayd': double free or corruption (fasttop): 0x00007fde0c000f60 ***

[1oojke]

First I want to compliment the dev and other contributors for this great and original coin. I will try to help where I can.

For start, I have written an instruction for how to use Biblepay GUI on Linux (it was not obvious for me in the beginning - i thought there was no GUI on Linux). Its in the Reddit comment on original Linux instructions, hope it will help other Linux Biblers:

https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/dncms4r/

[bible_pay]

The miner died again, This is the line emitted when it died with debug=true, nothing extra from the previous error.

Code:

*** Error in `./biblepayd': double free or corruption (fasttop): 0x00007fde0c000f60 ***

Thanks, I have an idea of one thing we can try.




So, blockchain news is almost ready to test in testnet, but its being held up by one issue with the QT HTML TextEdit feature:  we had to add a lot of code into biblepay-qt to support HTML images and ULs.  Ill have to release the QT5.0 Rich Text Edit manual to allow people to see the HTML markup supported - quite a wide array of markup is supported for the creation of a blockchain news article. 

It will take some getting used to but will be relatively easy to create an article after you create one.  It would be nice to add rewards for articles in the future but for now we will most likely have it include your BBP receiving address so you can receive donations when people like the article.  Upvoting/downvoting and a list of articles will eventually come also, but for the first phase we will just have : Create an article, Preview an article, Publish the article into the chain, See an RPC list of articles in the chain, and View an article based on a TXID.  (What is missing is a GUI list of the articles, the upvote/downvote, and some type of reward mechanism).

[seeksilence]

The coin looks interesting. I have some question for the pool mining.
I have higher hashes per second but lower hashes per second2 and lower shares comparing to some other miners. Also Sometime the shares dropped. Could someone explain how it works? Thanks.

[oliwer21]

The coin looks interesting. I have some question for the pool mining.
I have higher hashes per second but lower hashes per second2 and lower shares comparing to some other miners. Also Sometime the shares dropped. Could someone explain how it works? Thanks.

it's very "unknown", dev also don't know why hps2 is diffrent on almost same rigs.
So factors are: cpu, number of cores/threads, OS, LUCK
In short: go intel with 4 cores(stock) on linux and then you will get more coins than ryzen 1700X on win10

Edit. For last 3 days we have round 100 block's per day solved, so it's big drop;(