BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[slovakia]

dear igabyted pool exists only 1 monopol by Rob and is there .ca 25M and coins is over 280M

[m4tsby]

what is the trick again to get the wallet to sync? mine is stuck, I deleted the banlist but it still wont progress.
I think someone once said to delete peers?

[znffal]

what is the trick again to get the wallet to sync? mine is stuck, I deleted the banlist but it still wont progress.
I think someone once said to delete peers?

If I ever have issues I find that reindexing seems to work

[bible_pay]

what is the trick again to get the wallet to sync? mine is stuck, I deleted the banlist but it still wont progress.
I think someone once said to delete peers?

If those two dont work try:
rm chainstate -R
rm blocks -R

Resync

[saintarchimedes]

what is the trick again to get the wallet to sync? mine is stuck, I deleted the banlist but it still wont progress.
I think someone once said to delete peers?

If those two dont work try:
rm chainstate -R
rm blocks -R

Resync

I can't get biblepay to mine on linux... :/

"  GNU nano 2.5.3                                                                  File: biblepay.conf                                                                                                                                           
addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1
genproclimit=2
poolport=80
pool=http://pool.biblepay.org
workerid=testbig
" is in my conf file.


it keeps saying false for pool mining but its already setup in the conf file any ideas?

{
  "blocks": 20934,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 11168.1785701284,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 1421332572198.94,
  "hashps": 12973.67320610347,
  "minerstarttime": "12-13-2017 03:17:55",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 428,
  "poolmining": false
}

[znffal]

what is the trick again to get the wallet to sync? mine is stuck, I deleted the banlist but it still wont progress.
I think someone once said to delete peers?

If those two dont work try:
rm chainstate -R
rm blocks -R

Resync

I can't get biblepay to mine on linux... :/

"  GNU nano 2.5.3                                                                  File: biblepay.conf                                                                                                                                           
addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1
genproclimit=2
poolport=80
pool=http://pool.biblepay.org
workerid=testbig
" is in my conf file.


it keeps saying false for pool mining but its already setup in the conf file any ideas?

{
  "blocks": 20934,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 11168.1785701284,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 1421332572198.94,
  "hashps": 12973.67320610347,
  "minerstarttime": "12-13-2017 03:17:55",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 428,
  "poolmining": false
}

This occasionally happens to me. This almost always fixes it.

First, stop the daemon:

Code:

./biblepay/src/biblepay-cli stop

The reindex for at least 10 min, 20 min seems to be best for me

Code:

./biblepay/src/biblepayd -reindex

Then after that restart

Code:

./biblepay/src/biblepayd -daemon

Let us know how it goes

[bible_pay]

what is the trick again to get the wallet to sync? mine is stuck, I deleted the banlist but it still wont progress.
I think someone once said to delete peers?

If those two dont work try:
rm chainstate -R
rm blocks -R

Resync

I can't get biblepay to mine on linux... :/

"  GNU nano 2.5.3                                                                  File: biblepay.conf                                                                                                                                           
addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1
genproclimit=2
poolport=80
pool=http://pool.biblepay.org
workerid=testbig
" is in my conf file.


it keeps saying false for pool mining but its already setup in the conf file any ideas?

{
  "blocks": 20934,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 11168.1785701284,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 1421332572198.94,
  "hashps": 12973.67320610347,
  "minerstarttime": "12-13-2017 03:17:55",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 428,
  "poolmining": false
}

Hmm, thats kind of interesting.
Are you sure your changes with the pool= are set in the top level biblepay.conf? (Not the \testnet3 directory)?  And you have restarted after applying.

Maybe try an 'wget http://google.com' to ensure port 80 is open? You should be seeing an error in poolinfo1 if you had http connectivity.

If still no luck, set debug=true and debugmaster=true in the conf and restart with an empty debug.log- see if you receive any http errors?

Also of course ensure the testbiggie worker exists in the pool...
Maybe try testbiggie2 by creating a 2nd worker as another option.

[bible_pay]

PRE-ALERT:  Upcoming Mandatory Upgrade in approximately 1000 Blocks.

Please check back for more info.  The rough ETA is sometime Friday the 15th of 2017.

[znffal]

PRE-ALERT:  Upcoming Mandatory Upgrade in approximately 1000 Blocks.

Please check back for more info.  The rough ETA is sometime Friday the 15th of 2017.

Nice, thanks for the heads up.

Is this "f8000"?

[ferohers]

In these days I feel a bit sad that we do not really show people how to mine properly. On windows it seems easy but not everyone is good with their computers.

Anyone out there to record a video? Then we the community people will create subs in different languages.

1) Full HD screen recording.
2) A slow speaker with easy to understand accent.
3) Tells each part of setup patiently. (Getting around the config and pool setup etc)
4)One video is for Windows and the other one is for Linux.

Anyone created a bash script for biblepay installation? This can also help people to setup their servers super fast.

"Bash script to install Biblepay CLI on Linux and start mining in the official pool"
https://gist.github.com/anonymous/d1c1d35e3c8f67f5fb2e204479fa5c6b

Its also at the bottom of the reddit post for Linux Mining:
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

I wrote the Windows and Mining guides months ago and only updated based on comments I got.
This is my first and only time mining, I just got into cryptocurrencies 4 months ago LOL,
I think the guides could definitely be more user friendly and if someone made youtube video tutorials that would be awesome!

Ive been meaning to add all the guides I have to the BiblePay wiki so everyone can edit them: http://wiki.biblepay.org/Main_Page

===

From the top of my head we need guides/videos for:

- How to Mine BiblePay on Windows and Linux, How to use Pool
Windows: https://www.reddit.com/r/BiblePay/comments/6umlqq/how_to_mine_biblepay_on_windows/
Linux: https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/
MacOS: https://www.reddit.com/r/BiblePay/comments/7id9r9/advice_for_bible_pay_wallet_on_mac/

- How to Send and Receive BiblePay coins

- Wallet Security, How to Backup, How to Password Protect
Backup: http://forum.biblepay.org/index.php?topic=27.0

- How to Buy Bitcoin on Exchange, How to Buy BiblePay on Exchange
Coinbase: https://www.youtube.com/watch?v=_NgXWhfVVJU#t=20

- How to Create Sanctuary (Masternode)
http://wiki.biblepay.org/Create_Sanctuary

- How to Submit Budget Proposal
https://www.reddit.com/r/BiblePay/comments/7jbcfj/how_to_submit_budget_proposal/

- How to Write Orphan Letters
https://www.reddit.com/r/BiblePay/comments/7647fc/please_remember_to_write_orphan_letters/

- VIDEO: What is BiblePay? BiblePay Trailer?
Showcase BiblePay, What makes it different than other coins?

===

TODO:
- write missing guides
- add guides to wiki so everyone can edit and improve http://wiki.biblepay.org/Main_Page
- add screenshots to guides?
- make youtube videos of guides

If anyone is interested to jump onto any of this, please do!

Thank you very much!. I will start making a video based on these in Turkish. Bash scripts are super easy for new comers and also for power users who want to setup multiple servers.

[sxafir]

Normal fork is happend?

[zthomasz]

what is the trick again to get the wallet to sync? mine is stuck, I deleted the banlist but it still wont progress.
I think someone once said to delete peers?

If those two dont work try:
rm chainstate -R
rm blocks -R

Resync

I can't get biblepay to mine on linux... :/

"  GNU nano 2.5.3                                                                  File: biblepay.conf                                                                                                                                           
addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1
genproclimit=2
poolport=80
pool=http://pool.biblepay.org
workerid=testbig
" is in my conf file.


it keeps saying false for pool mining but its already setup in the conf file any ideas?

{
  "blocks": 20934,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 11168.1785701284,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 1421332572198.94,
  "hashps": 12973.67320610347,
  "minerstarttime": "12-13-2017 03:17:55",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 428,
  "poolmining": false
}

Hmm, thats kind of interesting.
Are you sure your changes with the pool= are set in the top level biblepay.conf? (Not the \testnet3 directory)?  And you have restarted after applying.

Maybe try an 'wget http://google.com' to ensure port 80 is open? You should be seeing an error in poolinfo1 if you had http connectivity.

If still no luck, set debug=true and debugmaster=true in the conf and restart with an empty debug.log- see if you receive any http errors?

