List view

• Post-Mainnet Launch

  Cleanup post launch.

  Due by March 28, 2023
  0% complete0 open0 closed

• Post M2.1 Maintenance (Tech debt)

  No due date

  •5/5 issues closed
  100% complete0 open5 closed

• Pre-Mainnet Launch

  Due by March 10, 2023

  •11/19 issues closed
  57% complete8 open11 closed

• M2.1 (r12) Carbonado.3

  Due by February 10, 2023

  •80/80 issues closed
  100% complete0 open80 closed

• M2.1 (rr11) Carbonado.2

  Due by January 16, 2023

  •46/46 issues closed
  100% complete0 open46 closed

• M2.1 (rr10.5) Grinch

  Due by January 2, 2023

  •1/1 issues closed
  100% complete0 open1 closed

• M2.1 (r9.1) Sapphire patch

  Due by December 8, 2022

  •17/17 issues closed
  100% complete0 open17 closed

• FIPs

  No due date

  •5/5 issues closed
  100% complete0 open5 closed

• M2.1 Audits

  No due date

  •6/6 issues closed
  100% complete0 open6 closed

• M2.1 Lab Week

  No due date
  0% complete0 open0 closed

• M2.1 Testing

  No due date

  •17/17 issues closed
  100% complete0 open17 closed

• M2.1 (rr10) Carbonado.1

  Due by December 20, 2022

  •27/27 issues closed
  100% complete0 open27 closed

• M2.1 (r9) Sapphire

  Due by November 30, 2022

  •15/15 issues closed
  100% complete0 open15 closed

• M2.1 (r8) Topaz

  Due by November 14, 2022

  •18/18 issues closed
  100% complete0 open18 closed

• M2.1 (r5-7) Obsidian/Rhodium/Quartz

  Due by October 11, 2022

  •13/13 issues closed
  100% complete0 open13 closed

• M2.1 (r4) Iron

  Due by September 27, 2022

  •7/7 issues closed
  100% complete0 open7 closed

• M2.1 (r3) Copper

  Due by September 13, 2022

  •11/11 issues closed
  100% complete0 open11 closed

• M2.1 (r2) Selenium

  Due by September 6, 2022

  •7/7 issues closed
  100% complete0 open7 closed

• M2.1 Talc (r1)

  Due by October 19, 2022

  •7/7 issues closed
  100% complete0 open7 closed

• M2.1

  EVM runtime and Ethereum support for the FVM.

  No due date

  •31/31 issues closed
  100% complete0 open31 closed

• M1

  Protocol forks to introduce preparatory changes ahead of user programmability, including gas schedule and architecture adjustments. By the end of this phase, 100% of the network should be running the FVM-backed system actors.

  No due date

  •40/41 issues closed
  97% complete1 open40 closed

• M0

  Canary launch of non-programmable FVM on mainnet, behind a feature flag or fork of the reference implementation (Lotus), running only system actors. Compatible with the existing chain and requiring no protocol upgrade.

  Due by March 15, 2022

  •11/11 issues closed
  100% complete0 open11 closed