# 🏛️ Berty Townhall Meeting (weekly)

**🗓️ Date**: **September 6th, 2024**
- Gnokey Mobile - update:
- MVP will be on Testflight and Playstore in a matter of days. The objective is to launch something (like a baseline) to be then able to engage with Alexis on UI/UX (and iterate) while we continue to build the core features.
- TX signing & Key Mng
- no security in the app
- no inter-app comms yet (but cooking)
- IMPORTANT: Jae has concerns about the name. He feels it shouldn't be called "GNOxxxx" until it has been authorized. So for the moment we will hide any "GNO" related names in the UI but keep the "GNO" internal identifiers as they are (ex: gnokey-mobile).
- Question 1: WDYT, does this sound good to you?

- Gno Native Kit:
- Fixed 2 issues gnoboard: compatibility with the latest changes on Gno Native (API files) and updated expo and RN to their latest version (thus fixing the incompatibility with xcode 15.3)
- Updated the API to allow multiple accounts to use the same GNK server. (Must specify the account to use for each operation).

- Other Gno Core topics:
- Validator Node: we are preparing a new, dedicated server to host the validator node (once we get the GO from Milos).
- Question 2: should we use a Sentry Node or Sentry Architecture for the Validator or can we stay with just a Validator Node for production?

- Invitation to collaborate https://optionetwork.io/
- They said: "we are in the process of building two more apps one for chat one for a video chat. And we think you can help us build those apps using your open source"
- These are the guys that run Parler.
- Question 3: WDYT, should we consider talking with them? We think it's more a marketing outreach to grow their network.

- Potential DNS configuration vulnerability for SPF uncovered by someone. He recommends changing "~all" to the more restrictive "-all" in "v=spf1 include:servers.mcsv.net include:_spf.google.com ~all".
- Question 4: WDYT, should do this? (if so, I believe you have the admin rights to do it)

**🗓️ Date**: **August 2nd, 2024**
- Manfred: Please validate dev account on Play Console.

**🗓️ Date**: **July 26th, 2024**
- Update on Validator Node
- Are coins sent to the validator address in test Test4? (Tokenomics/incentives)
- Sentry - should we spend time to setup one?
- New debug/log mobile RN dev tool + Onboarding / Iuri
- Configure gnonative/dsocial/gnokey-mobile to require 1 approval to merge a PR - @Manfred can you help now?
- New CI improvements:
- auto build on dSocial and manual release with flag
- Gnokey Mobile - updates / high level ideas
- 🤔 dilema? Bundle (large) GNK in each dapp?

@Manfred, here's a summary of our latest progress on various fronts. We also have a small homework for you (point 1 below) :)
1. @Manfred, can you please configure gnonative/dsocial/gnokey-mobile to require 1 approval to merge a PR?
2. dSocial updates: 3 new features: 1) add URLs in the posts and 2) in-app log retrieval feature --> Iuri will make a Journey post and share a demo; 3) dSocial usernames now sync with the blockchain (same keys)
3. Gnokey Mobile: PoC ongoing as we are considering foundational (back-end related) architecture options - Jeff leads this one --> will share soon our thoughts
4. Remi: Updated go-ipfs-log and go-orbit-db to latest libp2p/kubo version. Still working on Weshnet and Berty Messenger (dependency hell).

**🗓️ Date**: **June 28th, 2024**
- Iuri: Simplify GnoNative typescript API
- Jeff: Deleting an imported key deletes the old key. Answer: Make a PR with failing test. https://github.com/gnolang/gno/issues/2446
- Jeff: txtar to demo a bug doesn't get merged. Answer: Add "bug" tag. https://github.com/gnolang/gno/pull/1736
- Big picture: Will important packages stay in "demo"? Answer: It will change.

**🗓️ Date**: **June 14th, 2024**

- Iuri: update on dSocial
- preview of the next features/fixes (gnod (snot/snog/snod... ?), etc.)
- Remi: update on Push Notifs (approach change and progress)
- Call with Alexi - brainstorm on approach
- Costin has draft plan
- To brainstorm and update together

