Date   

Changes to Hyperledger-hosted Zoom meetings

Ry Jones
 

On September 27 Zoom is implementing a mandatory functionality change. Zoom will now enforce all meetings to have either a passcode or a waiting room. If no passcode is enabled, attendees will automatically be placed into a waiting room and the meeting hosts will need to add the attendees to the meeting manually.

 

You should be looking for updated meeting invites from lists.hyperledger.org that contain an embedded passcode as part of the zoom meeting URL. These notices will be tagged with #cal-invite.

 

Please be sure to sync your calendars if the updates are not reflected on your calendar tools. You can always subscribe to the calendar feed to stay up to date with any meeting changes by following the instructions below:

 

Opt into a Hyperledger subgroup mailing list (if you wish to receive calendar updates and subscribe to calendar feed) 

  • Log into https://lists.hyperledger.org/g/main

  • Click on Subgroups to the left and this will display the list of available subgroups for Hyperledger 

  • Navigate to the subgroup of your choice

  • Click +Join This Group toward the near bottom of the page and this will add you to the group.

Subscribe to a meeting calendar

  • Login to lists.hyperledger.org for the specific Hyperledger list you are interested in

  • For example, click the "Your Calendar" icon on the left: https://lists.hyperledger.org/g/tsc/calendar

  • Scroll to the bottom of the page

  • Click the "Subscribe to Calendar" button

  • copy the URL that is generated

  • Paste the URL using whatever method your calendar reader uses for internet calendar subscriptions

All Hyperledger public meetings can also be viewed on the wiki.


Hyperledger Project Quarterly Update Due #tsc-project-update - Thu, 09/03/2020 #tsc-project-update #cal-notice

grid@lists.hyperledger.org Calendar <noreply@...>
 

Hyperledger Project Quarterly Update Due #tsc-project-update

When:
Thursday, 3 September 2020

Organizer:
community-architects@...

Description:
Please file a project status report for the TSC here:

https://wiki.hyperledger.org/display/TSC/Project+Status+Updates


Proposed GCHMCP Plug-ins for Hyperledger Grid #tsc-project-update

Jayakar
 

Herewith some of the Plug-ins of 'Global Digital Corona Virus Harmful Mutation Control Program' for Hyperledger Grid, is expressed in Slide no: 7 of the attached deck, for proceeding with collaborative further developments.


Hyperledger Project Quarterly Update Due #tsc-project-update - Thu, 09/03/2020 #tsc-project-update #cal-reminder

grid@lists.hyperledger.org Calendar <grid@...>
 

Reminder: Hyperledger Project Quarterly Update Due #tsc-project-update

When: Thursday, 3 September 2020

View Event

Organizer: community-architects@...

Description: Please file a project status report for the TSC here:

https://wiki.hyperledger.org/display/TSC/Project+Status+Updates


Event: Grid Community Meeting #cal-invite

grid@lists.hyperledger.org Calendar <grid@...>
 

Grid Community Meeting

When:
Friday, 21 August 2020
10:00am to 11:00am
(UTC-05:00) America/Chicago
Repeats: Every 4 weeks on Friday

Where:
Zoom - https://us02web.zoom.us/j/86725415937

Organizer: Shawn Amundson amundson@...

Description:


Re: Trace and Trace issue

Prem Baranwal
 

Attaching the screenshot of the error i got after updating the docker images to 1.2


Re: Trace and Trace issue

Prem Baranwal
 

Thanks Peter.
Do you mean changing the tag in docker-compose.yaml from 1.1 to 1.2.5 for all the hyperledger images? The highest version matching 1.2.* published on docker hub for sawtooth-validator is 1.2.5.
validator:
  image: hyperledger/sawtooth-validator:1.1
 to 
validator:
  image: hyperledger/sawtooth-validator:1.2.5

