Crypto Derivative Markets
crypto-derivative-markets is a zero-runtime-dependency Python library for venue-neutral
crypto-derivative economics. Install the distribution from PyPI and import the cdm namespace:
python -m pip install crypto-derivative-markets
The package supplies:
- versioned JSON Schemas and immutable Python values;
- incomplete instrument descriptors with capability-specific assessment;
- amount-independent instrument scenario keys;
- optional protocol-scoped native identity references with ambiguity-safe selection;
- payoff and maturity classification;
- canonical market-datapoint meanings and ordered calculation lineage;
- context-independent open-interest conversions with exact ratios, structured missing inputs, and explicit unmodeled outcomes;
- funding-rate and interval semantics that preserve missing source evidence;
- deterministic JSON codecs and portable conformance vectors.
It intentionally contains no provider adapters, provider-specific identity definitions or mappings, catalog identifiers, network access, configuration, persistence, scheduling, or service policy. Opaque native values may be carried through the typed identity-reference contract but are never interpreted as economic evidence.
Quick start
from cdm import (
AssetRelationship,
ContractValueDescriptorV1,
ContractValueUnit,
InstrumentCapability,
InstrumentDescriptorV1,
InstrumentKind,
SettlementDescriptorV1,
assess_instrument_descriptor,
instrument_scenario,
)
descriptor = InstrumentDescriptorV1(
instrument_kind=InstrumentKind.PERPETUAL_SWAP,
contract_value=ContractValueDescriptorV1(unit=ContractValueUnit.BASE),
settlement=SettlementDescriptorV1(asset_relationship=AssetRelationship.QUOTE),
)
assessment = assess_instrument_descriptor(
descriptor,
InstrumentCapability.CLASSIFICATION,
)
scenario = instrument_scenario(descriptor)
Classification succeeds without contract amount, settlement method, margin, or funding metadata because those attributes do not affect payoff or maturity. A conversion assessment can require a different minimal set from the same descriptor.
Contracts and documentation
- Normative requirements
- Antora documentation component
- Versioned schemas
- Conformance vectors
- Compatibility policy
- Contribution guide
The project is in an initial public-contract release. Schema identifiers are versioned independently from the Python distribution and are never inferred during decoding.
Metadata
Release files for crypto-derivative-markets 0.1.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 | |
|---|---|---|---|
| crypto_derivative_markets-0.1.0.tar.gz | 49.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| crypto_derivative_markets-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 92.8 kB
Release files / crypto_derivative_markets-0.1.0.tar.gz
| Download URL | crypto_derivative_markets-0.1.0.tar.gz |
|---|---|
| Size | 49.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6f9ffa5db9298507126918f0db6d42ff488f5af0b0b0e8c27db65f72545100ef
|
|
BLAKE2b-256 checksum How to use checksums |
fd73f064fc49ba96e7029a1aec858dfd16cce629b3b05b7c24a0b6c2d28c8c10
|
| 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 Aug 9, 2026.
Transparency logRelease files / crypto_derivative_markets-0.1.0-py3-none-any.whl
| Download URL | crypto_derivative_markets-0.1.0-py3-none-any.whl |
|---|---|
| Size | 43.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
916ccf4c1182b1f6be820123d4e69f410826093714857cf4256d1187001c82cc
|
|
BLAKE2b-256 checksum How to use checksums |
46c8aa40c7e72ab087fd8c96439d6f188bcc340ff8a0d2105974789cabc27487
|
| 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 Aug 9, 2026.
Transparency log