1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
|
Delivery-date: Sat, 24 Feb 2024 08:22:15 -0800
Received: from mail-yb1-f192.google.com ([209.85.219.192])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBDB7DCGEYMLBBMFP5CXAMGQEWX3GVRQ@googlegroups.com>)
id 1rdun0-0003Aj-PA
for bitcoindev@gnusha.org; Sat, 24 Feb 2024 08:22:15 -0800
Received: by mail-yb1-f192.google.com with SMTP id 3f1490d57ef6-dcd94cc48a1sf2129410276.3
for <bitcoindev@gnusha.org>; Sat, 24 Feb 2024 08:22:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1708791728; x=1709396528; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:message-id:to:from:date:sender:from:to:cc:subject:date
:message-id:reply-to;
bh=NMiVHUTim9rHGM4Jp7AyfBuwnEUvIsn6m1TWbCqmFv0=;
b=TiYG3okM2bvsOpVRG5tS9A7RoBOhZUF0XK5mc6fFX4oBHdQN+bYi0Ar3aE1UQYY4N5
B9y4Ym4iEGUAi15yxrd1o3u9sQ58LsbjgB5k4TxLJd9M8WfMcFv/bIwFRTcK/ZqBG32b
EOq8LVFvHb38hV3sOPtNCs3WTFdb6Z1bHtXzCvmSvJjtV7f6IbZWtfAjVQ2B9SoUFwrG
1GUKo4r3QfTDEOkD0O4lR6KTi+Pl36OKA1RIcR4VqrZJvcfo+6PBEY2s9FgzbxQW2FyK
mK/zb6n0buZdcjLC0QSDrI54RhYiEqeeIgCI+FSdtlOUMB2JiVOtYsbKQ8uMLC1RseRE
FPXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1708791728; x=1709396528;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:message-id:to:from:date:x-beenthere:x-gm-message-state
:sender:from:to:cc:subject:date:message-id:reply-to;
bh=NMiVHUTim9rHGM4Jp7AyfBuwnEUvIsn6m1TWbCqmFv0=;
b=om778sJuToKMCED93D0drJED/PNQgKMQUoW8U3F+fCmIi/FnxLHPXJvHCDzEV/bELr
uvcHEKeQPA0sULElF6ZyE5AUTInDgTD2NNS+xAkVR3nRM/lCseGRpldMi2hGLxm/v8Ch
3LriqcSpj0iekwzv676ONT4r/2BUHc/QBlpNPGImb08OZ3LB7TqGHBiRJzBCGT/ZlaPO
EHJbLVKzWARk0HR7fmYXbvhFOHoiFlxwmesDQRl/nayqlcbO6wSegfy+U4hpM+1CNO+2
1Q4bc4e+zIQ3aHex63K9iXiiaNHyCfgpshlLrfhHPV+vp8iyfreJtV/+bwuXwRPhjbua
2WQA==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCWwSltPpzVy8OrQkVHhBO1BEEXsaOmx+uUKWgxfLr2C33ywceJMyqSbgTEkn1qF2jjt6bcYN+nWOEVGxMw99hRNdrRlMFY=
X-Gm-Message-State: AOJu0YwNhhZO/Ai1s7TPKooB68AwpCSHwvd0aFJiYocXP5Shq1DDEW1s
f6R9CvKocspjv6daH2efzA6j68HilWHFNA53dU899FqjuhFGiyUa
X-Google-Smtp-Source: AGHT+IH2U60u7D/Y5ElWr2rvMyHyC4TNVn9Y3glVOiBMrjNHPPCOr8wIlF47QFpq9799V8MXiYCDEw==
X-Received: by 2002:a25:9987:0:b0:dcb:b3dd:4f95 with SMTP id p7-20020a259987000000b00dcbb3dd4f95mr1994370ybo.43.1708791728550;
Sat, 24 Feb 2024 08:22:08 -0800 (PST)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a25:d68b:0:b0:dcc:4b24:c0e0 with SMTP id n133-20020a25d68b000000b00dcc4b24c0e0ls2281757ybg.0.-pod-prod-06-us;
Sat, 24 Feb 2024 08:22:07 -0800 (PST)
X-Received: by 2002:a81:8306:0:b0:608:cea7:9499 with SMTP id t6-20020a818306000000b00608cea79499mr656138ywf.8.1708791727740;
Sat, 24 Feb 2024 08:22:07 -0800 (PST)
Received: by 2002:a05:690c:82:b0:607:ff99:461 with SMTP id 00721157ae682-608967b497ams7b3;
Wed, 21 Feb 2024 12:11:22 -0800 (PST)
X-Received: by 2002:a0d:d813:0:b0:607:8441:a294 with SMTP id a19-20020a0dd813000000b006078441a294mr131855ywe.5.1708546281338;
Wed, 21 Feb 2024 12:11:21 -0800 (PST)
Date: Wed, 21 Feb 2024 12:11:20 -0800 (PST)
From: buffrr <contact@buffrr.dev>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <e748ac07-1aca-4f1e-ad3e-aa57e4d6dc05n@googlegroups.com>
Subject: [bitcoindev] Scalable & Permissionless Bitcoin CA
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_218_2099956947.1708546280908"
X-Original-Sender: contact@buffrr.dev
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
<https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.7 (/)
------=_Part_218_2099956947.1708546280908
Content-Type: multipart/alternative;
boundary="----=_Part_219_1200458138.1708546280908"
------=_Part_219_1200458138.1708546280908
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
I=E2=80=99d like to discuss a project we=E2=80=99re developing called Space=
s, for creating=20
a scalable & permissionless ~250KB Bitcoin Certificate Authority. We=E2=80=
=99re=20
working on building a zk light client for the protocol using RISC0 zkVM[0]=
=20
and the protocol uses client-side validation. Leveraging Bitcoin & ZK, it=
=20
seems we could finally get decentralized PKI that works well and=20
lightweight enough to verify by end-users.
What makes Spaces scalable is that it introduces a concept of =E2=80=9Csubs=
paces=E2=80=9D=20
which are off-chain entities that have great autonomy. It is not exactly=20
like zk-rollups as the data itself is off-chain - although it may not=20
exactly fit into =E2=80=9Cvalidium=E2=80=9D either as data availability its=
elf is not a=20
major issue. Users hold their own inclusion proofs. The commitments posted=
=20
on-chain have a lifetime during which they=E2=80=99re able to transact on-c=
hain and=20
off-chain.
We=E2=80=99re at an early stage and welcome your feedback. For more technic=
al=20
details:
https://spacesprotocol.org
[0] https://dev.risczero.com/proof-system-in-detail.pdf
--=20
You received this message because you are subscribed to the Google Groups "=
Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/=
bitcoindev/e748ac07-1aca-4f1e-ad3e-aa57e4d6dc05n%40googlegroups.com.
------=_Part_219_1200458138.1708546280908
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
I=E2=80=99d like to discuss a project we=E2=80=99re developing called Space=
s, for creating a scalable & permissionless ~250KB Bitcoin Certificate =
Authority. We=E2=80=99re working on building a zk light client for the prot=
ocol using RISC0 zkVM[0] and the protocol uses client-side validation. Leve=
raging Bitcoin & ZK, it seems we could finally get decentralized PKI th=
at works well and lightweight enough to verify by end-users.<br /><br />Wha=
t makes Spaces scalable is that it introduces a concept of =E2=80=9Csubspac=
es=E2=80=9D which are off-chain entities that have great autonomy. It is no=
t exactly like zk-rollups as the data itself is off-chain - although it may=
not exactly fit into =E2=80=9Cvalidium=E2=80=9D either as data availabilit=
y itself is not a major issue. Users hold their own inclusion proofs. The c=
ommitments posted on-chain have a lifetime during which they=E2=80=99re abl=
e to transact on-chain and off-chain.<br /><br />We=E2=80=99re at an early =
stage and welcome your feedback. For more technical details:<br /><div><br =
/></div><div>https://spacesprotocol.org</div><div><br /></div><div>[0] http=
s://dev.risczero.com/proof-system-in-detail.pdf<br /></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/e748ac07-1aca-4f1e-ad3e-aa57e4d6dc05n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/e748ac07-1aca-4f1e-ad3e-aa57e4d6dc05n%40googlegroups.com</a>.=
<br />
------=_Part_219_1200458138.1708546280908--
------=_Part_218_2099956947.1708546280908--
|
