Useful technology emerges from clear decisions about context, responsibility and the way people work. Three considerations for web3.
Explain intent before signing
Show the relevant asset, network, destination and permissions before asking a user to sign. The interface should make the action understandable in the context of the product.
Design for waiting
Wallet rejection, pending submission and network confirmation are distinct states. Give users a clear account of what is known and avoid encouraging duplicate submissions.
Reconcile the result
The application view and the network view can diverge temporarily. Build a reconciliation path and present the source of status information clearly.
Start with a workflow you can understand, observe and improve.
These are general design considerations. Implementation depends on the system, users and operational requirements.
Discuss your context