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

I think this is a very cool chart that shows our legitimacy

You need to associate it with your account in the pool, but you can use a receive-address from one of your current wallets.

(There is a guide on the new website btw )

I have BOINC running on Windows PCs and Linux servers using the same CPID and associated with the same wallet.

If I want my Android device to be Unbanked, I just attach it to a new Rosetta account with a new CPID.

Do I need to associate the new CPID/Android with a new BBP wallet, or can I use the same wallet that I use for my Windows/Linux devices?

Thanks a lot for the debugging guys.

So it looks like it was a race condition based on the logic also (caused by moving those prayers to the background thread).

Ok, Im testing the fix now, Ill have 1.1.2.7 out there before midnight tonight. 

I'll give it a go when i'm home.  But the race condition sounds logical.

When I logged into the wallet and ran "exec podcupdate true" on testnet it gave me an error about missing cpid
this was solved after running exec getboincinfo

Yep, that's exactly it!
What I did:
1. Stop wallet.
2. Change to "gen=0" in config
3. Start wallet, wait shortly.
4. exec getboincinfo was successful
5. exec podcupdate was successful (!)
6. setgenerate true 4
7. getmininginfo showed no errors (!)

Nice troubleshooting.


btw: it's almost midnight, I'm going to bed now.

So the theoretical minimum base case not considering confirmations for an attack is 2 distinct CPIDs with 51% of network hash rate that solve 2 consecutive blocks?  One block is solved to inject the amount to double spend and receive confirmations and the next block to send the transaction to the exchange?  This is theoretically though, because you said to inject a coinbase, the perpetrator would need 100 confirmations, which would take much longer than only 2 blocks thus making a 51% attack very unlikely?  Because the CPID solving consecutive block rules comes into play.  So then an attacker would need 51% of CPIDs.  If I am understanding this correctly, I am impressed, Rob. Brilliant.

I am curious about this.  I am in the beginning stages of trying to compare the way you designed this and trying to compare it to what Stellar does by using trusted nodes.  I know Stellar isn't POW but I am interested in what they do.  So I'm looking for what the minimum threshold for an attack would be, not to expose it but to learn the risk.  Thanks for your patience.

To me, in this case where peoples' savings are on the line, it is a no brainer to favor security over anonymity.  The miners would be tracked but still have a reasonable amount of anonymity.  They just forfeit hiding how much hash power they are contributing to the network.

I wish the industry would start to tilt more towards CPU coins with these ideas: unique IDs which limit solving consecutive blocks and staking to mine.  I think it is much more sustainable for the entire crypto market.  The problem is getting people to pay attention and adopt.

Before you downgrade please try this and tell me if it solves it so we know the problem:

Boot wallet
Wait 5 mins
Type exec getboincinfo
(Verify the CPID is present)
Type exec podcupdate
(Verify you dont see the error that no cpids exist that you saw before)

Then do: (This means you start the miner *after* exec getboincinfo was called)
setgenerate true 5 (or whatever number)

getmininginfo

Tell me if it mines.  I think the problem is that 'exec getboincinfo' has to be run before 'setgenerate true X'.  If that is the case its a race condition that needs a line of code during boot to fix 1.1.2.6.

So your CPID is in the chain and it cant send a podcupdate, interesting. 

Alright please see if downgrading actually solves it; I only have 1.1.1.9, which should be OK for this, here is the link:

https://pool.biblepay.org/downloads/biblepaycore-1.1.1-win64.exe

I'll check further into the problem.

I read it and have read similar ideas in the past, but the problem still appears to be the actual verification process can be hacked in opensource software.

It's an interesting concept though.

The brute force hash attack (with one CPID) will not work.  Because renting 51%*2500 PCs of hashpower will only let them solve 1 block with the single cpid.  To solve blocks N+2 to N+7, they need distinct CPIDs (or there is not a valid solution).  Thats why they would also need those rented machines to have associated distinct CPIDs with magnitude. 

Note that they are not causing the chain to fork.  They are trying to become the dominant miner on the main chain and then fraudulently inject a double spend after solving X consecutive blocks.  The entire attack fails if one of our good cpids solves Any block in between. 

Yes, the unique CPID idea with nicehash is true but this is also a classic tradeoff between anonymity and security.  Most coins do not consider GUIDs or CPIDs because they feel the users are losing anonymity.  We however needed it for cancer mining so we leverage it for security.  And of course our users know they can use nicknames etc in boinc, so they really dont lose anonymity (except for stats tracking which is a benefit).

First please ensure it is part of team Biblepay.

Next, decide if you want it to share your existing CPID (IE if you have other PCs associated with your wallet and want to add the phone on to that existing cpid).  If you do, just ensure the e-mail matches your other machines e-mail, and then all machines + this phone will tally to your controller wallet magnitude.

If you are sure you want to make it an unbanked phone, with its own distinct CPID, then you can log into the pool, and click Account | Associate Unbanked Device.  Once that is done you should show up in the unbanked report after ~ 6 confirms or so.

The pool operator has not asked for any compensation.  35% by my numbers will be still operating as a loss compared to running Sanctuary (after considering the time and expense of running the staking pool versus the ease of running a Sanctuary).

My hope when I approached the operator was he would be willing to do the work to change the GRCPool software to work with BBP and we could then make a proposal to do it internally.  However, he jumped right in and was willing to do the work to a much greater degree.  I had also hoped it would lower the barrier to entry and grow the coin.

