Binance SDK
Tribulnation SDK implementation for Binance.
Installation
pip install tribulnation-binance
Public market data
BinanceMarket.new(public=True) discovers spot and usdm. Both serve candles
and tickers; usdm also serves funding history, next funding and perp_stats.
Its bulk snapshots include actively trading perpetuals, not dated futures.
Perp stats combine bulk pricing/funding with a public open-interest request per
market, limited to five concurrent requests. These are separate observations,
not an atomic snapshot. No futures account credentials are required.
Reporting
Reporting is explicitly spot-side: snapshots contain Spot, Funding and Simple Earn balances; history contains spot fills, deposits/withdrawals and Spot ↔ Funding transfers. Futures, margin, options and Portfolio Margin are not inspected or represented as zero balances. No Futures permission or scope configuration is needed. Failures on supported reads propagate instead of becoming empty results. The underlying Typed futures APIs and existing public futures market data are unchanged.
Reporting.history(start=None, end=None) accepts omitted bounds. end defaults
to UTC now. When start is omitted, deposits/withdrawals start 90 days before
end and Spot/Funding transfers six calendar months before it. These are default query horizons, not completeness
guarantees; explicit bounds are preserved and split into legal endpoint windows.
Spot fill history discovers and sweeps the venue's published spot symbols.
No spot_markets or usdm_markets configuration is required or accepted. Spot
fills walk retained trade ids, filtering any supplied time bounds locally.
Discovery does not use current balances or open positions, so closing a position
does not remove its market from the sweep. A full sweep can require many requests.
API history is best-effort. Delisted symbols absent from discovery, venue retention and records beyond an inseparable endpoint cap may leave gaps for file ingestion.
Metadata
Release files for tribulnation-binance 0.5.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_binance-0.5.0.tar.gz | 22.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tribulnation_binance-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 53.9 kB
Release files / tribulnation_binance-0.5.0.tar.gz
| Download URL | tribulnation_binance-0.5.0.tar.gz |
|---|---|
| Size | 22.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
84f44573fba23fb75d57c6dd42c3cacd84f73221fee3833e4308f30344ef7bf4
|
|
BLAKE2b-256 checksum How to use checksums |
ac468404378b22f91fa9572d5bd915ba62dc9c46fb1414712f635a9715341a9e
|
| 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 Sep 29, 2026.
Transparency logRelease files / tribulnation_binance-0.5.0-py3-none-any.whl
| Download URL | tribulnation_binance-0.5.0-py3-none-any.whl |
|---|---|
| Size | 31.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ce392de4a6e8457dea42b5b0db7ca552a5e90d095023ec9f35dd32cd409b571c
|
|
BLAKE2b-256 checksum How to use checksums |
846ab21e264c245b3078db408c15c058f6cb8b0b07cb5768a002a2d10ebefc57
|
| 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 Sep 29, 2026.
Transparency log