dYdX SDK
Tribulnation SDK implementation for dYdX.
Installation
pip install tribulnation-dydx
Ticker availability
tickers() reports actual bid/ask prices and quantities when depth enrichment is
enabled. Its last is None: the market catalogue only publishes an oracle price,
which is not the last traded price. base_volume_24h is also None because the
catalogue's volume24H is quote-denominated turnover. No approximate conversion or
per-market trade-history sweep is performed. Use perp_stats().index for the oracle
price and candles() for historical trade prices and base volumes.
Reporting cost basis
Report.snapshot() returns the native Snapshots.snapshot() record. Each perpetual
subaccount pairs collateral (equity - unrealizedPnl) with the venue's signed sizes
and entry prices from the same indexer response. At the corresponding marks,
collateral plus sum(size * (mark - entry_price)) preserves venue equity. Snapshot
reads do not fetch or replay fills, so fill coverage and fill/snapshot timing
mismatches cannot introduce a separate cash adjustment.
History still replays chronological fills using average-cost accounting to compute realized P&L, retaining the remaining entry basis on partial closes and resetting it on position flips. This reconstructed basis can differ from the venue's snapshot basis. Consumers must not assume that history's realized P&L and snapshot cash share one reconstructed basis. Any reconciliation must adjust both collateral and position entry prices consistently and first establish matching holdings and capture times.
Version 0.7.1 restores native snapshot delegation to fix the equity distortion in 0.7.0 (issue #39). This correction applies to newly fetched snapshots; downstream dependency rollout and correction of stored snapshots are separate work.
Funding payment signs
Since 0.11.0, funding payments are positive when received and negative when paid, for every supported history scope. Requires SDK >=2.10.0. Funding rates keep their existing signs. See migration notes before upgrading.
1 maintainer
Metadata
1 maintainer
Release files for tribulnation-dydx 0.11.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 | |
|---|---|---|---|
| tribulnation_dydx-0.11.0.tar.gz | 37.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tribulnation_dydx-0.11.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 86.0 kB
Release files / tribulnation_dydx-0.11.0.tar.gz
| Download URL | tribulnation_dydx-0.11.0.tar.gz |
|---|---|
| Size | 37.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79ad52222f008bdb24ce3369a35b3d1d4becde174f5fbbad5a4104b8f003a2e1
|
|
BLAKE2b-256 checksum How to use checksums |
3a639d28256296d0fa0af91fd0d4ba555f23118bd60b586f37372f16423f911f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 5, 2026.
Transparency logRelease files / tribulnation_dydx-0.11.0-py3-none-any.whl
| Download URL | tribulnation_dydx-0.11.0-py3-none-any.whl |
|---|---|
| Size | 48.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8b731b528ddc1a773ac5eca987d15b762f206df5852a4254442a40fbbd7af04
|
|
BLAKE2b-256 checksum How to use checksums |
8ede1aa876a7040a909b61426d4c2af95cfc526c56e7caa5039669f3e58d3f57
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 5, 2026.
Transparency log
