From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: From: Melvin Carvalho To: "Marc D. Wood" 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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


On 2 May 2015 at 00:57, Marc D. Wood <metamarc@metamarket.biz> wrote:
ME= TAmarket: Trustless Federated Marketplaces
>>> http://met= amarket.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<= br> 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<= br> 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 th= e core before he left?

https://github.com/bitcoi= n/bitcoin/commit/5253d1ab77fab1995ede03fb934edd67f1359ba8
=C2= =A0


---------------------------------------------------------------------------= ---
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-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--001a1134612c6aceda05150fb523--