Aragon dTech Season 1 Funding Proposal

May EOM report

@daniel-ospina @lee0007 @fartunov

Deliverables

  1. All user support tickets replied to within 16 hours and resolved within 24 hours - Completed Monthly
    • Actual first response time is 47 hours this is due to a technical error which is under investigation
    • Actual resolution time is 64 hours this is due to a technical error which is under investigation
  2. Documentation translated into a minimum of two languages. - In Progress
    • Research completed into the most popular languages here.
    • Survey from
  3. Close communication with development and product teams for Zaragoza, meeting milestones for documentation and preparing for QA. - In Progress
  4. Provide communication and transparency to the satisfactory of other guilds at Aragon - Completed Monthly
    • Delegation transparency page here.
  5. Have tangible results from collaboration with “like services” guilds in other communities - In Progress
    • Managed to combine Otoco, Gnosis and Client so we created Aragon’s first legal wrapper.
  6. Bi weekly call transparency and auto transcription - In Progress
  7. Increase contributor engagement having at least 3 long term active contributors - In Progress
  8. Set backup delegations which shadow other delegated roles within the guild - In Progress

Additional deliverables

  • Finding the bug in the code regarding the problem with Aragon Client and Polygon mainnet and working with the DevOps team debugging it.
  • Requested and allocated moderator permissions for core contributors on Discord to further decentralize moderation tasks. Sorted out channels with no moderator access to ensure all public channels can be accessed. - Completed
  • Using Dework and keeping up to date with new developments, functionalities and features to prepare for DAOwide adoption - Ongoing

Finished bounties

  1. Recreating/ Debugging Tech Doc. III Part Dev. (CLI) - (DTG.P2.M4.N1)
  2. May contributor support training (DTG.P2.M5.N1)
  3. Importing Tech Doc. III and IV Part Dev (Govern + Vocdoni) (DTG.P2.M5.N5)

Funding Request

  • USDC 90% Total - $18,414
  • ANT 10% Total - $2,046
  • Amount Core Contributor compensation $10,500
  • Amount Flexible Rewards $3,500
  • Amount Bounty Rewards $6,460

See detailed financials here.

Thank you to everyone involved. I am available for any questions and am able to provide any additional details that may be requested.

1 Like

Thank you for a clear report. Few questions

Can you open access to this page?

Is there a link, please. Wondering what the survey is.

Congrats on this! has this process been documented?

Can you remind me please, how is long-term defined? and what is the current count?

Can we link these documents or the deWork bounties for transparency, please

Thank you Renee for your quick response.

  1. I opened access to the research page into the most popular languages. If that does not work I will need to speak to someone managing Notion as my powers are limited :thinking:
  2. ‘Survey from’ was a typo.
  3. Anson is going to get back to you here regarding the documentation for this work.
  4. Long term in our understanding is by the end of Season 1. In April we have onboarded 2 contributors who have been training and working on different bounties. With our new bounties we are working towards attracting more talent who could stay with us long term.
  5. Please find links to the Notion card or Dework task of the bounties below.

Should you need any more information or have any questions, please let me know.

1 Like

1/3 funding approved cc @daniel-ospina @fartunov

I’m not a lawyer™
however…

Legal wrappers - Aragon User Documentation does connect the dots between an Aragon DAO and a Delaware LLC

@lion917 @jessicasmith @eaglelex are all encouraged to critique what’s going on here… the super fun part is that we can use EVM Crispr to mint our new tokens and i think this is what makes that project so special = it should open up some doors for real development in established daos looking to move more mainstream

1 Like

2/3 supported @SpectraCryptoVerse

@Carla78 - dropped a question in the language selection Notion

@alibama Love the initiative! Certainly, the guide can use some polishing but the deliverable is marked as “in progress” so it makes sense. It seems though it’s just the tokens are minted on Aragon and then stored in a Gnosis Safe…it’s not an Aragon DAO with a wrapper by any means. Or am I deeply misunderstanding the guide?

I am not a lawyer™

All we’re doing here is minting new tokens for a DAO so that the DAO may exercise a legal instrument. As mentioned in the Otoco AMA held this morning there really is no such thing as a fully wrapped DAO (and i should probably edit my language accordingly).

What does exist = a way for DAO’s to leverage an LLC instrument, and begin using that legal primitive to then acquire traditional fintech assets such as bank accounts, insurance etc… we’ll even have a simpler way to pay taxes! (exclamation mark = snark)

As you point out = for Aragon to really be leveraged more strategically we would need to work with tools such as evm-crispr, openlaw.io perhaps, etc… to orchestrate additional process unique to a DAO = there’s no implicit connection between the inner-workings of a DAO and the functioning of the LLC.

My hope is that the leadership team may see some longer term value in this small proof-of-concept and be receptive to additional proposals in this space that would begin to address these orchestrations.

2 Likes

I am still not understanding this.

Let’s take the narrow definition of a DAO as addresses (defined either through a permissioned list, or by holding a specific token) that govern a shared on chain resource.

The way I understand the described design what we are “wrapping” is a Gnosis Safe so the “DAO members” are the signers on that Safe, NOT the holders of the token (leaving aside the fact that the tokens are held in the wallet)…it’s a very useful thing, but I don’t see how the token or Aragon has a role in it

Unless I am misunderstanding this and every member of the Example DAO should create a multisig where they hold their tokens in which case we are wrapping the individuals as LLCs, not the DAO itself

i really think we should get legal in on this = @Tayy or @eaglelex or @lion917 want to weigh in?

all i know is that from the people i’m working on next steps with it appears to be sufficient… the tokens themselves become part of a legal entity, and that means that if i choose to use something like c14.money to trade the tokens on VISA to grab some fiat I should be on the right side of the law.

perhaps when the next aragon app thing comes out we can do some host-the-party with lawyers and get some grindier reviews?

Thanks @fartunov for the question, my answer directly on the Notion page.

@ronald_k Hello Ser,

we’ve been working some “legal wrapper” work, however thusfar only @fartunov has really provided a thoughtful critique (which i genuinely appreciate). Frankly all of his points are pretty interesting, however I don’t feel competent to respond.

Could you help us out here? the way things are organized presently

Aragon - provides tokens and governance model
Gnosis - creates a multisig wallet that interacts with Otoco
Otoco - provides the LLC and signs it with the Gnosis vault as the “main signature”
Otoco - imports the token contract from Aragon as the “shares” of the LLC

my interpretation of this is that the functional aspects of the DAO could then be regulated within the Delaware LLC, however I am still not a lawyer™

1 Like

Hey, thought I would weigh in here since I’m from OtoCo and can probably speak on some of the technical and legal limitations.

As @alibama said, it’s pretty difficult to “wrap” a DAO in its entirety. It’s possible sometimes, with very small DAOs.

But Aragon and OtoCo can work together to bring entity management to web3. Here’s one idea:

Let’s say Example DAO of 4 people creates an OtoCo LLC (via multisig for low trust or single sig if you have plenty of trust).

LLC can have its “shares” be a certain Aragon governance token and all holders are considered members of the LLC. So you’re a member of Example DAO, and you’re also a member of Example LLC.

Now, for LLCs to add members, make big commercial decisions, remove members, acquire assets, etc. these things often require consensus among members. All of that consensus could be reached on Aragon (or any other DAO management platform). So what you’re left with is an OtoCo LLC where Owner/Shareholder Meetings, Member Voting, Meeting Minutes, etc, is done via Aragon instead of paper, pen, and zoom meetings.

3 Likes

Thanks for the clarification Michael - it is really helpful!
My previous understanding was that the Example LLC members are the multisig signers, not the token holders and those two groups are not necessarily the same.

Deliverables

@lee0007 @daniel-ospina @fartunov

  1. All user support tickets replied to within 16 hours and resolved within 24 hours - Completed Monthly
    • Actual first response time is 11 hours 45 minutes
    • Actual resolution time is 32 hours
  2. Documentation translated into a minimum of two languages. - In Progress
    • Spanish and French has been chosen as the first two languages
    • AI translation is completed and Spanish native speaker overview is done and French is in progress involving community members
  3. Close communication with development and product teams for Zaragoza, meeting milestones for documentation and preparing for QA. - In Progress
    • Developed guides for the Aragon App in conjunction with Harry and Product Marketing
  4. Provide communication and transparency to the satisfactory of other guilds at Aragon - Completed Monthly
    • Delegation transparency page here.
  5. Have tangible results from collaboration with “like services” guilds in other communities - In Progress
  6. Bi weekly call transparency and auto transcription - In Progress
  7. Increase contributor engagement having at least 3 long term active contributors - In Progress
    • Retained 2 long term contributors
  8. Set backup delegations which shadow other delegated roles within the guild - Completed

Additional deliverables

  • Polygon priority fee fix in alignment with the development team.
  • Fixed broken explorer link on Voice
  • Google blacklist problem help
  • Using Dework and keeping up to date with new developments, functionalities and features to prepare for DAOwide adoption - Ongoing