I actually tried to change it to chime tag which is essentially same as 1.2.5. That resolved the consensus error and i was able to execute the intkey TP transactions But it gave the following validator connection error when i submitted the get-started user form from aseet_client UI Failed to receive events; aborting: connection received invalid message: Received unexpected message: PING_REQUEST.


Re: Trace and Trace issue

Peter Schwarz
 

Hi Prem,

Looking at the particular error there, you want to make sure that you've updated both the validator and the devmode consensus engines to the 1.2 release branch.

Cheers,

Peter


On Mon, Jul 20, 2020 at 4:38 AM Prem Baranwal <prem.baranwal@...> wrote:
Hi, Has anyone recently been able to set up the grid/grid-contrib and run the asset-client successfully? Does it require any changes in the docker-compose.yaml?
I tried to run the asset-client example as per the instructions at https://github.com/hyperledger/grid-contrib/tree/master/track_and_trace and run into the following error -
Grid-TnTError.png
At this point there were already 12 blocks created. Later, I tried a couple of things like changing the hyperledger/sawtooth docker images to chime (1.2.5) and adding dependency of sabre-tp to *-contract-builder services. But that led to some validator connection error - Failed to receive events; aborting: connection received invalid message: Received unexpected message: PING_REQUEST.

Any help will be appreciated.

Prem Baranwal


Trace and Trace issue

Prem Baranwal
 

Hi, Has anyone recently been able to set up the grid/grid-contrib and run the asset-client successfully? Does it require any changes in the docker-compose.yaml?
I tried to run the asset-client example as per the instructions at https://github.com/hyperledger/grid-contrib/tree/master/track_and_trace and run into the following error -
Grid-TnTError.png
At this point there were already 12 blocks created. Later, I tried a couple of things like changing the hyperledger/sawtooth docker images to chime (1.2.5) and adding dependency of sabre-tp to *-contract-builder services. But that led to some validator connection error - Failed to receive events; aborting: connection received invalid message: Received unexpected message: PING_REQUEST.

Any help will be appreciated.

Prem Baranwal


Hyperledger Project Quarterly Update Due #tsc-project-update - Thu, 06/04/2020 #tsc-project-update #cal-notice

grid@lists.hyperledger.org Calendar <noreply@...>
 

Hyperledger Project Quarterly Update Due #tsc-project-update

When:
Thursday, 4 June 2020

Organizer:
community-architects@...

Description:
Please file a project status report for the TSC here:

https://wiki.hyperledger.org/display/TSC/Project+Status+Updates


Upcoming Event: Hyperledger Project Quarterly Update Due #tsc-project-update - Thu, 06/04/2020 #tsc-project-update #cal-reminder

grid@lists.hyperledger.org Calendar <grid@...>
 

Reminder: Hyperledger Project Quarterly Update Due #tsc-project-update

When: Thursday, 4 June 2020

View Event

Organizer: community-architects@...

Description: Please file a project status report for the TSC here:

https://wiki.hyperledger.org/display/TSC/Project+Status+Updates


Re: Introducing Hyperledger Project & How-to Webinars

Marta Piekarska
 

Right, if you would like to watch the past webinars, they can be found here: https://www.hyperledger.org/resources/video-library

For future webinars, visit : https://www.hyperledger.org/events or simply add the webinar calendar to your calendar: https://lists.hyperledger.org/g/webinars/ics/8084041/901820588/feed.ics

Thanks and have a good fay
m

Marta Piekarska-Geater
Director of Ecosystem, Hyperledger

SCHEDULE A MEETING WITH ME: calendly.com/mpiekarska


marta@...
+447802336641 (U.K) - Signal and Whatsapp
Wickr: martap

Skype: martapiekarska

Based in the U.K.

On 7 May 2020, 20:34 +0100, Jeff Neithercutt via lists.hyperledger.org <jeff=blockchainofevidence.org@...>, wrote:
I got this email from you, and I want to attend some of the webinars you mention in your email.

Jeff Neithercutt
Founder, Blockchain of Evidence
blockchainofevidence.org



May 7, 2020, 08:19 by mpiekarska@...:
Hello, 
To make sure that the broader community is up to date with latest the Hyperledger project developments and features, we would like to offer two main webinar opportunities:

1. Project Webinar - 1h long webinar on major releases and description of new functionality, ideally with demos. (max two/year)
2. Project How-To - 30 min, hands-on demos and how-tos. (max two/year + unlimited offline recordings)

Each project is limited to two webinars a year, so be sure to save it for major releases.  Project How-To's are supposed to be virtual demos, or short training sessions. Every submission should be sponsored by a maintainer: we want those to be aligned with the rest of the community, so at least one maintainer should sign off on the presentation.

The webinars take place every first and third Wednesday at 3pm GMT/7am PST. 

If you are interested, please contact marketing@....

Have a great day
m


Re: Introducing Hyperledger Project & How-to Webinars

Jeff Neithercutt
 

I got this email from you, and I want to attend some of the webinars you mention in your email.

Jeff Neithercutt
Founder, Blockchain of Evidence
blockchainofevidence.org



May 7, 2020, 08:19 by mpiekarska@...:

Hello, 
To make sure that the broader community is up to date with latest the Hyperledger project developments and features, we would like to offer two main webinar opportunities:

1. Project Webinar - 1h long webinar on major releases and description of new functionality, ideally with demos. (max two/year)
2. Project How-To - 30 min, hands-on demos and how-tos. (max two/year + unlimited offline recordings)

Each project is limited to two webinars a year, so be sure to save it for major releases.  Project How-To's are supposed to be virtual demos, or short training sessions. Every submission should be sponsored by a maintainer: we want those to be aligned with the rest of the community, so at least one maintainer should sign off on the presentation.

The webinars take place every first and third Wednesday at 3pm GMT/7am PST. 

If you are interested, please contact marketing@....

Have a great day
m


Introducing Hyperledger Project & How-to Webinars

Marta Piekarska
 

Hello, 
To make sure that the broader community is up to date with latest the Hyperledger project developments and features, we would like to offer two main webinar opportunities:

1. Project Webinar - 1h long webinar on major releases and description of new functionality, ideally with demos. (max two/year)
2. Project How-To - 30 min, hands-on demos and how-tos. (max two/year + unlimited offline recordings)

Each project is limited to two webinars a year, so be sure to save it for major releases.  Project How-To's are supposed to be virtual demos, or short training sessions. Every submission should be sponsored by a maintainer: we want those to be aligned with the rest of the community, so at least one maintainer should sign off on the presentation.

The webinars take place every first and third Wednesday at 3pm GMT/7am PST. 

If you are interested, please contact marketing@....


Have a great day
m


Introduction to Hyperledger Grid slides?

David Boswell
 

The Hyperledger Bologna meetup group is interested in running an online meetup focused on Hyperledger Grid.  Is there an introduction to Hyperledger Grid presentation available that we could share with Alberto, the organizer?

If there is a presentation, please let us know.  And if you're interested in helping present at the meetup, it is happening on April 23 and the details are at the link below.  Please let me and Alberto know if you would like to speak there.


Thanks,
David


Hyperledger Project Quarterly Update Due #tsc-project-update - Thu, 03/19/2020 #cal-notice #tsc-project-update

grid@lists.hyperledger.org Calendar <noreply@...>
 

Hyperledger Project Quarterly Update Due #tsc-project-update

When:
Thursday, 19 March 2020

Organizer:
community-architects@...

Description:
Please file a project status report for the TSC here:

https://wiki.hyperledger.org/display/TSC/Project+Status+Updates


Upcoming Event: Hyperledger Project Quarterly Update Due #tsc-project-update - Thu, 03/19/2020 #tsc-project-update #cal-reminder

grid@lists.hyperledger.org Calendar <grid@...>
 

Reminder: Hyperledger Project Quarterly Update Due #tsc-project-update

When: Thursday, 19 March 2020

View Event

Organizer: community-architects@...

Description: Please file a project status report for the TSC here:

https://wiki.hyperledger.org/display/TSC/Project+Status+Updates


Re: Intro - Digital Asset Trust Framework

Shawn Amundson
 

Grid does support multiple distributed ledgers today. The first, obviously, is Sawtooth using Sabre. The second is Splinter's Scabbard service which is implemented using Transact to run Sabre (https://github.com/hyperledger/grid/tree/master/examples/splinter). Thus, the pattern does exist within Grid to provide different backend ledgers. However, backends do need to minimally a) be able to run Sabre smart contracts (whether or not via Sabre directly wouldn't matter); and b) have a merkle-trie view of state to run those contracts; c) have a state-delta-export capability. That's a list of what Transact provides, as it happens, which is why we talk about the easy path being adopting Transact.

With respect to WASM host interfaces -- I think it is achievable if you limit yourself to Ethereum-style contracts. And we could standardize a separate set for Sabre, and one for Fabric-Chain-Code. That would be three standards, not one. Even if we were to somehow agree on a specific host interface ABI, the schematic differences exist and are profound and non-trivial. We also don't want to incur a race-to-the-bottom by supporting some limited subset of overlapping functionality.

So sure, its possible, but I wouldn't expect it to magically appear. The best path is still Fabric+Transact integration, which is far from an impossible task.

I'm very interested in Fabric+Transact integration from a Transact project perspective. But perhaps more compelling is Fabric-on-Splinter, implemented using Transact. As far as I can tell, Transact would replace the majority of the endorser node's code, which means the minority of effort would be re-implementing the remaining pieces of the endorser as a Splinter service. We could front that with a GRPC shim for Fabric client compatibility, which gives us a good path for those that adopted Fabric. As far as the orderer, that would be a pretty easy lift too given we have all the pieces to construct it out of Scabbard, Transact, Splinter, the consensus library, etc. We end up with a version of Fabric that uses Transact, and it would be pretty easy to write a Grid backend for it at that point.

-Shawn


On Tue, Mar 10, 2020 at 7:27 PM Brian Behlendorf <bbehlendorf@...> wrote:
So interestingly enough I was having a chat with Patrick Erichsen from Target about this at HGF last week, about what it would take to support Grid on other platforms, like Fabric.

First off to answer your question, Fabric does have early, use-at-your-own-risk support for WASM, thanks to a mentorship project last year:


It would be fantastic to see how much of the WASM code Transact expects can be run straight on WASM-on-Fabric. As I understand it from another conversation at HGF with Silas Davis and Sean Young, the WASM host interfaces on the above project, on Transact, and on the Solang Labs project are all slightly different, as they are not standardized in the WASM language spec (sort of like #include stdio.h in K&R C?), so that may impact that portability. As an aside, it would be nice, if those host interfaces don't have a great reason to be different, for the relevant devs on each project to chat and align on a common definition across HL projects, unless there's a great reason (like the eWASM subset for Ethereum public networks, or something).

it does seem like WASM support is growing both in the blockchain world and outside, so I'd hope the Fabric team would consider supporting more WASM-on-Fabric natively. Having something like Grid using it would be an excellent motivator.

I would assume there are other places aside from WASM where the Grid -> Transact -> Sawtooth dependency chain today makes for additional work to drop in Fabric, but it would be great to map those out and consider a layer of abstraction. Or if it's more complicated than that due to simply fundamental differences between Sawtooth and Fabric, to articulate what motivated parties could do to address that gap.

I realize there is a longer-term interest in seeing Transact itself supported on Fabric, but I leave that to others to work out; I assume it's a heavier lift than Grid->Fabric but would love (prefer, even!) to be wrong.

Brian


On 3/10/20 4:48 PM, clive boulton wrote:
Apparently Fabric currently prefers chain code native smart contracts.
Architecturally is there any other way to interoperate so that Fabric could run Grid ...

e.g. Is it practical to add Wasm support to Fabric so that Transact could run on Fabric? 

Btw, Wasm seems to have solid developer adoption in Seattle at Microsoft/Google, because the IoT edge is more resilient with a memory safe capabilities-based programming language. https://www.meetup.com/Seattle-Rust-Meetup/events/266941413 ) DAML also found a very fine-grained delegation model similar to the OCAP [object capability] model helps to solve resilience https://cacm.acm.org/magazines/2019/9/238966-daml/fulltext


-- 
Brian Behlendorf
Executive Director, Hyperledger
bbehlendorf@...
Twitter: @brianbehlendorf


Re: Intro - Digital Asset Trust Framework

Brian Behlendorf
 

So interestingly enough I was having a chat with Patrick Erichsen from Target about this at HGF last week, about what it would take to support Grid on other platforms, like Fabric.

First off to answer your question, Fabric does have early, use-at-your-own-risk support for WASM, thanks to a mentorship project last year:


It would be fantastic to see how much of the WASM code Transact expects can be run straight on WASM-on-Fabric. As I understand it from another conversation at HGF with Silas Davis and Sean Young, the WASM host interfaces on the above project, on Transact, and on the Solang Labs project are all slightly different, as they are not standardized in the WASM language spec (sort of like #include stdio.h in K&R C?), so that may impact that portability. As an aside, it would be nice, if those host interfaces don't have a great reason to be different, for the relevant devs on each project to chat and align on a common definition across HL projects, unless there's a great reason (like the eWASM subset for Ethereum public networks, or something).

it does seem like WASM support is growing both in the blockchain world and outside, so I'd hope the Fabric team would consider supporting more WASM-on-Fabric natively. Having something like Grid using it would be an excellent motivator.

I would assume there are other places aside from WASM where the Grid -> Transact -> Sawtooth dependency chain today makes for additional work to drop in Fabric, but it would be great to map those out and consider a layer of abstraction. Or if it's more complicated than that due to simply fundamental differences between Sawtooth and Fabric, to articulate what motivated parties could do to address that gap.

I realize there is a longer-term interest in seeing Transact itself supported on Fabric, but I leave that to others to work out; I assume it's a heavier lift than Grid->Fabric but would love (prefer, even!) to be wrong.

Brian


On 3/10/20 4:48 PM, clive boulton wrote:
Apparently Fabric currently prefers chain code native smart contracts.
Architecturally is there any other way to interoperate so that Fabric could run Grid ...

e.g. Is it practical to add Wasm support to Fabric so that Transact could run on Fabric? 

Btw, Wasm seems to have solid developer adoption in Seattle at Microsoft/Google, because the IoT edge is more resilient with a memory safe capabilities-based programming language. https://www.meetup.com/Seattle-Rust-Meetup/events/266941413 ) DAML also found a very fine-grained delegation model similar to the OCAP [object capability] model helps to solve resilience https://cacm.acm.org/magazines/2019/9/238966-daml/fulltext


-- 
Brian Behlendorf
Executive Director, Hyperledger
bbehlendorf@...
Twitter: @brianbehlendorf


Re: Intro - Digital Asset Trust Framework

clive boulton
 

Apparently Fabric currently prefers chain code native smart contracts.
Architecturally is there any other way to interoperate so that Fabric could run Grid ...

e.g. Is it practical to add Wasm support to Fabric so that Transact could run on Fabric? 

Btw, Wasm seems to have solid developer adoption in Seattle at Microsoft/Google, because the IoT edge is more resilient with a memory safe capabilities-based programming language. https://www.meetup.com/Seattle-Rust-Meetup/events/266941413 ) DAML also found a very fine-grained delegation model similar to the OCAP [object capability] model helps to solve resilience https://cacm.acm.org/magazines/2019/9/238966-daml/fulltext