-
m-relay
<ofrnxmr:xmr.mx> 🫡
-
m-relay
<ofrnxmr:xmr.mx> ^
-
m-relay
<lza_menace:monero.social> does btcpayserver monero plugin support a payout option?
-
m-relay
<lza_menace:monero.social> or do you need to import a view only wallet into it and manage the wallet outside of btcpay?
-
m-relay
<loeasy6:matrix.org> Just picked up an 1TB Sankdisk ssd
-
m-relay
<loeasy6:matrix.org> I'm not sure, What is btcpayserver?
-
m-relay
-
m-relay
<basses:matrix.org> terrible replies, please help this guy with logical guesses
-
m-relay
<shortwavesurfer2009:monero.social> For Fiat, I don't think so, since there would be no payment processor.
-
m-relay
<root:kimapr.net> integrated address
-
m-relay
<root:kimapr.net> Aren't payment ids deprecated nowadays
-
m-relay
<root:kimapr.net> there's 0 reason not to use subaddresses instead
-
m-relay
<jivan:opaline.uk> It's a self-hostable cryptocurrency payment processing platform.
-
m-relay
<marioob:matrix.org> Hello. For mining xmr is there a big difference in using multiple memory channels? Workstation CPUs can use anywhere from 4 to 12 channel memory. So, does it worth populating all of them?
-
m-relay
<fijxu:nadeko.net> I doubt it, RAM is very fast and I don't think adding more channels is going to make any difference
-
nioCat
the most basic setup is 2 channel memory and using both is significantly faster than using 1. If 4 channels then that is faster than 2 but I have no idea by what %
-
nioCat
beyond that I don't know
-
nioCat
AIUI 1 stick per channel is best
-
sech1
1 memory channel = 10-12 kh/s max, no matter how hard you try. So you need all memory channels for high core count CPUs
-
m-relay
<marioob:matrix.org> So, increasing memory channels beyond 2, will still give proportional increases in hashrate?
-
sech1
If your CPU supports it
-
sech1
And has enough cores and cache
-
m-relay
<marioob:matrix.org> Plan to build a x2 socket CPU server for mining. And trying to fin out if 4 RAM sticks (dual channel each CPU) will be hugely different from 24 RAM sticks (12 channel per CPU)
-
m-relay
<marioob:matrix.org> Plan to build a x2 socket CPU server for mining. And trying to find out if 4 RAM sticks (dual channel each CPU) will be hugely different from 24 RAM sticks (12 channel per CPU)
-
sech1
It depends on CPU
-
sech1
You can check your CPU on
xmrig.com/benchmark and see how many memory sticks the best results use
-
m-relay
<marioob:matrix.org> ty
-
m-relay
<lza_menace:monero.social> meant for xmr - i don't see a way to have the wallet send the funds out (i have a generated wallet on the server, did not import from a view key)
-
m-relay
<lza_menace:monero.social> so it seems like i'll just need to import a view key instead
-
m-relay
<jivan:opaline.uk> You mean for the store to receive payments from customers?
-
m-relay
<jivan:opaline.uk> In BTCPay, "payout" refers to setting aside funds for a user to claim at any future time using a privately shared URL
-
m-relay
<jivan:opaline.uk> My understanding is that these can't be automated on a regular basis, at least not using BTCPay's own tooling.
-
m-relay
<lza_menace:monero.social> oh, didn't realize that. i meant how to have the btcpayserver wallet transfer funds to my personal wallet
-
m-relay
<lza_menace:monero.social> but it seems like that's not support and what you're supposed to do is either upload a view key or copy the private keys from the btcpayserver wallet
-
m-relay
<fede:xmr.mx> why would you do this? if only view key touches the server then the wallet is secure
-
m-relay
<lza_menace:monero.social> it's just how i had set it up at the time. when provisioning the server a wallet is generated for btcpayserver to use so it's all automated one click
-
m-relay
<jivan:opaline.uk> That's correct, please read the documentation, most storefront implementations work in this way
-
m-relay
-
m-relay
<loeasy6:matrix.org> Hi