This kind of seems to me like barking up an unnecessary tree, but maybe as
part of making a case for this type of analysis, a point of comparison
could be made against a process that is a little more tangible for a human.
Instead of simply comparing the compute between the cryptographic
operations for different flavors of credential verification, perhaps you
could also compare to the amount of compute needed to do an everyday task
like load a webpage for a news article from a local newspaper website with
no ad-blocker enabled.
I am not quite an expert at reading the type of chart that comes out of the
profiling tools in the browser, but there's a heck of a lot of compute
involved in doing the sort of operation that a user might do hundreds of
times in a day. I'd expect that any of the cryptographic operations
involved in operating on a credential would be a lot smaller than what's
involved in loading a webpage. I tried it out real quick, and it took about
3 seconds of pretty brightly lit up CPU before the page settled down and I
could start reading an article.
[image: Screenshot 2023-09-08 at 2.13.26 PM.png]
*Nate Otto*
nate@ottonomy.net
Founder, Skybridge Skills
he/him/his
