Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 809. (Read 243376 times)

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).

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?

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.)

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.

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.

Normal fork is happend?

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.

Nice, thanks for the heads up.

Is this "f8000"?

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.

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.

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

First, stop the daemon:



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



Then after that restart



Let us know how it goes

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
}

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

Resync

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

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?

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

Its really common for a coin around position 600 on coinmarketcap to have 56% (i find it even pretty good often its 80%) for the top 25.  Keep in mind that most of the time in that top 25 you have the pools and exchange and also dev funds.

Im into UBIQ which is worth 50-70M$ a top 100 coin and top 25 hold 23M on a 38M supply.  And in this case the top wallet is bittrex which holds 13M of that 23M. 

And its even more true for CPU mineable coin.

What about this?

aikida3D sry its private sector.Few machines i have at home
 
616westwarmoth no coins got this style of RICHLISTS : its very bad when first 100 wallets got almost 75% coins .. dont know top 200 coins with this parameters which is mining


all how to setup MN is posted in forum.bible where user KLONDIKE wrote all guideline cos ofc masternode wiki is bad/with bugs

and beware: MN isnt for no IT guy: cos will be problems every day,when will rlse this masternode-life: on DASH got problems every day with masternodes  


and newest INFO:
im added my strong server to pool minersofmen and we hit 3 blocks last 2 hours .... i believe with this pool will be results muc much better

so check it https://minersofmen.com/

I've been looking at video capture cards, now that I have some more time, I hope to grab one and do a few YouTube videos on installing a MN on a Linux VPS.  In short, the guides that are out there will get you from point A to point B with a little trial and error if you have a decent handle on computers.  MN are really not intended for the average user of a coin so I don't see this as a huge problem, but I aim to do my best to get decent video tutorials up before MN go live.

As to how a relatively new coin can be concentrated in a few hands...

For the first several days there was no pool and only a few miners, each grabbing block rewards that were pretty close to 20K every 7 minutes.  Once the pool came on line, difficulty had jumped but if you had a decent i5, i7 or higher end Xeon you could pull 2-3K/day in pool or hit solo blocks every couple days.  Now that same hardware you're going to end up with 200 coins a day in pool.  With a lot of new coins, you don't get many users very quickly, but Biblepay struck a chord with people and the user base ramped up quickly.  So the people that solo'd that first week or two, ended up with a 1M coins without a lot of difficulty.  Since they were ultimately people that had some faith in the coin, I would wager most of them have held onto them as opposed to selling them.  So, nothing nefarious but its the same reason that a large quantity of anything does to the early adopters, they were there first, there was less demand and there were fewer parties to split it between.  While 50% in the top 25 is slightly atypical, it's not out of line and I'd wager is within one standard deviation of average.