TradingView alerts → DeFi execution
Find out exactly where your exit alert died.
When an alert should close a DeFi position and doesn't, the failure could be anywhere between TradingView and the chain. Most traders find out from their P&L and never learn why. We trace it, step by step.
Built after an exit alert on a winning trade never closed — and nobody could say why.
Four places an alert can die
Each one leaves a different trace. A post-mortem checks all four and names the one that broke.
01
TradingView never fired
The alert expired, ran on stale settings, or never triggered. Visible only in TradingView's alert log.
02
The webhook never arrived
The server was down, asleep or unreachable when TradingView sent it. Visible in your server's logs — if it keeps any.
03
The order was never sent
Rejected by validation, out of fees, an expired approval, or a failed RPC call. Visible in the connector — or nowhere.
04
Sent, but never executed
The transaction landed but the order was never filled, or the position never changed. Visible only on-chain.
Free post-mortems
Had an alert silently fail? Send us what you can export and we'll reconstruct what happened and name the step that broke. We're doing a limited number for free while we refine the method.
What we ask for
- Your TradingView alert history export
- Your server or connector logs, if you have them
- Your public wallet address, to read the on-chain record
What we never ask for
Private keys, seed phrases, API keys or logins. If anyone claiming to be us asks, it isn't us.
In development · GMX v2 first
What we're building
A self-hosted connector that turns TradingView alerts into DeFi orders — and proves what happened to every one.
Every alert, accounted for
Each alert is logged from arrival to the on-chain position change. If a step fails, you get a message naming it within seconds — not a surprise in your P&L.
Checks before every order
Trading approval expiry, remaining actions and fee balance are checked first, so an order that would fail is flagged loudly instead of failing silently.
A stop that outlives the software
An optional backstop stop rests on-chain, beyond your strategy's normal exits — designed to protect the position even if the connector goes down. Currently in testing.
Your server, your keys
It runs on your own host and is designed to sign with a trade-only GMX subaccount that cannot withdraw funds. We never see or handle your keys.
One-command, self-service setup with a check after every step.