[ARFC] Cancel Llama Service Provider Stream

Marc continues to state factual errors that we have politely corrected but he’s yet to respond to a single correction. Now, he has completely updated the original forum post and people cannot see it. Making false accusations, being corrected, and then deleting the original accusations is against the spirit of a good faith discourse.

The original forum post read that the reason for ending Llama’s stream was:

As most members of TokenLogic are no longer working at Llama and were responsible for most, if not all, contributions to Aave

As we pointed out, this is factually incorrect as only one member has left and everyone else is still an important part of Llama; our 35+ proposal payloads have been written by engineers who are still full-time at Llama. Marc has not responded to this and has since changed the narrative to something else.

If the issue was truly about performance, why did Marc not inform us about this before in the first 10 months of our contract? This is the first we are hearing directly about a desire to cancel our stream. There was a lot of time to initiate a discussion about cancellation, especially after our detailed 6 month update. We post updates every month (1, 2, 3, 4, 5, 6, 7, 8, 9). We host Twitter Spaces every month for community members to join (e.g. 1, 2, 3, 4, etc.). Marc could have responded to one of the forum post updates (he hasn’t responded to a single one) or joined one of the Twitter spaces and let us know of this desire to cancel the stream. He has also never expressed this via private message. Why is it being done when there are 8 weeks left?

The post said that we don’t have much to do over the next two months, which is also untrue.

As we responded previously, we are developing the Curator and Strategic Asset Manager, which are complex contracts. These contracts have taken months of technical research, development, and testing, along with coordination with external technical teams like Yearn, Balancer, and Cowswap. It is difficult to hand over contracts like this so late in the development process. We are also working on a treasury management payload, three data analytics dashboards, and Aave financial reports for July, August, and September.

He said:

It’s important to note that a stream cannot be modified once it’s started - it can only be cut and then a new one re-initiated.

We pointed out that this is factually incorrect as a stream can both be stopped with a smaller, new stream initiated in a single transaction, i.e. using the same proposal payload. He did not respond to this.

He criticized Llama for its engineering efforts in this post, but he has privately complimented our engineering work as high quality and has said that he often re-uses variations of our payloads for his own AIPs given how good they are.

We have been receiving messages in private from current and former Aave contributors and community members expressing a similar sentiment, but who are scared to communicate it on the forum because Marc is the largest delegate. He currently has 247k AAVE delegated - nearly 80% of the quorum requirement - so it is challenging for people to speak against him when he almost entirely drives a vote. This is in addition to being a paid service provider to Aave. He was the largest voter for his own proposal in April for Aave DAO to fund ACI.

Given that ACI’s 6-month contract ends soon and partly overlaps with Llama’s work, there is a clear conflict of interest in this discussion. It would be as if Gauntlet put up a proposal to cancel Chaos Labs’ stream.

Llama’s contract with Aave ends in 2 months and we do not intend to ask for a renewal, so we’re one of the few groups that feels comfortable voicing what’s on a lot of people’s minds.

We have been willing to compromise and request to work at a reduced price though it is a significant and unexpected reduction. We hope the DAO should at least discuss a reduced price as several community members have brought it up as a viable option.

10 Likes