-
m-relay_<bico653:matrix.org> banmonero.com
-
m-relay_<bico653:matrix.org> stacker.news/items/634963
-
m-relay_<bico653:matrix.org> github.com/supertestnet/examiner
-
aperechnevIf I follow this logic, should I get rid of my kitches knifes to avoid a potential crime? :-D Channel owners, sorry for getting involved into this.
-
flandreis this site a meme?
-
m-relay_<ofrnxmr:monero.social> The message was deleted and conversation moved to community or monero. Thanms
-
vthor_for monero gui in the readme is written Qt 5.9.7, still true, or better take 5.9.9?
-
vthor_sorry, forgot to mention for development, to integrate UR for offline signing
-
vthor_heck, thought I'm in monero-gui, never mind
-
m-relay_<r4v3r23:monero.social> youre adding UR to GUI?!
-
m-relay_<r4v3r23:monero.social> kayabanerve jberman do you have an idea of how the sizes of unsigned/signed tx payloads will change with FCMP++?
-
m-relay_<r4v3r23:monero.social> i know seraphis drops the need to sync outputs & key images for offline txs, are they still needed with FCMPs?
-
m-relay_<kayabanerve:monero.social> Unsigned TXs... should be a bit smaller? I think? The unsigned TX from hot to cold doesn't need the decoy information, and the returned signature should be smaller than a CLSAG.
-
m-relay_<kayabanerve:monero.social> The full TX will be larger, probably by a couple kB.
-
m-relay_<kayabanerve:monero.social> FCMP++ enables view-only wallets to calculate key images for *newly generated addresses*. I don't believe we're doing that degree of wallet code at launch.
-
m-relay_<kayabanerve:monero.social> So theoretically, yet probably not practically.
-
vthorr4v3r23: yes I'm on it
-
m-relay_<r4v3r23:monero.social> im asking in the context of how big the actual payloads will be to pass them by UR. current ones are already relatively big
-
m-relay_<r4v3r23:monero.social> will that involve any UR-related changes to actual monero codebase?