08/30 Hi community! Today, we had a checkpoint meeting with Exodus to review the SDK7 migration as part of our grant completion, and we can confirm that it is done. In the meeting, Lean Mendoza from the SDK Team, Benjamin and JTV from Exodus, and Zino and Fifi from the GSS participated. Exodus still needs to open-source the Potion and Farming features to the community. We agreed that they will publish these on their GitHub, and we will fork them to the DAO's GitHub. A final checkpoint is scheduled for Tuesday, the 10th, to verify this. Update 09/15 Hi Community! Here you will find two features that the Exodus team promised to open source in their original proposal: Farming and Potion. Please take a look: https://github.com/JTV-Development/Exodus-SDK7-Demo. I also want to confirm that this grant is officially over, as they collected the final payment after delivering the SDK7 migration and the features. I want to remind everyone that the pet skin was not included in this grant, as agreed, but I hope the team continues improving the Exodus experience for the community.

Dear Community! HI a week ago we had a meeting, FIFI and Zino met with Benjamin and JTV from Exodus to tackle issues regarding the formal investigation request, SDK7 migration, and the open-sourcing of two features they agreed to do with the community. During the investigation, we highlighted the need for them to migrate to SDK7 (the last stable version of the SDK). This was something we hadn't addressed before, and bringing it up now causes a change in their yearly roadmap. However, they are doing a great job and are close to achieving their proposed metrics. So, we are dismissing the case so they can receive their last payment, but it is a priority to complete the migration. This is a big task and could cause users to lose some features -temporarily-. To avoid harming the team expecting this payment and the community, we agreed to remove one of their goals for this grant period, the pet skin, to allow the team to complete the migration faster. They could include this feature later. They will need more time than the current vesting contract, which ends on July 31st Therefore, according to the following proposal, we will request a new vesting contract, with a one-month duration, starting the 15 of August, ending with a hard date of September 15th. A review with Lean from the SDK7 team will be needed days before. The next steps are: 1. Request to the DAO Committee (@HPrivakos @Tobik @rizk ) revoke the actual vesting contract and create a new one with a one-month duration, starting the August 15th within the rest of the funds not claimed ($14,167.-) 2. SDK7 Team (@Leandro ) with the GSS will review will to ensure the migration is complete with the Exodus team and GSS will set a date to do it before September 15th 4. Check with Exodus if they need help from the SDK team with this migration and how they want to receive that support. Thanks

Today, we had our Monthly Meeting with @JTV and Jonathan from Exodus, and I'm pleased to report that the project is on track. They showed progress, and we checked their GovApp Update and their Public Roadmap. They provided well-detailed impact metrics for the Valentine's Day event, mentioning they can provide similar metrics for the entire month if needed. GSS requested they choose one consistent method to report metrics, whether by event or by month, and include those numbers in the next update. We also requested the financial report. Since this was their first payment, the funds weren't used for their necessary updates on the GovApp, and they still haven't made the payroll. They inquired about payment for developers who don't use crypto. For now, they can repeat the transaction link to the fiat conversion. Please send the financial report when available and include it in the next update. Additionally, we agreed on their participation in the town hall on the 25th of April, and they need to send evidence for DAO recognition. We suggested they include this recognition in the flyers as well, as most of the funds requested for this grant were for events. Please don't forget to upload evidence on Notion, define the metrics timeframe, prepare a video for the town hall, and send the financial report. We also discussed: [Please add any additional topics discussed here.]

Enhancing "Exodus: Goodbye World" ( Revision and Resubmission ) This proposal has been ENACTED by a DAO Committee Member (0xfb1afa4dc069ffb47b19dbee196045d508fcd5a2) Vesting Contract Addresses: 0xbac329bc39a7e925246ff3ee9306b5cfbb75215b

[quote="HPrivakos, post:20, topic:21518"] One of the requirement of this category is to opensource evrything related to the project. [/quote] Hey @ExodusGBW hope you are aware of this just notifying you before you start making progress and come to realize that the proposal will not enact unless you open- source it.

Enhancing "Exodus: Goodbye World" ( Revision and Resubmission ) This proposal is now in status: PASSED. Voting Results: * Yes 63% 6,329,728 VP (52 votes) * No 36% 3,618,790 VP (17 votes) * Abstain 1% 3,937 VP (2 votes)

[quote="ExodusGBW, post:9, topic:21518"] We would love to be able to contribute to the community in some open source manner. However, open sourcing core parts of our codebase could prove technically complex and could also detract from Exodus’s unique value as a product. [/quote] No need to vote then, this proposal is invalid. One of the requirement of this category is to opensource evrything related to the project.

Okay, that makes a bit more sense considering you are utitlizing a few more features of AWS than us but I'm still shocked at the gap in costs. It's easy to find a breakdown of your monthly costs in the AWS dashboard to share what an average month looks like for you.

Our server costs consist of a variety services purposed towards providing our team with the resources needed for success. To list what this budget covers: - Autoscaling container (ECS) for our game APIs (cost scales with traffic) - Multiple websocket servers for our game - Database Cluster + Database management tools - Elasticache usage for cached data - Additional Servers, DB, Cache for quality assurance (testing environments) - Server log retention tools - Data analytics tools - Polygon node subscription - Any needed DevOps / maintenance work While it may seem surprising that server costs for an operation like ours could be as high as $5000 over 6 months, providing all the tools necessary to run a large codebase, product, and team can be quite costly. We think that the $5000 budget will give us sufficient runway to provide this for our team.

@OGContraBand Sometimes even more 😯 @JTV Will we be provided with evidence of the server cost or not? Nobody else wants to know?

@Mimsy, sometimes there can be as many as 2 or even 3 people inside a decenraland estate all at the same time!

How are your server costs this high?  Can you provide receipts that validate this amount, because we also use AWS and our costs are a fraction of that for the entire year. I'm not a dev, and I don't understand how storage and everything works so maybe it's just that different, but if you could show some evidence that this is actually how much you're spending that would be helpful.

Sweet deal! Thank you for considering it. I'm happy to vote yes then.

Appreciate the perspective that the DAO should get something tangible. We're happy to provide some open-source demo code for the Farming and Potion Making features that we intend to make for this grant if the community thinks that's valuable. Hope that reinforces our commitment towards providing value to DCL by building our content.

i wonder if you will be as active in the DAO when your delegation is recycled to someone else :thinking:

This sounds like a really good approach to be honest ^ Moving into the future I will be more likely to vote yes on projects that are open-sourcing *aspects* of their project (NOT the entire project). If you're going to ask for funding from the DAO, it makes sense to contribute something back that others can use to grow this platform. Maybe not the whole kitchen, like Doc says, just a few recipes that other chefs can add their own ingredients to, to make it their own ;) (Hope the kitchen analogy makes sense) In my mind: Publicly funded by the DAO: Open-source some aspects back to the community Privately funded (Not by the DAO): Closed-source, keep it all to yourself I am open to more dialogue around this topic to further my own understanding :slight_smile:

An open-sourced element does not need to be an exact copy from your game. It could be a dumbed down, white-labeled version. For example, maybe you'll find that the crafting table or potion making skill can be turned into a very basic demo - similar to what was suggested for the Santa Hat burn. It could have the models replaced with basic placeholder blocks so that Exodus retains its individuality. Your point that it could be a bit of a technical challenge is a good one, but I think that the effort would earn the other half of the budget requested. I don't think it's too much to ask. Exodus would be funded and the community could have some good building blocks with SDK7 examples - and of course Exodus team would get credit for that. I want Exodus to receive the full funding requested, but it's difficult when I'm weighing my opinion of what the community gets out of it. This is afterall, an open-source platform's grant system that's funding it, and those costs are still high imo as mentioned previously. Thank you for hearing my take.

Hi, thanks so much for your compliments about our past features! We would love to be able to contribute to the community in some open source manner. However, open sourcing core parts of our codebase could prove technically complex and could also detract from Exodus's unique value as a product. Those cool features and mechanisms are part of what makes Exodus what it is! The Santa burn mechanism you mentioned involved a smart contract which we are happy to open source, potentially along with some code that exhibits how it worked in DCL. Would be happy to hear any other suggestions that you think would provide value to the community

I agree with this take.

**Can any features be open-sourced?** I'm a fan of Exodus. It's a complex game with some really cool mechanisms. I'll never forget the time the Exodus team casually flexed with the Santa Hat burn mechanism, run at the same time as their other events. Removal of all SDK 7 conversion costs is noted and appreciated. I think the costs for each new skill is still higher than they need to be. But if any of the skills or base mechanisms from them could be open-sourced, then I think the community would get a lot more out of this grant. What are your thoughts on this?

Its a total waste of funds to develop this. No for me.

There are no plans to add marijuana into Exodus.

Before I vote, can we be ensured that no weed crops will be grown here? We already have a weed farming game at 27,24

As I have stated on the previous proposals, Decentraland MUST INVEST in games/activities. The Exodus team has continued building through the bear market, while most packed their bags and left. I understand Exodus is not a genre of game for everyone. But the events they host bring in players from all areas of Decentraland. Exodus has tons of different skills/activities to enjoy, and will be a staple in DCL in the next Bull market. Yes, there are some activities in DCL to play, but Exodus is one of the few ACTUAL games being developed. Decentraland HAS to invest in game development before the next bull run. Concerts and Fashion shows may bring in players to check out DCL, but those players are not staying and playing everyday. Daily Active Users are a MUST! And the only way to do that is to invest in games that will keep people in Decentraland! I believe DCL needs to come together to pass this grant. We need game development to bring in Daily Active Users.

Like my last comment I will continue to support this proposal because of the very same reasons. I believe exodus is also doing a great job in doing events and also is always in the explorer this gives a good impression!