twitter.com/hyc_symas/status/1203709575226183683

Last time I got an award like that was in a primary school football team. It had three stars too and said that I'm special :')

I just binned it though instead of showing it off to naive groupies. What kind of preson takes a group achievement award and presents it as a proof of their individual prowess anyway?

crst, My personal experience is, that mining only makes sense on a passively cooled CPU. Otherwise the maintenance costs overwhelm the profits.

mj-xmr: Thanks so much for that info! The servers are running for a fixed price in a DA anyway. I'm looking for a solution to gently use free CPU and not interfere with the running services.

Aha, if you're not responsible for the maintenance, then go for it! I do the same on my server in a data center.

Just one tip: run the process with a "nice" prefix, so that if you want to do something serious on the server, the mining software yields.

nice -n 15 ./xmr-stak-rx --noTest

Don't kill me for the choice of mining software, hahahaha

Awesome! Was just gonna ask if it's better than the normal xmrig :D

it's slower (= not better)

I can't say objectively, but xmrig can be used under Rpi4, stak not. OK. -dev. Let's chat somewhere else.

-community?

There's -pools and -otc

OK. I joined both.

Today I reported so much spam, that GitHub itself considered me a spammer for a while.

On my dev branches.

lol

merge list: 6810 7005 7274 7332 7349 7366 7368 7373 7394 7398 7400 7401 7402

(I'm a bot now)

lol

Keep getting `E couldn't query power status from /sys/class/power_supply` here on Ubuntu while running monerod.

Might not have the right kernel modules up.

You'll only need this if you want to set up smart mining though.

it appears wallets make 5 calls to the daemon when syncing starts and before the first call to get_blocks.bin: get_info, get_version, get_info, get_transaction_pool_hashes.bin, and get_transactions

thoughts on reducing this to one call before downloading blocks for performance?

What's slow ?

yeah with a remote node, those 5x calls can go slow before the user sees blocks downloading

Remote as in not yours ?

yes. and for a daemon, that's 5 requests to serve each time a client wallet polls

I guess you could add a "don't look at txpool" wallet setting...

get_info is now blocking on a mutex, since fairly recently. This needs fixing.

the wallet needs to look at the pool to get quick notification of txs though

Ah, so you want to have a "GIMME ALL" call ?

If that's a problem, maybe 0mq would be faster ?

yes, I was thinking something like a combined `get_tx_pool` which returns all info from get_info, get_version, get_transaction_pool_hashes.bin, and get_transactions necessary to start syncing

But if it only annoys those who don't run their own node, I'm not too bothered :)

There's already a get_txpool. It was replaced by get_transaction_pool_hashes.bin, because slow.

You don't want to get the whole txpool if you already have most txes.

i think it would be for any remote node, whether you control or not?

yeah I'm thinking of users of full wallet apps like cake wallet or monerujo who experience a noticeable delay before the wallet even starts syncing which is problematic for in-person payments

How much time does it take to get txpool contents then ?

the client wallet communicates a client_id to the daemon. perhaps the daemon call can exclude pool transactions already served to the client?

Define client_id ?

I don't remember that being a thing.

Unless you mean for RPC payment ?

it depends on the speed of connection, but there can easily be a 20 second startup time if it's slow, I suspect much of which is overhead in just making the hops

Wow. That's slow. Then use your own node.

Or speed up whatever is low if you want. Or delay txpool stuff.

The idea of a "do these unrelated things" RPC is vaguely unpalatable to me, but only vaguely I guess.

again the intended use case is for in-person payments for users of full wallet apps, e.g. cake

so this call would serve to improve performance in that case

I see wallet2 send a "client" field with the call to get_info

or perhaps such a field can be used in this call even if not there now

That's for RPC payment. Most clients won't do that.

After thinking some more, a RPC for that could be ok. You could probably piggy back on getblocks.bin in fact.

<moneromooo> Wow. That's slow. Then use your own node. >>> this is true if its a remote node you own or a public one....

the whole slow responsiveness thing. cakewallet and monerujo can both connect to a self-controlled node

I connect to my own .onion node, latency is an even bigger issue over Tor

Now that's a really good argument :)

"The node 839283 other people use is slow" isn't.

Did you know one of the developers is working on integrating Triptych?!

Triptych is a zero-knowledge proving system for confidential transactions created by the Monero Research Lab!

When Tari finally comes out, will you dump your Monero to buy it? Will others?

need to unsub from the repo if the spam continues like this :(

TheCharlatan, The spam has clearly identifiable patterns. I keep reporting this to GitHub. They could apply some automated filters, but you know how it is in large corporations. They need their meetings first...