- We are happy that Gno Core team responds to our requests to move fwd on several issues --> this is very nice and encouraging :) --> and motivating

**🗓️ Date**: **June 7th, 2024**

- Iuri: demo on dSocial
- Remi: update on Notifications
- Ethereum keys??? @Manfred wdyt?
- @Manfred when would be a good moment to start working on Gnokey mobile?
- @Manfred - OnePassword access for Iuri
- Jeff: How to move forward on https://github.com/gnolang/gno/pull/2135 ?
- Jeff: How to interact with gnoland w/o gnokey doc https://github.com/jefft0/gno/blob/chore/add-interact-with-gnoland-without-gnokey.md/docs/how-to-guides/interact-with-gnoland-without-gnokey.md
- to check with the team if we aren't missing something
- .....

**🗓️ Date**: **May 31th, 2024**
- Iuri: update on latest dSocial work
- Remi: dSocial push notifs design
- Jeff: How to move forward on indexer PR https://github.com/gnolang/tx-indexer/pull/34
- When to start Gnokey Mobile skeleton app?

**🗓️ Date**: **May 24th, 2024**
- Iuri: dSocial
- Update on user sign-ups
- Common Provider interface for Gno Native Kit and gno-js-client?
- Remi: Old expo account for berty-tech?
- Jeff: R&D report update
- Will make a hackerspace page next week
- (Sometimes gnoland stops responding with high CPU)
- Use `export DEBUG=1` . Make an issue with the zip of gnoland-data
- Grant proposals: Current status?

**🗓️ Date**: **May 14th, 2024**
- Report on tech findings
- maybe a blog section dedicated to mobile on gno website -->or directly on the gno repo?
- journey post to list and
- other place gno official blog squatting or berty blog in portal loop
- benchmarking--> open an issue / find a way to synthtise this and help people not start from scratch if they want to benchmark something new
- create documentation on how to interact with the chain via
- Quick update on dSocial on test
- WIP Iuri and Remi
- Ideas for next priorities:
- Notification (real-time) feat. on dSocial
- start with simple to implement use cases (get notified when someone you're following posts a message)
- including @mentions --> will imply indexers again
- Notif Service (as infra) --> mobile and not only mobile
- Wrapper React and React Native provider -
- Finish/add (simple) UI features started on dSocial
- 1. view other user's messages on his/hers feed
- 2. support reply threads
- Moderation DAO --> this maybe later
- Document interacting with blockchain/gRPC https://github.com/gnolang/gno/issues/2026
- Make a suggestion to Leon in the issue to add to https://github.com/gnolang/gno/tree/master/docs

- **🗓️ Date**: **May 3rd, 2024**
- **New Gno Grant**
- next steps
- PR Implement event emission https://github.com/gnolang/gno/pull/1653
- Potential demo (indexer function for the home feed)
- Release dSocial on Test Stores
- [TO DO] Update the version of GNK for dSocial
- [TO DO] Merge the PR with the indexer service
- [DONE] Recovery key feature disable --> except when creating new account
- Confirm next dates for the Townhall (May 10?)

**🗓️ Date**: **April 19th, 2024**
- **New Gno Grant**
- Show new grant approach to Manfred
- inform about the talk with Kristov in the afternoon
- target: submit by next Friday
- submit today
- more HL plan is OK --> it should be realted to the MOTIVATION ("please help us doing stuff")
- convince the core team that we have potential to be a good contributor
- individual engineers --> bootstrap the contributor pool
- simple metrics to remind of the volume of our contribs
- CORE TEAM TO CONVINCE. THAT'S IT!
- timeline history to put into context and prove that we are/will consolidate mobile specilist position --> and state that we want to deepen our expertise on gno mobile apps and devtools.
- 1) past history and
- 2) HL (flexible) goals for the future
- gnosocial BAU work is also ok
- gnokey should be in the timeline
- we already build some legos that will be used in gnokey
- backgorund gnome activity is ok
- it could be just to be sponsored to be funded whilke we "think" of gno stuff
- gno brand ID: 3d, start with isometric and see if we can make it shine on mobile. Make mobile THE place for nice visual experience.
- "we can make 3d on mobile"
- put in the plan that we will INCLUDE GNO BRAND ID (3d animation) in gnokey app.
- we can mention it even we are not ready now to included it; but we can prepare for it
- berty (seen by gno) = experts in the MOBILE niche + NICE EXPERIENCE niche
- animations for gnokey? --> jeff: animation for temp accounts
- the 1st applications that gno promotes should be awsome in animation/UI experience --> in line with gno visual identity.
- "ah, you want to see gno? check this mobile app (which has the best representation)

