Base

At Blocky, we think about trust as infrastructure you can provision - like an EC2 instance.

There are many ways to provision trust, each with trade-offs. Those trade-offs determine which flavor of trust is best for different use cases.

Care to join me for a quick walk & talk on trust models? 🧵

Building the next layer/Posting hot takes from the grind.  Get in Builder, we're doing #truststuff

A key driver of Web2 was the ability to quickly provision compute resources for applications (storage & messaging too, but let’s simplify).

In Web3, a key driver is the ability to provision trust - just like compute.

Each flavor of trust has unique properties that shape its strengths & weaknesses:

PoW/PoS - Best-in-class guarantees, poor performance, slow provisioning

ZKPs - Highly accessible, good performance, fast provisioning

Restaking - Good performance, decent provisioning, immature

TEEs - Extremely performant, best provisioning, physically centralized

Let’s break it down:

Industry terms like PoW or ZKPs describe a mechanism for how trust is achieved - the root being either through consensus, cryptography, or isolation.

(Simplifying a bit again, but this should help illustrate how different flavors of trust exist.)

There are several methods for provisioning trust, but they all stem from a few core categories:

*Proof of Work (PoW) - consensus
*Proof of Stake (PoS) - consensus
*Zero-Knowledge Proofs (ZKPs) - cryptography
*Restaking - consensus
*Trusted Execution Environments (TEEs) - isolation