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

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: WhyMe on January 20, 2020, 11:30:28 AM

Seems to be working, wallet is synching now, thanks.
But we can't upgrade from 1.4.8.5 ?

From what I understand we already released the binaries, could you please ensure you are running the right bitness? If not please post the URL and platform-bitness?
Im running windows 64 here and Im on 1487. I never uninstall the old version; I just install the latest and it works.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: bible_pay on January 20, 2020, 11:10:44 AM

Quote from: WhyMe on January 20, 2020, 11:05:33 AM

You use a standard x11 hash, then you use it in your pobh layer.
But it stays a true x11 hash, which is gpu and asic mineable since years ...

1) No, we don't
2) I am aware of randomX and its entire virtual machine and its code; and this is already taken into account for our dotnetcore version.

If you would like to give an example as to how you would run POBH in an asic or gpu, feel free to continue the discussion, but you cant.
Please review the code again in kjv.cpp.

Just to give more clarity on this, let me explain how a POBH hash is computed and why you cant run POBH in a GPU (because you claimed 'this x11 was gpu and asic mineable for years'):

1) The hash of the block header is hashed with X11 first, but not used in the core wallet
2) The X11 hash is hashed with POBH
3) The POBH hash is used in the wallet

Therefore, you can't hash it in a GPU, and skip over the POBH hash and use it in BBP. Of course Marcino, who ported POBH v1.0 to GPU actually *ported* the whole KJV and all of our code *into CUDA*, so he didnt simply run X11 in a GPU to mine bbp.

The new version released today is a *Stopgap* version. It I believe, is going to be fine until we release our next-gen miner. I want to stress, we are still working on something cooler that will do useful work while it mines in POW mode. But POBH 2.0 is still very good- because it still produces bible verses, and cant run in an gpu due to the new rules. I'm sure Marcino can certify this as he tries to hack it. Because it will take the hacker more clock cycles to circumvent security than to create a new block in parallel. The new security is based on the fact that a GPU miner must create more blocks than they care to per second of hashing.

WhyMe

sr. member

Activity: 661

Merit: 250

Seems to be working, wallet is synching now, thanks.
But we can't upgrade from 1.4.8.5 ?

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: WhyMe on January 20, 2020, 11:26:17 AM

New wallet is crashing. Installed on previous version.
Error was 2020-01-20 16:06:52 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at CBlockDiskPos(nFile=0, nPos=11296509)
I deleted my blocks directory to force rescan, now is crashing with no error in log.

Have you tried restarting with the "-erasechain=1" switch?

WhyMe

sr. member

Activity: 661

Merit: 250

New wallet is crashing. Installed on previous version.
Error was 2020-01-20 16:06:52 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at CBlockDiskPos(nFile=0, nPos=11296509)
I deleted my blocks directory to force rescan, now is crashing with no error in log.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

** Compassion Update **

So I just want to give a compassion.com transparency update.

We've spent $177,224 at compassion (which is btw, 82% of our total charity expenses since inception). We sponsored 4,657 orphan months of charity with them! An amazing accomplishment! Thank you everyone, this has certainly aligned a lot of our users with God by fulfilling James 1:27 for them.

Anyway, I gave them the 30 day notice to cancel all of our 81 children as of Jan 20th 2020 (to give us close to a zero balance).
However what's nice about Compassion is they not only have an insurance program to continue to cover a canceled child. But also they sometimes give us a credit balance back for the extra days. So we still have something like a $1,600 credit available to spend; and I was originally going to suggest Compassion for Babies, but since then I have come up with a better idea (also babies don't allow us to generate bios so there is less accountability).

I think what we can do for the most impact is go ahead and sponsor 10 more children with compassion, and this will give us approx 4 more months of positive impact then I will repeat the process and cancel those 10 around the beginning of May.

Praise Jesus.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: WhyMe on January 20, 2020, 11:05:33 AM

You use a standard x11 hash, then you use it in your pobh layer.
But it stays a true x11 hash, which is gpu and asic mineable since years ...

1) No, we don't
2) I am aware of randomX and its entire virtual machine and its code; and this is already taken into account for our dotnetcore version.

If you would like to give an example as to how you would run POBH in an asic or gpu, feel free to continue the discussion, but you cant.
Please review the code again in kjv.cpp.

WhyMe

sr. member

Activity: 661

Merit: 250

You use a standard x11 hash, then you use it in your pobh layer.
But it stays a true x11 hash, which is gpu and asic mineable since years ...

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: WhyMe on January 20, 2020, 10:53:48 AM

Why continue using standard x11 hash if you don't want gpu ? If you don't want gpu taking advantage, why not migrate to randomX for example ?

