that's been my experience with iGPUs in general. the fact that they're on the same main memory bus as the CPU certainly puts an upper bound on their perf, anyway

I don't understand why jamtis will introduce a 16 words mnemonic? Since the current xmr private key will remain valid then I suppose polyseed (jamtis 's 16 words mnemonic) don't intend to replace monero current 25 words mnemonics but just provid another alternative. Or is the goal to create a new standard of 16 words mnemonic for monero? And what is the benefit of these new 16 words mnemonics? Also I read about the impossibility to use

these keys for other blockchains is it the reason? Thanks for help

kwxmr[m]: did you read up on the proposal for the 16 word seed?

Thanks I already read that but I don't think it answers my questions

There was a plan to adopt the 16 word seed even before JAMTIS.

Yes, the old 25 seed would stay valid but new wallets would use the 16 word seed. The integrated restore height is important for user experience.

The benefits are explained on Github. Shorter, integrated restore height, etc.

I don't know regarding other blockchains but the current seed already is incompatible.

Shorter's not really a plus unless it's short enough to be memorized by most users.

selsta: Ok thanks for info. So it's just for integrated restore height, it was not possible to have those features (except shorter) with 25 words?

moneromooo: I'm not at your expertise level but as far as I'm concerned I commplagree

s/commplagree/completely agree, especially for private keys!/

> Polyseed was designed for the 128-bit security level. This corresponds to the security of the ed25519 elliptic curve, which requires about 2126 operations to break a key.

I assumed the 24 length for btc and 25 for xmr was chosen because it is the perfect balance between security and usability

It does talk about it, but I'm not the person to judge if it's correct or not.

Most Bitcoin wallets have a 12 word seed as far as I know.

it should be 2^126 in my previous quote

selsta: Yes but for hotwallets, most hardware wallets use 24

my Trezor came with a 12 word seed

with the rise of quantum those seeds could become obsolete sooner than expected! I don't know I'm not an expert but if it was for me to chose I would have increased the length not decrease it

it's not about the security, it's that the UX between 16 and 25 words is kind of the same. A length difference of this magnitude does not really make a difference.

I've had to deal with other cryptocurrencies with weird seeds when working on multi-coin wallets. It's annoying, especially if there is no tangible reason why they changed the algorihm.

That's not the case here though, there's a clear UX benefit with Jamtis, which is why I support it.

this bot didn't have notifications for months and now they show up again lol

Hello all. First time in public IRC. Just wanted to throw out an idea to gauge feasibility/usability. An plug-n-play RPi image that setups a monero wallet and begins mining to a pool. Configurable to what pool or even solo mining. Bonus points for a small touch screen attachment that can display wallet address/has buttons for common uses.

Thoughts?

moneromooo could you unlock the user 'haveno' on gitlab?

Doesn't seem locked. Did you mean allow projects ? If so, doing it now.

yep, i meant that

thanks

mirkoRainer: check out PiNodeXMR

Oh, he left :/

also mining on a Pi doesn't make sense

is there a way to pause monerod via rpc?

You can set in/out peers to 0.

Depending on your definition of pause.

that's a good thought. my definition of pause would be shut off everything outside of the ability to start it back up again :)

Has anyone created a setup for P2pool on Stagenet?

Getting RPC failures if I just point P2pool to monero-stagenet.exan.tech

guessing there is no stagenet sidechain

I thnk that one died long ago. IIRC xmr.to has a stagenet node somewhere. Search for those terms.

melo.tools has stagenet / testnet nodes

also here: monero.fail/?nettype=stagenet

great thanks folks! Seems like it also requires a change to the p2pool config

I think i'm just missing the name of the staging p2pool sidechain pool name

anyone know where to find that?

Does anyone have a general sense how difficult/expensive it would be to add a consensus rule that a tx output may not have a duplicate onetime address (similar to a key image check)?

Very easy.

vitruvius[m]: i.imgur.com/GHuJH0x.png

Well, fairly easy, since you have to add a db conversion function to add a table with all keys so far (and dupes do exist atm).

ah, _your_ staging p2pool sidechain pool name. Misread.

Requires some time/work, but nothing hard. It was deemed not worth the extra db space.

Scalability: Yeah I can't find any info anywhere on existing sidchain pool names

Try asking in #monero-pow.

I want to add that check to seraphis, to prevent weird edge cases around the more ‘loose’ tx construction rules (ie you can make an isolated output not tied to any other output or input, which can be funded in an arbitrary tx).

Then if you only need to avoid dupes among seraphis outs, and not among all (seraphis and pre-seraphis) outs, then it's very easy.

Yeah