We’re launching ADAMANT Market-Making Software — a self-hosted open-source toolkit for token issuers and crypto projects that want to improve CEX market quality without sending tokens, funds, or API keys to a third-party market maker. We believe projects should not have to hand over custody or control just to make their market usable. • Order book building • Spread and Liquidity support • Reference price / arbitrage logic We’d love feedback from token issuers, and exchange teams.
No reviews yetBe the first to leave a review for ADAMANT Market-Making Software
Maker
📌
“Is this a trading bot?”
It is not positioned as a trader-focused profit bot.
It is self-hosted market-making software for token issuers and crypto projects that need better CEX market quality after listing: order book depth, spread/depth support, liquidity maintenance, price ranges, and monitoring.
“Do you manage funds?”
No. We do not take custody of tokens or funds. The software runs on the project’s own server and uses the project’s own exchange account. API keys are not sent to ADAMANT.
“Is this legal?”
The software is a self-hosted tool. Users are responsible for complying with exchange rules and applicable laws. We focus the product on transparent liquidity operations, not misleading market manipulation.
“Why open-source?”
Because token teams should not have to trust a black box with market operations. Open-source code lets teams inspect, run, and monitor the software themselves.
“How is it different from Hummingbot?”
Hummingbot is a broad open-source trading framework. ADAMANT Market-Making Software is focused on token issuers and CEX market quality: order book depth, spread/depth support, price ranges, monitoring, and optional premium support/connectors.
Report
How does the self-hosted setup actually handle reference price feeds — do you pull from a few external oracles and average them, or is the logic pluggable so we can wire in our own price source?
CurrencyInfo is a separate open-source service that validates rates using multiple sources, including MOEX, Currency-Api, ExchangeRate.host, CoinMarketCap, CryptoCompare, and CoinGecko. It compares data from different providers and filters out suspicious or unreliable values.
So the model is not “one hardcoded oracle.” It is:
1. exchange market data from the trading venue itself;
2. optional/reference validation through CurrencyInfo;
3. configurable CurrencyInfo endpoint.
There is no generic plug-in interface for arbitrary custom price sources yet. But the CurrencyInfo endpoint is configurable, so you can run your own CurrencyInfo instance or use an instance you trust.
That gives teams control over the reference-price layer without requiring the bot to directly integrate every possible external oracle/source.
Report
Maker
Hi Product Hunt,
We’re launching ADAMANT Market-Making Software — a self-hosted open-source toolkit for token issuers and crypto teams that want to improve CEX market quality without sending tokens, funds, or API keys to a third-party market maker.
The problem we’re solving: after a CEX listing, many token projects have thin order books, wide spreads, weak visible liquidity, and expensive or opaque market-making options.
Our trust model:
no token custody;
no fund transfer;
no third-party API key access;
no black box;
self-hosted deployment;
open-source code.
The free basic version helps with order book building, spread/depth support, liquidity maintenance, price ranges, trading activity policies, reference price logic, and stats. Premium modules, custom exchange connectors, WebUI access, setup assistance, and support are available separately.
We’d love feedback from crypto builders, token issuers, exchange teams, and open-source developers.
Especially on:
Is the positioning clear?
Would you trust this model more than a black-box market maker?
How does the self-hosted setup actually handle reference price feeds — do you pull from a few external oracles and average them, or is the logic pluggable so we can wire in our own price source?
@alparslanvfgl Good question.
The bot primarily uses market data from the exchange it trades on, and can additionally verify/reference prices through ADAMANT CurrencyInfo:
https://github.com/Adamant-im/currencyinfo
CurrencyInfo is a separate open-source service that validates rates using multiple sources, including MOEX, Currency-Api, ExchangeRate.host, CoinMarketCap, CryptoCompare, and CoinGecko. It compares data from different providers and filters out suspicious or unreliable values.
So the model is not “one hardcoded oracle.” It is:
1. exchange market data from the trading venue itself;
2. optional/reference validation through CurrencyInfo;
3. configurable CurrencyInfo endpoint.
There is no generic plug-in interface for arbitrary custom price sources yet. But the CurrencyInfo endpoint is configurable, so you can run your own CurrencyInfo instance or use an instance you trust.
That gives teams control over the reference-price layer without requiring the bot to directly integrate every possible external oracle/source.
Hi Product Hunt,
We’re launching ADAMANT Market-Making Software — a self-hosted open-source toolkit for token issuers and crypto teams that want to improve CEX market quality without sending tokens, funds, or API keys to a third-party market maker.
The problem we’re solving: after a CEX listing, many token projects have thin order books, wide spreads, weak visible liquidity, and expensive or opaque market-making options.
Our trust model:
no token custody;
no fund transfer;
no third-party API key access;
no black box;
self-hosted deployment;
open-source code.
The free basic version helps with order book building, spread/depth support, liquidity maintenance, price ranges, trading activity policies, reference price logic, and stats. Premium modules, custom exchange connectors, WebUI access, setup assistance, and support are available separately.
We’d love feedback from crypto builders, token issuers, exchange teams, and open-source developers.
Especially on:
Is the positioning clear?
Would you trust this model more than a black-box market maker?
What would make onboarding easier?
Which exchange connectors should we add next?