Author

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

full member
Activity: 574
Merit: 104
Does the '10% orphans' in your title mean that 10% of the supply has been pre-mined or something like that?
No not pre-mined.
It means that every month (at least) 10% of our coins emitted that month are set aside for charity.
Often it ends up being more than 10%.


Thinking about it. Maybe the '10% orphans' in the title could be more clear. And the 'Sanctuaries' part is probably a bit overkill (outsiders only know the term 'Masternodes'). Looking at it from the outside again, they wouldn't know that 'POHB' stands for either. Those two terms would be something they would learn about when they start finding out who we are, but it's probably not something that would attract first-time visitors. What IS interesting though, is that we are participating in R@H.

First half is crypto-related, second half is about the good we do.

So maybe a better title would be something like this:

Quote
BiblePay | Masternodes | CPU only | Curing diseases | 10% goes to charity

Or:

Quote
BiblePay | Masternodes | ASIC and GPU resistant | Curing diseases | 10% goes to charity
full member
Activity: 364
Merit: 102
Does the '10% orphans' in your title mean that 10% of the supply has been pre-mined or something like that?
No not pre-mined.
It means that every month (at least) 10% of our coins emitted that month are set aside for charity.
Often it ends up being more than 10%.


full member
Activity: 420
Merit: 102
Does the '10% orphans' in your title mean that 10% of the supply has been pre-mined or something like that?
full member
Activity: 1260
Merit: 115
For my Sanctuary, I added this cron job to stop and reindex every 3 hours

Code:
crontab -e
0 */3 * * * /home/biblepay/src/biblepay-cli stop; /home/biblepay/src/biblepayd -reindex > /dev/null 2>&1

And I enabled shrinkdebuglog in the config:

Code:
cd ~/.biblepaycore && vi biblepay.conf
shrinkdebuglog=1

Not sure if reindexing every few hours is the best strategy, but I think it will work, is it bad to be reindexing all the time?,
I also feel kind of bad limiting the log file, because now any bugs in the log may get erased,
curious what you guys think and what strategys you guys have to make sure your sanctuary is always running

Sounds like overkill for something that happens once every few months.

Its not that reindexing is bad for the disk, its something that you frankly should never need to do, unless you were forked after a mandatory.

In my case I have a reboot.sh file that reboots all my sancs and an upgrade.sh (that does the git pull origin master && make).  I just run the script once every few months
 if more than 10% of my sancs die.  In general I only lose one node every 30 days or so, so that has worked for me and in my case I dont see a need to change it.  I dont even restart the single nodes, they keep running without a monitor script.  Im using the $5 vultr ubuntu 64 bit.

Maybe you are reacting to the high logging issue once per month and treating it as a regular occurrence.  On those days, I kill my debug.log while the node is hot and it keeps running without writing to the debug.log.

EDIT:  BTW, I run the script from my first sanc, and it SSH's the commands to the other nodes (I dont log in to my other sancs at all for upgrades or for reboots).

Woah your setup is awesome! That is really cool!

I am such a newbie in comparison,
I am manually connecting to each sanctuary with putty, with username/password,
and I type or copy paste commands

I was unlucky 1-2 days ago, my sanctuaries went EXPIRED,
the daemons were running, but they were all stuck at the same block,
and the latest block was further ahead,
Sounded like others experienced it too, not sure what happened.

But yeah typically some of my sanctuaries have issues every now and then.

I like your SSH scripting, I am going to try and use that now!
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
I saw two of these vehicles on the highway in central Texas yesterday:

https://www.activistpost.com/2016/06/u-n-vehicles-mysterious-troop-movement-spotted-in-va-nc-w-va-ohio.html

They were very mysterious looking, these vehicles were brand new - painted with a flat beige - possibly a base for camo.

The first thing I thought of when I saw them was Ken Peters (I saw the great tribulation) - what he said back in 1985 about these - except he described them as blue.

The only difference between the UN vehicles and the ones I saw were the lights were not blue & red (they were white), and they seemed to have a place for MPs with machine guns to stand on each quadrant.

I saw one per tractor trailer, there could have been more, but I had to get off the exit (but I did go out of my way to zoom up and around one and get a good look at it).

What do I think these are?  I have no clue - something used to round up citizens?  (Fema camp roundups, martial law etc ?)

But seeing these new leads me to believe these will be used just as Ken Peters said - so please... become more zealous for Jesus.

BTW here is the old link for Ken Peters:
http://pool.biblepay.org/Action.aspx?link=996d0be

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
For my Sanctuary, I added this cron job to stop and reindex every 3 hours

Code:
crontab -e
0 */3 * * * /home/biblepay/src/biblepay-cli stop; /home/biblepay/src/biblepayd -reindex > /dev/null 2>&1

