BIBLEPAY - RANDOMX INTEGRATION

Hi Earl,

On part 1 of this:
https://xmrig.com/docs/proxy/tls

So, I'm not replying that we *cant* do it, but, instead, we just cant do it at this phase.  Here is why:  One, we have this nomp system running as a proof of concept.  Although I fully believe it will work (and probably scale), I dont want to modify nomp for TLS until we know it can handle the traffic load and does not need rewritten.  Another words, there are a couple growing pains we need to go through:  One is ensuring we dont have white hat hackers trying to circumvent the charity aspect too soon (even though we are adding the sporks first), we just may need to pull in the C version of Monero and stop using minexmr (I dont want to, Im just saying we have to keep this option open), and secondly, if nomp does not scale well, if for example if we have 2000 new XMR miners and we find nomp is sluggish, instead of adding second and third pool I might write DAC-XMR in c# again (now that I know more about stratum, and Monero).  So with these unknowns, its not worth adding TLS to nomp just yet.  So, again Im not saying no, Im just saying since all the pool traffic goes through nomp, it cant handle this yet.  Of course I will get HTTPS working on nomp first and maybe we can turn on SSL for mining first as a req baby step then revisit this after that works in prod.  We will have a github open then you can put in a new issue for this once SSL is working, cool?

Yeah no problems i was just thinking, baby steps and all 


Anyways keep up the good work!

** ADDITIONAL TESTING STEP NEEDED **



I was just thinking also, since this is a *major* release (we are increasing ram footprint, switching algos, changing pools, adding randomx etc), we really should also be testing the MAC release.

Can someone please test solo mining and pool mining from a mac, and ensure biblepay-qt and biblepayd works?

I'm thinking we need to start wrapping up our testing within 7 days, so we need to do this quickly.

I also havent received any feedback on testing DAC mode yet (by anyone).

I will be rolling out the spork test tomorrow morning and testing in unit-test mode (that should be 99% reliable) then observing testnet afterwards.

** ADDITIONAL TESTING STEP NEEDED **



I was just thinking also, since this is a *major* release (we are increasing ram footprint, switching algos, changing pools, adding randomx etc), we really should also be testing the MAC release.

Can someone please test solo mining and pool mining from a mac, and ensure biblepay-qt and biblepayd works?

I will start testing solo mining on macOS. So far QT version with 2 mining threads takes 949MB RAM (81MB compressed). CPU usage is consistent with the 2 threads (marks 50% on the 4 core mac)

I will report back with any findings

Mined this block so far

Code: [Select]

Status: 10 confirmations
Date: 11/03/2020 03:21
Source: Generated
Credit: 3665.44027172 tBBP (matures in 92 more blocks)
Net amount: 0.00000000 tBBP
Transaction ID: c2e2bb92dc0e747c57f55178c1ea6aded6078f1c5d6c154e87808ba683ac6808
Output index: 0
Transaction total size: 197 bytes

Generated coins must mature 102 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

Height: 34052
Difficulty: 0.03
Time: 03-11-2020 10:21:09
Subsidy: 3665.4403

Credit: 3665.44027172 tBBP
To: yc5ooxeM3L2So41KzhJQ2GEWmQHU26w3kg 3665.0000 BIBLEPAY

Transaction:
CTransaction(hash=c2e2bb92dc, ver=3, type=5, vin.size=1, vout.size=2, nLockTime=0, vExtraPayload.size=38)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 03048500044967695e)
    CTxOut(nValue=3665.44027172, scriptPubKey=2102268878100f3f7aa982a5eb0354)
    CTxOut(nValue=6516.33826081, scriptPubKey=76a914874f7a2ed177e38b1685e4ff)


Mined this block so far

Code: [Select]

Status: 10 confirmations
Date: 11/03/2020 03:21
Source: Generated
Credit: 3665.44027172 tBBP (matures in 92 more blocks)
Net amount: 0.00000000 tBBP
Transaction ID: c2e2bb92dc0e747c57f55178c1ea6aded6078f1c5d6c154e87808ba683ac6808
Output index: 0
Transaction total size: 197 bytes

Generated coins must mature 102 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

Height: 34052
Difficulty: 0.03
Time: 03-11-2020 10:21:09
Subsidy: 3665.4403

Credit: 3665.44027172 tBBP
To: yc5ooxeM3L2So41KzhJQ2GEWmQHU26w3kg 3665.0000 BIBLEPAY

Transaction:
CTransaction(hash=c2e2bb92dc, ver=3, type=5, vin.size=1, vout.size=2, nLockTime=0, vExtraPayload.size=38)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 03048500044967695e)
    CTxOut(nValue=3665.44027172, scriptPubKey=2102268878100f3f7aa982a5eb0354)
    CTxOut(nValue=6516.33826081, scriptPubKey=76a914874f7a2ed177e38b1685e4ff)


