Application for Momentum, an open source, metaverse for digital societies. #1221
Conversation
|
|
|
I have agreed to the CLA for w3f/Grants-Program. Status is not updated immediately? |
ghost
closed this
|
Was closed due to signing issues (person that squashed the commits locally also had to sign) |
ghost
reopened this
There was a problem hiding this comment.
Thank you for the application, @dave4odyssey. I left some questions below, but mostly I am struggling with the staking pallet. I can stake my user profile, world or subspace to produce blocks and possibly get rewarded? And if I don't submit a block, my NFTs might get "slashed"? How are the NFTs priced in that case? Will I be able to stake NFTs and the native token in parallel?
Other than that, please review the deliverables tables. The name ("Deliverable") should be something concrete, such as a pallet, a document or file. "Use cases" and "Delivery" are ambiguous here. The specification should be as precise as possible to avoid misunderstandinds. For example, what does "complex configurations" refer to? Instead of writing "principles applied", please be more specific about what the deliverable accomplishes or -- if the deliverable is too abstract to be more precise -- remove it altogether. It would be difficult for you to prove (and for us to verify) that you did indeed "apply generic principles for re-use", unless you can point to a list of principles applied and corresponding commits.
|
|
||
| Odyssey is building Momentum, an open source, metaverse for digital societies. | ||
|
|
||
| The Momentum stack enables people to jointly build their own 3D worlds as well as develop and integrate plugins to unlock a wide range of decentralized 3D social action medium use cases. |
There was a problem hiding this comment.
We are basically a metaverse for co-creation and collaboration. A metaverse for activities rather than for content. People would come here for AMA’s, working together on complex issues, creating art together etc.
As an example we can compare the virtual concert of Travis Scott in Fortnite with Momentum. Although the Travis Scott concert is EPIC in terms of size, it was a stream comparable to having many people watching the same video on YouTube. What we, in contrast to the Travis Scott example envision as a 3D social action medium, is a place where you can co-create making music together, playing in a band together in real-time and having presence in a 3D world while at the same time being miles apart. Hence a 3D social action medium.
There was a problem hiding this comment.
P.S. The deliverables will be adjusted end of day. I understand the issue. We will rephrase the deliverables, so they are independently verifiable.
There was a problem hiding this comment.
Deliverables adjusted to make them verifiable.
|
|
||
| The Momentum network enables these different worlds, activities and people to come together, without the need for a middleman or land sales. For this purpose, we built the DRIVE parachain, which has three main functions: | ||
| - On-chain ownership and coordination through NFTs of nodes, 3D worlds, sub-spaces and personal profiles. | ||
| - On-chain connections between people, worlds and spaces and social capital allocation through staking in worlds, sub-spaces and people. |
There was a problem hiding this comment.
Can you explain or give an example for "social capital allocation through staking"?
There was a problem hiding this comment.
The DRIVE token we are creating can be staked in entities such as persons you want to back or projects you find interesting, communities you want to be part of or support. By staking in an entity both the user staking their DRIVE and the entity you stake in will get rewards.
There was a problem hiding this comment.
Where do these rewards come from? How are they allocated?
|
|
||
| Momentum sees the metaverse as a novel communications medium and provides the infrastructure for a new user experience, where social, economic and cultural activities, both on-chain and off-chain are intertwined and strengthen each other. With **Kusama (and optionally Polkadot) as its primary digital public infrastructure**, Momentum is co-created, governed and owned by its users. | ||
|
|
||
| DRIVE provides the users in the network with a universal way to turn their connections and activities into social capital and earnings. The goal is to enable users of these digital societies to thrive, by prioritizing resource allocation (e.g. funding, talent, knowledge) in general, optimizing network effects (e.g. connectivity, serendipity, virality), and a better user experience (e.g. search results, timelines and suggestions) based on the user's skin in the game. |
There was a problem hiding this comment.
I don't understand this paragraph. How do I turn my connections into earnings with DRIVE? Or social capital? What activities? How does DRIVE "prioritize resource allocation" and "optimize network effects"?
There was a problem hiding this comment.
In order to explain, I have split your question into 4 separate parts. Before answering these I’ll first provide some context first:
Context
In Momentum, people are able to create- and own worlds, spaces and subspaces with the goal to bring people with different backgrounds, experiences and craft together within the realm of these worlds, spaces and subspaces to work on a common goal.
A world (identified by an NFT) can have a World owner which can be a single individual but also can be a group of people based on the properties of the NFT. In this last case, a World can be created adhering to Council & Treasury based mechanisms, where the world’s council decides on important decisions and the revenue accrued in the treasury is not held nor decided on by one single person. This enables centralized and decentralized models to coexist.
Worlds can have different goals or have common goals, work together or be competitors. Odyssey does not prescribe any behavior in this sense. Momentum is for the community, by the community.
Part 1 - How do I turn my connections into earnings with DRIVE? Or social capital? -
Within Momentum there are different actors. I describe earning DRIVE based on a few of them.
As a world owner, bringing people’s attention to your world because people are interested in the goals pursued, could interest people to stake DRIVE in your world or (sub)spaces. Hence, providing you as an owner of worlds or (sub)spaces with a certain DRIVE revenue stream (When people stake into entities both the one staking their DRIVE and the entity being staked in will earn rewards).
Also, although drawing users into your world can be completely free, it also could involve optional access fees. As long as a world provides enough value, it can require some sort of ticket-based access e.g., making time-bound staking mandatory for participation or have participants pay an access fee.
One of the important elements that enable value creation within a world or (sub)space are plugins. Plugins are created to unlock a wide range of capabilities, providing utility by enabling and supporting actions. Plugins are created by developers and in return developers can receive DRIVE using one of the earning models e.g., fee/action based, or subscription based. World owners can activate any of the available plugins they believe are of value for the community within their world and (sub) spaces. If the use of a plug-in is required to store data on-chain (velocity), there will be a transaction fee involved which will partly fill the world’s treasury.
As a world owner you have multiple DRIVE related revenue streams that enable you to host and build and maintain your worlds and (sub)spaces, grow the functionality by adding plugins to better support the goals of the world, spaces and subspaces. With this, the value created through the combination of the people brought together within a world, space or subspace grows by providing them novel ways to co-create and meet the designated goal(s) of the world. Hence, earn DRIVE and build social capital.
As a developer you have a DRIVE related revenue stream because people have to pay when using your plugin e.g., fee/action based, or subscription based. As a developer you also grow your social capital by developing plugins that help the worlds, their cause and the community within it to better/faster/smarter achieve their goals. Hence, earn DRIVE and build social capital.
As a user you have a DRIVE related revenue stream because you can stake in people, worlds and (sub)spaces. By staking into entities both the one staking their DRIVE and the entity being staked in will earn rewards. In this way you will be contributing financially to the cause you care about most. In addition, a user can participate in a world and (sub) space to co-create in a novel way through a combination of people organized together, having different backgrounds and experiences but the same goal. Hence, earn DRIVE and build social capital.
Part 2 - What activities? -
The activities can be virtually anything as long as it involves co-creation. From actions taking place in hackethons like the SNI Kenya Wildlife Trust Hackathon, Town-Hall like applications like the Kusamaverse up to making music online in real time, together.
One other example is part of our upcoming showcases in cooperation with the Groninger Museum. In this showcase the story of the Van Gogh painting “The Parsonage Garden at Nuenen”, and its theft (20 March 2020) are the starting point for bringing people together in Momentum and crafting new stories and imagery together.
So, what are activities? Odyssey does not prescribe what it should be. It is up to the creativity of the world owners, its community and the developers to decide what their world and the associated goals need and create it accordingly.
Part 3 - How does DRIVE "prioritize resource allocation" -
Popular subjects/worlds have more adoption and more funding hence automatically have a bigger chance of attracting the right talent and knowledge to pursue their goals. Also, anyone that wants to invest can identify what the already invested social capital is and can be very specific in their investment choices.
Part 4 - How does DRIVE "optimize network effects" -
Trends in allocation of social capital have attraction. What gets support can go viral.
Trends can be visualized within momentum for instance by earning a more prominent place within Momentum (measurable by staking statistics and on-chain activity), driving even more engagement. Also, people will leverage new ways of creating connections and connection-structures. For instance, through connections based on 3D objects/ NFTs introducing totemism-like networks that go beyond the traditional interpersonal/ company connections. Last but not least developers are able to create plugins to further experiment and optimize network effects.
Please let me know if this helps. I'll be more than happy to elaborate in a 1:1.
There was a problem hiding this comment.
Thanks for the application. Just to add: I would also like to point out that your first milestone looks like it’s less “general” research, but rather specifically focuses on your own project, which will have its own token (DRIVE). We usually don’t fund this kind of research (which is similar to an initial whitepaper). Could you comment on this or focus on something more general?
Added md closing tags for bold text Co-authored-by: Sebastian Müller <sebastian@web3.foundation>
|
Let me know if I should take another look at the application. |
|
Hi David,
Thank you for the quick response. I love the questions you and Sebastiaan
provided. It gave us some additional insights on how to better explain this
novel concept.
There are some people absent due to the school holidays this week, but you
will have my response Monday afternoon when everybody is back.
I'll let you know when it's ready.
Thanks,
Dave
…On Thu, Oct 20, 2022 at 2:31 PM David Hawig ***@***.***> wrote:
Let me know if I should take another look at the application.
—
Reply to this email directly, view it on GitHub
<#1221 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3SC3GLB6WOPXV3N2GARIE3WEE3RJANCNFSM6AAAAAARH23FJU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hi David, In response to your question. The first goal of the NFT research is to find a ready NFT pallet that could meet all of our requirements and provide the infrastructure to properly make use of the NFT (mint, share etc). If not available, then research if any pallet available comes close to our requirements and investigate how it needs to be adapted to meet the requirements. Lastly, we have to research how to make such a pallet from scratch. The second goal brings us more towards the staking pallet, to make a pallet where we could stake on those "native" NFTs, but not to provide PoS or something, but just to "support" the NFT owner and let the staker get some rewards of some token in return. The third goal is to find a way to fractionalize the NFT in such a way where multiple people can earn shares of that NFT while at the same time, the staking pallet needs to take that into consideration in order to give the proper rewards. In addition to that we have a more sophisticated setup where worlds and (sub)spaces can configure the amount of commission they take from the staking mechanism. Hence, the staking rewards are divided using some formula using configurable parameters per world or (sub)space, that sets the ratio between the staker, the entity that has been staked in, and the world/ (sub)space and Treasury. So, What we deliver upon is a generalized way to stake in (fractionalized) NFTs, where both the NFT owner(s) as well as the one that stakes, earn some amount of some token. We believe this is an interesting and new way to look at staking that is different from the well known PoS mechanism and goes beyond a mere signaling of interest. Providing a generalized staking mechanism like this can create new ecosystems. Mentioning Momentum is just a matter of having a first example of a network that would like to implement such a mechanism, provide examples of ways it can be leveraged and is able to maintain it over time. I hope this helps to better understand. If required, I will be more than happy to change the document accordingly. Also, if you would like a 1:1 to go deep, no problem. I'll be more than happy to. Kind regards, Dave |
Edited the milestones to make them verifiable for W3F
If you can, please. Kind regards, Dave |
ghost
requested a review
from
There was a problem hiding this comment.
Thanks for the update and sorry for the late reply. We are currently on a company retreat. I will mark your application as ready for review. However, I personally think that given that this isn’t a “common good project” and you plan to have your token, the initial research should be done by you before you apply for the grant. Also, especially the second milestone looks rather expensive to me at the moment. Given that the result might be a single pallet. But this is just my opinion and I will ask the rest of the team to take a look at it.
Noc2
added
ready for review
Hi David, Thank you for the feedback. In response to your comments: This application does not describe all research that is done to build a token, since it is not part of this application. If you need information on what is happening outside of this application, I will be happy to elaborate. Looking forward to the feedback of the other team members! Kind Regards, |
|
Thanks for the updates and the thorough explanations. Could you describe how plugins are implemented and how they interact with your metaverse? And how do users interact with a plugin? Do they have to submit transactions for the plugin author to earn rewards? Also, given the price I would like to see some way to test each pallet (and their interplay) without having to enter a metaverse. Either a very thorough testing guide or a UI for changing parameters and seeing their effect. Maybe that's something you already have or have planned? |
|
Hi Semuelle, Plugin implementation can be initiated and managed using a standardized plugin-onboarding process. Typically, plugin functionality is related to an (3D-) object and can be applied to the object if it fits the requirements. As an example: a plugin-developer creates a plugin that enables state change from ON to OFF and vice versa and emits the event to some IFTTT provider. This plugin can be attached to an object that enables ‘touching’. The developer uploads the plugin code (and optionally some special object) to the Momentum repository together with a configuration file describing the plugin, the object requirements and preset (like subscription type, costs involved, reward address), required- and optional parameters, after which a process is initiated to mint an NFT to uniquely identify the plugin and enable ownership. A world node* (owner) can then select the plugin from the central repository and make it available for the worlds it hosts. A world owner can then select the plugin and apply it to the object that meets the requirements, for instance a clickable mushroom and apply parameters e.g. IFTTT API-key. Any user visiting the world can click the mushroom, optionally get its wallet invoked to pay a fee and see some magic happening as defined by the plugin. The example describes IFTTT as an example of what can happen, but there are no limitations, and it can be off-chain and/or on-chain activities expressed in any form. To get back your question “Do they have to submit transactions for the plugin author to earn rewards”. In regard to the testing: The plans are to use the Rust Unit Test Framework, as mentioned here together with integration tests using Rust and Zombienet (Js and DSL). Of course, we are open to any other testing method/framework/doc that might be suggested or if we may find it during research/development. Hope this information helps you. We understand it is a lot to comprehend in so little time. Please feel free to ask anything. Kind regards, Dave |
There was a problem hiding this comment.
@dave4odyssey thanks for the submission of your grant application. I have a few questions:
- What files are stored on the "Media manager" and "IPFS client" on the momentum node?
- What's the exact role of:
- the Backend controller? Is it limited to interacting with the plugin pallet (which I assume the "Plugin infrastructure" would do) or is there more to it?
- the Token monitor?
- the Harvester?
- Can you explain which features you need that the Uniques pallet is currently lacking? For example, if you need fractional NFTs my guess would be, you'd need some kind of ERC-1155-type semi-fungible tokens maybe?
Besides that, it is most likely that we would need to write a custom NFT pallet or a pallet that complements the Uniques pallet.
- Where would the tokens that are used for rewarding NFT staking come from?
Some additional thoughts:
- Something to be aware of, the Uniques 2022 pallet is currently in development and might support some of the features that you're lacking: Uniques V2 Roadmap 2022 (Tracking Issue) paritytech/substrate#11783
- Personally, I'm not willing to support M1 of this grant since it seems to be very specific to your own project. The type of research we'd usually be interested to fund is something that's of use to the whole community.
- Without having fully understood the scope of your stake pallet at this point, I have a gut feeling that M2 and M3 are rather pricy.
|
Hi Seraya, Thanks for your questions and tips, please find our answer below.
The content currently stored on the Media Manager is User uploaded content (UGCs), Captures for the 3D engine etc. The Media Manager is pending change to a full Web3 solution, hence the IPFS Client. The term Media Manager might stay, the way it stores data will be changed from centralized to decentralized.
The Backend Controller takes care of all communication between the Front-End (React Layer) and the Backend (Unity). Every action of each individual user/object in the Front-End makes a call to the Backend Controller, which takes care of processing/forwarding. So, the Backend Controller is not only communicating with the plugin pallet, it is communicating with basically everything. The Token Monitor is used for token gated access. It monitors changes in token ownership and acts on this (e.g., token gated access). The Harvester monitors blockchains and translates this to what can be visualized. An example of this can be found in Kusamaverse where you can see the parachains and a dynamic visualization of the blocks created.
Like you mentioned, the required functionality is that of the fractionalized NFT like the ERC-1155-type but then in a ‘Native’ Dotsama type.
Yes, we are very well aware of the developments regarding Uniques V2 and monitoring the good work that is performed there. The spirit in which this application has been drafted is that we reuse any quality components that already exist and keep track of developments that interfere or strengthen our roadmap. When the development of the Uniques V2 provides a solution (or any other project for that matter) that fits the roadmap, and we have not yet done the work ourselves, we do not have to deliver on that part and as such we will not claim the pledged grant in full.
We understand your point of view regarding M1. Although important to us, it is of less value to the community. My proposal is to remove it from the application. It has also been overtaken by time. It has been four weeks since the initial application and we have been making great progress. M1 is well under way to being delivered. From an operational perspective, do you want me to adjust the application right away or first finish the review of your coworkers?
Please clarify what you would like to better understand regarding the scope. We will be happy to clarify. In regard to the costs: Kind regards Dave Hoogendoorn |
|
Thanks for the infos and sorry for the late reply. Looking at the other comments, I'd say it might make sense to remove M1 and M3, as both seems rather specific to your application. Other than that, happy to proceed. |
Thank you for your response. I have discussed the feedback with the team, and we understand W3F's point of view. We are happy to continue with M2 since it indeed provides the most value-add to the community. |
|
Thanks for addressing all the questions @dave4odyssey.
|
keeganquigley
added
changes requested
Removed template text in response to @keeganquigley
|
Hi @keeganquigley, Thank you for your feedback. 'In production' is more like a Show & Tell combining the steps and making sure anybody can reproduce on their own dev env. Regarding the licensing: Kind regards, |
|
Hi David, It's a typo. 'NU' should be ' GNU' off course. Fixed it. Thank you! |
keeganquigley
added
ready for review
There was a problem hiding this comment.
Thanks @dave4odyssey. I still feel that this is a pretty ambitious project for having only one milestone, but I think you gave sufficient answers to the committee, and given Odyssey/Momentum's track record (I've flown around a few times in the Kusamaverse), I am happy to go forward with it. Happy Holidays!
@dave4odyssey and @deniscavalli could you still sign the latest terms and conditions? |
|
Once you sign the latest terms and conditions, we can merge the application. |
|
Hi David, we just signed it. |
|
Congratulations and welcome to the Web3 Foundation Grants Program! Please refer to our Milestone Delivery repository for instructions on how to submit milestones and invoices, our FAQ for frequently asked questions and the support section of our README for more ways to find answers to your questions. |
|
Hi @dave4odyssey how is the project coming along? |
|
Hi @keeganquigley I'll schedule something for next week. Would be good to have a chat. |
|
Hi @dave4odyssey do you still want to schedule a call? I don't believe I have received an email from you. keegan@web3.foundation |
|
Hi Keegan,
I have sent an invite for the coming Tuesday. Hope that fits your schedule.
Cheers,
Dave
…On Thu, May 25, 2023 at 11:44 PM Keegan | W3F ***@***.***> wrote:
Hi @dave4odyssey <https://github.com/dave4odyssey> do you still want to
schedule a call? I don't believe I have received an email from you.
***@***.***
—
Reply to this email directly, view it on GitHub
<#1221 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3SC3GPTOFY7NSNT67NXFQDXH7HETANCNFSM6AAAAAARH23FJU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hi @deniscavalli are you able to provide an update on the progress of milestone 1? A delivery was scheduled for the end of 2023 :) |
|
pinging @dave4you @deniscavalli I see the main benefactor for this grant deleted his GH account. Are you still working on this grant? |
|
Hi Keegan,
The project itself has been postponed and the grant work has been stopped. There has been a meeting about this with Daniel in October I believe. My apologies if the correct procedure was not followed. Officially i cannot act on behalf of the company anymore but if anything needs to be done to stop the application process, I can pull some strings.
Let me know if you need any help on this.
Once again, my apologies for the inconvenience.
Cheers,
Dave
… Op 25-01-2024 18:24 CET schreef Keegan | W3F ***@***.***>:
pinging @dave4you https://github.com/dave4you @deniscavalli https://github.com/deniscavalli I see the main benefactor for this grant deleted his GH account. Are you still working on this grant?
—
Reply to this email directly, view it on GitHub #1221 (comment), or unsubscribe https://github.com/notifications/unsubscribe-auth/AFJGEWNUA6KVLJOYOJH7ZJ3YQKINTAVCNFSM6AAAAAARH23FJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJQGY3DINZYHE.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Thanks for the update @dave4you much appreciated. Sorry to hear it didn't work out! I should be able to take care of it on our end. |
Project Abstract
Odyssey is building Momentum, an open source, metaverse for digital societies.
The Momentum stack enables people to jointly build their own 3D worlds as well as develop and integrate plugins to unlock a wide range of decentralized 3D social action medium use cases.
Momentum sees the metaverse as a novel communications medium and provides the infrastructure for a new user experience, where social, economic and cultural activities, both on-chain and off-chain are intertwined and strengthen each other. With Kusama (and optionally Polkadot) as its primary digital public infrastructure, Momentum is co-created, governed and owned by its users.
Grant level
Application Checklist
project_name.md).@dave4you:matrix.org(change the homeserver if you use a different one)