Thank you @Arb4Ever for the thoughtful comments, many of which concern tightly breaking down future deliverables and developments. These are most certainly valid when it comes to scaling a traditional, early-stage company that works towards objectives defined by its leadership team. These objectives are naturally well-defined and donât change in a short time frame. We have avoided a tight breakdown because our main goal is to serve the DAOâs needs, which are volatile and non-predictable even in the near term. By hammering down the exact outputs and the associated KPIs etc. at this stage on, e.g., a quarter-by-quarter basis, we are more than likely to create a structure that incentivizes us to work on deliverables that arenât relevant to what the DAO requires in the future. The core idea of Entropy is that we are agile and work in the open, meaning that at the end of the day, our exact deliverables and associated success should be decided by the DAO.
When it comes to the core fee structure and salary sizes, we have been actively analyzing the labor market, and to say things are competitive is an understatement. Good talent has options across VCs, research shops, leading CEXs, etc., all of which pay, at minimum, $100-150K and generous equity packages/carried interest. Considering we are and would be exclusive with Arbitrum, this does limit our upside in terms of equity valuation/growth. In addition, we are starting a business in a public setting for the whole world to view our finances. An example scenario for a potential hire: take $125K and an equity allocation at a top-tier research shop, or join Entropy for $125K + equity, exclusively working with one customer in the open at a company with a runway of 1 year and the possibility for the DAO to clawback funds at any moment. This example should put things into perspective, and we expect that we will have to pay accordingly in order to have a chance at these hires. Additionally, as mentioned in our proposal, it costs employers much more to pay people after health benefits, etc., and if you add in office and related expenses employees with extensive experience should be assumed to require at minimum, the amount of capital needed to scale a team expands extremely fast. We do, however, feel that talent is more likely to join us and contribute to Arbitrum full-time because we can offer these benefits and steady fiat-denominated salaries versus purely getting paid in ARB on a contract basis.
We have been contributing to Arbitrum full-time under the Entropy Advisors brand since late April, and weâve constantly been in a situation where there is more demand than we currently have the capacity to service. As such, we have hiring needs that we would need to begin fulfilling today to fully meet that demand. However, based on our experience in recruiting personnel, we know that this will take time since finding the right fit, especially for the positions we are recruiting for, is a time-intensive process. We are putting our reputation on the line here, and hiring for the sake of hiring is not an option. The cost structure of $100K per month until we scale to 7 FTEs is based on delegate feedback, and the idea is to create a clear ceiling on our costs while we continue showcasing our value and gradually increase FTEs. Weâve also added quarterly transparency reports to the proposal through which it will be easy to infer if we are utilizing funds with bad intent.
One of Entropyâs strengths is that our team has vast experience in operations and scaling teams, both in a DAO setting as well as connected to more traditional companies. Blockworks Research has become a leading research brand in the crypto space, with Sam as the first employee and Matt as his first hire. Sam hired/scaled the team to over 10 people, managed day-to-day operations, and worked with the engineering team for the MVP SaaS-based product launch back in 2022. (Here are multiple testaments from the Blockworks co-founders, Mike and Jason). Matt, on the other hand, took the initiative to launch and lead the governance services arm at Blockworks Research, which actually led to the establishment of the ARDC that the DAO leverages on a daily basis. Pruitt, Entropyâs first hire, co-founded 404 DAO while in college, which displays ambition much higher than even an above-average college grad. Brick, Entropyâs most recent hire, in addition to having worked as a research/governance analyst leading Blockwork Researchâs governance efforts within Arbitrum as well as the ARDC engagement, has several years of experience in TradFi within investment banking and venture capital, having specialized in corporate and financial structures.
As shown by our work within the Arbitrum ecosystem, we are acting as a mesh layer that operates in the open, which is something we will continue to do moving forwardâfunctioning as an extension of the DAO. In no way are we forcing ourselves into a central position that creates dependencies that would prevent the DAO from functioning as it has until now if we were removed. To be clear, we are not striving to implement ourselves in, e.g., any roles comparable to back-office functions in TradFi. At any point in the future, the DAO has the ability to terminate our contract and clawback funds. Although we recognize that this isnât a frictionless process, Entropy is always working in the open and under the direct supervision of another party, be that the DAO or possibly the OpCo in the future, meaning that itâll be clear if our services arenât providing value. Naturally, if we are doing a good job there will be some dependency as is the case with any service provider that is performing well. In a hypothetical scenario where Entropyâs contract is terminated even while being a value-add to the DAO, operational efficiency would decrease. You also brought up transition/unwind terms. To our knowledge, these havenât been utilized in any prior engagements between a service provider and the DAO. We actually think it might make sense to begin incorporating these across all relevant engagements and are happy to amend our proposal accordingly if delegates find it sensible.
For the rest of the points you brought up, we feel as though these are covered by the changes we recently made to the proposal: