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

[bible_pay]

every new user/miner add these nodes to config with peerers problem


addnode=node.biblepay.org:40000
addnode=biblepay.inspect.network  
addnode=node.biblepay-explorer.org

Don't recommend this, the second and third node are both dead, and the first node line isn't needed, it's already hard coded in the wallet.

For syncing issues, I would try going to the last pages of http://explorer.biblepay.org:3001/network , finding 1.1.2.1+ IP addresses and then in the console window type:

Code:

addnode "x.x.x.x:x" "onetry"

The problem with the node.biblepay.org being the master,  it is contributing to the sync/crash issues.

Since it was down, many users were unable to use the client.   this is a huge centralization issue

Lesson: if you want to take down bbp only go after 1 node.

We're not centralized; we have an unlimited amount of seed nodes available.  Please don't mislead the public if you have no knowledge of a particular subject.

If you want to run a seed node please send me your node address and Ill add it to the core.

[bible_pay]

I see all of our old addnodes hardcoded in the wallet are dead, so that explains why new users couldnt get on while node.biblepay.org was down yesterday.

So I added these two so far:
WriteKey("addnode","node.biblepay.org");
WriteKey("addnode","node.biblepay-explorer.org");
   

Does anyone else have any that will be up 24-7 on a solid dns external address?

[bible_pay]

So, just so everyone understands that the dev team is on top of this weeks problems, and to provide a less technical explanation of the problem:

1.  PODC was written with a large scale in mind (of 32,767 max researchers), however due to some shortsightedness it was not seen that the governance object had a max limited size that could only hold 370 CPIDs, so that had to be expanded in the middle of our mandatory schedule as a leisure.
2.  After that was released this week, it caused normal clients (IE like exchanges) to have a view of the blockchain that is slightly different than the supermajority (primarily because a block can be marked as "dirty").  The exchange-leisure could recover from this, but requires a -reindex once per day, which is a very big nuisance.
3.  In light of this, we decided to have the exchanges upgrade.

As far as mitigating this problem entirely in the future:

We are implementing these enhancements to the next version:
- Remove Spam in logs
- Recover from Orphaned chain (when a chain is found with more work)
- Reconsidering a bad block
- Avoiding a crash during -reindex
- Adding extra addnode(s) to the core

This version will be out tonight.  Note that this is a leisure, and will not break functionality.

[inblue]

I just tested node.biblepay-explorer and it works:

telnet node.biblepay-explorer.org 40000

UP

You are right. I only tried the main domain which doesn't resolve and I overlooked the fact that a subdomain can be on a different IP address.

That said, I'm wondering if hardcoding node.biblepay-explorer.org is good over the long term, because it is from an abandoned website after all, and I wouldn't trust the owner to keep the node updated at all times. If I understand correctly, nodes on older versions have a higher chance to potentially seed a wrong blockchain to others, right?

Does anyone else have any that will be up 24-7 on a solid dns external address?

1. Can it be a sanctuary at the same time?
2. Does it have to have a domain name?

[inblue]

So, just so everyone understands that the dev team is on top of this weeks problems, and to provide a less technical explanation of the problem:

1.  PODC was written with a large scale in mind (of 32,767 max researchers), however due to some shortsightedness it was not seen that the governance object had a max limited size that could only hold 370 CPIDs, so that had to be expanded in the middle of our mandatory schedule as a leisure.
2.  After that was released this week, it caused normal clients (IE like exchanges) to have a view of the blockchain that is slightly different than the supermajority (primarily because a block can be marked as "dirty").  The exchange-leisure could recover from this, but requires a -reindex once per day, which is a very big nuisance.
3.  In light of this, we decided to have the exchanges upgrade.

As far as mitigating this problem entirely in the future:

We are implementing these enhancements to the next version:
- Remove Spam in logs
- Recover from Orphaned chain (when a chain is found with more work)
- Reconsidering a bad block
- Avoiding a crash during -reindex
- Adding extra addnode(s) to the core