I was using the && symbol, but sometimes biblepay had already crashed and the stop command would fail, so I started using the ; symbol:

Code:
A; B    # Run A and then B, regardless of success of A
A && B  # Run B if and only if A succeeded
A || B  # Run B if and only if A failed
A &     # Run A in background.

And I enabled shrinkdebuglog in the config:

Code:
cd ~/.biblepaycore && vi biblepay.conf
shrinkdebuglog=1

Not sure if reindexing every few hours is the best strategy, but I think it will work, is it bad to be reindexing all the time?,
I also feel kind of bad limiting the log file, because now any bugs in the log may get erased,
curious what you guys think and what strategys you guys have to make sure your sanctuary is always running

Sounds like overkill for something that happens once every few months.

Its not that reindexing is bad for the disk, its something that you frankly should never need to do, unless you were forked after a mandatory.

In my case I have a reboot.sh file that reboots all my sancs and an upgrade.sh (that does the git pull origin master && make).  I just run the script once every few months
 if more than 10% of my sancs die.  In general I only lose one node every 30 days or so, so that has worked for me and in my case I dont see a need to change it.  I dont even restart the single nodes, they keep running without a monitor script.  Im using the $5 vultr ubuntu 64 bit.

Maybe you are reacting to the high logging issue once per month and treating it as a regular occurrence.  On those days, I kill my debug.log while the node is hot and it keeps running without writing to the debug.log.

EDIT:  BTW, I run the script from my first sanc, and it SSH's the commands to the other nodes (I dont log in to my other sancs at all for upgrades or for reboots).


full member
Activity: 1260
Merit: 115
For my Sanctuary, I added this cron job to stop and reindex every 3 hours

Code:
crontab -e
0 */3 * * * /home/biblepay/src/biblepay-cli stop; /home/biblepay/src/biblepayd -reindex > /dev/null 2>&1

I was using the && symbol, but sometimes biblepay had already crashed and the stop command would fail, so I started using the ; symbol:

Code:
A; B    # Run A and then B, regardless of success of A
A && B  # Run B if and only if A succeeded
A || B  # Run B if and only if A failed
A &     # Run A in background.

And I enabled shrinkdebuglog in the config:

Code:
cd ~/.biblepaycore && vi biblepay.conf
shrinkdebuglog=1

Not sure if reindexing every few hours is the best strategy, but I think it will work, is it bad to be reindexing all the time?,
I also feel kind of bad limiting the log file, because now any bugs in the log may get erased,
curious what you guys think and what strategys you guys have to make sure your sanctuary is always running
jr. member
Activity: 235
Merit: 3
I'm sure the C-CEX wallet issue will get resolved, but I took advantage of the open window to pull my BBP before any "weirdness" with a potential on-exchange fork. I'm looking forward to trying Crypto-Bridge out with those reserved funds!
full member
Activity: 574
Merit: 104
I have a question about C-CEX: they didn't update their wallet (because of their vacation-schedule). But what happens when you try to deposit BBP after block 57700? Will the C-CEX wallet be on a fork from that block on?

I did skype him the details (although they are unconfirmed), but usually what happens is he will at least put us in maintenance before that block.

However since we gave the appropriate notice they might upgrade us while on vacation.

If the wallet is not upgraded after 57,700 please post emergency message here and I will bombard messages to put us in maintenance (as at that point, ccex would be on a fork).

Note that any user can also help by going into the trollbox and asking us to be put in maintenance.

EDIT:  Looks like they are on 1124.  You can see the version on the top right but need to remove the 0's from the number.

EDIT2:  I'll start telling him now its an emergency to take us down...



Thx! Yes, I noticed that they were still on 1124. That's why I was wondering what would happen if they didn't upgrade before block 57700.

I hope that they react fast enough to your messages. Or else we'll have to raid the trollbox I suppose.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
I have a question about C-CEX: they didn't update their wallet (because of their vacation-schedule). But what happens when you try to deposit BBP after block 57700? Will the C-CEX wallet be on a fork from that block on?

I did skype him the details (although they are unconfirmed), but usually what happens is he will at least put us in maintenance before that block.

However since we gave the appropriate notice they might upgrade us while on vacation.

If the wallet is not upgraded after 57,700 please post emergency message here and I will bombard messages to put us in maintenance (as at that point, ccex would be on a fork).

Note that any user can also help by going into the trollbox and asking us to be put in maintenance.

EDIT:  Looks like they are on 1124.  You can see the version on the top right but need to remove the 0's from the number.

EDIT2:  I successfully entered a ticket...

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
** CCEX VACATION UPDATE **



Withdraws are open temporarily!

