Forget what I said about get_outputs_distributions.bin, I didn't realize I was testing on stagenet

On mainnet it's worse: 1.08 MB for the call and not as compressible

How cacheable is this data? Maybe that's a better approach.

tobtoht_, is that the function that gets a bunch of random inputs from the blockchain to create the ringsig?

gingeropolous: No, I believe that is get_outs.bin which only amounts to about 12-13KB

The indexes/outputs we ask from the daemon are based on the output distribution.

We ask the entire output distribution from block 0 each time we construct a transaction. But I would imagine most if not all the time the data remains static except for the any new blocks that were added since we last requested it.

or a re-org

Naive caching would only request data that we don't already have. (i.e. first block we don't have till current height). But this introduces a fingerprintable vector.

but, i don't think that would do much. if you're already unsyncd, it would catch that

But I guess it could be binned. Request the full data once. Then only the last, say, 100k blocks on subsequent calls.

so then you'd be binned as a user that hasn't been online for n bins of 100k blocks

?

Not if you request the full data on wallet startup, and cache that. Then ask for the latest blocks only when constructing a transaction.

"on wallet startup" might introduce some other metadata leak though, I'm not sure.

Although I'd argue that you ought to run your own node if this is within your threat model.

xiphon xiphon_me which branch of the gui wallet has one click qr scanning? I'd like to build it myself

Never mind it's in main. Do you guys know when the new version of the gui will be released officially?

Do you think that you are too intelligent to be in a cult? Then I would encourage you to look into how any other cult works. They aren't populated by stupid people. Aum Shinrikyo was almost exclusively university professors and graduates. For Pete's sake - they had the know-how and means to make WMDs.

As to Monero, I would encourage you to look at Jonestown mass-suicide. You know why Jones killed them all? Because he was afraid he is loosing control over them. People like that will burn everything around them rather than give up control. Being smart doesn't make you immune to being in a cult. This is the most valuable lesson Monero taught me.

anon_udxf6fdz[m]: "Do you guys know when the new version of the gui will be released officially?" -> no ETA yet AFAIK

approximately how many ms does it take to look up a single output for verification, cheap SSD

not looking for anything exact, just a rough estimate/range

If only one of you gave Papa ChooChoo some TLC when I wrote a faster miner, instead of ignoring him, things could have happened differently np.reddit.com/r/Monero/comments/5lsfgt/_/dbz0jnp

Are you looking to multiply this number of the number of outputs in a ring ?

moneromooo: yeah, the intent is trying to get rough verification times for different ringsizes

I have the numbers for clsag and triptych but that doesn't include output lookups

Outputs are lookedup in batches, across txes (when syncing).

You could add a log right at "gather all the output keys" and one after the code fragment that follows, at "now generate a table for each tx_prefix and k_image hashes".

Then check the elapsed time from the log timestamps. Also log how many outputs were looked up. Divide.

The number of outputs will be the sum of all offset_map[amount] for all amounts.

Typically there'll be just one amount, 0 (for ringct outs).

It'll depend a lot of what parts of this are cached in RAM though.

how does the daemon handle what outputs to keep in RAM right now?

It does not.

The OS deals with it.

I can tell you why you can't stop the 'spam'. You are thinking in cult doctrine. If it was real spam, and I was selling Viagra for example - you could easily ban keywords and urls. Instead, stop being a sheep, think like a cult leader. Recoginse that this 'spam' is just some bullshit that you tell to the sheep.

When you do that, solution will present itself. Observe. 'spam' -> 'FUK talks bad things about Monero on our IRC' (Don't say that out loud obviously, that will get you excommunicated) Solution? Get off-the-shelf sentiment analyser, detect anyone who 'talks bad things about Monero' and ban them.

how long can a transaction stay in the mempool? and what happens if never confirmed?

It can stay indefinitely in theory. monerod will kick it after a day though, or a week if it was ever in a (reorg'd) block.

oh good thanks