1/ "Zero trust" is a term that is growing fast in popularity, with mindshare growing faster (per Google trends) than "decentralization" and "self custody", two main pillars of crypto.
Why crypto need to refocus on capability, over blind emphasis on decentralization or verifiability.
All technological progress are defined by the capabilities unlocked.
For crypto: - Censorship-resistant money (and store of value) was the first capability unlock. - Permissionless asset creation and finance was the second capability unlock.
Notice the theme: censorship resistance and permissionless-ness, which are security features enabled by decentralization, were critical to these first two unlocks-- - Bitcoin would not be what it is if not for its self-custodial property and censorship resistance. - Ethereum would not have been what it is without ICO and defi summer, which were enabled by permissionless smart contracts.
Over the last few years, crypto got sidetracked and started to value decentralization, security, and verifiability without specific capability unlocks. Examples: decentralization theater (early forms of onchain AI), adding verifiability without specific purpose ("zk-everything").
I believe our the industry is finally exiting this sidetrack.
Example: If an app requires real-time censorship resistance, then decentralize. No need for real-time censorship resistance? Let's use a centralized sequencer but offer self-custodial guarantee via validity proofs.
Privacy is the last hurdle to mass-adoption of onchain finance. Can we simply add self-sovereign privacy to today's onchain finance and expect everything to work better?
The answer is no. We must make hard decisions on trade-offs between the following three desirable properties:
1. Maximally useful: no transaction limits, supports private payments and anonymous DeFi 2. Self-sovereign privacy: contents of private transactions cannot be revealed without consent from involved individuals 3. Threat resistant: adversaries cannot use it to hack & launder funds
If an L1 enforces censorship after a large hack, then why not go all the way to implement in-protocol mechanisms to enforce social consensus so that any consensus hack can be reverted?
In the end-state a chain is either a neutral base layer or a social consensus engine.
Theory crafting: SoV assets need *stability* of cashflow/REV, rather than the lack of it. =========== If BTC (or Gold) started to generate cashflow, it won't stop being a SoV asset, at least right away.
But, if this cashflow ever decrease, the valuation would drop in response.
Plus, markets may over-index on cashflow falling: a SoV asset with falling cashflow is less appealing than another SoV whose cashflow is not falling (could be due to it being zero).
Compound that with the fact that SoV relies on network effects, which means that relative marketshare movements could get amplified (a winning SoV can win harder). =========== In upshot, the downside of cashflow/REV for a SOV asset is that it makes the asset less appealing when cashflow falls.
Therefore, what's really important for SoV assets is the *stability* of cashflow/REV, rather than the lack of it.
(All of this is mostly empty speculation from first principles and not backed by any real data btw. So take it with a grain of salt.)
Theory crafting: SoV assets require *stability* of their cashflow/REV, rather than the lack of it. =========== If BTC (or Gold) started to generate cashflow, it won't stop being a SoV asset, at least right away.
But, if this cashflow ever decrease, the valuation would drop in response.
Plus, markets may over-index on cashflow falling: a SoV asset with falling cashflow is less appealing than another SoV whose cashflow is not falling (could be due to it being zero).
Compounds that with the fact that SoV relies on network effects, which means that relative marketshare movements could get amplified (a winning SoV can win harder). =========== In upshot, the downside of cashflow/REV for a SOV asset is that it makes the asset less appealing when cashflow falls.
Therefore, what's really important for SoV assets is the *stability* of cashflow/REV, rather than the lack of it.
(All of this is mostly empty speculation from first principles and not backed by any real data btw. So take it with a grain of salt.)
Theory crafting: SoV assets requires *stability* of their cashflow/REV, rather than the lack of it. =========== If BTC (or Gold) started to generate cashflow, it won't stop being a SoV asset, at least right away.
But, if this cashflow ever decrease, the valuation would drop in response.
Plus, markets may over-index on cashflow falling: a SoV asset with falling cashflow is less appealing than another SoV whose cashflow is not falling (could be due to it being zero).
Compounds that with the fact that SoV relies on network effects, which means that relative marketshare movements could get amplified (a winning SoV can win harder). =========== In upshot, the downside of cashflow/REV for a SOV asset is that it makes the asset less appealing when cashflow falls.
Therefore, what's really important for SoV assets is the *stability* of cashflow/REV, rather than the lack of it.
(All of this is mostly empty speculation from first principles and not backed by any real data btw. So take it with a grain of salt.)
You don't need a single composable state machine to have a coherent ecosystem, i.e. send to and receive from any address and interact with any app seamlessly.
It was never about single chain vs. multi chain.
However, seamless interoperability and network effects will win.
Recommend no more news like "latency = xx ms", for the sake of the people, our industry (and your business).
Instead, quantity what type of latency: - block/slot time - inclusion or execution confirmation latency - write-to-availability-of-effect latency - network latency - ...
Takeaways from zkSummit13: 1. War of zkVMs is still heating up. More new entrants & upgrades/redesigns will shake up the performance landscape. 2. VC attendance/attention on ZK has bottomed--someone (half jokingly) told me after the summit that I was the only VC in attendance (and they are not wrong). 3. Attention and stakes are moving up the stack: the zeitgeist is that the ZK adoption is no longer bottlenecked on cost or dev overhead, but onboarding more apps.
Some more subjective notes: - Attention on proving delay (real-time proving for Eth L1) will shift back to proving cost overhead (kappa). - We need more product-led companies building features with ZK (like Google wallet leveraging ZK for identity) - We are more likely to see de facto standards in ZK than de jure standards as progress is simply too fast.