Open-Sourcing Gainify Staking Platform

Category: Defi
Ask: 50,000 Algo

Content Available Upon Proposal Passing

• Open-sourcing of the 2 core PUYA smart contracts behind the Gainify Staking platform, which has unique fee structuring

• Frontend and Backend codebase, as well as testing files

Value

• A working implementation of staking contracts to add to existing open-sourced content as well as frontend codebase and testing files

• Unique Fee structuring: A microfee occurs upon every action that is taken with any pool contract

Comments

• At one point there was a minor bug that is public knowledge that has been patched regarding AVM box storage limitations, a workaround was implemented
• The logic behind the staking pool logic is sound and working in its current state

Contracts

• Staking Pool Master / Factory

• Staking Pool Contract

Team

• Leo Costa

• Allan Diamante

• Ulrik Diamante

Previous Works

• rxelms.com

• algo-learn.com & Python on AVM Youtube Tutorial series

• algonfts.info

• leostxs.com

• AF Wallet Watcher

In my opinion this proposal is out of scope for the xGov program, i.e. unpaid work stemming from dispute between two third-party entities.

Evening @uhudo — just as a courtesy so I don’t leave you hanging on this thread and the other two — I know it has been some time since you asked for some additional info; I want to address your comments but would like to get the thoughts of @ulrik and @Allan before I respond since these proposals are team efforts. Hope you don’t mind, we should finally be able to sit down and discuss together tomorrow and respond. Thanks for your patience!

Thanks for the reply. There’s no rush. Proposal submissions are open continiously.

Good morning @uhudo — I can remove any context surrounding unpaid work and keep it strictly about open sourcing the Gainify contracts.

All references to retribution for unpaid work removed

Thanks for these modifications. Now the proposal seems more in line with T&Cs.

Would you mind providing some metrics on the usage these two smart contracts have seen?
Without these, it is difficult to judge if the claimed unique fee structure provided sufficient benefit w.r.t. the ask, especially if the work is not open-sourced in advance.

Regarding open-sourcing, could you clarify which parts are already open-sourced and where are they accessible?

Oh I’d have to find the old App ID’s and manually run analytics, I made need a day or two for that.

Edit: By existing open-sourced content I mean on Algorand generally, I know they’re using it for their agents / llms (eg; the one Gabe from DevRel created recently)

Edit Edit: I found the master contract’s mainnet app: 2736035976 | Pera Algorand Explorer

There were a total of 78 pools created, this was a global state so we could easily keep track of this. If you need other analytics please let me know what you’re looking for specifically — thank you.

@uhudo I discussed with team and the consensus is we just open-source the Gainify contracts, Algofun Shares System, and AVM Email contracts — they are minimally documented and will contain no test files, frontend codebase, or any other supplementary files. We understand the risk of blindly accepting proposal TnC for conditional open-sourcing right now and feel its the least we could do to make your lives easier. We have uploaded Gainify contracts so far, we will add AVM Email & Algofun Shares System by tomorrow.

Edit: All contracts added 04/06/2026 10PM EST

atsoc1993/xGov-Proposals-Contracts: The Contracts for the Algo.fun Shares System, AVM Email, and Gainify Staking

About the formalities, the currently shared repo still does not meet T&Cs.
An open-source license is missing and the repo hasn’t been added to Electric Capital.
I also think joining again all proposals in the same repo adds back the confusion about the proposals.
Just sharing the contracts without the accompanying tests and documentation, i.e. a partial proposal, IMO still doesn’t meet T&Cs (while I know some other xGov Council members are more lenient on these points than me).

On the content side, I skimmed the shared Gainify Contracts.
IMO they don’t provide sufficient novelty and/or quality of execution w.r.t. to the ask.

I’d advise you to focus only on one proposal first, not multiple simultaneously. IMO the AVM Email proposal has the highest chances of passing.

Ok — we will place Algofun Shares System & Gainify proposals on hold — then for AVM Email, fully open-source, add license, document, and add repo to Electric capital. ~