<yokoama:matrix.org> If fcmp++ makes reorgs more impactful, what is the status of non-pos finality research to mitigate this? Is there active work on consensus hardening (like "Publish or Perish" or something else) to protect the FCMP tree?

There is Share or Perish, which can be deployed as a soft fork with reasonably low costs (but only works against minority hashrate attacks): monero-project/research-lab #146

<yokoama:matrix.org> tevador: Would this have avoided qubic type 18 block reorg ?

Yes. AFAIK they never actually had the majority of the hashrate. The 18 block reorg was just luck.

<jpk68:matrix.org> As koe mentioned at the last meeting, it is possible to encode (Jamtis) addresses as binary for use in QR codes. For example, Base32/62 could be used for its text representation; for QR codes, the ASCII characters monero: could be appended to the front of the raw address in bytes, and then that is encoded by the QR.

<jpk68:matrix.org> If my calculations are correct, this would result in smaller QR code sizes AND encoded address lengths, compared to just using Base32 for everything

<jpk68:matrix.org> It may be better to use monero: instead of xmr: as the 'identifier' at the start of it, since that would ostensibly be more distinct from random ASCII when the code is scanned by a device

<ofrnxmr:xmr.mx> monero: is what we use for URIs

<jpk68:matrix.org> The downside, of course, is implementation complexity

<jpk68:matrix.org> To make up for the more complicated QR code thing, we could always use the existing Base58 instead of Base62, as there are already so many code libraries that have implemented it. Three different encodings used is probably better than four

<jpk68:matrix.org> Plus the ASCII length reduction for Base58 versus Base62 is like something to the effect of 95% as good

I don't think binary QR codes are workable in practice. It needs to be a string to be a valid URI.

<jpk68:matrix.org> I could be wrong, but I think it can still be a string since binary QRs are seemingly interpreted as ASCII. It's just that the string isn't alphanumeric

It needs to pass URI validation rules, so most characters would need to be percent-encoded, which would nullify any space savings.

RFC 3986: unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"

<jpk68:matrix.org> Nuts :((

base62 saves 9 characters compared to base58 (577 -> 568)

Actually, Monero uses a slightly less efficient variant of base58, so it's 12 characters (580 -> 568)

Ideally, addresses would fit in one IRC message, but I don't think it's possible without cutting features or security :(

<jpk68:matrix.org> The fact that Base58 doesn't include similar characters wouldn't be good enough to replace the remaining Base32 part though, right?

not without UX reduction (comparing case insensitive characters is easier)

<silicon.dystopia:matrix.org> where do u folks conduct meetings? :3

<silicon.dystopia:matrix.org> is it something open to the public?

<silicon.dystopia:matrix.org> im not familiar closely enough with the project to meaningfully contribute, but would be exciting to listen to it

<redsh4de:matrix.org> that'd be here: #monero-research-lab:monero.social

<redsh4de:matrix.org> meetings are on wednesdays at 17:00 UTC

<jpk68:matrix.org> Also, the meta repo for all dates and times :)

<silicon.dystopia:matrix.org> @redsh4de:matrix.org: what platform do u use for communication then? just text based meetups?

<redsh4de:matrix.org> yeah, its all IRC/Matrix based

<jpk68:matrix.org> news.ycombinator.com/item?id=47897647

How bad is the fact that Jamtis addresses become linkable (e.g. 2 addresses that belong to the same wallet) if ECDLP is broken?

<jpk68:matrix.org> If you're talking about that article I sent, it's unrelated to Jamtis, I just thought it was interesting

<jpk68:matrix.org> Apologies if otherwise

This is largely unavoidable because the primary view tag still needs to be based on Curve25519 for performance reasons.

My comment was unrelated to the link you posted.

<jpk68:matrix.org> My bad, sorry

<ixr3:matrix.org> @jpk68:matrix.org: Read your private message please