Users seem confused by 'On-chain rejection created' status in the transaction's stepper:
I find it super super confusing, because it looks like I rejected + confirmed. Perhaps some differentiation around confirmation of the tx vs the actual method?
The current UI might lead to think that this transaction has failed and that the rejection happened first before it was confirmed or executed.
The timeline in details looks like a regular timeline.
Overview
Users seem confused by 'On-chain rejection created' status in the transaction's stepper:
The current UI might lead to think that this transaction has failed and that the rejection happened first before it was confirmed or executed.
The timeline in details looks like a regular timeline.
See more insights
Initial feature documentation
Old research docs: https://docs.google.com/document/d/13Z4093m8pugT0MVKcvtmJlGSo4k8w2xfZzCkWngyOhU/edit#
Goals
Allow easier visual representation of the rejection status by keeping the differentiation of the regular and a rejected transactions.
Deliveries