Description

💡 DSLA's approach to integrated risk management enables the downside-protected delivery of goods, services and digital assets without intermediaries. Learn more at stacktical.com.

This proposal is for enacting a new Service Level Agreement (SLA), between the DSLA core development team and DSLA community members.

Within the framework of this Service Level Agreement, the DSLA core development team shall commit to the timely release of DSLA-based product until 12/31/2022—and compensate DSLA utility token holders upon failing to deliver a DSLA-based product on time—as per the official roadmap displayed on stacktical.com, the core development team website.

On top of improving DSLA's own SLA compliance capabilities, this proposal acts as research material for a Deadline SLA template for DSLA Protocol.

Abstract

DSLA community members have recently expressed legitimate concerns about the ability of DSLA core developers to deliver DSLA-based products on time, 100% of the time.

At its current maturity level, the DSLA core development team addresses these concerns poorly, especially since the delivery rate of DSLA-based products isn't tracked, communicated—thus cannot be acted on.

Until now, DSLA community members had no recourse against delayed product releases, other than venting out their frustration on the various communication channels at their disposal, or leaving the DSLA community altogether.

Conversely, and on top of the main goal of releasing the product experiencing unfortunate delays, DSLA core development team members are exposed to various adverse effects, as a byproduct of this frustration:

• Developers address issues under aggravated pressure, further leading to human errors and additional delays;

• Marketers end up spending extra time managing expectations instead of building anticipation for upcoming deliveries;

• Deliveries are undermined by fear, uncertainty and doubt, translating into decreased performance at launch and beyond.

GRC—Governance, Risk, and Compliance—is a set of capabilities that helps organizations reliably achieve objectives, address uncertainty and act with integrity.

As a protocol, DSLA is set out to bring GRC to anyone. The goal of this proposal is to bring GRC to the DSLA core development team itself.

Rationale

By committing to being held accountable for failing to deliver a DSLA-based product on time, the DSLA core development team will benefit from increased trust from the DSLA community, and a necessary taste of their own medicine.

This process of using your own products, known as "dogfooding", is a mission-critical step towards ensuring that DSLA Protocol and DSLA-based products are delivering tangible value for end-users, when they need it the most.

Ever since the beginning of DSLA Protocol efforts, our founders have evaluated a series of dogfooding opportunities for the DSLA core development team. Engineering a GRC Automation Middleware—with product-market fit in mind—will require the DSLA core development team to sit at both the provider and user sides of the table.

This Service Level Agreement on product deadlines, dubbed Deadline SLA (for now), is also a perfect chance to accelerate the decentralization of the DSLA Protocol governance, and shed light on this very Snapshot space.

Proposal

This Service Level Agreement applies to the DSLA Metaverse release, tagged v1.5, initially schedule for a March 31st release at dsla.network/metaverse.

Lifecycle

Step 1

Two snapshots of all DSLA token holders will be taken:

• The 1st one on April 13 2022 12:00 CET
• The 2nd one on April 20 2022 12:00 CET

Step 2

The DSLA community will be asked to vote for the proposal during that aforementioned April 13 - April 20 timeframe.

Step 3

Every late day until launch, within the April 13 - April 20 timeframe, 1,473,000.00 (1.473M) DSLA will be pooled by the DSLA core development team, and distributed to voting participants that hold DSLA tokens from the 1st to the 2nd snapshot.

Step 4

Distribution will start on April 21 2022, and end on April 30 2022.

Requirements

• Votes are open, and you have until April 20 12:00 CET to vote.

• You need to hold at least 500K DSLA (~1,473.00 USD) to vote.

• DSLA utility tokens held on a CEX / DEX are not eligible.

• Only DSLA utility tokens will held on Ethereum network will be accounted for.

• The number of DSLA tokens held on the 2nd snapshot must be equivalent or greater than the number of DSLA tokens held on the 1st snapshot.

Distribution

• The compensation payout will use the DSLA utility token to encourage voters to use DSLA Protocol and the DSLA Network application.

• The initial pool size is 14,730,000.00 (14.73M) DSLA (~42,350.00 USD), accounting for 10 days behind schedule.

• The maximum pool size is 29,460,000.00 (29.46M) DSLA, equivalent to 1,473,000.00 (1.473M) DSLA every day from April 13 2022 to April 20 2022 .

This Service Level Agreement terminates upon delivery of the DSLA Metaverse, or on April 20 2022.

Trivia

Why 1473000 DSLA? Because the delivery is 1473 (late in leet).

Discussion

Discuss this proposal on Reddit now.