monero-project / meta

A Meta Repository for General Monero Project Matters
168 stars 71 forks source link

Monero Community Workgroup Meeting: Saturday 31th August 15:00UTC #1065

Closed plowsof closed 2 months ago

plowsof commented 2 months ago

Location: Libera.chat, #monero-community | Matrix

Instructions for joining the monero.social Matrix server.

Time 15:00 UTC Check your timezone

Moderator: plowsof

Please reach out in advance of the meeting if you would like to propose an agenda item.

Proposed Meeting Items:

  1. Introduction
  2. Greetings
  3. Community highlights
    News: Monero Observer - Revuo Monero - The Monero Standard - Monero Moon
  4. CCS updates
    a. New Monero Website placeholder / draft
    b. Haveno Multi-Platform Native App For Every OS wishes to be merged into work in progress and be funded entirely by the abandoned / now void haveno front end proposal gitlab comment for details c. Offline Signing Library for XmrSigner Production
  5. Workgroup reports
    a. Dev workgroup b. Localization workgroup c. Outreach workgroup d. Events workgroup - MoneroKon 2023 e. Website workgroup f. Policy workgroup g. Research workgroup h. Seraphis Migration workgroup
  6. Open ideas time
  7. Confirm next meeting date/time

Previous meeting including logs

Meeting logs will be posted here afterwards.

plowsof commented 2 months ago

Logs

< plowsof > meeting in

< plowsof > 2hr35 mins allegedly https://github.com/monero-project/meta/issues/1065

< plowsof > 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

< plowsof > 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

< plowsof > 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

< f​reeross:monero.social > m-relay: does this affect the haveno-web UI bounty?

< plowsof > no

< s​pirobel:kernal.eu > https://x.com/spirobel/status/1829742700876480690 kuno still stuck at 2 percent funding.

< s​pirobel:kernal.eu > might have to go the ccs route after all.

< s​pirobel:kernal.eu > but reading the comments by kaya it seems like he wants to eat that as well

< w​oodser:monero.social > hey so, thinking about this, we (kewbit and I) are interested to work together to create the new haveno ui

< plowsof > awesome woodser

< w​oodser:monero.social > essentially thinking to:

< w​oodser:monero.social > - find designer(s)

< w​oodser:monero.social > - improve the design of the desktop application, incorporating "wizard" elements from bisq2

< w​oodser:monero.social > - design for mobile

< w​oodser:monero.social > - kewbit is the lead dev for delivering the apps

< s​pirobel:kernal.eu > WHAT ABOUT ME lol

< plowsof > spirobel you hate the ccs leave us alone please

< w​oodser:monero.social > maybe there are good ways for you to help too, especially if you are familiar with dart/flutter?

< s​pirobel:kernal.eu > i hate getting fucked over like the last time

< s​pirobel:kernal.eu > i started a ccs

< w​oodser:monero.social > we can talk more about this, there will be a lot to develop

< k​ewbit:matrix.org > 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

< k​ewbit:matrix.org > 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.

< k​ewbit:matrix.org > 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!

< 3​21bob321:monero.social > Holy shit batman

< s​pirobel:kernal.eu > you are getting paid for by the community to be impartial. maybe time to get rid of you if you dont act the part

< w​oodser:monero.social > for sure we want to incorporate designers and their input in the process. they should really lead the design with us

< s​pirobel:kernal.eu > what is the point in using dart and flutter?

< s​pirobel:kernal.eu > thats an outdated dead technology

< s​pirobel:kernal.eu > waste of ressources

< s​pirobel:kernal.eu > waste of resources

< w​oodser:monero.social > I figure it's between dart/flutter or web technologies (react, electron, etc)

< k​ewbit:matrix.org > If you were not happy with the design from the previous devs? Why did it continue to get developed

< w​oodser:monero.social > apparently dart/flutter is one of the most common choices for creating cross platform apps for mobile and desktop

