From: buffrr <contact@buffrr•dev>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Scalable & Permissionless Bitcoin CA
Date: Wed, 21 Feb 2024 12:11:20 -0800 (PST) [thread overview]
Message-ID: <e748ac07-1aca-4f1e-ad3e-aa57e4d6dc05n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1466 bytes --]
I’d like to discuss a project we’re developing called Spaces, for creating
a scalable & permissionless ~250KB Bitcoin Certificate Authority. We’re
working on building a zk light client for the protocol using RISC0 zkVM[0]
and the protocol uses client-side validation. Leveraging Bitcoin & ZK, it
seems we could finally get decentralized PKI that works well and
lightweight enough to verify by end-users.
What makes Spaces scalable is that it introduces a concept of “subspaces”
which are off-chain entities that have great autonomy. It is not exactly
like zk-rollups as the data itself is off-chain - although it may not
exactly fit into “validium” either as data availability itself is not a
major issue. Users hold their own inclusion proofs. The commitments posted
on-chain have a lifetime during which they’re able to transact on-chain and
off-chain.
We’re at an early stage and welcome your feedback. For more technical
details:
https://spacesprotocol.org
[0] https://dev.risczero.com/proof-system-in-detail.pdf
--
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 email 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.
[-- Attachment #1.2: Type: text/html, Size: 1783 bytes --]
reply other threads:[~2024-02-24 16:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e748ac07-1aca-4f1e-ad3e-aa57e4d6dc05n@googlegroups.com \
--to=contact@buffrr$(echo .)dev \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox