I am very behind on worker proposals, starting with this period of September 2021 - October 2021. I had 3 weeks of vacation time in July and August, and then things got incredibly busy for me in August and September when there were issues with the Arbitrum launch that required redeployment of the governance base. In that time frame I fell behind on keeping up with the forum and with my own worker proposals and things remained very busy through the October events in Portugal. As time has elapsed, catching up on worker proposals has become a larger task, and other responsibilities and work continued to keep me busy. Timely worker proposals are critical for the DAO to operate efficiently and I am working on covering the missed proposals now. I am open to having some sort of late penalty and some sort of disincentive, but just know that I was busy handling a variety of responsibilities which felt pressing at the time. Please bear with me as I work through posting worker proposals for past periods. My goal is one per day this week.
9/1/21 - 10/31/21
This period involved a lot of travel and attending of conferences.
MCon in Denver from 9/15-9/17 (Wed. - Fri.)
Messari Mainnet from 9/20-9/22 (Mon. - Wed.)
DXretreat from 10/6-10/15 (Wed. - Fri.)
The DAOist Lisbon 10/19 (Tues.)
Liscon 10/20-10/21 (Wed. - Thurs.)
ETH Lisbon Hackathon 10/22 - 10/24 (Fri. - Sun.)
19 days of conferences and retreats, almost half the working days which is a lot, but these were some of the first conferences after lockdown and also the first time meeting many members of DXdao that I had been working with for a year or longer online!
Organize Arbitrum relaunch, including Arbitrum Base, Swapr, and SWPR token, as well as SWPR token migration
Sync and communicate with Arbitrum team to support DXdao deployment efforts
Support Arbitrum base operations and launch of Swapr farming.
Planning for DXretreat. Helped plan programming for the retreat and also coordinated lodging for DXdao in Lisbon.
Organize and run weekly dev call
Support DXgov team formation and ramp up
Work with Tammy on Hats grant and legal entity research
- Involvement in Arbitrum Relaunch.
Here is a quote from what I sent to our contributor chat:
“folks, we have a big problem. The permissions setting proposal failed to update the permissions and upon inspection it was discovered that the “Max time for execution” which is set to 1 day is actually counting from proposal submission rather than from the proposal passing (note other than Augusto observing this we haven’t double checked which we should do in the morning to be absolutely sure this is the case). This setting therefore is such that it prevents any proposal whatsoever to pass via boosting, because all the timelines are longer than 1 day from submission. The only way to pass a proposal on this deployment of DXvote (the current Arbitrum base) is to pass proposals by absolute majority, i.e. with > 50% of the vote. We have success in passing votes by absolute majority on xDai, so we were initially hopeful that this could be done on Arbitrum, but there are issues here that would make it much harder than on xDai. DXvote was deployed with the same mapped addresses that we used on xDai, however, unlike xDai, the unmapped smart contract addresses were not removed. The effect of this is, relatively speaking, the same people have less percentage of the vote on the Arbitrum base. Augusto, Federico, and I started looking through addresses. While it seems possible to get > 50% it would likely be very very hard to coordinate. And what makes this approach all the more difficult here is that in order for this to work, we actually would need to pass two proposals by absolute majority, 1 day apart, and each proposal only has 24 hours to be voted on, passed, and executed from submission.
The only other way we have thought of to address this issue would be to redeploy everything. At the moment, I actually think this is the best approach. I think first thing tomorrow we should meet, confirm the above issues as true, assess, and come up with a plan. For the folks that are still awake, I am happy to hop on a call now to discuss.
We have been working very hard and tirelessly, and there is a lot of positive momentum around the launch so far, and so I understand that this can be very discouraging. But we can’t give up now. And I am optimistic we can recover with minimal damage, but it will require great coordination and determination from everyone.”
This was quite the start to the month! And indeed, as you know, we redeployed everything. This was a colossal effort from many members of the team. In particular @AugustoL and @luzzifoss were instrumental, but there was also great support from many others, including @ross, @fluidDrop, @0xVenky, @KeenanL, @sky and probably others I am failing to remember. Very proud that we were able to recover from this and for awhile Swapr was doing great on Arbitrum. What made this more significant to me is that I had been supporting the strategy of being one of the first dapps to deploy on Arbitrum, the first general purpose L2 to be open to any app to deploy.
- Helping support DXgov formation
The benefit of being very late with this proposal is that I can say I think the DXgov team has been working out quite well, and a lot of the moves we made last fall set the stage for this.
What I think went well
As described above, Arbitrum relaunch, and DXgov team rampup
Started relationship with Omega Team which has been very important.
DXretreat was great.
What I think needed improvement
Arbitrum launch. While I am very proud of my involvement and everyone’s work on the relaunch, it would have been better if we could have caught the issues with governance prior to the launch. While we did have a thorough plan and deployments on testnet, the particular issue that bit us had to do with timescales and we could have been more careful with testing that.
Offboarding of Nissa was somewhat of a disaster. Not really sure what I could have done better given the circumstances at the time but clearly process improvements were needed. I think things have somewhat improved since.
Level K was already at the max amount of REP. According to the guidelines for a DXdao worker with expert level experience and a commitment level of 5, total compensation is 2 * 8000 = $16000 in stablecoins or ETH and 2 * 6000 = $12000 worth of DXD. Here I would like to suggest a poll to determine what a reasonable penalty could be for this proposal having such a late submission. This would represent a percentage off of Level K’s payment. For example, if the result was 10% then Level K would claim $14,400 and $10800 worth of DXD.
- 0 %
- 5 %
- 10 %
- 15 %
- 20 %