Author

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

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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.

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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.

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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...


full member
Activity: 1176
Merit: 111
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.
newbie
Activity: 52
Merit: 0
Well I do both.

I think pool.biblepay start working.

But purepool still shows no active workers
jr. member
Activity: 490
Merit: 4
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.
newbie
Activity: 52
Merit: 0
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.
jr. member
Activity: 490
Merit: 4
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.
jr. member
Activity: 405
Merit: 3
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. Smiley
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. Cheesy
5. The errors are independent of OS and occur on both pools (main pool and purepool) alike.

Hope this helps a bit. Wink

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 Smiley


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...
jr. member
Activity: 490
Merit: 4
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 Smiley
jr. member
Activity: 490
Merit: 4
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.
newbie
Activity: 52
Merit: 0
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
jr. member
Activity: 490
Merit: 4
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..
MIP
newbie
Activity: 362
Merit: 0
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.
jr. member
Activity: 490
Merit: 4
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. Smiley
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. Cheesy
5. The errors are independent of OS and occur on both pools (main pool and purepool) alike.

Hope this helps a bit. Wink

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 Smiley

jr. member
Activity: 490
Merit: 4
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.
full member
Activity: 364
Merit: 102


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.
newbie
Activity: 180
Merit: 0
Rob, can we change the symbol for finding a block and getting reward from a dove to a fish in homage to Matthew 17:27

However, not to give offense to them, go to the sea and cast a hook and take the first fish that comes up, and when you open its mouth you will find a shekel. Take that and give it to them for me and for yourself.”

A descending dove represents the Holy Spirit.  We wouldn't want to trouble the Holy Spirit, especially for monetary trivialities. 

Blessing of the Lord.
newbie
Activity: 180
Merit: 0

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?

This question is not addressed to me, but he has answered this question here: https://forum.biblepay.org/index.php?topic=109.0

"limit CPIDs from solving only one block per 6 block period."

Not sure if this was just a proposal, or actually in production as a safeguard already...

You really need to learn respect for the sacrament of marriage.  To combine 2 into one flesh is a big deal, especially in the eyes of God.

Please do not post Private Messages (PMs) in to a public forum. There's a reason why I PMed you and they are called Private Messages. If you can, please delete the part where I wrote you.

I'm not sure its really our place to judge others so vehemently when we are all sinners and there's no real effort to encourage change in K. Kardashian. Matthew 7:5 ESV
Quote
"You hypocrite, first take the log out of your own eye, and then you will see clearly to take the speck out of your brother’s eye."


This is what I was looking for:
Quote
from Rob
The reason a CPID with N magnitude does not need to equate to Y hashes per second for the CPIDs corresponding heat miners : is because one solved block with massive hashpower at that instance does not move the attacker closer to controlling our chain.  It moves them 1/CPID(Count) closer.  Which means my statement above, requiring you to control 51% of the cpids remains true.

Although I may have more questions as I learn more in the future.  

I appreciate you posting that link about the interaction with Swongel, but I wont delete the message you PMed: you accused me of libel.  It is up to Rob to delete the post if he decides.  No effort is made to change Kim Kardashian because it is not in our culture to make Kim Kardashian change.  Kanye has stated he is a Christian so he has ample opportunity to show her.  I wouldn't want Kim Kardashian to be broken into Christian faith.  I wouldn't have even wanted Paul the Disciple to be broken into faith.  There is only one scripture that supports breaking a person into faith: Matthew 21:44 "Anyone who falls on this stone will be broken to pieces; anyone on whom it falls will be crushed." My advice? Don't fall and look out above!  I much prefer when Christ said, "My yoke is easy and my burden is light."  The simple truth about Kim Kardashian is that it is doubtful she will change because of money.  They sell sex and sex appeal for money.  If they changed, they wouldn't make nearly so much money.  

I am making my judgement based on "Judge not lest ye be judged."  And I am prepared for judgement.

Peace be with you.
jr. member
Activity: 405
Merit: 3
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. Smiley
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. Cheesy
5. The errors are independent of OS and occur on both pools (main pool and purepool) alike.

Hope this helps a bit. Wink



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.
Jump to: