<kiersten5821:matrix.org> geonic: really?

yep

sech1: monero_wallet: uri is not for making txs, but restoration

that scheme probably needs a revamp for new carrot as well

<kiersten5821:matrix.org> geonic: do you have a source

kiersten5821: archive.ph/20260213070848/https://w…o-xmr-rises-stumping-crime-fighters

"[...] said Justin Ehrenhofer, who in 2023 set up a firm to investigate Monero transactions that was subsequently bought by his current employer, NAXO."

funnily, monero: url scheme works in href links

but not monero_wallet

monero-wallet would

I added `monero_wallet:` to entries under blocks.p2pool.observer/proofs

making them monero-wallet works, otherwise it assumes it's a relative link!

`scheme = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." )`

*scheme = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." )

basically according to RFC 3986 monero_wallet is not a valid scheme. _ is not in the allowed list (it can be included after)

see rfc-editor.org/rfc/rfc3986#section-3.1

as it is is unusable in applications (like browsers) that follow RFC 3986

thanks DataHoarder this is the exact esoteric uri knowledge i've been waiting for

<kiersten5821:matrix.org> geonic: thanks, that's really important to know idk why anyone would use a wallet from a surveillance firm

you're welcome. no one would, if they knew who the guy behind it is. hopefully sgp discloses this information in future marketing messages

I mean, to be fair, the software is open source and forces you to run your own backend

would be pretty obvious if it was phoning home also I guess

it'd maybe work on QR codes, but it should use RFC 3986 there too (os might not allow to register handlers for not valid schemes)

I can't even find where monero_wallet url scheme would get defined to get handled by OS

sure, but it would be less obvious if it was harming network anonymity in other ways. would you use an open-source monero wallet made by chainalysis?

the monero-gui has not implemented importing via monero_wallet links yet so this is uncharted territory?

if it sucked less mebbe :P

but it would still be useful to know it's by chainalysis right :)

cake wallet could be funded by CIA

why would you expect to know?

tbh maybe it's better if it's known at all right?

wait are you justifying a confirmed fact with a hypothetical

monero itself could be a NSA honeypot

<ufo808:matrix.org> chances are low, but never zero

right. so let's ignore facts because life is fleeting and at the end of the day nothing matters ...

<ufo808:matrix.org> Linkin Park - In The End 🎵

Cat brings meaning to life, the tao of Cat

btw Cat's wallet of choice is the CLI

mnemonic can be encoded as raw bytes yes

and that is vastly smaller

even after doing base64 on it

hex is bigger than base64, yet still smaller than the mnemonic string

plowsof: mnemonic AS hex

the mnemonic denotes a byte string value

with a checksum as well

I just don't really get what you're complaining about, it's not like he hides his identity or where he has worked, and if there was something nefarious about then...wouldn't he just publish under a nym?

also am a cli wallet enjoyoor

but I did test skylight beta

not always Cindy_

there is "secret key" too :P

sometimes there's a step from mnemonic raw bytes -> seed key

then another step from seed to spend

Cindy_: seed is not spend key always

if you look at base mnemonic yes Cindy_, but other stuff like polyseed or whatnot is different

also carrot :P

example -> border gutter unlikely coexist tsunami muddy portents pioneer arrow inflamed upper altitude loudly afraid luggage ounce against mowing spout egotistic trolling aggravate pivot pumpkins altitude encodes to fedd3d8a5918d4ac0307d9679fae0321209a347d2055a486d3c239a21f72ee05 under cryptonote

fedd3d8a5918d4ac0307d9679fae0321209a347d2055a486d3c239a21f72ee05 is also the spend key

so Cindy_ is asking that instead of passing border gutter unlikely coexist tsunami muddy portents pioneer arrow inflamed upper altitude loudly afraid luggage ounce against mowing spout egotistic trolling aggravate pivot pumpkins altitude on URL you pass fedd3d8a5918d4ac0307d9679fae0321209a347d2055a486d3c239a21f72ee05

you can go backwards in that step

(it's 1:1 encoding)

in case of mnemonic

polyseed differs a bit, but you could also just encode raw bytes

in total it's 150 bits for secret + 15 bits of feature/birthday

the 11 bits of checksum are not needed in hex encoding

from this the secret seed is derived, which is what starts the wallet construction process Cindy_

see github.com/tevador/polyseed

in case there's just mnemonic and standard legacy wallet, you could just send spend key

in some original wallets spend/view key were determined at random separately Cindy_. so you need to send both

then the derivation of the mnemonic/secret is different depending on wallet implementation ( 👀 MyMonero)