Smart-account mode in Python mirrors the TypeScript surface exactly. Use it for Python AA-stack integrations, paymaster sponsorship, batched approve+trade flows, or any case where the trading address should be a SimpleAccount derived from an external signer.Documentation Index
Fetch the complete documentation index at: https://docs.kash.bot/llms.txt
Use this file to discover all available pages before exploring further.
Construct the client
BundlerOptions(provider=..., url=..., api_key=...) accepts
alchemy, pimlico, flashbots, or generic. The provider value
is informational; the actual vendor preset is chosen by the consumer
when wiring the client.
Place a trade
userOpHash is what the signer signed — useful for log
correlation across the bundler RPC and the EntryPoint contract.
The transactionHash is the bundler-reported on-chain tx that
contains the UserOp. Both are surfaced because external monitoring
typically wants both views.
First-trade-with-deployment
Same auto-deploy story as the TypeScript SDK: the first UserOp from a fresh SmartAccount carriesfactory + factory_data so
the EntryPoint deploys the account in the same op. The Python SDK
auto-detects the undeployed state and populates these fields; you
don’t pass anything special. Verification gas is ~5x higher on
the deployment op, and the bundler’s gas estimate accounts for
this automatically.
Run the bundled examples
What’s next
EOA quickstart
Vanilla EIP-1559, no bundler.
Hummingbot integration
Full strategy walkthrough.