Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More →
Taiko ZK-EVM: Inheriting Layer 1 Security
Dave | d1onys1us
Developer Experience @ Taiko Labs
Topics
- Defining security
- Taiko overview
- Where should users be careful
- How can we improve user security
Defining security
- User centric definition:
- Failing to meet the trust assumptions about the system
- What is trustless and trust-minimized
- Bounded to a domain
Background to Taiko
- A decentralized Ethereum-equivalent ZK-Rollup
- Community ZK-EVM effort
- Released an alpha-1 testnet, alpha-2 coming soon 👀
What's inherited from Ethereum
- Ethereum architecture
- Execution clients
- Gas costs, state trees, hashes, etc.
- Validity rules
- Consensus and data availability
- Decentralization and open source
- A platform for building (eg. the bridge)
Taiko protocol walkthrough
Proposing
Proving
Verifying
Constructing the rollup state
Where should users be careful
Where should users be careful
- Placing trust
- Bridges
- Permissioned override / upgrade
- Correctness
- Bug in proof system
- Bug in the client
- Smart contract behavior
- Rollup context differences
- L2 nodes are a new actor
- Liveliness of chain
How can we improve user security
How can we improve user security
- Staying user centric
- Easy to use tools
- Education
- Do it themself
- Governance
- Diversity and collaboration
- Diversity in implementation (eg. multi-proof, multi-client)
- Collaboration on neutral interfaces (eg. L2Beat)
Thank you
Taiko ZK-EVM: Inheriting Layer 1 Security Dave | d1onys1us Developer Experience @ Taiko Labs
{"metaMigratedAt":"2023-06-17T22:21:41.454Z","metaMigratedFrom":"YAML","title":"Taiko ZK-EVM: Inheriting Layer 1 Security","breaks":true,"description":"Taiko talk on security","contributors":"[{\"id\":\"2435332b-f6a2-41d6-a459-c558af9bc6e3\",\"add\":2922,\"del\":10}]"}