00:49:19 I bought Pizza with monero and gave a goldback as a tip 01:32:47 Where can you buy pizza with Monero? 05:15:44 Dominos giftcard 05:16:11 <3​21bob321:monero.social> Cakepay? 05:18:18 Coinsbee 12:23:28 meeting in 12:24:34 2hr35 mins allegedly https://github.com/monero-project/meta/issues/1065 12:25:53 the "modularize monero" proposal from vthor is going to be drastically refined/edited after receiving feedback from rbrunner / tobtoht / kayabanerve to whom i am deeply thankful for 12:26:59 kewbit has changed his haveno UI from funding required to work in progress. if we agree on this then it will be funded from the now void haveno front end proposal and work would begin immediately upon merge 12:32:03 and 270 xmr was recently donated from the general fund to proposals on the funding required page https://nitter.poast.org/WatchFund/status/1829852188648357909#m 12:33:21 m-relay: does this affect the haveno-web UI bounty? 12:33:28 no 12:33:45 https://x.com/spirobel/status/1829742700876480690 kuno still stuck at 2 percent funding. 12:33:46 might have to go the ccs route after all. 12:33:48 but reading the comments by kaya it seems like he wants to eat that as well 12:34:32 hey so, thinking about this, we (kewbit and I) are interested to work together to create the new haveno ui 12:34:42 awesome woodser 12:34:46 essentially thinking to: 12:34:48 - find designer(s) 12:34:50 - improve the design of the desktop application, incorporating "wizard" elements from bisq2 12:34:52 - design for mobile 12:34:54 - kewbit is the lead dev for delivering the apps 12:35:31 WHAT ABOUT ME lol 12:35:41 spirobel you hate the ccs leave us alone please 12:36:07 maybe there are good ways for you to help too, especially if you are familiar with dart/flutter? 12:36:08 i hate getting fucked over like the last time 12:36:12 i started a ccs 12:36:29 we can talk more about this, there will be a lot to develop 12:42:10 Designers for sure, if you're not already happy with the desktop version in Figma done before by the previous devs, this can still be mimicked in Dart, albeit, with some time. I am working on Wizard elements since this morning actually, I'm making sure the user journey is clear and swift. Just playing around with different ideas but, for the app versions, these journeys will be qu 12:42:10 ite simple, you fill out some info on one page and then on the next. We have a bit more real estate on desktop screens so will likely not ultimately be the same design but the first version will be the same design. I'll bare in mind that there is some favour around the wizards in bisq 2 and use it as some inspiration. 12:42:12 I have been keeping a very very close eye on bisq 2 anyway, they don't have a daemon yet... but it's on my todo list to see if there is any unique problems they're solving with that that we might be able to use, extend functionality on without completely switching to it! 12:43:05 <3​21bob321:monero.social> Holy shit batman 12:43:08 you are getting paid for by the community to be impartial. maybe time to get rid of you if you dont act the part 12:43:33 for sure we want to incorporate designers and their input in the process. they should really lead the design with us 12:43:58 what is the point in using dart and flutter? 12:44:05 thats an outdated dead technology 12:44:15 waste of ressources 12:44:43 waste of resources 12:46:17 I figure it's between dart/flutter or web technologies (react, electron, etc) 12:46:31 If you were not happy with the design from the previous devs? Why did it continue to get developed 12:46:43 apparently dart/flutter is one of the most common choices for creating cross platform apps for mobile and desktop 12:47:13 Is it the best choice 12:47:25 Nothing even comes close 12:47:37 design versus development was ongoing contention between erc and I, and making any design changes was a struggle after basic development began 12:48:04 Maybe React Native comes close but meh 12:48:06 but imo, design should be prioritized first, then implement the design. that's how we'd get a modern beautiful app, versus developers doing what they like 12:48:10 Not even facebook use that anymore and they made it! 12:48:12 flutter is one of these dead google projects that will get killed off at some point 12:48:29 Absolutely nonsense 12:48:49 react is the better choice 12:48:52 The community is what makes flutter powerful at this point 12:48:56 much bigger ecosystem 12:51:57 google just fired the flutter team btw 12:52:02 I have my staff working on React native projects for about a year, thinking it was a good idea, it wasn't a terrible idea. It was just an OK idea, and it was only an OK idea because we chose to do it with Expo :) 12:52:02 It's much quicker to deliver a lot of value in Dart and I strongly suggest learning it, it's awesome. 12:52:10 and canonical is not going to fill the gap 12:52:11 ahhh the community will take over 12:52:25 100% 12:52:44 lol a cto. this thing is dead. wake up 12:52:52 New flutter update was quite recent! 12:52:54 look where the rest of the ecosystem is going 12:53:12 look at the bigger market cap coins 12:53:13 nah not at all you're living in a fantasy land! 12:53:14 ;) 12:53:16 like ethereum or solana 12:53:18 they are 100x our size 12:53:22 most of their stuff is in react 12:53:40 time to wake up and not invest in dying ecosystems 12:54:09 well apparently we dont care what frameworks we use anyway, COUGH COUGH ** 'elm'. 12:54:23 elm smh 12:56:51 What makes and ecosystem grow? 12:57:32 when people work together instead of against each other 12:57:40 Is it the support of a top 500 company? If thats the case, why did React Native not die of when facebook stopped supporting it. 13:01:42 Building native, generally, is a challenge, it's a learning curve people don't want to take when there are easier options like Svelte, Vue, React, Electrum. Dart itself isn't so bad but native platform channels and FFI can deter people, it is slightly more challenging to contribute to community plugins and repos so of course there may be less volume in contribution but the quality 13:01:42 tends to be higher. 13:06:08 woodser: https://github.com/haveno-dex/haveno/issues/1236 13:06:24 oop wrong chat 13:07:13 yeah we can bring that over to #haveno-dev:haveno.network and get more notifications implemented 13:17:19 That link is totally broken btw 13:18:38 this should work https://matrix.to/#/#haveno.exchange:monero.social 13:20:28 if I copy the link from the development room, it's https://matrix.to/#/#haveno-dev:haveno.network 🤔 13:21:10 The `haveno.network` domain is dead 13:21:27 So it wont load unless youre already in the group 13:21:54 The matrix space i created "should" let you join because it has the "real" address 13:25:32 I guess this should be the link that works: #haveno-dev:monero.social 13:26:34 it might, but only for monero.social users, since its a local-only address 13:27:03 The room cant be modified to change the main addresses bcuz the admin accounts are on haveno.network 13:28:18 `https://matrix.to/#/!HeVhOlajgOuVMOKhvS:haveno.network?via=monero.social?via=matrix.org` should work 13:28:31 ``` 13:28:32 https://matrix.to/#/!HeVhOlajgOuVMOKhvS:haveno.network?via=monero.social?via=matrix.org 13:28:34 ``` 13:28:38 Ffs lol 13:29:02 https://matrix dot to/#/!HeVhOlajgOuVMOKhvS:haveno.network?via=monero.social?via=matrix.org 13:34:18 shit does not work 13:34:38 what happend to the domain? 13:34:47 which link? 13:34:54 This one should work 13:35:05 so should this one 13:35:09 we switched the matrix rooms from haveno.network to matrix.social a long time ago 13:35:21 Erciccione killed the homeserver 13:35:37 Haveno-dev was never switched 13:35:57 I can take this as a todo 13:36:22 I switched haveno room, but matrix.org shit the bed and rolled back. Not main haveno room has no address again 13:36:45 Its not possible to change haveno-dev's main address 13:37:07 ah ok. and the only admin is @woodser:haveno.network and so dead account I guess 13:37:13 The only admins are on haveno.network, and that homeserver is dead. 13:37:14 main haveno room has vik as admin, so that one can be fixed again. 13:37:38 The new haveno space i created is on monero.social, so this problem shouldnt happen again 13:38:12 I switched haveno room, but monero.social** shit the bed and rolled back. Not main haveno room has no address again 13:39:14 Spirobel, did the haveno space link work for you? 13:40:04 yes. long time no see lol 13:40:17 remember being in the room in the good old days lol 13:43:23 so if we are to take this direction of designing and implementing for mobile and desktop, it's an evolution of haveno's previous ccs (without fees contributed back, as we do not run a network), or it should be written into any updated ccs request 13:43:47 so the current ccs would need updates before being merged 13:44:16 so the current ccs request would need updates before being merged 13:45:53 I agree we can expand a bit more, perhaps lets do this today, and hopefully we can move it across, like asap? 😆 13:47:59 noted woodser, thank you 14:14:05 reminds me a bit of the "facoring" thing 14:14:10 what happend to this guy btw? 14:14:22 he asked me to work with him in a twitter dm before 14:14:50 saying i asked the right right questions in the dev channel 14:15:05 and then he disappeared 14:15:07 lol 14:23:40 it is okay to have multiple libraries I think. But there needs to be a clear purpose. Not just random changes with unclear goals. 14:25:09 I need to have a library that eventually is robust enough to work in the browser and inside of browser extensions. It needs to be disentangled from the file system and threading. I doubt that any of the other libraries will deliver that. The goals are too different 14:25:57 in my mind it is crucial to have a browser wallet. even mobile wallet apps now embed browsers to interact with decentralized exchanges, do wallet login and other things. Monero seems stale in its current approach 14:29:24 If I look at serai and haveno I see a massive scope that is mostly building out a second decentralized p2p protocol. 14:29:27 Have you seen https://github.com/mainnet-pat/monujo-quasar ? 14:32:32 yes. and I have also seen monero hotshop 14:32:49 and my own work https://www.youtube.com/watch?app=desktop&v=4DLcsQ45zoE 14:32:56 and haveno 14:37:50 any one using crypto grampys hotshop still? 14:40:23 you guys dont need to see my initiative as a replacement for what you are doing. It is just a different thing with a different goal 15:00:21 Meeting time https://github.com/monero-project/meta/issues/1065 15:00:23 Greetings! 15:00:27 hello 15:00:58 hi :) 15:01:11 Morning 15:01:35 Afternoon 15:01:37 I'll be on the road during meeting, apologies if i miss out 15:01:39 Hello. 15:02:24 as i shared earlier, 270 xmr was recently donated from the general fund to proposals on the funding required page https://nitter.poast.org/WatchFund/status/1829852188648357909#m 🚀 15:02:27 hi 15:03:42 Neat! 15:03:51 cypherstack shared a report on effects of reducing moneros 10 block lock in MRL, currently being discussed there https://libera.monerologs.net/monero-research-lab/20240831#c419510 15:04:35 anyone like to share something thats happened over the previous week? 15:04:47 Were some pretty neat findings imo 15:05:35 Weblate is still down, I want to finish the Esperanto translation, but currently there is no way to do it :( 15:05:48 atomic swaps are really bogged down by the 10 block lock, to name an example that would benefit greatly from any decrease there 15:06:31 its not bad 15:06:56 slower than btc<>ltc, but not bad 15:06:58 jorge it seems as though all translations will be thrown into the trash and starting from a-fresh with a new site over the coming month(s) 15:07:13 this is not certain of course 15:08:10 and https://docs.getmonero.org is live . currently a work in progress 15:08:46 it has an A rating for http headers and everything, wow look at that 15:09:34 and an onion too 15:09:38 8) 15:09:55 http://xmrdoc6phnvjbf5hmjbwdfu47zavzfngymlnwhs2gyxxpxmad4c65kyd.onion 15:10:46 and Rucknium has began to tackle migrating moneroresearch.info to a newer back end with better search functionality.. i had failed to put time into it sooner but i should be able to help along the way if needed 15:11:22 Live chat between traders on haveno app now works realtime, and in general works almost flawlessly on android, implemented AES derived PBKDF2 encryption on the app data and files, added a caching layer so failures do not occur on network fluctuations, also implemented a cooldown mechanism to not overload the daemon, currently adding the ability to generate as many stealth address 15:11:22 es as you want with labels and trying to come up with a nice way of recording your history of successful trades to make it easier to trade with trusted parties again. 15:12:12 nice 15:12:55 i think we can jump into the open ccs ideas now? 15:13:30 Skip the website one please. 15:13:44 skippethd 15:13:48 As discussed in previous weeks it's not ready due to no design yet (which I'm working on) 15:13:56 thanks 15:14:09 b. [Haveno Multi-Platform Native App For Every OS](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/489) wishes to be merged into work in progress and be funded entirely by the abandoned / now void haveno front end proposal [gitlab comment for 15:14:09 details](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/489#note_25985) 15:14:19 kewbit 15:14:35 quite a big development on this arrived toda 15:14:38 today* 15:15:12 woodser began sharing his thoughts on the direction of this here https://libera.monerologs.net/monero-community/20240831#c419609 15:16:15 seems like they are going to discuss the plan further and come back with a modified proposal 15:16:36 anyone have opinions? happy? sad? that haveno UI is finally going to get rolling? 15:17:30 it would presumably move into funding required after absorbing the remaining funds from the original haveno front proposal 15:18:23 spirobel was even offered to take part if they have flutter/dart skills 15:18:31 I agree with the prospect of bringing on a designer, that would be really helpful. We have discussedd in private chat further since that brief chat earlier today in here, the design would come into play after this 'v1' lets called it, the app will be available on all platforms however, the designing coming in would really be to focus on the aesthetics of how the desktop design wou 15:18:32 ld look, I'd work closely with whoever that may be when the time comes. 15:19:59 mastodon or lemmy bot is much needed 15:20:34 CS has flutter/dart skills, and...design skills :P 15:20:43 I think a sufficient amount of work has been done on it to justify merging it, should any further UI improvements be requires as discussed earlier, this would be part of a different project, perhaps still under the funding of the original CCS. 15:20:46 sounds good. so we can patiently wait for the conversation to develop, resulting in changes to the proposal 15:21:06 oh look a designer with flutter/dart skills too 15:21:35 can learn it in a weekend. But tbh its the wrong direction 15:22:00 what we need is a real browser wallet. something i have put a lot of time and effort in 15:22:14 that is where the rest of crypto is moving. since ages 15:22:21 seems like we only have biasd opinons 15:22:27 please can we bring in an external consultant 15:22:29 you guys can keep going in this other direction 15:22:32 paid 15:22:38 bring in mckinsey 15:22:39 Hi. 15:22:40 LFG 15:22:46 who does not have any bias 15:22:53 at all 15:22:54 😆 15:23:04 an app on the system vs a web app has advantages in terms of security, so i've been told 15:23:07 because this is getting a bit stupid 15:23:10 :D 15:23:20 is objective. use any chain above 100billion market cap 15:23:24 its all web based 15:23:29 Scams 15:23:58 i mean fine u do yours 15:24:13 i will not interfere or fud 15:24:16 have fun guys 15:24:49 I feel web-based scams are much easier to perform than app-based ones. 15:24:51 so kewbit is saying merge as is, woodser is saying hold off on merging. im leaning towards holding off a bit 15:25:03 DONT FUD MY SHIT OKAY 15:25:07 That's why I personally have shied away from making it. But I may just be a coward there. 15:25:16 Doesnr disq react native 15:25:20 you never used eth or solana? 15:25:22 I agree that adoption would be much higher and faster with web based. 15:25:41 both are supported in Stack Wallet. Got several requests to do web-based wallet for it. Chose not to. 15:25:42 so maybe all the other shit is the real grift 15:25:51 Android app > webapp all day everyday 15:25:56 Ask localmoneri 15:26:15 Couldnt catch me using their website if you paid me to 15:26:18 In other words (and not to be wishy-washy) there are non-trivial pros and cons to both directions. 15:26:22 I pledged my 2 months though, so we can hold off but I dont see the value in it for the community. We can look for a designer in the meantime. 15:26:57 Monero waller, who uses a webwallet 15:27:00 all the successful wallets include browsers now 15:27:12 I try to say nothing, but the browser is the number one vunerability on a system. And this is all I will say. 15:27:15 Anyobe even uss a cex webapp? 15:27:18 on mobile 15:27:23 unpopular opinion: 15:27:24 Tauri > electron 15:27:28 yeah it's why I'm not successful :P 15:27:39 woodsers offer of working together on this came today, so hoding off after he said wait, seems sane .. when you as a team are on the same page, that also feels sane 15:27:59 this would be a matter of day(s) 15:28:47 kewbit your proposal was also made days ago. relax please 15:29:02 I'm sure we can work in days, sure 15:29:22 all evm is evm 15:29:41 plowsof: atomic swaps always have to use the confirmation depth during the swap. The coins you claim from a swap, and fund a new swap with, may be burdened by the 10-block lock yet better wallet software for atomic swaps client would resolve that without modifying the lock. Sorry for being late to chime in on that. 15:29:41 Of course they use browsers, its web3 15:29:48 I am relaxed :D 15:30:05 thanks for clarifying kayabanerve 15:30:13 relax further. Massage-levels 15:30:16 the CCS will pay for one 15:30:19 lol 15:30:35 unfortunately non of the massage parlours around here accept XMR yet 15:30:45 in fact, let's open the CCS for a masseuse for every contributor 15:30:51 can't work if we're burned out ;) 15:31:16 You joke, but it's good. 15:31:33 certainly a gap in the market, now then , waiting some day(s) for woodser and kewbits friendship to flourish? 15:31:34 Diego Salazar: it seems that you got your first payment for your ccs 15:32:05 kayabanerver vthor has closed and opened another proposal btw after your and others feedback 15:32:31 Indeed. 15:32:31 unless we have other things to mention regarding kewbits proposal we can move on 15:32:46 can you mention the works you have done in the past month? aside from bringing back ofrnxmr 15:33:51 Yes, there was a lot of discussion and work with the new website workgroup, a fair amount of discussion and resetting expectations with the current mod team, handling a couple of small odd jobs for luigi, and a lot of testing static site generators to determine a path forward for the new website 15:33:58 followed by a lot of design work for the new website 15:34:28 every CCS proposer posts milestone/payout updates on gitlab, that would be the best place to query details: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/470 15:34:41 It sounds like it will be very good, and using Astro. 15:34:50 the majority of hours were for backend exploration and preliminary design work 15:36:16 so most of them are claims that you worked but nothing notable for now on backend side right? 15:36:37 LOL 15:37:34 kk pls continue 15:37:51 You want me to do a write-up of the explored SSGs as proof? 15:38:16 lets get to vthors proposal, only a few day(s) old but has had a major re-write 15:38:24 you want me to share some of the designed icons here? 15:38:33 no i will wait for another month to see the fruit of those efforts 15:38:42 c. [Offline Signing Library for XmrSigner Production](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/495) 15:39:10 The fruit of the SSG exploration was that the longstanding stand still in the website room about which SSG to go with was resolved and we now have a path forward. 15:39:18 (one second plowsof, sorry for disrupting) 15:39:26 what is supported? send and receive and thats it? 15:39:59 Things were split between Astro and Hugo, with a small pocket of Jekyll people in the mix. 15:40:03 this was just submitted, but on first reading I'm positive towards vthor's updated proposal. I may have some further comments when I get a chance to look at this in more detail. 15:40:11 that's fine, and to confirm the things diego claims to have done i seen enough of them with my own 2 eyes to substantiate the claims 15:40:20 for some reason this didnt appear on CCS ideas section 15:40:30 why not just use wordpress with a cdn? 15:40:43 thank you tobtoht_ :) 15:40:44 I went through a deep dive of those ones (and others) and presented my findings and we decided as a group to move forward with Astro for a variety of reasons 15:41:13 thanks tobtoht, yes it was _just_ submitted. rbrunner, and kayabanerves feedback helped shape the new proposal. again thank you for the quick, direct, pointed feedback 15:41:14 anyways, that's enough tangent from me, please continue as normal plowsof 15:41:21 happy to continue this conversation after the meetinig 15:41:45 which didnt appear on the ccs ideas section real_glitch? 15:41:51 i feel like collaboration would be faster and more convenient if a normal CMS was used 15:41:59 oh i see it now, thanks... 15:42:03 vthor's new proposal 15:42:04 what is supported? send and receive and thats it? In the library? Seed generation output/key images, addresses and signing. 15:42:08 true, will have a look 15:42:46 vthor rename the file to .md (it has no extension currently) 15:43:12 https://moneroresearch.info successfully upgraded to the new 6.10.2 WIKINDX version. Now you can see how it looks by default before plowsof put in effort to make it look better. We'll re-add the custom display templates soon. 15:43:35 good job Rucknium 15:44:02 vthor rename the file to .md (it has no extension currently), oh, heck. Will do. 15:45:46 spirobel was first? one of? to lead the C ABI discussions, nice to have you here 15:46:23 also the pre-proposal-parser will show a red circle and "this is wrong pls fix" soon 15:47:12 spirobel: I'll answer your questions in the website channel so as not to further disrupt the meeting 15:47:26 Does c abi have any crossover with monero_c by mrcyjanek 15:47:40 when rbrunner, tobtoht, kayabanerve have time to read the new proposal it would be great to hear. not expected now as its too soon of course. 15:48:38 https://github.com/MrCyjaneK/monero_c 15:49:17 definitely would be great to have feedback from mrcyjanek too 15:50:04 my comment is: we are moving to rust 15:50:17 base it on the new rust libs instead of the old cpp trash 15:50:46 ofrnxmr: I dunno, not aware of it, but essentialy I will use the monero source create a new folder and build a library specific for this use case which should be as static as possible and provide a C ABI to use the library in other languages. This will be or a small shim, or declaring directly in the the needed files an `external "C"` declaration. 15:50:50 responding to this 15:51:31 we have tons of those all over the monero ecosystem 15:52:18 i just think we should focus resources and eyes on the new rust libraries 15:52:20 would be good if you could take a look at monero_c , its possible that theres alot to take from / use (you mention expertise in C) 15:52:28 that will take over everything sooner or later 15:53:02 vthor, u should look at it ;) 15:53:17 ofrnxmr: not exactly, I will avoid wallet2 completely, but thank you for the link, could be helpful. 15:53:38 Spirobel, we have 2 devs on ccs focused entirely on cuprate 15:55:07 listed on our -site roadmap also ( syntheticbird made cuprate.org using astro - msvb-lab who seems to be a fan of astro) 15:55:29 >Performance: The current implementation using wallet RPC is slow, 15:55:30 especially on resource-constrained devices. 15:55:34 100% agree with this btw 15:55:37 Are we still discussing c? 15:55:49 Topic c, the new signing library 15:55:58 Spirobel, I don't now if you are aware of my previous CCS I closed some hours ago, but that was out of scope, doing it on Rust, would be for sure not less scope. 15:56:01 we re discussing vthors new proposal. the modularizing monero one was closed 15:56:18 vthor: seed signer is a raspi, correct? 15:56:33 new one from vthor https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/495 15:56:48 correct pi zero 15:57:08 Yes, that's what I was referring to. I just wanted to check we hadn't moved on. 15:57:44 tangents 15:58:22 I lean towards NACK due to 15:58:24 > Unsigned transaction handling (description, sanity checks, signing) 15:58:26 But I may be being too harsh. 15:58:33 so you do buildroot arm target to cross compile the cpp ? 15:59:17 inb4 monero-oxide 15:59:20 more details required? or 15:59:23 Verifying an unsigned transaction requires verifying effectively every field inside the TX which isn't a proof. That requires building, and comparing, every part of the transaction. 15:59:30 That's several months of work. 15:59:48 I'm overwhelmed to respond to all at the same time and additional search in the webinterface to rename the file, sorry for delayed answers 15:59:58 This can be done in two months. I don't believe it can be done in two months without several security issues. 16:00:07 a response at this very moment to everything, is not required vthor 16:00:47 wdym i suppose this is to display the infos on the airgapped device to make sure it hasnt been messed with 16:00:56 essentially just displaying the info 16:01:42 The airgapped device has to make the ephemeral keys and do all the derivations itself. 16:02:08 It then has to tell the host computer the ephemeral keys to use for it do the proofs *unless* the airgapped device also does the proofs. 16:02:13 Verifying an unsigned transaction requires verifying effectively every field inside the TX which isn't a proof. That requires building, and comparing, every part of the transaction. Wallet RPC is not doing sanity checks? 16:02:23 I'm unsure a flow for that API even exists in Monero today. 16:02:44 the issue is that monero oxide is not going to solve all the issues for everyone. and you need to give others some room too kaya 16:02:47 vthor: If you build a new library to sign a TX, your library must check the content of the TX. 16:02:54 Wow, I haven't mentioned monero-oxide at all and don't plan to. 16:03:09 no ccs for monero-oxide? 16:03:20 put the cards on the table lol 16:03:22 I'm trying to have a legitimate discussion on what the flow here needs to be for this to be secure so everyone understands the timeline this work needs. 16:03:29 I don't believe 2 months is the answer. 16:03:35 This can be done in two months. I don't believe it can be done in two months without several security issues. <- I can't estimate it not knowing the source well enough at the moment and I nowhere stated that it is done in two months, did I? 16:03:37 kayabanerve: I think the idea is to use cryptonote_core to handle signing, not re-implement that logic 16:04:11 vthor: Clarifying, will this library do or not do the proof? 16:04:28 tobtoht_: wallet2 still has fingerprintable policy rules which need to be respected. 16:04:36 *proofs? 16:04:56 I'm unsure a flow for that API even exists in Monero today. <- well I was making transaction via wallet-rpc on both sides 16:05:09 are they well documented? 16:05:20 spirobel: of course not. 16:05:31 xD 16:05:44 yeah so lets work together to document them and reimplement all of this shit in rust 16:05:54 Sorry, if you're using wallet-rpc, then why are you proposing a new library vthor? 16:05:57 we want a piece of the library pie kaya 16:06:45 spirobel: Can you please stop? I'm not trying to quash this. I'm trying to work through it so there's a proper understanding. I haven't mentioned my work at all, only you have, and it's just a distraction. 16:07:00 nah it is not. 16:07:07 vthor: Clarifying, will this library do or not do the proof? The work will exactly done, how it would work (is working right now, with RPC), how written in the proposal I will not invent the wheel new. 16:07:11 wallet-rpc for example takes '2-4 mins to start up on a pi' or something to that effect. 16:07:14 you have a horse in this race 16:07:46 rust is iron oxide, so oxide right? 16:08:58 orry, if you're using wallet-rpc, then why are you proposing a new library vthor? Sorry, did you read, what I wrote in the answer of your comment and in the new proposal? 16:09:21 vthor: I don't follow even with your comments here 16:09:59 what? 16:10:07 1) Will this library still use wallet-rpc, or replace the need for wallet-rpc? 16:10:08 2) Will this library do the full TX flow, including the Bulletproofs, or will it outsource the Bulletproofs to a more computationally-enabled device? 16:10:45 Good meeting and good moderation, dankon everyone. 16:11:00 thanks for joining msvb-lab 16:12:31 1) of course not 2) it will do it the same way you would to it with two wallet-cli or two wallet-rpc, only eleminating all unneeded and put the need stuff clean in a library to use is then with another language. Not needing OpenSSL, not libhidusb etc. 16:12:52 I can follow up on the CCS if it'd be preferred by the way :) I don't have to get my context here and now. 16:13:23 as we're over the hour it would be best 16:13:24 Got it. Thank you for clarifying that for me. 16:13:33 thank you very much, this 1h is for me like 10h of work on energy drain level view. 16:14:06 thanks for attending the short meeting everyone, if kayabanerve has any follow up comments, much appreciated. else it can continue under the proposal 16:14:42 Thank you plowsof for you exelent service! :) 16:15:58 I have to do review on my end and I'll follow up on the CCS. I just wanted to check that the months paid for are actually feasible to do the work within. 16:17:09 k​ayabanerve: I can not estimate it, because I will need to hunt down in the source what I need and I had not really time to study it with calm yet. 16:17:31 Input on it is very welcome. 16:22:22 i wish we can just talk openly about the different projects that are in planning. and make sure we make space for everyone. 16:22:57 we had this situation before with seraphis when everyone was waiting for one person 16:23:04 lets not make the same mistake again 16:23:06 This proposal shouldn't say it's to build this library, and request funding over two months, if your estimate of the time necessary isn't two months IMO. If you need to do more work to make am estimate, I'd ask for that before this CCS is merged. 16:23:33 Is there some sort of central(ish) dev board somewhere that can organize all the things going on? 16:23:52 I don't love 16:23:52 > Should more time be needed, I'll submit a new proposal. 16:23:54 when the time estimate after 2 months may be 1 year. Then we either have to fund the work for a year OR we have to write-off the two months funded for incomplete work. 16:24:19 1 year is rediculous. 16:24:24 the vibe i am getting from kaya is that he plans his new lib and will make sure there are no "competing efforts" 16:24:43 not disagreeing with this per se 16:24:49 but we should talk about it openly 16:25:24 As in he modifies his work to make sure it meshes with others? 16:25:35 spirobel: I questioned the amount of time vthor's proposal would take, and they have stated they don't have an estimate. I feel that's a reasonable question as part of CCS review. 16:26:07 yep 16:26:10 they? It's only me stating it 16:26:12 If my reasonable review is making sure there aren't other libraries, you should complain to the proposers, not to me. 16:26:15 kayabanerve: which mcus did you have in mind when making changes to serai monero to work with no-std target ? 16:26:36 (They as in gender nonspecific singular I think) 16:26:39 If you do think I had any unreasonable parts to my review, then please call those out, don't ascribe malintent to me. 16:26:58 nah you are the right person to adress. I am not fronting you btw... just want to make it clear 16:27:20 no amlintent ascribed. just slight pvp vibes when there could be a chance for collaboration 16:27:40 no malintent ascribed. just slight pvp vibes when there could be a chance for collaboration 16:28:11 p​reland: "(They as in gender nonspecific singular I think)" <- a what? 16:29:30 Ie “they” is referring to one person (vthor) and not to a bunch of people 16:29:30 lol he was referring to you vthor when "they" (it was not a plural in that context) 16:29:53 spirobel: It doesn't matter as I'm not encouraging monero-serai over this lib. For the prior proposal, I asked how this proposal stands up against existing solutions, and I feel that was fair. I even explicitly said I just wanted to hear the differentiation. That's irrelevant here as I didn't, and don't, plan to bring up monero-serai here as I don't think this scope is inherently 16:29:54 already fulfilled by it. 16:30:52 I wish that English had a gender ambiguous term that wasn’t also number ambiguous lol 16:31:19 spirobel: You can't say it's not ascribing malintent when you say I'm unfairly attacking proposals. 16:31:27 that is "it" preland 16:32:02 There should be a pronoun for someone who wishes to remain anonymous and unidentified 16:32:07 call them monerochan 16:32:10 You said you're getting the vibe I'm trying to kill off 'competitors'. Either provide evidence of my misconduct or keep it to yourself. 16:32:17 its better to use the rust code base that we are building up like monero-serai (soon monero-oxide?) acceptxmr, monero-rs, cuprate ... as a basis to build this new offline signer focused library. toolchain will be simpler and the whole thing will be more future proof 16:32:23 "It" isn't generally used for humans vthor 16:32:34 Monero-chan…….M-chan……Man! 16:32:58 I'm not against monero-serai being used here. I'm not going to recommend it though. 16:33:12 nah thats not what i was saying. i just think its missing context and a missed opportunity to make this more future proof. 16:33:39 They explicitly want a C++ codebase which maintains support for the wallet2 API, despite not using wallet2. I'm not going to recommend my work in Rust when I believe that variety is beneficial. 16:33:41 to focus on these technicalities 16:33:54 no there is obvious he/she or if you speak with me you, except, and here you would be the first, acknowledge me as a deity. But that is off-topic 16:34:28 If I actually wanted to kill off a 'competitor', then yeah, I would say they should just use monero-oxide. 16:34:30 no. read carefully they just want something that works on a raspi zero and is interoperable. dont care about walle2 16:34:32 Malintent: intentional behavior, as opposed to merely *incidental* behavior 16:34:34 (Btw vthor, you should probably have a timeline for your ccs if you don’t have one already….) 16:34:40 just use it because its currently the elephant in the room 16:34:48 just use wallet2 as a basis because its currently the elephant in the room 16:34:50 monero-wallet-[rpc, gui] is built around wallet2 and they want to be able to serve as a cold wallet for those. 16:35:10 So they aren't using wallet2, but they do need API compatibility with its cold wallet API. 16:35:22 assumptions that i dont see like this reflected in the proposal 16:35:37 even if its true which i dont it is, we are short on resources(just look at the funding section of ccs 16:35:38 its better to not stretch ourselves thinner than right now 16:35:45 even if its true which i dont think it is, we are short on resources(just look at the funding section of ccs 16:35:46 its better to not stretch ourselves thinner than right now 16:35:55 spirobel: vthor said here it'd use that API. 16:36:36 ^ 16:37:06 yeah but we need a offline signer / ledger alternative. i am agreeing with you and thats why i am saying we shouldnt invest more into the old code base as it will be phased out anyway 16:37:08 assumptions. nothing else. 16:37:11 so better build on the rust shit 16:37:13 Unless I misread that. I took it as if you prior had a cold wallet using monero-wallet-rpc, talking to another monero-wallet-rpc, you could now have a cold wallet with this lib (still talking to monero-wallet-rpc). 16:37:54 I don't believe we're short on resources. Even if we were, I don't think the CCS should be comparatively ranking proposals. Any well reasoned proposal should be put up. 16:38:33 kaya thinks a lot haha 16:38:37 vthor: I'm sorry, did I misinterpret you? 16:38:59 "Unless I misread that. I took it as if you prior had a cold wallet using monero-wallet-rpc, talking to another monero-wallet-rpc, you could now have a cold wallet with this lib (still talking to monero-wallet-rpc)." on an Pi Zero waiting 3-4 min to load a walltet, switching a wallet wait again... 16:39:31 ... I'm not saying the Pi 0 would use wallet-rpc 16:39:38 I'm saying it'd use this library. The non-Pi 0 would still run wallet-rpc though. 16:39:52 and it is crap, it is valid for a PoC, but not for production actualy being security relevant. 16:40:32 I'm saying this library replaces wallet-rpc on the Pi 0, yet still talks to wallet-[rpc, gui] on the computer with the view keys which is connected to the internet. 16:40:57 I used it for the moment to finish it, if not I could had simply could abandon the project, or work fo fresh air. 16:41:04 I completely understand you don't want wallet-rpc on a Pi 0. 16:41:22 " I'm saying it'd use this library. The non-Pi 0 would still run wallet-rpc though." no of course not 16:42:04 So if I have a laptop and a Pi 0, and the Pi 0 runs this library yet isn't connected to the internet 16:42:15 What do I run on my laptop to get it to sign a transaction? 16:42:48 Does my laptop also run this library? Does my laptop run some dedicated XmrSigner client? 16:43:36 I'm very sorry I misinterpreted you there. You said it'd be the same as if you had two wallet-rpcs. I thought that meant you replaced the wallet-rpc on the Pi, yet kept the wallet-rpc on the laptop. 16:43:59 *[cli, rpc] 16:44:16 what I am saying is, I will fish in monero source how the things done, import where is feasable or copy paste where it is not to get all the dependencies not needed out. I will almost not write own code, more like shims (using existing code base) to make a small to hopefull tiney library as static as possible to do the absolut necessery, so audit is easier, ressources on the device are saved, it will be documented and easy reusable (so the next doesn't 16:44:17 need to make a deep dive). 16:45:05 What do I run on my laptop to get it to sign a transaction? The cmpanion app (which uses internally wallet-rpc) or feather, Nero or monero-gui (all view only wallet) 16:45:20 ... K, so, I was not wrong. 16:45:59 The Pi doesn't run wallet-rpc. It runs this library. The laptop (or whatever host device) still does run some wallet2-based program and uses its API. 16:46:24 Well I should reduce drastically scope I was told ;) 16:46:55 maybe do the research before the proposal 16:47:00 The Pi doesn't run wallet-rpc. It runs this library. The laptop (or whatever host device) still does run some wallet2-based program and uses its API. <- correct, for the signer irrelevant because it is agnostic about the counter part. 16:47:06 > " I'm saying it'd use this library. The non-Pi 0 would still run wallet-rpc though." no of course not 16:47:06 I said the non-Pi 0 would run wallet-rpc. As in, the device which isn't the Pi 0 would. You just said the companion app would use wallet-rpc, or an app which internally is wallet2 and exposes that API. 16:47:42 I'm sorry we've had communication issues today. 16:47:47 the view only side 16:48:40 In a perfect world this would be on an application like the companion app also not the case, and it would have only what it really needs - IMO 16:49:15 I'll do my research on the relevant wallet2 API and try to obtain my own beliefs on how long this would take. I'll leave feedback on the CCS when I have firm feedback to give. I'd encourage you to do your own estimates however and set your CCS's length accordingly. 16:55:32 I think it will be around that 60 days, but I can't be sure, not even after an estimate. And researching 20h (what would be part of the work), but now unpaid makes IMO no sense. It is not that I have too much time. And I stated in the proposal also "If the project completes before 240 hours, unused funds can be allocated to future proposals or returned to the general fund.", not only "Should more time be needed, I'll submit a new proposal." And yeah the 16:55:34 240h is what I estimate, but I can be on both sides off.