Replies: 5 comments 3 replies
-
I think it would be useful to define the intended behavior for different severity levels. Some severity levels that deserve definition:
|
Beta Was this translation helpful? Give feedback.
-
If only one more, I recommend “ A confident analysis to show the user”, as the design team is recommending collapsing most to a truncated view by default, since most are useless, and this strikes me as admitting defeat. We need to reserve space for coherence whenever it is available. |
Beta Was this translation helpful? Give feedback.
-
I’d rather we fail to showing too much info than too little, and am concerned that if we have no mechanism to ensure display, we will risk underinforming users. |
Beta Was this translation helpful? Give feedback.
-
I want to take my feature request further: If a snap declares it can provide a confident, authoritative representation of a confirmation, its view should appear at the top of the confirmation, as the primary view to represent it. I can imagine this becoming the default info that is usually shown when interacting with a smart contract. |
Beta Was this translation helpful? Give feedback.
-
We're talking about measuring "% of confident tx representations" as a KR to improve. This snap API could be used as a source of that data. There's an open question as to whether a simulation produces a confident (comprehensive) representation of an action, or merely represents some quantity of side effects. Ideally, a simulation snap would distinguish between which type of result it was providing. |
Beta Was this translation helpful? Give feedback.
-
This thread is meant to be a general place for open discussion concerning the state of SIP-11 (Transaction Insights V2).
The SIP is meant to define an additional
severity
property to the transaction insight return object.Beta Was this translation helpful? Give feedback.
All reactions