List view
- No due date•10/18 issues closed
- No due date•5/6 issues closed
The debt accounting process needs to be able to handle both writing off bad debt and forgiving debt, which impact reward distributions to network contributors. This milestone does not capture any work around repercussions of users not paying this debt (e.g. disconnecting or banning from the DoubleZero network).
No due date•13/26 issues closed- No due date•4/8 issues closed
Ottersec has performed their security audit of the Serviceability smart contract. This project will track all of their findings.
No due date•9/39 issues closedCollect issues around alerting success and errors for debt and rewards calculations by their respective accountants.
No due date•3/3 issues closedImprovements to existing commands or adding new commands for the v0.3 release.
No due date•6/6 issues closed- No due date•0/2 issues closed
Current Activator (v1) has resiliency issues, where it is fragile to make changes to the existing codebase. And building tests around the existing codebase is probably more work than it is worth. We aim to achieve the goal of phasing out Activator v1 in favor of v2.
No due date•4/29 issues closedTracking tasks related to doublezero-topology
No due date•0/4 issues closed- No due date•39/40 issues closed
- Overdue by 1 month(s)•Due by November 21, 2025•0/1 issues closed
- Due by February 16, 2026•12/35 issues closed
- Overdue by 4 day(s)•Due by December 31, 2025•33/36 issues closed
- No due date•5/5 issues closed
- No due date•12/16 issues closed
- No due date•21/27 issues closed
- No due date
- No due date•0/1 issues closed
- No due date•1/13 issues closed
- No due date•24/38 issues closed
- No due date•14/17 issues closed
- No due date•48/65 issues closed
- No due date•116/137 issues closed
- No due date•12/21 issues closed
- No due date•26/44 issues closed
- No due date•268/293 issues closed
- No due date•3/3 issues closed
As a network contributor I need to know how to interact with DZF and the other contributors during outage events so that we can restore service to the network and communicate to the users
Overdue by 4 month(s)•Due by August 31, 2025•1/1 issues closedAs a network contributor I want to ensure that my internet-facing DZDs have sufficient protections in place to mitigate DDoS, malicious users, etc.
Overdue by 4 month(s)•Due by August 31, 2025•3/4 issues closedAs a protocol I need to support rate limiting users by various criteria so that we can protect the physical network
Overdue by 5 month(s)•Due by July 31, 2025•0/1 issues closedAs a protocol, I need to research and decide on a DZX mode in each metro areas .
Overdue by 5 month(s)•Due by July 31, 2025As a protocol I need sufficient mainnet network bandwidth where Solana stake is concentrated to feel comfortable launching mainnet
Overdue by 4 month(s)•Due by August 29, 2025•11/15 issues closedAs a DZ community member I need a public facing dashboard to demonstrate the historical and current state of the DZ network so that I can choose to revert to the public internet if DZ is not performing
Overdue by 8 month(s)•Due by May 9, 2025•1/1 issues closedAs a DZ user, I need a mechanism to express my interest in sending and recieving multicast over the network so that I can benefit from multicast
Overdue by 7 month(s)•Due by May 17, 2025•45/48 issues closed