search

stacksgov / sips

Community-submitted Stacks Improvement Proposals (SIPs)
132 stars 80 forks source link

Sip 026 - Clarity DeFi Vault SIP #153

Open AcrossfireX opened 1 year ago

AcrossfireX commented 1 year ago

Here is the initial draft of SIP-026 for Clarity Defi Vaults. After initial review by SIP editors we have the following RICE score.

% of network affected: 90% Reach: 150,000 Impact: 2 Confidence: 80% Effort: 2 RICE Score: 120,000

This scoring can change with additional information as its available.

AcrossfireX commented 1 year ago

@FriendsFerdinand - FYI

FriendsFerdinand commented 1 year ago

The main reasoning behind this proposal is for explorers and other APIs to have standardized access to the information to vault state that is stored in a single Clarity contract.

AcrossfireX commented 11 months ago

SIP has been updated to Accepted by SIP Editors

wileyj commented 11 months ago

I'm curious why the word "explorer" is used several times throughout the SIP. It leads me to believe the end goal here is to both:

  1. add new vault trait
  2. display this trait in an explorer/api

But, it's a bit unclear how the explorer would do this as it pertains to the SIP. I think if the goal here is to add a new trait, language around how the explorer may use this should be more generic (ex: stacks explorers would then have the ability to display xyz in an easily digested manner). with the current wording, it makes it seem like changes to teh explorer/api would be necessary as part of this SIP.