Reduce scan times with 1-byte-per-output 'view tag' #73
Comments
|
This is a neat idea, and I don't perceive any information leaks as long as the protocol enforces view key tags on all transactions. |
|
I wrote up a basic timing test on this branch to examine the time savings from view tags and compare to the current scan functionality. Here's a plot showing the average scan time per output as a function of tag size, on a particular test machine: |
|
Note: 2-out tx may get a bigger reduction in scan times from view tags, since they only (in practice) have 1 tx pub key so you normally only compute |
|
To be clear, the linked code does not assume anything about transaction structure, and only examines outputs as separate discrete units with their own key derivation computations. Plot data was computed using the timing results from this code, not from any particular chain data. |
Yes, similar concepts 1, 2 have been suggested before, but they harmed privacy. The difference here is that the tag (or grouping) is coming from the shared secret and thus doesn't leak anything that could be used for fingerprinting AFAICT. Thus, this is a great enhancement of the general idea. |
|
This seems like the easiest trade ever. |
|
Forgive me if this is a dumb suggestion but what about adding 2 bytes? Seems like a 1/256 vs 1/65536 is a pretty good tradeoff before going into the diminishing returns field. |
|
This is... absolutely amazing, and no idea how it's been overlooked for so long. Would gladly donate 5XMR to anyone who can get this accepted as a PR into the Monero codebase. |
|
I've opened a bounty for the implementation of this idea as well, that anyone can freely donate to to incentivize and fund the work required here: https://bounties.monero.social/posts/28/implement-view-tags-to-decrease-wallet-sync-times-in-monero |
|
@aitorpazos At 256 bits you can at most gain 1/256 = 0.4%, which is basically meaningless. I have a working demo of view tags in my Seraphis PoC branch. |
|
Hey all.. this is awesome and we just donated 10 XMR to the bounty bringing it up to 15.2 XMR. Lets get this one done! UkoeHB's contributions to Monero are endless! |
|
so when/how does this get done? |
Someone jumps in and proposes the code that implements this, and we include it in the upcoming hard fork for usage! Just need someone to step in and write the code, then people to review it before inclusion. The concept seems sound enough to implement at this point, and there are no real drawbacks. |
|
In to take this, commented on the bounty :) Shooting for PR within ~4 weeks |
OJ coming through. (OJ as in "other Justin") 😉 |
Implements view tags as proposed by @UkoeHB in MRL issue monero-project/research-lab#73 At tx construction, the sender adds a 1-byte view tag to each output. The view tag is derived from the sender-receiver shared secret. When scanning for outputs, the receiver can check the view tag for a match, in order to reduce scanning time. When the view tag does not match, the wallet avoids the more expensive EC operations when deriving the output public key using the shared secret.
Implements view tags as proposed by @UkoeHB in MRL issue monero-project/research-lab#73 At tx construction, the sender adds a 1-byte view tag to each output. The view tag is derived from the sender-receiver shared secret. When scanning for outputs, the receiver can check the view tag for a match, in order to reduce scanning time. When the view tag does not match, the wallet avoids the more expensive EC operations when deriving the output public key using the shared secret.
It seems important to speed up scan times, especially with Janus (Issue #62) potentially increasing scan times, and as transaction volume has started to rise. I think we can easily reduce scanning by around 50-70% with 1 additional byte per output, call it the 'view tag’, a reduction even taking into account Janus.
The principle is simple (and has likely been suggested before), make a shared secret between the sender and receiver, hash it, then record the first 1 byte in the chain (the view tag). Recipients calculate the shared secret, hash it, and check if it matches any view tags in the tx. If it does match, then continue checking for owned outputs in the normal way. It will only match about 1/256 of the time, so scan time will be primarily a function of checking view tags.
The shared secret has to be the normal one calculated, e.g. r*K^v, since there is no easy way around the subaddress problem. The view tag hash should be domain separated from the so-called ‘derivation to scalar’ used in one-time addresses, to avoid leaking any part of it on-chain. An easy way to do this, and to more generally insert view tags into the scanning process, is to just hash the derivation to scalar a second time, then compare it to the corresponding output's view tag. If it matches, continue with the checking procedure, if not skip to the next output.
Currently, to check a normal 2-output transaction (they basically all have 1 transaction public key), it takes these EC operations: 1 scalar-mult-key (shared secret with tx pub key), 2 scalar-mult-base (derivation to scalar times G, one for each output), 2 ec subtractions (each one-time key minus the H(rKv,t)*G). See derive_subaddress_public_key() and ZtM2 sections 4.2-4.3. Five EC operations.
With Janus, it will take: 2 scalar-mult-key (shared secrets for each tx pub key), 2 scalar-mult-base (derivation to scalar times G, one for each output), 2 ec subtractions (each one-time key minus the H(rKv,t)*G). See Issue #62. Six EC operations.
With Janus and view tag it will take (in 255/256 cases): 2 scalar-mult-key (shared secrets for each tx pub key). Two EC operations.
The average output count recently (excluding miner tx) is around 2.2 per tx, so an average 50-70% reduction in scan time per tx seems reasonable. I’d say 50% is a very conservative estimate.
My recommendation is to roll this out in a hard fork alongside Janus, and in that hard fork reorganize the transaction structure to remove a lot of stuff from the tx extra field (there has been recent discussion around this). In other words, put the Janus base key, the tx pub keys (one per output), and the view tags (one per output), in the transaction structure (and possibly the encrypted payment ID).
The text was updated successfully, but these errors were encountered: