#dusk $DUSK @Dusk bought $ZEC at 365 now look it break its all time high 300 + profit patience always pays off
$POL is about to short fuel ended now
i keep thinking about how much wallet friction gets blamed on blockchains when sometimes its just discovery.
The interesting part of Dusk Connect isnt really the connect button. Its that a dApp can discover multiple compatible wallet providers, expose them to the user, and let the user choose instead of hardcoding one extension into the application.
That sounds minor. It isnt.
The old single-provider assumption gets messy once several wallets exist in the same browser. EIP-6963-style discovery tackles that general problem by letting providers announce themselves instead of competing to be the one object a dApp happens to find. Dusk Connect is aiming at the same practical outcome on Dusk: discover whats available first, select second, request access after.
i like the separation. What im less convinced about is whether discovery alone removes the real friction. The application still has to react correctly when the selected provider, profile, authorization or network changes after connection.
Thats where clean standards usually meet messy user behavior.
So does multi-wallet discovery actually solve the connection problem, or does it just move the difficult part from finding a wallet to managing its state correctly??
@Dusk #dusk
$POL is about to short fuel ended now
i keep thinking about how much wallet friction gets blamed on blockchains when sometimes its just discovery.
The interesting part of Dusk Connect isnt really the connect button. Its that a dApp can discover multiple compatible wallet providers, expose them to the user, and let the user choose instead of hardcoding one extension into the application.
That sounds minor. It isnt.
The old single-provider assumption gets messy once several wallets exist in the same browser. EIP-6963-style discovery tackles that general problem by letting providers announce themselves instead of competing to be the one object a dApp happens to find. Dusk Connect is aiming at the same practical outcome on Dusk: discover whats available first, select second, request access after.
i like the separation. What im less convinced about is whether discovery alone removes the real friction. The application still has to react correctly when the selected provider, profile, authorization or network changes after connection.
Thats where clean standards usually meet messy user behavior.
So does multi-wallet discovery actually solve the connection problem, or does it just move the difficult part from finding a wallet to managing its state correctly??
@Dusk #dusk
