gnolang / meetings

meeting organization, transcripts, and resource sharing
3 stars 2 forks source link

Minutes: Public Dev Calls [every Wednesday] #37

Open moul opened 7 months ago

moul commented 7 months ago

Purpose: To store notes from our recurring Public Developer Calls.

Process:

  1. Initial Notes: Taken live in Hackmd or Google Docs.
  2. Posting: Notes are posted as comments here.
  3. Recording Links: Calls are recorded and shared on YouTube. Comments will be updated with these links.
### HackMD template: ``` # Gno.land Ecosystem/Contributor Call Join Gnolang's core tech team and partners for the bi-weekly developer call, a regular sync with Gnolang developers working on the technology and community members interested in the engineering and development discussions. You can find the proposed agenda below, if you have additional technical points to discuss, please add them to this issue. Previous meetings: https://github.com/gnolang/meetings/issues/37 ![image](https://github.com/gnolang/meetings/assets/117160070/535121c8-a5b6-4e88-a6d9-432bc15464a9) --- ## Gno.land Developer Call (Contributors) Date: XXX Duration: One hour of structured updates, presentations and troubleshooting from our contributors. Description: This call will primarily focus on updates from Gno.land contributors and apps or projects (even internal ones)that are building on Gno.land. ### Agenda: - XXX ### Notes: - ... ### Resources: - Notes from HackMD (link will be provided) - Recording (link will be provided) ```
michelleellen commented 7 months ago

Gno.land Developer Call (Contributors) Recap from 22.11.2023

Agenda:

Notes:

📹 Recording

michelleellen commented 7 months ago

Gno.land Developer Call (Gno Core) Recap from 29.11.202

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: DAO and economics

Section Four: VM and gnolang

Section Five: Tendermint 2

Section Six: Q&A

Free form discussion on issues that require more discussion!

proposal: ordered tree-structured maps 1374

📹 Video recording

michelleellen commented 6 months ago

Gno.land Developer Call (Contributors)

Date: 06.12.2023 at 5pm CET

Duration: One hour of structured updates, presentations and troubleshooting from our contributors

Description: This call will primarily focus on updates from Gno.land contributors and apps or projects (even internal ones)that are building on Gno.land

Agenda:

Q&A or other callouts and updates

michelleellen commented 6 months ago

Gno.land Core Team (bi-weekly)

Date: December 13th, 2023

Duration: One hour of structured updates

Description:

This call will primarily focus on the Gno Core team updates related to specific topics

Duration: One hour, with the option to go over if there are issues to cover and discuss

Agenda format

It is broken down into sections that can be discussed by respective gno core team members

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: DAO and economics

Section Four: VM and gnolang

Section Five: Tendermint 2

Section Six: Q&A

Free form discussion on issues that require more discussion!

proposal: ordered tree-structured maps 1374 (Morgan)

michelleellen commented 6 months ago

Gno.land Developer Call (Contributors)

Date: 20.12.2023

Duration: One hour of structured updates, presentations and troubleshooting from our contributors

Description: This call will primarily focus on updates from Gno.land contributors and apps or projects (even internal ones)that are building on Gno.land

Agenda:

Q&A

Happy Holidays and until the next time in 2024 ❤️

michelleellen commented 5 months ago

Gno.land Core Team (bi-weekly)

Date: January 10th, 2024

Duration: One hour of structured updates

Description:

This call will primarily focus on the Gno Core team updates related to specific topics

Duration: One hour, with the option to go over if there are issues to cover and discuss

Agenda format

It is broken down into sections that can be discussed by respective gno core team members

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: DAO and economics

Section Four: VM and gnolang

Section Five: Tendermint 2

Section Six: Q&A and discussion points

michelleellen commented 5 months ago

Gno.land Developer Call, Contributors Edition (biweekly)

Date: 17.01.2023

Duration: One hour of structured updates, presentations and troubleshooting from our contributors

Description: This call will primarily focus on updates from Gno.land contributors and apps or projects (even internal ones)that are building on Gno.land

Agenda: Onbloc Teritori update Berty GnoSocial Flippando - update on the launch! Varmeta GnoChess Meme off - time to vote!

Q&A

Recording

jefft0 commented 5 months ago

Berty

hthieu1110 commented 5 months ago

Teritori Gno Project Manager

irreverentsimplicity commented 5 months ago

Flippando launch in beta and roadmap

adr-sk commented 5 months ago

Onbloc's Update (Jan 17, 2024)

https://github.com/gnolang/hackerspace/issues/29#issuecomment-1895877273

michelleellen commented 5 months ago

Gno.land Core Team (bi-weekly)

Date: January 24th, 2024

Duration: One hour of structured updates

Description:

This call will primarily focus on the Gno Core team updates related to specific topics

Duration: One hour, with the option to go over if there are issues to cover and discuss

Agenda format

It is broken down into sections that can be discussed by respective gno core team members

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: DAO and economics

Section Four: VM and gnolang

Section Five: Tendermint 2

Section Six: Q&A and discussion points Submit your best memes!!!

Recording link

michelleellen commented 5 months ago

Gno.land Developer Call (Contributors)

Date: 31.01.2024

Duration: One hour of structured updates, presentations and troubleshooting from our contributors

Description: This call will primarily focus on updates from Gno.land contributors and apps or projects (even internal ones)that are building on Gno.land

Agenda:

Q&A

Recording

michelleellen commented 4 months ago

Gno.land Core Team (bi-weekly)

Date: February 7th, 2024

Duration: One hour of structured updates

Description:

This call will primarily focus on the Gno Core team updates related to specific topics

Duration: One hour, with the option to go over if there are issues to cover and discuss

Agenda format

It is broken down into sections that can be discussed by respective gno core team members

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: DAO and economics

Section Four: VM and gno

Section Five: Tendermint 2

Section Six: Q&A and discussion points

Recording

michelleellen commented 4 months ago

Gno.land Developer Call (Contributors)

Date: 14.02.2024 ❤️ Recording

Duration: One hour of structured updates, presentations and troubleshooting from our contributors

Description: This call will primarily focus on updates from Gno.land contributors and apps or projects (even internal ones)that are building on Gno.land

Agenda:

michelleellen commented 4 months ago

Gno.land Core Team (bi-weekly)

Date: February 21st 2024 Recording

Duration: One hour of structured updates

Description:

This call will primarily focus on the Gno Core team updates related to specific topics

Duration: One hour, with the option to go over if there are issues to cover and discuss

Agenda format

It is broken down into sections that can be discussed by respective gno core team members

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: DAO and economics

Section Four: VM and gno

Section Five: Tendermint 2

Q&A

waymobetta commented 4 months ago

Gno.land Developer Call (Contributors)

Date: February 28st 2024 Transcript Recording ^TODO: Will be uploaded via YouTube shortly

Duration: One hour of structured updates, presentations and troubleshooting from our contributors

Description: This call will primarily focus on updates from Gno.land contributors and apps or projects (even internal ones)that are building on Gno.land

Agenda:

Q&A

Berty:

Varmeta:

michelleellen commented 3 months ago

Gno.land Developer Call (Core Edition)

Recording

Date: March 6th, 2024

Duration: One hour of structured updates

Description:

This call will primarily focus on the Gno Core team updates related to specific topics

Duration: One hour, with the option to go over if there are issues to cover and discuss

Agenda format

It is broken down into sections that can be discussed by respective gno core team members

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: DAO and economics

Section Four: VM and gno

Section Five: Tendermint 2

Q&A

michelleellen commented 3 months ago

Gno.land Developer Call (Contributors)

Recording

Date: 13.03.2024

Duration: One hour of structured updates, presentations and troubleshooting from our contributors

Description: This call will primarily focus on updates from Gno.land contributors and apps or projects (even internal ones)that are building on Gno.land

Agenda:

Q&A

michelleellen commented 3 months ago

Gno.land Developer Call (Core Edition)

Recording

Date: March 20th, 2024

Duration: One hour of structured updates

Description:

This call will primarily focus on the Gno Core team updates related to specific topics

Duration: One hour, with the option to go over if there are issues to cover and discuss

Agenda format

It is broken down into sections that can be discussed by respective gno core team members

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: Governance and DAO structurization

Section Four: VM and gno

Section Five: Tendermint 2

Q&A

michelleellen commented 3 months ago

Gno.land Developer Call (Contributors)

Date: 27.03.2024

Duration: One hour of structured updates, presentations and troubleshooting from our contributors

Description: This call will primarily focus on updates from Gno.land contributors and apps or projects (even internal ones)that are building on Gno.land

Agenda:

michelleellen commented 2 months ago

Gno.land Developer Call (Gno Core)

Date: April 3rd, 2024 Recording

Duration: One hour of structured updates

Description:

This call will primarily focus on the Gno Core team updates related to specific topics

Duration: One hour, with the option to go over if there are issues to cover and discuss

Agenda format

It is broken down into sections that can be discussed by respective gno core team members

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: Governance and DAO structurization

Section Four: VM and gno

Section Five: Tendermint 2

michelleellen commented 2 months ago

Gno.land Developer Call (Contributors)

Date: 10.04.2024 Recording

Duration: One hour of structured updates, presentations and troubleshooting from our contributors

Description: This call will primarily focus on updates from Gno.land contributors and apps or projects (even internal ones)that are building on Gno.land

Agenda:

Discussion points:

Q&A

michelleellen commented 1 month ago

Gno.land Developer Call (Gno Core Edition)

Recording

Date: April 17th, 2024

Agenda format

It is broken down into sections that can be discussed by respective gno core team members

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: Governance and DAO structurization

Section Four: VM and gno

Section Five: Tendermint 2

Section 6: Questions :)

michelleellen commented 1 month ago

Gno.land Developer Call (Contributors Edition)

Recording

Date: 24.04.2024

Agenda:

Drum roll......the Gno.land Faucet Hub is live 🎉 Are you interested in adding your gno-chain to the hub? Let us know. Here's the Readme with instructions.

Onbloc

Teritori Main focus Worx Aggregator

https://github.com/TERITORI/gno/pull/19

What we're aiming to accomplish right now is the indexation of the worx_added events in order to display them on a profile page (Worx based).

image

Secondary focus

trying to understand and review ongoing PRs that will be usefull on Dev path, For example feat(gnovm, tm2): implement event emission with std.Emit #1653 Dragos

Flippando

Zentasktic Core

ZenTasktic Project

Berty

Varmeta

Roeun Students : Malek:

Theo

All contributors welcome to add questions 🎉 there are quite a few new ones

michelleellen commented 1 month ago

Gno.land Developer Calls (Gno Core Edition)

Date: May 1st, 2024

(no recording available)

Agenda

It is broken down into sections that can be discussed by respective gno core team members

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: Governance and DAO structurization

Section Four: VM and gno

Section Five: Tendermint 2

Section 6: Questions :)

michelleellen commented 1 month ago

Gno.land Developer Calls (Contributor Edition)

Recording

Date: 08.05.2024

Agenda:

Quick over view of the highlights from Gno Core

Onbloc

Dragos

ZenTasktic

Flippando

Berty

Teritori

Varmeta

Rouen Students :

Malek:

All are welcome to add contributions

michelleellen commented 1 month ago

Gno.land Developer Calls (Gno Core Edition)

Recording

Date: May 15th, 2024

Agenda

It is broken down into sections that can be discussed by respective gno core team members

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: Governance and DAO structurization

Section Four: VM and gno

Section Five: Tendermint 2

michelleellen commented 1 month ago

Gno.land Developer Weekly (Contributor Edition)

Date: 22.05.2024

Recording

Agenda:

Core team is coming live from Belgrade❤️

Onbloc

Dragos

Berty

Teritori

Varmeta

Rouen Students :

Theo: UUID package -> It’s not finished because they forgot a resolver, and I'm looking for a good method for that because Gno does not support sync/atomic. @notJoon mentioned using crypto/rand, but it hasn't been merged yet https://github.com/gnolang/gno/pull/2076 (Reviewing)

Malek:

Antonio (Add link to project)

All are welcome to add contributions

michelleellen commented 3 weeks ago

Gno.land Developer Weekly (Gno Core Edition)

Date: May 29th, 2024

Recording

Agenda

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: Governance and DAO structurization

Section Four: VM and gno

Section Five: Tendermint 2

michelleellen commented 2 weeks ago

Gno.land Developer Weekly (Contributor Edition)

Date: 05.06.2024

Recording

Agenda:

Onbloc

  1. Multinode/Validator Docs: https://github.com/gnolang/gno/pull/2285
  2. test4 Validator Initiative Discussion: https://github.com/gnolang/hackerspace/issues/69
  3. GnoSwap Portal Loop Migration Blocker: https://github.com/gnolang/gno/issues/2283
    • Liquidity Pool realm deployment failing on portal-loop
    • Attempts tried:
      • Changing package path / reducing realm size / setting gax-wanted to max / changing client env
      • Cloning gno repo every single recent commit to re-produce on local but never failed.
    • Update: Potential cause → Certain failing txs are causing corrupt cache files cacheNodes

Dragos

Berty

Teritori

Var Meta

Q&A

Mustapha

Antonio

All are welcome to add contributions

michelleellen commented 6 days ago

Gno.land Developer Weekly (Gno Core Team Edition)

June, 12th, 2024

Recording

Agenda format

It is broken down into sections that can be discussed by respective gno core team members

Section One: What to Gno section: What are the highlevel updates to share! (short and sweet a TL;DR)

Section Two: Gno.land Blockchain: Faucet, implementation, Portal Loop, clients, SDK as examples

Section Three: Governance and DAO structurization

Section Four: VM and Gno

Section Five: Tendermint 2

michelleellen commented 6 days ago

Gno.land Developer Weekly (Contributor Edition)

June 19th, 2024 Recording

Agenda

Berty

Onbloc

Teritori

Dragos

Var Meta

Title: ZeroAddress issue: https://github.com/gnolang/gno/issues/2316 Des:

Title: gasUsed in unit test issue: https://github.com/gnolang/gno/issues/1998 PR: WIP due to #2149 is reviewed and discussed. Des: Want to expose gas used in unit test, then add it into gno test -cover Status: WIP

Title: Verify and Sign functions now are not a pair issue: https://github.com/gnolang/gno/issues/2311 https://github.com/gnolang/gno/issues/2272 PR: https://github.com/gnolang/gno/pull/2333 Des: This PR changes the Verify() to read the signed doc, verify the exactly original message hash that was signed. It also adds chainid, account-number, account-sequence config flag to the gnokey verify command. The sign function now expose the hex-format of signature to the IO in oder to feed the verify as an argument. I think we need better way for user to verify their signed document, which currently need this hex-format Status: Waiting for review

Title: Define NoopMsg to facilitate the creation of gas sponsorship transactions issue: https://github.com/gnolang/gno/issues/2152 PR: https://github.com/gnolang/gno/pull/2209 Des: define SponsorTransaction which contains a NoopMsg and a specific Std.Msg to pay fee on behalf of someone. Details inside the PR Status: WIP

Title: Add missing unit tests for tm2/pkg/crypto/client PR: https://github.com/gnolang/gno/issues/2350 Status: WIP

Title: Print out the transaction hash when maketx executes successfully issue: https://github.com/gnolang/gno/issues/2303 PR: https://github.com/gnolang/gno/pull/2309 Status: Under reviewing

Title: Return error when getting keypair information issue: https://github.com/gnolang/gno/issues/2133 PR: https://github.com/gnolang/gno/pull/2300 Des: panic when getting a non-existed key name from keybase Status: Under reviewing

Title: Define Ownable and Transferrable Interfaces issue: https://github.com/gnolang/gno/issues/2193 PR: https://github.com/gnolang/gno/pull/2198 Des: refactoring p/ownable from a struct with a specific implementation to a more minimal interface Status: Under reviewing

Rouen Students

p/timelock and p/accesscontrol : PR: https://github.com/gnolang/gno/pull/2307
One approval and new reviewing

Theo -> UUID PR: https://github.com/gnolang/gno/pull/2076 wait new review with new corrective

Oracle VRF Issue: https://github.com/gnolang/gno/issues/2364

Zak

PoC Innovation Students

Docs and ecosystem exploration done, starting some small projects Mohammed:

Alex:

All contributors welcome to share updates!