Project Decorum - Wallet Release

[oetyng]

Finally sat down with new browser.
@Seneca, what a great contribution!
The token protocol is very interesting.

Btw, I played around transferring between two wallets, and it took ~10s before a balance was updated.
After about 5 rounds back and forth, I was up at ~20s
8 rounds, ~29s
9, ~32s
11 ~37s

Going back to the topic linked by @anon40790172 I found this:

@Seneca

If there’s a history of 10K transaction to validate, that’s 3 MB of data. To prevent having to download them one by one which would be incredibly slow, the sender of the transaction could send a list of all addresses of the transaction history rather than just the address of the last one. That list would in this case be 320 KB. Now the recipient can start downloading them in parallel and then verify them.

There’d be 10K signatures to verify. I read in a paper that a 2010 Intel Xeon quadcore CPU that’s now a little over a hundred dollars can verify 71K Ed25519 signatures per second. Even if you have an outdated desktop CPU, verifying those 10K signatures likely won’t take longer than a second, assuming optimised software.

So I’m not worried about this, even with hundreds of thousands or even millions of transactions to verify in the very distant future (when computing will be even faster), I don’t think verification will need to take longer than 5-10 seconds. Computing speed increases may very well outpace transaction history growth.

Great stuff!
So, I guess this list is not sent now, and we’re doing a sequential download of transactions currently?
Is this still the solution you’re planning?