Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <melvincarvalho@gmail.com>) id 1YoMkR-0003ST-Nf
	for bitcoin-development@lists.sourceforge.net;
	Sat, 02 May 2015 02:01:43 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.45 as permitted sender)
	client-ip=209.85.215.45; envelope-from=melvincarvalho@gmail.com;
	helo=mail-la0-f45.google.com; 
Received: from mail-la0-f45.google.com ([209.85.215.45])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YoMkQ-0002bo-7q
	for bitcoin-development@lists.sourceforge.net;
	Sat, 02 May 2015 02:01:43 +0000
Received: by laat2 with SMTP id t2so73694153laa.1
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 01 May 2015 19:01:35 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.47.73 with SMTP id b9mr10347996lbn.46.1430532095919;
	Fri, 01 May 2015 19:01:35 -0700 (PDT)
Received: by 10.112.154.103 with HTTP; Fri, 1 May 2015 19:01:35 -0700 (PDT)
In-Reply-To: <7cfbfe793dd4be50dd97cfc1fe937880.squirrel@server151.web-hosting.com>
References: <7cfbfe793dd4be50dd97cfc1fe937880.squirrel@server151.web-hosting.com>
Date: Sat, 2 May 2015 04:01:35 +0200
Message-ID: <CAKaEYhKxw+aUO_j6=nCAtNUw=5gSQ6TSGTa8YP1ATFHn-EW5_A@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: "Marc D. Wood" <metamarc@metamarket.biz>
Content-Type: multipart/alternative; boundary=001a1134612c6aceda05150fb523
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(melvincarvalho[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1YoMkQ-0002bo-7q
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [ANN] METAmarket - Trustless Federated
	Marketplaces
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 02 May 2015 02:01:43 -0000

--001a1134612c6aceda05150fb523
Content-Type: text/plain; charset=UTF-8

On 2 May 2015 at 00:57, Marc D. Wood <metamarc@metamarket.biz> wrote:

> METAmarket: Trustless Federated Marketplaces
> >>> http://metamarket.biz <<<
>
> * * *
> Introduction
>
> METAmarket is an open source protocol and proof-of-concept reference
> client specifying a trustless federated marketplace which uses Bitcoin as
> a universal currency and Bitmessage as a P2P communication network.
> Time-locked refund transactions ensure that incentives are aligned toward
> completing the trade without the need for trusted third parties. Systemic
> vulnerabilities such as transaction malleability are mitigated through the
> use of a federated reputation model. This document is a non-technical
> overview of how the METAmarket client and protocol work. For more
> technical details, see the protocol specification.
>
> Motivation
>
> Overly centralized marketplaces and payment services extract high fees,
> impose and abuse excessive control and remove any hope of privacy from
> users. As more commerce moves online, many consumers may find their
> lifetime history of purchases (including books, personal items and
> location details) for sale to advertisers, employers, curious neighbors,
> stalkers, political opponents and government agencies. An ideal system
> would be one of secure private transactions directly between buyer and
> seller without middle men collecting data or adding fees. Such systems are
> now feasible by combining recently developed technologies for anonymous
> decentralized payment and messaging systems.
>
> Client
>
> To use the marketplaces, a client application which implements the
> METAmarket protocol is required. The client is used to post, browse and
> execute trades. It also requires a Bitcoin Core wallet to handle payments
> and refunds. A working client is available at:
>
> http://github.com/metamarcdw/metamarket
>

Is there any relation between this and the work satoshi was putting into
the core before he left?

https://github.com/bitcoin/bitcoin/commit/5253d1ab77fab1995ede03fb934edd67f1359ba8

>
>
>
>
> ------------------------------------------------------------------------------
> 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
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--001a1134612c6aceda05150fb523
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 2 May 2015 at 00:57, Marc D. Wood <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:metamarc@metamarket.biz" target=3D"_blank">metamarc@metamarket.biz</a=
>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">ME=
TAmarket: Trustless Federated Marketplaces<br>
&gt;&gt;&gt; <a href=3D"http://metamarket.biz" target=3D"_blank">http://met=
amarket.biz</a> &lt;&lt;&lt;<br>
<br>
* * *<br>
Introduction<br>
<br>
METAmarket is an open source protocol and proof-of-concept reference<br>
client specifying a trustless federated marketplace which uses Bitcoin as<b=
r>
a universal currency and Bitmessage as a P2P communication network.<br>
Time-locked refund transactions ensure that incentives are aligned toward<b=
r>
completing the trade without the need for trusted third parties. Systemic<b=
r>
vulnerabilities such as transaction malleability are mitigated through the<=
br>
use of a federated reputation model. This document is a non-technical<br>
overview of how the METAmarket client and protocol work. For more<br>
technical details, see the protocol specification.<br>
<br>
Motivation<br>
<br>
Overly centralized marketplaces and payment services extract high fees,<br>
impose and abuse excessive control and remove any hope of privacy from<br>
users. As more commerce moves online, many consumers may find their<br>
lifetime history of purchases (including books, personal items and<br>
location details) for sale to advertisers, employers, curious neighbors,<br=
>
stalkers, political opponents and government agencies. An ideal system<br>
would be one of secure private transactions directly between buyer and<br>
seller without middle men collecting data or adding fees. Such systems are<=
br>
now feasible by combining recently developed technologies for anonymous<br>
decentralized payment and messaging systems.<br>
<br>
Client<br>
<br>
To use the marketplaces, a client application which implements the<br>
METAmarket protocol is required. The client is used to post, browse and<br>
execute trades. It also requires a Bitcoin Core wallet to handle payments<b=
r>
and refunds. A working client is available at:<br>
<br>
<a href=3D"http://github.com/metamarcdw/metamarket" target=3D"_blank">http:=
//github.com/metamarcdw/metamarket</a><br></blockquote><div><br></div><div>=
Is there any relation between this and the work satoshi was putting into th=
e core before he left?<br><br><a href=3D"https://github.com/bitcoin/bitcoin=
/commit/5253d1ab77fab1995ede03fb934edd67f1359ba8">https://github.com/bitcoi=
n/bitcoin/commit/5253d1ab77fab1995ede03fb934edd67f1359ba8</a><br></div>=C2=
=A0<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
---------------------------------------------------------------------------=
---<br>
One dashboard for servers and applications across Physical-Virtual-Cloud<br=
>
Widest out-of-the-box monitoring support with 50+ applications<br>
Performance metrics, stats and reports that give you Actionable Insights<br=
>
Deep dive visibility with transaction tracing using APM Insight.<br>
<a href=3D"http://ad.doubleclick.net/ddm/clk/290420510;117567292;y" target=
=3D"_blank">http://ad.doubleclick.net/ddm/clk/290420510;117567292;y</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div></div>

--001a1134612c6aceda05150fb523--