4 ms·
1) Actually, removing as much risk as possible, limiting risk to a small subset of wealth, at the expense of latency in some cases, is a perfect solution here (
by rdl 14y ago
1) Actually, removing as much risk as possible, limiting risk to a small subset of wealth, at the expense of latency in some cases, is a perfect solution here (I'm not charging $1k/yr yet...). Coinbase presumably has a certain amount of risk they'll cover internally, and some level they can't or won't cover, so making sure the worst case breach doesn't exceed their risk tolerance is necessary and brilliant.
Any insurer would require a solution like this, on top of any other audit and control measures. The only weakness with the system as it stands now is documentation (which the blog post accomplishes, to some extent) -- the next step is to develop legal and technical measures (possibly using threshold cryptography, HSMs, etc., as well as multiple contracted parties like law firms, escrow agents, etc.) to enforce the fundamental principle of reducing value at risk to a reasonable level.
2) Please give me an example of ANYTHING the military, banking, or smart grids has solved "elegantly", especially in security. Elegance is the opposite of how those industries work -- they solve things with brute force.
3) This solution is elegant in that it's a simple hack and accomplishes the goals using the resources available.
It's not a general solution to the computer security problem, but took advantage of a compromise (latency) they could make.
CAs, for a long time, actually did a lot of work using laptops stored in bank vaults, rather than HSMs, since there was no good way to run all the code they needed in-HSM, or they needed to use kinds of keys not supported in HSM. Later, they bought HSMs for the keys themselves (mainly to do multi-party access control), and kept the laptop too.