neume
Open Office - 27th April 2023 #23
Replies: 3 comments 1 reply
-
|
Some big changes are coming to Lens. Might be worth discussing this as well... |
Beta Was this translation helpful? Give feedback.
-
|
Ah yeah I saw this yesterday, will add to the agenda |
Beta Was this translation helpful? Give feedback.
-
AI notesAction Items
SummaryThe team is discussing the Bonsai Momoka platform and its potential relevance to their music NFT project. They note that while it currently only supports non-collectible posts, it may become more relevant in the future as social capabilities are added. Kevin provided an update. The workstream is focused on developing a way for nodes to operate on subsets of data, allowing for more efficient and targeted data retrieval. This is being done through the use of modified Merkle Patricia tries, which allow for deterministic structures and prefix-based subsets. The initial implementation will involve determining prefixes for filtering data based on wallet addresses, and prioritizing which sources to focus on for data retrieval. The goal is to create lighter weight nodes that can operate on subsets of data, rather than creating another archive node. The Riff team is working on a new feature for Lens that will allow users to follow their favorite artists' wallet addresses on the blockchain and receive updates on their activities. This is aimed at providing a more unified interface for music across different marketplaces and chains. The Riff team aims to address the problem of music discovery in the current market, which has become increasingly difficult due to the sheer volume of content and creators. The project seeks to leverage the social context of the Lens platform to make it easier for users to discover new music and follow their favorite artists across different platforms. The Riff team also aims to explore the potential of user-generated content in the music NFT space, which has so far been quite rigid and focused on floor prices and artist success. The team sees blockchain technology as offering new possibilities for creating shared experiences based on music and driving value back to the original creators through on-chain splits and other mechanisms. The Riff team is focused on expanding the music NFT space and experimenting with new experiences using music as a building block. They are also exploring the use of middleware solutions to ingest data into their application, and are open to collaboration with other teams to find a solution. The neume team is discussing the best approach for maintaining historical state in a database, which would allow different nodes to sync and consumers to consume data. They are considering a solution that involves maintaining only the latest state in SQL and having a log file that can generate the state up to any block number. The team is prioritizing operationalizing this feature and iterating on it, with the possibility of updating the code later if needed. The neume team is actively seeking funding through the Gitcoin platform and is encouraging members to signal boost and contribute to the funding pool. They are also considering setting up a multisig wallet in the future to simplify transactions and grant management. Although highlighted that this is likely not an issue yet. |
Beta Was this translation helpful? Give feedback.
-
Neume Office Hours (Notes 04.27.23)Tl;drNeume discusses the relevance of a system called Bonzai/Momoka to the music industry and social interaction. Currently, Momoka only caters to non-collectible posts, but the team plans to introduce social capabilities in the future. Some members of the group see potential in Momoka's curation aspect for music-related content. Neume continues discussing how to get a grant to a member without being taxed heavily, and they talk about using partial set reconciliation to enable nodes to cooperate without coordination. They also discuss the idea of partitioning a database to support various use cases. Neume adds that the implementation of a system that retrieves data related to specific wallet addresses, which they plan to do by using prefixes in the state tree. The goal is to provide a more unified interface for music-related content and to allow creators to reach their audience consistently across different marketplaces and chains. They also mention the use of specifications as a schema to identify the data they need. The Riff team introduce themselves and explain how they are exploring how to integrate Lens and the on-chain music graph to make music more accessible and open up the music NFT space. They want to create a platform for users to create content on top of music and drive value back to the original creators. Pierre suggests collaboration with Lens and offers to provide direction if needed. The team's work on switching to SQL could make Neume more user-friendly for applications, and Dan reports on the progress of Gitcoin and announces contributions from 16 contributors. --
-- DiscussionDuring a discussion about Bonzai / Momoka, a group of individuals consider its relevance to the music industry and social interaction. Bonzai is a system that replicates transactions and shares them to L3 for verification when read. At present, it only caters to non-collectible posts. Although users can create posts and save them on L3, they are not collectible or divisible. The next step for Bonzai is to introduce social capabilities such as commenting, liking, and mirroring, which will then move to their weave. One member of the group feels that Bonzai is not relevant to music as it only covers non-collectible posts. However, another member believes it could be significant for neume due to its curation aspect. They suggest that even if someone creates a collectible post on Polygon, it can still be interacted with. One member of the group has yet to investigate Bonzai's capabilities. The post contains motivational background information in the top half, while the actual technical details are located in the bottom half. Context: https://twitter.com/LensProtocol/status/1651270830729592832?s=20 -- Dan suggests that they begin with the usual Open Office agenda, which he has put in the chat. Since Vaibhav is late, they decide to skip the infrastructure and database topic and start with the Lens money Grant, which they received last week. They talk about how they can get the grant to Kevin without being taxed an insane amount, as crypto in India is not favorable. They explai that this workstream is a part of the Lens grant, which is motivated by the idea of following a set of wallets and some forward-looking needs from other projects. They also suggest the idea of partial set reconciliation, which would allow nodes to operate on a subset of data that they need. This would enable nodes to cooperate without coordination, which would be informed by the work that Tim has been doing with the set reconciliation algorithm. The modified Merkel that the theorem uses for its state is a great fit for this idea. They suggest that the key structure used to support all these use cases would be like partitioning a database, where you would come up with a key structure that supports all these use cases. It is essential to have some index type prefixes as well to support multiple partitioning of the data. -- The team is discussing the implementation of a system that retrieves data related to specific wallet addresses. They plan to describe data dependencies by using a prefix in the state tree. The initial implementation involves determining these prefixes and mapping parameters to a prefix in the state tree. The team needs to consider the scope of retrieving data from the node and prioritize sources based on specific needs. One proposal is to switch to a model where all transactions are pulled, and data can be filtered by wallet address. However, this requires lighter weight nodes that can operate on subsets of data to avoid creating another archive node. The team believes that this new system, called "New Blank," will serve the specific needs of its users better than archive nodes. -- They state that it is hard for creators to reach their audience consistently because of different marketplaces and chains. The idea is to serve a user all music from their favorite artists by following an array of wallet addresses that they want to stay in touch with and see what they're up to. The goal is to provide a more unified interface for all their music. The speaker acknowledges that they are not familiar with all the terminology and asks if specifications are like a preset that they can use to get a subset of data. Another speaker confirms that specifications are essentially a schema, a preset that they can use to identify the data they need. The speaker explains that the Merkel Patricia tree allows for the use of prefixes to provide a subset of data. This is not important at the consumer level, but it is significant at the networking level. They also mention that this is an extrapolation of what's already happened internally with the Level DB database for partitioning. -- Vaibhav provided updates on the work they have been doing. They mentioned that they are thinking about maintaining historical state in their database, which will allow different nodes to sync. They proposed a solution to maintain only the latest state in SQL and have a log file that can generate the state up to any block number. They are currently working on the same functionality for sync, which allows one node to sync with the other node and allows consumers of Neume to consume the data. Its assumed that they are only maintaining the latest data state, but they can update their code if something else comes up. They plan to create three PRs, the first for the schema, the second for the database, and the third for adding Lens strategy and updating the Sound Protocol strategy. Speaker 2 suggested creating new discussions around PRs when they get pushed in to have long-form discussions within the PR. They also introduced the project on Lens and its potential use cases. -- The Riff team express gratitude for being given the opportunity to explain what their project is about. The project was initially about exploring how lens could be integrated into the music industry and how it could address the issue of music discovery for creators. Lens was chosen because it provided social context that could help people discover new things. There was also a great interest and overlap with the music community. Talking with Dan and looking at Neume expanded the scope of what they wanted to do, which was to bring together the on-chain music graph and make it more accessible to people. There were two main goals: to make it easier to aggregate music based on the people that people follow on Lens and to explore the user-generated content layer on top of music. The speaker expressed excitement about the possibilities that blockchain technology could provide in terms of new design space and driving value back to the original creators. They also highlighted the current rigidity of the music NFT space and how their project aims to open up that space again to make it more accessible for most people. They want to create a platform that makes it easy for users to use music and start creating content on top of it, with an automatic way to drive value back to the original creator. -- The Riff team introduce themselves to Pierre and expresses their interest in learning about Neume. They ask if there is any part of it that could potentially be open source or if Pierre could offer any tips on how to implement something similar. Pierre responds that this is a great question and something they have on their to-do list. They suggest having a conversation with Lens and setting up a call with them to better understand how they can help and potentially find a solution where the code they have created so far can be utilized. Riff clarify that they cannot promise to open source anything at the moment but stresses the importance of having a conversation to explore potential collaboration. Pierre acknowledges that they understand the difficulties of starting a project and offers to provide direction if collaboration is not possible. They propose a meeting for the following week to discuss options and play it by Joe, their CEO. Riff team express their gratitude and agrees to set up the meeting via message. -- The host acknowledged the team's presence and states that the team's positive energy has contributed to the current development of Neume. He then opened up the floor for questions and thoughts about Neume, and encouraged the team to ask any questions they might have. A member Speaker responded by discussing how the team's work on switching to SQL could make Neume more user-friendly for applications. The host agreed, stating that the switch to Postgres dB could allow for direct querying of the database without the need for a full crawl. -- Dan reported on the progress of Gitcoin and announced that they had already received contributions from 16 contributors, which was fantastic. The speaker also mentioned that the amount of money raised had halved at some point, which they attributed to a bug on Gitcoin's side. However, the number of contributors is what matters most due to the quadratic function. The funding raised on Gitcoin will contribute to core operations and specific projects, such as the ENS explorer. The speaker urged others to help signal boost Gitcoin, which currently has 350k DAI, and there are 12 more days to go. They state that they had spoken to one of the funding leads at Gitcoin about setting up a music and media specific track. On the topic of Enzyme, Speaker 2 was content with where the project was at and suggested linking Enzyme to Neume to create a good grant. As for operations, the money raised on Gitcoin is currently going to Dan's wallet, and they mentioned the possibility of setting up a multi-sig in the future. A member shared their personal opinion that it did not make sense to switch to a multi-sig at this point, given the project's current size and Dan's role. They suggested creating a second wallet to separate the streams of transactions, which Dan agreed with. --
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
10am EST / 3pm GMT
https://meet.google.com/uwf-pmat-xos
Agenda
Lens
Gitcoin
ENS
Dev
Ops
Beta Was this translation helpful? Give feedback.
All reactions