Author : Fifoooo(11008), PG(4895) Quorum Requirement : 20% (7.2M) Vote Duration : 14 Days Discord thread: https://discord.com/channels/732491344970383370/1380191188211994675

Introduction

After successfully delivering all the features stated in AGIP135, this proposal aims at funding more useful features to be implemented in the official dapp. As in AGIP135, those features would be implemented by community members, PG and myself. We both proved with the previous run that we are qualified to work on the aavegotchi smart contract and dapp along with the PC team members. We did our best to respect their guidelines and workflows in order to deliver code that matches their standards. The result has been a fluid and productive collaboration.

With that in mind, our ecosystem has moved a bit and some new features could be added to the official dapp. As always my goal is to make our ecosystem as fluid and easy to use as possible, especially for new comers.

I actually see 3 features that could be added and this prop aims at presenting them and request funding.

Wearable Lendings UI

With Orium closing shop we now need another UI to access wearable lending features. Smart contract implementation and subgraph are still there, all we need is a new UI. So I really think we need to make that feature available again and as it is a part of the protocol, I’m convinced it should be implemented in the official dapp this time. This feature has a lot of potential coupled with the gotchi configs and upcoming Battler plans, only thing that we need is a good UI for people to use it. Also PG and I decided to add batch functions to the smart contract so you can list multiple items in one tx, and also claim all ended lendings in one tx. The actual one by one way of listing and reclaiming wearables is just too big of a barrier to adoption.

The feature contains:

• Adding batch functions to the smart contract so you can list multiple items in one tx, and also claim all ended lendings in one tx
• A UI to display all the wearables you listed, their state and the wearables you could list as designed in figma .
• A UI to display all wearables currently available for borrowing with all filters needed

The overall cost is 10K$, it includes the implementation, a small contingency(10%) and a bugfix budget.

Gotchis Batch lending

As some of you are aware I’m the one behind verse-analytics.xyz dapp. I developed it around 3 years ago, at a time harvesting and channeling alchemica was seen as the foundation of the gotchiverse ecosystem to come. So it is centered around alchemica, which is going to disappear at some point. The number of unique visitors on verse-analytics has decreased substantially from its ATH (from 1.2K unique visitors per month to around 80 last months). I have no plans to shut it down soon and AGIP 129 has passed 9 months ago to fund me and other buildoors to maintain our dapps, so i plan to do just that for the duration of the AGIP and even after that if needed. But I think it’s time the batch lending features get implemented inside the official dapp for the following reasons:

• It’s not something I invented, it’s been part of the protocol for years with functions in the aavegotchi contract dedicated to it.
• It’s so cumbersome and complicated for gotchi owners to manage multiple lendings without it that they basically stop lending.
• if we want to attract and onboard new players to our ecosystem, having a large base of gotchis available for borrowing may be pivotal to success.

The feature contains:

• All batch lending features (batch listing, batch cancel, batch claim, batch claim + end, batch claim + end + relist)
• UI as designed in figma
• A complete dashboard regarding lendings (gotchis and wearables) as designed in figma

The overall cost is 8K$, it includes the implementation, a small contingency(10%) and a bugfix budget.

BRS optimizer.

This feature has been on my mind for quite some times. It’s kinda related to the gotchi configs, but not entirely and it fits another purpose. Last time I played Battler and I severely messed up my gotchi configurations (I wanted a LOT of mages) and I did not kept screenshots or whatever backup of my setup. Plus i sold and bought some wearables so backup would have been useless anyway. And even if I just have 10 gotchis, it took me a while to put back a BRS optimized config altogether. I found the exercise not fun at all and it’s clear that if you have more than 15 gotchis and a lot of wearables i can’t imagine how painful it can be… That’s how the idea to build a global BRS optimizer / solver was born.

BRS solver should be able to find the best combination in term of overall BRS for your whole asset collection (all your gotchis, all the wearables you own or borrow). You would just need one click to display optimal configuration for all your gotchis at once. And thanks to the BatchEquip functions @PG added in the aavegotchi contracts while developping Gotchi configs features, you would just need a 2nd click to apply the new configuration to all your gotchis. I scratched my head thinking about this feature for quite some time so i know perfectly well such feature is no easy task but that’s the kind of coding challenge I love and i’m sure:

• It’s more complex to code than a basic UI, but it’s technically doable
• A lot of people want it
• It will be a great addition to the official dapp

The feature contains:

• An algorithm able to optimize any wallets and suggest most optimized config BRS-wise
• A ui to use that algo, as suggested in the figma.

The overall cost is 11K$, it includes the implementation, a small contingency(10%) and a bugfix budget.

Total funding and schedule.

The total funding requested is 29K$, payable in USDC or DAI. The experience we gained working on AGIP 135 has allowed us to reduce significantly the cost of those features. I expect to deliver those 3 features in less than 4 months (optimistic schedule with no back and forth, no issues, no feedbacks from PC team, working full-time on that project makes it less than 3 months).

The features would be developped in that order:

• Gotchis Batch lending
• Wearable Lendings UI
• 2-clicks BRS optimizer.

Based on that assertion, if the proposal succeeds, I would like disbursement to be spread over a 4 month period using following schedule:

• A 6000$ upfront disbursement immediately after the proposal is accepted.
• Starting from that date, 3 disbursements of 6000$, one every 30 days.
• Then a last payment of 5000$ (would be 4 months after the proposal passed)

Conclusion

After acquiring experience working on the official dapp during AGIP 135. It’s now time to use that experience again. I keep thinking that even if the official dapp and the contracts should remain under PixelCraft governance, the community should be able to contribute to the dapp and the contracts when they see fit. As this is a sigprop, discussions are still open in the DAO thread. All comments and suggestions are still welcome.