EmeraldSnake[m]: hundreds of developers are

selsta: This might be interesting for you (until "Branches" paragraph), since you said, that the compilation time increase could have been a measurement problem:

In short: it doesn't appear so, and this is kind of confirmed by changes in the inputs and the new output: memory consumption for compilation.

Does monero support aarch64?

s/Does/Is/

Collected monero-gui from sources. Can I make the GUI version show up?

версия = version, sorry for non-english language

Monero has code to build for aarch64. I can't say how well it runs in practice though.

<BigmenPixel[m]> "Does monero support aarch64?" <- Do you mean RPi4 by a chance?

mj-xmr[m]: Him and all other PCs with aarch64 processor

As long as other SoCs have AES support, it should run.

Are we talking about 64-bit OS on your RPi4 or 32?

Ah, OK. You're mostly interested in GUI.

But the previous question remains.

mj-xmr[m]: I'm just wondering if it makes sense to build a flatpak assembly of monero-gui for the aarch64 architecture.

s/assembly/build/

I myself do not have a PC with aarch64 processor architecture.

BigmenPixel: It should make sense. Why not?

Bringing up the multisig pr again (#7877): is there anyone currently planning to review this? Do we need to find someone able to review it?

That's one massive diff :/

Monero aarch64 support is perfectly good

anything that supports DIYers on a limited budget using XMR is likely to be good

moneromooo: yep unfortunately I had to redo most of the existing implementation.

evidence so far suggests that majority of rpi owners have no idea what they're doing

they don't even realize their 64bit CPUs are running 32bit OSs

After the new protocol (be it Seraphis or something else) is defined, is it possible that we will be able to spend outputs without waiting for 10 confirmations like we currently do?

s/defined/implemented/

The ability to instantly spend coins from received from a wallet you trust is a great feature for speeding up commercial transactions.

in practice that 10 block delay doesn't slow anything down in commercial transactions

because a wallet that's actually being used frequently will have more than 1 spendable output at any given time

people spend too much time fixating on this non-issue

alex[m]123456721: with Seraphis/Lelantus-Spark, there is a way IF 1) you are willing to reveal the true spends of your tx to the recipient; 2) the recipient trusts you not to double-spend. It isn't useful for most cases.

Plus the recipient will still have to wait for 10 blocks to spend your output (unless he extends the of-chain tx chain...).