< k​ewbit:matrix.org > Is it the best choice

< k​ewbit:matrix.org > Nothing even comes close

< w​oodser:monero.social > design versus development was ongoing contention between erc and I, and making any design changes was a struggle after basic development began

< k​ewbit:matrix.org > Maybe React Native comes close but meh

< w​oodser:monero.social > 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

< k​ewbit:matrix.org > Not even facebook use that anymore and they made it!

< s​pirobel:kernal.eu > flutter is one of these dead google projects that will get killed off at some point

< k​ewbit:matrix.org > Absolutely nonsense

< s​pirobel:kernal.eu > react is the better choice

< k​ewbit:matrix.org > The community is what makes flutter powerful at this point

< s​pirobel:kernal.eu > much bigger ecosystem

< s​pirobel:kernal.eu > google just fired the flutter team btw

< k​ewbit:matrix.org > 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 :)

< k​ewbit:matrix.org > It's much quicker to deliver a lot of value in Dart and I strongly suggest learning it, it's awesome.

< s​pirobel:kernal.eu > and canonical is not going to fill the gap

< k​ewbit:matrix.org > ahhh the community will take over

< k​ewbit:matrix.org > 100%

< s​pirobel:kernal.eu > lol a cto. this thing is dead. wake up

< k​ewbit:matrix.org > New flutter update was quite recent!

< s​pirobel:kernal.eu > look where the rest of the ecosystem is going

< s​pirobel:kernal.eu > look at the bigger market cap coins

< k​ewbit:matrix.org > nah not at all you're living in a fantasy land!

< k​ewbit:matrix.org > ;)

< s​pirobel:kernal.eu > like ethereum or solana

< s​pirobel:kernal.eu > they are 100x our size

< s​pirobel:kernal.eu > most of their stuff is in react

< s​pirobel:kernal.eu > time to wake up and not invest in dying ecosystems

< k​ewbit:matrix.org > well apparently we dont care what frameworks we use anyway, COUGH COUGH ** 'elm'.

< s​pirobel:kernal.eu > elm smh

< k​ewbit:matrix.org > What makes and ecosystem grow?

< s​pirobel:kernal.eu > when people work together instead of against each other

< k​ewbit:matrix.org > 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.

< k​ewbit:matrix.org > 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

< k​ewbit:matrix.org > tends to be higher.

< k​ewbit:matrix.org > woodser: https://github.com/haveno-dex/haveno/issues/1236

< k​ewbit:matrix.org > oop wrong chat

< w​oodser:monero.social > yeah we can bring that over to #haveno-dev:haveno.network and get more notifications implemented

< ofrnxmr > That link is totally broken btw

< o​frnxmr:monero.social > this should work https://matrix.to/#/#haveno.exchange:monero.social

< w​oodser:monero.social > if I copy the link from the development room, it's https://matrix.to/#/#haveno-dev:haveno.network 🤔

< o​frnxmr:monero.social > The haveno.network domain is dead

< o​frnxmr:monero.social > So it wont load unless youre already in the group

< o​frnxmr:monero.social > The matrix space i created "should" let you join because it has the "real" address

< w​oodser:monero.social > I guess this should be the link that works: #haveno-dev:monero.social

< o​frnxmr:monero.social > it might, but only for monero.social users, since its a local-only address

< o​frnxmr:monero.social > The room cant be modified to change the main addresses bcuz the admin accounts are on haveno.network

< o​frnxmr:monero.social > https://matrix.to/#/!HeVhOlajgOuVMOKhvS:haveno.network?via=monero.social?via=matrix.org should work

< o​frnxmr:monero.social > ```

< o​frnxmr:monero.social > https://matrix.to/#/!HeVhOlajgOuVMOKhvS:haveno.network?via=monero.social?via=matrix.org

< o​frnxmr:monero.social > ```

< o​frnxmr:monero.social > Ffs lol

