Topic: BiblePay - New Coin Launch - Official Thread - page 132. (Read 119850 times)

Thank you very much. You really save my day

I'm not very handy with Linux compile and qt, mainly on Windows machine.

https://www.youtube.com/watch?v=26lW1eE5Mn0&feature=youtu.be

My Biblepay Rig

I would be a little worried that some users might intentionally send offensive materials in an effort to jeopardize the project's relationship with the charity partner. If the people at compassion.com are okay with filtering the occasional offensive letter on their end it might work, since I doubt it'd be a common occurrence.

Would it be practical to somehow have Sanctuaries involved in checking the letters once masternodes are implemented?

I got the same, but it only took some time. Try to leave it on for some time.

Can anyone confirm whether or not this is the most recent wallet version?

Biblepay Core version 1.0.1.9 (64-bit)

For some reason after rebooting the wallet it gets stuck on the synchronization at 0 hours behind?

So I was just looking over the interfaces at compassion.com (thats the org we started initially partnering with to sponsor orphans.  Each longest waiting child is $40 a month, btw.).  So I reached out to May the director of the region I am in, and she expressed interest in holding meetings with conf calls for IT integration (ideas like an API to sponsor an orphan, a query for the sponsored orphan list, etc). 

This morning, I found an interface where we can electronically write a letter (with pictures) to an orphan that we sponsor, and we can receive a list of incoming letters from the orphans who write to us.  I was thinking we should look into adding this ability to the wallet, so the community can take over this function.  (Since normally, to have a social media presence, we have someone manually manning twitter, facebook, and handling the correspondence between the orphans and the community.  (We would probably need one full time volunteer just to write to our orphans!).

So trying to do this in a more efficient way, if we clone our Send BBP page, and make a write to sponsored orphan page, we could make a multiline textbox with a space for a letter to a child, and let anyone on the blockchain write a letter to one of our current sponsored orphans, and shoot it through the Compassion API.  This may sound funny or rife for abuse, but otoh, its important, because these children are waiting for us and some are depressed, and just waiting for letters.  The interface is already there, and that would take one function off of a full time volunteer.  As far as receiving letters from our orphans back to the community, we could potentially insert those letters back in the chain and allow our community to view them in the wallet.

I think some of the bigger whales are waiting on the sidelines to ensure we do what we say we will do: We will dump the orphan cold wallet, spend 100% on orphans, and provide an orphan database that is auditable on the expense side, then when they feel more comfortable that this is 100% legit I think we will get a lot more attention.  It should become very clear to them within 60 days.

Why is god only valued at 30 satoshi?
I mean I will even have to buy some bags for cheap god
777 satoshi should be target ok , thank you.

If all your qt dependencies are there then look in biblepay/src/qt for the qt binary.

Okay, I managed to build the wallet successfully. But it is not the gui version, or maybe I overlook it? How to build for the qt GUI wallet?

Yes all coins are like this, this is by design with blockchains.  The whole point is your wallet doesn't know its a Orphan until the network rejects it, because someone found a block at the same time.

I get all that, but why is it necessary for the wallet client to tell me about a transaction that isn't actually incoming? Can it not tell that it was an orphan block and there's no incoming reward? Are all crypto wallets like this when solo mining an orphan block?

The volume is quite low on C-Cex. Not much for sale either. 1,4 BTC would clear out sell orders and take price to 325 satoshi.
Good thing that the miners see that the current prices is not worth selling for, it will rise. As it is a bible coin im tempted to say "let there be light"  

Have tried everything and every time it still ends up compiling 1.0.1.7.

Will have to give up for now and will try again in a few days.

Will update if I figure out the problem.

This is perfectly normal and happens in all coins. An orphan is a block that you solved and submitted to the network but someone else also solved a block at almost the same time and also submitted. Due to various reasons including latency the network receives and accepts the other miner's block and rejects yours. The block you solved then becomes an orphan. This is most prevelant when a coin launches and lots of blocks are solved in quick succession at low difficulty, but it can happen at any time.

Before you blame it on the dev, rather do things from your side like increase your internet speed but most of all your latency. Go fixed line or fibre or even better, mine in the cloud where the internet is super fast.

Orphan blocks are something that happen in all blockchains, although you normally wouldn't notice if you're not solo mining. You might even have been mining a fork, so you wouldn't even be mining against the network hashing power of the main blockchain. Take a look at your getmininginfo and make sure your blockchain agrees with http://biblepay.inspect.network/

So the wallet displays an incoming transaction popup for transactions that aren't actually being credited? That's pretty absurd...

Really discouraging to be informed that I've mined a block when that's not actually true. As a user, I don't want to be told about non-existent incoming transactions. Don't tease me, confuse me, and waste my time! Sheesh.

I like this project BiblePay.
Hopefully soon this coin will go up and it will be since the dev is working very hard in the background. Good luck and hopfully soon it will be on bigger exchange

Well, that would be why it's wasn't credited. It's pretty unusual, I don't think I've solo mined any orphan Biblepay blocks. Does getmininginfo show that you're on block 2488 right now?

As far as the address goes, that's normal. A new receiving address is generated whenever you receive a block reward. It all ends up in your wallet.

Why is address BCGn9AzpeM2Q1GccM64a4rJr3jvRhFWdFC showing up? That's not mine...