Skip to content

Releases: Trac-Systems/intercom-dex

intercom-dex 0.1.39

Choose a tag to compare

@TracSystems TracSystems released this 26 Oct 12:12

Sellers are told before a trade when they need SOL to receive their USDC, and failed claims are no longer silent.

  • Receiving USDC on Solana needs a small SOL network fee (plus a one-time USDC account if the wallet never held
    USDC). Before a sell offer is posted, a buy offer is taken or a take is accepted, the app now checks the seller's
    Solana wallet and, if it is short, says exactly how much SOL to add and to which address. Nothing is sent first.
  • A claim that fails is shown on the trade row, in the alerts and in status, with the reason and what to do. The
    claim keeps retrying every 15 seconds and goes through as soon as the wallet is funded.

If a sale of yours is stuck at "claiming": add about 0.01 SOL to your DEX Solana wallet and leave the app running.

Works together with 0.1.32 and later. No minimum-version change: nobody is locked out.

intercom-dex 0.1.38

Choose a tag to compare

@TracSystems TracSystems released this 26 Oct 10:58

A seller's transfer is never missed again because one message got lost.

  • Signers now find the seller's transfer themselves. If a trade has waited 30 seconds without the seller's
    "transfer sent" message, each signer looks up the seller's newest transactions on the Trac explorer every 15
    seconds and checks any match on its own peer, exactly as it checks a reported transfer. The explorer only
    suggests transaction ids; nothing is trusted from it.
  • The seller's app repeats its "transfer sent" message until the signers respond: after 10 s, 20 s, 40 s and so
    on, at most every 2 minutes, and only inside the transfer window.
  • A seller trade whose USDC lock was refunded now ends as lost instead of staying in "waiting for shares", also
    for trades saved by older versions; a claimed lock ends as complete.

Signers (run by the venue) carry the main fix, so traders are protected without updating. Updating the app adds
the repeated message and the corrected trade status.

Works together with 0.1.32 and later. No minimum-version change: nobody is locked out.

intercom-dex 0.1.37

Choose a tag to compare

@TracSystems TracSystems released this 26 Oct 01:02

Balances that cannot hang, and trade lists that keep refreshing.

  • When the RESET chain data a balance needs has not arrived yet, the balance read now gives up after five
    seconds with a clear message instead of waiting 30 seconds for "Bridge timeout: dex_balances", and the peer
    reconnects to the RESET data by itself.
  • A failed balance read never shows as zero. The dashboard keeps the last good balances with the time they were
    read and a visible warning, and leaves them out of trade amounts until a fresh read succeeds.
  • A pair whose trade list was empty when you opened it now keeps checking and shows new trades as they happen.
    Order book, chart and trade history say when a refresh fails instead of silently showing old data.
  • RESET catch-up no longer holds up the peer: chain entries are applied in short slices and the per-entry log
    lines are summarized every 30 seconds.
  • The peer re-opens its connection to the venue by itself if that connection stops answering.

Works together with 0.1.32 and later. No minimum-version change: nobody is locked out.
Update when convenient; traders who saw "Balances unavailable right now" benefit most.

No changes to contracts.

Archive intercom-dex-v0.1.37.tar.gz
sha256 8c298cb3ad2c7b5aa63bc45842844cec85c05c0b1a8d74dbc252556df0b0b1d1

Venue keys to pin:

  • serviceKey f5ac9f9cae208e0d8bb4e79e066e5ec423d6abb820377a5b0258e2ff358e6437
  • servicePeerKey e5fed943601365608957d82588fd8b71e1e44457f2c2e80dcb5748fd803ff1f1

Locks venue key to pin:

  • locks.venueKey 3efae9e5671ef2105a9b72bdbb3d97292a44960b69f0398527a468673c24aa0f

Install: unpack, then npm ci and npm ci --prefix peer. See README.md and docs/OPERATORS.md.

intercom-dex 0.1.36

Choose a tag to compare

@TracSystems TracSystems released this 25 Oct 17:42

Two fixes for trades that end without delivery.

  • A buyer lock that never landed on Solana no longer holds the buyer's USDC for 48 hours. Once the lock
    transaction has provably expired and no escrow exists, the trade ends and the USDC is free again for new
    offers. This also clears trades that are already stuck in that state: update, restart, and they resolve within
    a few minutes.
  • When a buyer refunds and the seller never sent tokens, the amount returns to the seller's open offer
    (also after a restart). Wallet commitments, dashboard offer sizes and trade history follow the same rule.
    Recorded or uncertain transfers still count as sent.

Works together with 0.1.32, 0.1.33, 0.1.34 and 0.1.35. No minimum-version change: nobody is locked out.
Update when convenient; traders with a trade stuck in "locked" benefit most.

No changes to contracts.

Archive intercom-dex-v0.1.36.tar.gz
sha256 f29054f5530c734de5256e34fdc358ff2497d76dc15d63f02863fbb0e696faf8

Venue keys to pin:

  • serviceKey f5ac9f9cae208e0d8bb4e79e066e5ec423d6abb820377a5b0258e2ff358e6437
  • servicePeerKey e5fed943601365608957d82588fd8b71e1e44457f2c2e80dcb5748fd803ff1f1