Omni Analytics Group
@OmniAnalytics
https://twitter.com/OmniAnalytics/status/1006234347236679680



BiblePay (BBP) is one of the few masternode coins with a Governance system!

Check out OmniAnalytics, they do other interesting analysis on Masternode Coins

I've found a very interesting concept which could be useful in the times during and after The Great Tribulation:

PoHW (Proof of Human Work)

https://bitcointalksearch.org/topic/proof-of-thought-pot-the-holy-grail-has-arrived-only-humans-can-mine-4459113

@Rob, I think you may like this concept. I wonder if something along those lines could be in BiblePay someday.

Thank's for at least considering the issue.

sent you pm's details for prod and test environments.

PROD: one machine is mining again off the new wallet,  the rest are still reporting errors.

I started running BOINC on an Android device a couple of days ago.

It shows up in Your Computers at my boinc.bakerlab.org account, user name zthomasz.

It has crunched some Rosetta tasks (Avg Credit 65, Total Credit 673) but it is not in the Rosetta Unbanked Report at pool.biblepay.org.

Is there anything I need to do to get it listed on at the pool?

I am against premarital fornication.  Rob has said he wants this space to discuss Biblepay AND spirituality.  So unless this has changed, my post is relevant, no matter if it makes you or a girl uncomfortable. 

Like EEEEVVVVVVEERRRRYYYOOOONNNNNEEE in the church engages in premarital sex.  It used to be a thing that celebrities would get promise rings a few years ago, but they couldn't keep them.

More generally, I am very frustrated with spirituality and the state of things.  Nothing is being done right by Christians and Jews.  Christians don't tell the gospel with homage to the woman who poured perfume over Christ.  The aliyah back into Israel should probably not happen until the tribes remanifest.  In God's eyes it looks like the nation of Israel is still a divided nation.  Why is this significant?  Because God promises Israel will never again fall if the tribes come back and the aliyah is done correctly.  So without it being done correctly, I believe there is significant chance that Israel falls again.  That is huge significance, because once Israel is attacked, Evangelical Christians will believe it is the Apocalypse.  But when/if Israel falls and Christ doesn't return, they will have a crisis of faith.  Likely the US and UK are drawn into a war with whomever is attacking Israel (probably Russia and Iran).  If it is a bloody mess, opinion in the US and UK will shift away from supporting Israel. 

There's more.  There are church groups in the US called "Celebrate Recovery".  In Celebrate Recovery they teach you to say the Serenity Prayer:

God, give me grace to accept with serenity
the things that cannot be changed,
Courage to change the things
which should be changed,
and the Wisdom to distinguish
the one from the other.

Living one day at a time,
Enjoying one moment at a time,
Accepting hardship as a pathway to peace,
Taking, as Jesus did,
This sinful world as it is,
Not as I would have it,
Trusting that You will make all things right,
If I surrender to Your will,
So that I may be reasonably happy in this life,
And supremely happy with You forever in the next.

Amen.

Particularly this first stanza is garbage:

God, give me grace to accept with serenity
the things that cannot be changed,
Courage to change the things
which should be changed,
and the Wisdom to distinguish
the one from the other.

Remember:
You can do all things through Christ who strengthens you.
With God, all things are possible.
With the faith of a MUSTARD SEED you can say to this mountain move and it will move.  (It needs to be within the Will of God, though)
So the Serenity Prayer is garbage. 

I have come to distrust Rick Warren and Saddleback church whom started this group.  In summary, a bunch of things are wrong and I am getting tired of spirituality.  Hopefully if I can better control myself, these are the last spiritual things I will post for a long time or perhaps even forever. 

I was under the impression, perhaps incorrectly, that an attacker could have 1 CPID to gain magnitude and use the rest of the machines as heat miners to enforce that attack to solve 1 block at 51% of the network hash rate.  I wondered if solving that 1 block would cause the chain to fork and thus giving the attacker their way against the coin and allowing double spend.  What you are saying is that greater than 3 blocks need to be solved consecutively with over 51% of network hash rate in order to even begin at starting a successful 51% attack?

There is a website that has been published that is listing the cost of attempted 1 hour 51% attacks for various coins:  http://crypto51.app  I haven't tried to calculate the 1 hour cost myself, so I am still a little bit skeptical at some of the assumed costs for some of the coins are so low.  For example, the 1 hour attack cost of Vertcoin is $700.  

What is unique about Biblepay is that Rob has come up with a much better solution to prevent 51% attacks.  Staking to mine makes a possible attack more expensive (Even though a small stake would be required to heat mine, it is a good solution to require for other POW coins).  The unique CPID requirement makes an attack more difficult.  I am interested in more general solutions to preventing 51% attacks to make crypto safer and more sustainable.  If all coins required a unique ID like a burned CPID, Nicehash could require a CPID tied to a user's account so that someone attempting a 51% attack through Nicehash would be stopped.  

Wallet has been running for hours, but no POBh possible.



Thx for looking into this. In the meantime: is there an archive with the old 1.1.2.4 win64-install? I'd like to go back to that for the time being...




Edit: now, after approx. 5 hours, it seems to have sorted itself out again. PODCUpdate also works again. The datalist output remains the same.