Ours is far different than x11: We have POBH, which has the KJV bible in it, and it has anti-gpu features on top of it.

The new bounty will be reinstated that POBH 2.0 cannot function better in a GPU than in a CPU.

EDIT: The x11 you see in nomp is just the label (its there because we also use x11 below pobh). I'll edit it.

WhyMe

sr. member

Activity: 661

Merit: 250

Why continue using standard x11 hash if you don't want gpu ? If you don't want gpu taking advantage, why not migrate to randomX for example ?

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

So far so good, I just ran my sanctuary report and the nodes are all in sync and agree with the explorer (Chainz has already upgraded):

https://chainz.cryptoid.info/bbp/block.dws?170840.htm

Please, if anyone finds a discrepency after upgrading - post.

I'll verify POBH 2.0 and DWS next. Caution: Although DWS appears to be working now, I caution against using it for a few days until we verify we are exchange ready. We don't want a burn in the chain to get rolled back when more hashpower gets added (as you could lose the funds if your burn is not recorded in the main chain).

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: Borgholio on January 20, 2020, 02:58:34 AM

Out of curiosity, what's the difference between the bbpminer-x86.exe and the bbpminer32.exe binaries? Thanks!

The x86 version is the 64 bit version, and the 32 is for 32 bit processors.
(I remember we had to add the 32 for Prof. Budinga when he reported the 64 bit didn't run on his 32 bit windows xp machine).

Good luck. I see our diff is around 5K. Not sure if this is because of low switchover rates or if this is the new environment.

Borgholio

newbie

Activity: 99

Merit: 0

Out of curiosity, what's the difference between the bbpminer-x86.exe and the bbpminer32.exe binaries? Thanks!

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

BiblePay
1.4.8.6-Mandatory Upgrade for Entire Network @ 170830

- Increase sanctuary protoversion to 70751 (Enable new consensus rules
for PODC - fix low payment bug)
- Adjust deflation rate to match target in GetBlockSubsidy
- Add anti-gpu measures to POBH (reject high-nonce blocks)
- Mandatory height: 170830
- Adjust DWS creation and validation for DWS 2.0
- Add upgradesanc warning when no \r\n exists (Togo)
- Add addl warnings to exec rac, and ensure exec rac does not crash the
node
- Remove dead code from miner; modify miner to handle anti-gpu nonce
rules

** Note: We also have a mandatory upgrade for the external miner, please find the binaries here:
https://github.com/biblepay/cpuminer/tree/master/binaries

** Sanctuaries, please upgrade also

** The new POBH 2.0 rules do not start until 170830, so in the mean time, the pool will reject most of the shares. As soon as this height passes the pool should start working correctly. The pool is coming back online now.

POOLS: Please upgrade. The software has been updated here:
https://github.com/biblepay/node-stratum-pool/commits/master
To upgrade please follow the upgrade instructions in this document:
https://github.com/biblepay/node-open-mining-portal/blob/master/Deploy%20a%20Nomp%20BiblePay%20Pool.txt

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

** BBP Network Wide update **

So, I heard back from all the exchanges and they all have put us in maintenance.

This puts us in a good position to release our new mandatory upgrade and regression test/verify it tomorrow in prod, to ensure the anti-gpu feature works as expected. Once we verify DWS and Anti-GPU, then we will give the exchanges the green light to upgrade.

So the timeline looks something like this now:

- We will release the new mandatory upgrade in the next few hours.
- The cutover height is for tomorrow at 9 AM.
- We will verify DWS and Anti-GPU in prod tomorrow. Then we give the exchanges the green light to upgrade Tuesday.
- Sometime tomorrow, I will be working on releasing an upgrade to the external miner. This will be required to work with the new version.

Please keep your eyes peeled for the mandatory upgrade. The chain will cutover at height 170830.

Sanctuaries, we are going to take this opportunity to require a mandatory Sanc upgrade at the same time. This upgrades the PODC rules to the latest which fixes the low payment bug also.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: Borgholio on January 18, 2020, 06:09:58 PM

If the pool is currently disabled, is the processing we're doing now being wasted? Thanks!

No, the hashpower is not wasted because what happens is the stratum error (cant connect to pool) occurs, then it sleeps, so it doesnt use electricity; but yes, the miner would have to be restarted in solo mining mode to make the hashes count.

Actually this is a good point, because we would like everyone to help keep the network secure, so please run your biblepay client in solo mining mode if possible.

Borgholio

newbie

Activity: 99

Merit: 0

If the pool is currently disabled, is the processing we're doing now being wasted? Thanks!

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: bible_pay on January 18, 2020, 12:20:50 PM

Quote from: bible_pay on January 17, 2020, 04:42:23 PM

We have 31 Megahash hitting nomp.biblepay.org (this is about 31* the normal rate).
I see the pool has solved over 75 blocks, which is way above normal.
SouthXChange even asked me about this, please if anyone has any idea what is going on let me know.

From what I can see, everything is fine.
All of our sanctuaries are in sync at the current height (looking at the advanced view, which shows the hash), so I know the chain is solid.

Im happy to see 55 WCG/smart-contract participants! God bless you.

Ok, so we finally have an answer on this 31 megahash hitting the pool: we believe Marcino ported BBPs miner to a GPU.

Thats impressive, but, I don't believe we should become a GPU coin. We have something to offer the PC community (and also for using commodity pcs).

This schedule is subject to change, but let me lay out a rough call to action:

- Block any user in the pool that hits with more than 1mh/s
- Work the ticket that we have, where we equalize the hash speed between solo and external mining
- Finish the next gen cpu miner in testnet
- Test CPU mining and the new dash changes that have been released (Nov-Dec 2020 changes) all at once in testnet
- Release our new cpu miner in our next mandatory upgrade (March 2020)

** UPDATE **

- We are going to release a GPU mitigation release (a mandatory upgrade) within 7 days. This is primarily due to the decision that we don't want an unfair advantage floating around for GPUs while CPUs make a lesser share. Additionally we don't want any potential security vector attacks to be possible. So please be ready to upgrade within 7 days. We will also be notifying exchanges. (This release will also include our necessary changes to fix the PODC low-payment bug for users who do not meet the escrow reqs).
- MIP has been speaking with Marcino and he tells me he is not acting in a hostile fashion. He is keeping his hashpower low and not attacking the coin.
- I have taken the pool offline for now. I'll bring it up later after the upgrade (as it is just a cat & mouse game to keep it running).
- We sent Marcino info on our POBH bounty. Afaik it will be paid to him, as I believe he has met the requirements.
- We will still focus on designing and releasing our next gen cpu-miner after this mandatory patch is released.
- The patch will be nomp compatible, and will also make solo mining equal to external mining (based on the most recent information).

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: bible_pay on January 17, 2020, 04:42:23 PM

We have 31 Megahash hitting nomp.biblepay.org (this is about 31* the normal rate).
I see the pool has solved over 75 blocks, which is way above normal.
SouthXChange even asked me about this, please if anyone has any idea what is going on let me know.

From what I can see, everything is fine.
All of our sanctuaries are in sync at the current height (looking at the advanced view, which shows the hash), so I know the chain is solid.

Im happy to see 55 WCG/smart-contract participants! God bless you.

Ok, so we finally have an answer on this 31 megahash hitting the pool: we believe Marcino ported BBPs miner to a GPU.

Thats impressive, but, I don't believe we should become a GPU coin. We have something to offer the PC community (and also for using commodity pcs).

This schedule is subject to change, but let me lay out a rough call to action:

- Block any user in the pool that hits with more than 1mh/s
- Work the ticket that we have, where we equalize the hash speed between solo and external mining
- Finish the next gen cpu miner in testnet
- Test CPU mining and the new dash changes that have been released (Nov-Dec 2020 changes) all at once in testnet
- Release our new cpu miner in our next mandatory upgrade (March 2020)

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: shorty34 on January 18, 2020, 04:08:53 AM

Quote from: slovakia on January 18, 2020, 12:37:34 AM

any new users (all tutorials looks very amateur)

i can help you with setup

masternode
PODC
mining

PM me (Slovak Team = orbis/capulo/slovakia)

co tak si konecne zobrat priklad z inych minci web,navody atd

Great job Slovaks

And I will help newcomers with the stake requirement. Here is the deal:

1. Open a new account on World Community Grid
2. Join team Biblepay, make sure "Display my data" and "Link my devices" boxes are checked under the "Data Sharing" tab
3. Start solving tasks
4. Download BBP wallet and synchronize (Do not acquire any BBP)
5. Once your WCG RAC is greater than 250 (no big deal - one core over a few days), find me on BBP Discord (shorty)
6. Upon confirmation of your RAC, I will send you 1500 BBP (more than the stake requirement for 250 RAC)

The rest is upon you - follow guides and get help from Slovaks and keep earning BBP through the PODC daily rewards as long as you crunch for WCG.

This offer is valid for the first 100 newcomers. Please note you have to be a new WCG member to be eligible.

May God bless & reward everyone that contributes to science in both worlds !

This is great!

And also, remember users can also get 200bbp from web.biblepay.org | Faucet.

And, as a backup for Shorty, I am available to send some free BBP to new CPIDs if you email me at [email protected] if the faucet didnt give you enough.

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