Joint L1 Task Force

Q: What is the project goal for Q1?
The goal is to primarily to stabilize the chain, and achieve parity with Luna v2. The final leg of Q1 will be to explore solutions to get listed on TFLs interchain wallet.

Q: Positive/Negative - It is difficult to speculate on positive business outcomes; however, the negative consequences of not performing this work may be a progressively slower and slower network, until the point where archive nodes cannot sync (I do not know how dire this is, we currently still have archive nodes fully synced).

Q: What does the community need to do for the budget, A: nothing at the moment, if this were to pass community spend, given the rate of seigniorage, we would probably still have half the community pool.

Q: who is Till . A: Till is Fragwuerdig and has contributed more recently to the IBCs

@Dannavan_Morrison Q: Who will audit the codes? A: The code will be audited by 3 parties. Notional, this classic team, and a third party (explained below).

Q: Budget for TGF A: TGF has it’s own budget, no need for it here.
Q: No canonical repo: A: this is a further measure of decentralization. There will be no centralized github repo, but rather it will be the onus of the developer group to gain the trust of the validators to accept code via git commit history or code audits
Q: Who will own the blockchain repo, A: all code is open source and thus anyone can be an owner
Q: All code commits, all modifications will be open source. If the team quits, the entire code history is open for everyone to use.
@Guyver44 - community oversight committee. Zaradar formed this so he should be the one to explain. That being said, the admin will liaise with the community.
@arunadaybasu Q: KYC doxxed A: All members are currently doxxed
Q: Legal contract A: There is not legal contract; however, if you see in the distribution of payment, the distribution only happens after milestones are met and approval of oversight +TGF, so there is a reduced risk,
Q. Project budget A: I looked at golang.cafe where 150k is close to the middle, or maybe even low end given the market cap of the chain
Q: Team member leaving, A: yes this makes sense. If anyone chooses to leave, they forfeit their portion and we would immediately search for a replacement. This is only for the next 3 months.
@terraki Q. Leading the Dev team, A: Zaradar and Notional are contracted full-time and would be the leads. The admin is also going to assist as scrum master.
Q. TGF infrastructure, A: Yes this sounds reasonable.
@Marko Q:USTC repeg A: The repeg work is something that can be investigated in parallel. Given the current economic/political climate in the US (and current legislation) I believe it may be best solved by a community member outside the US.
@godoal Q: 50/50 burn tax, community pool. A: More details forthcoming in the next few days.
@Rbb786 Q: Z work, A: Zaradar as full time, he has already quit his other full time job.
Q: Luna and Lunc merge, A: This prop will get us as close to a merge as we can get at the moment, parity with v2, and IBCs to the chain. Interchain wallet will be investigated too.
Q: Distribution of payment. A: the request is at the current exchange rate and “escrowed” for the next 3 months.
@Peter_Sutton Q: antehandler, A: No worries, that will ultimately have to go through another gov vote to get implemented.
Q: Cosmwasm A: We are looking at a dual VM setup where 2 versions of cosmwasm can co-exist at the same time use namespaces. Secret chain did this. That will be explored after Feb. and the upgrade
Q: Enough in CP, A: currently there is and is not dependent of 11111
@Mel1 Q: oversight A: Strath, PFC, DJ Trev, Jagmot, Marco are all overseeing to some degree
@RabbiJebediah Q: drop educational, A: that was just something we did, not something we are asking to be funded to do here
Q: PFC A: Allnodes is already overseeing to some degree, PFC’s political stance is not something considered. His technical knowledge and current oversight of the chain is why he was chosen.
Q: Junior devs A: New information will repurpose this junior budget, see below.


OK sorry if I didn’t mention everyone here (there is limit to 10 on the number of people I can tag), i think there were some overlaps so tried to bundle them. Now to an amendment to the proposal. After posting this proposal, I was contacted by a collaborator in the Cosmos who has 4 years experience running an L1 chain. I have consulted with this person in the past, and can vouch for their motivation to help us. They are willing to assist us, but wish to remain anonymous. They are also willing to help for free, but I would prefer that they be written into the budget. They said that they will make code changes/ audit code/ and contribute to the github and the community can decide on the quality of their work, and choose to pay them after it is done.

In light of this opportunity, I propose to repurpose the junior dev budget of $5k per month, and reduce the computing budget from $6.75k per month to $5.5k per month to budget for another part-time senior developer at $6.25k. The total requested budget does not change. All code commits will be publicly viewable on the github. I personally believe this person is one of the best devs in the cosmos, is massively beneficial to the L1 task force, and I hope that this is an acceptable amendment to the proposal.

23 Likes