This version will be out tonight.  Note that this is a leisure, and will not break functionality.

Thank you Rob and the dev team for your dedicated work! It's unbelievable how fast you are, those bullet points are not easy, it doesn't have to be tonight already, take your time

[thesnat21]

I see all of our old addnodes hardcoded in the wallet are dead, so that explains why new users couldnt get on while node.biblepay.org was down yesterday.

So I added these two so far:
WriteKey("addnode","node.biblepay.org");
WriteKey("addnode","node.biblepay-explorer.org");
   

Does anyone else have any that will be up 24-7 on a solid dns external address?

does it have to be a sanctuary or just a node that's online?

I appreciate you looking into this, it will definitely help the issues we've been seeing the past few days

[Dimarzio123]

I see that the top three miners have 36% of the magnitude.
Looks like we are in danger of becoming a top 1% coin - (ref top 1% of humanity = 90% of wealth)

This will possibly discourage the small guys and  in the end prevent global acceptance of BBP
Maybe we should limit magnitude of 1% (or less) per account in the name of fairness.
Thoughts?

Regards
PM

[leetlezee]

So, just so everyone understands that the dev team is on top of this weeks problems, and to provide a less technical explanation of the problem:

1.  PODC was written with a large scale in mind (of 32,767 max researchers), however due to some shortsightedness it was not seen that the governance object had a max limited size that could only hold 370 CPIDs, so that had to be expanded in the middle of our mandatory schedule as a leisure.
2.  After that was released this week, it caused normal clients (IE like exchanges) to have a view of the blockchain that is slightly different than the supermajority (primarily because a block can be marked as "dirty").  The exchange-leisure could recover from this, but requires a -reindex once per day, which is a very big nuisance.
3.  In light of this, we decided to have the exchanges upgrade.

As far as mitigating this problem entirely in the future:

We are implementing these enhancements to the next version:
- Remove Spam in logs
- Recover from Orphaned chain (when a chain is found with more work)
- Reconsidering a bad block
- Avoiding a crash during -reindex
- Adding extra addnode(s) to the core

This version will be out tonight.  Note that this is a leisure, and will not break functionality.

Thanks for the explanation! Looking forward to the fix being implemented.

My mining issue was also resolved, I kept the BOINC software running and after a day, my stats were updated and my heat mining started working again.

[Lichtsucher]

I see that the top three miners have 36% of the magnitude.
Looks like we are in danger of becoming a top 1% coin - (ref top 1% of humanity = 90% of wealth)
This will possibly discourage the small guys and  in the end prevent global acceptance of BBP
Maybe we should limit magnitude of 1% (or less) per account in the name of fairness.
Thoughts?

Then they would create 36 small accounts. Don't think we can solve it easily. We need more users with more calculation power.

[Lichtsucher]

I see all of our old addnodes hardcoded in the wallet are dead, so that explains why new users couldnt get on while node.biblepay.org was down yesterday.
So I added these two so far:
WriteKey("addnode","node.biblepay.org");
WriteKey("addnode","node.biblepay-explorer.org");
Does anyone else have any that will be up 24-7 on a solid dns external address?

Rob, how about creating Subdomains on biblepay.org and you set it to ips of stable servers. This way, if a server goes away, you only need to change the dns, but not the client.

Like:
node.biblepay.org
node2.biblepay.org
node3.biblepay.org
node4.biblepay.org
node5.biblepay.org
...

[bible_pay]

I see that the top three miners have 36% of the magnitude.
Looks like we are in danger of becoming a top 1% coin - (ref top 1% of humanity = 90% of wealth)

This will possibly discourage the small guys and  in the end prevent global acceptance of BBP
Maybe we should limit magnitude of 1% (or less) per account in the name of fairness.
Thoughts?

Regards
PM