- **GnoSocial**
- renaming to dSocial (tbc during the Townhall)
- including renaming the repo
- publish to TestFlight
- including removing the Recovery Phrase screen
- publish to the equivalent of TestFlight for Android
- to investigate how we can do it (apk?) --> Google Play Console
- Indexer updates
- graphQL client, including websocket subscriptions

**🗓️ Date**: **April 12th, 2024**
- **GnoSocial**
- Oracle / followers tech challenge @jeff
- rename: Berty Social, SocialExp, ExpSocial, DSocial, other names

- **GNK NPM**
- update

- **Future grant:**
- debrief after Milos talk

**🗓️ Date**: **April 5th, 2024**
- GnoSocial
- Demo
- Indexer update
- Profile picture temp sol
- GNK NPM

**🗓️ Date**: **March 29nd, 2024**
- gnosocial repo change name --> not urgent but should be done / voting or we choose (SocialExp --- indicates that it will forever will remain an experiment / mokup / demo / test / explore / labs , etc --> that is easily recyclable). Future directions:
- archive all
- start a more complex project with other teams (joint venture) --> team up and build something awesome
- who pays to refresh the feed?
- indexer option (not the realm): so a "centralized" server, no storage on the chain --> need to choose/experiment with a storage solution --> so we come up with a recommendation (of a storage solution) for other Gno builders.
- TARGET: study and comparison of various options:
- A) keep logic in the realm, storage elswhere. more expensive. Keep what we have but setup and limit refresh functions to just 100 posts.
- B) have oracles (= a wallet asociated with a human, not a script) listen to contract and have an ecosystem of validators based on rewards/punishments. As a dev you have to make a single "import" - Dylan Boltz / [the "gnorkle" PR](https://github.com/gnolang/gno/pull/1568). An oracle can function automatically, without having to call it. It could proabilly self-trigger if needed (schedule itself to run again in x time). You can have "write only" oracles that just write data to the blockchain. Other smart-contracts can query the data without talking to the oracle. Obviously, the oracle must have a private key to interact with the realm; it also consumes gas: someone needs to run the oracle --> this could also be distributed (good). The oracles can interact with the internet and communicate with the internet.
- C) The builder offers/sets up the infra --> the cost could be passed on to the user or assumed by the provider (builder).
- D) others..

- ask Michelle to ask Antonio to come to at least one of Berty's sync / decide when internally
- Gno Native Kit Tutorial - episode 2 ready
- NPM progress for GNK --> maybe make one for Wesh Net. as well :)
- Berty Messenger - new release March 22nd / push notifs re-enabled!
- next steps: fixes (libp2p, IPFS), do smaller demo apps focused (BLE or other)

**🗓️ Date**: **March 22nd, 2024**

**Description:**

In this sync call we are reviewing the latest progress of the current projects, debate relevant topics (tech, product, comm and so on) and adjust priorities.

Duration: 30min - 1 hr.

**Agenda**

**Gnosocial**
* Guilhem’s JSON messages: Should we use it?
- Manfred: Yes, use it.
* Indexer: Next steps?

**Gno Native Kit**
* porting Flippando app
* GNK Tutorial eisode 2 in preparation

**Other**
* (time permitting) Does Berty Messenger implement encrypted links? (There are some unit tests. https://github.com/berty/berty/issues/2402#issuecomment-1976250373)
* April 1 is holiday (move/cancel Gno sync meeting?)