---
# System prepended metadata

title: APRIL Logos Labs Agenda - Reports
tags: [Logos Innovation Lab]

---

###### tags: `Logos Innovation Lab`
To plan meetings: check availability
[kiki](https://calendar.google.com/calendar/u/0?cid=a3Jpc3RpZW5kZXdhY2h0ZXIuc2FAZ21haWwuY29t)
[barbara1](https://calendar.proton.me/api/calendar/v1/url/DDYrtLP_tPDXlv4HmiArSP-2c3r3f-7610qTXJ46bSYS1sHoco2ZX4csOqb4RKYjMUXkGjUkKJ8tZr4FHq41qQ==/calendar.ics?CacheKey=z1SmcJPK_L4_J-o3K7g_hw%3D%3D) [barbara2](https://calendar.proton.me/api/calendar/v1/url/w8kSOBO_u7rGPX3wgRg3JQL6z643wefeb4ql38er5bm1durUS_DdHPDgNvNYVDvETwFZ5p64dsZ0O2ujT11qsQ==/calendar.ics?CacheKey=osf-ufjSuyZZx9otcJQfNQ%3D%3D) [barbara3](https://calendar.proton.me/api/calendar/v1/url/_7JIn7AU27RvefcutNTll5OlBPdc0qbClAP8XS7ZsAESIathe9AhslJw8aep65AOU34liKDBB0PJVJ3NWBGoyw==/calendar.ics?CacheKey=RUCuLII37RZCL-3IfcGDBg%3D%3D) (sorry I work with multiple calendars and can't export them together as one 😕)
[david](https://cal.com/davidgauquelin)

# APRIL Logos Labs Agenda - Reports

## meeting report 27.04  team meeting

**Michelle**
Back from the visit to Attila in Nice
Happy with the way of working, more like rapid prototyping, having things to play with and improve from there.

**Barbara**
working on the playground repo together with Vojtech

**Vojtech**
It feels good to just dive in, able to make decisions, or to discover things that need to be resolved later.
Trying to figure out Kurate and Zkitter, writing the documentation and lessons learnt for follow-up, propably draft doen by next team meeting

**David**
All good, back from holiday
prepared for the retro

**Philippe**
not much update, can we continue talking about WAKU Object > meeting is planned for friday

**Attila**
Prepared the retro

**Matt**
Happy to help Vojtech with writing up documentation

**Kiki**
Question about Kurate: are we following up on Tsukino?
Michelle will do this
David also has some improvements for Kurate 
TODO: Michelle and Kiki talk to Ned and see how we can handover Kurate, will come back with info

## meeting report 25.04 waku objects work meeting

This report is a destillation and grouping  of the topics that were discussed and the arguments or questions that were raised.

### Way of working:
Instead of working in a sequence (research-design-develop-communicate) we want to work simultanious with all skillsets. Up until now David has made first designs, Vojtech and Barbara have buikd the chat app and Philippe has been doing tech research.
We are still in the phase where we can think of what could be possible in 5 years, and from there we need to define the scooe of what we can start working on now, what are the first steps.

### what could be possible (long term thinking)?
#### A chat app with a waku object where 2 people can privatly and off-chain transact with a zk rollup
**Q:**  how would this work? 
**A** zk stuff, machine that works in the dark, trusted parties.
**Q:** What about the trusted parties? Do we need to work with attestations? Or so we have to get trust in another way (via other app), or do we even need to worry about trust, assuming that 2 people in a chat already have some trust? 
**A** we will have to go on chain at a certain point, something has to validate. we can use zkevm, but then we need transactions
 
#### A store and a design system for waku objects. 
**Q:** Can we have a little zk machine for each waku object?
 **Q:** Do we need to think on the  trusted parties topic (establishing trust versus assuming there is trust)?

### What we could start with now 
#### Can we start with the simple thing: chat between 2 people, plus button to add an object (hello world), sign the message, getting the object in 2 places?
**Q:** Why do we need permission to load an object? 
**A:** maybe to see its credibility, to signal it is ok to show this object in the app, or as spam protection...

#### Can we scope the project to chat app with a plus button to add an object, have a design guide for developers to build objects and gave a store for these objects?

### what is out of scope for us now
Let's not get into the trust-issue

### unclear/need to solve
are we gonna build a platform? a protocol? or an example/examples?

## Meeting Report 20.04 Team meeting
**Michelle**
Going to have a talk with Al on future collaboration and on Acid taking over Kurate.
once the hand-over is finalised, we can archive Kurate on our github (no traces)

**Philippe**
No updates on Kurate
Waku Objects: been studying protocols, not sure if this will be usefull. Probably easier if the concept is more refined first and the priorities are clear.
**TODO**: organise a work-meeting early next week to get the direction of where we are going in the next two weeks. 

**Vojtech**
UPdate on Kurate: creating post works, creating persona doesn"t work, chat send works, chat receive doesn't work
Will try to get everything running locally
Go doesn't work (waiting on tech to be ready)
Rep doesn't work, is it worth it without the GO?
Excited to start on WAKU Objects, already putting David's design into Front-end, so we can play and iterate quicker.
**TODO**: sort the persona's in Kurate standard to most users at top

**Kiki**
**ToDO** take the lead on having a technical handover document for Acid. With the current state and the todo's or what we are waiting for. Vojtech will write this.

**Barbara**
Acid forked Kurate yesterday.
Learning more on Svelte
Going through David's design and giving input


## Meeting report 18.04 team meeting

**Michelle**
Is going to present Kurate to the Logos Townhall the 25th.
Making clothes as a hobby project
Talking to Ned to handover Kurate, idea is that they clone the whole repo and we have a clean slate in our team on github

**Philippe**
Focussed on the VAC specs and getting a basic chat working
On Kurate: still issues, figured some of them out

**Barbara**
Checked in with Vojtech yesterday, going to work on some functionalities for Waku Objects
Worked on some issues for Kurate

**Matt** 
Went through all the WAKU objects documents and designs
Preparing for good retro

**Kiki**
Looking into good ways to organise a retro that is constructive and leads to improvements that are supported by everyone.


## Meeting Report 13.04 team meeting

**Michelle**
Attila would like to join the team for the second project as from May. 

**Vojtech**
Happy about Attila
Made a second adapter for zkitter in god mode: infinite GO and REP, no restrictions. But so far posting, publish persona and chat don't work yet. 
Need guidance into Waku Objects, where to start

**Philippe**
On Waku Objects: reading the specs, setting out the base for chat
For Vojtech: create a simple chat, create identity, talking to other people, + button. Build this quick qnd dirty so we can iterate and modify later

**kiki**
Can we update the read.me on Kurate to give more info to developers coming in?

## Meeting Report 13.04 core dev meeting

### Updates

#### Vojtech

Implemented a `zkitter` godmode adapter, that overrides the methods that require REP to use the routes that don't.

Tried to run `zkitter` with Tsukino's comments from last time but is having some issues:
- When posting
    - `The leaf does not exist in the tree`
    - `Cannot read properties of undefined (reading 'syncGroup')`
- When publishing a persona
    - `It does nothing but says that "Epoch 1 ended" and "polled before setup, nooping"`
- When starting a chat
    - `Cannot read properties of undefined (reading 'siblings')`

Asked Tsukino if he could prepare a readme with steps of how to run everything locally, including `zkitter-js`. There's actually no need to run `zkitter-js` locally anymore because everything is in the browser, including caching. The circuits are now served through the relayer, so the `zkitter` servers are no longer necessary.

#### Tsukino

Will get back at us offline.

## Meeting Report 11.04 Team meeting

Today was a bit of a "special" team meeting with only Vojtech, Philippe, Michelle and Kiki.
We took the opportunity to have more of a unorganised talk about a few topics

- we discussed the first use issue, starting without rep, so if there is not a lot of activity (yet) in the app it is hard to build rep. We decided to gift every new user 50 REP.
- there is still some work that needs to be done on the circuits (Tsukino) 
- Philippe suggests to have a 2nd adapter for dev-mode with no Go and no REP so the zkitter implementation can be tested. Later another adapter wit REP and lastly one with REP and GO
- RLN is not compatible, Tsukino is working on that
- Michelle will talk to Acid.info Ned to see if they want to play more with the app and see who can take over Kurate
- let's collect all the feedback we have on the app, doesn't mean we will execute on everything, but we should list this so we can give advise on what is possible, what needs more attention while we proceed on to the next project
- Kiki will plan a retro. 


## Meeting Report 07.04 core dev meeting

### Updates

#### Tsukino

Doesn't think there's too much left to get a working MVP. Todo:
- [ ] Figure out who can post without rep, or have a script that can post without rep or grant rep to people

Currently we need to comment out the part that posts with rep and uncomment the part that posts without rep to be able to test the relayer.

Go tokens don't work at all currently, but that's because the circuits don't work right now. Tsukino will fix this now that he received the fixed ones.

#### Vojtech

Questions to Tsukino:
- Does the chat now work, and do I need to join a persona?
    - Yes and yes

#### Philippe

Questions to Tsukino:
- What are the `noop` logs in the `relayer`?
    - Can be removed, not an error though
- Why are the circuits not loaded correctly?
    - Could be a fastify assets issue
    - Could be a CORS issue?
- Can we fix some CORS issues?
    - Yes, we can send a list to Tsukino to fix some specific issues

### Agenda

#### Should we cancel following meetings?

We should sync again after we were able to test everything out. Dailies on next Monday and Tuesday are cancelled.

## Meeting Report 06.04 core dev meeting

Cancelled, Tsukino wasn't present.

## Meeting report team meeting 06.04

**Vojtech** 
Big PR merge on tuesday, still a lot of issues
I would consider doing everything again ourselves, because we then control everything, no we have to rely on zkitter-js and it may brake our app if they change things
But also ok with looking at Kurate as the reference implementation and a playing field for someone else to come in.

**Philippe**
Really complicated to debug,  all of the typescript errors
We will meet with Tsukino today and discuss a plan of action
Not a fan of doing it again ourselves, but yes a fan of someone else doing that and we (Philippe and Vojtech) supervise

**Barbara**
Are we done or do we need to proceed working on Kurate? It feels like we delivered on the promise. 

**Michelle**
We reached the goal, but we all feel like Kurate deserves follow-up, so we will discuss with Logos on how to proceed. We can be supervisors.

**David**
I'd love to push Kurate forward, there is such a big potential. So would love to help to supervise.
Want to improve some UI on Kurate, some low hanging fruit.

**Matt**
all ok

## Meeting Report 04.04 core dev meeting

### Updates

#### Tsukino

Got the [#357](https://github.com/logos-innovation-lab/Kurate/pull/357) PR ready, which was now merged.

#### Vojtech

Making sure the UI and everything works for tomorrow. Run the epoch cycle but preserving demoted posts. Reviewed and tested zkitter branch

TODO:
- [x] fix starting chat
- [x] make sure everything still works after merging zkitter branch

#### Philippe

Deployed the `relayer` on https://relayer.kurate.apyos.dev/. Opened a PR [#381](https://github.com/logos-innovation-lab/Kurate/pull/381) for a Dockerfile on the `relayer` to make deployments easier, and fixed a few details Kurate.

Fixed all design related things on the FAQ page and is now working on the search.

### Agenda

#### Cancelling tomorow's meeting (and subsequent ones?)

Was not discussed because Tsukino wasn't present.

## Meeting Report 04.04 Team meeting

**Philippe**
Need to get the PR from Tsukino in, first need to be reviewed.
Relayer ready, will be a good step towards testing an all-in version of the app
finishing touches on FAQ, probably ready tomorrow

**David**
worked on the presentation, review and improve
Worked more on the persona in the app, new posts
Collecting feedback, small details to improve in the app
request to Barbara: Can we review the website page?

**Barbara**
Mostly working on small fixes, issues
updated faq and website

**Matt**
Linking the help tips in the app to the FAQ
Link the website to the FAQ
Posting in the app
working on the pending posts

**Michelle**
Happy and impressed
talked to Tsukino yesterday

## Meeting Report 03.04 core dev meeting

### Updates

#### Tsukino

Tried to generate proofs and verifying them, but the proofs seem to be considered invalid. Tested from the `relayer` and directly from the `ui`, none of them worked. Made sure that the circuits are the same. 

To fix this, we can look a bit into how `rlnjs` works, they might have tree depths hardcoded in the contracts, but we have to look into that.

Another idea might be to use `zk-kit`, but we think that it's not worth it anymore at this point, and we feel like finding / report a bug in `rlnjs` would be more valuable at this point.

#### Vojtech

Fixed a lot of UI bugs and worked on finishing touches for the demo.

#### Philippe

Tried to figure out testing on the `relayer`, but mocking was made quite painful because of bad design decisions at the beginning.

Will deploy the `relayer` so it can be used for the app. Todo:
- [ ] Use the private key (pinned in #kurate-dev)
- [ ] Run a CRON job every 8 hours (Tsukino will build this into the `relayer`)
