Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Unm5Y-0002m3-8k for bitcoin-development@lists.sourceforge.net; Sat, 15 Jun 2013 08:44:00 +0000 X-ACL-Warn: Received: from mail-we0-f172.google.com ([74.125.82.172]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Unm5W-0006O9-Sw for bitcoin-development@lists.sourceforge.net; Sat, 15 Jun 2013 08:44:00 +0000 Received: by mail-we0-f172.google.com with SMTP id q56so1138036wes.31 for ; Sat, 15 Jun 2013 01:43:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=W8L5F7jG7xtfqtiv2xhlqmsEsOG/vjIhN4PkRTqZ3bU=; b=Dwkm8FK9R98qoNiH2Bg6WH2qqztvC6mEXT2rNnWpSQCTPMv70ZnUTWJfe7hwToKAHF 1+dgY4A7ZjxaD8vPlut+ML2cl+9KP5uDs57wPTPbNiINPPC9+GF4zqmcH2T7TYYhVkho j1+y446K/wcYjDFZevH3CjVP0rJLzFXnXrz1HHbQZESCEaq37hfMC3XwJ6J3xrXuByxO kLs5owpQBPPuIVJxjIPDcuzri4ZZXPmuVVg9HNiPb8ZmpNKexgZHUmTUk14vm/u7n7fj COIUWe6XTqNWqGaO5CopEEy8D9PQsI/PHUFKe2Ey+DBXogEHBKbfNcbq/E8WpM6JiIPW 0VgQ== X-Received: by 10.181.12.1 with SMTP id em1mr704022wid.4.1371285832715; Sat, 15 Jun 2013 01:43:52 -0700 (PDT) Received: from [192.168.1.180] (host152-91-dynamic.54-79-r.retail.telecomitalia.it. [79.54.91.152]) by mx.google.com with ESMTPSA id fo10sm7873522wib.8.2013.06.15.01.43.50 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 15 Jun 2013 01:43:51 -0700 (PDT) References: <20130519132359.GA12366@netbook.cypherspace.org> <51BB8A58.7000308@petersson.at> <27BA300C-71B8-4AB1-9459-09975ABED8EB@dennisonbertram.com> <201306150157.07228.luke@dashjr.org> Mime-Version: 1.0 (1.0) In-Reply-To: <201306150157.07228.luke@dashjr.org> Content-Type: multipart/alternative; boundary=Apple-Mail-5FB12426-CC06-420B-90B2-323A19E150F4 Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: iPhone Mail (10A523) From: Dennison Bertram Date: Sat, 15 Jun 2013 10:43:48 +0200 To: Luke-Jr X-Gm-Message-State: ALoCoQkqda401V43hBVn5UXyTselBPWTPJJguF9HPpxS3AOd8MTU96j5NmlNpvCIB1g4fcYdDLUs X-Spam-Score: 1.3 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message 0.3 HTML_FONT_FACE_BAD BODY: HTML font face is not a word 0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars X-Headers-End: 1Unm5W-0006O9-Sw Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] is there a way to do bitcoin-staging? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jun 2013 08:44:00 -0000 --Apple-Mail-5FB12426-CC06-420B-90B2-323A19E150F4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable That is true, but someone is already running it as a service on the blockcha= in itself. See: https://www.proofofexistence.com/ You can imagine similar services cropping up for things like torrents, send= ing btc tweets, etc. While I am not saying these things are particularly ref= ined ideas in and of themselves, people should have an opportunity to play w= ith them, and better testnet.=20 Sent from my iPhone On Jun 15, 2013, at 3:57 AM, "Luke-Jr" wrote: > Timestamping ("proof of existence") doesn't need a coin at all. Just colle= ct=20 > all the hashes you need timestamped into a PoE merkle tree and add that to= the=20 > merged mining MT. It's pretty simple and straightforward, just needs someo= ne=20 > to implement it. >=20 > On Saturday, June 15, 2013 12:09:09 AM Dennison Bertram wrote: >> Have your seen 'proof of existence'? It's basically a bitcoin notary >> service that proves a document existed before it gets inserted into the >> blockchain. While a good idea- you could argue that it's blockchain spam >> as well- especially if one were to adapt it to high volumes in the future= >> for notarizing permanently things like tweets (for example) or combining >> it with something like colored coins. These are great ideas, but maybe >> better suited to a proto bitcoin without needing to fashion a brand new >> coin. --Apple-Mail-5FB12426-CC06-420B-90B2-323A19E150F4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
That is true, but someone is already running it as a service on the blo= ckchain itself. See:
https://www.proofofexistence.com= /

You can imagine similar  services cropping up for t= hings like torrents, sending btc tweets, etc. While I am not saying these th= ings are particularly refined ideas in and of themselves, people should have= an opportunity to play with them, and better testnet. 

Sent from my iPhone

On Jun 15, 201= 3, at 3:57 AM, "Luke-Jr" <luke@dashjr.= org> wrote:

Timestamping ("proof of existence") does= n't need a coin at all. Just collect
all the hashes you nee= d timestamped into a PoE merkle tree and add that to the
me= rged mining MT. It's pretty simple and straightforward, just needs someone <= /span>
to implement it.

On Saturda= y, June 15, 2013 12:09:09 AM Dennison Bertram wrote:
Have your seen 'proof of existence'? It's basically a bit= coin notary
service t= hat proves a document existed before it gets inserted into the
blockchain. While a good idea- you= could argue that it's blockchain spam
as well- especially if one were to adapt it to high volume= s in the future
for n= otarizing permanently things like tweets (for example) or combining
it with something like colore= d coins. These are great ideas, but maybe
better suited to a proto bitcoin without needing to fas= hion a brand new
coin= .
= --Apple-Mail-5FB12426-CC06-420B-90B2-323A19E150F4--