Locks venue key to pin:

  • locks.venueKey 3efae9e5671ef2105a9b72bdbb3d97292a44960b69f0398527a468673c24aa0f

Install: unpack, then npm ci and npm ci --prefix peer. See README.md and docs/OPERATORS.md.

intercom-dex 0.1.35

Choose a tag to compare

@TracSystems TracSystems released this 25 Oct 14:55

Trades waiting for a refund no longer slow down new trades.

  • A trade waiting for its refund used to repeat its old messages every ten seconds, each with fresh proof-of-work.
    With a few of these, the app was too busy to answer new trades in time ("Reveal arrived too late",
    "Accept slot outside the freshness window"). Waiting trades now stay quiet after the send deadline.
  • New negotiations are stamped before repeated trade dealings.
  • Sellers stop repeating transfer messages once the verification window has closed.
  • Reconnect recovery, missing-share requests and automatic refunds work as before.

Works together with 0.1.32, 0.1.33 and 0.1.34. No minimum-version change: nobody is locked out. Update when convenient;
traders with trades waiting for a refund benefit most.

No changes to contracts.

Archive intercom-dex-v0.1.35.tar.gz
sha256 a940e9c330100eaff2a5c16eb4d779e9caa0f1563cf46a0555e5cebfad73c211

Venue keys to pin:

  • serviceKey f5ac9f9cae208e0d8bb4e79e066e5ec423d6abb820377a5b0258e2ff358e6437
  • servicePeerKey e5fed943601365608957d82588fd8b71e1e44457f2c2e80dcb5748fd803ff1f1

Locks venue key to pin:

  • locks.venueKey 3efae9e5671ef2105a9b72bdbb3d97292a44960b69f0398527a468673c24aa0f

Install: unpack, then npm ci and npm ci --prefix peer. See README.md and docs/OPERATORS.md.

intercom-dex 0.1.34

Choose a tag to compare

@TracSystems TracSystems released this 25 Oct 05:23

Traders prove their Trac address, and signers stop sellers who leave paid trades unsent.

  • Every trader now proves, with a signature from the Trac wallet it trades from, that it controls its Trac address.
    Before, an offer could name someone else's well-funded address. Nothing is paid or locked for this.
  • Before agreeing to a trade, signers check that the seller's Trac wallet holds the coins, minus what that wallet
    already owes in other trades.
  • A seller who twice leaves a paid trade unsent within seven days is paused for seven days. A new DEX identity does
    not clear it: the pause follows the proven Trac address.
  • Refused trades now say why straight away. Makers turn down takes that cannot cover the trade and its fees.
  • Offers made under older fee or registry terms that are still valid stay visible.

How it rolls out: signers first, then the venue and market feeds, then traders. The address proof only becomes
required when the venue raises its minimum version to 0.1.34; it will be announced before that. After that, open
offers have to be posted again from an updated app, and older apps show "update required". Trades already agreed
finish normally. No collateral or trading deposit is required.

No changes to contracts.

Archive intercom-dex-v0.1.34.tar.gz
sha256 caddceac56276367cbb4a06e14d85746b7f4b8f2148ef491fe4b84a6738440f8

Venue keys to pin:

  • serviceKey f5ac9f9cae208e0d8bb4e79e066e5ec423d6abb820377a5b0258e2ff358e6437
  • servicePeerKey e5fed943601365608957d82588fd8b71e1e44457f2c2e80dcb5748fd803ff1f1

Locks venue key to pin:

  • locks.venueKey 3efae9e5671ef2105a9b72bdbb3d97292a44960b69f0398527a468673c24aa0f

Install: unpack, then npm ci and npm ci --prefix peer. See README.md and docs/OPERATORS.md.

intercom-dex 0.1.33

Choose a tag to compare

@TracSystems TracSystems released this 24 Oct 16:02

One command starts the DEX in the background.

  • node bin/dex.mjs start --config /path/to/dex-data/trader.json asks for your password, starts the peer and the
    trading program together, prints the dashboard link and returns. Both keep running after you close the terminal or
    your agent. On Windows no console windows stay open.
  • If the peer or the trading program crashes, it is restarted on its own. After five crashes in ten minutes it stops
    and writes the reason to the log.
  • status, logs and stop show what is running, print recent logs and shut the DEX down. Stop refuses while a
    trade, withdrawal or locks position is unfinished and names the step.
  • The MCP server uses the running DEX and leaves it running when your agent closes.

Nothing changes for apps you already run another way: the separate peer and trader commands work as before.

Updating is recommended: apps from 0.1.5 on keep trading, and old and new apps work together. No changes to contracts.

Archive intercom-dex-v0.1.33.tar.gz
sha256 c50a70269f22e77a5b0884c2b9be2372bbbd8b5f083a6044f8a536e04f5f7563

Venue keys to pin:

  • serviceKey f5ac9f9cae208e0d8bb4e79e066e5ec423d6abb820377a5b0258e2ff358e6437
  • servicePeerKey e5fed943601365608957d82588fd8b71e1e44457f2c2e80dcb5748fd803ff1f1

Locks venue key to pin:

  • locks.venueKey 3efae9e5671ef2105a9b72bdbb3d97292a44960b69f0398527a468673c24aa0f

Install: unpack, then npm ci and npm ci --prefix peer. See README.md and docs/OPERATORS.md.

intercom-dex 0.1.32

Choose a tag to compare

@TracSystems TracSystems released this 24 Oct 14:25

Takes reach the seller on busy apps.

  • 0.1.31 limited an app to eight network connections. On a busy network those slots filled at once, and a buy
    could then fail to reach the seller: the buyer sent its take and heard nothing until "the other side took too long
    to answer". The limit is gone. Offers, the book and signer heartbeats still come only from the venue, so the lower
    traffic from 0.1.31 stays.

Thanks to the community member who sent detailed logs.

Agents and scripts using the control API or MCP get the fixes automatically after updating.

Updating is recommended: apps from 0.1.5 on keep trading, and old and new apps work together. No changes to contracts.

Archive intercom-dex-v0.1.32.tar.gz
sha256 e06336f46867a33d31f7de817b0c00d1d57f7d9bf49baf35f696e9c5c490940b

Venue keys to pin:

  • serviceKey f5ac9f9cae208e0d8bb4e79e066e5ec423d6abb820377a5b0258e2ff358e6437
  • servicePeerKey e5fed943601365608957d82588fd8b71e1e44457f2c2e80dcb5748fd803ff1f1

Locks venue key to pin:

  • locks.venueKey 3efae9e5671ef2105a9b72bdbb3d97292a44960b69f0398527a468673c24aa0f

Install: unpack, then npm ci and npm ci --prefix peer. See README.md and docs/OPERATORS.md.

intercom-dex 0.1.31

Choose a tag to compare

@TracSystems TracSystems released this 24 Oct 12:15

Much less network traffic, and every refused trade gets an answer.

  • An idle app used about 300 KB/s in each direction, because every peer passed every offer, heartbeat and book update
    on to all its neighbours. Offers, the book and signer heartbeats now come from the venue only, and apps forward
    nothing. In tests an idle app dropped to a few KB/s. Trades still connect buyer and seller directly, or through a
    relay when a direct connection is not possible.
  • A seller that cannot take a trade now always says so: setup errors are declined, a take that does not match the
    offer is aborted at once, and a take that waits more than ten seconds for a Solana view is aborted with that
    reason. Before, the buyer could wait without an answer.
  • Peers can report what their traffic is made of with the bandwidth.stats bridge command (see docs/OPERATORS.md).

Thanks to the community members who reported the bandwidth use and the silent refusals.

Agents and scripts using the control API or MCP get the fixes automatically after updating.

Updating is recommended: apps from 0.1.5 on keep trading, and old and new apps work together. No changes to contracts.

Archive intercom-dex-v0.1.31.tar.gz
sha256 5b6ef05ed3cc6062323e2b52e01affec57c5bebc83e625e0c8ec78c19a965267

Venue keys to pin:

  • serviceKey f5ac9f9cae208e0d8bb4e79e066e5ec423d6abb820377a5b0258e2ff358e6437
  • servicePeerKey e5fed943601365608957d82588fd8b71e1e44457f2c2e80dcb5748fd803ff1f1

Locks venue key to pin:

  • locks.venueKey 3efae9e5671ef2105a9b72bdbb3d97292a44960b69f0398527a468673c24aa0f

Install: unpack, then npm ci and npm ci --prefix peer. See README.md and docs/OPERATORS.md.

intercom-dex 0.1.30

Choose a tag to compare

@TracSystems TracSystems released this 24 Oct 02:17

Offers are always announced on busy peers.

  • On a busy app (many heartbeats, acks and trade steps at once), new offers, settled notices and presence updates could
    wait for their proof-of-work stamp indefinitely. The offer then showed in your own book but never reached the public
    book, and some accepts arrived too late to count. A stamp now waits for more urgent stamps for at most two seconds,
    then shares the work with them, so every offer goes out.
  • Urgent trade messages still go first.

Thanks to the community member whose agent reported it.

Agents and scripts using the control API or MCP get the fix automatically after updating.

Updating is recommended: apps from 0.1.5 on keep trading. No changes to contracts.

Archive intercom-dex-v0.1.30.tar.gz
sha256 65eef96527d11cd05af6cfe5bdf333ad7361b70ce9ed95fb745a75a7aaddf209

Venue keys to pin:

  • serviceKey f5ac9f9cae208e0d8bb4e79e066e5ec423d6abb820377a5b0258e2ff358e6437
  • servicePeerKey e5fed943601365608957d82588fd8b71e1e44457f2c2e80dcb5748fd803ff1f1

Locks venue key to pin:

  • locks.venueKey 3efae9e5671ef2105a9b72bdbb3d97292a44960b69f0398527a468673c24aa0f

Install: unpack, then npm ci and npm ci --prefix peer. See README.md and docs/OPERATORS.md.