Molecule API: Generating and Managing Trading Keys

A trading key is an Ed25519 keypair you generate locally. You register the public key with Molecule, and Molecule uses it to verify that each signed request originated from a process holding the corresponding private key. Ed25519 is used because it produces compact, deterministic 64-byte signatures with strong security properties and fast verification — suitable for the low-latency, high-throughput requirements of trading infrastructure. The private key is never transmitted to Molecule and never stored anywhere outside your own systems.

Key format

The canonical private key format is a base64-encoded 32-byte Ed25519 seed. This is the format you should use when storing keys in environment variables, secrets managers, or configuration files. The SDK also accepts the following alternative representations, all of which resolve to the same 32-byte seed:

Format	Details
Base64 (canonical)	Base64 encoding of the 32-byte seed. This is the recommended storage format.
Hex string	64-character lowercase hex string of the 32-byte seed.
Raw bytes	A `bytes` object of exactly 32 bytes.
64-byte blob	Base64 or `bytes` of the 64-byte `seed \|\| public_key` concatenation — the SDK truncates to the first 32 bytes.

Generate a keypair

Use the nacl library (installed as a dependency of the molecule package) to generate a new keypair and export the seed in canonical format. Register the printed public key hex with Molecule, and store the private seed securely.

from nacl.signing import SigningKey
import base64

key = SigningKey.generate()
private_seed_b64 = base64.b64encode(bytes(key)).decode()
public_key_hex = key.verify_key.encode().hex()

print("Private (seed, base64):", private_seed_b64)
print("Public (hex):", public_key_hex)

The private seed printed above grants full signing authority over any subaccount it is associated with. Never log, transmit, or commit it to version control. Treat it with the same care as a private TLS key or database password.

Loading the key in the SDK

Pass the private seed directly to the Molecule constructor using the private_key parameter, alongside your registered key_id.

import os
from molecule import Molecule

client = Molecule(
    base_url=os.environ["MOLECULE_BASE_URL"],
    key_id=os.environ["MOLECULE_KEY_ID"],
    private_key=os.environ["MOLECULE_PRIVATE_KEY"],  # base64 seed string
)

Using environment variables

The SDK reads the following environment variables if the corresponding constructor parameters are omitted:

Variable	Constructor parameter	Description
`MOLECULE_BASE_URL`	`base_url`	API base URL (required)
`MOLECULE_KEY_ID`	`key_id`	Registered key identifier
`MOLECULE_PRIVATE_KEY`	`private_key`	Ed25519 seed in any accepted format

With all three variables set, you can instantiate the client with no arguments:

from molecule import Molecule

# Reads MOLECULE_BASE_URL, MOLECULE_KEY_ID, MOLECULE_PRIVATE_KEY from environment
client = Molecule()

In containerised or serverless environments, inject secrets at runtime through your orchestration platform’s secrets mechanism (e.g., Kubernetes Secrets, AWS Secrets Manager, HashiCorp Vault) rather than baking them into the container image or source code.

Loading the key from raw bytes at runtime

If your secrets manager returns the key as raw bytes rather than a string, pass them directly:

import os
from molecule import Molecule

# e.g., bytes retrieved from a hardware security module or secrets API
raw_seed: bytes = fetch_key_from_hsm()

client = Molecule(
    base_url=os.environ["MOLECULE_BASE_URL"],
    key_id=os.environ["MOLECULE_KEY_ID"],
    private_key=raw_seed,  # 32-byte bytes object
)

Security best practices

Store keys in environment variables or secrets managers

Never hardcode a private key in source code or configuration files that are committed to version control. Use environment variables for local development and a dedicated secrets manager (AWS Secrets Manager, GCP Secret Manager, HashiCorp Vault, or equivalent) for production workloads. Rotate access to the secrets manager itself through IAM roles rather than long-lived credentials.

Never commit keys to version control

A private key committed to a repository — even a private one, even for a single commit — must be considered compromised. The commit history persists indefinitely. If a key is accidentally committed, rotate it immediately: register a new public key, update your running systems, and revoke the exposed key through the Molecule dashboard.

Use separate keys per trading system

Trading keys are bound to subaccounts. If you operate multiple independent trading systems, register a distinct keypair for each. This limits the blast radius of a compromised key to a single system and gives you a clear audit trail of which system generated each signed request.

Rotate keys on a regular schedule

To rotate a trading key:

Generate a new Ed25519 keypair using the snippet in Key format.
Register the new public key with Molecule through the dashboard.
Update your running systems to use the new key_id and private_key.
Verify that traffic is signing correctly with the new key.
Deregister the old public key.

Avoid gaps in service by completing steps 2–4 before deregistering the old key.

Molecule stores only the public key. Your private seed is never transmitted during registration or at any other point. If you lose the private seed, there is no recovery path — you must generate a new keypair and register the new public key.

Overview

Authentication

Guides

Venues

Security

Molecule API: Generating and Managing Trading Keys

Key format

Generate a keypair

Loading the key in the SDK

Using environment variables

Loading the key from raw bytes at runtime

Security best practices

​Key format

​Generate a keypair

​Loading the key in the SDK

​Using environment variables

​Loading the key from raw bytes at runtime

​Security best practices

Key format

Generate a keypair

Loading the key in the SDK

Using environment variables

Loading the key from raw bytes at runtime

Security best practices