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

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

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.

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

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:


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

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.

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.

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

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

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.

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

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

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

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?


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

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.

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?

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.

Thanks Bible_pay,


1) Thank you for the pamphlet, I will have a loot at it later today.

2) That's very nice! For the balances in BTC, USD, etc. I was thinking that even though everything is spent every month, BBP still need to be sold to BTC and then the BTC has to be sold to USD and then the USD is spent. So it would be nice to be able to reconcile easily all of that if you know what I mean.
Maybe for now just adding a "total" to both the fundraisers page and expenses paid so that it's all added up automatically on these pages. But in the end (and I mean in the future when we grow more), I think the best would be to have an account per currency. Just throwing out ideas.

any idea how long till it stops saying invalid/illegal cpid? its getting podc updates again.


and i do appreciate the help. ty

Your user is BF82a4mCHgYsQVeATQQ2Xq9Mh71SX4CqM2? (found it in another post).

I took the last rejected solution from the log files and validated it again. Here is the result:

{'Command': 'hexblocktocoinbase', 'biblehash': '000003dec5371466195741c313bec6d7c3bf4caa4f22620e4c25935ac0a3c322', 'blockversion': '1.1.2.3', 'txid': '6787e37242ae8bf17d32c6de65a4a825c45cf5679e81141fb3685538062d2d37', 'cpid_legality_narr': 'CPID_HAS_NO_MAGNITUDE', 'subsidy': 512, 'recipient': 'BA3cgTBNea2jrChntZQz4fJbNFzyGtuttx', 'blockmessage': '1.1.2.3f75aecf265ef66a949ddfc750f9e45f1;a4fcf89390f6f275f829cb81d2e417bebdbd37fbb86f950fd5367ce796c042aa;BF82a4mCHgYsQVeATQQ2Xq9Mh71SX4CqM2;H50EBoglQCEmp4JaxHQAg+skgCgugJWDJ65Ssla52asnIY6yKu3bn7T9x8qpvkyc4uflxtunQMb9tWG02PNjSHc=ada16105-5246-41bb-93e6-b1f05c1da42c', 'cpid_legal': False, 'cpid_sig_valid': True}

Important are the parts with "cpid_*":

'cpid_legal': False
'cpid_sig_valid': True
'cpid_legality_narr': 'CPID_HAS_NO_MAGNITUDE'

This is the output of the biblepay client on the pool.

If I use the given CPID, I see the problem:
  "42452 [04-24-2018 04:53:04] (24549 BBP) [TXID=16f0996ea97dc16059d5884e5184cacb7a831ce65fc21d804973df40eb70d125] ": "0.41",
  "41692 [04-20-2018 08:19:23] (23634 BBP) [TXID=1ebdeb465bd61b59f9b70432914b61479c67fdec3e7d145b5ae1141ccc14dc18] ": "3.86",

You had a long time without any podc updates from a biblepay client. For that reason, you have no magnitude.

Important: The same rules the Pool is using are used by all other clients, too. So if you would, for example, solo mine, your found blocks would be rejected by all other biblepay clients for the same reason. It is not a pool rule, it is a network rule

I have a magnitude of .19 for the week, but purepool doesnt show a valid cpid..and no shares found