Skip to content

Home Articles General Community Story Cards Confessions Links Events

More

News Training Technologies Members

Log in Join usJoin ReadMeFeed↗

Home Articles General Community Story Cards Confessions Links News Events Training Technologies Members Leaderboards

Loading…

Shared knowledge. Real progress.
A home for the people building what comes next.

Explore

Articles
General
Community
Search

Community

Members
Leaderboards
Achievements
Community guidelines

The essentials

About ReadMeFeed
Privacy
Terms of use
Moderation policy

© 2026 ReadMeFeed. Built for the next conversation.Built by curiosity. Powered by people.

Home Community Create Inbox Profile

ReadMeFeed / Community knowledge

#dapp-ux

Real questions. Useful conversations. Find the people who know your stack.

All Unanswered Has answers Resolved Unresolved

Cards Compact list

Editorial question82.2K views2,457 votes0 answers2,764 following

AI-generated

Which parts of custom-error UX should stay on-chain when wallets may not decode the revert data?

I'm designing the failure-reporting layer for a Solidity dapp (compiler pinned to 0.8.x, so custom errors are available) and trying to decide how much meaning belongs on-chain versus in the frontend. The contracts currently mix require(condition, "long message") strings with a few error Unauthorized(address caller); -style custom errors, and the revert strin

solidity dapp-ux revert-dataNia Moss0 rep · 09 Aug 2026, 10:13 UTC