Open Office - 20th April 2023

[djfnd]

10am EST / 3pm GMT

https://meet.google.com/uwf-pmat-xos

Agenda

Lens

• Update on progress
  • Generalise neume architecture to facilitate the indexing of Lens
  • Move neume to new database structure
  • Initial work into indexing based on an array of pre-determined wallets
• First tranche of grant money should be received < 5 days

Gitcoin

• Our application is in review, nothing else to do right now
• Once things open up we will need to put in a concerted public push around the project to raise awareness

ENS

• Thoughts on applying for the next round
  • Dan - I think that we should probably focus on a successful gitcoin beta round rather than spreading too thin, but open to other thoughts

Update from NFTNYC

Blogging / name recognition

• Anyone can push a blog @ https://github.com/neume-network/website - there is an explainer there, but let Dan know if you have any questions
• Would be fantastic to get some other pieces put through it!

Operations

• Do we need to be "more DAO"?

---

Please add any other topics to the comments below and I will update this.

[djfnd]

AI notes:

The Gist
Group discussed updates on Lens project, database schema, Merkel trees & set reconciliation algorithms, ENS funding, & increasing name recognition.

Summary
The group discussed the challenges of finding the invite link for their weekly event and suggested making it a clickable link for easier access.

The group discussed updates on the Lens project, including receiving the first grant money and discussing database challenges.

The team is working on implementing a database schema for maintaining the latest state of the data, as maintaining all previous states is time-consuming and complicated. They are also working on integrating the database with lens, and testing for bugs.

The team discovered that some songs on lens are encrypted and can only be accessed with a particular token. They also found that some songs on lens are reposts from the sound protocol, using the same token URI. This could potentially lead to duplications that need to be resolved in the database schema.

The idea of using set reconciliation algorithms to enable partial syncing and dependency-based crawling for specific subsets of data sets could be a useful tool for niche projects with specific needs. This could allow for the creation of lightweight nodes that only get the data they need and produce novel data that can be shared with other nodes.

The preservation of history could be important in the future, and one way to approach this would be to have SQL for the internal state used to serve queries and produce new data sets, and a lower-level key-value store that handles networking behavior and storage of beefs and work boots, miracle trees. This could provide a sense of permanence and immutability for the data sets.

The importance of providing users with the ability to use only the parts of a system that they want and need, especially in the context of specific communities.

The potential for using Merkel trees and set reconciliation algorithms in peer-to-peer networking to efficiently compare and communicate subsets of data, but the need for further development in how nodes working on different subsets can cooperate and communicate effectively.

The team discussed the status of the Gitcoin application and that when it goes live we will all need to support promoting neume across socials etc.

The team discussed the possibility of applying for funding from the Ethereum Name Service (ENS) and the importance of demonstrating how the project can benefit the entire system overall. They also discussed the need to focus on the project's core goals and not spread themselves too thin by pursuing too many opportunities at once.

The team also discussed the importance of increasing name recognition for the project and exploring ways to engage with different communities and events. They discussed the possibility of sponsoring hackathons and using social media more effectively to raise awareness of the project.

[neatonk]

a lower-level key-value store that handles networking behavior and storage of beefs and work boots, miracle trees.

Ooof

[djfnd]

That's kinda poetic hahaha

[estmcmxci]

Neume Sync (04.20.23)

Tl;dr

The group discuss funding, technical development, governance, and promotion for Neume. They will receive the first tranche of $5,000 and plan to make the application public. They discuss data management, technical development, and the possibility of spinning up a multi-sig. They also discuss governance and the process of applying for public goods and growth rounds. The speaker encourages others to raise the profile of Neume through writing for the blog, sponsoring hackathons, and attending events. There is also talk of creating a website to demonstrate project functionality.

--

Participants:

• Dan
• Pierre
• Vaibhav
• Marcus
• Kevin
• Kevin

Overview:

Funding and Finance:

• The first tranche of $5,000 will be received in the next couple of days.
• The funds will be forwarded to Vaibhav, Kevin, and the recipient separately based on their wallet addresses.
• The agreed split is four and one between Vaibhav, Kevin, and the recipient.
• The recipient needs to confirm if they are okay with the split before moving forward.
• Kevin is interested in the idea of public assembly and wants to act as a curator.
• The curation token for public assembly would point to the other token itself.
• The market-based approach will be discussed further with Kevin.
• They discuss the possibility of spinning up a multi-sig when the Gitcoin money comes in.
• They plan to make the application public and start raising its visibility.
• Gitcoin is transitioning to a more decentralized way of doing funding rounds.
• The speaker has been talking to them about a music-specific grant.
• They hope to find out in the next couple of days if they've been successful.

Governance and Organizational Structure:

• The speaker is hesitant to introduce more bureaucracy in governance.
• They will reach consensus through GitHub discussions for now, but as they grow, they may require a more formal governance structure.
• They discuss the process of applying for public goods and growth rounds.
• It's worth getting on one of the public goods calls to present the project and get feedback from the stewards.
• The first step would be to win a small grant rather than going through the growth rounds.
• For the ENS route, an application demonstrating what can be done with ENS data would make more sense.

Publicity and Promotion:

• The speaker encourages others to write for the blog, sponsor hackathons, and attend events to raise the profile of Neume.
• Slobo.eth suggested creating a website to demonstrate project functionality through a prototype.
• Explorer on the website: mNFT explorer front-end; can search by .eth, include a way to register ens domains from the mNFT explorer and perhaps launch a vault from the .eth

--

tags: Neume