Ran the default flow on Dusk Foundation this week instead of the advanced settings, just to see what a first-timer actually gets… and it's not what I expected. Rusk-wallet has fully moved off the old HTTP API onto RUES now, per Dusk's own engineering notes — the "previous HTTP client" is basically retired. Fine change technically. But it means the default wallet path you land on today isn't the one most of the older guides and screenshots still floating around describe.
That's the thing that stuck. Not a flaw exactly, just a gap between what gets shown as "how Dusk works" and what the wallet actually hands you the moment you open it fresh. Default transaction type, default client, default expectations — all quietly shifted underneath while the public narrative stayed the same.
Had to stop and double check I wasn't on a stale build, actually. Wasted ten minutes assuming the friction was on my end before realizing the rails themselves had moved.
Doesn't feel malicious, just… fast-moving infra outpacing the default onboarding story people still repeat.
Makes me wonder how many people are following month-old walkthroughs against a chain that's already changed its own defaults underneath them.
$DUSK #dusk @Dusk
That's the thing that stuck. Not a flaw exactly, just a gap between what gets shown as "how Dusk works" and what the wallet actually hands you the moment you open it fresh. Default transaction type, default client, default expectations — all quietly shifted underneath while the public narrative stayed the same.
Had to stop and double check I wasn't on a stale build, actually. Wasted ten minutes assuming the friction was on my end before realizing the rails themselves had moved.
Doesn't feel malicious, just… fast-moving infra outpacing the default onboarding story people still repeat.
Makes me wonder how many people are following month-old walkthroughs against a chain that's already changed its own defaults underneath them.
$DUSK #dusk @Dusk