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

[thesnat21]

I don't see a problem with 1.1.2.6, this looks to be on your end.

Classic IT response..  I'll sit back and watch if others encounter issues.

edit2:
Same message on testnet with a "clean" install and associated cpid.

[thesnat21]

So I tested 1.1.2.6 on my two Windows machines (old Thinkpad Win7, newer Xeon Win10). Here's what I see so far:

1. The startup is indeed much faster without the "memorizing prayers" step. Nice work there.
2. After the wallet opened there is a longer period of time with huge CPU utilization. This is the "memorizing prayers" step I suppose?
3. I immediately got the CPID errors mentioned by thesnat.
4. The self-payment Rob suggested helped this error for approx. 1 minute, then it returned.
5. The errors are independent of OS and occur on both pools (main pool and purepool) alike.

Hope this helps a bit.

Edit: Well, that's strange. On my Win10-Xeon it seems to have sorted itself out after maybe 10 minutes and is now submitting solutions as usual. On the Win7-Thinkpad getmininginfo is still full of CPID errors.

Thanks Dave,  Glad i'm not crazy

[MIP]

iOS only allows background execution tasks for a short period of time.

So BOINC is not only limited by policies or processor but also by the OS internals itself.

BTW on iOS wallet app. I'm getting more and more questions from Testflight evaluators.

I also got report that conditions for publishing crypto wallets in App Store have been hardened, to the point that only "Corporate" apple developer accounts would be entitled to publish such apps.

[thesnat21]

I also got report that conditions for publishing crypto wallets in App Store have been hardened, to the point that only "Corporate" apple developer accounts would be entitled to publish such apps.

This is unfortunate, but fits in with Apple's corporate model of dictatorship..

[pagalo]

Hello

I have some Windows PCs on pool.biblepay.org
100% CPID_SIGNATURE_INVALID

I also have some Windows PCs on purepool.org
All PCs Invalid_CPID


I have 1.1.2.6 version installed


Also have Task & UTXO weight 0

[thesnat21]

Hello

I have some Windows PCs on pool.biblepay.org
100% CPID_SIGNATURE_INVALID

I also have some Windows PCs on purepool.org
All PCs Invalid_CPID


I have 1.1.2.6 version installed


Also have Task & UTXO weight 0

Is this a new install, or you upgraded?

Can you run "exec getboincinfo" in the debug window and post here?  then we can try to help troubleshoot.

[thesnat21]

RE: PoDC Update

I seem to be able to send PoDC Updates with zero fee.

Can someone else try?

Send tab
* Radio box on Custom
* Uncheck Pay only the required fee
* Check on Send as zero-fee

Not sure what the consequence of zero-fee will be when the network has more traffic and solo/pool miners decide what transactions (txs) to include in a block.

You can do it while there is a low transaction volume I suppose?

The risk would be your transactions are at the back of the line, and if the mempool gets large enough may never get processed into a block

Probably minimal risk at present, but it's bad practice not to support the network

[dave_bbp]

So I tested 1.1.2.6 on my two Windows machines (old Thinkpad Win7, newer Xeon Win10). Here's what I see so far:

1. The startup is indeed much faster without the "memorizing prayers" step. Nice work there.
2. After the wallet opened there is a longer period of time with huge CPU utilization. This is the "memorizing prayers" step I suppose?
3. I immediately got the CPID errors mentioned by thesnat.
4. The self-payment Rob suggested helped this error for approx. 1 minute, then it returned.
5. The errors are independent of OS and occur on both pools (main pool and purepool) alike.

Hope this helps a bit.

Edit: Well, that's strange. On my Win10-Xeon it seems to have sorted itself out after maybe 10 minutes and is now submitting solutions as usual. On the Win7-Thinkpad getmininginfo is still full of CPID errors.

Thanks Dave,  Glad i'm not crazy

I realized that actually it also sorted itself out on my Win7 laptop, just much later. So it seems to be a problem of time (or rather of number of submitted shares?).

I then tried closing the wallet and starting it again and - lo and behold - the errors were back. Also without the "bug-fixing" self-payment they persist over hours. I now made the transaction again but for 20 minutes it hasn't solved the errors yet...

[thesnat21]

I realized that actually it also sorted itself out on my Win7 laptop, just much later. So it seems to be a problem of time (or rather of number of submitted shares?).

I then tried closing the wallet and starting it again and - lo and behold - the errors were back. Also without the "bug-fixing" self-payment they persist over hours. I now made the transaction again but for 20 minutes it hasn't solved the errors yet...

I let a few machines run overnight, they never resolved themselves.

Associated my CPID to a new wallet in test,  same issue.

So it's not legacy data causing the issue.

[pagalo]

They are upgraded.


{
  "Command": "getboincinfo",
  "CPID": "fa5062d1c29baf2e298b674f40ee59b7",
  "Address": "BJZ4XQ8XghfBmHedGfSz16TfdjVsSiK3u6",
  "CPIDS": "fa5062d1c29baf2e298b674f40ee59b7;",
  "CPID-Age (hours)": 424693,
  "NextSuperblockHeight": 52275,
  "NextSuperblockBudget": 1144187,
  "fa5062d1c29baf2e298b674f40ee59b7_ADDRESS": "BJZ4XQ8XghfBmHedGfSz16TfdjVsSiK3u6",
  "fa5062d1c29baf2e298b674f40ee59b7_RAC": 42844.58,
  "fa5062d1c29baf2e298b674f40ee59b7_TEAM": 15044,
  "fa5062d1c29baf2e298b674f40ee59b7_WCGRAC": 0,
  "fa5062d1c29baf2e298b674f40ee59b7_TaskWeight": 100,
  "fa5062d1c29baf2e298b674f40ee59b7_UTXOWeight": 786389,
  "Total_RAC": 42844.58,
  "Total Payments (One Day)": 6195,
  "Total Payments (One Week)": 33656,
  "Total Budget (One Day)": 1144187,
  "Total Budget (One Week)": 6865122,
  "Superblock Count (One Week)": 7,
  "Superblock Hit Count (One Week)": 7,
  "Superblock List": "52070,51865,51660,51455,51250,51045,50840",
  "Last Superblock Height": 52070,
  "Last Superblock Budget": 1144187,
  "Last Superblock Payment": 6195,
  "Magnitude (One-Day)": 5.414324756355386,
  "Magnitude (One-Week)": 4.902462039276214
}

Task & UTXO came back to normal.

Hello

I have some Windows PCs on pool.biblepay.org
100% CPID_SIGNATURE_INVALID

I also have some Windows PCs on purepool.org
All PCs Invalid_CPID


I have 1.1.2.6 version installed


Also have Task & UTXO weight 0

Is this a new install, or you upgraded?

Can you run "exec getboincinfo" in the debug window and post here?  then we can try to help troubleshoot.

[thesnat21]

They are upgraded.

Task & UTXO came back to normal.

Hello

I have some Windows PCs on pool.biblepay.org
100% CPID_SIGNATURE_INVALID

I also have some Windows PCs on purepool.org
All PCs Invalid_CPID


I have 1.1.2.6 version installed


Also have Task & UTXO weight 0

Is this a new install, or you upgraded?

Can you run "exec getboincinfo" in the debug window and post here?  then we can try to help troubleshoot.

Ok, unfortunately this seems to be an issue with the 1.1.2.6 client,  I suggest downgrading if you are heat mining.

[pagalo]

Well I do both.

I think pool.biblepay start working.

But purepool still shows no active workers

[sunk818]

Yes, Kim Kardashian was married to...

Can we please try to keep this post specifically relevant to BiblePay. For example, I don't think everyone wants to read some of the things you posted, certainly it would make some people (for example my wife, or some teenage girl who is interested in BiblePay) uncomfortable to hear about personal sin issues, especially of the kind you wrote about.

Perhaps you could start up a new channel for confessing sin, asking for prayer for these things. But in my opinion, it is better to keep this channel about BiblePay cryptocurrency.

Which is precisely why I PMed aikida3k instead.

[bible_pay]

I don't see a problem with 1.1.2.6, this looks to be on your end.

Classic IT response..  I'll sit back and watch if others encounter issues.

edit2:
Same message on testnet with a "clean" install and associated cpid.

...  Let me check into this...

[bible_pay]

I don't see a problem with 1.1.2.6, this looks to be on your end.

Classic IT response..  I'll sit back and watch if others encounter issues.

edit2:
Same message on testnet with a "clean" install and associated cpid.

...  Let me check into this...

I dont see a problem with 1.1.2.6, Im still mining after 24 hours. 

To diagnose this in prod, first type:

exec datalist dcc;YYYY 365

Where YYYY equals the first 4 chars of your CPID.  Paste the results here.

Step 2:

Type 'exec podcupdate' and paste the results here.


I'm sure the other person who had the problem resolved itself after the prayers were memorized.  The high cpu usage during 15 seconds after the GUI loads is just the prayers being memorized in the background.

You should leave the machine on for at least 10 minutes of mining to see if the errors clear.

[bible_pay]

Man, what's up with our POW difficulty right now? 26006 - and it's been over an hour since the last block as a result. Crazy.

