BiblePay - New Coin Launch - Official Thread

[civilufo]

Im having trouble with linux as well (Ubuntu 16.04)

==== References:
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt
https://michael.mckinnon.id.au/2016/05/13/building-a-namecoin-server-with-ubuntu-16-04/
https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md

==== Step by Step Commands (not sure if this is all correct, please someone point out any issues)
sudo apt-get install g++
sudo apt install make
sudo apt-get install build-essential
sudo apt-get install autoconf libtool pkg-config
sudo apt-get install libboost-all-dev libssl-dev libevent-dev

sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler

cd /home/yourname
git clone https://github.com/biblepay/biblepay

BP_ROOT=$(pwd)
BDB_PREFIX="${BP_ROOT}/db4"
mkdir -p $BDB_PREFIX

wget 'http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz'
echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef  db-4.8.30.NC.tar.gz' | sha256sum -c

tar -xzvf db-4.8.30.NC.tar.gz
cd db-4.8.30.NC/build_unix
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX
make install

cd $BP_ROOT
./autogen.sh
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/"
sudo make
===================

And then it freezes on last command sudo make, last output: 
  CXX      libbitcoin_server_a-init.o

Ive been waiting 20 minutes,
is it frozen?, did I do something wrong? or do I need to wait longer?
(Its just a one core machine Im testing/building on, I have very little Linux experience and almost no mining experience)

The very first compile takes over an hour on a fast machine as it has to build all the obj files and moc stuff for qt.

Wow, one hour is really lol... i never built a wallet with more than 30 minutes before. But I will try with togoshigekata method in my Ubuntu 16.04 later. Will update my status.

[LilyCakes]

Why did I get a popup notification about an incoming transaction (block reward) but it's not showing up anywhere in my wallet nor in the explorer?? Why was I issued a block reward that disappeared? What is this.

[happy_merchant]

Why did I get a popup notification about an incoming transaction (block reward) but it's not showing up anywhere in my wallet nor in the explorer?? Why was I issued a block reward that disappeared? What is this.

Is it in your immature balance?

[LilyCakes]

Why did I get a popup notification about an incoming transaction (block reward) but it's not showing up anywhere in my wallet nor in the explorer?? Why was I issued a block reward that disappeared? What is this.

Is it in your immature balance?

Nope.

[happy_merchant]

Why did I get a popup notification about an incoming transaction (block reward) but it's not showing up anywhere in my wallet nor in the explorer?? Why was I issued a block reward that disappeared? What is this.

Is it in your immature balance?

Nope.

Open the debug console, type getwalletinfo and post it here. Also type listtransactions and post the transaction.

--edit--
Meant getwalletinfo, not getmininginfo

[LilyCakes]

Why did I get a popup notification about an incoming transaction (block reward) but it's not showing up anywhere in my wallet nor in the explorer?? Why was I issued a block reward that disappeared? What is this.

Is it in your immature balance?

Nope.

Open the debug console, type getwalletinfo and post it here. Also type listtransactions and post the transaction.

--edit--
Meant getwalletinfo, not getmininginfo

{
  "walletversion": 61000,
  "balance": 0.00000000,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 0.00000000,
  "txcount": 1,
  "keypoololdest": 1502323227,
  "keypoolsize": 1015,
  "keys_left": 1025,
  "paytxfee": 0.00000000
}

[
  {
    "account": "",
    "address": "BCGn9AzpeM2Q1GccM64a4rJr3jvRhFWdFC",
    "category": "orphan",
    "amount": 19936.00000000,
    "vout": 0,
    "confirmations": 0,
    "bcconfirmations": 0,
    "generated": true,
    "trusted": false,
    "txid": "ada3fdb5102be983264c63a6b7dad91a1fb7f2903331f8eea45cfc0620d390e3",
    "walletconflicts": [
    ],
    "time": 1502334391,
    "timereceived": 1502334393,
    "bip125-replaceable": "unknown"
  }
]

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

[happy_merchant]

    "category": "orphan",

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.

[Bannedseller]

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

[LilyCakes]

    "category": "orphan",

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.

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.

[happy_merchant]

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.

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/

[jc12345]

    "category": "orphan",

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.

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.

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.

[DirtyMiner]

Every time I recompile from source I end up with version 1.0.7 not the latest, what am I missing/doing wrong?

I simply backed up the wallet, removed all trace of Biblepay and recompiled..

System is Linux Mint.

Finally, great coin, great project i'll be here for the long haul!