Ok, Excellent!  We needed this.

So one other thing we need for mac, can you please compile biblepay-xmrig for mac (our branch of xmrig)?  And then deploy it and let us know the name of it, and test it also?

This would ensure you can pool mine with the mac using mac xmrig .

The pool : rxtest.biblepay.org has the correct startup info on the easy start page and the op post should be correct also.


EDIT: With the coronavirus kicking up in Europe, I realize you might be hit now, please do not put this ahead of anything that is an emergency at work.  We can always delay our go-live if need be.


Thanks!

So, just to summarize, we have plenty of time to test the DAC-qt side (but I still would like to see the testing done so we can confirm it works), but it is not holding up our go-live.

I just added our randomx-pools-spork, but I need to let some blocks pass before I can test it.  We should know if this works by the end of the night.

The only outstanding item I know of is the need to test xmrig on the mac.  I suppose that is not a show stopper either, because by the end of the month MIP should be around again to release that - and we can always tell people in prod the mac version will be out soon.

Can anyone think of anything else that we need to wrap up for this randomx release for a March 30th rollout?

I will make a wiki page describing how to heat mine with RandomX.

Actually looking at the state of the sancs I see half are POSE banned; can everyone please check their sancs and see if you have not upgraded?

Actually looking at the state of the sancs I see half are POSE banned; can everyone please check their sancs and see if you have not upgraded?

My sancs look OK, except, one I forgot to restart - so I revived it with 'exec revivesanc sancname'.
The rest are mostly Oncoapops, I think?

The dual hash miner seems real solid to me. I have been running non stop latest version.  no problems for windows or linux/ubuntu for me.

The 10%  charity fee seem pretty much spot on when i compare hashrate normal xmrig then bbpxmrigdual for 12/24 hours.

So im looking forward mainnet launch so can save up for sanctuary.

The dual hash miner seems real solid to me. I have been running non stop latest version.  no problems for windows or linux/ubuntu for me.

The 10%  charity fee seem pretty much spot on when i compare hashrate normal xmrig then bbpxmrigdual for 12/24 hours.

So im looking forward mainnet launch so can save up for sanctuary.

Thats awesome man!

Let me try to test this spork now and make some feedback.

** Feedback **

So I'm going to spare you all the boring details.  In a nutshell, I created the spork yesterday, tested it, and the test was successful.  However it did fork a few nodes (rightly so) that were running the newest version (IE that particular block was rejected). 
But, since we have a few sancs out there who are not upgraded - we kind of have a bad consensus now in testnet.

Anyway since the test was successful, what Id like to do next is create the release for production.  I'm going to notify the exchanges of this intent to upgrade in about 12 days, release it, then I'll be back in testnet.

Since we have one more very minor thing to test in testnet Id like to make one more release here before we relax.  Then when I come back we can continue testing the final part while we wait to go live in prod.

I want to thank everyone who participated in this testing, especially:  EarlZ, and Oncoapop.  Without you two, I don't think we would have been ready to release RandomX in prod on time.
I also thank everyone else who helped:  MIP, Togo, Sun and everyone who helped in the background.

I could compile our xmrig for for MacOS, please find it here

http://www.biblepay.org/xmrig_mac.zip

However it comes unsigned, so at the moment whoever wants to use it will have to disable gatekeeper to use it.
I could not test it myself yet either.

I could compile our xmrig for for MacOS, please find it here

http://www.biblepay.org/xmrig_mac.zip

However it comes unsigned, so at the moment whoever wants to use it will have to disable gatekeeper to use it.
I could not test it myself yet either.

Thank you MIP, excuse my ignorance on the matters with Mac, as I understand the part about being able to compile it and not digitally sign it (and that the user has to disable gatekeeper).

The part I am hazy on, are you unable to test it because Gatekeeper will make your whole system insecure if you test it, or are you unable to test it because of time due to the coronavirus problems?  Another words, will anyone be able to use this or do we need to find a way to sign it?

We can't sign it with our iphone app key can we?

Thank you MIP, excuse my ignorance on the matters with Mac, as I understand the part about being able to compile it and not digitally sign it (and that the user has to disable gatekeeper).

The part I am hazy on, are you unable to test it because Gatekeeper will make your whole system insecure if you test it, or are you unable to test it because of time due to the coronavirus problems?  Another words, will anyone be able to use this or do we need to find a way to sign it?

We can't sign it with our iphone app key can we?

It's mainly lack of time for signing and for testing because of the CV emergency. I will try to create a signing script and DMG today. Without signing, anyone can use the binary but disabling the gatekeeper protection for that specific binary.

Are there any other requirements for the pool besides updating the code and daemon? Do I need to add a Monero wallet or anything like that?