@Dusk_Foundation #dusk
ready to fly higher and higher 🚀
One thing in @Dusk’s W3sper docs really caught my attention, and it wasn’t the signing part.
It was the simple warning that a transaction builder is not a wallet.
W3sper gives apps the tools to connect to Rusk, read state, and build transactions. But if you want an app to sign without a wallet extension, you also take on some serious responsibilities yourself.
You need secure key storage, recovery, and a properly synced Bookkeeper with the latest balance and nonce.
Just creating a new profile isn’t enough. You can have the identity and still be missing the current state needed to build a valid transaction.
That’s the part I almost overlooked.
Signing tells you which key approved the transaction.
State synchronization tells you what that key can actually do right now.
I like that W3sper keeps that boundary clear instead of trying to quietly become a wallet.
But it does make me wonder:
Does this separation make W3sper better infrastructure, or does it make it easier for developers to build custom signers without realizing how much responsibility they’ve taken on?
$TUT $DUSK
$CLO
ready to fly higher and higher 🚀
One thing in @Dusk’s W3sper docs really caught my attention, and it wasn’t the signing part.
It was the simple warning that a transaction builder is not a wallet.
W3sper gives apps the tools to connect to Rusk, read state, and build transactions. But if you want an app to sign without a wallet extension, you also take on some serious responsibilities yourself.
You need secure key storage, recovery, and a properly synced Bookkeeper with the latest balance and nonce.
Just creating a new profile isn’t enough. You can have the identity and still be missing the current state needed to build a valid transaction.
That’s the part I almost overlooked.
Signing tells you which key approved the transaction.
State synchronization tells you what that key can actually do right now.
I like that W3sper keeps that boundary clear instead of trying to quietly become a wallet.
But it does make me wonder:
Does this separation make W3sper better infrastructure, or does it make it easier for developers to build custom signers without realizing how much responsibility they’ve taken on?
$TUT $DUSK
$CLO