full member
Activity: 574
Merit: 104
I have a question about C-CEX: they didn't update their wallet (because of their vacation-schedule). But what happens when you try to deposit BBP after block 57700? Will the C-CEX wallet be on a fork from that block on?
member
Activity: 489
Merit: 12
I'm trying to write an orphan letter at pool.biblepay.org. After clicking on "Save" a window pops up with "Record Not Updated: Sorry, you are not authorized to edit this message." Am I missing something?

Could you try logging out and in again?

That worked, thanks Jaap!
full member
Activity: 574
Merit: 104
I'm trying to write an orphan letter at pool.biblepay.org. After clicking on "Save" a window pops up with "Record Not Updated: Sorry, you are not authorized to edit this message." Am I missing something?

Could you try logging out and in again?
member
Activity: 489
Merit: 12
I'm trying to write an orphan letter at pool.biblepay.org. After clicking on "Save" a window pops up with "Record Not Updated: Sorry, you are not authorized to edit this message." Am I missing something?
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
How long will the previous BiblePay Official thread be available?

It's a great resource, would be nice to have ongoing access to it.

I don't think it will be deleted for at least 5 years, but its up to the policies of btctalk.  We will try to leave it here forever.
full member
Activity: 574
Merit: 104
Hello,

the outcome of exec getboicinfo is below.

"Command": "podcupdate",
  "PODCUpdate": "Processed (33) over 1 CPID(s) successfully."

"Command": "stakebalance",
  "StakeBalance": 45263

I solve Rosseta task since the beginning. It has stopped to count my WCG task that I solve.

All my computers are visible and all are connected to internet.

My username is pagalo, same as here

Everything was running fine since Friday

I have updated to 1.1.3.8c my main wallet and 1.1.3.8? all other wallets.

All other wallets that are pooling are copied from my main wallet and don't do podcupdate.


Thanks


Kostas


Yes it does.

I updated to latest 1.1.3.8...

Hello,

In pool.biblepay.org I have the error CPID_HAS_NO_MAGNITUDE since Friday.

I also didn't receive anything from PODC. Last payment was on Friday also.

I have upgraded to 1.1.3.8 and after that I have these errors.


What can I do?


 "Command": "getboincinfo",
  "CPID": "fa5062d1c29baf2e298b674f40ee59b7",
  "Address": "BJZ4XQ8XghfBmHedGfSz16TfdjVsSiK3u6",
  "CPIDS": "fa5062d1c29baf2e298b674f40ee59b7;",
  "CPID-Age (hours)": 425311,
  "NextSuperblockHeight": 57195,
  "NextSuperblockBudget": 1127025,
  "fa5062d1c29baf2e298b674f40ee59b7_ADDRESS": "BJZ4XQ8XghfBmHedGfSz16TfdjVsSiK3u6",
  "fa5062d1c29baf2e298b674f40ee59b7_RAC": 37023.88,
  "fa5062d1c29baf2e298b674f40ee59b7_TEAM": 15044,
  "fa5062d1c29baf2e298b674f40ee59b7_WCGRAC": 0,
  "fa5062d1c29baf2e298b674f40ee59b7_TaskWeight": 100,
  "fa5062d1c29baf2e298b674f40ee59b7_UTXOWeight": 411,
  "Total_RAC": 37023.88,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 19369,
  "Total Budget (One Day)": 1127025,
  "Total Budget (One Week)": 6762150,
  "Superblock Count (One Week)": 7,
  "Superblock Hit Count (One Week)": 7,
  "Superblock List": "56990,56785,56580,56375,56170,55965,55760",
  "Last Superblock Height": 56990,
  "Last Superblock Budget": 1127025,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 2.864325695230068




Try typing the following command

Code:
exec podcupdate true


Has your wallet been sending PoDC update transactions?

I think we need more information to be able to help you. What happened when you used the 'exec podcupdate true' command?

Also, you can find a mining troubleshoot guide in our FAQ:
https://www.biblepay.org/faq/

I'll post it here for you:

Quote
First, please check if your question is answered on this page: https://www.biblepay-central.org/en/documentations/mining-how-to/faq/. If not, then:

(i) Collect data so that we can do a proper troubleshoot:

What does the output of the following commands give you?
exec getboincinfo
exec stakebalance
exec podcupdate true
Have you been solved Rosetta/WCG tasks in the last 24 hours?
Are you on team BiblePay on Rosetta/WCG?
Are your computers on Rosetta/WCG hidden?
What is your name in the pool list?
Is your controller wallet connected to the internet 24/7?
What wallet version are you running?

(ii) Post the answers to above question on our bitcointalk thread alongside with a general explanation of the troubles you are having. The community will try to help you as best as it can.



Are you absolutely sure that the other wallets don't do PoDC-updates? Because I'm looking at the 'PoDC updates' list:
https://www.biblepay-central.org/en/podc/user/1987721/

