User wallet
The connected user wallet identifies the account, provides explicit signatures where required and remains responsible for the funds and market exposure associated with the selected workflow.
Stryx Learn / permissions
Executor wallets and delegated trading permissions
Some supported trading workflows separate the user wallet that controls funds and grants authority from an executor wallet or signer that submits approved venue actions. The exact model, scope and funding path depend on the selected service.
User wallet and executor roles
Executor wallet or signer
Where supported, a separate execution identity can submit actions within authority accepted by the venue or contract flow. It does not make the workflow universally custodial or non-custodial; inspect the actual route.
Connection is not authorization
Connect
Connecting exposes an address and selected network to the interface. It does not by itself approve trading, transfers or automated instructions.
Approve or sign
A supported workflow may require a wallet signature, venue authorization, contract approval or stored start approval. Read the presented scope before confirming.
Activate
Only after service readiness, required funding and applicable authorization should a runtime be able to submit its configured actions.
Scope and lifecycle
Understand the scope
Check which account, venue, contract, market, action type and spending or trading authority the workflow can reach. Do not infer restrictions that are not visible in the approval.
Monitor state
Compare the application’s runtime state with live venue orders, positions and balances. Authorization can remain while a service is paused or offline, depending on the implementation.
Stop, replace or revoke
Stopping a runtime, replacing an executor and revoking an approval are distinct operations where those controls exist. Confirm the applicable venue or contract state instead of assuming one action performs all three.
Funding and operational security
Fund only the required path
Some workflows require collateral, gas, or a balance associated with an execution wallet; others use the user’s venue account. Too little can block execution, while excess exposure can increase operational loss.
Protect every authorized component
Secure wallet devices, recovery material, API credentials and executor keys. Review unexpected signatures, stale sessions, changed addresses and permissions before resuming a service.
Limits of delegated execution
Delegation can separate repetitive execution from direct user interaction, but it does not validate a strategy, guarantee an order, eliminate smart-contract or venue risk, or remove the user’s market exposure. Service outages, stale data, rejected orders, compromised authority and configuration mistakes can still produce loss.
Pre-activation checklist
Identity
Verify the connected user address, selected network, execution identity and destination venue or contract.
Authority
Review every signature and approval, its visible scope, and the available method for stopping or changing it.
Recovery
Know how to inspect open orders and positions manually if the interface or runtime becomes unavailable.