Clarify which data comes from the Blockchain and which doesn’t.
Clarify the address of the contract(s)
Link all Blockchain data to independent Blockchain explorers.
Clarify which data comes from oracles.
Use expandable references:
Make a hover state for Blockchain data points, you can provide a contextual expanded tooltip with more information
Clearly show which links open the external Blockchain explorer.
Manage styling conflicts with link icons: If a data point is both a “Blockchain datapoint” and a link then:
1. Add a link-icon: that follows any Blockchain datapoint.
2. Open expandable reference and insert secondary link.
On the hover state, the data can be temporarily styled like a filter. The filter should help the user see which data is a Blockchain datapoint.
Exposed data should actionable.
If the exposed data is not directly actionable it should be trust-building and/or educational.
Clarify the address of the contracts.
Use expandable references.
Manage styling conflicts with link icons.
Using color, font, and shape to clearly distinguish Blockchain data.
Use a side panel (Chain View).
For data-intensive interfaces like Decentralized Exchanges or market views following the previous suggestions would probably mean styling the majority of the interface, probably adding more confusion. To solve this you can envisage a “Chain-view” button that when hovered or clicked, temporarily styles the data. It’s like putting a filter over the page, a filter that helps the user see which data is a Blockchain datapoint.
