Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Minutes: Public Dev Calls [every Wednesday] #37

Open
moul opened this issue Nov 19, 2023 · 44 comments
Open

Minutes: Public Dev Calls [every Wednesday] #37

moul opened this issue Nov 19, 2023 · 44 comments
Assignees
@waymobetta @leohhhn @michelleellen
Labels
⌚️ minutes Issues tracking meeting notes from recurring meetings.

Comments

@moul
Copy link
Member

moul commented Nov 19, 2023 •
edited
Loading

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
<!-- instructions, please, do not touch -->

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)
    

<!-- write below this line -->
---

## 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
Copy link
Contributor

michelleellen commented Nov 21, 2023 •
edited
Loading

Gno.land Developer Call (Contributors) Recap from 22.11.2023

Agenda:

  • On-Chain project management recap (Dragos)
  • Berty update on the final steps for GnoMobile (maybe Berty?)
  • Flippando update(Dragos)
    • on time for public launch in November, waiting on the PR for GRC721 SetTokenURI to be merged
  • Varmeta presentation
  • Gno Unity SDK - GoC, Dotnet library wrapper - working on a game and use it to sample projects to publish on Gno.land mainnet.
  • Onbloc mainnet support and wallet
  • GnoChess repo
  • Teritori update
  • Q&A and Gno Core team feedback

Notes:

  • Testnet 4 will be launching in December, after Portal Loop.
  • Portal Loop, as Testnet 4 will allow publishing contracts with the latest stdlibs and examples/ packages.
  • Discuss API strategy
    • Official SDKs
    • Specific SDKs
      • Unity-SDK - Go to C binding, to be used with DotNet, Python, etc
      • Gnomobile - Uses Gomobile to generate libraries embedding the Go binary + Go runtime and create the bindings + provide a gRPC local API; Can be extended with custom Go code; or just be used to provide a local gRPC API to your existing program.
      • tm2-js-client + gno-js-client - Gno client for the internet guys
    • TODO: @jefft0 to open a PR against @moul's PR to help making #1047 mergeable and better.
  • Gnomobile vs. gno-js-client, in the context of mobile app
    • native vs embedding a browser
  • Dragos working on gno-app-in-under-one-hour
  • Core Team to prioritize the review of client-oriented PRs to prepare for the upcoming Hackathons
  • Can core team review the wallet security issue posted by Onbloc?
  • Onbloc's updates for today's call: Onbloc's Builder Journey hackerspace#29 (comment)

📹 Recording

@gnolang gnolang locked as off-topic and limited conversation to collaborators Nov 22, 2023
@gnolang gnolang deleted a comment from adr-sk Nov 22, 2023
@thehowl thehowl changed the title Public Dev Calls - Meeting Notes Minutes: Public Dev Calls [every Wednesday] Nov 24, 2023
@thehowl thehowl pinned this issue Nov 24, 2023
@thehowl thehowl added the ⌚️ minutes Issues tracking meeting notes from recurring meetings. label Nov 24, 2023
@michelleellen
Copy link
Contributor

michelleellen commented Nov 27, 2023 •
edited
Loading

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

  • What is new?
    • fix(cmd/gno): allow testing packages which contain test files with package x_test 1330

Section Three: DAO and economics

  • What is new?
    • Naming changes (Contributor DAO is now more or less GovDAO. WorxDAO includes all support tasks currently covered by AiB such as EngineeringDAO, GrantDAO, etc.)
    • Governance Module/current governance documentation will be released by Dec 1
    • Prop 848 research, Twitter Space, and work on ATOM One
  • What is planned and in the works for the next two weeks?
    • Finalizing the fee/gas systems after a couple more meetings +
    • Further Game of Realms automation +
    • Game of Realms tasks defined, monthly meetings started, and scoring system designed
    • Starting an economics podcast with Michelle
    • Trip to France to see Manfred and the Gnoland team

Section Four: VM and gnolang

  • What is new?
  • What is planned and in the works for the next two weeks?
    • Final review: fix: properly mark array elements when an realm slice is updated
      1305
    • Work on issue 1326

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 michelleellen reopened this Nov 27, 2023
@michelleellen
Copy link
Contributor

michelleellen commented Dec 6, 2023 •
edited
Loading

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:

  • Flippando update on launch 🥳time to play!
  • Berty news on naming to replace GnoMobile and updates from the team. New application for GnoSocial
  • Onbloc updates on issues and pull requests and Adena
  • On chain project management proposal by Dragos
  • Varmeta application
  • GnoChess update

Q&A or other callouts and updates

@gnolang gnolang unlocked this conversation Dec 6, 2023
@michelleellen
Copy link
Contributor

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

  • What is new?
  • What is planned and in the works for the next two weeks?

Section Three: DAO and economics

  • What is new?
    • Reward debate: % of fees per tier vs GNOT reward pegged to USD value per tier (salary/UBI)
    • Tokenomics workshop recordings on various topics
    • Gas system/fee equation work continuing, met with the engineering team regarding implementation
    • Teamed up with Dev Rel to begin defining GoR scoring rubrics/protocols/UX. Preparation completed
  • What is planned and in the works for the next two weeks?
    • Next draft of gas + fee work to be submitted for review
    • Modeling both reward system options
    • GoR scoring/protocol v2 with additional automation scripts
    • Aiming to port math/rand package from Go to Gno
    • Agent-Based Modeling example built in Gno

Section Four: VM and gnolang

Section Five: Tendermint 2

  • What is new?
  • What is planned and in the works for the next two weeks?

Section Six: Q&A

Free form discussion on issues that require more discussion!

proposal: ordered tree-structured maps 1374 (Morgan)

@michelleellen
Copy link
Contributor

michelleellen commented Dec 20, 2023 •
edited by jaekwon
Loading

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:

  • Teritori update on VRF, escrow module and other topics
  • Berty update on Gno Social
  • Flippando - status update
  • Onbloc news on pull request progress
  • GnoChess updates following retrospective
  • 40 seconds in the desert

Q&A

Happy Holidays and until the next time in 2024 ❤️

@michelleellen
Copy link
Contributor

michelleellen commented Jan 10, 2024 •
edited
Loading

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)

  • What is new?
    • As announced in the chat, we have a new team member. Please welcome Kristov -- he will be working as a security engineer 🎉
    • Native Bindings is merged!
    • gnodev has been merged. You can now use it to efficiently develop contracts, using a single command to launch gnoweb + the blockchain + perform the deployment.
    • Leon is continuing work on the docs, documenting the standard library. #1468
  • What is planned and in the works for the next two weeks?

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

Section Three: DAO and economics

  • What is new?
    • Break is over!
    • Official tokenomics documentation gradually being completed/revised
    • Go/Gno Game of Life & Moses Agent-Based Models
    • DAO structure mostly finalized
    • GoR v2 submission and scoring systems
  • What is planned and in the works for the next two weeks?
    • Meeting with Google's Gemini team
    • Finish additional documentation
    • Finish GoR scoring rubric/guidelines in tandem with Effective Gno
    • Integrate GoR submission system into the User Profile GitHub directories
    • Onchain analysis and data scraping
    • Using VM benchmark data to finish gas & fee systems
    • Discussing a grant proposal to structure our work into an academic paper

Section Four: VM and gnolang

Section Five: Tendermint 2

  • What is new?
  • What is planned and in the works for the next two weeks?

Section Six: Q&A and discussion points

  • Kick off weekly meme faceoff?

@michelleellen
Copy link
Contributor

michelleellen commented Jan 16, 2024 •
edited
Loading

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

  • Working on a Portal Loop guide, suggestion is trying with staging for now and will also work with Portal Loop.

Recording

@jefft0
Copy link

jefft0 commented Jan 17, 2024 •
edited
Loading

Berty

  • GnoSocial Journey: Berty's dSocial Builder Journey hackerspace#51
  • GnoSocial backend implemented: PostMessage, PostReply, RepostThread
  • Realm code stress testing - Feedback needed from Gno core team
    • Should we test on gnoland or gnodev?
    • Should we test the Rust implementation?
    • Should the test code be custom Go code or in gno test?
    • Is it valid to test the current code or wait? (Any major upgrades planned?)
    • Why is gnoland much slower than gnodev (because not in-memory?)
    • How to increase gnoland limit for gas-wanted?
  • GnoSocial web interface progress demo
  • Meeting with Varmeta/Onbloc/Manfred next week on Account Session ("transaction cookies")
  • Guilhem: ETA on Tracking to merge fix/gnodev-block-commit gnoverse/dsocial#2 ? This fixes faucet interaction with gnodev, needed for testing.

@hthieu1110
Copy link

hthieu1110 commented Jan 17, 2024 •
edited
Loading

Teritori Gno Project Manager

  • Demo link: https://deploy-preview-702--testitori.netlify.app/projects/

  • What is working:

    • As a Funder:
      • I can create a project and fund it
      • I can put a potential developer If I want
      • I can search a project and chose a project to fund
      • I can accept/reject a proposal from a developer
      • I can review/approve and pay a milestone
      • I can manage my invested projects
    • As a developer:
      • I can create a project
      • I can add a potential funder if I want
      • I can search a project and submit my candidate to become the developer for that project
      • I can accept/reject a proposal from a funder
      • I can change state of milestone: Open/In progress/Review
      • I will receive needed amount once the milestone is set to completed by funder

  • What missing:

    • Resolve the conflict when it happens by DAO
    • We can search developer/funder by name instead of address
    • When an user become a funder/developer, the contract creator can accept/reject if he want, the deposited amount will be transferred back to funder
    • Interact with Social Feeds: when contract create, change state, discussions ....

