As dApps expand across both Ethereum rollups and high-throughput chains like Solana, handling user identity becomes a messy architectural bottleneck:
EVM relies on EIP-4361 (Sign-In with Ethereum).
Solana typically falls back on arbitrary text signing or ad-hoc custom hooks.
Backends end up managing two different session models, double cookie layers, and custom token verifications.
To eliminate this fragmentation, we implemented the open standard CAIP-122 (Sign-In with X) and released @tuwaio/siwx an open-source, modular auth toolkit that gives developers a unified identity pipeline across EVM and Solana with zero vendor lock-in.
Most Web3 frontends still treat blockchain interactions like standard HTTP requests: fire an RPC call, trigger setIsLoading(true), and pray the user stays on the page until a receipt returns.
In reality, blockchains are asynchronous, distributed state machines. The moment you hit real-world network conditions, naive useState bindings collapse across several critical failure modes:
Component Unmounts: Route transitions kill the promise listener and destroy local component state, leaving users in the dark.
The Speed-Up Trap: When users speed up transactions in MetaMask, the wallet reuses the nonce with a new hash. Naive frontends await the orphaned hash indefinitely.
Browser Reload Amnesia: Ephemeral RAM memory wipes tracking on page refreshes while the transaction is still pending in the mempool.
Multi-Tab Desynchronization: Interactions initiated in one tab are completely invisible to others.
When building Web3 infrastructure or apps, testing webhooks locally usually breaks the flow.
You find yourself setting up third-party tunnels (ngrok, cloudflared), copying temp URLs into dashboards, and constantly restarting everything when sessions expire.
To eliminate this friction in Quasar, we just added native Local Dev Relay:
