Skip to main content

Aster SDK

Spot and linear perpetual Market support for Aster, built on typed-aster. Install with pip install tribulnation-aster.

from tribulnation.aster import AsterMarket

async with AsterMarket.new(public=True) as venue:
  market = await venue.perp.market('BTCUSDT')
  book = await market.depth(levels=5)

Authenticated use needs the main wallet's address (user) and the private key of a trading agent registered for it (signer). The main wallet's own key is never needed:

venue = AsterMarket.new(user='0x…', signer='0x…', mainnet=False)
  1. Exchanges are spot and perp, with native symbols such as BTCUSDT.
  2. Public data: discovery, tickers, rules, REST depth (up to 1000 levels), shared depth streams (up to 20 levels), candles in the six SDK intervals, perpetual index, next funding, funding-rate history and bulk perp_stats (without open interest).
  3. Account and trading: fees, order queries, open orders, fill streams, perpetual trade history, MARKET, LIMIT (GTC) and POST_ONLY (GTX) orders, and all cancellation methods. Market orders ignore the SDK price. Perpetual position and collateral cover one-way, cross-margin accounts. These are verified on testnet only. Perpetual funding payments are available per market or exchange-wide, with positive amounts paid, and are verified on mainnet.
  4. Unsupported methods raise NotImplementedError: spot balances, spot trade history, available_notional and perp_collateral.
  5. tribulnation.aster.Report snapshots, through ReportSDK, the mainnet perp wallet (without unrealized PnL) and positions with their entry prices, the spot wallet, and ASTER staked on Aster Chain with its unclaimed rewards, signed by the trading agent. Testnet snapshots are unsupported. Its history() streams perpetual income and spot transactions as unclassified cash deltas, verified on testnet only.

See Aster Market for account configuration through MarketSDK.

Funding payment signs

Since 0.5.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.

Metadata

Release files for tribulnation-aster 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tribulnation-aster 0.5.0
File Size Uploaded
tribulnation_aster-0.5.0.tar.gz 18.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for tribulnation-aster 0.5.0
File Interpreter ABI Platform
tribulnation_aster-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 40.6 kB

Release files / tribulnation_aster-0.5.0.tar.gz

Download URL tribulnation_aster-0.5.0.tar.gz
Size 18.9 kB
Tags Source
SHA-256 checksum
How to use checksums
097bd8204544b7e357d39798890520230785b0929c7e1326ef6ed4d528aa5edb
BLAKE2b-256 checksum
How to use checksums
52f561feb041a01edb4fb065222307c2e71720d16ed8b07a29a0f8712c763792
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

Release files / tribulnation_aster-0.5.0-py3-none-any.whl

Download URL tribulnation_aster-0.5.0-py3-none-any.whl
Size 21.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e4b0200dcb1a7ceaa034035c144a84a2ac00b275dc95e6ac90f84629381ca8d1
BLAKE2b-256 checksum
How to use checksums
0a131b99ea6cda53592251098bf40748833e7ca963f6a4b2406216f027d79c09
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

Release history Release notifications | RSS feed

0.9.0

2 release files

0.8.0

2 release files

0.7.0

2 release files

0.6.0

2 release files

This release

0.5.0 This release

2 release files

0.4.2

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page