@irreverentsimplicity
Copy link

Flippando launch in beta and roadmap

@adr-sk
Copy link

adr-sk commented Jan 17, 2024 •
edited
Loading

Onbloc's Update (Jan 17, 2024)

gnolang/hackerspace#29 (comment)

@michelleellen
Copy link
Contributor

michelleellen commented Jan 24, 2024 •
edited
Loading

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

  • What is new?
    • GoR (and eventually Gnoland) GitHub contributor profiles will be entering testing by the end of the week
    • Tokenomics/DAO legal discussions
    • Flippando modeling prep w/ Dragos (scenario modeling, sensitivity analysis, etc)
    • All data received to begin the GovNo/GovOne airdrop simulation (thanks Albert and Thomas!)
  • What is planned and in the works for the next two weeks?
    • Inital repo testing for GoR profile scripts and new submission process
    • Additional tokenomics docs/recordings/conversations (incl Building Gnoland series w/ Christina)
    • Begin Flippando modeling
    • Complete first version of the GovNo/GovOne airdrop sim
    • New tokenomics meeting schedule

Section Four: VM and gnolang

Section Five: Tendermint 2

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

Recording link

@michelleellen
Copy link
Contributor

michelleellen commented Jan 31, 2024 •
edited
Loading

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:

  • Teritori

    • Updating Escrow for on-chain project manager
      • Connect latest Escrow realm to on-chain project manager frontend and test on demo UI
      • Refactoring to manage multiple milestones in parallel
      • Contract metadata addition to handle extra data
      • Addition of milestone priorities
      • Add contractorCandidates mechanism and allow proposal submission and accepting by project funder
      • SubmitFunder to accept milestones optionally instead of all milestones
      • Update usage of OrigCaller to PrevRealm for upcoming upgrade
      • Add missing validations on contract accepting logic
      • In progress of adding multiple tokens manager realm which handles both GRC20 and bank module tokens (GNOT)
      • PR - feat: project manager TERITORI/gno#12

  • Berty

    • GnoSocial: Updates to UI
    • The Berty test node is now using gnodev with GnoSocial (+ faucet) http://testnet.gno.berty.io/r/berty/social:jefft0
    • Stress test app chore: Add misc/stress-test gno#1583
      • Guilhem is adding gnodev options to save memory.
      • Is there an advantage to test with local GnoVM instead of gnodev?
      • Gno utility to format a JSON string for return?
      • Need feedback: The Run script uses a loop to add 50 messages each time. If more than 50 then the call to Run takes too much gas. However if I update r/demo/boards with a test API function and send a transaction to Call it, then the function's loop can add 400 messages in each transaction. This is a lot more efficient for long stress tests. Why the difference? Does Run have so much more overhead?

  • Onbloc

    • Adena Demo of the air-gap feature and new sign-in flows!
    • Full updates from Onbloc: link

  • Varmeta

    • Account session update
    • Gno Unity SDK update

  • GnoChess

  • Flippando

    • Steady on the roadmap, this week: game management, picking up unfinished games
    • stuck on "VM panic unexpected object with id", issue here

  • Blockdudes (Amrit)

    • Mutli sig grant, Ledger contribution, and ideas

  • Meme Realm

Q&A

Recording

@michelleellen
Copy link
Contributor

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)

  • What is new?

    • New logging standardization #1302
    • Added Gnodev in the root Makefile #1626
    • Gno (programming language) to be referred as simply Gno, instead of Gnolang #1607
    • Added Gnodev reference to the docs; make install.gnodev is now a top-level command

  • What is planned and in the works for the next two weeks?

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

Section Three: DAO and economics

  • What is new?
    • User profile system in final testing stages
    • GovGen sim, testing, & analysis framework nearly complete
    • Ray and I renewing gas & fee discussions (CPU cycles and transaction processing time)
    • Gnoland legal reviews in-progress
  • What is planned and in the works for the next two weeks?
    • Finishing and formatting profile system + continuing to add features
    • Adding GovGen framework to atomone-hub repo for future use/parameter changes
    • Begin Flippando modeling : minting and token supply discussions
    • Gas & fee system progress (largely based on CPU and time, not mem or storage)
    • Discussing future storage fee solutions and validator deterrents
    • Community updates/communication

Section Four: VM and gno

  • What is new?
  • What is planned and in the works for the next two weeks?
    • Better support for precompilation, which will allow to precompile non-Go standard libraries other than std.
    • Working with Maxwell to review and iterate on gno type check, a landmark PR for type safety in Gno.

Section Five: Tendermint 2

Section Six: Q&A and discussion points

Recording

@michelleellen
Copy link
Contributor

