Delivery-Date: Sun, 15 Nov 2015 05:40:10 -0500
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,
	URIBL_RED 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 2EBFC1E04E7;
	Sun, 15 Nov 2015 05:40:09 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 55E3237D23;
	Sun, 15 Nov 2015 10:40:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id ADD9337C28
 for <tor-talk@lists.torproject.org>; Sun, 15 Nov 2015 10:40:01 +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 djXZMOEno7w5 for <tor-talk@lists.torproject.org>;
 Sun, 15 Nov 2015 10:40:01 +0000 (UTC)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com
 [IPv6:2607:f8b0:4001:c06::229])
 (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 8D2B237BB8
 for <tor-talk@lists.torproject.org>; Sun, 15 Nov 2015 10:40:01 +0000 (UTC)
Received: by ioc74 with SMTP id 74so135204658ioc.2
 for <tor-talk@lists.torproject.org>; Sun, 15 Nov 2015 02:39:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :cc:content-type;
 bh=k+HP9errizYKMwngNy2k/Sn1b7ea4Js8dm3mZKckjto=;
 b=GDQV+AsfsaWRxbi/X7QOT6c4nVtgoMs1Le5PoVWYOPRMhGwAOjRM4Z27vRtXLRqX9M
 u7WLqOPqLhYqD2BQpgrR6ZAgzRq73WzJOsuJw60H0RhTcuVfR46R3wVh4iPOitmlxd+R
 RXO6B+4HH1WPIoFOGOJv42+qUXc25YY584//9EwCpsbgBrH03NnkKXolHEm86I+n74Qh
 3vD/Iq/6LbExS155dxjGHhEluwEjkdi3kwa4Y9oU+QJNvKlRcnjjox5fkC0yy5d9gyN2
 tW0+ZAoWiFFj9RGxC/vXnCjXx7N+aAY4b7srUgsR2fy6tXWd9ET6hVaC3qg62zaZLrL8
 cLZA==
X-Received: by 10.107.17.18 with SMTP id z18mr32586567ioi.7.1447583999244;
 Sun, 15 Nov 2015 02:39:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.36.137.197 with HTTP; Sun, 15 Nov 2015 02:39:19 -0800 (PST)
In-Reply-To: <20151114182041.Horde.KkP9f3xtW8IxvNjuHmEz4ZI@pam.asoshared.com>
References: <90915577-0641-4F27-A566-8197D25C92E9@me.com>
 <20151114182041.Horde.KkP9f3xtW8IxvNjuHmEz4ZI@pam.asoshared.com>
From: grarpamp <grarpamp@gmail.com>
Date: Sun, 15 Nov 2015 05:39:19 -0500
Message-ID: <CAD2Ti28Q229gY1gMJE24cdP6F1+8tA5NTg98VqXXoVMwEhQYng@mail.gmail.com>
To: allen@bearbonds.org
Cc: cypherpunks@cpunks.org, tor-talk@lists.torproject.org,
 cryptography@metzdowd.com
Subject: Re: [tor-talk] [Cryptography] Bear Bonds - a new crytpocurrency
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>

>> And details on "directory servers", "witnesses", "trusted party
>> transaction servers".

I was looking for details on who or what process selects / runs / chooses
these nodes, and how.

That and words like 'trusted' are critical in these communities and
do we not yet see these established in the quoted things above?

What makes them unable to censor transactions?
Or to censor other nodes, or unspent outputs?
Who has authority for issuing control messages?
What are their key practices and defense to various threats?

>> An admittedly very brief reading, site verbage, including trademark,
>> patent and copyright claims leaves question as to commitment to
>> fully decentralized p2p model and opensource. If true, you might find
>> quite limited interest here and more interest by banks, govts, and
>> commercial. If untrue and misread, please address.

This question was not yet answered.

These and the license may not be 'notable features' for certain
of these communities, and should certainly be detailed
in any full and legitimate comparison to Bitcoin...
https://www.bearbonds.org/legal/software-license-agreement/
What is the open development model?
What aligns you (or not) with the various non-technical philosophies
of Bitcoin (to which you already strive to technically compare)?

> We currently do not support any network other than Tor.  Before introducing a
> new network, we would have to carefully consider whether it could potentially
> compromise privacy and security.

Do you have a paper covering your analysis of Tor in that regard?
It would certainly be welcomed and of interest to at least the
Tor community.
-- 
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

