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

[Nipar]

@bible_pay
On the installation of NOMP pool you said it is installed as root. So all files and directories under /pool should be owned by root? Mine has half of it in my username instead.

It's all in root now. Still has issues but I will work them out.

[SEO_Account]

Should my sancs be dip3? It says I got paid but I didn't receive anything on cold wallet or sanc wallet..

[sunk818]

Should my sancs be dip3? It says I got paid but I didn't receive anything on cold wallet or sanc wallet..

Should my sancs be dip3? It says I got paid but I didn't receive anything on cold wallet or sanc wallet..

all sancs middle tab is correct, not dip3. it is rotation of 165 or so sancs

[sunk818]

I got my test pool working. I still have more testing to do, but the basic mechanics of submitting shares, getting historical stats, and payout is working.

How do I install NOMP pool for BiblePay?
https://whitewalr.us/2019/install-nomp-pool-biblepay.html

I added troubleshooting notes and my thoughts on setting up the pool.

[bible_pay]

I got my test pool working. I still have more testing to do, but the basic mechanics of submitting shares, getting historical stats, and payout is working.

How do I install NOMP pool for BiblePay?
https://whitewalr.us/2019/install-nomp-pool-biblepay.html

I added troubleshooting notes and my thoughts on setting up the pool.

Did you resolve the nTime issue?  I don't have that issue on nomp.biblepay.org; the submitted time of each miner *is* falling between the acceptable time range window.
Basically your biblepay core server has to have an acceptable nTime in UTC agreeing with the UTC time of the NOMP node.js server (within 60 secs or so) and that time is used to check the share submission time window range (-300 to +7200 etc).

[bible_pay]

@bible_pay
On the installation of NOMP pool you said it is installed as root. So all files and directories under /pool should be owned by root? Mine has half of it in my username instead.

It's all in root now. Still has issues but I will work them out.

I think its basically an issue where we have to re-write the guide from the ground up after installing the Biblepay daemon as a user, and use that same user account to install nomp and any extraneous circumstances encountered as the user need addl rows of docs (Ie missing libs encountered with the user install).

[bible_pay]

Hi,
I changed my Sanctuary station IP, and copy the content of one station to another.

Now I get this after starting Sanctuary:

bbp@stationu1:~/zminer$ ./biblepay-cli masternode status
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "78.47.86.179:40000",
  "status": "Not capable masternode: Masternode collateral is a ProTx and ProTx address does not match local address"
}


How can I fix it ?

By the way, the DIP3 link is not working :
https://wiki.biblepay.org/Evolution_Upgrade

I don't know if you already resolved this; but if you didnt; let me say this: In our .14 branch, we will have an addl command that lets you revive a moved sanc - but its not in our current live branch yet (.13).

The other thing:  DIP3 is partially enabled in Prod - you can have a non deterministic (legacy) sanc *or* a new deterministic sanc.  It will probably be this way for 60 more days, while we find out the status of Apollons integration.

Next, the easiest way to recover from this currently is to just destroy your sanctuary.  If you do this:

- Spend the collateral, back to yourself by unlocking it
- Create a new sanc with a new name

Later after its running again, you can do the 'upgradesanc' command on it to make it deterministic.

Good luck.

[bible_pay]

Hi,
I changed my Sanctuary station IP, and copy the content of one station to another.

Now I get this after starting Sanctuary:

bbp@stationu1:~/zminer$ ./biblepay-cli masternode status
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "78.47.86.179:40000",
  "status": "Not capable masternode: Masternode collateral is a ProTx and ProTx address does not match local address"
}


How can I fix it ?

By the way, the DIP3 link is not working :
https://wiki.biblepay.org/Evolution_Upgrade

When I set up my sanctuary (masternode), I didn't have to do upgradesanc to receive daily payments. I don't think DIP3 is required yet.

Correct - right now you do not have to be deterministic to get rewarded.

If you did upgrade to deterministic, you will still be paid.

We are running in hybrid mode currently.

I will check with Apollon on our integration status and report back within 30 days.  For now, its safe to run either way.

[inblue]

Just wanted to express my gratitude to sunk818 for all the informative blog articles! Awesome community spirit.

And thank you Rob of course for the amazing perseverance and coding talent.

[CjMapope]

Just wanted to express my gratitude to sunk818 for all the informative blog articles! Awesome community spirit.

And Rob of course for such a perseverance.

Ya they really put in alot for Biblepay hey? i agree man
i was gonna say ive noticed that the NOMP pool has aquired like x2 as many miners over the last few days, and they seem to be sticking around too
Good sign of faith in the pool from miners   efficiency seems to be improving more too, my miner is closer to 95% good shares now, which is enough for me!

