Re: [Din] Hyperledger evaluation on a mesh network
Jehan Tremback <jehan@altheamesh.com> Wed, 04 April 2018 15:58 UTC
Return-Path: <jehan@altheamesh.com>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5297512DA49 for <din@ietfa.amsl.com>; Wed, 4 Apr 2018 08:58:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c8K22M2LXO5m for <din@ietfa.amsl.com>; Wed, 4 Apr 2018 08:58:24 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17D7F1201F8 for <din@irtf.org>; Wed, 4 Apr 2018 08:58:24 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B8D0A212FC; Wed, 4 Apr 2018 11:58:22 -0400 (EDT)
Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Wed, 04 Apr 2018 11:58:22 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=roERPQ I/x4pOE0QzXM4uIFZHWa+8eallu0qbNmpS0CU=; b=SOeyiJrDtAd60uGNRJ9/E8 vLLPsn60j8CVZsmYE19h4iej2r2JIDzU6Yakzuh83UIbA9hOclxW+0L6Vu46m7f0 dwlxKXxSCE+5mzy62Lr2iE4FtboHk6qE7HleRIhhluP9vz9No7aECt3d8SdabLol XZ67R0+QWlNbevW5WVnvdWRWZKmuTvwt6sKI8ZLvtFdz8X7dAMPvWVAw1zBFf/hr 3koVfhr35aIWc6dnNFESnQbs1hFCLnpxvnbDcZbr+iG5lnGoX/54/F1VS6INBxpM NZuKyDfirqxa5ouGsAriCfnpAsHn+vtUyUoQUIpY+t8VzsAwuKzU0b2O7rGv0PmQ ==
X-ME-Sender: <xms:HvbEWkI-brOks9lK9OtDgJw9ibdw6tlpeVpwBl8b22A-_ftf7-225A>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 3DA699E19E; Wed, 4 Apr 2018 11:58:22 -0400 (EDT)
Message-Id: <1522857502.1313779.1326451800.352B185C@webmail.messagingengine.com>
From: Jehan Tremback <jehan@altheamesh.com>
To: Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk>
Cc: din@irtf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_152285750213137791"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-bb419338
In-Reply-To: <CAEeTejK71xdhXYowRS+fh=Ni-4dusbAui9h9BJ3K-n-8TTAPOg@mail.gmail.com>
Date: Wed, 04 Apr 2018 08:58:22 -0700
References: <CAPaG1AnJjDQh4N+kiT-QhgiFyNwi69TM74jcYFx6xQiwPXB+EQ@mail.gmail.com> <1522807761.2691505.1325710912.72C042EF@webmail.messagingengine.com> <CAEeTejK71xdhXYowRS+fh=Ni-4dusbAui9h9BJ3K-n-8TTAPOg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/uBzVLzRtCIAsCtDnWv1knwpXOy8>
Subject: Re: [Din] Hyperledger evaluation on a mesh network
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/din>, <mailto:din-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din/>
List-Post: <mailto:din@irtf.org>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/din>, <mailto:din-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Apr 2018 15:58:26 -0000
Even simpler, by adding a monetary price metric to a distance vector protocol (we are currently testing this in production). Skimming your paper, it looks like you are thinking along the same lines. https://altheamesh.com/documents/whitepaper.pdf Back to the Arjuna's post, the use of a blockchain implies that there is some value to having an immutable transaction ordering mechanism. In our protocol we conceptualize these ordered transactions as "payments", while in Arjuna's paper the actual use of this transaction ordering is left unspecified. Running the transaction ordering consensus protocol on the network nodes themselves seems like a bad idea. These nodes have more of an incentive to mess with the ordering than some faraway validators who know nothing about the specific application and are only incentivized to order transactions correctly. Also, the fact that there are always going to be many fewer validators available on a local network means that the consensus pool is smaller and more vulnerable to manipulation. I say, leave the transaction ordering to a global network of validators who specialize in transaction ordering and leave the networking to network hardware equipped with light clients. With Althea, we are able to run everything on commodity routers on OpenWRT. -- Jehan Tremback jehan@altheamesh.com On Wed, Apr 4, 2018, at 1:04 AM, Jon Crowcroft wrote: > or a much simpler approach: > https://hal.inria.fr/inria-00466747/document > > On Wed, Apr 4, 2018 at 3:09 AM, Jehan Tremback > <jehan@altheamesh.com> wrote:>> __ >> Why run full nodes on your networking hardware? One could achieve the >> same security characteristics (or better) by simply using light >> clients of a public blockchain on the networking hardware.>> >> -- >> Jehan Tremback >> jehan@altheamesh.com >> >> >> >> On Tue, Apr 3, 2018, at 4:44 AM, Arjuna Sathiaseelan wrote: >>> we recently did an evaluation of the hyperledger fabric in a >>> community wireless network within the famous guifi.net..>>> >>> will be of interest https://arxiv.org/pdf/1804.00561.pdf >>> >>> Regards >>> >>> -- >>> >>> Arjuna Sathiaseelan >>> University of Cambridge | Ammbr Research Labs >>> Personal: http://www.cl.cam.ac.uk/~as2330/ >>> N4D Lab: http://www.cl.cam.ac.uk/~as2330/n4d >>> _________________________________________________ >>> Din mailing list >>> Din@irtf.org >>> https://www.irtf.org/mailman/listinfo/din >> >> >> _______________________________________________ >> Din mailing list >> Din@irtf.org >> https://www.irtf.org/mailman/listinfo/din >>
- [Din] Hyperledger evaluation on a mesh network Arjuna Sathiaseelan
- Re: [Din] Hyperledger evaluation on a mesh network Jehan Tremback
- Re: [Din] Hyperledger evaluation on a mesh network Jon Crowcroft
- Re: [Din] Hyperledger evaluation on a mesh network Jehan Tremback
- Re: [Din] Hyperledger evaluation on a mesh network Arjuna Sathiaseelan
- Re: [Din] Hyperledger evaluation on a mesh network Leandro Navarro
- Re: [Din] Hyperledger evaluation on a mesh network Jehan Tremback
- Re: [Din] Hyperledger evaluation on a mesh network Jon Crowcroft