Imho, this signature wont last forever, as we become more popular, the reward will be arb'ed closer to the electricity cost, and as we approach 10,000 CPIDs, the largest would be a smaller piece of the pie.  But the important thing is that our exchange rate rises and our CPID count rises...  Then it remains fair.

Its something we cant really control, the cat and mouse games are not preventable without infringing on privacy and thats definitely a no-no as that would discourage growth.

[bible_pay]

I see all of our old addnodes hardcoded in the wallet are dead, so that explains why new users couldnt get on while node.biblepay.org was down yesterday.
So I added these two so far:
WriteKey("addnode","node.biblepay.org");
WriteKey("addnode","node.biblepay-explorer.org");
Does anyone else have any that will be up 24-7 on a solid dns external address?

Rob, how about creating Subdomains on biblepay.org and you set it to ips of stable servers. This way, if a server goes away, you only need to change the dns, but not the client.

Like:
node.biblepay.org
node2.biblepay.org
node3.biblepay.org
node4.biblepay.org
node5.biblepay.org
...

Blue, yes it can be a sanc.  

Yes Lich, thats a good idea.

I have a DNS portal for biblepay.org we can control, so yes, lets set up DNS based nodes.  

EDIT: Ok I set up dns1.biblepay.org - dns5.biblepay.org (IE 5 nodes), and added them into the wallet, and its checked in for the next build, and the nodes are up.  One of the nodes is rebooting right now.

[inblue]

Is there a green light to install 1.1.2.4 on Linux? That was super fast.

My sanctuary currently crashes once or twice a day because of these errors:

CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match

CGovernanceTriggerManager::AddNewTrigger -- Error creating superblock: CSuperblock::ParsePaymentSchedule -- Mismatched payments and amounts

So I would like to try if the new version will resolve it.

[bible_pay]

Is there a green light to install 1.1.2.4 on Linux? That was super fast.

My sanctuary currently crashes once or twice a day because of these errors:

CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match

CGovernanceTriggerManager::AddNewTrigger -- Error creating superblock: CSuperblock::ParsePaymentSchedule -- Mismatched payments and amounts

So I would like to try if the new version will resolve it.

Yes, please try it.  Please delete your mnpayments*.* and gov*.* and chainstate and blocks before starting and see if that ParsePayment error dissapears.

[bible_pay]

Im skyping with c-cex right now.

Hes doing us a huge favor and upgrading right now....

Thanks C-CEX!




EDIT:  Tested C-CEX successfully.  All outstanding deposits should be there now.

[bible_pay]

BiblePay - 1.1.2.4
Leisure Upgrade

- Remove spam in logs
- Recover Orphaned chain (when one is found with greater work)
- Reconsider a bad block feature
- Avoiding crash during -reindex
- Adding extra addnodes to the core

[inblue]

Im skyping with c-cex right now.

Hes doing us a huge favor and upgrading right now....

Thanks C-CEX!

It's amazing that you can contact him that way, and I see it's already done - C-CEX wallet is on 1.1.2.4 and up again

[slovakia]

LICHTUCHER chief, can we get more entries in Latest Transactions like 100? its possible? thanks

[bible_pay]

Im skyping with c-cex right now.

Hes doing us a huge favor and upgrading right now....

Thanks C-CEX!

It's amazing that you can contact him that way, and I see it's already done - C-CEX wallet is on 1.1.2.4 and up again

Its a good service Tuesday- SouthXChange is upgrading right now...

[thesnat21]

Rob, how about creating Subdomains on biblepay.org and you set it to ips of stable servers. This way, if a server goes away, you only need to change the dns, but not the client.

Like:
node.biblepay.org
node2.biblepay.org
node3.biblepay.org
node4.biblepay.org
node5.biblepay.org
...

Nice idea, but still points to centralization.   If the biblepay.org domain gets hijacked everyone is stuck.

The probability of that may be low, but better safe than sorry.