[bible_pay]

Just wanted to express my gratitude to sunk818 for all the informative blog articles! Awesome community spirit.

And thank you Rob of course for the amazing perseverance and coding talent.

Thanks!

And thanks to everyone that has helped turn this project into something truly special for the benefit of humanity, both in this dimension and in the one coming .

[realdantreccia]

Well, I sure do love this coin. But I think even Jesus would be confused because of the brainy lingo that gets thrown around in this topic. That being said, I am 100% supportive of this project. I have enough BBP, I do miss being able to mine it, but it got a bit too hard on my poor PC haha. Thank you for the hard work!

[bible_pay]

November BiblePay update:

- Today, I had a conf. call with MIP and we were discussing some ideas for 2020.  For example, ideas that utilize the hashing power of POBH 2.0 for a useful activity such as video encoding.
 
- Bhavani has pulled down the latest branch, and is working on the governance expense graph.  She had to visit a sick relative in India, so she had some delays in getting started with the .14 branch.
- PODC 2.0, phase 1 is almost ready for TestNet.  ETA: Within 48 hours.  I believe we will need to test PODC, make a punchlist of enhancements and do an addl round of testing to attempt to shoot for a December release.
- Ive been notifying Cameroon and Kairos about the DSS poll that won, and ramifications on sponsorships.  We still have at least 60 days of credit left with Compassion, so I will reach out to them in 30 days or so and notify them of the wind down.  So, with Cameroon, we have 11 core children that are not in POOM that we have paid until the end of the year.  I mentioned to Todd, we will need to cancel these children as of the end of the year, but alternatively, we will be glad to pick them up in POOM.  If anyone wants to sponsor them please notify Todd that you are taking one of our 11.  If no one does by mid December I will sponsor them in POOM.  Very similar situation with Kairos; I explained the integration reqs to Andy at Kairos, and mentioned we will need to cancel the 21 children, unless - they can convert to POOM by the end of the year.  I mentioned to Andy, we will pick these kids up via POOM one way or another -- if Andy integrates.  Ill keep everyone informed if Kairos decides to implement POOM.
- MIP is working on mobile church tithing.

[sunk818]

Just wanted to express my gratitude to sunk818 for all the informative blog articles! Awesome community spirit.

And thank you Rob of course for the amazing perseverance and coding talent.

Thanks for the compliment inblue. If we can help "orphans", this helps to propel Christian values forward.

James 1:27 English Standard Version (ESV)
27 Religion that is pure and undefiled before God the Father is this: to visit orphans and widows in their affliction, and to keep oneself unstained from the world.

[bible_pay]

** PODC 2.0 is ready for Testing in TestNet **


https://forum.biblepay.org/index.php?topic=465.msg6423#msg6423
https://wiki.biblepay.org/PODC

Note:  The only binaries we have so far are for windows.  However you can self compile one, or wait for MIP to post an update.

[cuarc001]

November BiblePay update:

- Today, I had a conf. call with MIP and we were discussing some ideas for 2020.  For example, ideas that utilize the hashing power of POBH 2.0 for a useful activity such as video encoding.
 

Any possibility of this concept being also tied to PODC 2.0 by utilizing BURP? http://burp.renderfarming.net/

[bible_pay]

We just received 5 letters from Kairos children:

http://pool.biblepay.org/SAN/Mission/Kairos/k1.jpg
http://pool.biblepay.org/SAN/Mission/Kairos/k2.jpg
http://pool.biblepay.org/SAN/Mission/Kairos/k3.jpg
http://pool.biblepay.org/SAN/Mission/Kairos/k4.jpg
http://pool.biblepay.org/SAN/Mission/Kairos/k5.jpg

[realdantreccia]

Can someone help me get my wallet sync? I downloaded the latest version for Windows 64-bit off the website. It's stuck at "connecting to peers and 10 days behind"

Code:

2019-11-04 14:34:04 init message: Loading addresses...
2019-11-04 14:34:04 Loaded 44315 addresses from peers.dat  116ms
2019-11-04 14:34:04 init message: Loading banlist...
2019-11-04 14:34:04 init message: Starting network threads...
2019-11-04 14:34:04 net thread start
2019-11-04 14:34:04 dnsseed thread start
2019-11-04 14:34:04 addcon thread start
2019-11-04 14:34:04 opencon thread start
2019-11-04 14:34:04 msghand thread start
2019-11-04 14:34:04 mncon thread start
2019-11-04 14:34:04 init message: Starting Miner...
2019-11-04 14:34:04 BibleMiner -- started thread 0.000000
2019-11-04 14:34:04  ** Started 1.000000 BibleMiner threads. **