I think that is a rare issue, last time that happened to me I did a
git reset --hard HEAD
and then I was able to see the latest commit.  You should see 1.0.1.9 now.

  Still unable to solve this issue, also be aware I am a novice at linux.

Maybe someone else besides the main dev could help me out with this?

Make a new git clone and install correctly. There are tutorial thats works for biblepay too
https://michael.mckinnon.id.au/2016/05/13/building-a-namecoin-server-with-ubuntu-16-04/

Thanks for chipping in.

I have attempted to remove all trace of bible pay (biblepay & .biblepaycore in /home directory)

Then tried both reinstalling from source & from directly downloading the git source, everytime I reinstall it comes back at 1.0.1.7...

Hmm, you could either try deleting a lot of the .cpp files in /src, and doing a git, then comparing the hex hash from the git head at github.com/biblepay/biblepay (its 5fdd), and re-building.  It could be having trouble overwriting your files. Maybe you can chown user -R then redo the git, and recompile.  Anyway you can also try git clone master over again into a whole new directory - and obviously that should give you something to compare to isolate the problem.

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.

[Ginzink]

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"  

[LilyCakes]

    "category": "orphan",

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.

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.

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.

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?

[gigabyted]

    "category": "orphan",

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.

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.

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.

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?

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.

[civilufo]

Im having trouble with linux as well (Ubuntu 16.04)

==== References:
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt
https://michael.mckinnon.id.au/2016/05/13/building-a-namecoin-server-with-ubuntu-16-04/
https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md

==== Step by Step Commands (not sure if this is all correct, please someone point out any issues)
sudo apt-get install g++
sudo apt install make
sudo apt-get install build-essential
sudo apt-get install autoconf libtool pkg-config
sudo apt-get install libboost-all-dev libssl-dev libevent-dev

sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler

cd /home/yourname
git clone https://github.com/biblepay/biblepay

BP_ROOT=$(pwd)
BDB_PREFIX="${BP_ROOT}/db4"
mkdir -p $BDB_PREFIX

wget 'http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz'
echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef  db-4.8.30.NC.tar.gz' | sha256sum -c

tar -xzvf db-4.8.30.NC.tar.gz
cd db-4.8.30.NC/build_unix
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX
make install

cd $BP_ROOT
./autogen.sh
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/"
sudo make
===================

And then it freezes on last command sudo make, last output: 
  CXX      libbitcoin_server_a-init.o

Ive been waiting 20 minutes,
is it frozen?, did I do something wrong? or do I need to wait longer?
(Its just a one core machine Im testing/building on, I have very little Linux experience and almost no mining experience)

The very first compile takes over an hour on a fast machine as it has to build all the obj files and moc stuff for qt.

Wow, one hour is really lol... i never built a wallet with more than 30 minutes before. But I will try with togoshigekata method in my Ubuntu 16.04 later. Will update my status.

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?

[jc12345]

Im having trouble with linux as well (Ubuntu 16.04)

==== References:
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt
https://michael.mckinnon.id.au/2016/05/13/building-a-namecoin-server-with-ubuntu-16-04/
https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md

==== Step by Step Commands (not sure if this is all correct, please someone point out any issues)
sudo apt-get install g++
sudo apt install make
sudo apt-get install build-essential
sudo apt-get install autoconf libtool pkg-config
sudo apt-get install libboost-all-dev libssl-dev libevent-dev

sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler

cd /home/yourname
git clone https://github.com/biblepay/biblepay

BP_ROOT=$(pwd)
BDB_PREFIX="${BP_ROOT}/db4"
mkdir -p $BDB_PREFIX

wget 'http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz'
echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef  db-4.8.30.NC.tar.gz' | sha256sum -c

tar -xzvf db-4.8.30.NC.tar.gz
cd db-4.8.30.NC/build_unix
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX
make install

cd $BP_ROOT
./autogen.sh
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/"
sudo make
===================

And then it freezes on last command sudo make, last output: 
  CXX      libbitcoin_server_a-init.o

Ive been waiting 20 minutes,
is it frozen?, did I do something wrong? or do I need to wait longer?
(Its just a one core machine Im testing/building on, I have very little Linux experience and almost no mining experience)

The very first compile takes over an hour on a fast machine as it has to build all the obj files and moc stuff for qt.

Wow, one hour is really lol... i never built a wallet with more than 30 minutes before. But I will try with togoshigekata method in my Ubuntu 16.04 later. Will update my status.

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?

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

[ACP]

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.

[bible_pay]

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.

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.

[bible_pay]

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.