Bitstamp
Bitstamp is planned for Phase 4, 2029, subject to a data agreement with Bitstamp. The plan covers spot pairs in USD, EUR and GBP at every depth from L2 to L4.
What we plan to offer on Bitstamp.
Coverage of Bitstamp begins once a data agreement with Bitstamp is in place, and the final scope follows that agreement.
All spot pairs in USD, EUR, GBP, USDT, USDC and crypto quotes.
Not part of the planned coverage for this venue.
Not applicable: planned coverage is spot only.
Full-depth snapshots and deltas, merged across two regions by venue sequence number.
Every order created, changed and deleted, plus fills, normalized to the shared event types.
L3 plus a participant id, if the data agreement with the venue includes participant-level data.
How we plan to capture Bitstamp.
Once a data agreement with Bitstamp is in place, we capture Bitstamp independently from two regions and merge the two streams by venue sequence number, as we do for every venue. Production capture starts at least 90 days before early access, so depth history covers three months or more on day one.
- Venue type
- Centralized exchange (spot)
- Funding interval
- Not applicable (spot only)
- Integrity
- Venue sequence numbers, and book checksums where the feed includes them, verified at capture
- Snapshots
- A full-depth book snapshot at the top of every UTC hour (the 00:00 snapshot opens each daily file), plus the venue's own snapshots on reconnect, flagged with
is_snapshotandsnapshot_reason - Timestamps
- Microseconds in
ts_exchange.ts_captureis int64 nanoseconds from a PTP-disciplined clock. - Regions
- Two independent regions, assigned once the data agreement is in place
- Participant id
- Offered if the data agreement includes participant-level data
| Market | venue_symbol | symbol |
|---|---|---|
| Spot | btcusd | BTC-USD |
| Spot | btceur | BTC-EUR |
| Spot | ethbtc | ETH-BTC |
Bitstamp uses lowercase concatenated pairs. The split into base and quote comes from the venue's pair reference, stored in instruments. The full rules are in symbology.
- Microsecond venue timestamps are stored in
ts_exchangeas nanoseconds, without rounding. - EUR and GBP pairs are kept as separate instruments from USD pairs.
- Each gap finding is kept in
gaps, wheredetected_bysays which check found it.
Where history starts.
The history available for Bitstamp depends on the agreement with Bitstamp. Data we capture ourselves starts on the first day of production capture, which begins once that agreement is in place.
| Table | Offered | History from | source | Note |
|---|---|---|---|---|
trades | ● | Per agreement | fdc_capture | |
candles | ● | Per agreement | fdc_capture | |
quotes | ● | Per agreement | fdc_capture | |
book_l2 | ● | Per agreement | fdc_capture | |
book_l3 | ● | Per agreement | fdc_capture | |
book_l4 | ● | Per agreement | fdc_capture | If the agreement includes participant-level data |
funding | ○ | · | · | Spot only |
open_interest | ○ | · | · | Spot only |
liquidations | ○ | · | · | Spot only |
mark_index | ○ | · | · | Spot only |
extended | ● | Per agreement | computed from fdc_capture | |
instruments | ● | Per agreement | venue reference data | |
gaps | ● | Per agreement | fdc_capture |
History for Bitstamp follows the agreement with Bitstamp. Gaps that survive the two-region merge are listed in the gaps table and never filled. See data quality.
Derived fields on Bitstamp.
Extended fields are computed on ts_capture and published on a 100 ms grid. A field is available on a venue when its source data is.
Query it.
The same calls work on every venue; only venue and symbol change. Endpoints go live with Phase 1, and the v1 spec is a draft until then.
from fdc import Client
fdc = Client(api_key="fdc_live_...")
# L4 order events with participant ids
book = fdc.book(
venue="bitstamp",
symbol="BTC-USD",
depth="L4",
start="2029-06-04",
end="2029-06-04T01:00:00",
)
df = book.to_polars()curl -H "Authorization: Bearer fdc_live_..." \
"https://api.financedatacloud.com/v1/book/l4?venue=bitstamp&symbol=BTC-USD&start=2029-06-04T00:00:00Z&end=2029-06-04T00:05:00Z"{"op":"subscribe","channel":"book_l4","venue":"bitstamp","symbol":"BTC-USD"}aws s3 cp \
s3://fdc-archive/book_l4/venue=bitstamp/date=2029-06-04/BTC-USD.parquet .Compare with.
Centralized exchange (spot). Planned, subject to a data agreement with Coinbase.
View coverageCentralized exchange. Planned, subject to a data agreement with Kraken.
View coverageCentralized exchange. Planned, subject to a data agreement with Bitfinex.
View coverageShape what ships next.
Pre-registered partners vote on which venues and datasets ship first. Add Bitstamp to your pre-registration to register your interest.
EARLY ACCESS · PRE-SALE PRICINGPre-register for early access → DANIEL GARCIA · CEO & FOUNDERdaniel@financedatacloud.com →