Also of course ensure the testbiggie worker exists in the pool...
Maybe try testbiggie2 by creating a 2nd worker as another option.

With Ubuntu Xenial (16.04) I've found that simply restarting biblepay doesn't cause it to recognize changes made to the biblepay.conf file, you have to reboot the server, then start biblepay again.

[bible_pay]

Normal fork is happend?

My nodes look like they agree: height 20990.

You mean the mandatory?  Yes, its a hard fork upgrade around block 22000, but the block # is not set firm until after c-cex takes us down.

[bible_pay]

PRE-ALERT:  Upcoming Mandatory Upgrade in approximately 1000 Blocks.

Please check back for more info.  The rough ETA is sometime Friday the 15th of 2017.

Nice, thanks for the heads up.

Is this "f8000"?

Yes, f8000 and the Sanctuaries.  The release is a little early so we can offer a one-time fundraiser on c-cex for integration expenses for an expense we voted on for Jan 2018 that should greatly benefit the community and the orphans.  This will allow anyone here to buy some BBP on c-cex at a discount for one day when we come back online (and use it for a Sanctuary if you want).  The timing of this event will most likely be next week mid week (when c-cex comes back online with our new version).  Ill post more info about that sale as we get closer.

Most likely the mandatory upgrade will be set for Friday or Saturday this week, block # to be adjusted once we know c-cex is in maintenance.

Once you upgrade your node, you can start deploying a sanctuary, and we should see each other in the sanctuary list, but sanctuary payments do not actually start until block 23000 - this gives us time to set up the Sanctuaries and ensure we are all synced.  I have the first superblock at block # 30001.

Superblocks will be monthly, to keep our voting requirements down to a minimum.  However while on that subject, it will be extremely important for us to vote for the charity expenses every month and vote for our budget and ensure its going to pass before the monthly block number (Ill post instructions how to know what our monthly superblock block number will be), as otherwise we will miss the payment for all of our orphans for one, or other catastrophic things could happen.  

I thought about the dynamics of the cutover between my manual funding of compassion and our first superblock also.  The way I have it set now it the first superblock should occur around Jan 16th.  So the tithe blocks for compassion still occur even in f8000, up until block 30000.  On block 30001, tithe blocks stop forever and our first voted in budget is paid.  So we can ensure there is no double payment for orphan expenses in block 30001, we can vote on a partial budget and ensure it is emitted, then we will have a clear path for timing for the next charitable superblock (202*30) blocks or 30 days in the future after the first superblock.


EDIT:

Please see the instructions for creating a Sanctuary in Prod:
http://wiki.biblepay.org/Create_Sanctuary

(If anyone finds any errors in the wiki guide please let me know.  Escrow amounts have been updated to 1,550,001 in the guide and the next
mandatory version.)

[saintarchimedes]

alright so I've tried reindexing and created a new worker… also confirmed I was connected using wget however its still not letting me mine for some reason. I also tried restarting biblepay and restarting with the conf edited but no luck. Where is this other directory you speak of? right now I'm in the biblepay folder in usr (src). How do I cd to the dir you are talking about?

what is the trick again to get the wallet to sync? mine is stuck, I deleted the banlist but it still wont progress.
I think someone once said to delete peers?

If those two dont work try:
rm chainstate -R
rm blocks -R

Resync

I can't get biblepay to mine on linux... :/

"  GNU nano 2.5.3                                                                  File: biblepay.conf                                                                                                                                           
addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1
genproclimit=2
poolport=80
pool=http://pool.biblepay.org
workerid=testbig
" is in my conf file.


it keeps saying false for pool mining but its already setup in the conf file any ideas?

{
  "blocks": 20934,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 11168.1785701284,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 1421332572198.94,
  "hashps": 12973.67320610347,
  "minerstarttime": "12-13-2017 03:17:55",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 428,
  "poolmining": false
}

Hmm, thats kind of interesting.
Are you sure your changes with the pool= are set in the top level biblepay.conf? (Not the \testnet3 directory)?  And you have restarted after applying.

Maybe try an 'wget http://google.com' to ensure port 80 is open? You should be seeing an error in poolinfo1 if you had http connectivity.

