Development talks

Communication Event
42

@HugoTrentesaux ,

When will be the next meetings? :grinning:

2 Likes
43

I did not have the availability to schedule a next meeting. I am starting to emerge and will hopefully work on a next meeting agenda.

Apart from that, there is a request from the “collectif MaJ v2” to have some devs attend their weekly monday meetings, it would be a good place to demonstrate the current state of Cesium v2. (Visio coordination de la migration v2 – Chaque lundi - Mise à jour V2 - Forum Monnaie Libre).

44

Did you guys took notes during March meeting?
I find nothing on CodiMD - Collaborative markdown notes

45

Not really, we were 2; me and @zoltounet

So we just checked a bit CesiumÂČ state :slight_smile:

1 Like
46

I am sad to hear that. Let’s try to do better for the meeting of April!

2 Likes
47

According to CrabFit, the best time is again Friday afternoon.
@contributors, so next meeting would be on Friday, April 4th 2025 at 5:00PM.

6 Likes
48

@contributors, friendly reminder. Next meeting is this Friday April 4th from 5:00 PM.

Please prepare topics you would like to talk about.

4 Likes
49

It’s now!

1 Like
50

Hi all - I won’t make it this time, just as a mini update: I caught up with @kapis to help him out with g1 superbot and paired a little on getting myself set up and planning a bit, but besides that haven’t made any progress yet.

2 Likes
52

We had a nice meeting yesterday with 8 people during 2 hours. Here is a short recap of what was discussed:

Info

  • there is design work on a gchange with moderation done here:
  • some NGI funding applications were submitted through Axiom Team
    • Pour une place de marchĂ© / Gchange
    • Pour du vote en ligne s’appuyant sur la TdC
    • Pour du SSO via g1compagnon et autres aspects de g1compagnon
  • the Axiom Team secret category was moved from Duniter forum to Monnaie Libre forum

Agenda

  • Accounts created before genesis and post genesis can be told apart using their creation block stored in squid (see Duniter-squid version 0.2.8 and Ğ1nkgo v2 support progress, plan and pubkeys/address proposal for history)
  • Urls of mirror endpoints used in clients should be known before g1 launch to allow easy transition. Up-to-date nodes and outdated ones can be told apart thanks to the genesis hash
  • We talked about a uniform centralized notification system to allow transmitting important messages through all apps
  • We designed the structure of a guidelines document that will be discussed in another forum topic. Here is what we came to:
guideline document structure
  • gestion des endpoints et des rĂ©seaux
    • gestion duniter rpc
    • gestion graphql squid
    • gestion hash genesis gdev, gtest, g1
  • gestion des secrets et dĂ©rivations
    • ed25519 par dĂ©faut
    • scan des dĂ©rivations
    • prĂ©sentation du mnemonic
    • code pin / mot de passe / [code de dĂ©verrouillage]
      • utiliser un algo comme Argon2
      • ne pas suggĂ©rer de code de <4 caractĂšres
  • gestion du compte membre vs portefeuille
    • forcer une meilleure sĂ©curitĂ© sur le compte membre
    • suggĂ©rer une meilleure sĂ©curitĂ© en cas de gros montants
    • interdire de stocker le mnemonic (uniquement stocker seed ou clĂ© privĂ©e ?)
    • ne pas donner lieu Ă  un dĂ©verrouillage du compte membre pour les transactions simples depuis compte courant
  • gestion des notification de diffusion
  • The storage use of smith nodes is a real problem that should be addressed or mitigated before g1 launch. Some options were discussed like modifying substrate to allow block header pruning or pre-allocating space on the system and preventing other apps to use it.
  • We discussed then the minimum quantity of available services. Here are our conclusions:
minimum number of services to start the g1 v2
  • forgeron
  • miroir
    • minimum technique Ă  1
    • mĂȘme critĂšres que forgeron, mais avec des exigencs en nombre plus faible (1 FR, 1 ES, 1 non-UE, 1 auto-hĂ©bergĂ©, 1 en data-center, 1 DNS bind local, 1 DNS externe hors GAFAM)
    • les critĂšres du minimum doivent ĂȘtre couverts par des nƓuds “attestĂ©s” par un membre
  • squid
    • mĂȘme chose que les miroirs
    • contrainte additionnelle dDOS
    • DoS protection | SQD
    • r&d ? authentification sur couche HTTP
  • datapods
    • strict minimum 3 par expĂ©rience C+
    • minimum 5 pour ĂȘtre “confort”
  • rĂšgle de distance et prĂ©calcul
    • mini 3
  • Finally install methods were discussed with the idea of making curl [
] | sh the default install method to reach ultimate simplicity. A way to make it decentralized using blockchain was also discussed.

For more details you can see on Dev talks 2025-04-04 - CodiMD

3 Likes