for solo mining you get absolutely nothing unless you find a block right?

correct

Revuo Issue 102: Jan 02-09, 2022. localmonero.co/revuo/weekly/102

Mochi102: not entirely correct. you get the good feeling in your heart knowing you contributed to making the network more secure.

leonardus: actually, you don't. No blocks found when mining solo == as if you never mined at all

The network difficulty is based on the actual blocks found, not the "real" hashrate of the miners working

A couple of pow-priority questions if/when anyone has time:

- (1) Where can I learn best practices to understand and defend against various attacks, and specifically avoid any "gotchas" which might compromise privacy for myself or others?

- (2) Where can I learn about integrating payments into an existing real-world business? Is there a de-facto standard payment processor with reasonable integration? The company currently accepts fiat only, via Stripe.

- (2.1) A key factor here is that payments would make their way to the company-registered KYC exchange account to be converted to fiat and tax reported- so the "privacy" from the company's receiving wallet and beyond is noncritical. But we don't want to do anything which would impact privacy for those actually making (typically monthly or annual) payments.

Any guidance would be appreciated, even if the answer is "you shouldn't do it that way". Done.

if I didn't want my ISP to see that I am running a monero node but only that I have copied the blockchain and synced with it can I just sync the blockchain fully with my non-tor connection and then copy the blockchain file over to tails for example and use tor to actually run the node?

Yes, though if your ISP really wants to know, they could analyze the timing and size of your tor packets and see if that correlates with monero blocks being found.

there is no official monero-gui for arm ?

MalMen: I don't think so, could compile it yourself tho

moneromooo: that wouldn't work if I'm using a tor bridge, right?

MalMen: monero-gui runs on ARM but you have to self compile it

no binaries yet

ok

good to know

trying it on ubports :)

I'm getting a lot of blocked hosts on my node: paste.debian.net/hidden/e3bcb5b2

Has anyone else noticed it?

Me too. Everything works fine though

selsta sent me more peers to add to the DNS based bin yesterday. If you use that, it's possibly the reason.

sech1: yes

sech1: it should only print once in the logs

moneromooo: I think the code to only print it once doesn't work with subnets

doesn't work or wasn't added

I made my own node to make the failed transaction disappear from the list

but it's here again

which list?

the list of transactions in monero gui

there was a command to type maybe, flush_txpool or something like that, I'll try it

moneromooo I use DNS blocklist

sech1: it should be fixed in a couple mins

mawk: you can try `flush_txpool txid`, if it doesn't work you have to rescan your wallet / restore from seed

or just ignore it

ah thanks

can I do remote commands on the node

I can stop it and restart it in interactive mode to type commands but that's not practical

mawk: `./monerod command`

monerod is already running

works if they are on tge same machine

the*

ah, so even if its already running?

yes

ah nice

can I get a REPL like this? or just command by command

seems like it's just command by command but still nice

although it says "Error: Unsuccessful-- rpc_request: " but maybe I need to tweak the ports it's connecting to

ah yes it's good now

the ugly tx is still here though, so I suppose I will rescan the wallet

and it didn't change anything either

am I stuck forever with the ugly failed tx

I did "check_blockchain_pruning" to see what it would do and now the daemon is unresponsive

I don't understand why the failed TX is sticking here

I submitted this TX which failed on whatever online node, so why is it appearing on my own node again now

why is it being broadcasted between nodes if it's failed