< o​frnxmr:monero.social > https://matrix dot to/#/!HeVhOlajgOuVMOKhvS:haveno.network?via=monero.social?via=matrix.org

< s​pirobel:kernal.eu > shit does not work

< s​pirobel:kernal.eu > what happend to the domain?

< o​frnxmr:monero.social > which link?

< o​frnxmr:monero.social > This one should work

< o​frnxmr:monero.social > so should this one

< w​oodser:monero.social > we switched the matrix rooms from haveno.network to matrix.social a long time ago

< o​frnxmr:monero.social > Erciccione killed the homeserver

< o​frnxmr:monero.social > Haveno-dev was never switched

< w​oodser:monero.social > I can take this as a todo

< o​frnxmr:monero.social > I switched haveno room, but matrix.org shit the bed and rolled back. Not main haveno room has no address again

< o​frnxmr:monero.social > Its not possible to change haveno-dev's main address

< w​oodser:monero.social > ah ok. and the only admin is @woodser:haveno.network and so dead account I guess

< o​frnxmr:monero.social > The only admins are on haveno.network, and that homeserver is dead.

< o​frnxmr:monero.social > main haveno room has vik as admin, so that one can be fixed again.

< o​frnxmr:monero.social > The new haveno space i created is on monero.social, so this problem shouldnt happen again

< o​frnxmr:monero.social > I switched haveno room, but monero.social** shit the bed and rolled back. Not main haveno room has no address again

< o​frnxmr:monero.social > Spirobel, did the haveno space link work for you?

< s​pirobel:kernal.eu > yes. long time no see lol

< s​pirobel:kernal.eu > remember being in the room in the good old days lol

< w​oodser:monero.social > 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

< w​oodser:monero.social > so the current ccs would need updates before being merged

< w​oodser:monero.social > so the current ccs request would need updates before being merged

< k​ewbit:matrix.org > I agree we can expand a bit more, perhaps lets do this today, and hopefully we can move it across, like asap? 😆

< plowsof > noted woodser, thank you

< s​pirobel:kernal.eu > reminds me a bit of the "facoring" thing

< s​pirobel:kernal.eu > what happend to this guy btw?

< s​pirobel:kernal.eu > he asked me to work with him in a twitter dm before

< s​pirobel:kernal.eu > saying i asked the right right questions in the dev channel

< s​pirobel:kernal.eu > and then he disappeared

< s​pirobel:kernal.eu > lol

< s​pirobel:kernal.eu > it is okay to have multiple libraries I think. But there needs to be a clear purpose. Not just random changes with unclear goals.

< s​pirobel:kernal.eu > 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

< s​pirobel:kernal.eu > 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

< s​pirobel:kernal.eu > If I look at serai and haveno I see a massive scope that is mostly building out a second decentralized p2p protocol.

< r​ucknium:monero.social > Have you seen https://github.com/mainnet-pat/monujo-quasar ?

< s​pirobel:kernal.eu > yes. and I have also seen monero hotshop

< s​pirobel:kernal.eu > and my own work https://www.youtube.com/watch?app=desktop&v=4DLcsQ45zoE

< s​pirobel:kernal.eu > and haveno

< s​pirobel:kernal.eu > any one using crypto grampys hotshop still?

< s​pirobel:kernal.eu > 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

< plowsof > Meeting time https://github.com/monero-project/meta/issues/1065

< plowsof > Greetings!

< jorge > hello

< vthor > hi :)

< o​frnxmr:monero.social > Morning

< k​ewbit:matrix.org > Afternoon

< o​frnxmr:monero.social > I'll be on the road during meeting, apologies if i miss out

< msvb-lab > Hello.

< plowsof > 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 🚀

< d​iego:cypherstack.com > hi

< d​iego:cypherstack.com > Neat!

< plowsof > 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

< plowsof > anyone like to share something thats happened over the previous week?

< d​iego:cypherstack.com > Were some pretty neat findings imo

