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.