I don't understand this obsession with PoW difficulty. Difficulty goes up and down to keep the average blocktime as close to 7 minutes as possible. Since network hashrate changes and time to produce an acceptable hash is not guaranteed, you will see fluctuation of blocktime and difficulty. Ideally, you want the smallest gap between min & max time between blocks but this not possible with proof-of-work algorithm.

Well, I'm not sure I'd go with the word "obsession" - but let me explain why it is interesting. The sliding scale of difficulty to hit 7 minute blocks is obvious and uninteresting - however, you said it yourself, that the network hashrate changes. The comment is roughly equivalent to "wow, our network hashrate 2 hours ago must have been much much higher than now, because our difficulty is high and it has taken a long time to get a block as a result - meaning that the difficulty will again soon slide back down to adapt to the fact that our network hashrate has shrunk."

What it does it tell us some things about who is mining when. If the network hash suddenly increases such that our difficulty triples for an hour or two and then goes back down, how is that not a conversation topic? Nobody who has that much hash power is doing this adhoc, which means we have the part-time attention of some very big players. I find that a worthy note and a good discussion point. I do NOT find "DUH, 7 minute blocks!" to be an interesting point, but I guess to each their own.

If the network hash rate is suddenly increasing for a short time, someone could very well be attempting a 51% attack to try and attempt to induce the ability to double spend.  

Rob, what are the controls that make sure this doesn't happen?  What prevents someone from registering a CPID with Rosetta and then spinning up as many heat miners as they can to try and gain 51% or more of the network hash rate?  They don't have the incentive to heat mine for reward but they have an incentive to attack and double spend.

I don't yet know as much about this as I should, but doesn't the chain have to fork for a 51% attack and an attempt at double spend (spending currency the attacker did not earn) to be successful?  So at 51% of the hash rate the attacker has the ability to enforce their own version of the blockchain, which in their own version, they could give themselves as much coin as they wanted.  Couldn't we use the masternodes as trusted nodes to check for forks in the chain or unauthorized changes in the chain to prevent a successful 51% attack?  Can you explain the security we have against a 51% attack?  Thanks, Rob.

We have better 51% attack protection than bitcoin but we are cheaper to attack (being smaller).  Bitcoin has the problem of concentrated asics owned by a small quantity of miners that could collude together to attack.  We have the broad base of 2500 pc's, which are more likely to be decentralized.  So that part is the run of the mill answer (IE pc based vs ASIC based).

However what we have added that makes it a magnitude harder to attack us is we require a distinct CPID to solve each block, and the CPID must have magnitude.  Every 4th block we clear the buffer and allow (the old CPID to start again).  This means we effectively break the ability to solve consecutive blocks.  Of course you could own more than one CPID with mag, but you would need to buy 51% of the CPID pool, and thats a lot of research, in order to add an effective attack vector on top of the one above (IE the classic 51%).  So in our case it looks like a 51% attack would be : 51% of the CPIDs, with magnitude, running on 51% * 2500 PC's (heat mining portion) - heat mining PCs running boinc with at least 250 CPIDs (based on last superblock of 524 researchers) with magnitude.  It would be an expensive attack.  We also have DGW (dark gravity wave) which increases the diff during an attack.  

If the perpetrator were trying to issue a coinbase, they would need 100 confirms, which is pretty much impossible.  I don't want to discuss this publically to give any more ideas to any large whales and fuel the fire with any chance of putting our coin at risk.

[dave_bbp]

I don't see a problem with 1.1.2.6, this looks to be on your end.

Classic IT response..  I'll sit back and watch if others encounter issues.

edit2:
Same message on testnet with a "clean" install and associated cpid.

...  Let me check into this...

I dont see a problem with 1.1.2.6, Im still mining after 24 hours.  

To diagnose this in prod, first type:

exec datalist dcc;YYYY 365

Where YYYY equals the first 4 chars of your CPID.  Paste the results here.

Step 2:

Type 'exec podcupdate' and paste the results here.


I'm sure the other person who had the problem resolved itself after the prayers were memorized.  The high cpu usage during 15 seconds after the GUI loads is just the prayers being memorized in the background.

You should leave the machine on for at least 10 minutes of mining to see if the errors clear.

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

Code:

{
  "DataList": "DCC;7C92",
  "4559FEF3C1C689EE9FC3FF42494 (03-07-2018 20:01:05)": "7c9264559fef3c1c689ee9fc3ff42494;BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh;BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh;1981794;IIN5nTV5xxNV9tflryvwAcWzvf9WyxKPUx1XxpKGl1tgOZQ3uXzDIxPgjxxTtUIyZXHa1TMzDuTFcPDS7cl/U10=;0"
}

Code:

{
  "Command": "podcupdate",
  "PODCUpdate": "Unable to find any CPIDS.  Please try exec getboincinfo."
}

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.

[aikida3k]

Man, what's up with our POW difficulty right now? 26006 - and it's been over an hour since the last block as a result. Crazy.

I don't understand this obsession with PoW difficulty. Difficulty goes up and down to keep the average blocktime as close to 7 minutes as possible. Since network hashrate changes and time to produce an acceptable hash is not guaranteed, you will see fluctuation of blocktime and difficulty. Ideally, you want the smallest gap between min & max time between blocks but this not possible with proof-of-work algorithm.

Well, I'm not sure I'd go with the word "obsession" - but let me explain why it is interesting. The sliding scale of difficulty to hit 7 minute blocks is obvious and uninteresting - however, you said it yourself, that the network hashrate changes. The comment is roughly equivalent to "wow, our network hashrate 2 hours ago must have been much much higher than now, because our difficulty is high and it has taken a long time to get a block as a result - meaning that the difficulty will again soon slide back down to adapt to the fact that our network hashrate has shrunk."

What it does it tell us some things about who is mining when. If the network hash suddenly increases such that our difficulty triples for an hour or two and then goes back down, how is that not a conversation topic? Nobody who has that much hash power is doing this adhoc, which means we have the part-time attention of some very big players. I find that a worthy note and a good discussion point. I do NOT find "DUH, 7 minute blocks!" to be an interesting point, but I guess to each their own.

If the network hash rate is suddenly increasing for a short time, someone could very well be attempting a 51% attack to try and attempt to induce the ability to double spend.  

Rob, what are the controls that make sure this doesn't happen?  What prevents someone from registering a CPID with Rosetta and then spinning up as many heat miners as they can to try and gain 51% or more of the network hash rate?  They don't have the incentive to heat mine for reward but they have an incentive to attack and double spend.

I don't yet know as much about this as I should, but doesn't the chain have to fork for a 51% attack and an attempt at double spend (spending currency the attacker did not earn) to be successful?  So at 51% of the hash rate the attacker has the ability to enforce their own version of the blockchain, which in their own version, they could give themselves as much coin as they wanted.  Couldn't we use the masternodes as trusted nodes to check for forks in the chain or unauthorized changes in the chain to prevent a successful 51% attack?  Can you explain the security we have against a 51% attack?  Thanks, Rob.

We have better 51% attack protection than bitcoin but we are cheaper to attack (being smaller).  Bitcoin has the problem of concentrated asics owned by a small quantity of miners that could collude together to attack.  We have the broad base of 2500 pc's, which are more likely to be decentralized.  So that part is the run of the mill answer (IE pc based vs ASIC based).

However what we have added that makes it a magnitude harder to attack us is we require a distinct CPID to solve each block, and the CPID must have magnitude.  Every 4th block we clear the buffer and allow (the old CPID to start again).  This means we effectively break the ability to solve consecutive blocks.  Of course you could own more than one CPID with mag, but you would need to buy 51% of the CPID pool, and thats a lot of research, in order to add an effective attack vector on top of the one above (IE the classic 51%).  So in our case it looks like a 51% attack would be : 51% of the CPIDs, with magnitude, running on 51% * 2500 PC's (heat mining portion) - heat mining PCs running boinc with at least 250 CPIDs (based on last superblock of 524 researchers) with magnitude.  It would be an expensive attack.  We also have DGW (dark gravity wave) which increases the diff during an attack.  

If the perpetrator were trying to issue a coinbase, they would need 100 confirms, which is pretty much impossible.  I don't want to discuss this publically to give any more ideas to any large whales and fuel the fire with any chance of putting our coin at risk.

Every 4th block we clear the buffer and allow (the old CPID to start again).  This means we effectively break the ability to solve consecutive blocks.  Of course you could own more than one CPID with mag, but you would need to buy 51% of the CPID pool, and that's a lot of research, in order to add an effective attack vector on top of the one above (IE the classic 51%).

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.  

[aikida3k]

Yes, Kim Kardashian was married to...

Can we please try to keep this post specifically relevant to BiblePay. For example, I don't think everyone wants to read some of the things you posted, certainly it would make some people (for example my wife, or some teenage girl who is interested in BiblePay) uncomfortable to hear about personal sin issues, especially of the kind you wrote about.

Perhaps you could start up a new channel for confessing sin, asking for prayer for these things. But in my opinion, it is better to keep this channel about BiblePay cryptocurrency.

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. 

[zthomasz]

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?