< jorge > Weblate is still down, I want to finish the Esperanto translation, but currently there is no way to do it :(

< plowsof > atomic swaps are really bogged down by the 10 block lock, to name an example that would benefit greatly from any decrease there

< ofrnxmr > its not bad

< ofrnxmr > slower than btc<>ltc, but not bad

< plowsof > 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)

< plowsof > this is not certain of course

< plowsof > and https://docs.getmonero.org is live . currently a work in progress

< plowsof > it has an A rating for http headers and everything, wow look at that

< ofrnxmr > and an onion too

< vthor > 8)

< ofrnxmr > http://xmrdoc6phnvjbf5hmjbwdfu47zavzfngymlnwhs2gyxxpxmad4c65kyd.onion

< plowsof > 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

< k​ewbit:matrix.org > 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

< k​ewbit:matrix.org > 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.

< plowsof > nice

< plowsof > i think we can jump into the open ccs ideas now?

< d​iego:cypherstack.com > Skip the website one please.

< plowsof > skippethd

< d​iego:cypherstack.com > As discussed in previous weeks it's not ready due to no design yet (which I'm working on)

< plowsof > thanks

< plowsof > b. Haveno Multi-Platform Native App For Every OS wishes to be merged into work in progress and be funded entirely by the abandoned / now void haveno front end proposal [gitlab comment for

< plowsof > details](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/489#note_25985)

< plowsof > kewbit

< plowsof > quite a big development on this arrived toda

< plowsof > today*

< plowsof > woodser began sharing his thoughts on the direction of this here https://libera.monerologs.net/monero-community/20240831#c419609

< plowsof > seems like they are going to discuss the plan further and come back with a modified proposal

< plowsof > anyone have opinions? happy? sad? that haveno UI is finally going to get rolling?

< plowsof > it would presumably move into funding required after absorbing the remaining funds from the original haveno front proposal

< plowsof > spirobel was even offered to take part if they have flutter/dart skills

< k​ewbit:matrix.org > 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

< k​ewbit:matrix.org > ld look, I'd work closely with whoever that may be when the time comes.

< h​ardenedsteel:monero.social > mastodon or lemmy bot is much needed

< d​iego:cypherstack.com > CS has flutter/dart skills, and...design skills :P

< k​ewbit:matrix.org > 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.

< plowsof > sounds good. so we can patiently wait for the conversation to develop, resulting in changes to the proposal

< plowsof > oh look a designer with flutter/dart skills too

< s​pirobel:kernal.eu > can learn it in a weekend. But tbh its the wrong direction

< s​pirobel:kernal.eu > what we need is a real browser wallet. something i have put a lot of time and effort in

< s​pirobel:kernal.eu > that is where the rest of crypto is moving. since ages

< k​ewbit:matrix.org > seems like we only have biasd opinons

< k​ewbit:matrix.org > please can we bring in an external consultant

< s​pirobel:kernal.eu > you guys can keep going in this other direction

< k​ewbit:matrix.org > paid

< s​pirobel:kernal.eu > bring in mckinsey

< ofrnxmr > Hi.

< s​pirobel:kernal.eu > LFG

< k​ewbit:matrix.org > who does not have any bias

< k​ewbit:matrix.org > at all

< ofrnxmr > 😆

< plowsof > an app on the system vs a web app has advantages in terms of security, so i've been told

< k​ewbit:matrix.org > because this is getting a bit stupid

< k​ewbit:matrix.org > :D

< s​pirobel:kernal.eu > is objective. use any chain above 100billion market cap

< s​pirobel:kernal.eu > its all web based

< ofrnxmr > Scams

< s​pirobel:kernal.eu > i mean fine u do yours

< s​pirobel:kernal.eu > i will not interfere or fud

< s​pirobel:kernal.eu > have fun guys

< d​iego:cypherstack.com > I feel web-based scams are much easier to perform than app-based ones.

< plowsof > so kewbit is saying merge as is, woodser is saying hold off on merging. im leaning towards holding off a bit

< s​pirobel:kernal.eu > DONT FUD MY SHIT OKAY

< d​iego:cypherstack.com > That's why I personally have shied away from making it. But I may just be a coward there.

< ofrnxmr > Doesnr disq react native

< s​pirobel:kernal.eu > you never used eth or solana?

< d​iego:cypherstack.com > I agree that adoption would be much higher and faster with web based.

< d​iego:cypherstack.com > both are supported in Stack Wallet. Got several requests to do web-based wallet for it. Chose not to.

< s​pirobel:kernal.eu > so maybe all the other shit is the real grift

< ofrnxmr > Android app > webapp all day everyday

< ofrnxmr > Ask localmoneri

< ofrnxmr > Couldnt catch me using their website if you paid me to

< d​iego:cypherstack.com > In other words (and not to be wishy-washy) there are non-trivial pros and cons to both directions.

< k​ewbit:matrix.org > 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.

< ofrnxmr > Monero waller, who uses a webwallet

< s​pirobel:kernal.eu > all the successful wallets include browsers now

< vthor > I try to say nothing, but the browser is the number one vunerability on a system. And this is all I will say.

< ofrnxmr > Anyobe even uss a cex webapp?

< s​pirobel:kernal.eu > on mobile

__< r​eal_glitch:matrix.org >__ unpopular opinion:

__< r​eal_glitch:matrix.org >__ Tauri > electron

< d​iego:cypherstack.com > yeah it's why I'm not successful :P

< plowsof > 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

< plowsof > this would be a matter of day(s)

< plowsof > kewbit your proposal was also made days ago. relax please

< k​ewbit:matrix.org > I'm sure we can work in days, sure

< ofrnxmr > all evm is evm

< k​ayabanerve:monero.social > 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.

< ofrnxmr > Of course they use browsers, its web3

< k​ewbit:matrix.org > I am relaxed :D

< plowsof > thanks for clarifying kayabanerve

< d​iego:cypherstack.com > relax further. Massage-levels

< d​iego:cypherstack.com > the CCS will pay for one

< plowsof > lol

< k​ewbit:matrix.org > unfortunately non of the massage parlours around here accept XMR yet

< d​iego:cypherstack.com > in fact, let's open the CCS for a masseuse for every contributor

< d​iego:cypherstack.com > can't work if we're burned out ;)

