You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Xopowo's overall commitment remains the same as in #154. In short: Xopowo is focused on supporting existing Yearn projects while innovating and shipping new ones.
Highlights
The good
We built and launched a sexy front end for yETH.
veYFI UI was turned around in record time (translation: stressful) as an 'all hands to the wheel' endevour with the veYFI contributors.
A snazzy new v3 UI is in development.
Ape Tax is live in prod.
We have our own infrastrature for error reporting, hosting and so on
Migrated the provider to wagmi + rainbow kit
Yearn.fi is now omnichain, leading to an improved and more robust UX.
The bad
The team has been stretched thin on development resources this quater. We're aware and very much on it - using this as an opportunity to scale the team using the tried and true 'yearn method' (PoW) for testing new candidates. It's a bit slower, but it's totally worth it in the end.
The ugly
Related to the above, with the team being stretched and a busy period (yETH, veYFI, v3 and more) we have not been as strong on organization and communication as we would like to be. Improving in this area is a top priority for us now and we're focusing on building a better process for project management and communication with yTeams.
Moar projects
Some things we worked on this quater that were outside our initial scope:
yETH: from bootstrap to full launch
Current scope
Revenue generating
yearn.finance
OP staking (Over $1m of new TVL to Yearn)
yCRV
yBribe
veYFI
yAudit
V3
yETH
Infrastructure
Web lib | Web Template
yDaemon
Meta
APR
Strategic
B2B Dashboard
ape.tax
yearn.clinic
NFTreasury.click
Macarena.finance
The Plan
The Xopowo team remains committed to both maintaining and improving Yearn's current front ends while also looking to create products that bring new users to Yearn through innovative approaches and new functionality. Ensuring a great product experience for current users while seeking new ones. We therefore propose that the Xopowo team continues maintaining Yearn's website, in addition to creating new projects.
Additionally, the team is going to be searching for additional opportunities for product development, partnerships and integrations with other projects and protocols. This may involve grants or funding opportunities from external sources to Yearn - which will bring value back to Yearn through integrations and complementary functions that enhance the user experience.
In the future, the Xopowo Team may seek to reduce its dependence on grants from Yearn and move towards a revenue-sharing scheme. The team believes that this approach will help align its incentives with Yearn's interests while also promoting sustainable growth.
Deadline
2023-01-31
Money
We propose a dual approach to funding contributions toward the development and maintenance of our projects. Firstly, we plan to distribute a grant to each person working on a project.
Secondly, we will use bounties to fund isolated contributions or contributions linked to projects in maintenance mode. This approach will enable us to incentivize individual contributors, ensuring the continued success and growth of our projects.
Our breakdown:
Description
Token
Amount
Contributors
DAI
95000
Infra
DAI
2000
Amount
97,000 DAI per month
Wallet address
0x4F909396A75FE9d59F584156A851B3770f3F438a
Reporting
Monthly
The text was updated successfully, but these errors were encountered:
Xopowo's overall commitment remains the same as in #154. In short: Xopowo is focused on supporting existing Yearn projects while innovating and shipping new ones.
Highlights
The good
The bad
The team has been stretched thin on development resources this quater. We're aware and very much on it - using this as an opportunity to scale the team using the tried and true 'yearn method' (PoW) for testing new candidates. It's a bit slower, but it's totally worth it in the end.
The ugly
Related to the above, with the team being stretched and a busy period (yETH, veYFI, v3 and more) we have not been as strong on organization and communication as we would like to be. Improving in this area is a top priority for us now and we're focusing on building a better process for project management and communication with yTeams.
Moar projects
Some things we worked on this quater that were outside our initial scope:
Current scope
Revenue generating
Infrastructure
Strategic
The Plan
The Xopowo team remains committed to both maintaining and improving Yearn's current front ends while also looking to create products that bring new users to Yearn through innovative approaches and new functionality. Ensuring a great product experience for current users while seeking new ones. We therefore propose that the Xopowo team continues maintaining Yearn's website, in addition to creating new projects.
Additionally, the team is going to be searching for additional opportunities for product development, partnerships and integrations with other projects and protocols. This may involve grants or funding opportunities from external sources to Yearn - which will bring value back to Yearn through integrations and complementary functions that enhance the user experience.
In the future, the Xopowo Team may seek to reduce its dependence on grants from Yearn and move towards a revenue-sharing scheme. The team believes that this approach will help align its incentives with Yearn's interests while also promoting sustainable growth.
Deadline
2023-01-31
Money
We propose a dual approach to funding contributions toward the development and maintenance of our projects. Firstly, we plan to distribute a grant to each person working on a project.
Secondly, we will use bounties to fund isolated contributions or contributions linked to projects in maintenance mode. This approach will enable us to incentivize individual contributors, ensuring the continued success and growth of our projects.
Our breakdown:
Amount
Wallet address
0x4F909396A75FE9d59F584156A851B3770f3F438a
Reporting
Monthly
The text was updated successfully, but these errors were encountered: