IETF Logo Mail Archive

Re: [Din] Hyperledger evaluation on a mesh network

Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk> Wed, 04 April 2018 08:04 UTC

Return-Path: <crowcroft@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 01AC4124205 for <din@ietfa.amsl.com>; Wed, 4 Apr 2018 01:04:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 0gO2nxZCcyt0 for <din@ietfa.amsl.com>; Wed, 4 Apr 2018 01:04:33 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 B84DC120047 for <din@irtf.org>; Wed, 4 Apr 2018 01:04:32 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id r191so7721361wmg.4 for <din@irtf.org>; Wed, 04 Apr 2018 01:04:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=zW5OcYP1zGimW8bXtQ5pXJuABe/DJGCqXApB0THNpdI=; b=oGHiFh2Zs6MX1a7MbBcbM+tWWp6ttQ9vt7QGsI9fs9QWSDBsgDfvStirDPzrPo20wz +u3fD0csp4uuTt+B7grRouXLXinK9/wYxP1+ST+6w6gjrUR6QMl+WR0vLlvAwCiKeUKh KOBeWUwxHImEXGdbSgdO1CihiKMyuwX7Z4A+Bs6m5vohpCdEGqXc134TCsofw4RZpZJ2 pCDv5WsX5JClCHq+nTDNOKPFFs6+jtFygXAAX8AJN9ljTq4V7QfQEoxjW4t2Fq4mTqen wrCDDxln+CpmkGKcHulbWnSZkVBizNPvTS3yK+5NKnybaol/bnfPNqw+L/ohmDVWmcoe grXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=zW5OcYP1zGimW8bXtQ5pXJuABe/DJGCqXApB0THNpdI=; b=exNRfNJ16AocsctMgk4yaKtMe84ZSGXKJt1onsckK0h+U5p1F4gDKfa5uriLMK77WE qG3Wgxf/kHmnk3ZHHeq26kARbuiMVHVApJQ1Yl975DiQp/cToQfE/gHdF35N/0xkasKY ZwbZ0MBDfuJc7YT0dxj99JPH8BDSlfjwwVs4stHgQc2EgnkGrNAAF5AfxQ9gjrevk3Ok 09V2ZI+Ov3P1OCPGQOivaOhYb+auHdUMFF18/C+NwIJRFgERmtasIltTlBOtIT9UGk8+ NoO3KyQSrjzNS//c6TeVSEAvmKbs95Gdx1uPf8eh/q7UEa/l+6lp9RleD56OacOlT7ec FtSA==
X-Gm-Message-State: AElRT7Hy0IaUbvy46dmZ/W5f/JEv5Rf4c4cZjkZ2qUl7/njRHM/zQ9i9 UMcfvuhiEJolvtSX/d4Nh5KLl1Ize8juKxFXI8o=
X-Google-Smtp-Source: AIpwx49DeRIegarBEfpdF7HnMrrdWRao8Uou5Fldvy+4BRCDJQoJZZtw+X6xBdnp9H37N8Hs6+7YKMK2TK+W/YwCZMI=
X-Received: by 10.28.153.12 with SMTP id b12mr6961812wme.104.1522829071221; Wed, 04 Apr 2018 01:04:31 -0700 (PDT)
MIME-Version: 1.0
Sender: crowcroft@gmail.com
Received: by 10.28.167.86 with HTTP; Wed, 4 Apr 2018 01:04:30 -0700 (PDT)
In-Reply-To: <1522807761.2691505.1325710912.72C042EF@webmail.messagingengine.com>
References: <CAPaG1AnJjDQh4N+kiT-QhgiFyNwi69TM74jcYFx6xQiwPXB+EQ@mail.gmail.com> <1522807761.2691505.1325710912.72C042EF@webmail.messagingengine.com>
From: Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk>
Date: Wed, 04 Apr 2018 09:04:30 +0100
X-Google-Sender-Auth: 1fDKSLNk1kWCY__LKgjpGvzGcB4
Message-ID: <CAEeTejK71xdhXYowRS+fh=Ni-4dusbAui9h9BJ3K-n-8TTAPOg@mail.gmail.com>
To: Jehan Tremback <jehan@altheamesh.com>
Cc: din@irtf.org
Content-Type: multipart/alternative; boundary="001a114b1ca2d809bd05690145d5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/PlH9U6-cB8lQGdJ1K_RuC5pSu54>
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 08:04:36 -0000

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
>
>

v2.23.0 | Report a Bug | By Email