search

Stacktical / stacktical-dsla-residency

Welcome to the DSLA Residency, the DAO testbed of DSLA Protocol!
0 stars 0 forks source link

Infographic - Risk Management, Legacy vs. DSLA #5

Closed darrylhansen closed 2 years ago

darrylhansen commented 2 years ago

The Issue

Create an infographic overview showing the differences in how 3rd party risk is managed in the legacy system vs. using DSLA Protocol risk management middleware

Git Issue format

Infographic

About DSLA protocol

DSLA Protocol is a smart-contract based application and network middleware for managing risk. It allows developers to plug risk management capabilities into their applications and uses incentives to align the goals of different stakeholders.

Prize Bounty

The prize bounty for this task is 50000 DSLA.

Challenge Description

This infographic should show the contrast between two ways of managing 3rd party risk - one using legacy SLAs and one using DSLA Protocol middleware. The salient points to cover for this infographic are:

  1. Managing 3rd Party risk using the legacy system:
    1. Offline agreements
    2. Agreements are executed through one or more intermediaries
    3. Unverifiable guarantees - no way to confirm a providers claimed performance
    4. Not capital efficient
    5. Non-negotiable commissions - providers that charge commissions earn them regardless of Quality of Service
    6. Convoluted, time-consuming claims process (if claims are even possible and not just at the discretion of the Provider)
  2. Managing 3rd Party risk using DSLA Protocol:
    1. Agreements are online and live
    2. Decentralized, direct, programmable agreements
    3. Service levels are based on measurable parameters which are monitored, confirmed and immutably stored
    4. Capital efficient. Staked capital can earn a return while backstopping a live DSLA contract
    5. Quality of Service failures entitle users to a compensation, while meeting Quality of Service targets entitle service providers to a reward
    6. Compensation and/or rewards are automatically enabled and instantly available based on service performance.

The infographic should show how an SLA would be established using the legacy system vs. DSLA Protocol. It should illustrate the pitfalls, inefficiencies, bottlenecks and user risks associated with a traditional SLA. Contrasting with the very clean and efficient flow of establishing an SLA using DSLA Protocol.

General Branding Guidelines

Follow the branding guidelines available in our gitbook: https://readme.stacktical.com/dsla-network/media-and-branding-guidelines

How to participate?

Step 1: Pick a task

Browse Github issues and raise your hand 🙋‍♂️ in the comments section to show interest.

Step 2: Contact us

Email founders+residency@stacktical.com] with:

Your Github username

An introduction about yourself

A link to the task of your choice

An outline of your plan to complete it

Include some prior similar works as a reference, if applicable

Step 3: Onboarding

If you are selected for the task, the core team will allocate resources to facilitate its completion.

Some tasks might require signing a Non Disclosure Agreement (NDA).

Step 4: Complete your task

Some marketing or content related tasks may require review and updates before being accepted.

Congratulations on contributing to DSLA! 🎉

Completed tasks will be reflected in this repository.

Judging Criteria

  1. Quality: Overall quality of submission.

Follow DSLA Protocol

DSLA Residency Github https://github.com/Stacktical/stacktical-dsla-residency DSLA DTK Github https://github.com/Stacktical/stacktical-dsla-developer-toolkit DSLA Protocol Developer Guide https://readme.stacktical.com/developer-guide/ DSLA Protocol Discord (for technical discussions) https://discord.gg/bknuhcXV DSLA Support Telegram https://t.me/dsla_network DSLA Protocol Community Telegram https://t.me/stacktical

darrylhansen commented 2 years ago

Replaced with DSLA Residency Challenge on Dework