2019-11-04 14:34:04 init message: Done loading
2019-11-04 14:34:04 GUI: Platform customization: "windows"
2019-11-04 14:34:04 GUI: PaymentServer::LoadRootCAs: Loaded  68  root certificates
2019-11-04 14:34:15 Loading addresses from DNS seeds (could take a while)
2019-11-04 14:34:15 1 addresses found from DNS seeds
2019-11-04 14:34:15 dnsseed thread exit
2019-11-04 14:35:00 ERROR: AcceptBlockHeader: block 10d7b6ebc06d41a4c7b1059470af579a4cc24ff7ffefe8e10f135525fae39038 is marked invalid
2019-11-04 14:35:00 ERROR: invalid header received
2019-11-04 14:35:00
ios_base_failure::mesg_fail::ProcessMessages(headers, 161031 bytes) FAILED peer=0
2019-11-04 14:35:00 Misbehaving: 134.209.2.19:40000 peer=0 (0 -> 1)

[bible_pay]

November BiblePay update:

- Today, I had a conf. call with MIP and we were discussing some ideas for 2020.  For example, ideas that utilize the hashing power of POBH 2.0 for a useful activity such as video encoding.
 

Any possibility of this concept being also tied to PODC 2.0 by utilizing BURP? http://burp.renderfarming.net/

(I have participated in BURP a long time ago so I am familiar with what they do), but this idea is more along the lines of making a hash function in dotnetcore (the cross platform dotnet) that splits its time doing some hashing for "Part A" and does something useful in "Part B" - but the parts are tied together.

The Part B, I was thinking would do something to the effect of finding a random Christian youtube video - along with its metadata - and scanning a chunk of it (converting it to mp4).  Then verifying the hash with a sanctuary - if the converted chunk matches.  Another words, this 'useful part' has to be small and quick to verify.  BURP is good for a longer job and better for rendering - but this is more of a conversion from the youtube format to mp4 so the file can be hosted outside of google (so that a backup exists during the tribulation).

Anyway this 'part B' in this case is not really the main driver - part of this effort is to create a new type of hash function that still maintains its integrity for chain rollbacks while doing some type of useful work; and Id like to make it so the 'brain' can be upgraded for Part B - another words its resilient to forks and has some type of abstraction layer above it.

[bible_pay]

Can someone help me get my wallet sync? I downloaded the latest version for Windows 64-bit off the website. It's stuck at "connecting to peers and 10 days behind"

Code:

2019-11-04 14:34:04 init message: Loading addresses...
2019-11-04 14:34:04 Loaded 44315 addresses from peers.dat  116ms
2019-11-04 14:34:04 init message: Loading banlist...
2019-11-04 14:34:04 init message: Starting network threads...
2019-11-04 14:34:04 net thread start
2019-11-04 14:34:04 dnsseed thread start
2019-11-04 14:34:04 addcon thread start
2019-11-04 14:34:04 opencon thread start
2019-11-04 14:34:04 msghand thread start
2019-11-04 14:34:04 mncon thread start
2019-11-04 14:34:04 init message: Starting Miner...
2019-11-04 14:34:04 BibleMiner -- started thread 0.000000
2019-11-04 14:34:04  ** Started 1.000000 BibleMiner threads. **

2019-11-04 14:34:04 init message: Done loading
2019-11-04 14:34:04 GUI: Platform customization: "windows"
2019-11-04 14:34:04 GUI: PaymentServer::LoadRootCAs: Loaded  68  root certificates
2019-11-04 14:34:15 Loading addresses from DNS seeds (could take a while)
2019-11-04 14:34:15 1 addresses found from DNS seeds
2019-11-04 14:34:15 dnsseed thread exit
2019-11-04 14:35:00 ERROR: AcceptBlockHeader: block 10d7b6ebc06d41a4c7b1059470af579a4cc24ff7ffefe8e10f135525fae39038 is marked invalid
2019-11-04 14:35:00 ERROR: invalid header received
2019-11-04 14:35:00
ios_base_failure::mesg_fail::ProcessMessages(headers, 161031 bytes) FAILED peer=0
2019-11-04 14:35:00 Misbehaving: 134.209.2.19:40000 peer=0 (0 -> 1)

Could you first please check your time & timezone, ensure it is correct within a minute or so?  Thats a common problem.

Next you could add a couple peers:

addnode add 216.116.134.119 onetry
addnode add 192.3.249.34 onetry

If that fails, just restart with:
./biblepay-qt -erasechain=1

Could be a bad cache of gobjects, possibly.