how unsecure is money gui client?

user85, monero GUI client?

user85: what kind of answer to you expect?

some answer that outlines potential holes

stuff to be aware of

in general the CLI wallet is more secure because it also does mem

in memory encryption*

but that's only relevant if you have malware on your system and even then it doesn't 100% protect you from it

otherwise i can't think of anything else

I almost exclusively use the CLI

Both Monerujo and Cake choke on my wallets.

Too many txs I think.

Kind of sad really.

choke in what way?

ok yes cli can be better

also linking transactions - if i send funds from address a to address b both are mine they can not be linked or they can

that's a more general monero related question and not gui specifically

yes

selsta, they both become totally unresponsive.

which phone?

selsta, the wallets have >20k txs though

Normal person phone.

the gui should work fine with 20k tx not sure about mobile wallets

Yes, GUI woks fine. Mobile clients choke.

dsc_ made sure to add pages to the wallet history

because of it

GUI used to choke but dsc_ fixed that adter me complaining.

So now I'm going to complain about the mobile wallets.... maybe they'll get fixed too.

Complain more please:)

right on cue lol

yes hello this is the transaction history performance helpdesk

hi

o/

:D

so the reason why Cake/Monerujo are slow here is (probably) related to the way those apps render results to the screen. For example Cake uses Flutter and when you have 20k transactions, that's a lot of drawing for poor Flutter to do.

Do you guys even transact?

hi

for the monero GUI this was also a bit much, so I introduced pagination there

dsc_, the mobile wallets need to cache older txs to disk or something... only keep the last 50 or so in memory

dsc_: did you use qt data model thing in wowlet?

for Feather pagination was not neccesary, because QtWidgets can easily render 100k items without breaking a sweat

selsta: the wut? :P

don't know how it's called

Yeah same model is being used as in the GUI

you currently write the tx history in javascript array

Maybe "virtualized data store"?

I don't know. It's not a problem that affects many users at the moment. But it needs to be addressed by the mobile wallets soon.

For me it's a terrible user experience.

How did you get so many? With your dice games?

Nice try FBI.

rbrunner, yeah

I would suggest pagination for Cake/Monerujo

Trust me, the FBI knows already, if there is something to know :)

I dod a lot of testing on mainnet too.

So I have a few wallets with a lot of txs.

Questions like these may become important soon, when deciding on the architecture of future Seraphis and Jamtis wallets

There may be wallets around with so many outputs that you can't read them in all at once.

and need a true DB to manage

at least not with decent performance

< Mochi101> dsc_, the mobile wallets need to cache older txs to disk or something... only keep the last 50 or so in memory <== the retrieval of transactions is fast, the rendering is what makes it slow

yes... I imagine that in the future... hopefully there will be wallets with 100's of thousands of txs in them.

ah I see dsc_

Then they need to stop trying to render all of them.

exactly :P

dsc_, will you work for cake?

its like the Twitter mobile app trying to render your feed from when you created your account

"the retrieval of transactions is fast" Well, up to a certain point. Early Monero daemons also loaded the whole blockchain into RAM when they started!

chocolate, vanilla, something special like tres leches... which do you prefer dsc_ ?

rbrunner: there is a libwallet function to retreive an array of Tx's, i think that one is quite fast

Mochi101: I worked on Cake quite a bit to make cake-tech/cake_wallet #362

but I dont think they can afford me

ahhh....wownero

dsc_: Yes of course, it's an array kept in RAM by wallet2 anyway

rbrunner: ah ok

The problem is e.g. wallet opening and saving if you get into really large numbers of outputs

rbrunner: in database land, you'd get a cursor to loop results

E.g. after Mochi101 took over Macao

rbrunner: :p

Exactly

Trouble is, using a DB is way overkill for 99% or even 99.9% of all wallets in existence ...

right, if someone has such a large wallet i assume they also have a couple gb ram for their wallet

It's a bit like the transaction pool in the daemon that *does* use a db for less than a couple hundred waiting txs 99.9% of the time :)

rbrunner, macao?

Ah, come on, biggest gambling paradise on Earth, I think bigger than Vegas

selsta, a normal user with 5-10 years of tx history will likely run into problems.

monero.win is tiny

FBI! FBI!

it's just a game

:D

Mochi101: but you don't run into any problems ram wise, right?

mobile wallets drawing the full tx history at once is a different topic

selsta, tbh I've never really investigated into what's really going on.

cake is using 350mb

So... no

and now it's unresponsive

you are using monero too hard

That is called "demo effect"

Well known among devs

won't even get past the pin screen after sending it to the background to check ram usage and returning

a51?

The FBI downloads your wallet right now :)

Yes dsc_ Samsung A51

i think the only thing you can do is create an issue on their github

yeah

I will do it for both projects.

You think I should use monero more lightly dsc_ ?

you're out of control dude...

:D

Using Monero over it's maximum allowed velocity!

I may be addicted...

Is there a Monero help line?

but selsta has a point, these are extraordinary requirements. it should get fixed eventually, but also note you are a heavy user

and since we are dealing with free software, yeah.. things may take a while

As you see, I'm not making a massive deal about it. Not like I did with the locked_tx thing... hehehehe

That was fun.