Finished bounties

  1. Community review Tech Doc. III Part Dev. (CLI) 1/2 (DTG.P2.M5.N2)
  2. Community review Tech Doc. III Part Dev. 2/2 (CLI) (DTG.P2.M5.N3)
  3. Importing Tech Doc. V Part Dev. - Apps, API, ACL, UI (DTG.P2.M5.N6)
  4. Walk a client through building a DAO for Otoco integration (DTG.P1.M5.N7)
  5. Recreating/ Debugging Tech Doc. IV Part Dev (Govern + Vocdoni) (DTG.P2.M5.N8)
  6. Creating Visual Docs (DTG.P1.M5.N10)
  7. June Team Development (DTG.P1.M6.N31)
  8. Fast check Tech Doc. V Part Dev. - Apps, API, ACL, UI (DTG.P2.M6.N348)
  9. AI Translation Fundamentals + Aragon Client Docs into Español (DTG.P2.M6.N38)
  10. AI Translation Fundamentals + Aragon Client Docs into French (DTG.P2.M6.N40)

Funding Request

  • USDC 90% Total - $18.369
  • ANT 10% Total - $2,041
  • Amount Core Contributor compensation $10,500
  • Amount Flexible Rewards $3,500
  • Amount Bounty Rewards $6,410

See detailed financials here.

Thank you to everyone involved. I am available for any questions and am able to provide any additional details that may be requested.

3 Likes

1/3 approved

Love your guys super clear, simple reporting thank you 2/3 approved cc @Ricktik6

Thank you Spectra and dTech team, great work and exemplary reporting!

I understood there is a migration going on from Helpscout to HubSpot’s ticketing system which is a substantial initiative worth mentioning?

I had a chat on this with @brent.

  • The notion space provides no rationale for choosing these languages
  • What is your best estimate of a metric to determine whether it is worth allocating further resources towards multilanguage efforts to avoid sunk cost situation where we go “oh well we have some documents now in Spanish, let’s keep translating”, and start offering support and start a blog and a separate telegram and so on and so on without a validation if there is actual need

Please link the respective spaces where this progress is documented

Contingent on responding to the above I give my support for release of funding 3/3.

Another discussion with @brent is that since Season 0 one of the objectives of the guild was to professionalize the support role. We are nearing the end of season 1 and this is still not live. I understand there is some consensus and understanding across current guild members about process and scope but having this documented is still lacking:

  • which type of questions does support answer and what requests are outside of its scope
  • which types of questions are escalated or handed over to other guilds or directed to external resources

e.g. (my examples might be completely off-base, but they are here to illustrate the point)

  • Someone comes and asks to connect a Gnosis Safe to a Client based DAO?
  • Someone has a problem with their Client DAO and we have determined the problem is with the Polygon network, how do we proceed?
  • Someone comes enquiring about conviction voting or NFT-based census

For these past two seasons to be considered a successful experiment and to have confidence in the Main DAO funding, the guild should be able to demonstrate some professionalization of the function

The notion space provides no rationale for choosing these languages

Not sure why we are discussing this in the forum. I thought we resolved this on a call we had when I gave you a link to a notion page on the rationale for choosing these languages that you had already commented on June 3rd and I also explained the move to go to Spanish with you which you then understood. What you did point out is that the conclusion to our findings could be explained a little better, I updated the notion page for this… https://www.notion.so/aragonorg/User-Tech-docs-Translation-7fcb376f892d4413a2833be479fb50ae

  • What is your best estimate of a metric to determine whether it is worth allocating further resources towards multilanguage efforts to avoid sunk cost situation where we go “oh well we have some documents now in Spanish, let’s keep translating”, and start offering support and start a blog and a separate telegram and so on and so on without a validation if there is actual need

This proposal says nothing about allocating further resources or to keep translating, it only says two languages will be translated, end of story. The decision to move forward with a language past documentation is a separate discussion that is out of scope of this report. I have never heard anything about an Aragon blog or Telegram in another language.

Thank you for the clarification - much appreciated!

Also to make it crystal clear, the update happened yesterday (after the statement to which you are responding) although our discussion referred took place on 28th of June

I don’t think this is fair at all compared to what dTech set out to do since its inception last year and dTech is far beyond an experimentation phase. Professionalism is definitely not the word to use here. Writing down what requests are outside of dTech’s scope is important, but a reason for the DAO to not have confidence in the dTech team after all the progress they have made is brutal.

dTech is a passionate and driven team that has consistently executed on many initiatives with success, provides solutions not problems, brings a huge amount of value for the DAO… and has room for improvement like updating the Notion page to have a note about dTech’s support scope.

2 Likes