00:00:25 thx binaryfate, nioc 00:06:49 You guys dont know how I am pissed off that you guys released a wallet that can't create wallet.... Will soon open a test labs, I will accept submission for proper QA testing, for a fee 01:11:52 how come creating a wallet wasnt tested in 0.18.5.1? 01:11:58 the most basic functionality is not tested before release? 01:13:19 open source project, everyone can help with testing 01:15:14 in this case it depended on a specific folder existing which already existed for everyone who did test it 01:27:25 Sure, but imo it should be a proper thing to do to test supported feature before cristening a new version for release. 01:27:25 Imajin Microslop selling a new Word version that can't create new documents if there is no files is "my documents" 01:28:59 Basic testing, aka QA, to be sure that the stuff that is officially supported, actually work 01:29:28 there is no one funded to do QA work before a release, and no one volunteered to do its 01:29:43 it* 01:30:20 again, that's why I spent time now to implement this QML test system so at least the wizard part is covered 01:31:14 Even if there was, it's not possible to catch all issues, otherwise there would be no reason for bug fixes 01:34:11 It seems simple enough to say that this should have been tested, but what if this issue was specific to an os that nobody uses? if you didnt create a new build env for every commit that you built and tested, then this issue is hidden by a prior build succeeding 01:37:04 Create a new wallet : all OS 01:37:57 @ravfx:xmr.mx: and if you didn't use a fresh OS install you already wouldn't have caught it 01:37:59 None of which would error if you had tested the previous commit 01:40:06 new os / user 01:40:32 these discussion are a bit pointless, looking back you can always say why did you not test this with these exact preconditions 01:49:27 i think creating a new wallet is the most basic functionality and should have been tested 02:00:32 selsta: I love shit like this 02:01:52 I don't really know why but it's so interesting to me 02:02:27 Like, it's such a logical cause and effect thing? 02:03:51 Of course testers will have wallets from previous tests, of course there is a bug that specifically only appears when you don't have any yet 02:04:02 Fascinating 02:25:32 The bug: flatpak let you manually enter a directory that it did not have permission to write to. When creatinf a wallet, it would work, but the wallet would not persist / would not be written to disk = lost funds 02:25:50 wow, ic 02:26:07 a two for one 😂 02:38:24 lost funds? 02:38:28 @seen seed 02:53:26 who writes those down? I just remember a couple and bypass the check 02:54:03 In cake, you can just close the app on the check / confirmation screen 02:56:43 good luck lol 02:58:12 create wallet and write down seed 02:58:17 close wallet 02:58:36 open wallet and check seed 02:59:15 even for a temporary wallet 02:59:37 monero is life itself 04:05:25 I just make 100 copies of the wallet file 🧠🧠 04:05:57 And then send them to my friends 04:08:20 Im only half joking. I do actually have probably 30 wallets without the seed stored anywhere, but none of these hold any funds. Just used/reused for testing .. or as decoys, so if my drive is ever seized, rheyll have to sync 30 wallets that all have history but none have funds 🧠 04:08:42 "theres 700 transactions across 300 subaddresses, and it says the balance is zero? What am i missing." 04:08:49 @ofrnxmr:xmr.mx: Based 04:29:50 > rheyll have to sync 30 wallets that all have history but none have funds 04:29:51 GPU (private) scanners now exist that can do a full scan in ~5-15s btw :) 04:30:40 wrote something similar for bruteforcing tari pubkey burn bug and got similar speeds 04:31:54 DataHoarder: Why not public 04:32:01 slop 04:32:50 mine is public, anyhow, on the tari repo. I have the CPU scanner/verifier and the GPU one was also sourced from normal C code, then slop'd keccak/derivations 04:32:54 How can it do a full scan in 15sec if you have to read 30gb from the db? 04:33:02 the db is pre-processed :) 04:33:09 and it fits in GPU 04:33:15 Gotcha 04:33:28 you effectively take all the outputs and process them in a standard format to scan quick 04:33:41 is it rust tho 04:33:45 😀 04:33:54 surely not 04:34:07 Finally 07:47:32 Yep, I have the GPU scanner that does a fullchain scan of a wallet in 8 seconds on RTX 5070. AI vibe coded but it works. 07:48:32 The required data fits into ~8.3 GB VRAM, so it needs a GPU with 12 or more GB VRAM 07:48:50 Although, streaming the data is possible, but not implemented 08:21:51 ArticMine ^ 09:32:01 sech1: CUDA ? Vulkan ? 09:32:21 C++/CUDA 09:33:01 alr 09:47:58 Rbrunner^ 09:52:27 * plowsof searches if his old android phone has 12GB of vram 10:12:21 For tari not monero sech1? Need to read the backlog 10:15:03 I was thinking back to artic wanting to utilize the gpu on a pi to help block verification 10:21:07 Not sure where I might be able contribute something to the discussion? 10:25:26 Hello, sorry looks like its not for monero but tari, pinged as i thought the nwlb workgroup would like to see that. Maybe theres still something there to help us sync the "old" chain faster 11:24:28 NVIDIA TM POWERED MONERO SYNCING 11:28:25 One LWS node to control the entire chain 12:06:41 Publix for tari, but iiuc the 8-15s applies to monero 12:07:09 Since that what we were talking abt (monero sync time) 16:48:27 @jeffro256:monero.social: shared https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/688 via @MoneroSpace. =] https://x.com/MoneroSpace/status/2079971347518894509 // nitter: https://xcancel.com/MoneroSpace/status/2079971347518894509 16:58:25 Thank you 17:58:28 plowsof it's for Monero. Yes, it's possible to speedup node syncing using the GPU, but what I have now is only wallet-side scanning with the viewkey