From: Ben Vulpes <benkay@gmail•com>
To: Jonas Schnelli <dev@jonasschnelli•ch>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Virtual Notary.
Date: Fri, 22 May 2015 18:46:12 -0700 [thread overview]
Message-ID: <CACMPkv=NL7mCLMiw-KcLDu61RgA1rsUmV7Sdn+KeMn6zi3a8yA@mail.gmail.com> (raw)
In-Reply-To: <555EF028.2010302@jonasschnelli.ch>
[-- Attachment #1: Type: text/plain, Size: 3419 bytes --]
I cannot let http://www.deedbot.org go unmentioned on this thread.
On Friday, May 22, 2015, Jonas Schnelli <dev@jonasschnelli•ch> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > * 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.
>
>
> Hi Emin
>
> This is going into the right direction. Well done!
> The certificates (X.509/p12) are far more enduser-friendly than just a
> normal PoE hash.
>
> Your site needs some UX love and i just tried to OR_RETURN a
> Email-Address-Verification. But after creating a 0.0001 tx and waiting
> for two confirmations it still said that the payment has not yet been
> received. There is probably something broken regarding the bitcoin
> payment verification.
>
> The weather and real estate notarization definitively needs a „US
> only“ badge somewhere.
>
> Two ideas:
> - - Maybe adding a way of decentralize your notary service log via a
> opensource p2p daemon (obviously sensitive data should be somehow
> encrypted)?
> - - Adding a opensource UI app to examine certs (maybe offline capable
> with p2p daemon chain as mentioned above). This could prove
> independence from your website/service.
>
> </jonas>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQIcBAEBAgAGBQJVXvAoAAoJECnUvLZBb1PsJpsQAKRYDUTUYA59765w0jbBlK+S
> ArxpaxwPmG7ZLhDYoTHJ/welvXsMSzREZrJNKYl7LBHQBPldeTRQHfHwH05qiwBL
> H5rC+BTyaglud3x7Bxo0fNrXJB4tkfX2ykPJs+2bqPi9OE0uVlXi2Vh/6cV1U/Uq
> RWRfpa19GnSE7IRft5G19FVsG8hrrpuLhzVraAQeZTLyGBKd+hlpjI/qr6TOl8ra
> 5K3bFb2J1+UoaFXLlKCSsSx+9PsydlcJFwnr2H/Z7r1M39j5XYag3Ba6W58ats4z
> 6DCTL1xRVOCTNDbVgkYzZUDCtv5oDspQ2S0nauJLDVz5ADUaZ+bsmBFwseo+XuZV
> TLUxsYfPsqEzUKF2a7ZfMjQG0EUx8oh5DU+o1F5wcBSXDOM+ucdOGYbMrBMV1i9W
> GoPUN1QPkqfUTTRiYYnzP2ySyPUoJqZrcwEB7E7nV8O2xE4Q00zCDlOSqU8aVl7j
> 9lIs/sTpcK5S0kFfc68n6NVlWYU+CBdGlnmvMdbEkydV2P3ft1+THqQ8LNiYRhWX
> 7kHzgG58yUQjvgsOEEb4xTXgA5u4euxBVY+SwKN6cTXA7dWg1s39UEJroaKuXYN5
> iZTj2XkBtD+pwtUPIMs79Kb2/PZRGy7SJui2RbExFX1/8oBbHRV5Ii6+MNw11RNz
> RTV0kHof6+6u1BFYHTFX
> =UmgJ
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net <javascript:;>
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 4201 bytes --]
next prev parent reply other threads:[~2015-05-23 1:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 9:00 Jonas Schnelli
2015-05-23 1:46 ` Ben Vulpes [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-20 10:25 Emin Gün Sirer
2015-05-20 15:54 ` Jeff Garzik
2015-05-25 18:07 ` Mike Hearn
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='CACMPkv=NL7mCLMiw-KcLDu61RgA1rsUmV7Sdn+KeMn6zi3a8yA@mail.gmail.com' \
--to=benkay@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=dev@jonasschnelli$(echo .)ch \
/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