The interface must reveal where execution authority resides
For a dYdX-style request, we select an independently scoped architecture rather than assuming one protocol design. The interface explains wallet actions, execution states and the source of position data. Contract, network and operator responsibilities are documented so decentralisation is not used as a vague assurance.
Architecture choice
Define which components are on-chain or operated services.
Data freshness
Expose delayed indexing rather than showing stale state as final.
Where it fits
Practical Use Cases
01
Protocol-connected interfaces
Build a distinct client for approved trading infrastructure.