Quote from: sunk818 on Today at 03:50:56 PM
Miners want to know if BiblePay can only mine BBP and XMR. Could BiblePay mine other altcoins that use RandomX so BBP, XMR, and this other altcoin? I think the term "merged-mining" gets thrown around a lot like DogeCoin with LiteCoin. You seem to have specifically used dual mining which I feel is a different technology than merged-mining. Am I correct in this assumption?
Please see this wiki page first:
http://wiki.biblepay.org/Preventing_Preimage_AttacksWhile implementing dual hash mining, I encountered the Preimage attack vector, and decided to use our equation for dual hash mining instead of classic merged mining (they are almost the same, but a couple small differences exist on the pool side and in the wallet).
Yes, the good news is the underlying wallet does support every RandomX coin (not just XMR).
Our block solution requires a RandomX header (from any RX based coin), proof that you are mining at the right height, and, the dual-hash (blake) solution.
However, there are a couple practical things stopping us from simply starting a second line of pools for coins other than XMR:
1) Accountability - sporks. The spork allows us to enforce solutions that only come from pools we trust (pools that promise to pay each months orphanage liquidation). We initially chose XMR so we can easily liquidate the earnings.
2) A new branch of Nomp or foundation.biblepay.org Pool specifically branched and code tailored for that other coin. This is a minor change, to nomp for example, but - it is a real change requiring developer hours and testing.
So my actual view on the matter is I wanted to see the viability of XMR + BBP for a few months, and know that it will certainly generate orphan revenue, and be a success or not a success. Then rerelease a pool with a little more orphan security (one that prevents people from circumventing the tithe completely). The biblepay core wallet has all the code necessary for security already in production. The only rules that we really need in baby step 2 is enforcement of the 10% tithe on the miners. This can certainly be done on the pool side.
So to make end-to-end security I think we will need to : monitor the pool liquidations of each address, add the sporks before the end of this month for the known pools, and enable the enforcement of hashpower for the 10% tithe over the monitored span (on the pool side).
Now in the future, if we grow signifigcantly I dont see why we cant focus on a second pool type (for another coin). If anyone is very zealous about this you can start now; you wont really need me to run the other pool. I would be open to working with that person and enabling the spork for that pool, if they promise to give the 10% for orphan charity back to the designated orphans, etc.