From: "Emin Gün Sirer" <el33th4x0r@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Virtual Notary.
Date: Wed, 20 May 2015 06:25:01 -0400 [thread overview]
Message-ID: <CAPkFh0tWykVJU-9mCTR95eqUF0B5TO-ZO7B3L0wf_QYAmAuuBA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
Hi everyone,
Given the recent discussions on projects that use the Bitcoin blockchain to
record factoids, people on this list might be interested in the Virtual
Notary project. Virtual Notary is essentially an online witness (aka
attestor) to online factoids. It can provide:
* proof of Bitcoin funds (without revealing public addresses or fund
location on the blockchain)
* proof of Bitcoin address ownership
* proof of Tweet
* proof of real estate value
* proof of DNS ownership
* proof of existence
* proof of web page contents
* proof of weather conditions
The factoids can be recorded on the blockchain (if you pay for the
transaction with Bitcoin or PayPal), or they can be part of a free
attestation chain that we maintain. The website provides a permanent URL to
the factoids it generates; it also provides an X.509 certificate that you
can download and keep safe in perpetuity, independent of the website.
The link to the website is here:
http://virtual-notary.org
The link to the writeup describing the various factoids and their use cases
is here:
http://hackingdistributed.com/2013/06/20/virtual-notary-intro/
We are actively looking for people who are interested in developing the
service further. Specifically, if you have suggestions for how to extend
the service, for new proof/factoid types, or for how to build a business
case around the core idea, please let us know.
Best,
- egs
[-- Attachment #2: Type: text/html, Size: 1963 bytes --]
next reply other threads:[~2015-05-20 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 10:25 Emin Gün Sirer [this message]
2015-05-20 15:54 ` Jeff Garzik
2015-05-25 18:07 ` Mike Hearn
2015-05-22 9:00 Jonas Schnelli
2015-05-23 1:46 ` Ben Vulpes
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=CAPkFh0tWykVJU-9mCTR95eqUF0B5TO-ZO7B3L0wf_QYAmAuuBA@mail.gmail.com \
--to=el33th4x0r@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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