Skip to main content

Abyss

Abyss Python SDK

Python SDK for token launches, swaps, and lending with web3.py. Import the public package as black_market_sdk. Requires Python 3.10+.

Install

Install the package with python -m pip install black-market-sdk, or use a checkout to run and customize the examples:

git clone https://github.com/abysshopper/black-market-python-sdk.git
cd black-market-python-sdk
python -m venv .venv
. .venv/bin/activate
python -m pip install -e .

Version 0.11.0 adds HMM-aware gas sizing, automatic preparation packing, and bounded simulation-prefix admission with explicit deferred steps. See simulation and recovery.

Version 0.10.0 introduced a breaking HMM V2-only cutover: generic HMM helpers and profile keys now target the newly admitted V2 graph and 512-byte launch tails. default_hmm_launch_config requires explicit max_bid_quote and reference_deviation; other defaults are unchanged. HMM V1 identities, hook enum values and 448-byte tails are no longer supported. See the HMM configuration and owner-controls guide.

Examples

The most complete case is launch_erc20_dividends_multiquote_mixed.py. On Robinhood mainnet (chain 4663), it:

  1. Creates an ERC20 with 1,000,000 initial tokens and holder dividends. Fee-asset allocations split 40% to rewards and 60% to the owner, not a 40% tax.
  2. Splits liquidity across V4/WETH (two positions), V4/USDG (two), and Abyss/WETH (three), priced from the same whole-supply USD valuation (default $5,000).
  3. Funds one opening buy per market with 0.00001 ETH each by default. ETH wraps into WETH; USDG uses an admitted Kyber conversion. ETH for gas is additional.
  4. Prepares and proves the available staged prefix, prints the economic review, and saves artifacts. Buy calibration requires activation outputs to fit the selected RPC's simulation budget. The default dry-run never signs or submits.
  5. With authorization, stages metadata, begins and prepares the markets, then activates all seven positions and three buys together. It verifies chain results and API publication; optional images are verified before submission.

Configure and run

From the checkout root, create .env without overwriting existing configuration:

cp -n examples/.env.example .env
chmod 600 .env

Set LAUNCH_API_URL and exactly one key source: PRIVATE_KEY, or EXAMPLE_KEYSTORE_PATH to an owner-only V3 JSON keystore (EXAMPLE_KEYSTORE_PASSWORD defaults to empty). Optional RPC_URL overrides the official chain4663 RPC. Remote endpoints require HTTPS; existing environment values override .env.

# Dry run: no signing, chain submission, image upload, or publication.
python examples/launch_erc20_dividends_multiquote_mixed.py
# Explicitly authorize spending funds and publishing; no confirmation prompt.
python examples/launch_erc20_dividends_multiquote_mixed.py --broadcast
# After partial execution, replace this path with the ORIGINAL run directory.
python examples/launch_erc20_dividends_multiquote_mixed.py --resume "launch-results/<original-run>"

Dry-run needs live RPC/API access, the creator key, funding, and admission. Review the saved economic-review.json in launch-results/. Broadcast builds a fresh plan; resume may spend/publish but retains the original plan and session. Keep recovery files; never commit or share keys, private artifacts, or signed bytes.

Creating your own

Copy the case wrapper beside its helpers, then customize it:

cp examples/launch_erc20_dividends_multiquote_mixed.py examples/launch_my_token.py
python examples/launch_my_token.py

Edit CASE: unique id, tokenKind (0 ERC20 / 1 ERC404), rewardMode (0 none / 1 staking / 2 dividends), mode (atomic / staged), markets (venue, quote, positions), and buysPerMarket. Supported venues are v4/abyss, quotes WETH/USDG. Customize identity, valuation, and buy input with the EXAMPLE_* keys in .env.example. For supply, fees, budgets, or ranges, adapt construct_plan, fee_policies, and derive_market_pricing in launch_examples.py; copy _launch_support.py with it.

See the launch/API guide, runner configuration, and MIT license for deeper reference.

Metadata

Release files for black-market-sdk 0.11.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 black-market-sdk 0.11.0
File Size Uploaded Provenance Actions
black_market_sdk-0.11.0.tar.gz 501.9 kB With provenance Details for black_market_sdk-0.11.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for black-market-sdk 0.11.0
File Interpreter ABI Platform Actions
black_market_sdk-0.11.0-py3-none-any.whl Python 3 none any Details for black_market_sdk-0.11.0-py3-none-any.whl

Total release size: 702.1 kB

Release files / black_market_sdk-0.11.0.tar.gz

Download URL black_market_sdk-0.11.0.tar.gz
Size 501.9 kB
Tags Source
SHA-256 checksum
How to use checksums
a5eaae681c89ad6c8a0f4cb262d6e5ce971780e29b44bd86a8d99cd1456b6c86
BLAKE2b-256 checksum
How to use checksums
4087dc416abe7882bf59a35f139e56e2bec1a9eb3b1b282de92b0f315120f3ef
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 18, 2026.

Transparency log

Release files / black_market_sdk-0.11.0-py3-none-any.whl

Download URL black_market_sdk-0.11.0-py3-none-any.whl
Size 200.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
96fd729a2f5c3b74ae472b0b478fdc614dd42eb038fcc6805df26c6b7f8122e1
BLAKE2b-256 checksum
How to use checksums
d6b655e2952023ba4710aabf4d97a83cfd77633850eac289b07ae11553778117
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 18, 2026.

Transparency log

Security for black-market-sdk 0.11.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.

Select from 2 files

Attestation for black_market_sdk-0.11.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 18, 2026.

Transparency log

A 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.

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