<r​brunner7:monero.social> I am sorry to be *that* guy, but you know, any library that does Monero "crypto" on their own will run into a very serious challenge in probably less than a year, with FCMP++. If they want to keep the library functioning with that approach and not suffer a serious downgrade of functionality to merely one RPC client more, they will have to support that somehow as well. Maybe it wou<clipped message>

<r​brunner7:monero.social> ld be worth to ask about their thoughts in this respect?

<k​ayabanerve:matrix.org> rbrunner7: my rust libs will easily integrate the rust libs I wrote, wdym

<k​ayabanerve:matrix.org> :p

<k​ayabanerve:matrix.org> Jokes aside, a reimplementation of FCMP++s isn't completely infeasible but the immediate step forward would be to bind it. The Rust should be decently bindable itself but it could also be compiled to wasm and bound that way.

<k​ayabanerve:matrix.org> The signature is trivial. The ability to delegate the FCMP opens a lot of freedom.

<b​asses:matrix.org> Diego Salazar

<s​yntheticbird:monero.social> Because the left one is more important

<b​asses:matrix.org> bruh you forgot what I propsed?

<b​asses:matrix.org> proposed*

<b​asses:matrix.org> see messages below

<d​iego:cypherstack.com> Secondary buttons don't have to be empty, and in our case where there is a kind of design behind it (not finalized) it's fine