Delivery-Date: Thu, 30 Apr 2015 10:18:19 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 1412B1E0E54
	for <archiver@seul.org>; Thu, 30 Apr 2015 10:18:17 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 08B4521003;
	Thu, 30 Apr 2015 14:18:14 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 4BE3D20EC0
 for <tor-talk@lists.torproject.org>; Thu, 30 Apr 2015 14:18:10 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 0_MEOXOZDhtg for <tor-talk@lists.torproject.org>;
 Thu, 30 Apr 2015 14:18:10 +0000 (UTC)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com
 [IPv6:2a00:1450:4010:c03::22d])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id E675B20EB3
 for <tor-talk@lists.torproject.org>; Thu, 30 Apr 2015 14:18:06 +0000 (UTC)
Received: by labbd9 with SMTP id bd9so45392273lab.2
 for <tor-talk@lists.torproject.org>; Thu, 30 Apr 2015 07:18:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:from:date:message-id:subject:to:content-type;
 bh=s96ZfMDD3VaKuJM24BKrEN2xwqQ/YQb4tUbuOPHJBAc=;
 b=gPFnukwKRqsB0Jjuu9DW6vQqXwxOSshnoPKaZmZr+4wyBxOz3XM0MlGomOeY/WF2mn
 NMTd62J4gwKaqiMQmie4oFYJsHHDhWrsXx2pQbXHOC3aC1lwVvz8T4Tyte7yttg8tAgn
 XTKO7/jeSPH1ervwiuuLxV4JF+zv+ReLMVBL9uHbkOMnfZgoX7kTpkqg60G0KFYonTrp
 DTUUNYB8llc5Dauo9fLdhUBIKbmqQEokjNrWWe2QmETOZRxrwbaYUR5BWXXj2pmXzMaU
 SGITbAjFHuqKh+9eg3GyMoxTHgDVey7uH+7ekt00cRncZjJv00voRtjYQCmccS2N2ZfG
 e1dA==
X-Received: by 10.112.17.8 with SMTP id k8mr4093357lbd.28.1430403483686; Thu,
 30 Apr 2015 07:18:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.117.202 with HTTP; Thu, 30 Apr 2015 07:17:23 -0700 (PDT)
From: Felipe Micaroni Lalli <micaroni+tor@gmail.com>
Date: Thu, 30 Apr 2015 11:17:23 -0300
X-Google-Sender-Auth: tYZcdj2UMGnDUXwlHnyCdRvhMJ4
Message-ID: <CAHvMVPQtZ3tHWTAMyrsbTZoK_sEUWXf0cKULe==P2aD16MC+ww@mail.gmail.com>
To: TOR Talk <tor-talk@lists.torproject.org>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] Full integration with bitcoin (suggestion / feature
	request)
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Hi!

Why not make a fully true integration with bitcoin in the network? Bitcoin
could be the fuel: who wants to use pays, who want to help the network with
a exit node receives, simple like that. The exit nodes could define a
minimum to receive, for example: 0.001 BTC / MB or 0.01 BTC / MB or for
free, and the user could define a maximum to pay, like 0.0005 BTC / MB or
even free. Then, the network would find the right matches / patches. In a
free market more you pay, more you get in speed and reliability. The
networks could continue free but slow and faster if paid.

Forget the intermediate nodes for now, think in this situation:

- A, B and C is final user.
- D, E and F are exit nodes.

A is poor and set his configuration to spend max of 0 BTC / MB.
B set max pend of 0.001 BTC / MB, and C is rich, so he set max to 0.01 BTC
/ MB.

D is a very nice guy, and rely a exit node for free. E has a few network
resources, so he set min. to 0.001 BTC / MB. F is even more poor, and he
wouldn't be a exit node anyway, so he set the min. to 0.01 BTC / MB.

A would use D as exit node, with the rate of 0 BTC / MB.
B would use D and E as exit node, with the avg. rate of 0.0005 BTC / MB.
C would use D, E and F as exit node, with the avg. rate of 0.00367 BTC / MB.

F won't earn too much because he is very expensive and few users would use
that. But E could make more money even charging less. The market will
decide the equilibrium.



Thanks!
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

