I noticed a small but very useful detail in @Dusk_Foundation ’s node interface documentation for wallets and exchanges: node responses include a Rusk-Version, and clients can also tell the node which versions they accept. If Rusk-Version-Strict is included, the node will immediately reject the request when the versions don’t match.
Many people see an old interface still working and think “compatibility” means it will work forever. But the documentation also lists three old shortcut routes that are deprecated and will be removed in the future.
I see this in two parts.
The first is version checking. A client doesn’t have to wait for the interface to change and then discover a problem. It can tell the node in advance which Rusk version it accepts. Strict checking is useful because it is better to clearly reject a request than let an old client receive data it may understand incorrectly.
The second is route migration. New integrations should use /graphql for chain, block, transaction, mempool, and archive queries. Contract methods should move to /on/contracts/.... The old routes are only for the transition period.
This matters to normal users too. Exchange deposits, wallet balances, and browser history all depend on clients correctly understanding node data.
For $DUSK, I think maturity is not just about keeping the chain online. It also means wallets, exchanges, and indexers keeping up with interface changes.
The real question is: will mainstream clients migrate before the old routes are removed, or only after users start seeing failures?
#dusk $DUSK
Many people see an old interface still working and think “compatibility” means it will work forever. But the documentation also lists three old shortcut routes that are deprecated and will be removed in the future.
I see this in two parts.
The first is version checking. A client doesn’t have to wait for the interface to change and then discover a problem. It can tell the node in advance which Rusk version it accepts. Strict checking is useful because it is better to clearly reject a request than let an old client receive data it may understand incorrectly.
The second is route migration. New integrations should use /graphql for chain, block, transaction, mempool, and archive queries. Contract methods should move to /on/contracts/.... The old routes are only for the transition period.
This matters to normal users too. Exchange deposits, wallet balances, and browser history all depend on clients correctly understanding node data.
For $DUSK, I think maturity is not just about keeping the chain online. It also means wallets, exchanges, and indexers keeping up with interface changes.
The real question is: will mainstream clients migrate before the old routes are removed, or only after users start seeing failures?
#dusk $DUSK