03:54:30 https://x.com/sebp888/status/2101510193091932161 03:55:26 can someone answer this ? 03:55:26 i am sure its been already addressed earlier but i don't recall exactly what was it 04:01:17 anything to do with adaptive block size ? 04:03:04 also to consider is currently bitcoin has lot of transactions with non-finanical data on the chain , often referred as "spam". But monero network doesn't support them op-return or witness data so there is less incentive to create spam transactions. 04:48:38 https://www.reddit.com/r/AIDiscussion/comments/1wl72dn/wormgptlivewormgptcowormgpt4comwormgpt4net_legit/ has anyone use this wormgpt service? 08:52:46 "can someone answer this ?" Why, and answer how? A quick calculation showed me that the growth of 1.7 GB per day is probably in the right ballpark. Such a growth may be ok in a few years, thanks to technological progress, but if the number of transactions exploded to BTC levels overnight, the network would run into serious problems. 08:59:05 1.7gb for full nodes, probably closer to 600-800 mb for pruned 09:00:44 Avg about 700 tx per block, and 2 mb blocks 09:54:42 @ofrnxmr: with fcpm++ ? 09:58:07 multiply by 3 10:49:34 @ofrnxmr:xmr.mx: Will be fun to sync wallets/nodes 10:57:00 syncing wallets isnt that bad 11:00:36 @ofrnxmr:xmr.mx: pov you live in a first world country 11:02:51 @ofrnxmr:xmr.mx: How much data would be consumed to sync one month of blockchain ? Post fcmp++ if we have 600/700 txs per block 11:09:32 i have some... trusted sync mode that reduces data do a few bytes for blocks where you dont own anything 11:10:00 so about 6gb for the full chain today, about 1/10th of the data and sync time 11:38:38 @ofrnxmr:xmr.mx: few bytes per block ? 11:38:47 yea 11:42:25 @ofrnxmr:xmr.mx: So you need to run your own node, or can use any trusted* node like cake ? 11:43:16 no privacy issue ? or is it like lws 11:43:38 @yokoama:matrix.org: i think the how the communicates with each other doesn't change after fcmp++ 11:44:07 @yokoama:matrix.org: one you trust with some info about your txs 11:44:16 node* 11:44:46 its not as bad as lws, but it requests data from node about specific transactions that match your view keys 11:45:13 there is another alternative, which is about 13gb of local storage, and drops the resolve part 11:45:22 @ofrnxmr:xmr.mx: doesnt lws do the same ? 11:45:25 but the biggest saving resolves matchess 11:45:30 so if you were trusting a remote node before this upgrade then probably you can still trust them 11:45:45 no, lws scans the whole chain and knows definitively what txs are your, and their amounts 11:46:13 @ofrnxmr:xmr.mx: yah the so called trusted node can save your view key and scan the entire chain 11:46:26 my scandata thing resolves all txs that match your view tags, with have a false positive in 1/256 txs 11:46:41 scandata doesnt share view keys 11:47:02 it uses view tags 11:47:50 @ofrnxmr:xmr.mx: so you send view tags & get related txs from node per block and only check them 11:47:56 currently we downlaod all data, and only scan the data that matches out view tags. scandata only downloads view tags, and resolves the txs that match the tag 11:49:22 of which only real matches and 1/256 false positives are scanned. so even during a period with no activity, you will resolve 1/256 txs that dont match and are discarded locally. the node doesnt know which txs that you scan are yours, but it can learn which view tag groups you are resolving 11:49:27 is this being implemented ? or just your idea 11:49:50 its implemented locally, and if it does go upstream it wont happen til fcmp 11:50:23 @yokoama:matrix.org: i think this will be part of the light wallet . But regular wallets would still have your view keys locally 11:50:25 there are numerous ways to tackle the issue, such as using a shared local cache 11:50:37 reduces sync to about a minute 11:50:46 @yokoama:matrix.org: its part of carrot i think 11:50:50 for the full scan of general fund, or for my spam wallet on fcmp 11:51:34 the resolve method is better for people using tor, or mobile, since storing 15gb is a big ask 11:51:54 but for desktop users, the stored cache is better, since wallets can reuse it 11:53:12 and this is even better for lws, which current has to sync a ton of data from a local node. can be reduces to 15gb and a few mins for a full sync, instead of upwards of an hour for each new wallet connected 11:53:56 using gpus to run off the same cache does a sync in about 10 seconds 11:54:26 so the tldr is that, wallet sync time is current ineffient due to old designs, not due to limitations 11:54:41 bandwidth is likewise much higher than necessary 11:55:15 node sync is another story. there are plenty of places it can be sped up, but its not so easy 12:00:00 wallet sync is a relatively simple matter, if you dont mind changing the design 12:01:06 like, syncing over tor is slow ah because you have to download a LOT of data, and it all uses a single circuit, sqeuential downloads. parallelize downloads, use separate circuits, and you 2+x the speed 12:01:22 reduce the bandwidth 9x and you effectively reduce the sync time on tor by the same 12:01:39 When ccs to research on wallet usability 12:01:56 ask why is so slow to sync wallets on for 12:04:23 @elongated:matrix.org: wwwwhat for, its being done for "free" by numerous people 12:04:38 @wolixoriginal23:matrix.org: i just answered this. bandwidth 12:04:48 wallet download a ton of data that it doesnt need 12:05:12 dont download the data = turn an 8 hour sync into 56mins 12:05:19 45* 12:05:40 download the data using multiple circuits and turn a 45min sync into 30 12:06:46 why no pr? because there are 500 different ways to attack the problem. dont need to change the design 10x, just need PoC for each of them, so they can be evaluated and compared 12:07:51 example, the downloading of cache and a flag to tell the wallet to check the local cache before syncing from the node is relatively simple and could probably land without much opposition 12:08:07 but adding a change that needs to stitch together connections due ti multiple circuits / parallel downloads, needs more scrutiny so that its not silently building corrupt wallets 12:10:31 multi-node sync likewise. if you are connected to a swarm of nodes and one of them is sending bad data, that can cause issues. scandata being someone of a privacy reduction in exchange for a 5-10x increase in sync speeds when using a trusted node, also requires the node that you are connected to supporting the new rpc endpoint [... too long, see https://mrelay.p2pool.observer/e/39rjwawLVGREQmRt ] 12:10:40 on fcmp alone, i think i got something like a 30x speedup with a couple bug fixes + scandata 12:11:24 bug fixes were 6x alone, and scandata another 5x on top of that 12:11:38 bug fixes like 50 loc altogether, possibly land with the next stressnet 12:23:30 @ofrnxmr:xmr.mx: because I using cake wallet means once be downloaded automatically sync to node 12:24:29 if/when any of these changes are formally proposed, cake will inherit them 12:25:32 because cake wallet is partnered with monero to make monero wallet on android 12:51:05 i dont see any improvements on wallet sync, last one was view tags > <@ofrnxmr:xmr.mx> wwwwhat for, its being done for "free" by numerous people 12:51:24 didnt you read the last 50 messages i sent 12:52:21 ai can code poc, dont need real dev time > <@ofrnxmr:xmr.mx> why no pr? because there are 500 different ways to attack the problem. dont need to change the design 10x, just need PoC for each of them, so they can be evaluated and compared 12:52:21 if poc looks good then devs can code it properly 12:52:41 sech1 has a gpu scanner that does it in 8 seconds, plowsof has cache and multinode that cuts time to ~1min (cache) and cuts download in half, and i have scandata + cache that also hits the 1min mark and reduces bandwidth by 90% 12:52:44 @ofrnxmr:xmr.mx: going through it 12:53:09 all of us have PoCs tested and in use locally 12:55:20 but none are production ready, and all have drawbacks or design choices that need addressing. such as gpu times are only on a modern gpu with preprocessed data, scandata requires new rpc endpoints and is built against fcmp repos, and multinode sync exposes you to more potentially malicious nodes 12:55:37 the common denominator for remote note enhancements currently seems to be a 15gb local cache that can be reused across wallets 12:56:34 whether that is feasible is not yet known. as in, is this something people would use for a wallet? 15 gb is a lot of data for an android app if you arent using multiple wallets, and it only helps when syncing an old/restored wallet or catchup sync on a 2nds+ wallet. the first wallet still needs to download a lot of data 12:56:56 modifying the download is a major change that isnt likely to get consensus quickly. 12:57:05 I know a skitzo rant when I see one 12:57:19 shut up setvin 12:57:34 cant even spell the word 13:28:37 less than 8 seconds actually: https://p2pool.io/u/4e4c135dd01424b7/image.png 13:31:07 guys iam have question what wallet is best for monero 13:36:44 @wolixoriginal23:matrix.org: I like feather or just the main GUI wallet built from source 13:37:15 @isaac_newton:matrix.org: for android 13:37:28 Cake is popular for Android but I never use mobile wallets 13:37:45 @wolixoriginal23:matrix.org: You can get termux and build the cli from source 13:43:23 What happened to all the "early adopters?" 😇 13:48:38 @wolixoriginal23:matrix.org: you just mentioned one in a previous coment. 13:48:38 take it to #monero-offtopic:monero.social too 13:49:07 Monero wallets are off topic? 13:49:35 https://x.com/umbraXMR 13:49:47 50/50 :D 14:23:26 I'm looking for some good written resources on poisoned output/EAE attacks, I wasn't really able to understand the Breaking Monero video on it. Does anyone have any that explain using an actual blockchain explorer? 14:24:45 https://moonstoneresearch.com/2023/11/03/Postmortem-of-Monero-CCS-Hack.html 14:26:07 plowsof: Thank you. 21:59:20 🙄 23:03:37 how good is monero 23:04:03 It's the greatest thing ever 23:04:15 it's life itself 23:15:15 🚪 23:15:24 СВИНЬИ 23:18:13 narf: It's the only one 23:18:13 There is no second best 23:25:14 @ravfx:xmr.mx: There was a first best 23:25:28 @isaac_newton:matrix.org: That would be Monero 23:25:52 Two knocks and a handshake at the barber shop 23:40:28 iced version is comming soon™ 23:40:28 72M hamsters burned so far 23:41:06 s/hamsters/tokens/g 23:42:22 What made you choose Iced over egui? Just curious :) 23:44:52 @jpk68:matrix.org: Iced leverage opengl/VK better afaik. I did not do very very very deep research but basic search told me to use that one. Plus you seam to know your rust options very good and it's the first one you mentionned 23:45:22 I wouldn't take my word for it, but sounds good :D 23:45:44 Well, so far your recommendation has been very good 23:45:46 Though egui is more minimal, if that's what you're going for 23:48:45 @jpk68:matrix.org: I want something that work good and is small. It's why I initially tought about x11rb. But Iced and egui seam to both be very small. And I am fine with iced, it does use video accel on all platform and won't require any extra shit. 23:48:45 The goal is to make it small yes and also I don't want to be bothered with the distribution (I just want the binary to just work on everything I try it to) so both option are good but I have the feeling Iced might be faster 23:49:56 So I assume that if it work fine with Iced, I will just have to install a 10 years old Debian and build it on that (for the Linux release)