00:03:32 <QuickBASIC> [18:00]  crypto_grampy[m]: <QuickBASIC> "Too bad someone can't package..." <- https://github.com/garrylachman/react-native-xmrig <--- As far as I could tell it's hardcoded to algo switch on MoneroOcean.
07:43:51 <alcryptome[m]> Straggling to get P2Pool working on Linux. Does anyone know of a good guide?
07:44:12 <DataHoarder> setting up via docker, or directly as is?
07:44:37 <alcryptome[m]> Directly
07:45:42 <DataHoarder> then I'd say the README.md on p2pool is good of that
07:45:54 <DataHoarder> gets you on how to compile it, and how to run it with the commands
07:46:22 <DataHoarder> you should then be free to use your preferred method to bring it up or similar :)
07:46:34 <DataHoarder> what are you having issues with?
07:47:49 <alcryptome[m]> I followed those instructions, but I don't think that I installed xmrig or monerod correctly. 
07:50:26 <alcryptome[m]> Can run P2Pool but get: "monerod RPC v.3.5 is incompatible, update to RPC >= v.3.8"
07:51:48 <DataHoarder> you need a custom monerod version as the instructions say, and start the custom version
07:52:09 <DataHoarder> you can build off release-v0.17 at the moment https://github.com/monero-project/monero/commits/release-v0.17
07:53:16 <alcryptome[m]> I used the "Official Download Link" from the GitHub releases page for 0.17.2.3 
07:53:37 <DataHoarder> that's not enough. There are patches added after that needed to run p2pool
07:53:49 <DataHoarder> RPC and ZMQ api changes
07:54:09 <alcryptome[m]> okay
07:54:24 <alcryptome[m]> so i need to build from 0.17
07:54:25 <DataHoarder> hopefully it's on next point release, but for now, you'll have to use one of the provided binaries or build monerod yourself from that branch :)
07:54:28 <DataHoarder> aye
07:55:13 <DataHoarder> on build instructions https://github.com/SChernykh/p2pool#build-instructions
07:55:17 <DataHoarder> for monerod section
07:55:40 <DataHoarder> change the "git clone --recursive" to: git clone --recursive https://github.com/monero-project/monero.git
07:56:01 <DataHoarder> and the "git checkout" command to: git checkout release-v0.17
07:57:16 <DataHoarder> if you find issues with make release-static, use "make release" instead I think
07:59:04 <alcryptome[m]> thanks! ill give that a go 
10:00:33 <alcryptome[m]> Thanks for the help DataHoarder, I think I've got everything cooperating now.
14:22:38 <Halver[m]> Does somebody have an idea of the hashrate which is reachable with a RaspberryPi4 ? 🙏
14:24:08 <DataHoarder> not good, maybe jaska087 has numbers? or I might be misremembering
14:24:11 <DataHoarder> better on a phone
14:27:34 <jaska087> DataHoarder Never mentioned raspi hashrates, I do have raspi 1 and 2 though ;P
14:27:41 <crypto_grampy[m]> <hoverhalver[m]> "Does somebody have an idea of..." <- Pi4 doesn't have AES, so it's not going to be very good.   
14:29:32 <Halver[m]> ah yes, I forgot that ! Thanks for the reminder.
14:34:42 <hv-bridge> <sech1> RPi4 = 100 h/s
14:48:20 <crypto_grampy[m]> Seth For Privacy: it might be good to add a note in your guides to not use subaddresses
14:49:33 <crypto_grampy[m]> for p2pool 
14:52:49 <DataHoarder> it will output an error message when starting with that, but yes
14:53:02 <sethsimmons> crypto_grampy[m]: I do have that in the step where they change the address:
14:53:03 <sethsimmons> > NOTE: Be sure to create a new wallet for using with p2pool to preserve your privacy, and only use a “standard” address starting with a 4, subaddresses are not yet supported.
14:53:19 <sethsimmons> In this section: https://sethforprivacy.com/guides/run-a-p2pool-node/#download-and-run-monerod-and-p2pool-via-docker
14:54:47 <crypto_grampy[m]> awesome.  reading through the guide now.  thanks for putting this together!
16:22:04 <crypto_grampy[m]> I'm not super familiar with React / React-Native, but I think you could replace the config.json contents with something like Seth has on his page, and update the Tools.java file and  change                 pool.put("user", username); to pool.put("url", username);  .... This would allow you to set use the wallet address input as a URL input instead... also hardcode the validation line here to true:     const
16:22:04 <crypto_grampy[m]> isWalletInputValid:boolean = React.useMemo<boolean>(() => validateWalletAddress(walletInputValue), [walletInputValue]);
16:22:22 <crypto_grampy[m]> * / React-Native (Looking at that Android React Native XMrig app someone made above), but
16:23:12 <crypto_grampy[m]> might be worth a shot for a simple start/stop mining app that allows you to set a url 
16:25:35 <crypto_grampy[m]>  * I'm not super familiar with React / React-Native (Looking at that Android React Native XMrig app someone made above), but I think you could: 
16:25:35 <crypto_grampy[m]> 1. replace the config.json contents with something like Seth has on his page
16:25:35 <crypto_grampy[m]> 2. and update the Tools.java file and  change    pool.put("user", username); to pool.put("url", username);  .... This would allow you to set use the wallet address input as a URL input instead...  (maybe also remove the donation and other unnecessary setters)
16:25:35 <crypto_grampy[m]> 3. also hardcode the validation line here to true:     const isWalletInputValid:boolean = React.useMemo<boolean>(() => validateWalletAddress(walletInputValue), [walletInputValue]);
17:35:45 <alcryptome[m]> Never mined before, what is a good way to confirm that my node is indeed mining?
18:12:01 <xmrpow> I recently tried to send some xmr from a p2pool mining wallet by using the gui. The issue is that I got the following error: "failed to get outputs to mix: failed to get random outs". I do use a remote node. Does sb know what I am doing wrong there?
18:13:51 <Inge> the node might not know how to handle the coinbase tx with many outputs
18:14:00 <Inge> (guessing here)
18:15:26 <xmrpow> Before that I was able to send a transaction using the same remote node.
18:16:13 <xmrpow> Yea, but I think it s the output count.
18:16:57 <xmrpow> Smaller transactions go through. Bigger one s get stuck.
18:17:33 <xmrpow> Is this already fixed?
18:17:36 <selsta> xmrpow: too many outputs for a restricted remote node
18:17:50 <selsta> it's an anti dos measure
18:17:52 <xmrpow> Ah ok. 
18:18:17 <selsta> send smaller transactions or use a unrestricted node
18:24:47 <DataHoarder> xmrpow: use a local node, or wait until no outputs are locked
18:24:58 <DataHoarder> had the same issue with remote nodes, even trusted (???)
18:25:15 <DataHoarder> And yeah try unrestricted
18:54:02 <jaska087> 2021-10-08 15:43:01.602 [P2P8]  ERROR   bulletproofs    src/ringct/bulletproofs.cc:1075 Verification failure
18:54:03 <jaska087> hmmm
18:55:40 <jaska087> could be related copying (not syncing) the whole database from node to another and running them at he same time, on different machines?
19:06:51 <xmrpow> Datahoarder: Ok. Do you know what kind of relevant data unrestricted rpc does provide? In monerod doc it s written that public remote nodes need restricted rpc in order to prohibit data leaks. 
19:07:48 <DataHoarder> If you have many outputs it can fail :)
19:08:13 <DataHoarder> So doing a small output set at a time it can work
19:08:51 <xmrpow> Yes, but my issue here is that im not sure if i want to run a public node without restricted mode...
19:09:15 <DataHoarder> You can have two ports
19:09:22 <DataHoarder> one internal one external
19:09:36 <DataHoarder> monerod allows that :)
19:09:44 <xmrpow> Im running it on another box
19:12:10 <DataHoarder> Yes
19:12:16 <DataHoarder> you can whitelist ip 
19:12:39 <DataHoarder> or user / password at least for the non-restricted one, for the wallet
19:13:16 <xmrpow> I think the user /password  will do it
19:14:40 <jaska087> unrestriced rpc allows remote node closing, setting it to mine for evil ppl and so on
19:14:54 <jaska087> that user / pass is best approach
19:15:29 <xmrpow> jaska: Ok. Then it does make sense to have restricted rpc :)
19:16:36 <jaska087> Well as DataHoarder said, user / pass is best for remote node if you trust users who can have full access on it.
19:16:54 <xmrpow> Ok. Thank you guys!