L1 Task Force Sprint #4 Status Update

The following summary provides a status update for activities for the L1 Task Force from February 20th to March 3rd, 2023.

Q1 Roadmap and Release Milestones

Currently, the L1 Task Force is on-schedule for reaching all Q1 target milestones. Release v1.0.5 and v1.1.0 have been completed successfully. Release v2.0.0 and v2.1.0 are on schedule.

Q1 key releases include: Classic v1.0.5 Hotfix (Completed), Classic v1.1.0 (Binance Whitelist and Burntax Split, Completed), Cosmos SDK Upgrade to v0.45.11, Tendermint upgrade to v0.34.24, and Classic release v2.0.0

Current Status

• All items are currently on schedule and within budget.

Current Issues/Risks

• None

Sprint #4 February 20th to March 3rd
During sprint #4, the L1 Task Force implemented the Binance whitelist functionality, and burntax split, which went live on February 28th. Binance returned to burning Luna Classic immediately following the upgrade. The upgrade to the antehandler provides a method for funding the community pool without the reminting of Luna Classic. Significant work has also been completed on upcoming major milestones for the v2.0.0 release in March, and the Cosmwasm upgrade in early Q2.

Status of Sprint #4 at end of sprint. All in-progress items and in-review items (currently undergoing testing) will be rolled over into sprint #4.

The L1 Sprint #4 project board can be viewed in real-time at GitHub. The L1 Sprint #4 Project Board will be updated this upcoming Monday, following the sprint planning session.

Next sprint: March 6 to March 17th

v1.1.0 After-Action Review and Lessons Learned

• An after-action review is currently being completed, reviewing the steps taken during the upgrade on Feb 28th, to better understand how to improve the process for the next upgrade.
• It is important to note that the L1 team is responsible for the upgrade and testing of layer 1 functionality, and not layer 2 applications. L2 application providers (wallet providers and dApp providers) are responsible for the testing of their application and implementation of pull requests prior to upgrades.

Q1 Budget Forecast and Actuals

• The Q1 implementation is expected to be completed within budget.
• It has been proposed and requested to TGF that the $12.5k monthly budget which was originally allocated to Notional be re-allocated for Vinh and also possibly LuncBurnArmy. This would ensure payment for work as a part-time developer and senior project manager at fair market rates. *These items are currently under review by TGF and may require a small governance proposal as an amendment to the original L1 Joint Task Force governance proposal. This item is awaiting approval.
• A monthly OPEX cost of $108 has been added for Microsoft 365 licensing for all core team members.

Questions or Comments?

If you have any questions or comments with respect to how the development team is progressing, what may be coming up next, or have any other general questions — please do not hesitate to reach out. You can contact myself directly with any questions related to the L1 Task Force on Twitter @LuncBurnArmy, and/or contact the TGF Compliance Officer @DemonMonkey777 on Twitter with any questions related to payments. Also be sure to attend attend the next L1 Task Force monthly AMA’s toward the end of February to speak to the development team directly and ask any questions you may have!