Ask for the diagram
Four boxes is enough. If they need a novella, they are hiding a custodian or a mess.
If a vendor cannot draw their engine on a napkin, they are selling smoke.
“Engine” sounds like a proprietary turbine in a locked room. Sometimes that is a matching engine. Sometimes it is a Python file with a newsletter. Either way, you deserve a diagram.
OpenFidex’s core loop is dull on purpose: data and models produce context, you produce intent, your wallet produces a signature, a third-party venue produces a fill or it does not. That is the engine. There is no fourth hidden piston where we borrow your coins.
Three moves. None of them hand OpenFidex your funds.
Four boxes is enough. If they need a novella, they are hiding a custodian or a mess.
Only one box should be allowed to spend, and it should have your name on it.
Particle effects are not horsepower. Coverage and a stable signing path are.
The model is an input transformer, not a treasurer.
Your ticket is the only thing the venue should ever see from this stack.
Venues can change. The “you sign” piston should not.
We will not quote fake TPS as if this were a Layer-1 launch video.
Your signed transaction may be. The web UI is not a smart contract you deposit into.
You can originate ideas elsewhere and still sign here. That is a feature of self-custody.
They may change which tools you see. They do not add a house signer.
Because we do not match. Words matter on this page especially.
No. OpenFidex is a non-custodial software interface. A wallet is created in your browser, you keep the keys, and you cryptographically sign every order before it reaches a third-party venue such as Hyperliquid. The software does not take custody of assets and does not submit transactions unless you sign them.
Nearby guides on the same topic — different intent, different copy.
Create an account with your email. You sign every transaction from your own wallet.