12:44:01 geonic maybe I'll just block you. say hi to your lookalike ofrn on the other side, garden gnome. bye-bye. 12:44:28 thanks to the new bridge you can block individual irc accounts on matrix. love you DataHoarder[m] tks. 12:45:04 :) 12:45:17 @jbabb:cypherstack.com: where does that post-quantum turnstile thing from @jeffro256:monero.social fall into regular polyseed vs. polyseed++? have you seen? 12:45:21 it was shared in latest revuo. one sec. 12:45:36 this: https://gist.github.com/jeffro256/146bfd5306ea3a8a2a0ea4d660cd2243 12:45:50 also, this: https://stacker.news/items/1356557 12:46:11 ah... lol > <@jbabb:cypherstack.com> sorry, it should be "classic++ seeds", not polyseed++ 13:49:32 @rottenwheel:unredacted.org: As far as I know the seed should not matter. That turnstile does not care about the way you used to build your private spend key bits. 15:04:50 Sorry for mixing my terminologies: “polyseed++” is my made up term for polyseed+carrot, which as I understand it will incorporate the pq turnstile > <@rottenwheel:unredacted.org> @jbabb:cypherstack.com: where does that post-quantum turnstile thing from @jeffro256:monero.social fall into regular polyseed vs. polyseed++? have you seen? 15:05:34 The classic seeds should also 15:06:17 “Classic++” is another made up term for a hypothetical seed extension to embed restore height and some additional to-be-presently-unused feature/upgrade bits 15:12:51 Why wpuld u need classic++? 15:13:00 Polyseeed exists 15:13:44 Classic++ sounda like "polyseed with 10+ more words" 15:14:52 imma gunna see how many 25 word seeds I can memorize 15:15:47 @ofrnxmr:xmr.mx: what, do you hate security?? 15:16:09 ? 15:16:16 polyseed is 128 bits. I bought my bits, I want my bits 15:16:20 25 isnt more secure than 16 15:16:38 quantum computers might make the difference negligible in the future 15:16:44 Isnt the private key 128bits 15:16:45 more bits but still polyseed is secure 15:16:50 practically, 128 bits is fine 15:16:55 no, it's below 128 bits. yes polyseed IS secure 15:17:17 compatibility is key 15:17:21 I prefer it for usability but would prefer 26-28 word classic seeds with an extension for blockheight so it's all contained 15:17:35 Roght/ so how os a 4664567 bit seed more secure than the private key? 15:18:06 another issue is that I can't convert all my old 25-word seeds to 16-word polyseeds 15:18:30 not all classic keys can be represented in the new scheme. that's a major usability gap for me: i want to be able to "upgrade" any classic seeds by embedding a restore height 15:18:42 polyseed doesn't achieve this (personal) requirement 15:26:31 Your okd seeds wont have pfs etc 15:26:32 U cant upgrade your seeds to carrot keys w/o generating new wallets 15:37:09 so? 15:38:01 old seeds can be upgraded with the simple addition of an embedded restore blockheight 15:38:01 that doesn't regen the new carrot keys, no 15:38:01 it doesn't have to 15:40:59 Sounds like a waste of time 15:41:30 it's a waste of time to gen the carrot keys for restore purposes before its activation height anyways 15:42:06 sounds like you hate the users 15:42:13 If youre storing an extra 3 words, why not store the height (1 word) 15:42:25 ofrnxmr: Enemy of the User 15:42:51 Joshbadd inventing problems 15:43:07 i will consider your opinions valid if you can get rotten and geonic to agree 15:43:37 f you make the seed even 1 word longer, its no different than wroting dowm the restore height 15:43:56 @jbabb:cypherstack.com: i lol'd 15:44:01 saving abandon...abandon1234567 is the current "solution" 15:44:34 how much time and energy is wasted by syncing from 0 for so many classic seeds? 15:44:53 @jbabb:cypherstack.com: Abandon...abandon is the proposed 15:45:15 with some extra words for extra bits which will initially be unused, yes 15:46:33 why do we even have a mnemonic phrase? why not just save the keys? 15:47:08 Cuz u need multiple keys + address to restore 15:47:30 depending on the key... 15:48:05 monero uri supports a list of txids for wallet restoration and "almost instant" syncing , which is more convenient for the user. if they want to do arts and crafts they can hand scribble a QR code 15:48:41 after fcmp you csnt "skip sync" anymore 15:48:56 So it would do full sync from the earliest txid 15:49:17 no rct sync 15:51:25 the monero gui has a pdf for people to put their restore height on :( 15:51:30 I do like monero uris, plowsof, and that does include everything I need... thanks for the reminder 15:52:05 I just want polyseed functionality with the ability to represent (directly 1-to-1 convert) all my old seeds 15:52:25 the only real issue with monero uris is adoption at this point 15:52:35 ... but polyseed suffers on that point as well. 15:52:41 Dont we have a height param on uris 15:52:43 so txid list will be deprecated in fcmp, no one likes the user. would a uri still be possible to reduce sync times under fcmp++? 15:52:43 @jbabb:cypherstack.com: How? 15:52:47 (tho polyseed > uris in an adoption sense) 15:52:52 @ofrnxmr:xmr.mx: yes 15:53:22 monero uri wallet restores just aren't very widely supported afaik 15:55:06 plowsof: checking 15:56:10 Only by modifying the restore height 15:56:29 Thentree building has to be sequential, so u cant just scan in txs 15:57:07 So the earliest txid would set the restore height and it woukd sync normalltly from that point 16:06:04 tree building needs to be sequential from the restore point but can be jumpstarted w init_tree_sync_data 16:06:54 plowsof: no, txid lists via uri will not help speed up syncs post-fcmp++, at least not with the current code and i'm not sure that it's feasible anyhow 16:07:12 there is a manual scan_tx path but it's not for future txs, just for rescanning txs at or below the current sync height 16:08:29 key image exports still exist in fcmpland... 16:13:34 it does 16:13:34 key image export/import can help speed wallet sync. looks like key images could feasibly speed restores unless i'm mistaken. haven't had coffee yet so it's all a bit of a blur 17:13:49 You definitely can theoretically "skip sync", its just not supported by the wallet at the moment since its kinda complex > <@ofrnxmr:xmr.mx> after fcmp you csnt "skip sync" anymore 17:14:58 I was told (maybe i misunderstood) that you can't because of tree building 17:16:39 Yeah the tree building makes that code a lot more complicated , but it should still be possible with more or less the same trust assumptions 17:19:37 For scan_tx specifically, which I think is what youre talking about, we made the choice to not support "future scans" since they would encounter that enote anyways upon a normal refresh , so the complexity wasn't worth it 17:40:57 @loop.ster:matrix.org: hello, under what account name? manual approval is needed for accounts who login via a 3rd party or emails fail to get through 19:08:09 selsta https://xcancel.com/MoneroSpace/status/2029272604675018996 19:08:52 ty for sharing 20:30:29 👋 20:34:17 anyone have any luck with monero android POS apps on those special android terminals with a printer and such? 20:34:50 I wonder which device to go with, as the Alacrity isn't very easy to get in EU 20:35:08 and when I looked deeper there's all sorts of brands with dodgy listings and names 20:46:04 @intr:unredacted.org: why buy a specialized device? just use a tablet with cake wallet on it or something 20:46:38 cake wallet let's you request specific amounts in your local currency from the customers too 20:48:52 yeah I know about wallet apps, I'm asking about point of sale apps like Kasisto, XMRpos, etc. on point of sale terminals 20:49:22 I think they're cool and I think presentation matters 20:49:44 I feel like in-person payment flow is a little too overlooked and could use more attention 20:49:57 cool cool 👍️ 22:18:51 Has anybody used Gummo's https://nevercast.app/ service? 23:17:40 <321bob321> @intr:unredacted.org: Ajs question