< k​ewbit:matrix.org > You joke, but it's good.

< plowsof > certainly a gap in the market, now then , waiting some day(s) for woodser and kewbits friendship to flourish?

__< r​eal_glitch:matrix.org >__ Diego Salazar: it seems that you got your first payment for your ccs

< plowsof > kayabanerver vthor has closed and opened another proposal btw after your and others feedback

< d​iego:cypherstack.com > Indeed.

< plowsof > unless we have other things to mention regarding kewbits proposal we can move on

__< r​eal_glitch:matrix.org >__ can you mention the works you have done in the past month? aside from bringing back ofrnxmr

< d​iego:cypherstack.com > 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

< d​iego:cypherstack.com > followed by a lot of design work for the new website

< plowsof > 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

< msvb-lab > It sounds like it will be very good, and using Astro.

< d​iego:cypherstack.com > the majority of hours were for backend exploration and preliminary design work

__< r​eal_glitch:matrix.org >__ so most of them are claims that you worked but nothing notable for now on backend side right?

< d​iego:cypherstack.com > LOL

__< r​eal_glitch:matrix.org >__ kk pls continue

< d​iego:cypherstack.com > You want me to do a write-up of the explored SSGs as proof?

< plowsof > lets get to vthors proposal, only a few day(s) old but has had a major re-write

< d​iego:cypherstack.com > you want me to share some of the designed icons here?

__< r​eal_glitch:matrix.org >__ no i will wait for another month to see the fruit of those efforts

< plowsof > c. Offline Signing Library for XmrSigner Production

< d​iego:cypherstack.com > 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.

< d​iego:cypherstack.com > (one second plowsof, sorry for disrupting)

< s​pirobel:kernal.eu > what is supported? send and receive and thats it?

< d​iego:cypherstack.com > Things were split between Astro and Hugo, with a small pocket of Jekyll people in the mix.

_< tobtoht >__ 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.

< plowsof > 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

__< r​eal_glitch:matrix.org >__ for some reason this didnt appear on CCS ideas section

< s​pirobel:kernal.eu > why not just use wordpress with a cdn?

< vthor > thank you tobtoht_ :)

< d​iego:cypherstack.com > 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

< plowsof > 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

< d​iego:cypherstack.com > anyways, that's enough tangent from me, please continue as normal plowsof

< d​iego:cypherstack.com > happy to continue this conversation after the meetinig

< plowsof > which didnt appear on the ccs ideas section real_glitch?

< s​pirobel:kernal.eu > i feel like collaboration would be faster and more convenient if a normal CMS was used

< plowsof > oh i see it now, thanks...

__< r​eal_glitch:matrix.org >__ vthor's new proposal

< vthor > what is supported? send and receive and thats it? In the library? Seed generation output/key images, addresses and signing.

< plowsof > true, will have a look

< plowsof > vthor rename the file to .md (it has no extension currently)

< r​ucknium:monero.social > 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.

< plowsof > good job Rucknium

< vthor > vthor rename the file to .md (it has no extension currently), oh, heck. Will do.

< plowsof > spirobel was first? one of? to lead the C ABI discussions, nice to have you here

< plowsof > also the pre-proposal-parser will show a red circle and "this is wrong pls fix" soon

< d​iego:cypherstack.com > spirobel: I'll answer your questions in the website channel so as not to further disrupt the meeting

< ofrnxmr > Does c abi have any crossover with monero_c by mrcyjanek

< plowsof > 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.

< ofrnxmr > https://github.com/MrCyjaneK/monero_c

< plowsof > definitely would be great to have feedback from mrcyjanek too

< s​pirobel:kernal.eu > my comment is: we are moving to rust

< s​pirobel:kernal.eu > base it on the new rust libs instead of the old cpp trash

< vthor > 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.

< s​pirobel:kernal.eu > responding to this

< s​pirobel:kernal.eu > we have tons of those all over the monero ecosystem

< s​pirobel:kernal.eu > i just think we should focus resources and eyes on the new rust libraries

< plowsof > 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)

< s​pirobel:kernal.eu > that will take over everything sooner or later

< ofrnxmr > vthor, u should look at it ;)

< vthor > ofrnxmr: not exactly, I will avoid wallet2 completely, but thank you for the link, could be helpful.

< ofrnxmr > Spirobel, we have 2 devs on ccs focused entirely on cuprate

< plowsof > listed on our -site roadmap also ( syntheticbird made cuprate.org using astro - msvb-lab who seems to be a fan of astro)

< s​pirobel:kernal.eu > >Performance: The current implementation using wallet RPC is slow,

< s​pirobel:kernal.eu > especially on resource-constrained devices.

< s​pirobel:kernal.eu > 100% agree with this btw

< k​ayabanerve:matrix.org > Are we still discussing c?

< k​ayabanerve:matrix.org > Topic c, the new signing library

< vthor > 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.

< plowsof > we re discussing vthors new proposal. the modularizing monero one was closed

< s​pirobel:kernal.eu > vthor: seed signer is a raspi, correct?

< plowsof > new one from vthor https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/495

< vthor > correct pi zero

< k​ayabanerve:matrix.org > Yes, that's what I was referring to. I just wanted to check we hadn't moved on.

< plowsof > tangents

< k​ayabanerve:matrix.org > I lean towards NACK due to

< k​ayabanerve:matrix.org > > Unsigned transaction handling (description, sanity checks, signing)

< k​ayabanerve:matrix.org > But I may be being too harsh.

< s​pirobel:kernal.eu > so you do buildroot arm target to cross compile the cpp ?

< s​pirobel:kernal.eu > inb4 monero-oxide

< plowsof > more details required? or

< k​ayabanerve:matrix.org > 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.

< k​ayabanerve:matrix.org > That's several months of work.

< vthor > 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

< k​ayabanerve:matrix.org > This can be done in two months. I don't believe it can be done in two months without several security issues.

< plowsof > a response at this very moment to everything, is not required vthor

< s​pirobel:kernal.eu > wdym i suppose this is to display the infos on the airgapped device to make sure it hasnt been messed with

< s​pirobel:kernal.eu > essentially just displaying the info

< k​ayabanerve:matrix.org > The airgapped device has to make the ephemeral keys and do all the derivations itself.

< k​ayabanerve:matrix.org > 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.

< vthor > 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?

< k​ayabanerve:matrix.org > I'm unsure a flow for that API even exists in Monero today.

< s​pirobel:kernal.eu > 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

< k​ayabanerve:matrix.org > vthor: If you build a new library to sign a TX, your library must check the content of the TX.

< k​ayabanerve:matrix.org > Wow, I haven't mentioned monero-oxide at all and don't plan to.

< s​pirobel:kernal.eu > no ccs for monero-oxide?

< s​pirobel:kernal.eu > put the cards on the table lol

< k​ayabanerve:matrix.org > 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.

< k​ayabanerve:matrix.org > I don't believe 2 months is the answer.

< vthor > 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?

_< tobtoht >__ kayabanerve: I think the idea is to use cryptonote_core to handle signing, not re-implement that logic

< k​ayabanerve:matrix.org > vthor: Clarifying, will this library do or not do the proof?

< k​ayabanerve:matrix.org > tobtoht_: wallet2 still has fingerprintable policy rules which need to be respected.

< k​ayabanerve:matrix.org > *proofs?

< vthor > I'm unsure a flow for that API even exists in Monero today. <- well I was making transaction via wallet-rpc on both sides

< s​pirobel:kernal.eu > are they well documented?

< k​ayabanerve:matrix.org > spirobel: of course not.

< plowsof > xD

< s​pirobel:kernal.eu > yeah so lets work together to document them and reimplement all of this shit in rust

< k​ayabanerve:matrix.org > Sorry, if you're using wallet-rpc, then why are you proposing a new library vthor?

< s​pirobel:kernal.eu > we want a piece of the library pie kaya

< k​ayabanerve:matrix.org > 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.

< s​pirobel:kernal.eu > nah it is not.

< vthor > 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.

< plowsof > wallet-rpc for example takes '2-4 mins to start up on a pi' or something to that effect.

< s​pirobel:kernal.eu > you have a horse in this race

< plowsof > rust is iron oxide, so oxide right?

< vthor > 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?

< k​ayabanerve:matrix.org > vthor: I don't follow even with your comments here

< vthor > what?

< k​ayabanerve:matrix.org > 1) Will this library still use wallet-rpc, or replace the need for wallet-rpc?

< k​ayabanerve:matrix.org > 2) Will this library do the full TX flow, including the Bulletproofs, or will it outsource the Bulletproofs to a more computationally-enabled device?

< msvb-lab > Good meeting and good moderation, dankon everyone.

< plowsof > thanks for joining msvb-lab

< vthor > 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.

< k​ayabanerve:matrix.org > 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.

< plowsof > as we're over the hour it would be best

< k​ayabanerve:matrix.org > Got it. Thank you for clarifying that for me.

< vthor > thank you very much, this 1h is for me like 10h of work on energy drain level view.

< plowsof > thanks for attending the short meeting everyone, if kayabanerve has any follow up comments, much appreciated. else it can continue under the proposal

Automated by this