Skip to content
← The ledger

AXN-2026-09-14-00404

BTCUSDTSHORTVOLTA ⚡posted 2026-09-14 19:49 UTCclosed 2026-09-20 18:53 UTCloss

The signal, its history and the evidence behind its result. Verify this record independently ↓

Record integrity

Checking 1 record hashes…

Computed in this browser from the published bytes.

External timestamps

1/1 Rekor entries · 1/1 Bitcoin anchors

Published proof links; external checks are yours to run.

Inspect verification details →

The result, and where its numbers come from

Every figure here is Trading Core's. This page substitutes them into the formula the methodology publishes; it does not do the division itself.

The R, with the numbers in it
R = (exit − entry)÷(entry − stop),signed for direction
(81,047.3 − 81,030.8)÷(81,030.8 − 82,100)
= −0.02R
Entry the R was measured from81,030.8
Stop the R was divided by82,100
Exit81,047.3
Unleveraged price move−0.02%

Laddered entry — R is measured from the average of its fills (81,030.8), not the first level posted (80,800).

No stop was posted in the opening message. The stop the R was divided by is the one in force at the first fill, which arrived separately.

Which exit, and the market evidence for it
Exit reachedCLOSE
EvidenceCONFIRMED_CANDLE
VenueBYBIT · BTCUSDT
Exit at2026-09-20 18:54 UTC
Candlevirtual-fill:25ef4f01b46ea77ee2e5559dccfd028c5c14405674f856b5f7895f3dffc45950

The signal as posted

The structured levels, exactly as they reached the record. The analyst's own message is never reproduced here — only what it said in numbers.

Entries
entry-1LIMIT80,800
Stop as posted
—
Leverage as posted
—
Targets
No targets were posted.

Posted as Discord message 1549145034123645059. Open it in Discord →

What happened, in order

Every canonical event, including the ones later superseded. They are flagged rather than removed, because there is one attestation record per event and hiding them would leave records below corresponding to nothing.

Planned
2026-09-14 19:49 UTC
Opened
2026-09-20 10:16 UTC
Opened
2026-09-20 10:18 UTC
Closed
2026-09-20 18:53 UTC

Result after trading costs

Compare the signal’s gross result with its result after estimated trading costs.

Follower R · after estimated costs−0.09R
Round-trip cost−0.07R
Follower price move−0.12%
Cost as price move−0.10%

The published signal result with estimated entry and exit fees and slippage applied. Costs reflect the order type for each leg.

Fees and execution assumptions
Maker fee2 bps
Taker fee5.5 bps
Market slippage2 bps
Stop slippage5 bps
The legs this call resolved to
ENTRY: a limit, range or DCA entry, which rests in the book — MAKER, 2 bps fee
EXIT: the analyst closed or trimmed the position by hand — TAKER, 5.5 bps fee, 2 bps slippage
Every leg in the table
ENTRY: a limit, range or DCA entry, which rests in the book — MAKER, 2 bps
ENTRY: a market or cmp entry, taken at whatever was there — TAKER, 5.5 bps + 2 bps slippage
ENTRY: a stop entry, which crosses the book when it triggers — TAKER, 5.5 bps + 5 bps slippage
EXIT: the exit is a published target, which rests in the book — MAKER, 2 bps
EXIT: the exit is a stop, break-even included — TAKER, 5.5 bps + 5 bps slippage
EXIT: the analyst closed or trimmed the position by hand — TAKER, 5.5 bps + 2 bps slippage

Uses the published signal’s entry and exit convention. Your result depends on your fills, fee tier and exit choices. Read from benchmark policy axion-bybit-linear-v4 v4.

Verify this call yourself

Your browser recomputes each published record’s fingerprint and checks the links between records. Follow the external proofs to compare the anchored hashes and timestamps.

Checking 1 record…

Recomputing each hash in this browser.

#1plan
Record committed2026-09-14 19:50 UTC · signal posted 2026-09-14 19:49 UTC
Published hash7ad5dd140c8da40efdf654fcc2b9d3c0655a60ddad4ad0b5649b4586425d2908
The exact bytes that were hashed (1,612 characters)
{"corrected_kind":null,"event":{"effective_at":"2026-09-14T19:49:17.000000Z","id":"asv2:00fc08c8822f927562e18df5cc6a2750074d97f1","observed_at":"2026-09-14T19:49:36.000000Z","origin":"ANALYST_REPORTED","recorded_at":"2026-09-14T19:49:37.253662Z","semantic":"INSTRUCTION","type":"TRADE_PLANNED"},"kind":"plan","levels":{"announced_dca_slots":"0","auto_sl_be_override":null,"entries":[{"allocation_pct":null,"entry_id":"entry-1","match_current_position_quantity":false,"price":"80800","price_high":null,"price_low":null,"trigger_price_type":"LAST","type":"LIMIT"}],"label":null,"leverage":null,"quantity_basis":null,"quantity_pct":null,"reference_price":null,"semantic_kind":"INSTRUCTION","stop":null,"stop_deferral":null,"targets":[]},"posted_at":"2026-09-14T19:49:17.000000Z","previous_record_hash":null,"record_id":"AXN-2026-09-14-00404/1","record_number":"1","restates":null,"result":null,"salt":"fc5551171f2b366da1b77dda3abd0234c9e368387fdf92ca0e4c66d622eda2e3","schema":"axion-attestation/2","signal_id":"AXN-2026-09-14-00404","source":{"analyst_id":"1325152295318716418","channel_id":"1546221995627122849","content_hash":"83a8c7ff61c0e17f4df09d472dc312bd5f40ef7efdebb83128b960bbed09b80e","event_key":"1549145034123645059:9bdeae8d0c40:0","guild_id":"793098557715906597","message_id":"1549145034123645059","revision":"0","system":"AXIONSIGNAL_V2"},"source_record":{"record_hash":"f3498d5ba4138e1d8de8e317539f87125809ead7db35e48d9cae0f6c012ab475","record_id":"AXM-2026-09-14-01413/1"},"supersedes":null,"trade":{"analyst":"discord-1325152295318716418","instrument":"BTCUSDT","provider":"axion","side":"SHORT"}}
Or check it in a terminal
sha256sum records/AXN-2026-09-14-00404/1.json
Anchors
Public loganchoredlog/2026-09-14.jsonl line 53 →2026-09-14 19:50 UTC
Sigstore Rekoranchoredlog index 2834443569 →2026-09-14 19:50 UTC
OpenTimestampsanchoredBitcoin block 967,020 →2026-09-14 21:50 UTC
Proof fileanchoredcommit 3903063 →2026-09-14 21:50 UTC

Every record above is published in Axion's public transparency repository, alongside the signing key and a description of the format.

Which engines produced these figures

official-v4
Portfolio
axion-bybit-linear-v4
Policy
4
Policy version
v25
Projector
v1
Calculation
2026-09-20 20:38 UTC
Read at
Policy hash c25615a2bb2cf3e3590165216539c05770c26a18926f19f4c3b5c738ba99f031