And it seems that you have updates with a very low UTXO-weight (for instance, the update on block 57154).
It's been happening on-and-off since block 56445. So that would be around the time you updated your wallets.
full member
Activity: 462
Merit: 103
If anyone has any feedback on this FAQ, please let me know Smiley

I know that with time there will be more than 7 questions, but still, I feel like the category tabs are unnecessary, their only purpose seems to be to hide other questions. It was not easy for me to spot the tabs - at first glance I thought there was only one question, and if I weren't looking for the new question about sanctuary states, I wouldn't even see the tabs. I know the tabs looks fancy, but I think it's better for readability to have all questions visible outright, but still nested in those categories of course, just one below the other. At least until there are like 50+ questions or 10+ questions per category. You can always choose to have this current functionality in the future, just comment it out to save it.

By the way, I really liked how you spontaneously added a real frequently asked question to the website. Smiley

Thanks for the feedback! I've adjusted the page to be more intuïtive Smiley
https://www.biblepay.org/faq/

And yes, I'm trying to let the FAQ grow naturally. If anyone has any additions for the FAQ, please mail me at jaap (at) biblepay (dot) org.

You were fast and that is exactly how I imagined it!
newbie
Activity: 52
Merit: 0
Hello,

the outcome of exec getboicinfo is below.

"Command": "podcupdate",
  "PODCUpdate": "Processed (33) over 1 CPID(s) successfully."

"Command": "stakebalance",
  "StakeBalance": 45263

I solve Rosseta task since the beginning. It has stopped to count my WCG task that I solve.

All my computers are visible and all are connected to internet.

My username is pagalo, same as here

Everything was running fine since Friday

I have updated to 1.1.3.8c my main wallet and 1.1.3.8? all other wallets.

All other wallets that are pooling are copied from my main wallet and don't do podcupdate.


Thanks


Kostas


Yes it does.

I updated to latest 1.1.3.8...

Hello,

In pool.biblepay.org I have the error CPID_HAS_NO_MAGNITUDE since Friday.

I also didn't receive anything from PODC. Last payment was on Friday also.

I have upgraded to 1.1.3.8 and after that I have these errors.


What can I do?


 "Command": "getboincinfo",
  "CPID": "fa5062d1c29baf2e298b674f40ee59b7",
  "Address": "BJZ4XQ8XghfBmHedGfSz16TfdjVsSiK3u6",
  "CPIDS": "fa5062d1c29baf2e298b674f40ee59b7;",
  "CPID-Age (hours)": 425311,
  "NextSuperblockHeight": 57195,
  "NextSuperblockBudget": 1127025,
  "fa5062d1c29baf2e298b674f40ee59b7_ADDRESS": "BJZ4XQ8XghfBmHedGfSz16TfdjVsSiK3u6",
  "fa5062d1c29baf2e298b674f40ee59b7_RAC": 37023.88,
  "fa5062d1c29baf2e298b674f40ee59b7_TEAM": 15044,
  "fa5062d1c29baf2e298b674f40ee59b7_WCGRAC": 0,
  "fa5062d1c29baf2e298b674f40ee59b7_TaskWeight": 100,
  "fa5062d1c29baf2e298b674f40ee59b7_UTXOWeight": 411,
  "Total_RAC": 37023.88,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 19369,
  "Total Budget (One Day)": 1127025,
  "Total Budget (One Week)": 6762150,
  "Superblock Count (One Week)": 7,
  "Superblock Hit Count (One Week)": 7,
  "Superblock List": "56990,56785,56580,56375,56170,55965,55760",
  "Last Superblock Height": 56990,
  "Last Superblock Budget": 1127025,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 2.864325695230068




Try typing the following command

Code:
exec podcupdate true


Has your wallet been sending PoDC update transactions?

I think we need more information to be able to help you. What happened when you used the 'exec podcupdate true' command?

Also, you can find a mining troubleshoot guide in our FAQ:
https://www.biblepay.org/faq/

I'll post it here for you:

Quote
First, please check if your question is answered on this page: https://www.biblepay-central.org/en/documentations/mining-how-to/faq/. If not, then:

(i) Collect data so that we can do a proper troubleshoot:

What does the output of the following commands give you?
exec getboincinfo
exec stakebalance
exec podcupdate true
Have you been solved Rosetta/WCG tasks in the last 24 hours?
Are you on team BiblePay on Rosetta/WCG?
Are your computers on Rosetta/WCG hidden?
What is your name in the pool list?
Is your controller wallet connected to the internet 24/7?
What wallet version are you running?

(ii) Post the answers to above question on our bitcointalk thread alongside with a general explanation of the troubles you are having. The community will try to help you as best as it can.


jr. member
Activity: 224
Merit: 2
How long will the previous BiblePay Official thread be available?

It's a great resource, would be nice to have ongoing access to it.
Jump to: