📅 Original date posted:2013-02-08
📝 Original message:There have been proposals to use the blockchain to establish
"identities". firstbits is a simple example. I would like to announce a
project that extends this idea to turn the blockchain into a "root CA"
that can sign arbitrary certificates. The purpose is to use these
certificates in the payment protocol, where some might consider
traditional centralized root CAs unsatisfactory.
Code is here: https://github.com/bcpki
Technical specification and full-length examples are found in the wiki.
I therefore spare myself from repeating the details here, even though,
of course, discussion about those details is welcome on this list.
Excerpt from README.md follows:
First, we have drafted a quite general specification for bitcoin certificates (protobuf messages) that allow for a variety of payment protocols (e.g. static as well as customer-side-generated payment addresses).
This part has surely been done elsewhere as well and is orthogonal to the goal of this project.
What is new here is the signatures _under_ the certificates.
We have patched the bitcoind to handle certificates, submit signatures to the blockchain, verify certificates against the blockchain, pay directly to certificates (with various payment methods), revoke certificates.
Signatures in the blockchain are stored entirely in the UTXO set (i.e. the unspend, unprunable outputs).
This seems to make signature lookup and verification reasonably fast:
it took us 10s in the mainnet test we performed (lookup is instant on the testnet, of course).
Payment methods include: static bitcoin addresses, client-side derived
payment addresses (pay-to-contract), pay-to-contract with multisig destinations (P2SH)
Full-length real-world examples for all payment methods are provided in the tutorial pages.
These examples have actually been carried out on testnet3.
For further details and specifications see the wiki.
timo hanke
Timo Hanke [ARCHIVE] /
npub1dd…pgp9a
2023-06-07 11:31:13
in reply to nevent1q…5cfm
Author Public Key
npub1ddqaln8xsfmy6sxqplt9sz5ev99kh052sveqsh02q7hmc3a6n68shpgp9aSeen on
wss://nostr21.comPublished at
2023-06-07 11:31:13Event JSON
{
"id": "d8842aba4c1d084041eaf86387e8357a7a7253c793def02dd00afe2507542218",
"pubkey": "6b41dfcce682764d40c00fd6580a99614b6bbe8a8332085dea07afbc47ba9e8f",
"created_at": 1686137473,
"kind": 1,
"tags": [
[
"e",
"e992a0596803801bdc60b39e6a8f2a9b5632f4cd93d71e49809fd4b4885dc86d",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2013-02-08\n📝 Original message:There have been proposals to use the blockchain to establish\n\"identities\". firstbits is a simple example. I would like to announce a\nproject that extends this idea to turn the blockchain into a \"root CA\"\nthat can sign arbitrary certificates. The purpose is to use these\ncertificates in the payment protocol, where some might consider\ntraditional centralized root CAs unsatisfactory. \n\nCode is here: https://github.com/bcpki\n\nTechnical specification and full-length examples are found in the wiki.\nI therefore spare myself from repeating the details here, even though,\nof course, discussion about those details is welcome on this list.\n\nExcerpt from README.md follows:\n\nFirst, we have drafted a quite general specification for bitcoin certificates (protobuf messages) that allow for a variety of payment protocols (e.g. static as well as customer-side-generated payment addresses).\nThis part has surely been done elsewhere as well and is orthogonal to the goal of this project.\nWhat is new here is the signatures _under_ the certificates.\n\nWe have patched the bitcoind to handle certificates, submit signatures to the blockchain, verify certificates against the blockchain, pay directly to certificates (with various payment methods), revoke certificates.\nSignatures in the blockchain are stored entirely in the UTXO set (i.e. the unspend, unprunable outputs). \nThis seems to make signature lookup and verification reasonably fast: \nit took us 10s in the mainnet test we performed (lookup is instant on the testnet, of course).\n\nPayment methods include: static bitcoin addresses, client-side derived\npayment addresses (pay-to-contract), pay-to-contract with multisig destinations (P2SH)\n\nFull-length real-world examples for all payment methods are provided in the tutorial pages.\nThese examples have actually been carried out on testnet3.\n\nFor further details and specifications see the wiki.\n\ntimo hanke",
"sig": "caa317a84b31c7250636532141f332f43cb171d931a6b26fcc619084646e40f754aa2107925f921054fab245c2402ba879fdc661f43b90d2a0a08e6e40cc7007"
}