Level K Worker Proposal and Payout 5/2022 - 6/2022 - LATE SUBMISSION

dxDAO
1

This is number 5 of 5 catchup proposals

1: Level K Worker Proposal and Payout 9/2021 - 10/2021 - LATE SUBMISSION

2: Level K Worker Proposal and Payout 11/2021 - 12/2021 - LATE SUBMISSION

3: Level K Worker Proposal and Payout 1/2022 - 2/2022 - LATE SUBMISSION

4: Level K Worker Proposal and Payout 3/2022 - 4/2022 - LATE SUBMISSION

Timeframe

I worked full time in May without vacation days. This period included attendance of MIT Bitcoin Conference May 7-8 which was a weekend. In June I took a week of vacation. I also attended Consensus in Austin in June.

  • 5/1/22 - 6/30/22

  • 2 months

Responsibilities

  • Support Arbitrum base operations, mostly Swapr farming.

  • Organize and run weekly dev call

  • Speak on community calls and as needs and opportunities arise for public speaking

  • DXdao Multisig transactions

  • Keep up on all product chats

  • Keep up on all Discord chats and ensure users/community members’ problems with products are being addressed

  • Coordinate smart contract auditing and architecture

  • Interview new product team candidates and support onboarding

  • Support technical due diligence and review as needed across squads

  • Help DXdao prepare for Devcon

Accomplishments

  • Continued auditing activities
    -In May Coordinated kickoff of first audit with Sigma Prime, of DXgovernance
    -In June coordinated plans for Carrot V1 audits by Sigma Prime and Omega Team
    -Audit of Curve wrapper contract
  • Spoke about DXdao at DeFi Toronto

  • Reviewed Reflexer system to better understand RAI and determine what DXdao’s course of action should be with its RAI holdings.

  • Talking to DAOhaus about DXdao to support their feature of DXdao as a “DAO of the Week” in the Gnosis Chain newsletter.

  • New contributors Philip and Velu

  • Helped preparation for hotels for Devcon6

  • Active in initial planning for DXhackathon, helping to secure venue

What I think went well

Scheduling of auditing for Carrot V1 went smoothly. And auditing busy in general.

What I think needs improvement

Lost lead dev from Space Inch as he got moved to another project. Could have tried more to keep him going with Swapr.

There is lack of clarity on Nimi’s relationship to DXdao. I feel like this could have been addressed by now, but hasn’t.

Compensation

Experience Level: 8

Month one.

  • $9,000 (9000 xDAI)
  • $9,500 DXD
  • 0.1667% REP or till 4% max is reached

Month two.

  • .75 * $9,000 = 6750 (xDAI)
  • .75 * $9,500 = $7125 of DXD
  • .75 * 0.1667% = .125% REP or till 4% max is reached

The full 2 month period.

  • $15,750 (xDAI)
  • $16,625 (DXD) to be paid in a vesting contract continuously for three years with a one year cliff.
  • 0.2892% (REP) up to 4% max

Experience

I have been involved with DXdao since inception, as part of Level K, involved in a variety of areas of responsibility. You can find Level K worker proposals via the governance interfaces by searching for “Level K”

1 Like
2

Caney Fork voted NO on this proposal with all of its REP. The proof of work in this proposal is not up to the standards of a Level 8 contributor in DXdao working full-time.

The ‘accomplishments’ section consists mostly of John’s activities outside of DXdao - instead of proof of his contributions to technical development of the products. There are no links to Github repos or any technical work in this reflection, because there was no activity from jpkcambridge during this worker period on any active DXdao product on Github (only Nimi).

Moreover, John has failed to follow through on commitments to improve DXdao’s security and proposal monitoring system. Over this worker period on the May 25 Governance Discussion, John gave an overview of how to manually monitor proposals. And then said:

We want a robust [monitoring] system that scales with the DAO…We want to expand this into a more reliable system that’s transparent that has contributors participating equally across the board. So our next step is to form a small team, and probably draft a few other contributors…and create a shared spreadsheet and actively share our records of how we’re monitoring.

Three months later, there is no progress on this front and no updates from John. More troubling, this is not the first time John made a commitment to a better system for proposal monitoring. In the dxdao.security chat in Keybase in July 2021:

John security monitoring commitment
John security monitoring commitment1449×846 158 KB

Despite saying he would “share a couple docs soon”, there was no spreadsheet or followup and those are the last messages in the dxdao.security chat.

This all comes after an on-chain proposal passed to pay an auditor in January 2021 complete these services:

Proposal Monitoring Posture (7 days to complete)

  • Review overall monitoring process and procedures
  • Review monitoring scripts to ensure full coverage

$15k was paid for these services, but 1.5 years later, there is still no robust proposal monitoring system at DXdao.

John himself has always preached the importance of security, but his actions suggest otherwise.

1 Like
3

A couple clarifications:

Are you claiming REP in these proposals? You mention the REP amounts in the forum post but then not including in the on-chain proposal? Is this REP able to be claimed later on?

Also, are you applying the overall haircut to REP as well?

The haircut is include in the pay portion of your on-chain proposal but not mentioned in post, so seeking clarification?

Another thing:
The forum and on-chain proposal say you are claiming xDai but the proposal is not requesting xDai. You are claiming USDC instead?

Is this correct?