-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ATTN IBC working group: agenda (February 13th at 17:00 CET bi-weekly call) #377
Comments
I will give a quick update on IBC implementation status, then glad to discuss any requested topics. |
question :
|
Can we get a relayer update? |
Dean notes that fixes for 0.38 are now in the IBC branch. |
What is zoom password? |
Thanks @Michelle-L |
Is there a Game of Zones update? Jack discussed the demo briefly last week. |
@zmanian says - evangelise this meeting! |
Another note - moving more IBC development to Discord. |
If you want to get added to the calendar invite, email Chris Goes or sign up for the working group mailing list. We have been sending weekly product updates and reminders for the IBC working group call and plan to do this more consistently. |
@Michelle-L Did you upload the recording somewhere? We should link it in the README file. |
Here is the recent video https://www.youtube.com/watch?v=_xP6xxvqTMM They will be uploaded following the session to our IBC youtube channel. |
Date: February 13th
Time: 17:00 CET
Zoom dial in information
If you have something to discuss, please add items to the agenda below. This issue serves as the IBC bi-weekly working group's agenda and meeting minutes.
Click here for previous meeting notes
Purpose
The evolution of IBC requires cross-industry collaboration to support developing standards that are secure, open, and deployable. The IBC ecosystem working group is a growing team of contributors supporting the standardisation of blockchain development from protocol level to applications. Join the mailing list for email and meeting updates.
Currently the IBC working group is being actively led and managed by Tendermint (All in Bits), Agoric and the Interchain Foundation. Over time, we anticipate this will shift into breakout working groups and a more decentralised way of managing the interoperability standards development process.
The text was updated successfully, but these errors were encountered: