Re: [Din] Hyperledger evaluation on a mesh network
Arjuna Sathiaseelan <arjuna.sathiaseelan@gmail.com> Wed, 04 April 2018 20:31 UTC
Return-Path: <arjuna.sathiaseelan@gmail.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 1939812DA68 for <din@ietfa.amsl.com>; Wed, 4 Apr 2018 13:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5EjM3Qp0qRdD for <din@ietfa.amsl.com>; Wed, 4 Apr 2018 13:31:33 -0700 (PDT)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EFA112D864 for <din@irtf.org>; Wed, 4 Apr 2018 13:31:33 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id e79so27920426ioi.7 for <din@irtf.org>; Wed, 04 Apr 2018 13:31:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3BklwErmudoAC2L+mIH2lbfC6SV7AkR/wA2imAQvumY=; b=ELr+PLg9tgsringhUlqL0JyYxIC7NYBeVwqwnpSmrLIowDEpxXbVKVoDh8APjmQe8Q sOP7quPg/LIZD6XOUPqtpwHaS6MoJPH2viSYVDOKANpPASGiBOqfBBd6mV9pGYgVakVY 3J+KYQyLlrAqw9f9lscLrBcBLYNCb4DUPT02r+c+ZqXuXlqyzaMs5RnDJ/st+azrtvID NCE2Ut2gha6wpFGyTzLGrQHy24V6DLZQwa3Kyg6fhxr5FoTVwIh4/uw/uUsekmUsW5Zg Ix0v8LQIW60LZc5y7G9Bj+VUa4z/vL3yYTvOQIyfs5byscnP9u5k+FoWVXVwa31U3uZQ Yevw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3BklwErmudoAC2L+mIH2lbfC6SV7AkR/wA2imAQvumY=; b=F3o9OZHdaVOYjQAcT+QYmLzbaKYHWuMkzJMpNd/gqYgJa+g1dExNmLs5m2Q5wkY84P bZVkZdEUTRh9GF4pBOdG2EMWJvdwaI54oeTO0Nd50NzEf11Go7EgduM2pC6XHc0vqEfL UV09Wik3XeM+Az+eEiZBjH6xGF3NAHfatC/xSDZYhznNMY4TMcT3PzmW/9zwGFu81JeX EFo+AEd8qPtaG8iw6aNboucKEGDaj2RFP2wpQBNxmj1/lplpdZ8W/A/NH9YBQwM5o6Mx PZURgH08HIzYiX7A2IrsSI2hKeKhZpUnmVntqnvwzhf5FGou7CT3zhPKKoSIvUUUaua8 Xu9g==
X-Gm-Message-State: AElRT7EygdmuSlLg6I+4MWO1/rHRFxbBMNBoWH9lju3aON+vS0pc2Bm+ tDLfk3cibMaMi5Bw4WPIPcktBun6/8/pw35AmQg=
X-Google-Smtp-Source: AIpwx4+qOnYYzEy1Cdwaq2NNocO0b6m+mDyjyCPqgiec4FFqnthqseRPzCDbCe2K0o6ot4GdFqLj9wB+vt4hLcFYCFE=
X-Received: by 10.107.37.5 with SMTP id l5mr17225551iol.47.1522873892666; Wed, 04 Apr 2018 13:31:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.198.5 with HTTP; Wed, 4 Apr 2018 13:31:31 -0700 (PDT)
In-Reply-To: <1522857502.1313779.1326451800.352B185C@webmail.messagingengine.com>
References: <CAPaG1AnJjDQh4N+kiT-QhgiFyNwi69TM74jcYFx6xQiwPXB+EQ@mail.gmail.com> <1522807761.2691505.1325710912.72C042EF@webmail.messagingengine.com> <CAEeTejK71xdhXYowRS+fh=Ni-4dusbAui9h9BJ3K-n-8TTAPOg@mail.gmail.com> <1522857502.1313779.1326451800.352B185C@webmail.messagingengine.com>
From: Arjuna Sathiaseelan <arjuna.sathiaseelan@gmail.com>
Date: Wed, 04 Apr 2018 21:31:31 +0100
Message-ID: <CAPaG1A=Z=yVHAZ5HkrtieQdOgm8R7J302VN3d93yLYgQ05Zd_A@mail.gmail.com>
To: Jehan Tremback <jehan@altheamesh.com>
Cc: Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk>, din@irtf.org
Content-Type: multipart/alternative; boundary="001a1140f4186903b505690bb503"
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/KxEmdVBPFYFdWlrTCxHeqyMA3q4>
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 20:31:36 -0000
Jehan, Good points. The aim of the paper was to benchmark HL and understand the painpoints and hardware requirements. So this is the way I see things from Ammbr's point of view: 1. We are developing hardware (the Ammbr routers) that would function as part of the blockchain e.g. act as orderers & any node/hardware can still be a light node within the network - they just cant participate in the consensus. 2. Our PoET/PoV consensus + the underlying DAO ensures fairness/decentralisation + does not allow nodes to mess around - any bad behaviour will involve revoking the certificates by the certification authority.. Regards On Wed, 4 Apr 2018, 16:58 Jehan Tremback, <jehan@altheamesh.com> wrote: > 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 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