michelleellen commented Feb 24, 2024 •
edited
Loading

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:

  • Teritori:
    • PRs
      • GRC20 and Banker tokens management on a single registry in collaboration with Leon (Support multiple tokens (GRC20 + Banker) TERITORI/gno#14)
        • Use grc20-dynamic-call-with-registered-interface branch from gnoswap as reference for this realm
        • Add/Modify RealmAddr, BalanceOfByInterfaceName, TransferByInterfaceName, BalanceOf, TransferFrom, Transfer, appendBankToken functions on the registry
        • Refactor GRC20Pair -> TokenInfo, pkgPath -> token, isBank field add, required functions addition for adding bank token
        • Unit test fixes (TestUnregisterUnauthorized, TestUnregisterAuthorized)
        • CLI script to deploy registry and bar token realm & register ugnot as bank token on the registry + testing
        • BankerTypeReadonly typo report (fix(docs): banker typo gno#1634)
      • Escrow realm modification after testing through CLI
        • Resolve build issues for contract rendering on Escrow
        • Remove funding process on create contract when it's created by funder
      • Review interactive debugger for GnoVM
    • give a brief overview of upcoming grant proposal
  • Berty
  • Onbloc
  • Varmeta
    • Finalizing grant overview
  • DecentraHub with Mateo
  • Dragos is traveling - Flippando roadmap

@michelleellen
Copy link
Contributor

michelleellen commented Feb 24, 2024 •
edited
Loading

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

  • What is new?
    • The GoR and eventual mainnet user/contributor profile system completed its first successful test at 1am last night!
    • Flippando analysis framework nearly complete (what-if scenario analysis, sensitivity analysis, value capture/economic simulations)
    • AtomOne analysis framework + dashboard nearly complete (to assist community coders and non-coders alike in discussing eventual ATONE distribution)
    • Gnoland community Office Hours, townhalls, articles, and other communication efforts are continuing as planned
    • Discussions around validator deterrents ("bad actor alert" from Tendermint resulting in an account freeze + review, a trustworthiness score, etc)
  • What is planned and in the works for the next two weeks?
    • Finishing tests of last 2-3 profile scripts, spot check CSV formatting, and begin adding additional features
    • Complete a comprehensive README for the profile system
    • Fix and finish equations within the Flippando sim and submit it to hackerspace for Dragos's use
    • Fix a final AtomOne analysis bug and add additional graphing support
    • Additional office hours, townhalls, and articles

Section Four: VM and gno

Section Five: Tendermint 2

  • What is new?
    • Alas, N/A 🙃
      • @zivkovicmilos: For now! Lots of Tendermint improvements are in the pipeline 😎
  • What is planned and in the works for the next two weeks?

Q&A

@waymobetta
Copy link

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:

  • Onbloc

  • Berty

  • Teritori

    • Token registry realm (GRC20+Banker) test and fixes (Support multiple tokens (GRC20 + Banker) TERITORI/gno#14)
      • GRC20 token registration and token send test and confirm success
      • Resolve GNOT bank token send from realm issue (used RealmSend permission) & confirm success in CLI
      • Resolve coinSent.AmountOf build issue in communication with Leon
    • Integrating token registry package into Escrow (Support multiple tokens (GRC20 + Banker) TERITORI/gno#14)
      • Prepare package version of token registry and deploy
      • Add token registry instance on Escrow
      • TransferFrom and Transfer methods to use token registry
      • Resolve type conversion issues in TransferFromByInterfaceName
      • Deploy token registry integrated version of escrow and testing token registration and fund/release

  • Flippando

    • Adena wallet integration, wip
      • question 1: is there a way to display a GRC20 token in Adena? If so, is there a standard way to do it, something like the URL of the GRC20 package, and a standardized method, like TotalSupply()? Or we can add a different method that returns a custom total supply of the GRC20 token? In Flippando case, the supply is divided into locked and unlocked (fungible) tokens.
        • You can permissionlessly add any GRC20 tokens in Testnet3 via the Manage Tokens button in the Wallet menu.👍
        • To add extra information about your token such as its logo or a description, please register it on the gno-token-resource repo. 👍
      • is there a way to import an existing seed phrase programatically? Example: I create a wallet with gno-js, I save the seed phrase in local storage. Is there a way to read from local storage and add this wallet? (AFAIK, the answer is no, but checking if something changed). Related to this: is there any integration between the Wallet objects defined in Adena, and the one in gno-js? Can we call a gno-js object from within Adena libraries?
        • Can you elaborate more on "importing an existing seed phrase programatically?". Ok, no, unfortunately it's something that a wallet shoudln't provide due to potential security issues. 👍 Can I ask you why do you need this feature for?
        • It might be easier to onboard users if we create their account "underneath" any existing UI. But it's ok. Moving forward.
        • Yeah I agree but this will cause a lot of concerns for users who understand how a wallet works :(
    • multi-chain dashabord live (placeholder for chain-related metrics) - deployments on Gno, Saga, Evmos, Polygon, Near (Aurora), Arbitrum, Optimism and Goerli
    • dynamic canvas size, based on the total number of unused basic NFTs

  • Varmeta

    • Account Abstraction Gno Account Abstraction hackerspace#58
    • Unity SDK update:
      • Implemented send api
      • Implemented airdrop feature
      • Unity sample for send and airdrop feature
    • Demo (Unity SDK + game showcase)

Q&A

Berty:

  • Naming: Gnonative, Gno Native Toolkit, Gno Native Kit?
    Response: We settled on "Gno Native Kit". (Formerly "GnoMobile".) For brevity, the repository and package is gnonative.
  • As I understand it, you can write a package that contains bindings from a Gno package, which are invoked via Java (Andriod) or Objective-C/Swift (iOS)?
    Response: See the system diagram in the Gno Native Kit proposal: GnoMobile, a Gno Framework for Mobile. Implementation Plan gnonative#15 . It makes calls through gRPC where the gRPC client can be in any language (Java, Swift, etc.) which gRPC supports.
  • Is there caching in place next time the app (Gnosocial) is open, until the newest fetch, older data will be shown?
    Response: These are two questions. We plan to implement local caching. Secondly, like most social apps, it will let you scroll the current view. If there are more messages, there will be a "refresh" button to fetch them.
  • Do you have an official site page outside of the repo?
    Response: We have a journey for Gno Native Kit (formerly GnoMobile) Berty's GnoMobile / Gno Native Kit Builder Journey hackerspace#28 and a new journey for GnoSocial Berty's dSocial Builder Journey hackerspace#51 . Of course, the Berty organization has its web page https://berty.tech .

Varmeta:

  • How is the signing done- browser with Adena or is signing done within Unity, in that case do you have an in-game wallet?
    Response: We plan deploy that game on mobile so we will use in-game wallet, it already supported on our unity sdk.

@michelleellen
Copy link
Contributor

michelleellen commented Mar 21, 2024 •
edited
Loading

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

  • What is new?
    • Flippando analysis/sim dashboard ready for scenario testing, will be posted on hackerspace today under a new directory
    • GovGen launched, attention is shifting back towards AtomOne and its possible distributions
    • Game of Realms system and profile review, presentation being put together for the rest of the team
    • Working with marketing to finalize articles and video content
    • OFAC sanctions check script
  • What is planned and in the works for the next two weeks?
    • Phil H grant starting, currently filling him in on current progress before his writing begins
    • Game of Realms presentation based on our automated profile system, grading rubric, bounty ideas, and similar recommended changes coming soon
    • AtomOne analysis dashboard for use in proposal discussions getting posted on GitHub, first GovGen proposal being posted soon
    • Continued legal reviews of all projects
    • Work with Dylan and Ray to finalize the oracle, GNOT airdrop, and fee/gas benchmarking
    • Gnoland constitution drafts

Section Four: VM and gno

Section Five: Tendermint 2

  • What is new?
    • No code has been merged again; but we've been cooking...
    • Internal gnokey security audit in progress, looking good so far (Kristov)
  • What is planned and in the works for the next two weeks?
    • Antonio developed a GraphQL API for the Transaction Indexer. This implements filtering functionality while also bringing massive improvements to the storage layer of the indexer.
    • We're also adding an endpoint to retrieve transaction results directly
    • We're working on a rework of the Tendermint consensus engine
    • Also considering removing alternative database implementations, such as BoltDB, from the tendermint 2 code; in an effort to make our lives easier (and eventually, focus on optimising a small subset of databases!).
    • We're adding an option to disable the Write-Ahead Log; this is mostly useful for gnodev, where it doesn't serve much of a purpose anyway.

Q&A

@michelleellen
Copy link
Contributor

michelleellen commented Mar 21, 2024 •
edited
Loading

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
Copy link
Contributor

michelleellen commented Mar 21, 2024 •
edited
Loading

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)

  • What is new?
    • Memeland is now LIVE!! 🎉
    • You can now edit the Gno.land node configuration straight from the command line, without needing sed, grep or other hacks! gnoland config, #1605
      • The API is likely to change, by making the names of the config fields the same as the TOML fields: #1769
    • Gno.land has received a small face-lift:
      • Docs & Playground now in the navbar
      • Updated text on home page, event page, about page, etc
    • Test4 preparaton talks 🐣
      • First attempt at a chain that doesn't need to be reset.
      • Does test4 have multiple validators? (yes)
      • Let's get creative, names welcome
    • Morgan's been developing a small tool, gh-sql, to fetch data from GitHub repositories to have them in a Sqlite database. This will mostly be useful for Game of Realms, and possibly as a tool to improve our PR reviews
    • Docs - Search bar is finally here! Just in time for the call - props to Albert!
    • Maxwell, grepsuzette, Joon, r3v4s, and others have all been super active with their contributions! Thanks!
  • What is planned and in the works for the next two weeks?
    • Better error logging with Gnodev #1790 @gfanton
    • Type checking when calling linter gno lint
    • More Coin & Coins functions in Gno #1696
    • Docs:
      • Getting started & how-to section refactors
    • "Go to Gno" event in Seoul, Korea on Saturday (with the help of OnBloc)

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

  • What is new?
    • txtar now parses quotes properly for gnokey #1745
    • The gnofaucet command now uses gnolang/faucet, a more resilient version originally developed by Milos; this enables the portal loop faucet to actually work. #1614
    • gnodev now supports the flags --node-rpc-listener, --chain-id, --no-replay and --max-gas. #1622
    • CGO is now disabled in makefiles, which have been reorganized #1715
    • Updates to p/demo/ufmt:
    • Indexer with new performance improvements and GraphQL API is finally merged!
  • What is planned and in the works for the next two weeks?
    • JSON arguments in Msgcall (demo at the end)
    • gnoweb will get some (internal) rehauls, and one important feature which is to be added is the ability to view Godoc-style documentation for Gno packages, realms and standard libraries. Issue #522
    • Discussion: Run gnoweb from any commit, a richer doc service for realms, readme.md display, everything through gnoweb instead of different versions in different places. API could be used by wallets and other clients, so it is the most documented system by default through gnoweb. Discoverability all docs from local realms from gnoweb backend. (please edit if I didn't properly capture)

Section Three: Governance and DAO structurization

  • What is new?
  • What is planned and in the works for the next two weeks?
    • @moul, clarify the plan like AtomOne/GovGen and its genesis repo: Constitution, plan, list of concerns to address.
    • Organize town halls or architecture sessions afterward to collaborate effectively.

Section Four: VM and gno

  • What is new?
    • Clarified that Gno does not support shadowing native types #1711
    • Ongoing effort to fix closures created within for loops led primarily by Jae and Maxwell
      • Ideas: Replace label statement with a block statement, until the next label. (in progress)
    • Native bindings no longer support "linked types": #1700. This simplifies their functioning, and paves the way for some future transpiler changes.
  • What is planned and in the works for the next two weeks?
    • Enforce rules to disallow builtin/uverse name shadowing #1793
    • External contributor: Termination analysis to panic on non-terminating statements #1750
    • Make time.Now return different timestamps for different transactions. #1777
    • Adding the math/overflow stdlib: #1698

Section Five: Tendermint 2

  • What is new?

    • WAL can now be optionally disabled @dylan #1723
    • tm2/pkg/maths was replaced with min/max #1746

  • What is planned and in the works for the next two weeks?

Q&A

@michelleellen
Copy link
Contributor

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:

  • Onbloc

    • Onbloc x Gno Core Workshop to Define Key Tasks for Testnet4 (Meeting)
    • The uint256 Package
    • Pop Window + Responsive UI for Adena
    • Automatic GRC20 Registry
    • Go to Gno Meetup (Recap)

  • Berty

    • GnoSocial app UI updates
      • Follow/Unfollow button
      • Display following and followed users
      • Display "home feed" with followed posts
        • Need to follow all the users you are following, things are saved as a realm function. (Refresh = gas)
      • Use back-end RefreshHomePosts
    • RefreshHomePosts
      • Explicitly spend gas to pull new followed posts
      • 10_000_000 ugnot only enough for about 100 posts
      • Meta question: Why a limit on gas? Will it be increased?
        • If you can only process 100 posts, that is not much.
        • Amount of gas will not match gnot. In general, it makes sense to have a limit per block, reasoning - it is not just to not overwhelm, but it is to have a shorter time period of reaching consensus.
        • Gas limit is potentially on the lower side if we are considering real application development.
        • The number of gas used is being benchmarked and calculated (maximum amount allowed). Example for Test4 10x.
        • The block gas might increase - but more general problem is not to increase the gas, but here is how we can think about realms storage. We will eventually have Merkle Proofs, if you are using AVL tree relatively optimized, and can create services outside of the blockchain to read data and provide readers a set of proofs, that 'this is good' is generally what we can do. Solution idea: multiple indexers with accountable signed results, so if you get a wrong result you can have an audit.
        • How can we move it off chain to an indexer? How do you not rely on a single centralized server, multiple competing. (Correctness and availability)
        • Indexer results signed, and prove a fraud proof, there could be a slashing (data formating required). Language here is irrelevant, more about the data or Merkle Tree structure.
      • Can RefreshHomePosts "know" that it's about to run out of gas?
      • Would a different data structure make sense?
      • Multi message and multiple transactions with one signature.
      • [chain] Gas Estimations gno#1826 (open discussion)
      • With concurrency, we should be able to support a long running process using left over gas?
    • Met with Flippando about using Gno Native Kit
      • npm package progressing (makes it easier to build)

  • Zentasktic

    • zentasktic_core data types and logic, marshaling
    • Question: The progress made towards making gnovm written in JSON output. Is there any timeline to merging this? feat(keeper): handle JSON arguments in MsgCall gno#1776. Also potentially updating the Gno API, and how we interact with it. Multpile questions to answer before it is merged. Gno rush :)

  • Flippando

    • meeting with Gno Native and started a Flippando mobile app using Gno Native Kit

  • Varmeta

  • Teritori

    • Opened issue about invalid PrevRealm in init() functions during gno test runs: PrevRealm within init() functions in gno test is invalid gno#1852

    • Brainstorm on "worxdao" data aggregator: https://hackmd.io/@80hyAELHTEe760NS2xnc2g/SJjEhkUAT?view

      This definition of worxdao things come from docs and talks with manfred that updated parts of the intent.

      Questions:

      • Do you agree with the direction it's going in?

      • Should we rename worxdao to worxaggregator? Since it's not a DAO

        • Maybe considers hours, duration, weeks, so it is a tool to evaluate contributions to the project

      • @grepsuzette said:

        worx is a cool name and I like the concept. But the name of the dao itself, I suggest to compare "Work DAO" VS "Worx DAO". Contribution DAO, Evaluation DAO, Support DAO, very neutral and grounded names, similar to Apple products like Numbers, Pages. Worx DAO sounds different and breaks the pattern.

        For the points I like "worx" as it's differentiating (working for worx). I suggest keeping it for worxaggregator but maybe rename the eventual DAO. What is your opinion on this?

      • Strict types or anys in the interfaces?

    • Brainstorm on github account linking: https://hackmd.io/gj0T70HTQiSHYrRKhrvcPg?view#Proposal-1

      We are starting a PoC of Proposal 1 with mocked signature verification here: https://github.com/TERITORI/gno/pull/16/files

      Questions:

      • Do you plan to support golang's stdlib's signature verification packages?
        • It is not a gno signature now, it can be anything you want.
      • We would like to use ed25519, should we make PR to add it in gno std? Makes sense to support what is in tm2. You don't necessarily need this if an address is not derived, but nice to support. Golang.org x crypto (needs more info)
      • If yes, should we use the same pattern as with sha256, wrapping go's stdlib?
      • Comments:
        If we do end up adding it, I can't see it being a port to gno since these libs are usually optimized client-side

@michelleellen
Copy link
Contributor

michelleellen commented Apr 17, 2024 •
edited
Loading

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)

  • What is new?

    • Test4 Milestone is live! Track progress for test4.
      • will be adding a project board (in two weeks)
    • gnoland secrets PR merged 🎉
      • Chain overflow initiative - Store your node and go! Linked to this master issue for test4
    • Gnoclient reference & short how-to guide added to the docs
    • Go to Gno Seoul successfully finished! Read OnBloc's recap here
    • Overview from the gas benchmarking workshop
      • Use standardized contract to measure physical CPU for each op code, to get an idea on how to configure gas parameters. Conclusion: node is stable, some issues related to setting min gas price.

  • What is planned and in the works for the next two weeks?

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

Section Three: Governance and DAO structurization

  • What is new?

    • Organizing workshop on governance DAO needs

  • What is planned and in the works for the next two weeks?

    • Governance and DAO test4 requirements

Section Four: VM and gno

Section Five: Tendermint 2

  • What is new?

    • Milos & Petar have wrapped up initial work on a tendermint consensus engine library (libtm). We are in the process of publicizing it, and running it through an internal audit with @kristovatlas

  • What is planned and in the works for the next two weeks?

@michelleellen
Copy link
Contributor

michelleellen commented Apr 17, 2024 •
edited
Loading

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:

  • Fraud proof generation as an interesting topic

  • IBC first, maybe in the future roll ups

  • Gno has built in Merkle Proofs, so it will be easy to have clients that verify the state of the blockchain

  • Focus on Test4 and roadmap is coming soon

  • Berty

  • Teritori

    Our current focus is on developing a proof of concept realm that allows linking a GitHub account with an on-chain address. This realm aims to enable users to associate their GitHub identity with an on-chain address bidirectionally.

    Current Status

    1. Linking GitHub Account with On-Chain Address

      • The realm allows a bot to add a public key.
      • The bot can sign the address and GitHub ID account.
      • This functionality permits everyone to link their account on the realm seamlessly.

    2. Blockers and Solutions

      • PR: #1863:
        • This PR enables the realm to verify a signature.
        • Currently in the review stage.
      • PR: #100:
        • This was an issue blocking the publish transaction.
        • Resolved and merged.

    3. Demo

      • We have created a demo showcasing how the flow works:

    Next Steps

    1. Aggregate Worx/Hours Distribution

      • We have begun development on the worx/hours distribution aggregator.
      • Our focus is on creating a generic aggregator that allows specialized aggregators like contribution to register on it.

    2. Related PRs

      • Branch: #17:
        • This PR is related to the development of the generic aggregator.
        • It focuses on allowing specialized aggregators, such as contribution, to register.

  • Contributors feedback

Q&A

@michelleellen
Copy link
Contributor

michelleellen commented May 6, 2024 •
edited
Loading

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

  • What is new?
  • What is planned and in the works for the next two weeks?
    • Repo coming soon - standalone repo on genesis, constitution, design of the inter DAO (IBC equivalent of DAOs)
    • AtomOne Genesis repo (TODO add link)

Section Four: VM and gno

Section Five: Tendermint 2

Section 6: Questions :)

@michelleellen
Copy link
Contributor

michelleellen commented May 6, 2024 •
edited
Loading

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

TERITORI/gno#19

  • Develop a worx package that will deal with all the Worx functionnalities and easily usable for all realms related.
  • A mock realm that will inyect random Worx for a given address this in order to start a PoC of what would be the profile page

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

  • public faucet set up at https://faucet.flippando.xyz, waiting for the integration with the Faucet hub
  • fixed and slightly improved the multi-chain dashboard at https://flippando.xyz
  • moderate progress using gnonative, played with the npm package and started refactoring for React Native

Zentasktic Core

ZenTasktic Project

Berty

Varmeta

Roeun Students :
Malek:

  • Surprised, happy and proud to be cited for the 2 PRs (ufmt multibyte & and todolist example V0).
  • Working on a GnoFundMe (crowdfunding example), finished a quick V0 and working on the front with react as @leohhhn suggested. Will try to have the project/example as complete as possible.
  • As discussed with @moul, will think about one of some important missing pkgs on GNO to work on it.

Theo

  • I made a pull request (PR) on issue#11 of the memeland repo. Then I will make corrections based on the comments from @leohhhn or @zmilos.
  • I wanted to create a library, but I stopped at developing a logistics system for the books.
  • After a brainstorming session with @moul, I want to start working on creating a UUID for Gno. Currently, I was thinking of building on the UUID from Go. If you have any tips on best practices for success, I'm all ears :) Sequential ID library (link)

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

@michelleellen
Copy link
Contributor

michelleellen commented May 22, 2024 •
edited
Loading

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

  • What is new?
  • What is planned and in the works for the next two weeks?

Section Four: VM and gno

Section Five: Tendermint 2

  • What is new?
    • Worth mentioning again - std.Emit by @notJoon!!
  • What is planned and in the works for the next two weeks?

Section 6: Questions :)

@michelleellen
Copy link
Contributor

michelleellen commented May 22, 2024 •
edited
Loading

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

  • speed, usability and gas fees improvements, by replacing gnokey maketx with query
  • refactor for using different endpoints, including support for Portal Loop (and future integration of https://faucet.flippando.xyz with the Faucet Hub)
  • Flippando airdrop 🎉 mechanics. Requesting 5-7 minutes for a demo
  • TLDR
    • use hackerville.xyz as the launch site (certs to be added soon).
    • 10,000 basic NFTs, 8x8 squares
    • airdrop mechanics: 156 hackers sliced into individual 64 basic NFTs.
    • 156 hackers = 9984 basic NFTs
    • and 16 basic NFTs as very rare, OG collection, maybe very clear gradients using all the shapes

Berty

Teritori

  • Completed Tasks:

    • Resolved issues in GnoVM, including preventing infinite loops caused by cyclic references and fixing the inability to use structs as keys in maps (PR #2036, PR #2044).
    • Enhanced Gnoweb by prettifying json code blocks in realm render (PR #2033).
    • Fixed broken cd examples && make lint command (PR #2034).

  • Ongoing Tasks:

    • Waiting for review/merge on PRs addressing Go2Gno type info loss (PR #2016) and printing all errors from goparser (PR #2011).
    • Continuing work on Genesis tx indexing, with pending feedback on a solution for retrieving genesis transaction results (PR #1941) and a patch for the tx-indexer (PR #34).

  • Further Developments:

    • Advancing efforts on the DAO SDK, atomic PRs (PR #1925), guides addition in docusaurus sidebar (PR #26), and requests for integrating docusaurus and markdown files (Issue #27).
    • Continuing development on the WorxDAO/aggregator. Currently waiting for genesis tx result indexing guideline so we can target portal loop
    • Continuing on Github Account linking.
      Question: Since another version has been merged recently (with oracle framework), should we continue on our version of github account linking? It supports bidirectional linking and allows to offload gas cost from oracle operator to user.
    • Progressing with the Project Manager and Conflict solver module atomic PRs (Branch).

  • Exploration:

    • Hackaton idea: Gno multi-user DAW (Digital Audio Workstation) (Issue #65).

Varmeta

Rouen Students :

Malek:

  • Still working on GnoFundMe, discovering how gno-js tm2-js and adena wallet work. Progressed on the front (but will need help), working on the coin side too.
  • Campaigns for:
    • individuals (need help or other)
    • startup/project creator on gno.land...
    • patreon like campaigns.
  • Maybe create categories, and a search bar.
  • Discussion: (maybe open a PR so anyone can comment?)
    • Is it a good idea to have users registered (to be sure of the wallet owner!!)?
    • Moderation: how to moderate and who moderates (when a campaign isn't legal/moral...)?

All are welcome to add contributions

@michelleellen
Copy link
Contributor

michelleellen commented May 22, 2024 •
edited
Loading

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

  • What is new?
  • What is planned and in the works for the next two weeks?
    • Let's unlock the topic next week!

Section Four: VM and gno

Section Five: Tendermint 2

  • What is new?
  • What is planned and in the works for the next two weeks?
    • Finally adding gas estimations
    • Integrate validator set as a realm, not a genesis file

@michelleellen
Copy link
Contributor

michelleellen commented May 24, 2024 •
edited
Loading

Gno.land Developer Weekly (Contributor Edition)

Date: 22.05.2024

Recording

Agenda:

Core team is coming live from Belgrade❤️

Onbloc

Dragos

Berty

Teritori

  • GnoVM

    • Cannot use struct as key of a map: We resolved the issue where structs couldn't be used as keys in maps. This PR has been merged (PR #2044).
    • Go2Gno loses type info: This issue is still awaiting review and merge (PR #2016).
    • Gno Issue with pointer: We proposed a solution (Issue #2060).
    • Stacktrace functionality: We added stacktrace functionality and replaced some uses of Machine.String (PR #2145).
    • Recover not working correctly with runtime panics: We created an issue to address this problem (Issue #2146).
    • Panic when adding a package with subpaths: We worked on this issue and waiting for review and merge PR #2155).

  • Gno lint

    • Printing all the errors from goparser: This improvement is waiting for review and merge (PR #2011).

  • DAO SDK

    • DAO SDK: Waiting Review and merge: PR #1925.

  • Project Manager
    Since we have already a lot in review, before opening a PR on the Gno repo, we're taking time to:

    • Polish the "private" atomic PR
    • Polish the UI
    • Set-up e2e testing with gnodev and a gno-js-client wallet, you can see a demo recording here, the end-goal is to run e2e tests in CI

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 gnolang/gno#2076 (Reviewing)

Malek:

  • No big news, still working on GnoFundMe.
  • Thanks to @iam-agf for all the comments he left on this PR #2085, I kindly ask others when they have time to go check this PR and comment with questions/suggestions...

Antonio (Add link to project)

All are welcome to add contributions

@michelleellen
Copy link
Contributor

michelleellen commented Jun 5, 2024 •
edited
Loading

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
Copy link
Contributor

michelleellen commented Jun 12, 2024 •
edited
Loading

Gno.land Developer Weekly (Contributor Edition)

Date: 05.06.2024

Recording

Agenda:

Onbloc

  1. Multinode/Validator Docs: docs: new validator docs (+ updated docs for gnoland cli) gno#2285
  2. test4 Validator Initiative Discussion: Testnet 4 Validator Initiative Discussion hackerspace#69
  3. GnoSwap Portal Loop Migration Blocker: [bug/portal_loop] runtime error: index out of range [2] with length 0 while deploying certain realm on poral-loop gno#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

  • tx-indexer genesis PR34 (related to PR1941? ) / Jeff
    • blank screen bug fixed
  • dSocial latest features / Iuri
    • reply to a post
    • view other user's posts
    • others
  • UI conversation with Alexis - to plan soon

Teritori

  • GnoVM

    • Add stacktrace functionality and replace some uses of Machine.String: This pull request is currently in review discussions with Morgan (PR #2145).
    • Go2Gno loses type info: This issue is Merged (PR #2016).
    • Avoid instantiation of banker on pure package: This change is awaiting review and merge (PR #2248).
    • Missing length check in value declaration: This pull request is also awaiting review and merge (PR #2206).
    • Issue: File line not set on ValueDeclr, ImportDecl, TypeDecl: The issue has been resolved and closed (Issue #2220).
    • File line not set on ValueDeclr, ImportDecl, TypeDecl: The fix has been successfully merged (PR #2221).

  • Gno lint

    • Printing all the errors from goparser: This pull request has been successfully merged (PR #2011).
    • Lint all files in folder before panicking: This pull request is awaiting review and merge (PR #2202).

  • DAO SDK (still waiting for review)
    PR: #1925

Var Meta

Q&A

  • SPONSOR TX
    If this feature is make sense and approved, can we integrate it into a dapp like gnostudio? var-meta is currently available to support this implementation.
  • ZK LOGIN
    Since Adena implemented the Web3Auth login based -> We are starting thinking about ZeroKnowledge-Proof-based as a login protocol where user privacy is paramount, and minimal data disclosure is desired during authentication.
    The questions are:
    What are special standards / requirements for a login protocol in GNO? Is it need to be audited?
    What is CoreTeam view about Adena's Web3Auth Login compare to ZKProof Base protocol?
    What does CoreTeam think if we use MODIFIED opensource or SELF-Developed libs in implementation of ZK Proof?
    Is it possible to add ZK Proof Validator into tendermint2 to adaptive with ZK Proof?

Mustapha

Antonio

All are welcome to add contributions

@michelleellen
Copy link
Contributor

michelleellen commented Jun 26, 2024 •
edited
Loading

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
Copy link
Contributor

michelleellen commented Jun 26, 2024 •
edited
Loading

Gno.land Developer Weekly (Contributor Edition)

June 19th, 2024
Recording

Agenda

Berty

Onbloc

Teritori

Dragos

  • Flippando
  • ZenTasktic
    • started work on UI for all 3 packages, core, project and user, basic dashboard to follow up on development at https://gno.zentasktic.com
  • Questions
    • when calling myNFT.Approve(std.CurrentRealm().Addr(), tokenId), CurrentRealm().Addr() returns the address of the file containing the code, marketplace.gno, not of the package, r/demo/flippando. Is this by design? Are there different addresses for each file?
    • when marshalling manually, using byte arrays, there is a random " appended at the end of the JSON response. This kinda breaks the cleaning of the response with gno js client. Using gnodev, this doesn't happen.

Var Meta

Title: ZeroAddress issue: gnolang/gno#2316
Des:
- provide g100000000000000000000000000000000dnmcnx as ZeroAddress as std.ZeroAddress or genesis.
- Init an Account for ZeroAddress when chain starts (?)
- Additional, considering that the banker.Remove() should substract burner's coins and add this corresponding amount into ZeroAddress.
Status: WIP - Making some realm usecases.

Title: gasUsed in unit test issue: gnolang/gno#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: gnolang/gno#2311
gnolang/gno#2272
PR: gnolang/gno#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: gnolang/gno#2152
PR: gnolang/gno#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: gnolang/gno#2350
Status: WIP

Title: Print out the transaction hash when maketx executes successfully
issue: gnolang/gno#2303
PR: gnolang/gno#2309
Status: Under reviewing

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

Title: Define Ownable and Transferrable Interfaces
issue: gnolang/gno#2193
PR: gnolang/gno#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: gnolang/gno#2307
One approval and new reviewing

Theo ->
UUID
PR: gnolang/gno#2076
wait new review with new corrective

Oracle VRF
Issue: gnolang/gno#2364

Zak

PoC Innovation Students

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

Alex:

  • Working on a small project to write some basic gno (FutureMe clone) inspired by r/demo/memeland

All contributors welcome to share updates!

@michelleellen
Copy link
Contributor

michelleellen commented Jul 10, 2024 •
edited
Loading

gno.land Developer Weekly (Core Team Edition)

June 26th, 2024
Recording

Today, we will have the last 20 minutes for presentations from the SCP Roeun students.

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

  • What is new?
    • @moul
    • Continued work on GovDAO

Section Four: VM and Gno

Section Five: Tendermint 2

  • What is new?

Section Six: Security

Presentation/feedback from our first SCP cohort

  • Malek
  • Zak
  • Mustapha
  • Theo

gnobro demo by Guilhem what you all are here for! :)

@michelleellen
Copy link
Contributor

michelleellen commented Jul 10, 2024 •
edited
Loading

gno.land Developer Weekly (Contributor Edition)

03.07.2024
Recording

Team Contributors

Onbloc

  • Testnet4 related work merged:
    • docs: new validator docs (+ updated docs for gnoland cli) #2285
    • feat(stdlibs/std): restrict Banker methods based on caller of GetBanker #1921
    • refactor(stdlibs/std): re-organize gnoEvent struct #2160
  • Generic support experiment by Byeongjun
  • Applying onbloc-api in GnoScan to support custom RPC networks (+custom indexers) will be done by the end of this week
    • Also adding gnoEvent information in upcoming GnoScan
    • Looking into finding the best way to support events tree (events in depth) in GnoScan. One possible way is to have getlog RPC call in Gno so it can be used in tx-indexer to support this functionality. You can find the discussion here.
  • For the coming weeks, we will be focusing on supporting testnet4 with valiadator, deploying Adena & GnoScan and developing GnoSwap's governance contracts.

Berty

Var Meta

  • [Adena Wallet x tm2] SPONSOR Service demo video - Introduce the service and Q&A

  1. Title: ZeroAddress
    issue: [Discussion] std.ZeroAddress gno#2316
    Des:

    • provide g100000000000000000000000000000000dnmcnx as ZeroAddress as std.ZeroAddress or genesis.
    • Init an Account for ZeroAddress when chain starts (?)
    • Additional, considering that the banker.Remove() should substract burner's coins and add this corresponding amount into ZeroAddress.
      Status: WIP - Making some realm usecases.

  2. Title: gasUsed instead of time in gno test
    issue: Add gno std package function GasUsed gno#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

  3. Title: Verify and Sign functions now are not a pair
    issue: [gnokey] Verify and Sign function are not harmonious gno#2311
    [gnokey] verify not functioning as intended gno#2272
    PR: feat(gnokey): update gnokey verify and tests gno#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

  4. Title: Define NoopMsg to facilitate the creation of gas sponsorship transactions
    issue: Proposal: Integrate Sponsor Mechanism for Transaction Fees gno#2152
    PR: feat(gnoland): Define NoopMsg to facilitate the creation of sponsor transaction (gasless transaction) gno#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: Waiting for review

  5. Title: Add missing unit tests for tm2/pkg/crypto/client
    PR: feat(tm2): Add missing unit tests for tm2/pkg/crypto/client gno#2350
    Status: WIP

  6. Title: Print out the transaction hash when maketx executes successfully
    issue: [gnokey] Display transaction hash to user after a maketx call gno#2303
    PR: feat(gnokey): Print out the transaction hash when maketx executes successfully gno#2309
    Status: Under reviewing

  7. Title: Return error when getting keypair information
    issue: Panic when getting keypair information gno#2133
    PR: fix(gnoclient): Return error when getting keypair information gno#2300
    Des: panic when getting a non-existed key name from keybase
    Status: Merged

  8. Title: Define Ownable and Transferrable Interfaces
    issue: minimal p/ownable Interface with multiple implementations gno#2193
    PR: feat(examples): Define Ownable and Transferrable Interfaces gno#2198
    Des: refactoring p/ownable from a struct with a specific implementation to a more minimal interface
    Status: Under reviewing

  9. Title: Use uassert/urequire instead of testing in some demo packages
    issue: Improve p/uassert and p/urequire gno#2481
    PR: chore(examples): Use uassert/urequire instead of testing in some demo packages gno#2491
    Status: Waiting for review

Dragos

  • end to end basic task flow demo for ZenTasktic (10-15 minutes)
  • next weeks plans: end to end enhance task flow demo for ZenTasktic, with Teams, Actors and Points

Teritori

  • Teritori Realms

  • GnoVM

    • New PRs:

      • Recover Not Working Correctly with Runtime Panics: Addressed an issue with runtime panics in Gnolang. Waiting for review and merge: PR #2484.
      • Annotate does not implement preprocessing error: Started throwing ideas about how to tackle this (Early draft) PR #2206.

    • Still Waiting Reviews:

      • Add Stacktrace Functionality: Implemented stacktrace functionality and replaced some uses of Machine.String. Currently under review: PR #2145.
      • Avoid Instantiation of Banker on Pure Package: This improvement is still awaiting review and merge: PR #2248.
      • Missing Length Check in Value Declaration: This fix is awaiting review and merge: PR #2206.

  • Gno lint

    • Still Waiting Reviews:
      • Lint All Files in Folder Before Panicking: Ensured all files in a folder are linted before the process panics. Waiting for review and merge: PR #2202.

Antonio

Student contributors

PoC

@michelleellen
Copy link
Contributor

gno.land Developer Weekly (Gno Core Edition)

July 10, 2024
No available recording

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

  • What is new?
    • We have our first genesis! Update on the internal launch of Test4 in preparation for Monday, July 15th @zmilos
      • We have roughly 30 GovDAO members for testing purposes, and by Monday will have conducted voting on 3 governance proposals and on-chain update.
    • We have the full v0.1.0 release updates
    • Important update on Namespaces in gno.land @gfanton
  • What is planned for the next two weeks?
    • A breather :)

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

  • What is new?
  • What is planned for the next two weeks?
    • Refactor, add versioning and remove nighlightlies (PR 2477) - user work flow related and manual releases @Tyge
    • Others we want to add?

Section Three: Governance and DAO structurization

  • What is new?
    • Governance Updates @moul

Section Four: VM and Gno

Section Five: Tendermint 2

Section Six: Security

  • Auditing in final stages of validation, results are being compiled into a private doc available upon request
  • Taking a quick look at GovDAO

@michelleellen
Copy link
Contributor

gno.land Developer Weekly (Contributor Edition)

17.07.2024
Recording

Berty

  • Validator Node:

  • dSocial latest:

    • ✅ Iuri: UX Improvement - syncing username with r/demo/users
    • ✅ Iuri: New Dev Tool for React Native
    • ✅ Remi: Update on notifications. Try it!
    • ✅ Jeff: Updated dSocial node with new gnodev (use less memory)

  • Gno Native Kit:

    • ✅ Jeff: Updated to use new qEval syntax

  • Gnokey Mobile:

    • 🏗️ Work started! ...with Alexis :D

Teritori

  • Teritori Node
    Updates:

    • Node Setup and Monitoring: We have successfully set up Gno nodes for test4 (validator + sentry) and added alerting mechanisms to monitor the nodes' status and ensure they remains operational.

  • Test 4
    Deployed social_feeds realm on test4
    UI: https://app.teritori.com/feed?network=gno-test4
    Gnoweb: https://test4.gno.land/r/teritori/social_feeds:teritori

  • GnoVM

    Updates:

    • Comment Fixes on Length Check: Made corrections to comments on the missing length check in value declaration: PR #2206.
    • Annotate Specific Reason for Interface Non-Implementation: Added annotations to specify the reason a value does not implement an interface. The PR has been approved and is waiting for merge: PR #2492.

    Pending PRs:

    • Add Stacktrace Functionality: PR #2145.
    • Avoid Instantiation of Banker on Pure Package: PR #2248.
    • Missing Length Check in Value Declaration: PR #2206.

  • Gno Lint

    Pending PRs:

    • Lint All Files in Folder Before Panicking: PR #2202 - Waiting for review and merge.

  • Gno CI

    Updates:

    • Gno Lint Action: We are implementing a POC Gno lint action to detect and report issues using the same mechanism as the golint-action. The temporary repository can be found here.
      Hope we will have a demo next call

    Blockers:

    • Required PR for Linting: We need PR #2202 to be merged. This PR enables linting of all files when running 'gno lint'.

Dragos

  • Zentasktic

    • ✅ zentasktic core deployed on test4. Use it at https://gno.zentasktic.com/core
    • ✅ validator node https://rpc.irreverentsimplicity.xyz/ up and running, currently synced and waiting for gov / proposal instructions
    • ✅ node above addedd to the list of persistent peers in test 4 config.toml, PR: feat: add irreverentsimplicity to persistent_peers gno#2577 merged
    • ✅ syncing a new development node for test4 (former flippando node)
      • ❓ how can I have just a consumer node (i.e. syncing with the main validators node, but not being used as a peer). Is this what a sentry node is intended to do?
    • ❓ how can I deploy a p/ or r namespace? the current p/zentasktic package is deployed on a user address: gno.land/p/g17ernafy6ctpcz6uepfsq2js8x2vz0wladh5yc3/zentasktic, same for the realm: gno.land/r/g17ernafy6ctpcz6uepfsq2js8x2vz0wladh5yc3/zentasktic_core. The idea is to have something like p/demo/zentasktic, or, even better, p/apps/zentasktic. Same for p/games/flippando.
    • kind reminder about 2 new repos for flippando & zentasktic codebases

  • Flippando

    • ⏸️ on hold, waiting to integrate the upgraded grc721 / grc20 in test4

Var Meta

About ongoing PRs, we currently have:

  1. Title: /p/demo/mux supports query strings
    issue: p/demo/mux: support query strings gno#2585
    PR:
    feat(package): /p/demo/mux support query strings gno#2594
    Status: Reviewing

  2. Title: ZeroAddress
    issue: [Discussion] std.ZeroAddress gno#2316
    PR:
    feat(gnovm/tm2): add ZeroAddress constant gno#2401
    Status: Reviewing

  3. Title: gasUsed instead of time in gno test
    issue: Add gno std package function GasUsed gno#1998
    PR: feat(gnovm): gno test now has gas used information gno#2571
    Status: Reviewing

  4. Title: Verify and Sign functions now are not a pair
    issue: [gnokey] Verify and Sign function are not harmonious gno#2311
    [gnokey] verify not functioning as intended gno#2272
    PR: feat(gnokey): update gnokey verify and tests gno#2333
    Status: Waiting for review

  5. Title: NoopMsg - Support for sponsoring things (Keypoint PR)
    issue: Proposal: Integrate Sponsor Mechanism for Transaction Fees gno#2152
    PR: feat(gnoland): Define NoopMsg to facilitate the creation of sponsor transaction (gasless transaction) gno#2209
    feat(examples): Implement sponsors (p+r) for sponsor service management gno#2411
    Status: Reviewing

  6. Title: Add missing unit tests for tm2/pkg/crypto/client
    PR: feat(tm2): Add missing unit tests for tm2/pkg/crypto/client gno#2350
    Status: WIP

  7. Title: Print out the transaction hash when maketx executes successfully
    issue: [gnokey] Display transaction hash to user after a maketx call gno#2303
    PR: feat(gnokey): Print out the transaction hash when maketx executes successfully gno#2309
    Status: Reviewing

  8. Title: Define Ownable and Transferrable Interfaces
    issue: minimal p/ownable Interface with multiple implementations gno#2193
    PR: feat(examples): Define Ownable and Transferrable Interfaces gno#2198
    Status: Reviewing

  9. Title: Implement Basic Authentication in HTTP Client
    issue: Client-side HTTP basic authentication support gno#2450
    PR: feat(tm2): Implement Basic Authentication in HTTP Client gno#2590
    Status: Reviewing

  10. Title: Fix request_id mismatch at http client
    PR: fix(tm2): Fix request_id mismatch at http client gno#2589
    Status: Waiting for review

  11. Title: Fix the endpoint /tx?hash= to make it work
    issue: [gnoland] /tx?hash= endpoint not usable gno#2489
    PR: fix(tm2): Fix the endpoint /tx?hash= to make it work gno#2518
    Status: Waiting for review

Beside contributing with PRs, We are now have ideas about:

  • Sponsor service - supporting wallets make a sponsor transaction (already demo, verifying flow with adena dev team)

  • we propose creating gno.land/p/demo/orderbook as a standard example for the Gno.land. This will enable dapp developers to build and deploy their own trading exchanges efficiently. Here is our implementation idea :

type Order struct {
	ID        string
	Type      OrderType
	Price     float64
	Quantity  float64
	Timestamp time.Time
}

type OrderBook interface {
	// AddOrder adds a new order to the order book
	AddOrder(order Order) error
	// RemoveOrder removes an existing order from the order book by its ID
	RemoveOrder(orderID string) error
	// GetOrder retrieves an order from the order book by its ID
	GetOrder(orderID string) (*Order, error)
	// GetBestBid returns the highest bid (buy) order in the order book
	GetBestBid() (*Order, error)
	// GetBestAsk returns the lowest ask (sell) order in the order book
	GetBestAsk() (*Order, error)
	// GetOrderBookSnapshot returns a snapshot of the current state of the order book
	GetOrderBookSnapshot() ([]Order, error)
	// MatchOrders matches buy and sell orders in the order book
	MatchOrders() ([]Order, error)
}
  • A proposal about Gno Name Service:
    Proposal: Developing Gno Name Service (GNS) hackerspace#73
    This project aims to develop a service that maps wallet addresses to specific names, such as yourname.gno -> g1xxx..., on the Gno.land platform. This will help users, dapps, wallet... in managing addresses.

Onbloc

  • Product updates regarding testnet4
    • GnoScan
      • Testnet4 & Portal Loop Integration
      • Fully customizable with any Gno RPC & Tx-indexer
      • gnoEvent support
    • Adena
      • Testnet4 Integration
      • Added support for custom tx-indexer
      • Updated explore menu
    • GnoSwap
      • Deployed realms on testnet4
      • GnoSwap Beta on testnet4 will be coming up next week
  • Testnet4 feedback
    • Good:
      • It was great to get a heads up from the Gno team on breaking changes so that we were able to prepare accordingly.
      • The chain feels very lively with multi nodes and faster block time. It's also great to have more nodes for making abci_query
    • Suggestion:
      • Add Multicall to RPC > Reduce the number of individual ABCI queries when fetching the balance of all GRC20 tokens for users
      • Add more getter functions to the FOO20 demo realm supported in the GRC20 package: Name / Symbol / Decimals / # of Holders > would come in handy for dApps that display GRC20 token info
      • What do you think about adding a pagination and sorting feature to the tx-indexer? (by Jinwoo)
      • Have a safer way to read on-chain data from off-chain (by Blake)
      • Upgradable Realm

Antonio

  • Shiken

Rouen Students (grants proram)

  • GnoPool

PoC Students

All contributors welcome to add

@michelleellen
Copy link
Contributor

gno.land Developer Weekly (Gno Core Edition)

July 24th
Recording

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

  • What is new?
    • Short overview of ongoing Governance discussions and considerations for Test4 (team)
      • Currently 30 members and an estimated 3 governance proposals for adding 3 validators
      • Considerations for future governance proposals: notable contributions
    • GnoBro update is done, and documentation coming soon!
    • feat(examples): implement r/events, p/authorizable (PR 2372)

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

Section Three: Governance and DAO structurization

  • What is new?
    • Recap from discussions and next steps

Section Four: VM and Gno

Section Five: Tendermint 2

  • What is new?
    • feat: protocol level dynamic gas price (PR 2544) Ray
    • expose InitChain tx responses (PR 1941)

Section Six: Security

  • Researching approaches to fuzzing:
    • generating random gno code to crash node
    • generate random gno code and compare result of gnovm to running go run on same file
  • PR reviews underway
  • Findings validation
  • Investigating graphql testing (indexer)

@michelleellen
Copy link
Contributor

gno.land Developer Weekly (Contributor Edition)

31.07.2024
Recording

Var Meta

Contributing:

Sponsor feature live demo

Gno Naming Service

  • General purpose: Helping people can interact with our chain without remembering exactly on-chain addresses. More information @here
  • Flow: User send token to human-readable-name -> wallet query to on-chain resolver to get real-address -> making transaction.
  • Current status: Designed Interfaces. Going to implement for each interface.

Teritori

  • GnoVM

    Updates:

    • Stacktrace PR: Addressed comments for the stacktrace PR.
    • Length Check PR: Addressed comments for the missing length check in value declaration.
    • New Issues Created:
    • Merged PR: Missing length check in value declaration: PR #2206

    Pending PRs:

    • Add Stacktrace Functionality and Replace (Some) Uses of Machine.String: PR #2145
    • Avoid Instantiation of Banker on Pure Package: PR #2248

  • Gno Lint

    Pending PRs:

    • Lint All Files in Folder Before Panicking: PR #2202 - Waiting for review and merge.

  • Teritori DAPP: Social Feed Map
    allowing to browse a gno social feed by exploring a world map UI. Geolocation is optional, and the address is chosen manually by the user, not automatically by device localization, to protect users while allowing them to view the community in a region, or have fun colonizing an area in groups of gnomees.

    Updates:

    • Map Post Publisher: Implemented a feature to publish posts with geolocations.
    • Indexing Posts:
      • Posts are indexed using the tx-indexer.
      • The tx-indexer runs as an independent service, and we use its GraphQL endpoint to sync all posts to our own database.
      • Detailed process: Documentation.

Onbloc

Berty

  • Jeff: (related to Gnokey Mobile developement) Update gnoclient API: Separate make, sign and broadcast tx PR2641
  • Iuri: dSocial update: new features:
    • New version - try it out!
      • usernames and keys in the app are now in sync with r/demo/users
      • clickable @mentions, http://web-links and email@addresses
      • new debug tool
    • Profile Pic feature (still cooking)
      • r/demo/profile: Standard for Avatar field issue 2598

Dragos

  • Flippando PR to be integrated in the gnoland codebase (including airdrop backend):

  • Zentasktic PR to be integrated in the gnoland codebase:

  • Flippando UI updated, including Simple, Airdrop and AI canvas:

  • Flippando airdrop checker demo (not live)

  • ZenTasktic Project questions:

    • creating a separate realm p/demo/teams acting as a base layer for team functionality (add, edit, remove team name, team members). A team should have its own address. Zentasktic Team realm will enrich this package. Thoughts?
    • pros and cons for wrapping Actors on top of p/demo/users same as above?
    • Rewards Points - what's the closest represenation we already have on chain and how do we wrap on top of it? Game of Realms?

  • Deployment question: what are the best practices for initializing a specific account on a server, to be used as the caller in a web app? Ex: hackerville.xyz is a next.js app, that needs to interact with a Gno contract that only accepts a specific account. The wallet used by hackerville.xyz needs to be initialized with a specific mnemonic. Thoughts on ansible-vault? (I already know Adena is the best way to go, just asking for a specific use case when I still use gno-js/tm-js libraries)

PoC Students

Welcome all contributors

@michelleellen
Copy link
Contributor

gno.land Developer Call

14.08.24

New Format Update:

  • Short form announcements from contributors (30 minutes):
    • Contributors can add their updates and have the 'main point' they want to cover and highlight. For contributors, we can find other mediums to extend the presentation and discussions in the future. Suggestions are welcome 😊
  • Discussions to be added and led by the core engineers and involve everyone (30 minutes + depending on discussions):

Contributor Section (short and sweet)

Discussion topics:

  • Gnokey mobile security concerns

    • An average user may not know if they are typing into a secure enclave
    • Phone hardware and software is closed and could be compromised
    • Temporary name - further discussions
    • Hardware signers will be supported

  • Berty:

    • Potential bug: Keybase 1-to-1 mapping of name/address. PR: fix: In dbKeybase.writeInfo, if replacing a name entry, remove the lookup by the old address gno#2685
      • If you try to replace existing name, you are given a prompt, and suggest to delete old entry
      • Add another PR for renaming keys, if you don't want to replace you can have a name change
    • New Feature: gnoclient API - separate transaction signing chore: In gnoclient, separate out SignTx and BroadcastTxCommit gno#2641 . This is needed for Gnokey Mobile.
    • How would signing work? Factor out a library from gnokey and make the keybase more general (RPC client) to create an HTTP connection which gnokey uses. In gnokey password request, it calls the gnokey api. Password doesn't go over HTTP - key signing app happens locally, and gets the password from the user and temporarily signs the transaction through the keybase api rather than HTTP.
    • Wrapper of a key cli service, used on the gno.land blog
    • Session keys would help with gnokey mobile and gno client
    • gno client and web socket connection discussion

  • Name service spec

    • Do we have a written spec? Reserve a name? Keep it? And what about squatters? (The squatting problem: collect and buy a bunch of names and keep them so no one else can use them)

  • Discuss adding time zone support to the Gno standard libraries: Add timezone support to the gno standard library's time package gno#2688 (Dylan)

    • Looks good

  • Discuss the usage of int64 for block numbers and native banker Coin amounts (Leon)

    • Why are the signed and not unsigned? Never have a negative block height.
      • Potential to introduce bugs with unsigned numbers
    • Discuss large storage numbers, can we use uint64?
      • Survey other blockchains to consider and inform the decision.
      • What about base account numbers and banker API? If more chains are using 256 then potentially? (Tendermint doesn't use 256, so would need to take that into account)

  • How do we see Proof of Contribution currently? How can we decide if someone is a valid contributor, that has gained the right to join the GovDAO or the validator set? (Leon)

    • Tiers of membership: Tier 1 (50% of voting power) and so on

    • Tiering conundrum:

      • One core tier, small in size can be self-mutating is manageable. Scalability is the challenge. How do you intro people to Tier1, what is the vetting process across a group of people?
      • Tier2, this adds more complexity and compounds the scaling problem.

    • Problem: Restricting contributions to one core tier adds problems

    • Problem: Sybil attacks creates challenges to scaling and the vetting process

    • Problem: Unequal distribution of expertise and experience - exclusivity

    • Problem: Voting challenges - example: voting on an individual topic may make sense, but as a whole is divergent

      • Question: Decaying curve applied to stagnant contributors? Timespans of contribution are considered in tiering model to have voters be actively contributing and informed/involved?

@michelleellen
Copy link
Contributor

gno.land Developer Call

21.08

Gno Core Announcements

  • General update from the team on test4 (Milos)
  • Gnoweb updates on revisions (Guilhem - Alexis)
  • gnoVM: correct type for shift expression #1775 (Maxwell)
  • feat: protocol level dynamic gas price #2544 (piux2)
  • fix(gnovm): correct comparison between different types #1890 - merged
  • fix(gnovm): handle non call expression valuedecl values #2647 - merged
  • Add timezone support to the gno standard library's time package #2688 (timezone locations) and feat: Add timezone location support #2705 (Dylan)
  • fix(gnovm): Fix panic when calling len()/cap() on pointer array #2709 (opened by NotJoon, feedback Dylan)
  • feat(gnovm): handle loop variables #2429

Discussion topics

  • Follow up questions from Signal GovDAO:
    • What is the scope and role of govDAO
    • What are the details about Proof of Contribution?
    • How the whole system can come to existence 'alive' and remain 'alive' after multiple eras have passed
  • Berty: (defer to next meeting) Support Rename in r/demo/users? (correct a mistake, transfer name)

@michelleellen
Copy link
Contributor

gno.land Developer Weekly

28.08

Contributor section (short form updates):

Please add your highlights ❤️

Dragos

VarMeta:

  • Ready for reviewing: #2209 noop-message and sponsor transaction #2630 PRs. Other PRs in tx-indexer, adena wallet, js-client are waiting for above PRs be approved 🙏

Berty:

  • "Mobile Key Manager App" - a lot of work, especially around the Keybase API - MVP v1.0 will be ready in the next weeks.

Onbloc:

  • Gno Core - Ready for review
    • feat(tm2): Add Specific Block Height query Feature to ABCI Queries #2722
    • feat(gnovm): Executable Markdown #2357
    • fix(gnovm): Prevent use of blank identifier in named conversion #2699
    • fix: Longer package Path Spend More Gas [investigate] #2736
  • Adena SDK related work
  • GnoSwap
    • We started an external audit of the core realms of GnoSwap with local security experts. We're expecting a report and will share it to public.

Teritori:

  • Continued on our Social feed map
  • Made plan and started work on a grc20 launchpad
  • Brainstorm on WorxDAO "cockpit" and providers (data aggregator), we have a plan and are starting to implement

Discussion topics:

If you have a topic you'd like to discuss, please add it with as much detail below.

VarMeta:

  • Anti-squatting system for both namespace r/sys/users and our domain name dapp: technical idea
    1. Registering new namespace: auction. When you are the first registering for a namespace, there is a duration for other can join in a bidding session. Also, applying the lock-down period after a namespace registered that can not be transfered / changed admin. This can help reduce the supicious registering action / reducing speculative buying / giving true market value of namespace.
    2. Safeguarding Precious Names: Thinking about a contract that holds the data-source about important / famous / common system namespace, data is pushed into contract, and is voted by DAO.
    3. Resolve conflict: If there is confliction comes from sides about namespace, then use a special DAO to vote (?). We need evidences like trademark documents, reason for registering that namespace... etc.
    4. Rent fee to keep the namespace alive. This can be done in 2 approaches:
      • Pay renewal fee
      • Proof of that namespace's owner have assets on our chain, defined by credits. If they withdraw / burn assets, then the credits gonna decrease, when the credits equals to 0, their namespace is no longer available.
    5. Thinking about oracle data that reflecting the name or word-in-name which should be voted / restricted / bid ...
  • Discuss questions:
    • is sealed bidding possible in gno?
    • is voting by DAO is good for these usecases?
    • should people deposit to get their exchanged credits, or just make it automatically base on their assets on-chain?

Berty:

Onbloc:

  • Regarding: fix: Longer package Path Spend More Gas [investigate] #2736
    • Currently, the gas consumption is determined by the length of the transaction data multiplied by an arbitrary value (default 10). Is this something that can be adjusted?

@michelleellen
Copy link
Contributor

gno.land Developer Weekly

04.09.2024

Gno Core announcements (20 minutes)

  • Testnet plans (Morgan)
    • portal loop - feat(gno.land): support setting custom height/timestamp for genesis txs PR 2751 (Morgan)
    • test4 - fix(gno.land): make gno store cache respect rollbacks PR 2319
  • Grafana demo - testnets (Albert)
  • feat(examples): a shifumi (rock, paper, scissors) smart contract (merged) PR 2629 (Marc)
  • fix: addressability PR 2731 (Dylan)
  • Initialize math/rand with entropy Issue 2745 (Manfred)
  • Gno Realm and Ownership Spec Issue 2743
    • Related test(gnovm): add test for bounding PR 2526
  • fix(gnovm): correct type comparison for bool type PR 2725(Maxwell)
  • fix: Longer package Path Spend More Gas [investigate] PR 2736
  • Updates on gas estimations and benchmarking
  • Gnome Spotlight Series on Discord (bi-weekly Thursday 5PM CEST)
  • Invite to make r/username/home realms. Examples: manfred, leon

Discussion Topics

(Please feel free to add)

  • Anti-squatting System for gno.land namespaces - needed for mainnet, priority
  • discussion on strategy re: 2319 (on test4) and 2751 (for portal loop, and future)
  • sponsor-transaction (PR 2630 PR 2209)
  • Should deploying the same code to longer pkgpaths cost more?
    • gno.land/r/leon/whatever
    • Faireness vs. security - the longer the package path, the higher the chance for a typo and an evil contract for example. Short package names recommended.

@michelleellen
Copy link
Contributor

gno.land Developer Weekly

11.09.2024

Gno Contributors (20 minute short form updates)

Follow our contributor ecosystem gnomes on Hackerspace too!

Discussion topics

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@waymobetta waymobetta

@leohhhn leohhhn

@michelleellen michelleellen

Labels
⌚️ minutes Issues tracking meeting notes from recurring meetings.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@moul @hthieu1110 @jefft0 @thehowl @waymobetta @leohhhn @adr-sk @michelleellen @irreverentsimplicity