Tribulnation SDK
Fully-typed, async Python SDK for crypto trading and data.
Market, Wallet, Earn, and Report are abstract interfaces implemented per exchange and chain. Code written against MarketSDK runs unchanged on dYdX, Hyperliquid, MEXC, or any other supported venue.
Installation
pip install tribulnation-sdk[dydx,hyperliquid,mexc]
See the support matrix for details on extras.
Standalone gateway
Install tribulnation-sdk[gateway] for tn gateway and the remote ProxySDK.
Venue adapters are installed separately on the server. See the
gateway guide
for configuration, supported operations and migration details.
Trading Quick Start
from dotenv import load_dotenv
from tribulnation.sdk import MarketSDK, accounts
load_dotenv() # load credentials from .env file
sdk = MarketSDK(
{
'mexc_account1': accounts.Mexc(
api_key='$MEXC_API_KEY', api_secret='$MEXC_API_SECRET'
),
# 'dydx', 'hyperliquid', and 'mexc' are available by default, even without listing them here
}
)
mexc = await sdk.market('mexc_account1:spot:BTCUSDT')
dydx = await sdk.market('dydx:perp:BTC-USD')
async with mexc.trades_stream() as my_trades:
async for my_trade in my_trades:
print(f'Hedging {my_trade}')
await dydx.place_order(
{
'type': 'LIMIT',
'qty': -my_trade.qty,
'price': my_trade.price,
}
)
accounts.<Venue>() reads credentials from environment variables named after each field (accounts.Mexc() reads $MEXC_API_KEY/$MEXC_API_SECRET) — pass explicit values or other $VAR names to override.
Market IDs & Scoping
<account_id>:<exchange_id>:<market_id>, e.g. mexc_account1:spot:BTCUSDT. account_id is the key you registered in accounts — not necessarily the venue's own name — so you can run several accounts on one venue side by side. Equivalent ways to reach a market:
await sdk.depth('mexc_account1:spot:BTCUSDT')
venue = await sdk.venue('mexc_account1')
await venue.depth('spot:BTCUSDT')
exchange = await venue.exchange('spot')
await exchange.depth('BTCUSDT')
market = await exchange.market('BTCUSDT')
await market.depth()
Hold a Market reference in hot loops; use the scoped one-shot calls otherwise.
Market Interface
- Public data:
depth() -> Bookdepth_stream() -> AsyncContextManager[AsyncIterable[Book]]rules() -> Rules: tick/step size, fees, min/max, rounding helperscandles(interval, start, end) -> PaginatedResponse[Candle]: trade candles opening in[start, end), with timezone-aware bounds and no ordering guarantee;CANDLE_INTERVALSsays which widths a venue serves
- User data:
query_order(id) -> OrderState | Noneopen_orders() -> Sequence[OrderState]trades_history(start, end) -> AsyncIterable[Sequence[Trade]]trades_stream() -> AsyncContextManager[AsyncIterable[Trade]]position() -> Positionavailable_notional() -> Decimal: max. notional you could open now
- Trading:
place_order(order) -> OrderResponseplace_orders(orders) -> Sequence[OrderResponse]cancel_order(id)cancel_orders(ids)cancel_open_orders()
- Perpetual markets:
index() -> Decimalnext_funding() -> FundingRatefunding_rates(start, end=None) -> AsyncIterable[Sequence[FundingRate]]: market-wide rate historyfunding_payments(start, end) -> AsyncIterable[Sequence[FundingPayment]]: your own settled cashflowsperp_position() -> PerpPosition: includes entry price
Full reference: docs/market/index.md, with per-venue notes for dYdX, Hyperliquid, and MEXC.
Mutating methods also take an optional settings dict for venue-specific options, keyed by venue:
await dydx.place_order(
{
'type': 'LIMIT',
'qty': 0.01,
'price': 60_000,
},
settings={'dydx': {'flags': 'SHORT_TERM', 'short_term_gtb': 2}},
)
Other SDKs
Same account-mapping shape as MarketSDK:
WalletSDK: deposit/withdrawal methods — docs/wallet.mdEarnSDK: yield instruments — docs/earn.mdReportSDK: balance/position history, with provenance — docs/report.md
Every SDK object is an async context manager: call methods on it directly, or enter it with async with to close its connections at a point you choose. Details: Async Usage.
Error Handling
All errors subclass Error: NetworkError, ValidationError, ApiError (BadRequest, AuthError, RateLimited, OrderRejected), LogicError.
Context, Logging & Retries
SDK calls are plain by default — no logging, no retries. Wrap them in a Context to add both:
from tribulnation.sdk import Context, NetworkError, RateLimited
ctx = Context().retried(NetworkError, RateLimited, max_retries=5).logged()
with ctx.use():
await sdk.place_order(
'mexc_account1:spot:BTCUSDT', {'type': 'LIMIT', 'qty': 0.01, 'price': 60_000}
)
Retries back off exponentially and only wrap plain async calls, not streams or paginated history. Nested SDK calls each re-apply the active context, so retries can compound across scoping layers. Details: Context, Logging & Retries.
License
1 maintainer
Metadata
1 maintainer
Release files for tribulnation-sdk 2.20.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| tribulnation_sdk-2.20.0.tar.gz | 80.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tribulnation_sdk-2.20.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 186.4 kB
Release files / tribulnation_sdk-2.20.0.tar.gz
| Download URL | tribulnation_sdk-2.20.0.tar.gz |
|---|---|
| Size | 80.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52dafd1a11792c865a22659e6afebc58f16b5665dd8ba72c672e7807dc46dc01
|
|
BLAKE2b-256 checksum How to use checksums |
69881ed85dbb8307d0783ab3b17d3c97d9a22192e06797a09d8e3030f3c4ac24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / tribulnation_sdk-2.20.0-py3-none-any.whl
| Download URL | tribulnation_sdk-2.20.0-py3-none-any.whl |
|---|---|
| Size | 105.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
89824c81c9c7708e8842e473d23cb9116419044a6e5cedb7fa2e2fffa7b39334
|
|
BLAKE2b-256 checksum How to use checksums |
ad3804ca73e7d8085a437bab4801382470b3f7d6be6b91d16f116827ee518ad6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for tribulnation-sdk 2.20.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for tribulnation_sdk-2.20.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