If still no luck, set debug=true and debugmaster=true in the conf and restart with an empty debug.log- see if you receive any http errors?

Also of course ensure the testbiggie worker exists in the pool...
Maybe try testbiggie2 by creating a 2nd worker as another option.

alright so I've tried reindexing and created a new worker… also confirmed I was connected using wget however its still not letting me mine for some reason. I also tried restarting biblepay and restarting with the conf edited but no luck. Where is this other directory you speak of? right now I'm in the biblepay folder in usr (src). How do I cd to the dir you are talking about?

[bible_pay]

alright so I've tried reindexing and created a new worker… also confirmed I was connected using wget however its still not letting me mine for some reason. I also tried restarting biblepay and restarting with the conf edited but no luck. Where is this other directory you speak of? right now I'm in the biblepay folder in usr (src). How do I cd to the dir you are talking about?

Aha! Thats probably it, its probably the execution user is different than the working dir (maybe).

So heres one way to try:
Go back to linux command prompt.
cd ~/.biblepaycore
nano biblepay.conf

modify this file to have gen=0
debug=true
debugmaster=true

exit nano

rm debug.log


Then start biblepay, and while it is running:

cd ~/.biblepaycore
cat debug.log


Verify the timestamps in the log are current.

Also, verify 'getmininginfo' shows biblepaygenerate=false


If these two things are true, then just edit the biblepay.conf file again with the pool info, and try again.

We need to ensure setting gen=0 says biblepaygenerate=false, then setting gen=1 makes getmininginfo say biblepaygenerate=true, then we know you are affecting the correct config file.


(The testnet config file is at ~/.biblepaycore/testnet3/biblepay.conf to answer your question but you wont need that).

[bible_pay]

See pool | External Links:

15 YR OLD JEWISH BOY NATAN - TESTIMONY OF END OF DAYS

http://pool.biblepay.org/Action.aspx?link=af87b7f

[zthomasz]

PRE-ALERT:  Upcoming Mandatory Upgrade in approximately 1000 Blocks.

Please check back for more info.  The rough ETA is sometime Friday the 15th of 2017.

Nice, thanks for the heads up.

Is this "f8000"?

Yes, f8000 and the Sanctuaries.  The release is a little early so we can offer a one-time fundraiser on c-cex for integration expenses for an expense we voted on for Jan 2018 that should greatly benefit the community and the orphans.  This will allow anyone here to buy some BBP on c-cex at a discount for one day when we come back online (and use it for a Sanctuary if you want).  The timing of this event will most likely be next week mid week (when c-cex comes back online with our new version).  Ill post more info about that sale as we get closer.

Most likely the mandatory upgrade will be set for Friday or Saturday this week, block # to be adjusted once we know c-cex is in maintenance.

Once you upgrade your node, you can start deploying a sanctuary, and we should see each other in the sanctuary list, but sanctuary payments do not actually start until block 23000 - this gives us time to set up the Sanctuaries and ensure we are all synced.  I have the first superblock at block # 30001.

Superblocks will be monthly, to keep our voting requirements down to a minimum.  However while on that subject, it will be extremely important for us to vote for the charity expenses every month and vote for our budget and ensure its going to pass before the monthly block number (Ill post instructions how to know what our monthly superblock block number will be), as otherwise we will miss the payment for all of our orphans for one, or other catastrophic things could happen.  

I thought about the dynamics of the cutover between my manual funding of compassion and our first superblock also.  The way I have it set now it the first superblock should occur around Jan 16th.  So the tithe blocks for compassion still occur even in f8000, up until block 30000.  On block 30001, tithe blocks stop forever and our first voted in budget is paid.  So we can ensure there is no double payment for orphan expenses in block 30001, we can vote on a partial budget and ensure it is emitted, then we will have a clear path for timing for the next charitable superblock (202*30) blocks or 30 days in the future after the first superblock.


EDIT:

Please see the instructions for creating a Sanctuary in Prod:
http://wiki.biblepay.org/Create_Sanctuary

(If anyone finds any errors in the wiki guide please let me know.  Escrow amounts have been updated to 1,550,001 in the guide and the next
mandatory version.)

Rob, will you elaborate a bit on specifics to implement the Mandatory Upgrade ...

1) What is "f8000"?

2) What if anything will miners need to do? Will they need to pgrade the BiblePay mining software on their PC or servers?

3) What will Sanctuary providers need to do?

4) What do you mean by "once you upgrade your node"?

5) How much of a discount will there be to buy BBP on c-cex for the one day when we come back online?

6) What is the difference between a superblock and a regular block?

7) What is a charitable superblock?

Thanks!

[bible_pay]

Yes, f8000 and the Sanctuaries.  The release is a little early so we can offer a one-time fundraiser on c-cex for integration expenses for an expense we voted on for Jan 2018 that should greatly benefit the community and the orphans.  This will allow anyone here to buy some BBP on c-cex at a discount for one day when we come back online (and use it for a Sanctuary if you want).  The timing of this event will most likely be next week mid week (when c-cex comes back online with our new version).  Ill post more info about that sale as we get closer.

Most likely the mandatory upgrade will be set for Friday or Saturday this week, block # to be adjusted once we know c-cex is in maintenance.

Once you upgrade your node, you can start deploying a sanctuary, and we should see each other in the sanctuary list, but sanctuary payments do not actually start until block 23000 - this gives us time to set up the Sanctuaries and ensure we are all synced.  I have the first superblock at block # 30001.

Superblocks will be monthly, to keep our voting requirements down to a minimum.  However while on that subject, it will be extremely important for us to vote for the charity expenses every month and vote for our budget and ensure its going to pass before the monthly block number (Ill post instructions how to know what our monthly superblock block number will be), as otherwise we will miss the payment for all of our orphans for one, or other catastrophic things could happen.  

Rob, will you elaborate a bit on specifics to implement the Mandatory Upgrade ...

1) What is "f8000"?

-> f8000 is the new PoBh algorithm that has a processor mutex instead of node mutex.  This means when it keeps the processor busier, it is not subject to the multiple-biblepay-copies-on-one-node-hps-gain attack.


2) What if anything will miners need to do? Will they need to pgrade the BiblePay mining software on their PC or servers?
-> Since this is a mandatory upgrade, every server, pc, and service provider (IE exchange) will need to upgrade otherwise they will start mining on their own fork. 

3) What will Sanctuary providers need to do?
-> Sanctuaries are not live yet, but they would have needed to upgrade.  This brings up a good point.  Sanctuaries are expected to upgrade even during leisure upgrades, where leisures upgrades are optional for everyone else.

4) What do you mean by "once you upgrade your node"?
-> Once the biblepay software is upgraded, then sanctuary features will be enabled (they are current disabled).  Things like instantsend, coin mixing, and operating a sanctuary will be enabled.

5) How much of a discount will there be to buy BBP on c-cex for the one day when we come back online?
->  Im checking this now, I am actually PMing back and forth regarding this now.

6) What is the difference between a superblock and a regular block?
-> A regular block is one that is mined by a miner and paid partially to the miner and partially to a sanctuary.  However a superblock is only once a month (in our configuration), and contains not only the miners payment, but also a list of voted in expenses.  Whatever was proposed, voted, budgeted, approved, budged-voted in that month up to T-1 of the superblock timestamp is included in the superblock.  The superblock generates the payments to the proposals original payment address.  Btw, the term superblock in general came from the ability to pay thousands of payments in one block, but in our case we only need to pay 100 or less.  One bitcoin block had 32,000 transactions in it, so that is pretty much what we can expect that is possible in a superblock.

7) What is a charitable superblock?
-> A charitable superblock is just something I named since I expect these blocks to primarily contain the compassion.com expense.  And we have a propensity to vote in other charities for payment.  It could potentially have some IT expenses in it, if we have any voted in.

Thanks!

[bible_pay]

I just got a message that the deal fell through [to add us to Two Top 5 exchanges in Jan 2018].  So I am modifying the client to Not mint the 3.5 BTC block.  

(Note, the block was for 3.3 BTC for integration fees + .2 BTC for service fees that is why it was 3.5 btc).

I just wanted to update anyone that was waiting in the wings - not buying BBP to realize that we wont have any special deal to buy at next week, so I didnt want to stop anyone if you were holding off.  Now going forward, everything is voted in by the sanctuaries.