Earn Interest on wxDAI with Hatch Funds - TEC x AGAVE


The Tam-Zepti proposal for making an initial buy into our own bonding curve ignited further explorations into possible economic and inter-DAO opportunities for the TEC. Coincidentally, after much anticipation, the AGAVE platform launched shortly thereafter. AGAVE, an offshoot from 1hive, is a protocol built on xDAI for Borrowing and Lending various types of token assets. I saw this as a perfect opportunity to seize the momentum and build on the soft-conensus we found around exploring all the possibilities laid out before us, given the success of the Hatch.

We arranged a meeting on September 6, 2021 with representatives of the TEC and AGAVE and after fruitful discussion I can come forward with three opportunities for us to collaborate with AGAVE and provide economic benefit for the TEC. I will draft three different posts to allow us to accurately discuss and iterate on each proposal.

Proposal #1 - Deposit a portion of Hatch funds in wxDAI into AGAVE

This was a great idea brought forth by @sem where we could take a portion of funds from either the Common Pool (TEC initiative funding), the Reserve Balance (the underlying collateral backing the ABC) or both and deposit it into AGAVE, earning passive, low-risk yield.

Similar to other lending platforms when depositing collateral you receive a token that represents your deposit (with interest added) that you use to redeem the original asset whenever you choose to withdraw (and collect said interest). If we deposit xDAI into AGAVE we receive agxDAI which would be held in our Common Pool or be used as all or part of the base currency for the ABC.

I’ll address using the Common Pool and the Reserve Balance separately since each carries unique risks and benefits.

Common Pool

The most straightforward way to execute this proposal would be to use a portion of our Common Pool funds (based on the Commons Tribute) to earn some passive income. Our Commons Tribute probably will lie anywhere between 20-50% of Hatch funds and it is not likely (hopefully) that we will spend all of that in the near future and we will constantly be collecting more as our Augmented Bonding Curve provides us with a constant stream of additonal funding. Putting in a sizeable chunk of wxDAI from this pool will allow us to get around 3-5% APY back that can be channeled back into our Common Pool and provide more funding for Token Engineering.

The benefit for AGAVE is the TVL and liquidity on their platform allowing them to offer competitive borrowing rates. There was some initial discussion on AGAVE providing us with preferred interest rates for providing collateral, however they have a DAO and a governance process so that needs to be investigated further on their side.

Some questions to consider are:

  • How much of the Common Pool funds should be deposited?
  • How much should we be able to withdraw at a time?
  • Can we trust the AGAVE contracts(which hold our wxDAI)?
  • ???

Reserve Balance

This is where it gets a bit spicy, but basically the point is that there will be a huge amount of xDAI held in the Augmented Bonding Curve which will never see the light of day, very likely. We can deposit this xDAI into AGAVE and earn passive yield, thus increasing slowly the value of the TEC token as interest accumulates. This could be implemented in three ways (please correct me if I’m wrong @sem):

  • Changing the base currency of the ABC into agwxDAI (buying and selling TEC for agwxDAI).
  • Having two ABC’s (one for wxDAI, one for agwxDAI) .
  • A hybrid ABC that has two base tokens that accepts or returns a bit of both when transactions are made.

This, while technically can be done, I feel there are significant cultural hurdles that would be needed to make this solution feasible. My personal opinion is we should focus on educating our community and launching our ABC as is without doing any spooky changes that could have technical bugs or unforeseen economic consequences, however I leave it here so we can open up the discussion.

Opening the Discussion

This is a great opportunity for us to explore new platforms and support the protocols being built on xDAI. I think the best way to collaborate with other projects and protocols is to actually use the tools they are building. I’d like to open up the discussion here and I would love to hear from a token engineering perspective any further ideas or perspectives around this proposal!


Well done @divine_comedian for reaching out to a similar community and developing possibilities for collaboration with shared-purpose. The DAO is a great organizational model, but it takes individual people to recognize each other and form connections. :ok_hand:


These are fantastic posts @divine_comedian, thank you for bringing them up.

I think this proposal can have a HUGE good impact in both communities if TEC staked most of it’s wxDAI into Agave:

  • With only with a modest 3% APY (to be conservative), TECommons would earn 40k every year that could be used to fund an extra Token Engineering project.
  • It would bootstrap Agave’s wxDAI lending pool allowing people to borrow money at a very competitive price during the first months, possibly entering a virtuous circle in which even more collateral enters into the protocol, as it is required to borrow.

These are some considerations we have to take into account:

  • We should assess the risks before putting relevant parts or all TECommons treasury in another protocol. Being in the lenders part of the relation puts us in the low-risk area, as all Agave borrowings are over-collateralized (for each wxDAI you lend, you can only borrow 0.775 wxDAI). Although there are other smart contract or Agave governance risks that we will need to assess before we can make this decision.
  • Another think we have to consider is the harm we can do to others. If it were the case in which TEC provided a huge proportion of WXDAI in Agave and it withdrew them all at once, it would cause a spike in the borrowing interests, potentially leaning to liquidations.
    • That would not limit TECommons day to day operations as agWXDAI can be used as any other token to be held in the Common Pool and the Reserve.
    • It would only limit TECommons in the scenario that it wants to migrate their wxDAI to another protocol. In that case it should be done with care to not have excessive negative side effects on Agave.
    • That being said, Agave may offer preferred interest to TECommons in the conditional tokens they are planing to launch next if TECommons agrees on leaving in an ordered way in the case it wants to withdraw the funds from the protocol, maybe by adding an anti-“bank run” clause in it’s Garden Agreement.

In relation to technical solutions, I’ve been researching a bit since the call on September 6, and it looks like it’s totally factible to have both wxDAI and agWXDAI in both Common Pool and Reserve in any desired ratio. We can start with 30%-70% agWXDAI-wxDAI and increase the lended token over time if TEC wants.

This could be done with some Solidity work adapting an Aragon app for Compound (an Agave similar lending protocol) to manage the transformation of wxDAI and agWXDAI in the pools. This would be transparent for the Conviction Voting and Augmented Bonding Curve apps, which will interact with wxDAI all the time, and periodically call a function that returns wxDAI and agWXDAI to the desired ratio. This way TEC could earn interest having part or all of the funds in agWXDAI meanwhile the user only interacts with wxDAI. This app could also be used to withdraw progressively wxDAI from the protocol without causing the bad consequences of a “bank run”.

In order to have an informed decision making on this proposal, I find this video particularly educative and recommend it to anyone in the community:


This is assuming we put in how much wxDAI into AGAVE? It would be unreasonable to assume that the TEC would put in anywhere near to all of the hatch funds into AGAVE.

To your points regarding using agwxDAI as part of the reserve balance I have to re-state that I am hesitant to change any of the underlying structure of the ABC. While its cool to hear the technical validation, we have not been able to adequately introduce the basic Bonding Curve concept into the TEC and a vast number of people in the community probably don’t know how it works.

Adding new layers like a second base currency has lots of token engineering potential but it would probably also confuse a lot of users using our ABC. If this option (having part or all of our Reserve Balance in agwxDAI) gains traction I would propose two sub-solutions.

  1. Build this dual-currency(or agwxDAI only) ABC post Commons Upgrade and deploy it alongside the initial ABC, having another market for TEC (and perhaps providing more arbitrage opportunities). Also testing our Tao Voting capabilities along the way.

  2. In the event of a dual-currency and singular ABC we could accept both in any quantity in BUY orders and return only wxDAI, using AGAVE to unstake agwxDAI and return it in the same transaction, we could also use a base ratio of agwxDAI we want to hold in the reserve balance using some sort of dynamic ratio to maintain a percentage. This, while creating more technical overhead would streamline our user flow while leveraging AGAVE’s protocol and generating trade volume on their platform.

Otherwise, changing anything in the ABC user-flow this late in the game I think would become a big blocker for us launching, which in my opinion needs to happen ASAP given that we are right now somewhere in Hatch limbo.

I would advocate for a simpler solution right now which would be to use only Common Pool funds to exchange and hold agwxDAI, perhaps using a base percentage that stakes and unstakes tokens as funds enter and leave the Common Pool. I would propose, based on some initial numbers, somewhere to the tune of 30-40% of Common Pool funds. Which if we assume we have a Commons Tribute, at launch, between 20-50% would be between a deposit of 94k - 314k xDAI with an APY range at 3% would be 2.8k - 9.4k xDAI of passive funding income. Take into account that as our Commons Pool grows, and if we are offered a favourable interest rate these numbers could be higher.


To clarify, with the technical solution proposed in the previous post, we could have portions of the bonding curve reserve and conviction voting common pool with portions of agWXDAI and still have:

  • Only one bonding curve / primary market. I think this is the desirable thing.
  • Only one currency in the bonding curve (to choose between wxDAI or agWXDAI). We can leave it with wxDAI for simplicity. This means people would buy and sell with wxDAI only.

The pre-fixed proportion of Reserve and Common Pool’s wxDAI staked into agWXDAI (it could be 30%) could be increased or decreased using Tao Voting.


This particular sub-solution is very interesting to me.

I don’t like the idea of inserting a general financial product into the engine of our economy right before we design it. Maintaining the ABC as it currently stands has a lot of benefits and minimizes risk. The main benefits being – its simple and allows for communities to witness an effective implementation of a ‘collectively’ designed (small-scale) economic system. This isn’t trivial.

The risks of implementing a dual-currency ABC right now involve many because we are creating our first dependency (Agave), whose oversight process and community…are honestly unknown to me…and while I believe they probably have a strong community with good governance around decision-making…I simply do not know.

I think before this Proposition should ever be considered we should first have some type of information sharing between the communities – beyond the interactions and perspectives of a handful of community members…and while I appreciate the role of experts maintaining discretion over actions at this stage in our community…I believe we aren’t giving this issue the time that it deserves.

I know this is just in the exploration stage, but in my opinion it has exposed a lot of risks associated with DAO-2-DAO interactions of any kind.

If the success of their interest bearing financial product (and our ABC) is dependent on the decisions their community makes, then I believe it would be beneficial to understand how they make their decisions in the first place.

I am always afraid to say that, because I know it is still a young industry and honestly we don’t have that many options to choose from, especially when we know they are value aligned or involve people that we trust. These interactions are not enough to ensure the security we want in the long-term, especially around the ABC.

I’m all for getting creative and developing some badass bonding curve financial instrument…but I think keeping our ABC simple is more important.


Debate from 14-09-2021


I will third the concept of keeping the ABC simple for the first launch.

I tend to lean towards keeping Conviction Voting Simple as well… I would rather launch without extra complications and edge cases in the base layer… if we want to diversify our holdings, agwxdai would be one of many assets we might want to hold… I don’t know how i feel about making a bunch of extra work to earn 3-10% APR with a protocol that launched last week…

If we want to hold agwxdai let’s simply hold it in a subDAO that is outside the system and make it part of diversified Common Pool holdings, and then have clear rules about putting it back into the Common pool (like everytime we spend 50k, we top it up with 25k or something like that). This would be a simple system, that follows other working group models. This working group model could diversify our holdings

Let’s keep things simple, minimize scope and minimize risk for launch and then when everything is working, we can start weaving the web of DAO-integrations.

I definitely agree that messing with the ABC config before launch is inviting more headaches.

I think the key take-away from the debate was that nothing needs to be done right away to implement any of these proposals. @Tamara made a good suggestion of starting small (5%-10% of the Common Pool) and going up from there if it works well. We can choose when that would start. @santigs also echoed your point of having a sub-DAO in charge of managing these holdings.

I think there’s more value in this collaboration than just the APY. It’s important to support other projects on xDAI and incentivize users and protocols to remain on the network. If we don’t support each others work and encourage growth via the protocols and dapps unique to xDAI then surely users and organizations will go to where there is more action happening.

The TEC has a good position to leverage where it can meet the organizations goals by supporting other projects, and potentially generating funding for itself along the way.

1 Like

Of all the comments I have read here on TEC forum and in the recorded meeting I like this approach the most. It wouldn’t require a tremendous amount of work or really any commitment. Try it, if you don’t like it the subDAO moves liquidity elsewhere.


Just wanted to updated everyone here. Agave was approved by xdai community for $500k in $STAKE rewards to help bootstrap agave TVL so shortly this discussion may become more attractive for TEC from at least an ROI perspective.




Very Cool! I haven’t forgotten about these proposals. The TEC needs to figure out some important parameters before we can get a better estimate of funds we can commit towards an AGAVE collaboration.

  1. How much funds we’re going to spend buying TEC when our ABC opens.
  2. How much of the Hatch funds we’re allocating into our Common Pool
1 Like

Just wanted to share to keep the team up to date. The protocol has a modest $144k TVL slowly and steadily increasing in at a fairly linear consistent rate since Septembers launch.

As you may already know next week begins the deploying of rewards on the protocol and we expect tvl to grow a bit more, watch video to learn more

I will keep the TEC community informed as the team continues to roll out updates. Please feel free to follow us on twitter for updates.

1 Like

Thanks @Monstrosity, we are discussin how to manage TEC funds here: The Initial Buy-In

To give an update