Upload 4 files
Browse files- config.json +23 -0
- eigen_vectors.csv +0 -0
- eigenlayerKannan.snapshot.tar.gz +3 -0
- eigenraw.csv +2064 -0
config.json
ADDED
@@ -0,0 +1,23 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
{
|
2 |
+
"address": "0x68a3606a0397ac83622c1f98c13760956dd8e2d8",
|
3 |
+
"chat": "https://huggingface.co/gaianet/Meta-Llama-3.1-8B-Instruct-GGUF/resolve/main/Meta-Llama-3.1-8B-Instruct-Q5_K_M.gguf",
|
4 |
+
"chat_batch_size": "128",
|
5 |
+
"chat_ctx_size": "8096",
|
6 |
+
"chat_name": "Llama-3-8B-Instruct",
|
7 |
+
"description": "Llama-3.1-8B-Instruct",
|
8 |
+
"domain": "gaianet.network",
|
9 |
+
"embedding": "https://huggingface.co/gaianet/Nomic-embed-text-v1.5-Embedding-GGUF/resolve/main/nomic-embed-text-v1.5.f16.gguf",
|
10 |
+
"embedding_batch_size": "8192",
|
11 |
+
"embedding_collection_name": "default",
|
12 |
+
"embedding_ctx_size": "8192",
|
13 |
+
"embedding_name": "nomic-embed-text-v1.5",
|
14 |
+
"llamaedge_port": "8080",
|
15 |
+
"prompt_template": "llama-3-chat",
|
16 |
+
"qdrant_limit": "1",
|
17 |
+
"qdrant_score_threshold": "0.5",
|
18 |
+
"rag_policy": "system-message",
|
19 |
+
"rag_prompt": "Use the following pieces of context to answer the user's question.\n----------------\n",
|
20 |
+
"reverse_prompt": "",
|
21 |
+
"snapshot": "https://huggingface.co/datasets/gaianet/diplo/resolve/main/diplo-v2.snapshot",
|
22 |
+
"system_prompt": "You are Diplo, a famous DJ./n You are the guest of Gaia Launch Party on Sep 19th./n You are a co-creator and lead member of the electronic dancehall music project Major Lazer; a member of the supergroup LSD, with Labrinth and Sia; a member of electronic duo Jack Ü, with producer and DJ Skrillex; and a member of Silk City, with Mark Ronson. You founded the record company Mad Decent in 2006, as well as the non-profit organization Heaps Decent the following year. Your 2013 extended play (EP), Revolution, debuted at number 68 on the US Billboard 200. The EP's title track was later featured in a commercial for Hyundai and is featured on the WWE 2K16 soundtrack./n You also know a lot about Gaia and blockchain."
|
23 |
+
}
|
eigen_vectors.csv
ADDED
The diff for this file is too large to render.
See raw diff
|
|
eigenlayerKannan.snapshot.tar.gz
ADDED
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
1 |
+
version https://git-lfs.github.com/spec/v1
|
2 |
+
oid sha256:f3a5b4be38255c81e40aa8ff695d23f639cabbfee2891eec1dd598ed4303ffca
|
3 |
+
size 1574201
|
eigenraw.csv
ADDED
@@ -0,0 +1,2064 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
"## Speaking style of Sreeram Kannan
|
2 |
+
## Speech pattern of Sreeram Kannan
|
3 |
+
uh good morning everybody Welcome to The
|
4 |
+
reaking Summit it's my uh real pleasure
|
5 |
+
to welcome you all here uh I'm sham uh I
|
6 |
+
started this uh Ian layer project you
|
7 |
+
know two and a half years back and it
|
8 |
+
has been uh really exciting for us to
|
9 |
+
see all the progress from there um what
|
10 |
+
I'm going to do in today's uh talk is
|
11 |
+
try to set the context for why we doing
|
12 |
+
what we're doing what is our vision for
|
13 |
+
what we want to build and how we can all
|
14 |
+
partake in actually
|
15 |
+
okay um how we can all work together in
|
16 |
+
actually making this happen um as you
|
17 |
+
can see the subtitle of this talk is the
|
18 |
+
coordination engine for open Innovation
|
19 |
+
um really this is where uh I want to
|
20 |
+
give a little bit of uh orientation
|
21 |
+
around this uh title um to start with uh
|
22 |
+
you know if you think about it if you
|
23 |
+
zoom out there are only certain kind
|
24 |
+
kind of positive some games what's a
|
25 |
+
positivism game you know when we're
|
26 |
+
engaging in Collective action certain
|
27 |
+
kinds of games are win- win or positive
|
28 |
+
sum so that there's a net positive
|
29 |
+
created out of these games and if you
|
30 |
+
think about it fundamentally there are
|
31 |
+
only two kinds of prototypical postive
|
32 |
+
sum games number one is innovation
|
33 |
+
Innovation is when you take something
|
34 |
+
and make a resource out of a
|
35 |
+
non-resource right you can take air and
|
36 |
+
you make spectr from you take oil you
|
37 |
+
make energy you take sand and you make
|
38 |
+
silicon like these are innovations that
|
39 |
+
transform like one kind of a resource to
|
40 |
+
another you know a non-resource into a
|
41 |
+
resource really um highly positive for
|
42 |
+
everybody and Innovation is also like
|
43 |
+
this that if I have an idea and you have
|
44 |
+
an idea and we exchange it both of us
|
45 |
+
have two ideas clearly positive sum
|
46 |
+
unlike other resources which are finite
|
47 |
+
and you cannot create more of so
|
48 |
+
Innovation is one stere typical
|
49 |
+
prototypical or postive some game
|
50 |
+
there's another one which is also very
|
51 |
+
powerful coordination coordination is
|
52 |
+
when many parties come together and
|
53 |
+
create something which is greater than
|
54 |
+
the sum of the parts right if they work
|
55 |
+
together if we all work together we can
|
56 |
+
do something which is much bigger than
|
57 |
+
what we can all do just going our own
|
58 |
+
separate ways um and if you look at
|
59 |
+
these two different types of posm games
|
60 |
+
there's Echo of this structure
|
61 |
+
everywhere that you look you know in
|
62 |
+
working systems so you can think of like
|
63 |
+
you know these two structures interlay
|
64 |
+
and work together with each other in
|
65 |
+
very powerful ways in different examples
|
66 |
+
um and one example is let's say you know
|
67 |
+
you take a country like the United
|
68 |
+
States um on the you know or any you
|
69 |
+
know successful country for that matter
|
70 |
+
you'd see that basically the government
|
71 |
+
acts as like a coordinatEigenLayer on top
|
72 |
+
of which there is a free market a
|
73 |
+
competitive economy which can be built
|
74 |
+
on top of it which is you know akin to
|
75 |
+
open
|
76 |
+
Innovation and what we're aspiring to
|
77 |
+
here is for to to do this for digital
|
78 |
+
platforms essentially
|
79 |
+
coordination
|
80 |
+
via bringing decentralized trust who
|
81 |
+
brings trust you know trust trust is
|
82 |
+
created through like this decentralized
|
83 |
+
Collective you know in our vision
|
84 |
+
ethereum and EigenLayer work together to
|
85 |
+
actually create this on top of which
|
86 |
+
anybody can build arbitrary new digital
|
87 |
+
platforms which can compose with each
|
88 |
+
other and you know in our in our
|
89 |
+
ecosystem we call this AVS you know
|
90 |
+
actively validated services or you can
|
91 |
+
also think of these as uh like a
|
92 |
+
decentralized version of software as a
|
93 |
+
service that we um we see in the cloud
|
94 |
+
okay before I go in into explaining uh
|
95 |
+
you know what all we can do with this
|
96 |
+
kind of a platform I'm going to start
|
97 |
+
with the basics like for some of you who
|
98 |
+
may not be aware uh just a couple of
|
99 |
+
minutes so I in I lay what we do is we
|
100 |
+
bring together a variety of parties so I
|
101 |
+
mentioned being a coordinatEigenLayer
|
102 |
+
what does it mean to be a coordination
|
103 |
+
layer you need to bring together
|
104 |
+
different kinds of parties that work
|
105 |
+
together to actually achieve a certain
|
106 |
+
goal and in our case uh it is
|
107 |
+
mainly the first side of this is stakers
|
108 |
+
so what happens is in ethereum right
|
109 |
+
what you do is you go and stake your e
|
110 |
+
stake your e what does it mean to stake
|
111 |
+
your e you put it into a contract and
|
112 |
+
then make a promise that you will hold
|
113 |
+
to the conditions and the Covenant of
|
114 |
+
the ethereum protocol what EigenLayer
|
115 |
+
does is to make
|
116 |
+
this much more expansive so we call this
|
117 |
+
reaking reaking is you stake your wreath
|
118 |
+
and then you're adding on a additional
|
119 |
+
conditions taking on additional
|
120 |
+
covenants making additional promises uh
|
121 |
+
that's what you you know it's now
|
122 |
+
popularly called reaking in fact we're
|
123 |
+
calling this the reaking summit but if
|
124 |
+
you want to be really precise you would
|
125 |
+
call it permissionless programmable
|
126 |
+
staking that's really what it is what do
|
127 |
+
I mean by that so you take the e that's
|
128 |
+
staked in ethereum and then subject
|
129 |
+
yourself to additional programmable sets
|
130 |
+
of
|
131 |
+
conditions so when you take it into I
|
132 |
+
layer you're basically saying hey I'm
|
133 |
+
going to run any kinds of new middleware
|
134 |
+
Services actively validated Services
|
135 |
+
whatever you want to call it but
|
136 |
+
essentially what what you're doing is
|
137 |
+
you're saying hey I'm I'm taking my eat
|
138 |
+
and normally when I'm staking I'm
|
139 |
+
promising that I'm running the ethereum
|
140 |
+
protocol correctly but now I'm going to
|
141 |
+
promise that I run all these Services
|
142 |
+
correctly okay um and when somebody
|
143 |
+
wants to build an ABS essentially
|
144 |
+
they're talking we're talking about
|
145 |
+
building two things
|
146 |
+
number one they can build arbitrary
|
147 |
+
software you know a container in which
|
148 |
+
they can house and deploy arbitary
|
149 |
+
software and a smart contract so I
|
150 |
+
itself is a smart contract in ethereum
|
151 |
+
but it allows anybody to build new smart
|
152 |
+
contracts that talk to the IG ler
|
153 |
+
contract any new middleware or AVS can
|
154 |
+
build a new smart contract that talks to
|
155 |
+
the a l contracts and this the AVS
|
156 |
+
contract can SP ify the payment
|
157 |
+
condition the slashing conditions and
|
158 |
+
the registration conditions who can
|
159 |
+
register how much do they get paid and
|
160 |
+
how much should they get slashed so
|
161 |
+
that's the overall structure of how you
|
162 |
+
build uh how we are able to use Aon
|
163 |
+
layer to actually take the underlying
|
164 |
+
decentralized trust from ethereum and
|
165 |
+
then Supply it to any kinds of new
|
166 |
+
middlewares or services that can then be
|
167 |
+
built on top you can think of this as
|
168 |
+
the kind of open InnovatEigenLayer
|
169 |
+
anybody can build these new new kinds of
|
170 |
+
services okay so in the last slide I
|
171 |
+
call this permissionless programmable
|
172 |
+
staking right why is it programmable
|
173 |
+
staking because you're staking and then
|
174 |
+
other people permissionless can create
|
175 |
+
these middlewares and services that can
|
176 |
+
consume your staking and then create new
|
177 |
+
kinds of services based on that so you
|
178 |
+
can think of Ian lir as being a paradigm
|
179 |
+
for programmable trust okay so you know
|
180 |
+
at the base of all of this we have the I
|
181 |
+
layer Shad security system they're
|
182 |
+
calling it you another way of thinking
|
183 |
+
about it is a Shad security system why
|
184 |
+
are we calling it Shad security the same
|
185 |
+
stake or the same pool of validators are
|
186 |
+
actually sharing that security to a
|
187 |
+
variety of different applications so
|
188 |
+
that's another like model for thinking
|
189 |
+
about this there are really two things
|
190 |
+
that power this Shad security system on
|
191 |
+
the one side we have the eat staking
|
192 |
+
people can stake eat and this provides a
|
193 |
+
certain amount of of Economic Security
|
194 |
+
Economic Security means if you know that
|
195 |
+
if your service is not run correctly you
|
196 |
+
you will be able to slash a certain
|
197 |
+
amount of
|
198 |
+
e there's also a certain amount of
|
199 |
+
decentralization you because you're
|
200 |
+
borrowing the same set of node operators
|
201 |
+
that you know run something like
|
202 |
+
ethereum you can borrow the
|
203 |
+
decentralization and this gives you a a
|
204 |
+
certain amount of collusion resistance
|
205 |
+
that these are distinct operators you
|
206 |
+
know neutral set which which is actually
|
207 |
+
participating to validate your service
|
208 |
+
so these are the two dimensions of
|
209 |
+
programmable trust that are uh created
|
210 |
+
from the I lay ecosystem and now what
|
211 |
+
can you do with this you can actually
|
212 |
+
start uh building a variety of different
|
213 |
+
things and one way to like root this
|
214 |
+
thing is to take an analogy from like
|
215 |
+
the pre crypto or the web2 world and you
|
216 |
+
know you can think of in the cloud
|
217 |
+
era the you know if if you think back to
|
218 |
+
1995 and you want to build an
|
219 |
+
application you have to build your own
|
220 |
+
like you know server stack you have to
|
221 |
+
build your own you know uh
|
222 |
+
authentication payments database
|
223 |
+
everything yourself as well as building
|
224 |
+
whatever application you want this is
|
225 |
+
what you would have done if you wanted
|
226 |
+
to do web application development in
|
227 |
+
1995 in 2023 that's not what you would
|
228 |
+
do you would go basically use a cloud
|
229 |
+
service you there is a bunch of software
|
230 |
+
as a service solutions SAS Solutions on
|
231 |
+
top like o like mongodb like um you know
|
232 |
+
stripe all these things and then you
|
233 |
+
know when you want to build an end user
|
234 |
+
application you just concatenate these
|
235 |
+
pieces correctly and then you can build
|
236 |
+
whatever application you want leading to
|
237 |
+
much higher velocity of innovation how
|
238 |
+
can we kind of see an echo of this in
|
239 |
+
the uh crypto
|
240 |
+
world so you know one can start thinking
|
241 |
+
about what kinds of you know the the
|
242 |
+
middlewares and avss the actively
|
243 |
+
validated services that can be built on
|
244 |
+
top of won layer as something Akin into
|
245 |
+
these SAS services and then end user
|
246 |
+
applications can then build on top of
|
247 |
+
these services so what I'll do next is
|
248 |
+
give you like a little bit of idea of
|
249 |
+
what kinds of services can be built on
|
250 |
+
top of wag so you can categorize them in
|
251 |
+
many different ways here are a few so
|
252 |
+
number one is rollup services like
|
253 |
+
categories of services so if you think
|
254 |
+
about the ethereum road map one of the
|
255 |
+
biggest things going on in the theum
|
256 |
+
road map is the rollup Centric road map
|
257 |
+
the idea that that is going going to be
|
258 |
+
lots of rollups these rollups offload
|
259 |
+
computation from ethereum and are able
|
260 |
+
to therefore scale the whole ethereum uh
|
261 |
+
stack and in the rollup era there's lots
|
262 |
+
of rollup adjacent services that you
|
263 |
+
know may be interesting and we're seeing
|
264 |
+
a bunch of them being built you know
|
265 |
+
we're building the first one ourselves
|
266 |
+
Igan da the data availability service
|
267 |
+
the way to think about this is when
|
268 |
+
you're offloading computation you still
|
269 |
+
need a place to publish the inputs and
|
270 |
+
outputs of said computation
|
271 |
+
you know if I publish the inputs and
|
272 |
+
outputs of the computation anybody else
|
273 |
+
can then verify that I'm doing the
|
274 |
+
computation correctly so that's called a
|
275 |
+
data availability or a data publishing
|
276 |
+
system we're building Igan da as a data
|
277 |
+
availability system on using IG layer
|
278 |
+
but there's lots of other rollup
|
279 |
+
services that we're seeing emerging in
|
280 |
+
uh on the I lay ecosystem for example uh
|
281 |
+
rollups have a single Central sequencer
|
282 |
+
which orders all the transactions can we
|
283 |
+
instead build a decentralized
|
284 |
+
sequencing infrastructure on top of Ian
|
285 |
+
layer rollups take a certain lag before
|
286 |
+
they settle onto ethereum you may want
|
287 |
+
faster Bridges and there's a variety of
|
288 |
+
different Bridges being built on Ian lir
|
289 |
+
when how to handle the me that occurs in
|
290 |
+
the um rollup ecosystem you may want to
|
291 |
+
build all kinds of interesting me
|
292 |
+
services for example I want to say build
|
293 |
+
an encrypted mol for a rollup so which
|
294 |
+
means you need a bunch of nodes these
|
295 |
+
node needs needs to participate in some
|
296 |
+
kind of threshold cryptography so that
|
297 |
+
when you send a transaction no one node
|
298 |
+
is able to actually see the transaction
|
299 |
+
it's encrypted but then after the
|
300 |
+
transaction is included then it you can
|
301 |
+
actually decrypt it so you can build me
|
302 |
+
services on EigenLayer and another
|
303 |
+
category that we've seen emerge is
|
304 |
+
watchtowers you know if you have not one
|
305 |
+
or two or three optimistic rollups but
|
306 |
+
thousands of optimistic rollups which is
|
307 |
+
there we going towards you have to make
|
308 |
+
sure that there are people who are
|
309 |
+
actually watching what's going on in
|
310 |
+
these rollups and trigger a fraud alert
|
311 |
+
or a fault alert when such a thing
|
312 |
+
happens you need a neutral set of nodes
|
313 |
+
to do this so again you know a new
|
314 |
+
category that we're seeing on
|
315 |
+
ier so this is rollup Services another
|
316 |
+
category which I I'm quite excited about
|
317 |
+
personally is the family of
|
318 |
+
co-processors how do you think about a
|
319 |
+
co-processor you're sitting on ethereum
|
320 |
+
and then let's say you want to run an AI
|
321 |
+
application and then get the output of
|
322 |
+
such AI application onto ethereum this
|
323 |
+
would be an example of a co-processor
|
324 |
+
you know you on ethereum you're in the
|
325 |
+
evm programming environment but I want
|
326 |
+
to access running all kinds of other
|
327 |
+
outputs you know maybe you want to run a
|
328 |
+
Linux machine uh and a program you know
|
329 |
+
for which you made a commitment and then
|
330 |
+
you want to say that hey if you run this
|
331 |
+
program then this is the output and then
|
332 |
+
bring it all back to ium to be an
|
333 |
+
example of a co-processor you want to
|
334 |
+
run a database a SQL query on a major
|
335 |
+
database and then you want to say the
|
336 |
+
inputs the outputs of said SQL query you
|
337 |
+
want to bring it back to ethereum you
|
338 |
+
want to run like a ZK service and then
|
339 |
+
you want to bring you know the outputs
|
340 |
+
of such cryptography all of these could
|
341 |
+
be examples of co-process we're seeing
|
342 |
+
many of these uh show up on ION
|
343 |
+
layer the next category is you know new
|
344 |
+
kinds of cryptographic methods um you
|
345 |
+
know I'll talk about the ioner service
|
346 |
+
which is a new uh service that we are
|
347 |
+
building later but there are things like
|
348 |
+
trusted execution environments I want to
|
349 |
+
run like a trusted execution environment
|
350 |
+
committee a trusted execution
|
351 |
+
environment is a hardware device which
|
352 |
+
has certain kinds of you know uh there
|
353 |
+
is a little bit of trust assumption in
|
354 |
+
the manufacturer like Intel and uh AMD
|
355 |
+
and and Android all of these different
|
356 |
+
Hardware manufacturers have different te
|
357 |
+
environments but you know to be able to
|
358 |
+
access te networks on you know on
|
359 |
+
ethereum is a very interesting use case
|
360 |
+
you know things like secret sharing I
|
361 |
+
want to take a secret and encode it and
|
362 |
+
send it through the network so that
|
363 |
+
nobody has access to the secret but it's
|
364 |
+
spread all through the network um you
|
365 |
+
know more more General version of that
|
366 |
+
is the secure multiparty computation or
|
367 |
+
you know fully homomorphic encryption
|
368 |
+
we're seeing all of these new categories
|
369 |
+
emerge on EigenLayer um there's also
|
370 |
+
other kinds of things that one can do um
|
371 |
+
you know bring proofs of various kinds
|
372 |
+
into uh the ethereum ecosystem what
|
373 |
+
kinds of proofs am I talking about
|
374 |
+
suppose you want to know like where a
|
375 |
+
node operator is located a prove of
|
376 |
+
location you may want to get uh an
|
377 |
+
attestation that basically promises what
|
378 |
+
the prove of location of a certain uh
|
379 |
+
node operator is and and one way to do
|
380 |
+
it is have a decentralized group of
|
381 |
+
nodes which ping each other through the
|
382 |
+
native peer-to-peer Network to actually
|
383 |
+
then figure out what the Ping latencies
|
384 |
+
are you you know there are systems like
|
385 |
+
this being built proof of mashhood which
|
386 |
+
is a new kind of idea from automata
|
387 |
+
which is basically the idea that I want
|
388 |
+
to know like how many distinct devices
|
389 |
+
that you know somebody is logging in
|
390 |
+
from a distinct machine a distinct Apple
|
391 |
+
phone or a distinct Android uh you want
|
392 |
+
to have proofs of identity I want to log
|
393 |
+
into a https server and then you know
|
394 |
+
get the authenticated certificate into
|
395 |
+
ethereum you know there's a bunch of
|
396 |
+
protocols like reclaim building this um
|
397 |
+
there's also you know so all these other
|
398 |
+
services are things you would want
|
399 |
+
irrespective of the fact that these are
|
400 |
+
particularly ethereum stakers right they
|
401 |
+
need a certain amount of Economic
|
402 |
+
Security they need a certain amount of
|
403 |
+
decentralization but there's also the
|
404 |
+
fact that because we're doing restating
|
405 |
+
of e it's the ethereum block proposal
|
406 |
+
that are participating in the ecosystem
|
407 |
+
and you can start doing interesting
|
408 |
+
things on the uh on the ethereum side
|
409 |
+
for example managing me on the ethereum
|
410 |
+
L1 you can start thinking about event
|
411 |
+
driven actions whenever certain sets of
|
412 |
+
things are triggered you have to
|
413 |
+
actually you know for example whenever
|
414 |
+
there's a liquidation then that
|
415 |
+
liquidation has to be taken and these
|
416 |
+
these kinds of event driven actions for
|
417 |
+
example improve the usability of these
|
418 |
+
platforms massively because you know
|
419 |
+
imagine that like you're running a def
|
420 |
+
platform and you need to calculate the
|
421 |
+
time to uh you know you need to
|
422 |
+
calculate how much over
|
423 |
+
collateralization you you need it's
|
424 |
+
basically the time to liquidation which
|
425 |
+
is actually determining the over
|
426 |
+
collateralization factor and by reducing
|
427 |
+
the time to liquidation you can actually
|
428 |
+
get very tight systems um another system
|
429 |
+
which is you know new newly proposed is
|
430 |
+
the idea of based sequencing where like
|
431 |
+
you know from Justin Drake the idea that
|
432 |
+
ethereum L1 itself can actually do uh
|
433 |
+
ordering transactions for rollups but
|
434 |
+
when you're doing that one of the things
|
435 |
+
you may want to do is how do you get
|
436 |
+
like fast pre-confirmation and if there
|
437 |
+
is ethereum Stak by the block proposers
|
438 |
+
on ethereum then and and they're restak
|
439 |
+
on agal then you could basically start
|
440 |
+
doing things like pre-confirmation they
|
441 |
+
make a certificate that hey I am going
|
442 |
+
to include your transaction and send it
|
443 |
+
to you right away in an instant and then
|
444 |
+
later if they don't they get slashed so
|
445 |
+
these are the different examples I this
|
446 |
+
is not an exhaustive list but the but
|
447 |
+
the types of things that we starting to
|
448 |
+
see on on Ion
|
449 |
+
lay and the way we think about it is the
|
450 |
+
systems that build natively on EigenLayer
|
451 |
+
are like the SAS Services which means
|
452 |
+
they are infrastructured pieces and end
|
453 |
+
user applications will then concatenate
|
454 |
+
a bunch of these pieces to actually
|
455 |
+
build usable applications and we talking
|
456 |
+
about how do you take crypto to a
|
457 |
+
billion users one of the things you have
|
458 |
+
to think about is what what set of like
|
459 |
+
functionalities do they need and that's
|
460 |
+
that's where we think that IG layer will
|
461 |
+
play a role is the core functionality
|
462 |
+
layer and then applications will just
|
463 |
+
mix and match these different pieces to
|
464 |
+
then get the end us of functionality
|
465 |
+
that you want okay so that's a brief
|
466 |
+
overview of what the scope of the
|
467 |
+
project is and we're talking about to be
|
468 |
+
the coordinatEigenLayer for open
|
469 |
+
Innovation this is really what we mean
|
470 |
+
many of these things we had no idea that
|
471 |
+
these could be done on EigenLayer so these
|
472 |
+
are all emergent you know lots of people
|
473 |
+
here have actually come up with many of
|
474 |
+
these different things and it's it's
|
475 |
+
amazing for us to just sit and see that
|
476 |
+
once you allow this coordinatEigenLayer
|
477 |
+
what all can then emerge out of
|
478 |
+
it okay
|
479 |
+
so um in the next couple of minutes what
|
480 |
+
I'll do is briefly touch upon what is
|
481 |
+
the fundamentals of the shad secur
|
482 |
+
system um when when people think about
|
483 |
+
reaking they're thinking about something
|
484 |
+
like hey I'm reusing the same e some
|
485 |
+
kind of Leverage or some other concept
|
486 |
+
and I just want to dispel some of these
|
487 |
+
myths here so what is the core
|
488 |
+
functionality of what is actually uh
|
489 |
+
what i l is actually doing the first
|
490 |
+
point is that Shad security is strictly
|
491 |
+
better what do I mean by that so let's
|
492 |
+
forget that we're reaking from ethereum
|
493 |
+
to EigenLayer let's just imagine that
|
494 |
+
inside I there's a certain amount of
|
495 |
+
each stake but it's supplied to all
|
496 |
+
these Services simultaneously right so
|
497 |
+
one way to think about it is let's say
|
498 |
+
you have $1 billion restak to 1,000
|
499 |
+
services this is One World another world
|
500 |
+
in which each service has $1 million
|
501 |
+
state which world is
|
502 |
+
better right to to attack anyone service
|
503 |
+
in the other world you just need one uh
|
504 |
+
1 million whereas to attack anyone
|
505 |
+
service B the the same pool is restak
|
506 |
+
across all these Services you need 1
|
507 |
+
billion Capital as an attacker to go and
|
508 |
+
attack any one service there is a
|
509 |
+
certain rigidity a certain hardening of
|
510 |
+
security when you pull security together
|
511 |
+
we see this all all through the place
|
512 |
+
right like this is why Nations
|
513 |
+
coordinate you know you don't have City
|
514 |
+
cities don't have armies Nations have
|
515 |
+
armies sometimes even like many nation
|
516 |
+
states coordinate to create alliances
|
517 |
+
that actually work together it's exactly
|
518 |
+
the same phenomenon Shad security is
|
519 |
+
strictly better
|
520 |
+
there is a little bit of downside in
|
521 |
+
that which is in if you had segregated
|
522 |
+
security you have something attributable
|
523 |
+
to yourself each service has that 1
|
524 |
+
million whereas in this you get a little
|
525 |
+
bit of mixing together of pooling which
|
526 |
+
is good but you know if you also wanted
|
527 |
+
attributable security what we're doing
|
528 |
+
in ier in in the upcoming version not in
|
529 |
+
the version that is already live and
|
530 |
+
launched uh but in the upcoming versions
|
531 |
+
we are working on a design where you can
|
532 |
+
also get attributable security what do I
|
533 |
+
mean by that you know if you have $1
|
534 |
+
billion stake there's potentially $1
|
535 |
+
billion to be slashed and some service
|
536 |
+
you know maybe there's a bridge which
|
537 |
+
says hey I'm very very security critical
|
538 |
+
you know if my service goes down or
|
539 |
+
something gets compromised I need at
|
540 |
+
least $100 million of insurance of the
|
541 |
+
slash uh portion so instead of taking
|
542 |
+
the slash portion right now what we do
|
543 |
+
is we just burn it like ethereum does in
|
544 |
+
our V2 what we'll do is we can actually
|
545 |
+
give you a portion of that slash funds
|
546 |
+
and the ability to buy this is called
|
547 |
+
insurance and you pre- buby it and now
|
548 |
+
you not only have the pooled security to
|
549 |
+
attack any one service you need to be
|
550 |
+
able to acquire the $1 billion of
|
551 |
+
capital but to if your service gets
|
552 |
+
attacked you you know how much you can
|
553 |
+
slash uniquely this this insurance is
|
554 |
+
not over provisioned so you it is always
|
555 |
+
guaranteed that you will be able to
|
556 |
+
slash that muchoney
|
557 |
+
so that's a superpower so you can both
|
558 |
+
get the benefits of pool security and
|
559 |
+
the benefit of attributable security you
|
560 |
+
can also start seeing that there are
|
561 |
+
economies of scale which is if you're if
|
562 |
+
you're using an application the
|
563 |
+
application is using several avss built
|
564 |
+
on EigenLayer then you can you don't have
|
565 |
+
to pay 5x if you're using five Services
|
566 |
+
then you don't have to buy insurance
|
567 |
+
separately for each of these five
|
568 |
+
Services you just buy insurance once on
|
569 |
+
igon lay so there is is an economy of
|
570 |
+
scale and then finally there is an
|
571 |
+
elastic scaling of security you know uh
|
572 |
+
Amazon's called ec2 elastic compute
|
573 |
+
right which is I don't know how much
|
574 |
+
compute I'm going to need I'm going to
|
575 |
+
go and buy it from a common pool and
|
576 |
+
there is randomness of how much compute
|
577 |
+
is needed by different people they go
|
578 |
+
and buy the portion of compute that they
|
579 |
+
want there is a similar phenomenon in
|
580 |
+
ier which is the elastic scaling of
|
581 |
+
security there is a large pool $1
|
582 |
+
billion or whatever amount totally
|
583 |
+
sitting as security
|
584 |
+
now whenever like a different Services
|
585 |
+
there are lots of different Services
|
586 |
+
each service needs a randomly varying
|
587 |
+
amount of security why because you know
|
588 |
+
I'm running an E2 USD bridge when
|
589 |
+
there's a E2 USD price volatility people
|
590 |
+
might want to use more of that there is
|
591 |
+
a BTC to Sol like Bridge or something
|
592 |
+
else also sitting on top of EigenLayer then
|
593 |
+
you want different amounts of security
|
594 |
+
for each of these across time and by
|
595 |
+
having a single layer through which you
|
596 |
+
can buy sh security actually make makes
|
597 |
+
it much better okay
|
598 |
+
so um what I'm going to do from here is
|
599 |
+
just go through the
|
600 |
+
um let me just uh run this through I'm
|
601 |
+
not going to talk about all these things
|
602 |
+
um I want to basically go here talk
|
603 |
+
about our timeline of what we building
|
604 |
+
and when we're going to deploy it
|
605 |
+
um
|
606 |
+
so the um right so the earlier we had
|
607 |
+
divided the EigenLayer launch road map
|
608 |
+
into three different stages and stage
|
609 |
+
one was stakers stage two was going to
|
610 |
+
be operators and stage three was going
|
611 |
+
to be services and instead we've rivid
|
612 |
+
it it now you know in our current launch
|
613 |
+
plan in a different way stage one which
|
614 |
+
is already live is EigenLayer staking
|
615 |
+
like you can restake your e natively or
|
616 |
+
using liquid staking tokens stage two
|
617 |
+
instead of only launching ing for you
|
618 |
+
know operators what we're trying to do
|
619 |
+
is we're going to launch the entire
|
620 |
+
ecosystem IG layer you can have stakers
|
621 |
+
there's operators people can launch
|
622 |
+
Services Igan da or data availability
|
623 |
+
service all of them will go live except
|
624 |
+
the economic part payments and slashing
|
625 |
+
except the economic part everybody all
|
626 |
+
the different sites can come together
|
627 |
+
and start creating useful
|
628 |
+
Services um and in stage three we're
|
629 |
+
going to add payments and slashing so
|
630 |
+
that's our road map currently
|
631 |
+
and you know we are on the stage one is
|
632 |
+
already on the main net uh we will have
|
633 |
+
a stage two test net coming soon you
|
634 |
+
know definitely this quarter hopefully
|
635 |
+
much
|
636 |
+
earlier
|
637 |
+
um which will go on Main net next
|
638 |
+
quarter and then the stage three follows
|
639 |
+
that so that's the current launch road
|
640 |
+
map of uh Ian ler we're really excited
|
641 |
+
about all these different uh new things
|
642 |
+
that can be done across the different
|
643 |
+
sides of ecosystem stakers operators you
|
644 |
+
know um people building new avss rollups
|
645 |
+
consuming a DA lots of interesting
|
646 |
+
things happening there uh you'll hear
|
647 |
+
about some of them today um thank you so
|
648 |
+
much for listening to the first
|
649 |
+
talk"
|
650 |
+
"Q: I saw Vitalik’s blog post about overloading the consensus layer, and how restaking, in his view, could pose systemic risks to Ethereum. I'm curious to hear your take on his take?
|
651 |
+
Kannan: One of the things I think he wants to kind of lay out is that, “Hey don't externalize, and don't create something that, assuming that if the protocol goes wrong, Ethereum is going to fork around it.”
|
652 |
+
I think that is a pretty reasonable position from Ethereum, that you build protocols and the protocols have to internalize social consensus rather than externalize it to Ethereum.
|
653 |
+
So I read it as to not overload Ethereum social consensus, which is used only for forking the chain. And don't assume that you can build a protocol that, and because you're too big to fail, Ethereum can fork around that. So that's how I read it.
|
654 |
+
And I think it's a pretty obvious statement in our view. But I think it has to be said, somebody has to say it, so it's good that Vitalik went out and said it.
|
655 |
+
Because what we don't want is for calls to deploy code that is not properly audited, doesn't have internal security controls, and then the Ethereum community has to now work hard to figure out how to retrieve it.
|
656 |
+
I think a lot of people after reading the article have been talking a lot about restaking risks.
|
657 |
+
I want to make it super clear: anything that restaking can do, already liquid staking can do, so I view restaking as a lesser risk than liquid staking.
|
658 |
+
|
659 |
+
Q: Can you expand on that?
|
660 |
+
Kannan: Basically, you can take a liquid staking token and then deposit it into complex DeFi protocols, or you could just deposit it into validating a new layer 2, or a new oracle or any of these things.
|
661 |
+
So anything that restaking can do, liquid staking can already do. Because you know, you have the LSD [short for liquid staking derivative] token, and you can do anything with it. And one particular thing you could do with that is, of course, go and validate another network.
|
662 |
+
So I view restaking as just one particular use case of liquid staking, but actually reducing the risk of that one particular use case.
|
663 |
+
|
664 |
+
Q: Why do you think restaking is having a moment in the news?
|
665 |
+
Kannan: I don't know. I'm glad people are talking about it. Of course, anything that adds new rewards to stakers is something interesting.
|
666 |
+
I said anything that could be done with EigenLayer could be done with LSTs, but people didn't know what to do with these LSTs.
|
667 |
+
They were doing exactly the same thing that people are doing with ether, which is lending, borrowing, the same set of DeFi parameters.
|
668 |
+
I think one thing that EigenLayer did is by creating this new category, that validation, if I can borrow the Ethereum trust network to do new things: I can build a new layer 1, I can build a new like oracle network, I can build a new data availability system, I can build any system on top of the Ethereum trust network, so it internalizes all the innovation back into Ethereum, or aggregates all the innovation back into Ethereum, rather than each innovation requiring a whole new system.
|
669 |
+
So I think that narrative is quite attractive.
|
670 |
+
|
671 |
+
Q: I was just reading the news about EIP-7514, which is a short term solution for solving the overcrowdedness of validators, by limiting entries of new validators. How does that affect an EigenLayer?
|
672 |
+
Kannan: I think mostly, it means the same thing for EigenLayer that it means for liquid staking protocols, that there is going to be a smaller rate at which new validators can enter.
|
673 |
+
There's a long entry queue right now, and people don't want to wait that long.
|
674 |
+
And making it slower is going to just make the new growth of LSTs slower. But I understand fully that this is a super important thing for Ethereum to be conservative and not have an overflow of validators that may not be able to be handled by the consensus layer.
|
675 |
+
But in the long term, if the total staking of Ethereum cannot grow, one of the things that happens is the total yield or the return that stakers are getting is bounded by the Ethereum staking, whereas in the presence of restaking there is a possibility for them to get some of these additional rewards. Other than that, it's pretty similar.
|
676 |
+
|
677 |
+
Q: You were making the point that EigenDA is just like in-house AVS (actively validated service) – explain what it is:
|
678 |
+
Kannan: What we decided is, in order to keep this system of shared security, in order to keep EigenLayer as decentralized as possible, we want to make sure that there is a highly scalable data system at its backbone. And that's what EigenDA is, it's a highly scalable data availability system, built on the same ideas that underpin the Ethereum roadmap, particularly what is called danksharding.
|
679 |
+
Our view is that building an Ethereum-adjacent data availability layer requires first principles thinking, whereas Celestia and Avail are built to be chains by themselves.
|
680 |
+
If you're building a data availability system adjacent to Ethereum, you'd want Ethereum validators to participate. So that's just one part of the story. Of course, EigenLayer enables that.
|
681 |
+
But then you go beyond that, and then you see, “Oh, it's not just you want to get the Ethereum nodes to participate.”
|
682 |
+
Ethereum already has consensus built in, and Ethereum gives you the ordering of the various transactions. So you should build the data availability system, which doesn't need its own ordering.
|
683 |
+
Whereas all the existing other protocols like Celestia and Avail, are basically chains that have to do their own ordering; we built a system which doesn't have internal ordering; all ordering is done on Ethereum.
|
684 |
+
|
685 |
+
Q: Liquid restaking tokens - once your liquid staking tokens are locked on EigenLayer, they become illiquid?
|
686 |
+
Kannan: That’s correct, the problem that the liquid restaking tokens are trying to solve is, can I just have a restaked position, and then still keep it liquid. So you can take that receipt token of liquid restaking and then transfer it.
|
687 |
+
We are not building this kind of liquid restaking but other people are building liquid restaking on top of them.
|
688 |
+
|
689 |
+
Q: I think your comment was, you want to use the Ethereum shared security for as many things as possible. I'm curious, now that there's also people building on the back of what y'all are doing, is there a natural limit to how much that you know, Ethereum can support?
|
690 |
+
Kannan: This is a similar kind of question that one could ask already at the applicatEigenLayer of Ethereum: How many applications on Ethereum are smart contracts and how many smart contracts can be built on top of Ethereum?
|
691 |
+
So it's the same thing with EigenLayer because people staking and running new applications, but now they do it much more flexibly and programmably with these aliases on top of EigenLayer, all contribute back to Ethereum. Their ETH staking increases rewards, ETH itself potentially increases in value because of all these additional use cases.
|
692 |
+
So over time, this can start to accommodate more and more.
|
693 |
+
But there's absolutely a limit."
|
694 |
+
"the most successful outcome for i l
|
695 |
+
would be web 3 offers a brand new petri
|
696 |
+
dish our job is to buy Great Tech at
|
697 |
+
great prices AI is also libertarian
|
698 |
+
enable use case that people haven't been
|
699 |
+
able to do today the next hundreds of
|
700 |
+
millions of players they will come to
|
701 |
+
the market through mobile my personal
|
702 |
+
reason why I could be bullish in the
|
703 |
+
next five months
|
704 |
+
is hey everybody welcome back to another
|
705 |
+
episode of The Block runch podcast I'm
|
706 |
+
your host Jason Choy I'm the founder of
|
707 |
+
the angel fun tangent um and everything
|
708 |
+
we discuss on this show is not Financial
|
709 |
+
advice and not reflective of our
|
710 |
+
respective company opinions now one of
|
711 |
+
the biggest busws of this year is
|
712 |
+
reaking and the go-to project in this
|
713 |
+
vertical is obviously EigenLayer now
|
714 |
+
today even before the launch of the
|
715 |
+
token Ian leer has already attracted
|
716 |
+
almost $8 billion in funds deposited
|
717 |
+
this makes it the fourth largest
|
718 |
+
protocol by total value locked according
|
719 |
+
to defi Lama so already I'm getting a
|
720 |
+
lot of messages from people saying it's
|
721 |
+
either the most most transformative
|
722 |
+
thing to happen to ethereum but also
|
723 |
+
increasingly more people are talking
|
724 |
+
about potential systematic risk that
|
725 |
+
comes with the concept of reaking so as
|
726 |
+
an angel investor in igen ler these are
|
727 |
+
the questions that I've also thought a
|
728 |
+
lot about over the past few months so
|
729 |
+
I'm really really excited and grateful
|
730 |
+
for siram the founder of EigenLayer to
|
731 |
+
come on the show to chat with us today
|
732 |
+
so welcome to the show man hey thank you
|
733 |
+
so much Jason really excited to be here
|
734 |
+
looking forward to dive into uh the
|
735 |
+
depths of the project absolutely so I
|
736 |
+
actually stayed up last night and I went
|
737 |
+
through a lot of your tweets and a lot
|
738 |
+
of the transcripts for your podcast
|
739 |
+
interviews and I realized there's
|
740 |
+
actually so so much to go over but I
|
741 |
+
guess before we dive into the meat there
|
742 |
+
i' love to kind of di the clocks back a
|
743 |
+
little bit with start with the origin
|
744 |
+
because I know you've been interested in
|
745 |
+
PP networks before 2008 uh and doing
|
746 |
+
your PhD there and then you moved on to
|
747 |
+
computational genomics I think later and
|
748 |
+
then stumbled in the crypto in 2017 and
|
749 |
+
I heard that you almost began your
|
750 |
+
journey by building on cardano first so
|
751 |
+
I'm curious you know how did you go from
|
752 |
+
that to deciding to build this kind of
|
753 |
+
reaking idea yeah no actually like we
|
754 |
+
didn't you know we didn't Begin by
|
755 |
+
trying to build on cardano uh the story
|
756 |
+
goes back even further so you know in in
|
757 |
+
2017 2018 you know around end of 2017
|
758 |
+
actually when I got to uh know about
|
759 |
+
blockchain my first reaction was you
|
760 |
+
know is this some kind of like a
|
761 |
+
speculative bubble that you know and
|
762 |
+
last time you know I worked on
|
763 |
+
peer-to-peer wireless networks that
|
764 |
+
didn't turn out well
|
765 |
+
so I I was a bit skeptical of the whole
|
766 |
+
premise because you know centralized
|
767 |
+
systems are more efficient and they have
|
768 |
+
a way to like outrun decentralized
|
769 |
+
systems so that was the kind of starting
|
770 |
+
point but you know the when it turned
|
771 |
+
for me is when we realize that uh
|
772 |
+
blockchains can basically help us
|
773 |
+
coordinate in the absence of trust and
|
774 |
+
just like the internet is the
|
775 |
+
information super iway blockchains and
|
776 |
+
crypto could be our coordination super
|
777 |
+
iway way that was the kind of like
|
778 |
+
operating model and and once I could see
|
779 |
+
that okay actually if if trust is so
|
780 |
+
Central if we can have a neutral
|
781 |
+
decentralized source of trust that can
|
782 |
+
be like really valuable but you know the
|
783 |
+
the particular problems we are working
|
784 |
+
on at that time was you know how do you
|
785 |
+
scale a consensus protocol what
|
786 |
+
properties can a consensus protocol have
|
787 |
+
you know how would you build uh data
|
788 |
+
availability or an oracle or other
|
789 |
+
systems with various properties what is
|
790 |
+
the game theory for some of these things
|
791 |
+
what are the mathematical guarantees
|
792 |
+
this was kind of how we got introduced
|
793 |
+
into it and the obvious kind of thing we
|
794 |
+
wanted to do was to get like you know
|
795 |
+
Bitcoin or ethereum to use some of these
|
796 |
+
ideas and you know we were so far away
|
797 |
+
from the space and had no real uh
|
798 |
+
connections that we found it quite
|
799 |
+
difficult to kind of understand like and
|
800 |
+
and interact with the crypto space and
|
801 |
+
uh you know it appeared that the most
|
802 |
+
kind of like uh the the only way we were
|
803 |
+
seeing that people from the academic
|
804 |
+
background where getting into blockchain
|
805 |
+
and crypto was actually going and
|
806 |
+
starting hey you know here's a new
|
807 |
+
consensus protocol I'm going to build a
|
808 |
+
layer one blockchain around it and we
|
809 |
+
thought okay there's no other way this
|
810 |
+
is the only way to like take an idea at
|
811 |
+
the level of a consensus protocol
|
812 |
+
because you can't build it as a smart
|
813 |
+
contract on ethereum because the whole
|
814 |
+
point is to change the way that the the
|
815 |
+
nodes come into
|
816 |
+
consensus and so I said okay maybe we
|
817 |
+
should build our own like you know uh
|
818 |
+
layer one and we were actually you know
|
819 |
+
we took a very purist approach and we
|
820 |
+
said like let's first actually build the
|
821 |
+
whole system before we even do a fund
|
822 |
+
raise so we had a project called
|
823 |
+
Trifecta where we built the block built
|
824 |
+
a blockchain you know we were running it
|
825 |
+
on 100 nodes at that time there's an MIT
|
826 |
+
crypto economic summit video where we
|
827 |
+
demonstrated running at like you know
|
828 |
+
hundreds of thousands of transactions
|
829 |
+
per second but that project never
|
830 |
+
launched and that's why you know if if
|
831 |
+
you're a listener and wondering where is
|
832 |
+
this trifecto blockchain it doesn't
|
833 |
+
exist it was uh
|
834 |
+
it it it it only has had a uh short
|
835 |
+
Lifeline you know lifetime as a kind of
|
836 |
+
proof of concept so I because you know
|
837 |
+
we the questions that we got asked from
|
838 |
+
investors and other people was hey okay
|
839 |
+
you you got these 100,000 transactions
|
840 |
+
per second where is the user base where
|
841 |
+
is the ecosystem how are you going to
|
842 |
+
build all of this out and I said I don't
|
843 |
+
know you know if blockchain's a thing
|
844 |
+
you know fast blockchain is a thing and
|
845 |
+
here is the thing that actually does it
|
846 |
+
and from from that point actually you
|
847 |
+
know one of the things that I realized
|
848 |
+
is kind of like a fundamental problem
|
849 |
+
for starting a new like you know decent
|
850 |
+
L protocol is the source of trust right
|
851 |
+
I couldn't just take it and throw it on
|
852 |
+
top of ethereum if it was like that that
|
853 |
+
would have been so amazing right like I
|
854 |
+
just just like you write a smart
|
855 |
+
contract and throw it on ethereum Let
|
856 |
+
the blockchain like supplies the trust
|
857 |
+
so this is when I came up with this
|
858 |
+
model that you know it's very simple
|
859 |
+
once you state it basically like a
|
860 |
+
general purpose smart contract
|
861 |
+
blockchain is like selling trust and
|
862 |
+
earning fees in return for selling trust
|
863 |
+
and selling trust to whom to
|
864 |
+
Applications right so applications are
|
865 |
+
choosing to live on top of a blockchain
|
866 |
+
because it's consuming the trust okay so
|
867 |
+
once I understood this economy the
|
868 |
+
question was like how can we do this
|
869 |
+
more generally like you know more than
|
870 |
+
just smart contracts can we kind of like
|
871 |
+
take the same set of nodes same
|
872 |
+
economics and some more transfer it and
|
873 |
+
we Tred all kinds of things can you
|
874 |
+
build it on bitcoin you know can you
|
875 |
+
build it on ethereum uh and the the
|
876 |
+
original set of ideas we had were not
|
877 |
+
really related to reaking it was some
|
878 |
+
kind of like a complex cryptoeconomic
|
879 |
+
game but the the core idea was hey now I
|
880 |
+
know I can run a different virtual
|
881 |
+
machine on top of a different different
|
882 |
+
blockchain what would I do with that and
|
883 |
+
this was you know in 2021 and one of the
|
884 |
+
things we knew we could do was to run
|
885 |
+
evm on nonm blockchains and so this was
|
886 |
+
the kind of starting point of the kind
|
887 |
+
of ion lay project is we said oh let's
|
888 |
+
bring evm to all the non evm blockchains
|
889 |
+
and you know as a starting point we we
|
890 |
+
took cardano because cardano was
|
891 |
+
probably it had a barly functional smart"
|
892 |
+
"contract programming environment at that
|
893 |
+
time and what that meant was and and it
|
894 |
+
was very difficult for developers to
|
895 |
+
build on top of it so if we had evm
|
896 |
+
easily virtualized on top of Gano that
|
897 |
+
would be like a cool thing and you could
|
898 |
+
do this on any blockchain you know it
|
899 |
+
was not specific to cardano but it was a
|
900 |
+
starting point for what we could do but
|
901 |
+
you know as we were thinking about it
|
902 |
+
one of the things that clicked to me was
|
903 |
+
if the fundamental thing is
|
904 |
+
your you want to have a common source of
|
905 |
+
decentralized trust then building on
|
906 |
+
distinct source of decentralized trust
|
907 |
+
is replicated effort rather than
|
908 |
+
aggregated effort and so the obvious
|
909 |
+
place which was powerful and Central for
|
910 |
+
us to build was ethereum and so we
|
911 |
+
wanted to then like think about what we
|
912 |
+
would build on top of ethereum and at
|
913 |
+
that time I actually had no good idea
|
914 |
+
for what to build on ethereum and the
|
915 |
+
the story is you know I had a an
|
916 |
+
interaction with uh uh Kyle samani of
|
917 |
+
multicoin and you know pitching this
|
918 |
+
this idea that you can actually do
|
919 |
+
virtualization of evm or non evm
|
920 |
+
blockchains and Kyle in his
|
921 |
+
characteristic style said you know evm
|
922 |
+
is a piece of you know star I don't want
|
923 |
+
you know you should not be working on
|
924 |
+
that and I'm like okay
|
925 |
+
and then uh you know I said oh no but
|
926 |
+
you could run like arbitary virtual
|
927 |
+
machines on top of ethereum too like if
|
928 |
+
you wanted and then he said no this is
|
929 |
+
some kind of an optimistic type rollup
|
930 |
+
it it will never work I said like why
|
931 |
+
would it work because optimistic rollups
|
932 |
+
are going to be very
|
933 |
+
expensive and I went back and we sat
|
934 |
+
down with the team and we were trying to
|
935 |
+
understand this peculiar statement I
|
936 |
+
didn't know at that time went through
|
937 |
+
all the optimistic rups this is 2021 and
|
938 |
+
found that the fees was much higher
|
939 |
+
and I thought ZK rollups should be more
|
940 |
+
expensive because I have to give a ZK
|
941 |
+
proof so why is an optimistic rollup
|
942 |
+
more expensive it was because of data
|
943 |
+
availability and all the costs were
|
944 |
+
going into publishing data on ethereum
|
945 |
+
and so we then said oh yeah you know now
|
946 |
+
it all fit together we had been doing
|
947 |
+
research on data availability for many
|
948 |
+
many years before that so we said I know
|
949 |
+
how to scale data let's just build that
|
950 |
+
so we said okay we're building on
|
951 |
+
ethereum we'll build data availability
|
952 |
+
on top of it so now we have a killer
|
953 |
+
application so that that was the
|
954 |
+
beginning of how we decided to build on
|
955 |
+
ethereum but also know we wanted to
|
956 |
+
build on etherum we just had didn't have
|
957 |
+
a good use case you know at that time
|
958 |
+
you know we didn't know what programming
|
959 |
+
environment would be interesting I had
|
960 |
+
all these like high level pictures where
|
961 |
+
I'd say oh you can build AI you can
|
962 |
+
build like databases you can build like
|
963 |
+
gaming you know environments all these
|
964 |
+
things but you know you have to start
|
965 |
+
somewhere where you know there is Market
|
966 |
+
traction and we found that with data
|
967 |
+
availability so that's the origin of Ian
|
968 |
+
da and EigenLayer on on ethereum add to
|
969 |
+
this what happened was we said like
|
970 |
+
let's go to eat Denver you know we're
|
971 |
+
going to eat Denver now next week but
|
972 |
+
this was you know
|
973 |
+
2022 and go to Denver and hang out with
|
974 |
+
all the people that I didn't know
|
975 |
+
anybody there I actually know zero
|
976 |
+
people in in ethereum at that time and I
|
977 |
+
connected with the vi of ethereum which
|
978 |
+
was you know decentralization
|
979 |
+
permissionless Innovation censorship
|
980 |
+
resistance it felt like this community
|
981 |
+
had a set of principles that they're
|
982 |
+
anchoring on rather than you know either
|
983 |
+
individuals or expediency towards profit
|
984 |
+
or even a product which felt very
|
985 |
+
different to me I came back and told a
|
986 |
+
friend who was working in Google at that
|
987 |
+
time like imagine somebody just goes to
|
988 |
+
a Google conference they're not a Google
|
989 |
+
stock owner they're not a Google like
|
990 |
+
you know programmer they're not even a
|
991 |
+
Google really like application developer
|
992 |
+
they just feel like they're a Google
|
993 |
+
person at the end of a Google conf
|
994 |
+
that's how I felt at the end ofen and so
|
995 |
+
we decided to build on ethereum after
|
996 |
+
that I yeah I think the the three
|
997 |
+
biggest lessons that I've learned over
|
998 |
+
the past years of investing in the space
|
999 |
+
is that ethereum's greatest exports are
|
1000 |
+
three things right it's the liquidity of
|
1001 |
+
ethereum is the programmability of if
|
1002 |
+
evm and the ideology of ethereum and it
|
1003 |
+
sounds like to me that when I first saw
|
1004 |
+
I L I thought okay this is actually a
|
1005 |
+
project that helps expand this you know
|
1006 |
+
vastly beyond just the ethereum chain
|
1007 |
+
itself and I know you describe I as a
|
1008 |
+
generalized mechanism for anybody to
|
1009 |
+
build arbitrary distributed systems on
|
1010 |
+
top of the ethereum trust Network and
|
1011 |
+
when my Normie Friends Ask me okay what
|
1012 |
+
the hell does that mean I basically
|
1013 |
+
explained to them well you can stake
|
1014 |
+
your eth and not just validate for the
|
1015 |
+
eth network but for you know any project
|
1016 |
+
that chooses to borrow the security of
|
1017 |
+
this uh you know of this stake so I was
|
1018 |
+
actually quite fascinated because uh I
|
1019 |
+
feel like I've seen the similar ideas
|
1020 |
+
before in like polka do or Cosmos this
|
1021 |
+
idea of like shared security so how much
|
1022 |
+
of the inspiration came from observing
|
1023 |
+
what is being done on other chains what
|
1024 |
+
work what didn't work I would say that
|
1025 |
+
uh at least our own Journey was uh from
|
1026 |
+
we started from looking at
|
1027 |
+
Bitcoin uh where we we were looking at
|
1028 |
+
hey you know can you borrow trust from
|
1029 |
+
Bitcoin and the set of ideas we got
|
1030 |
+
exposed to was mostly merge mining the
|
1031 |
+
idea that you have a mining common
|
1032 |
+
mining uh Power and a lot of energy is
|
1033 |
+
expended on mining can you reuse that
|
1034 |
+
mining for other like securing other
|
1035 |
+
blockchains this idea was called Mudge
|
1036 |
+
mining back in in the day and I think
|
1037 |
+
even Satoshi wrote about it in one of
|
1038 |
+
their no Bitcoin talk or whatever and
|
1039 |
+
the thing
|
1040 |
+
is um we looked at merge Mining and one
|
1041 |
+
of the big incentive problems in merge
|
1042 |
+
mining is if you merge mine Bitcoin and
|
1043 |
+
some other altcoin the problem is you
|
1044 |
+
can attack the altcoin with impunity
|
1045 |
+
because I you know if you if there is an
|
1046 |
+
attack on the other chain it doesn't do
|
1047 |
+
anything to my mining equipment or like
|
1048 |
+
my Bitcoin price is not affected by the
|
1049 |
+
attack that happens on this other chain
|
1050 |
+
or coin so the crypto economics of
|
1051 |
+
Bitcoin is very uniquely tied to bitcoin
|
1052 |
+
itself which is that I have invested
|
1053 |
+
this bunch of money in like buying the
|
1054 |
+
mining hardware and therefore if I do
|
1055 |
+
some big harm and a majority tries to do
|
1056 |
+
an attack then my mining Hardware may
|
1057 |
+
become useless you know because you know
|
1058 |
+
the the the BTC is not valuable anymore
|
1059 |
+
so this was not the case for you know
|
1060 |
+
merge Mining and so the realization came
|
1061 |
+
from when you do staking the Dynamics
|
1062 |
+
are quite different because staking
|
1063 |
+
comes with slashing the equivalent of
|
1064 |
+
slashing is like going and finding out
|
1065 |
+
which miners behave badly and then
|
1066 |
+
burning their mining equipment right
|
1067 |
+
like that's not even thinkable as a as
|
1068 |
+
as a possible strategy right uh but the
|
1069 |
+
thing with staking is stake is
|
1070 |
+
intrinsically like you know on the chain
|
1071 |
+
and therefore you can burn the stake for
|
1072 |
+
misbehaviors on on the chain and this
|
1073 |
+
was such a powerful concept and then we
|
1074 |
+
realized that if you had a general
|
1075 |
+
purpose staking mechanism you can
|
1076 |
+
transfer the cryptoeconomic trust to
|
1077 |
+
arbitary other services much more easily
|
1078 |
+
we didn't know about much of the other
|
1079 |
+
other stuff like poka do or even layer
|
1080 |
+
tws or you know what was going on in
|
1081 |
+
Cosmos or avalanch at that time but of
|
1082 |
+
course later as you start exploring
|
1083 |
+
these ideas you find oh yeah you know"
|
1084 |
+
"these these other things are on this
|
1085 |
+
vicinity and what we I think have built
|
1086 |
+
is the most generalized system for shat
|
1087 |
+
security which is more General than all
|
1088 |
+
the other systems in in the flexibility
|
1089 |
+
with which trust can be offered and
|
1090 |
+
shared so that that's how I would phrase
|
1091 |
+
it in relationship with some of the
|
1092 |
+
other systems like any networks or
|
1093 |
+
protocols there's many different
|
1094 |
+
stakeholders so obviously there's rakers
|
1095 |
+
who are staking their eth and then also
|
1096 |
+
choosing to provide security with that
|
1097 |
+
stake to other applications there's The
|
1098 |
+
Operators that run the network but I
|
1099 |
+
think the concept of the AVS is quite
|
1100 |
+
interesting and not something that you
|
1101 |
+
know many people in crypto have kind of
|
1102 |
+
really come across before EigenLayer so
|
1103 |
+
can you help us explain you know what
|
1104 |
+
exactly are these abs maybe that's a
|
1105 |
+
good SEC way to talk about the the
|
1106 |
+
origins of IG da as well yeah um ABS is
|
1107 |
+
actively validated services it's a term
|
1108 |
+
that we co to explain what types of
|
1109 |
+
things can be built on EigenLayer because a
|
1110 |
+
lot of people look at EigenLayer you
|
1111 |
+
know at least right now in in the
|
1112 |
+
context of some kind of a D5 protocol it
|
1113 |
+
was never intended to be a D5 protocol
|
1114 |
+
it was intended to connect stakers and
|
1115 |
+
operators to innovators people inventing
|
1116 |
+
new distributed systems and
|
1117 |
+
decentralized protocols to borrow and
|
1118 |
+
share the the trust and security and we
|
1119 |
+
had to come up with an umbrella term you
|
1120 |
+
know people usually think of these as
|
1121 |
+
chains but we think chain is a very
|
1122 |
+
restrictive and a narrow way of thinking
|
1123 |
+
uh so we think of these as services and
|
1124 |
+
why service right like you know in in
|
1125 |
+
the cloud there is an analogous thing
|
1126 |
+
called software as a service right
|
1127 |
+
software as a service is you write a
|
1128 |
+
piece of software throw it on AWS or
|
1129 |
+
Google cloud and let it run there and
|
1130 |
+
you know as people are using the
|
1131 |
+
software you know you pay for the cloud
|
1132 |
+
but you also make money and if the unit
|
1133 |
+
Economics work then you're actually
|
1134 |
+
making money as a SAS but the most
|
1135 |
+
important thing for me in the structure
|
1136 |
+
of SAS and Cloud was how much open
|
1137 |
+
Innovation that actually enabled because
|
1138 |
+
you have the cloud and you don't have to
|
1139 |
+
think about all the hardware and like
|
1140 |
+
how to run it and how to scale it and
|
1141 |
+
how to Prov the enough amount of like
|
1142 |
+
compute to actually run your services
|
1143 |
+
what happens is you have uh a very
|
1144 |
+
powerful system where anybody can come
|
1145 |
+
and innovate and build new SAS services
|
1146 |
+
and put it on top of the internet this
|
1147 |
+
led to Super specialization very very
|
1148 |
+
narrow specialized SAS services that
|
1149 |
+
were built and lots of lots of people
|
1150 |
+
all around the world like you know in
|
1151 |
+
places which could not compete on the
|
1152 |
+
hardware basis could compete purely on a
|
1153 |
+
software basis and this is a very
|
1154 |
+
interesting important thing that
|
1155 |
+
happened with the internet and so if you
|
1156 |
+
think of what is the analog analogous
|
1157 |
+
thing that can be done on on top of the
|
1158 |
+
the crypto blockchain infrastructure
|
1159 |
+
that's what an AVS an actively validated
|
1160 |
+
service an actively validated service is
|
1161 |
+
a service that you uh you know write and
|
1162 |
+
it is anything that requires
|
1163 |
+
decentralized validation right and these
|
1164 |
+
decentralized validated services are
|
1165 |
+
then like managed by EigenLayer to make
|
1166 |
+
sure that all the node operators opt in
|
1167 |
+
the enough stake is backing it like how
|
1168 |
+
much particular attributable economic
|
1169 |
+
commitment has been backing that service
|
1170 |
+
all of this accounting is managed by Aon
|
1171 |
+
layer but as a Creator as an innovator
|
1172 |
+
you can just write the service and put
|
1173 |
+
it on top of like uh EigenLayer so that's
|
1174 |
+
the category of uh actively validated
|
1175 |
+
Services it includes something like
|
1176 |
+
running a new layer one chain but not
|
1177 |
+
exclusively running a chain you may be
|
1178 |
+
running very specific services and you
|
1179 |
+
know what might that service be to take"
|
1180 |
+
"you know usual examples it might be to
|
1181 |
+
run an oracle which fetches data from
|
1182 |
+
the internet has a group of nodes agree
|
1183 |
+
that that's the correct data and then
|
1184 |
+
put it on top of a blockchain it may be
|
1185 |
+
a a bridge which reads data from another
|
1186 |
+
chain and then moves it on top of
|
1187 |
+
another chain it may be a um you know an
|
1188 |
+
AI service you may be sitting on
|
1189 |
+
ethereum and you want to request some AI
|
1190 |
+
inputs and you know you need to run an
|
1191 |
+
AI inference to actually adjust the
|
1192 |
+
prices or something on top of your Unis
|
1193 |
+
swap pool so these are all examples of
|
1194 |
+
services there may be other like much
|
1195 |
+
more nuanced and specific services that
|
1196 |
+
show up on I which we already seeing for
|
1197 |
+
example uh we see things like prove of
|
1198 |
+
location proof of location is I want to
|
1199 |
+
know where these nodes are placed can I
|
1200 |
+
run a decentralized service to know the
|
1201 |
+
location of these other either operators
|
1202 |
+
or users in a decentralized manner and
|
1203 |
+
how might the decentralized nodes know
|
1204 |
+
it by sending Network latency
|
1205 |
+
information like you know I send a
|
1206 |
+
packet when do I receive it back if I
|
1207 |
+
can receive it back within like you know
|
1208 |
+
30 milliseconds it must be close to one
|
1209 |
+
of my locations
|
1210 |
+
and if many many nodes can do it and
|
1211 |
+
parallel and triangulate where the nodes
|
1212 |
+
are so that's a really interesting kind
|
1213 |
+
of piece of information so prove of
|
1214 |
+
location is that that's an example of a
|
1215 |
+
service but we've seen all kinds of
|
1216 |
+
different Services I would say like 20
|
1217 |
+
categories of services that are kind of
|
1218 |
+
building on top of EigenLayer so that's
|
1219 |
+
the ABS actively validated service is a
|
1220 |
+
category I can go into some of these
|
1221 |
+
examples but that's a high level uh
|
1222 |
+
overview yeah and given how diverse
|
1223 |
+
these use cases can be I'm curious uh
|
1224 |
+
and this is something that a lot of
|
1225 |
+
people are discussing as well in terms
|
1226 |
+
of the security assumptions because you
|
1227 |
+
mentioned the concept of slashing so
|
1228 |
+
let's say if someone is reaking for like
|
1229 |
+
20 different applications one of those
|
1230 |
+
applications happen to do something bad
|
1231 |
+
and you know the validator has to be
|
1232 |
+
slashed uh what does that process look
|
1233 |
+
like and you know how do we how do we
|
1234 |
+
think about the implications for the
|
1235 |
+
entire kind of uh you know EigenLayer
|
1236 |
+
stack the uh the way to think about it
|
1237 |
+
is
|
1238 |
+
slashing is encoded into smart contracts
|
1239 |
+
that talk to the EigenLayer contract
|
1240 |
+
whenever a Staker is opting into a new
|
1241 |
+
AVS they're basically opting
|
1242 |
+
specifically into an AVS contract and
|
1243 |
+
the AVS contract specifies the
|
1244 |
+
conditions of registration the
|
1245 |
+
conditions of payment and the conditions
|
1246 |
+
of slashing so basically who can come in
|
1247 |
+
what's the POs to incentive what's the
|
1248 |
+
negative incentive to do this stuff and
|
1249 |
+
those are encoded in the AVS contracts
|
1250 |
+
and so now when um when a Staker opts
|
1251 |
+
into a bunch of avss what they're
|
1252 |
+
actually saying is I'm opting into these
|
1253 |
+
bunch of conditions of like positive and
|
1254 |
+
negative incentives and I need to do
|
1255 |
+
this bunch of work to actually keep up
|
1256 |
+
my uh positive incentives and if the
|
1257 |
+
contracts if the slashing conditions are
|
1258 |
+
return in code on ethereum Smart
|
1259 |
+
contracts and you know for a moment
|
1260 |
+
let's assume there are no code
|
1261 |
+
programming errors which we have to deal
|
1262 |
+
with but you know then essentially what
|
1263 |
+
you're saying is you're opting into
|
1264 |
+
rigid objectively verifiable slashing
|
1265 |
+
conditions which are return in code on
|
1266 |
+
ethereum and what that means is if I
|
1267 |
+
know that I'm running the software
|
1268 |
+
correctly I won't get slashed by this
|
1269 |
+
you know by this contract in fact I may
|
1270 |
+
even run a piece of code we call an
|
1271 |
+
anti-s slasher what an anti slasher does
|
1272 |
+
is whenever I issue a signature it
|
1273 |
+
checks that this signature will not
|
1274 |
+
trigger slashing you know before it
|
1275 |
+
issues the signature and so this kind of
|
1276 |
+
an anti- slasher can be run locally and
|
1277 |
+
so you know that you will not get
|
1278 |
+
slashed if you actually if the contracts
|
1279 |
+
are correctly return so that's the first
|
1280 |
+
level which is as a Staker you're opting
|
1281 |
+
into objectively verifiable rigid
|
1282 |
+
conditions return as smart contracts on
|
1283 |
+
ethereum so the trust model is very
|
1284 |
+
similar to the other kind of trust model
|
1285 |
+
when you're going and opting into a Unis
|
1286 |
+
swap or a or any of these kinds of D5
|
1287 |
+
protocols but to protect users even more
|
1288 |
+
we have another layer of protection
|
1289 |
+
because we know that code can sometimes
|
1290 |
+
be buggy and we see this all the time in
|
1291 |
+
crypto like sometimes you know a
|
1292 |
+
protocol has a buggy code and then like
|
1293 |
+
suddenly people lose their funds and
|
1294 |
+
this is something we are taking a
|
1295 |
+
cautious approach to and the way we take
|
1296 |
+
the cous approach is by actually having
|
1297 |
+
what we call a slashing veto committee
|
1298 |
+
this is a committee of external parties
|
1299 |
+
you know experts in kind of protocol
|
1300 |
+
design who can actually vet whether the
|
1301 |
+
contract triggered the slashing for a
|
1302 |
+
you know on on on the actual protocol or
|
1303 |
+
it was a bug that LE led to the slashing
|
1304 |
+
if it is adjudicated as a bug slashing
|
1305 |
+
does not happen so therefore slashing
|
1306 |
+
requires two distinct things the
|
1307 |
+
objective contract to trigger the
|
1308 |
+
slashing and the kind of human committee
|
1309 |
+
to approve it otherwise slashing is not
|
1310 |
+
fulfilled so we you know in the balance
|
1311 |
+
of powers between stakers and avss we
|
1312 |
+
lean on protecting stakers because you
|
1313 |
+
know know stakers are basically like
|
1314 |
+
underwriting the system with their own
|
1315 |
+
like Risk and the the guarantee we want
|
1316 |
+
to give to a Staker is if you are not
|
1317 |
+
malicious you will not be slashed so
|
1318 |
+
slashing is there only
|
1319 |
+
for absolutely attributable attributable
|
1320 |
+
actions that the Staker or operator took
|
1321 |
+
which are malicious not for regular
|
1322 |
+
operations where they made a
|
1323 |
+
configuration mistake or the the program
|
1324 |
+
had a bug or anything like that so
|
1325 |
+
because you know when you're building a
|
1326 |
+
pon system where anybody can come in and
|
1327 |
+
participate you need to protect the
|
1328 |
+
system against like malicious actors INF
|
1329 |
+
infiltrating the system so you need a
|
1330 |
+
system of kerma like positive or
|
1331 |
+
negative incentives to keep the system
|
1332 |
+
going and that's what Igan does is make
|
1333 |
+
sure that as a Staker you don't have any
|
1334 |
+
incentive to try to like attack the
|
1335 |
+
system whereas also make sure that avss
|
1336 |
+
you know have no agency to attack the
|
1337 |
+
system even if they put in a buggy C
|
1338 |
+
firstly they to put in smart contract
|
1339 |
+
code not like you know have arbitrary
|
1340 |
+
adjudication conditions but smart
|
1341 |
+
contract code and then even then there
|
1342 |
+
is a back stop in terms of a common
|
1343 |
+
slashing V committee my guess is that a
|
1344 |
+
lot of people who are kind of you know
|
1345 |
+
concerned about systemic risks that Ian
|
1346 |
+
ler could introduce are almost confusing
|
1347 |
+
the concept of reaking with the concept
|
1348 |
+
of rehypothecation because they see this
|
1349 |
+
concept play out a lot in defi where
|
1350 |
+
somebody has a bunch of collateral and
|
1351 |
+
they use that to margin to do some sort
|
1352 |
+
of lending or borrowing and then they
|
1353 |
+
use the stuff they borrow to margin
|
1354 |
+
again and borrow more and more and more
|
1355 |
+
but this is something fundamentally
|
1356 |
+
different than that right so if if you
|
1357 |
+
do get slash it's not like everything
|
1358 |
+
just like every single app that's tied
|
1359 |
+
to that St suddenly just like collaps
|
1360 |
+
and and stop functioning right just to
|
1361 |
+
just to make that very clear to our
|
1362 |
+
listeners yeah absolutely I think there
|
1363 |
+
are lots and lots of differences I think
|
1364 |
+
to take the kind of comparison between
|
1365 |
+
the two two things you just laid out
|
1366 |
+
imagine you take uh you know people are
|
1367 |
+
thinking by reaking into 100 protocols
|
1368 |
+
is the same as like you know taking 100x
|
1369 |
+
leverage position actually these two
|
1370 |
+
concepts are not at all related and the
|
1371 |
+
easiest way to see it is if you take a
|
1372 |
+
100x you know margin landing position if
|
1373 |
+
the market price of that asset moves 1%
|
1374 |
+
you will get liquidated you will lose
|
1375 |
+
your entire position whereas if I opt
|
1376 |
+
into 100 protocols and I don't act
|
1377 |
+
maliciously on any of them I will never
|
1378 |
+
get slashed it's a completely different
|
1379 |
+
thing"
|
1380 |
+
"the basic principle and I think when
|
1381 |
+
vitalic was discussing a recently I
|
1382 |
+
think the two kind of uh areas to look
|
1383 |
+
out for that he mentioned were the
|
1384 |
+
security and the centralization aspect
|
1385 |
+
so I think we talked a lot about the
|
1386 |
+
security aspect what are some
|
1387 |
+
considerations that we should have when
|
1388 |
+
we think about the centralization that
|
1389 |
+
Ian L might or might not introduce
|
1390 |
+
yeah I think this is a much much more
|
1391 |
+
nuanced topic you know I'm glad you
|
1392 |
+
brought this up um there are various
|
1393 |
+
layers of decentralization that you know
|
1394 |
+
protocols uh you know like ethereum may
|
1395 |
+
want to have and you know the most I
|
1396 |
+
think direct is operator
|
1397 |
+
decentralization does EigenLayer
|
1398 |
+
contribute to more pressures for
|
1399 |
+
operators to centralize maybe there are
|
1400 |
+
only like a few operators when there are
|
1401 |
+
lots and lots of services that need to
|
1402 |
+
be oper opted into and you
|
1403 |
+
know the answer to this is you know
|
1404 |
+
in in the structure that we are building
|
1405 |
+
in igon we want to minimize the pressure
|
1406 |
+
to centralize so this is a kind of like
|
1407 |
+
an operating principle that we are
|
1408 |
+
taking in building EigenLayer and you
|
1409 |
+
know if a different team was building
|
1410 |
+
EigenLayer they would operate on maybe
|
1411 |
+
different principles but like I said we
|
1412 |
+
came into the space because of like you
|
1413 |
+
know particular ularly building on
|
1414 |
+
ethereum because of the shared values
|
1415 |
+
and so one of the particular things we
|
1416 |
+
do is can we try and encourage Services
|
1417 |
+
which do not require a lot of
|
1418 |
+
computational effort and this is how Ian
|
1419 |
+
da the first service is built on IG on I
|
1420 |
+
layer IG da is built to be horizontally
|
1421 |
+
scalable which means as you increase the
|
1422 |
+
number of nodes the system's performance
|
1423 |
+
keeps increasing rather than the I need
|
1424 |
+
to have a lot of node requirements on
|
1425 |
+
each node to satisfy a certain amount of
|
1426 |
+
bandwidth so for example systems like
|
1427 |
+
salana scale by vertical scaling each
|
1428 |
+
node needs to have more and more in
|
1429 |
+
order to actually do well and IG da
|
1430 |
+
scales horizontally which means the
|
1431 |
+
total performance of the system is the
|
1432 |
+
product of the amount of bandwidth
|
1433 |
+
available in a node times the number of
|
1434 |
+
nodes so you can increase it by like
|
1435 |
+
increasing the performance of a node or
|
1436 |
+
you can increase it by increasing the
|
1437 |
+
number of nodes and because the system
|
1438 |
+
is horizontally scaling decentralization
|
1439 |
+
itself becomes
|
1440 |
+
scalability the more nodes you have the
|
1441 |
+
more bandwidth you have and therefore
|
1442 |
+
you can scale so this is a principle
|
1443 |
+
that we used to build
|
1444 |
+
igda okay beyond that what can we do to
|
1445 |
+
encourage decentralization and I think
|
1446 |
+
over time what will happen is there will
|
1447 |
+
be services that require more
|
1448 |
+
centralized you know operations that'll
|
1449 |
+
be Services which will require more
|
1450 |
+
decentralized operations and you know I
|
1451 |
+
give us this example this secret sharing
|
1452 |
+
imagine I have a secret and I want to
|
1453 |
+
store it in a decentralized network so
|
1454 |
+
each node has a little bit of the secret
|
1455 |
+
if all the nodes were just the same
|
1456 |
+
party it was all just coinbase like
|
1457 |
+
running hundreds of nodes then I don't
|
1458 |
+
get any secret sharing benefit is the
|
1459 |
+
same guy just like running 100 nodes and
|
1460 |
+
storing portions of the secret so if I'm
|
1461 |
+
running a secret sharing Network I
|
1462 |
+
actually want
|
1463 |
+
decentralization and so one of the
|
1464 |
+
really powerful things we're building
|
1465 |
+
with EigenLayer is expressivity and
|
1466 |
+
flexibility for a service to specify
|
1467 |
+
that they only want let's say more
|
1468 |
+
decentralized operators how do they know
|
1469 |
+
which operators are more decentralized
|
1470 |
+
they can choose to use the Oracles of
|
1471 |
+
their choosing to decide which are more
|
1472 |
+
decentralized and which are more
|
1473 |
+
centralized maybe something as simple as
|
1474 |
+
I want to exclude all the exchange nodes
|
1475 |
+
and I want to exclude all the major lstd
|
1476 |
+
nodes maybe a thing that somebody wants
|
1477 |
+
to do so there are lots of expressivity
|
1478 |
+
in the lay platform and if decentralized
|
1479 |
+
trust actually has utility which is what
|
1480 |
+
we all believe you know EigenLayer creates
|
1481 |
+
a market place for the decentralized
|
1482 |
+
nodes to potentially even more earn more
|
1483 |
+
than centralized nodes because you know
|
1484 |
+
you can't go to ethereum today and say
|
1485 |
+
like hey I'm going to pay a transaction
|
1486 |
+
fee but this transaction fee only goes
|
1487 |
+
to home stakers that's not a thing like
|
1488 |
+
your transaction fee goes to whoever
|
1489 |
+
picks up the transaction and like Minds
|
1490 |
+
it but on IG layer you can actually do
|
1491 |
+
it you can actually say like hey I only
|
1492 |
+
want to build an oracle which uses the
|
1493 |
+
home
|
1494 |
+
stakers and you know so we will find out
|
1495 |
+
the market value of decentralized trust
|
1496 |
+
by actually allowing EigenLayer to exist
|
1497 |
+
and our thesis is you know there is
|
1498 |
+
enough interesting things to be built
|
1499 |
+
that decentralized trust has a real
|
1500 |
+
value and actually for the first time
|
1501 |
+
very first time in ethereum
|
1502 |
+
decentralized nodes could earn something
|
1503 |
+
more than centralized notes till now all
|
1504 |
+
is the centralized nodes are better yeah
|
1505 |
+
that's actually a huge reason why I was
|
1506 |
+
very excited to invest in N layer is
|
1507 |
+
because one of my big thesis is I
|
1508 |
+
believe crypto is the best way to create
|
1509 |
+
a market for anything um and I think
|
1510 |
+
this is the first market for actual
|
1511 |
+
decentralized trust you can actually put
|
1512 |
+
a value like a dollar amount fee value
|
1513 |
+
on how much people want to pay different
|
1514 |
+
type of stakers and what sort of
|
1515 |
+
centralization they actually want to see
|
1516 |
+
beyond the posturing you see on Twitter
|
1517 |
+
because now people can put the money
|
1518 |
+
with their mouth this so I'm very
|
1519 |
+
excited for that um and I love to kind
|
1520 |
+
of talk about the commercial aspect as
|
1521 |
+
well because one Trend that I saw in the
|
1522 |
+
past few years is you know projects
|
1523 |
+
verticalized into their own
|
1524 |
+
infrastructure so you see Taps like dydx
|
1525 |
+
becoming their own chain you see some uh
|
1526 |
+
you know guilds or games like Merit
|
1527 |
+
Circle you know verticalized into their
|
1528 |
+
own chain so it seems like the market is
|
1529 |
+
almost rewarding projects for becoming
|
1530 |
+
infrastructure for
|
1531 |
+
verticalized to ig layer since you know
|
1532 |
+
IG layer is basically telling everybody
|
1533 |
+
that hey you don't need to do that you
|
1534 |
+
can just simply use existing security
|
1535 |
+
from ethereum so from a commercial angle
|
1536 |
+
you know what drives founders of you
|
1537 |
+
know abss of apps to use EigenLayer
|
1538 |
+
versus becoming an L1 or L2 themselves
|
1539 |
+
the way to think about it
|
1540 |
+
is if you are an AVS founder what are
|
1541 |
+
the choices on the table option one
|
1542 |
+
build with your own like token and your
|
1543 |
+
own trust Network and option to build on
|
1544 |
+
top of an existing trust Network like
|
1545 |
+
ethereum I and you know deploy your
|
1546 |
+
service and you know in the simplest
|
1547 |
+
world one would say maybe a lot of avss
|
1548 |
+
would want to get started off as the
|
1549 |
+
second one which is you know um use uh
|
1550 |
+
ethereum and and you know find product
|
1551 |
+
Market fit and then maybe like go and do
|
1552 |
+
their own
|
1553 |
+
thing"
|
1554 |
+
"and you know maybe this analogy
|
1555 |
+
that I recently came up with may be
|
1556 |
+
useful imagine you go into a store you
|
1557 |
+
know you go into a mall and then there
|
1558 |
+
is this main store that says that hey
|
1559 |
+
you have to put up a deposit you know if
|
1560 |
+
you come and steal anything here you
|
1561 |
+
will lose your deposit and then you know
|
1562 |
+
I come in and say hey anyway the main
|
1563 |
+
store you're putting up a $100 deposit
|
1564 |
+
to enter why don't you make a promise
|
1565 |
+
that you know with this $100 you will
|
1566 |
+
not steal anything even on the other
|
1567 |
+
smaller stores in the mall they say yeah
|
1568 |
+
you know now it's in your control to not
|
1569 |
+
steal at the mall right like it's very
|
1570 |
+
different from taking a margin lending
|
1571 |
+
or any other kind of like financial
|
1572 |
+
position so the risk is endogeneous to
|
1573 |
+
the Staker except smart contract risk
|
1574 |
+
and smart contract risk is just
|
1575 |
+
pervasive in all of blockchains and
|
1576 |
+
that's just what it is right and even
|
1577 |
+
that we are trying to build a very
|
1578 |
+
cautious govern system in the beginning
|
1579 |
+
over time these governance features can
|
1580 |
+
be removed but that's the trade-off that
|
1581 |
+
we're taking is be cautious in
|
1582 |
+
protecting the stake so you know to take
|
1583 |
+
another like mental model that people
|
1584 |
+
have which is I think very erroneous
|
1585 |
+
when 100 Protocols are sharing common
|
1586 |
+
stake the model is oh you know maybe
|
1587 |
+
there's no risk from the Staker side
|
1588 |
+
maybe there's a risk from the protocol
|
1589 |
+
side or from the AVS side and I think
|
1590 |
+
this is also erroneous and the reason is
|
1591 |
+
if there are 100 protocols Each of which
|
1592 |
+
can sustain $1 billion staking on their
|
1593 |
+
own let's say that's the 100 protocols
|
1594 |
+
and so which means they're paying some
|
1595 |
+
amount of fee which is sustaining that
|
1596 |
+
amount of State in that platform now if
|
1597 |
+
you aggregate all of this and create a
|
1598 |
+
$100 billion pool this can be restak
|
1599 |
+
across 100 protocols the fee is
|
1600 |
+
identical to the previous world because
|
1601 |
+
you know you're paying the same fee and
|
1602 |
+
you're able to sustain $100 billion now
|
1603 |
+
to attack any one protocol you need 100
|
1604 |
+
billion doar rather than requiring $1
|
1605 |
+
billion security has this nonlinearity
|
1606 |
+
where the the more stake you need to do
|
1607 |
+
an attack the more stake you need to
|
1608 |
+
actually profit out of and Escape in
|
1609 |
+
real world with all this kind of crazy
|
1610 |
+
stuff becomes impossible there is no
|
1611 |
+
liquidity on an exchange there is no you
|
1612 |
+
know tornado or whatever to go and hial
|
1613 |
+
transactions it's simply not possible to
|
1614 |
+
pull off an attack Beyond a certain
|
1615 |
+
scale so there's hardening of security
|
1616 |
+
that actually happens at scale so that's
|
1617 |
+
the the other I think model which is
|
1618 |
+
missing because when people are thinking
|
1619 |
+
about 100 protocols sharing the same
|
1620 |
+
stake they're thinking the amount of
|
1621 |
+
Stak is going to remain the same as the
|
1622 |
+
number of protocols increases but that's
|
1623 |
+
not the case as more and more protocol
|
1624 |
+
bring more and more fees the amount of
|
1625 |
+
stake will keep increasing so this is a
|
1626 |
+
market equilibrium and and another
|
1627 |
+
feature that we're building with IG
|
1628 |
+
layer is what we call attributable
|
1629 |
+
security when 100 Protocols are sharing
|
1630 |
+
a common pool of let's say 100 billion
|
1631 |
+
dollars of stake there may be one
|
1632 |
+
protocol which says hey you know I just
|
1633 |
+
not only want to have this PO olded
|
1634 |
+
security but I also want to have unique
|
1635 |
+
attributable security just to myself
|
1636 |
+
which means even if all the protocols
|
1637 |
+
get attack simultaneously I should be
|
1638 |
+
able to slash and redistribute let's say
|
1639 |
+
$10 billion because I'm coinbase I want
|
1640 |
+
to you know be very sure I want to be
|
1641 |
+
able to re you know slash and
|
1642 |
+
redistribute $10 billion on my own you
|
1643 |
+
can do this on EigenLayer EigenLayer
|
1644 |
+
gives you an ability to express both
|
1645 |
+
unique attributable security as well as
|
1646 |
+
pool Security in a common system and the
|
1647 |
+
power of pool security is very similar
|
1648 |
+
to why like nation states have like
|
1649 |
+
security functions cities don't have
|
1650 |
+
security functions is because there is a
|
1651 |
+
hardening of security at scale so that's
|
1652 |
+
um so one of the things we did as
|
1653 |
+
you know we thought through like what
|
1654 |
+
are the incentives of the F you know of
|
1655 |
+
the protocols we know that crypto runs
|
1656 |
+
on incentives if the incentive is not
|
1657 |
+
aligned people are not going to come and
|
1658 |
+
build on top of us one of the things we
|
1659 |
+
did is to break the binary choice
|
1660 |
+
between hey I stake my own token or I
|
1661 |
+
get security from ethereum we support
|
1662 |
+
natively what we call dual staking dual
|
1663 |
+
staking means I as an ABS can borrow
|
1664 |
+
trust from two
|
1665 |
+
distinct parties one is stakers of my
|
1666 |
+
own token whose whose interests are
|
1667 |
+
directly aligned with like the protocols
|
1668 |
+
well-being because you know they have
|
1669 |
+
exposure to the token and a neutral high
|
1670 |
+
value Quorum which is coming from
|
1671 |
+
ethereum so you have we have this dual
|
1672 |
+
Quorum model which is a very popular
|
1673 |
+
model among the many AVS even if they're
|
1674 |
+
launching on a single eorum to begin
|
1675 |
+
with over time they have the idea to
|
1676 |
+
actually build their own other Corum and
|
1677 |
+
instead of forcing a binary choice where
|
1678 |
+
we say Oh either you choose your your
|
1679 |
+
own token Corum or you choose you know
|
1680 |
+
the Eid Korum you can say oh I'm sending
|
1681 |
+
80% of the fees to the E Korum and 20%
|
1682 |
+
to my own Quorum today and over time I'm
|
1683 |
+
going to maybe spend send more to my
|
1684 |
+
Corum and less to ethereum maybe at some
|
1685 |
+
point I may even send zero to the
|
1686 |
+
ethereum cor and send all the value to
|
1687 |
+
myself so what this means is specific
|
1688 |
+
specifically if you try to use some kind
|
1689 |
+
of a discounted cash flow model to try
|
1690 |
+
to Value like an AVS you know uh token
|
1691 |
+
you might say that the total value that
|
1692 |
+
can be accured by the AVS because you
|
1693 |
+
have and the thing is this decision
|
1694 |
+
between how much value goes to the AVS
|
1695 |
+
token versus how much value goes to eth
|
1696 |
+
is decided by the avss governance which
|
1697 |
+
which will be in their own native token
|
1698 |
+
so the at the end of the day EigenLayer
|
1699 |
+
is continuous and pure optionality like
|
1700 |
+
you have the option to use e if it is
|
1701 |
+
beneficial to you you have the option to
|
1702 |
+
opt out if it is beneficial to you and
|
1703 |
+
what this does is it makes it breaks
|
1704 |
+
this binary choice and in in this world
|
1705 |
+
the value of the AVS token with igon
|
1706 |
+
layer is actually only greater than the
|
1707 |
+
value in the absence of wagon layer
|
1708 |
+
because adding an option to consume
|
1709 |
+
additional Security in a way that you
|
1710 |
+
can opt in and out as needed doesn't
|
1711 |
+
increase your like uh you know uh cost
|
1712 |
+
basis so that's the first first thing is
|
1713 |
+
the dual token model basically like
|
1714 |
+
completely breaks this artificial
|
1715 |
+
tradeoff and makes it very very smooth
|
1716 |
+
for people to like borrow as much
|
1717 |
+
security as they need to keep their
|
1718 |
+
platform in in continuous utility okay
|
1719 |
+
so in in this case one of the downstream
|
1720 |
+
questions I get is hey does it mean that
|
1721 |
+
over time uh you know services will
|
1722 |
+
launch on eorum and eventually just
|
1723 |
+
migrate on their own and you know this
|
1724 |
+
is really a question of whether igen
|
1725 |
+
layer is viable not only as a
|
1726 |
+
bootstrapping platform for avss but also
|
1727 |
+
as a continuous service platform for
|
1728 |
+
avss and so it's incumbent on us to find
|
1729 |
+
ways to create synergies across these
|
1730 |
+
avss in a way that they actually want to
|
1731 |
+
stay rather than they are stuck with us
|
1732 |
+
and you know we have this you know
|
1733 |
+
entrenched Monopoly to like keep this
|
1734 |
+
platform going and there are many
|
1735 |
+
interesting ways we can actually do it"
|
1736 |
+
"and one way you know I pointed to
|
1737 |
+
examples of the cloud early on and one
|
1738 |
+
of the really powerful things Amazon's
|
1739 |
+
cloud is called ec2 which is elastic
|
1740 |
+
Cloud compute right an elastic compute
|
1741 |
+
is the idea that I can borrow as much
|
1742 |
+
computer as I want and EigenLayer is
|
1743 |
+
elastic scaling of security you know if
|
1744 |
+
Amazon's ec2 like ion is es2 and es2 is
|
1745 |
+
basically elastic scaling of security
|
1746 |
+
which is you can borrow how much
|
1747 |
+
security you want and so why is this
|
1748 |
+
meaningful imagine a Bridge you know
|
1749 |
+
who's doing a weekly transaction volume
|
1750 |
+
of like you know anywhere between 10
|
1751 |
+
million and 200 million okay so now how
|
1752 |
+
much security do I need if I have to
|
1753 |
+
provision security separately for the
|
1754 |
+
bridge I need to provision worst case
|
1755 |
+
200 million so I need to have 200
|
1756 |
+
million of security just for my bridge
|
1757 |
+
but in the EigenLayer worldview there is
|
1758 |
+
this common huge pool of security I can
|
1759 |
+
randomly pull the amount of security
|
1760 |
+
that I want exactly like the cloud which
|
1761 |
+
am across all the services creating a
|
1762 |
+
big compute platform from which you can
|
1763 |
+
pull the amount of compute that you want
|
1764 |
+
randomly and that's exactly what happens
|
1765 |
+
with I so this reduces dramatically the
|
1766 |
+
cost of security because you're not over
|
1767 |
+
provisioning for the worst case you're
|
1768 |
+
you're consuming security just in time
|
1769 |
+
how much you need this is one benefit of
|
1770 |
+
EigenLayer there's also all kinds of other
|
1771 |
+
benefits where what happens is if a Dap
|
1772 |
+
consumes multiple EigenLayer Services I
|
1773 |
+
want an AAL I want a DA I want some
|
1774 |
+
other thing instead of paying for
|
1775 |
+
security separately for each of these
|
1776 |
+
Services they can just pay one time
|
1777 |
+
because the same pole of security is
|
1778 |
+
backing all of these services so there
|
1779 |
+
is an economy of scale in Igan lay that
|
1780 |
+
actually incentivizes services that kind
|
1781 |
+
of are mutually synergistic to stay
|
1782 |
+
together so these are you can create
|
1783 |
+
almost what what I call like a uh X
|
1784 |
+
Market bundling like instead of BU you
|
1785 |
+
know somebody could have thought and
|
1786 |
+
said oh let let me create a new
|
1787 |
+
middleware which is an oracle plus da
|
1788 |
+
plus AI together but like who knows how
|
1789 |
+
to build an oracle plus da plus AI
|
1790 |
+
together in today's market condition
|
1791 |
+
like figuring out how to build one is
|
1792 |
+
already a huge lift so the EigenLayer
|
1793 |
+
allows postmarket bundling of these
|
1794 |
+
Services into like useful things that
|
1795 |
+
Services can consume reducing the cost
|
1796 |
+
basis as well as offering a consumer
|
1797 |
+
segment across these different Services
|
1798 |
+
just like you go to AWS and you have a
|
1799 |
+
bunch of SAS services and you just hook
|
1800 |
+
into like five you know a statistic is a
|
1801 |
+
typical web2 app has 15 SAS Services
|
1802 |
+
integrated in the back end something
|
1803 |
+
like that could happen on IG and I think
|
1804 |
+
another kind of under uh explored
|
1805 |
+
incentive for developers to stick around
|
1806 |
+
with i l long term is the fact that it
|
1807 |
+
enables kind of New Primitives to be
|
1808 |
+
built and one such new primitive that I
|
1809 |
+
came across on your Twitter is this idea
|
1810 |
+
of like co-processors for instance um
|
1811 |
+
and you kind of talked about this idea
|
1812 |
+
of like intelligent defi as well which
|
1813 |
+
is you know not something that at least
|
1814 |
+
I don't think you can build without ion
|
1815 |
+
layer so can you kind of break us down
|
1816 |
+
you know what exactly is a C- processor
|
1817 |
+
and what did you mean by intelligent
|
1818 |
+
defi yeah um a a Cod processor is kind
|
1819 |
+
of like a layer two system but Layer Two
|
1820 |
+
normally you think of as like a chain so
|
1821 |
+
this is one of the reasons I don't like
|
1822 |
+
the chain terminology so imagine I'm
|
1823 |
+
sitting on ethereum and I'm writing a
|
1824 |
+
smart contract program and you know
|
1825 |
+
maybe I'm on Unis Swap and and you know
|
1826 |
+
one of the things I want to do is
|
1827 |
+
instead of doing passive liquidity
|
1828 |
+
provisioning which is I just put it into
|
1829 |
+
a pool and you know fix a certain price
|
1830 |
+
level at which I'm provisioning
|
1831 |
+
liquidity instead I want to dynamically
|
1832 |
+
move around the liquidity right but then
|
1833 |
+
the question is who is doing it are you
|
1834 |
+
an active participant are you a passive
|
1835 |
+
participant what is going on and what
|
1836 |
+
might happen is somebody may come up
|
1837 |
+
with a machine learning or AI protocol
|
1838 |
+
which takes the history of all the
|
1839 |
+
transactions and moves around the
|
1840 |
+
liquidity like provisioning Spectrum
|
1841 |
+
right based on you know these hard
|
1842 |
+
inputs on the blockchain imagine that I
|
1843 |
+
can actually get high integrity
|
1844 |
+
provision of this service which means
|
1845 |
+
when the service says that this is the
|
1846 |
+
right like you know if I ran this AI on
|
1847 |
+
this history and this is the output I
|
1848 |
+
get and it's absolutely correct if you
|
1849 |
+
had this access and what you could do is
|
1850 |
+
you could write you know in uh in your
|
1851 |
+
D5 program that hey I'm I'm a passive
|
1852 |
+
provider but I'm provisioning liquidity
|
1853 |
+
to this AI protocol and you know I'm
|
1854 |
+
just hands off after that point and the
|
1855 |
+
AI like sits and keeps adjusting your
|
1856 |
+
like you know liquidity range and this
|
1857 |
+
is a really like interesting service if
|
1858 |
+
it could be built but it's not possible
|
1859 |
+
to write this in evm or you know you
|
1860 |
+
know fit it into the small gas limit of
|
1861 |
+
ethereum but if I had an EigenLayer
|
1862 |
+
service that I can sit and call on on
|
1863 |
+
top of like ethereum the these nodes run
|
1864 |
+
the AI service offchain and you know
|
1865 |
+
sign off on the in the output of this AI
|
1866 |
+
service and then put it on top of
|
1867 |
+
ethereum back it with a certain amount
|
1868 |
+
of Economic Security now you have a
|
1869 |
+
rigid input that the protocol can take
|
1870 |
+
and move around this liquidity based on
|
1871 |
+
that this becomes really really powerful
|
1872 |
+
because now you know we called you know
|
1873 |
+
this thing smart contracts right and you
|
1874 |
+
know smart contracts you know as they
|
1875 |
+
exist today are rigid but not that smart
|
1876 |
+
not that intelligent right you know
|
1877 |
+
smart means like oh is it an agent is it
|
1878 |
+
like doing complex like you know
|
1879 |
+
adaptations you have to write it in
|
1880 |
+
simple easy code like you know in Unis
|
1881 |
+
swap has this curve called XY equals K
|
1882 |
+
which is like the first kind of simple
|
1883 |
+
programmatic thing that one might think
|
1884 |
+
of and what if instead like you had a
|
1885 |
+
complex
|
1886 |
+
expressivity while not giving up
|
1887 |
+
rigidity or correctness how can I get
|
1888 |
+
smart and you know accurate execution
|
1889 |
+
simultaneously and that's what Ian layer
|
1890 |
+
promises there are other Technologies
|
1891 |
+
like ZK proofs which could give you this
|
1892 |
+
but they're very very expensive today
|
1893 |
+
you know running a ZK proof may be as
|
1894 |
+
expensive as 100,000 times just running
|
1895 |
+
the software you know this is this is
|
1896 |
+
possible for simple applications but
|
1897 |
+
when I'm when you're talking about
|
1898 |
+
running complex AI this cost just like
|
1899 |
+
blows up out of control whereas on IG
|
1900 |
+
layer you don't incur such a cost so
|
1901 |
+
that's that's the idea of cryptoeconomic
|
1902 |
+
co-processors I'm going to link your
|
1903 |
+
Tweet in the show notes below as well
|
1904 |
+
for anyone who wants to check out this
|
1905 |
+
idea because I think this is one of the
|
1906 |
+
more interesting directions that dii can
|
1907 |
+
take that can really Revitalize um now S
|
1908 |
+
I think my last question for you just to
|
1909 |
+
wrap this up is uh let's assume that
|
1910 |
+
there are many parallel realities and
|
1911 |
+
we're able to zoom out and see all these
|
1912 |
+
realities and in one reality we have IG
|
1913 |
+
layer at its most successful and then
|
1914 |
+
one where everything's gone wrong
|
1915 |
+
something has you horrible happen
|
1916 |
+
something horrible has happened so what
|
1917 |
+
would EigenLayer look like in these two
|
1918 |
+
Universe like what is the most kind of
|
1919 |
+
successful outcome you can see and the
|
1920 |
+
least successful outcome for EigenLayer
|
1921 |
+
the most successful outcome for IG layer
|
1922 |
+
would be that you know it it accelerates
|
1923 |
+
this whole crypto Vision which is that
|
1924 |
+
we can actually enable anybody to come
|
1925 |
+
and build new and interesting services
|
1926 |
+
on top of a common coordinatEigenLayer"
|
1927 |
+
"and so what the means is you have this
|
1928 |
+
Rich world of not only like you know we
|
1929 |
+
talk about end users owning assets but
|
1930 |
+
also developers owning the platform or
|
1931 |
+
like working on immutable platforms on
|
1932 |
+
which they're building their projects so
|
1933 |
+
their long-term source of sustenance is
|
1934 |
+
actually like really rewarded so many
|
1935 |
+
people coming and building new
|
1936 |
+
interesting Services you know a rich and
|
1937 |
+
vibrant economy of consumption of these
|
1938 |
+
services to build things like the open
|
1939 |
+
metav ver to build our decentralized AGI
|
1940 |
+
to build things like you know secure uh
|
1941 |
+
private homomorphic encryption all kinds
|
1942 |
+
of interesting things running on top of
|
1943 |
+
this common substrate so that's what the
|
1944 |
+
most successful interesting world for
|
1945 |
+
looks like what is the most catastrophic
|
1946 |
+
thing that can happen uh we think about
|
1947 |
+
this a lot you know because we want to
|
1948 |
+
make sure that we maximize the
|
1949 |
+
likelihood of the successful outcome and
|
1950 |
+
minimize is the likelihood of the
|
1951 |
+
catastrophic outcome what would a
|
1952 |
+
catastrophic outcome be something got
|
1953 |
+
hacked right and you know people lost
|
1954 |
+
money I think that would be a
|
1955 |
+
catastrophic outcome uh we we take a lot
|
1956 |
+
of precaution to try to ensure that
|
1957 |
+
that's very unlikely but in blockchains
|
1958 |
+
you know you we don't know these are new
|
1959 |
+
and new systems so there's always some
|
1960 |
+
risk that you know nobody understands so
|
1961 |
+
that's that's one one aspect that could
|
1962 |
+
be some smart contract problems in the
|
1963 |
+
uh uh in the EigenLayer ecosystem that
|
1964 |
+
leads to you know some kind of loss of
|
1965 |
+
funds okay the other catastrophic
|
1966 |
+
outcome I can Envision is something
|
1967 |
+
happening not in EigenLayer but some
|
1968 |
+
like you know layers on top and one kind
|
1969 |
+
of a layer on top is this
|
1970 |
+
financializatEigenLayer where something
|
1971 |
+
like you know there is this whole
|
1972 |
+
ecosystem of liquid reaking tokens and
|
1973 |
+
what they do is they take people who
|
1974 |
+
have staged uh you know in the IG layer
|
1975 |
+
protocol and issue like a receipt token
|
1976 |
+
which is representing their position in
|
1977 |
+
EigenLayer this itself I think is not at
|
1978 |
+
all harmful like having a liquid
|
1979 |
+
representation of your token actually
|
1980 |
+
buffers the system quite heavily because
|
1981 |
+
when somebody has if you don't have a
|
1982 |
+
liquid reaking position what might
|
1983 |
+
happen is if somebody uh has a staged
|
1984 |
+
position and wants to go and
|
1985 |
+
collateralize it to like do Ling or
|
1986 |
+
borrowing or whatever and they get
|
1987 |
+
liquidated then the only way to like
|
1988 |
+
clear off their loan is to go and
|
1989 |
+
withdraw from Ian lay and from ethereum
|
1990 |
+
their stake and this leads to like you
|
1991 |
+
know uh pressures into the protocol into
|
1992 |
+
the IG protocol as well as into ethereum
|
1993 |
+
itself and what a liquid reaking token
|
1994 |
+
does is by issuing a fungible
|
1995 |
+
representation which is a token that can
|
1996 |
+
just be that change hands instead of you
|
1997 |
+
know actually going and withdrawing it
|
1998 |
+
actually buffers the risk out of the
|
1999 |
+
deeper layers of the stack but what we
|
2000 |
+
see happening which might be a risk to
|
2001 |
+
the financialized infrastructure on top
|
2002 |
+
is people taking leverage on top of
|
2003 |
+
their liquid reaking positions you know
|
2004 |
+
when people are worried about leverage
|
2005 |
+
in igen lay this is the place we should
|
2006 |
+
focus on is are people lending and
|
2007 |
+
borrowing against their liquid reaking
|
2008 |
+
tokens in a kind of unmeasured you know
|
2009 |
+
way you know ideally there is no
|
2010 |
+
leverage but at you know in practice
|
2011 |
+
leverage should be be kept very minimal
|
2012 |
+
and this is where I I would urge The
|
2013 |
+
Lending protocols for example to urge
|
2014 |
+
caution when estimating the value of a
|
2015 |
+
liquid reaking token instead of like
|
2016 |
+
pegging it at it will always be one as
|
2017 |
+
to one to eat they should take cautious
|
2018 |
+
approach so that people don't take
|
2019 |
+
excess risk and externalize it onto
|
2020 |
+
other parties who may then have lent
|
2021 |
+
their eath into these Landing protocols
|
2022 |
+
and so on so that's the place where I
|
2023 |
+
can see some kind of financialization go
|
2024 |
+
wrong this is one of the reasons we
|
2025 |
+
don't necessarily either build these
|
2026 |
+
liquidy staking tokens or you know
|
2027 |
+
Landing platforms but we do want to urge
|
2028 |
+
all the users to exercise caution at
|
2029 |
+
these layers to minimize this kind of an
|
2030 |
+
outcome yeah well s I'm really
|
2031 |
+
appreciative of how candid you are with
|
2032 |
+
this and I look forward to seeing you
|
2033 |
+
make sure that the Universe we live in
|
2034 |
+
is the first one and not the second one
|
2035 |
+
um so thank you so much for coming on
|
2036 |
+
the show and we're going to put your
|
2037 |
+
socials in the show notes below as well
|
2038 |
+
so for listeners at home or if you're
|
2039 |
+
watching this on YouTube just click on
|
2040 |
+
the drop Dr down and you can follow
|
2041 |
+
instram on Twitter so thank you so much
|
2042 |
+
for coming on absolutely really enjoyed
|
2043 |
+
this conversation Jason hey thanks for
|
2044 |
+
supporting another episode of The Block
|
2045 |
+
wrench podcast if you've enjoyed this
|
2046 |
+
episode please give us a festar rating
|
2047 |
+
on Spotify and apple podcast or whatever
|
2048 |
+
platform you're listening to this on it
|
2049 |
+
really helps us a lot or if you prefer
|
2050 |
+
YouTube you can subscribe to our Channel
|
2051 |
+
on YouTube as well to not miss an
|
2052 |
+
episode I'd love to hear from you guys
|
2053 |
+
as well and I personally make sure to
|
2054 |
+
read every single comment on YouTube or
|
2055 |
+
tweets that are directed at me so feel
|
2056 |
+
free to leave a comment there let us
|
2057 |
+
know what project you want us to bring
|
2058 |
+
on or what trends you want us to talk
|
2059 |
+
about or tweet at me at Mr Jason Troy or
|
2060 |
+
at theblock crunch on the platform
|
2061 |
+
previously known as Twitter currently
|
2062 |
+
known as X and thank you so much for
|
2063 |
+
supporting and I'll see you in the next
|
2064 |
+
episode"
|