Looking for blunt feedback from people who run bots or backends that swap.
Context: I'm on the BlazePhoenix team. We are a small team building an on-chain DEX aggregator. Our quotes come from a contract (the Quoter), so you read them with a plain eth_call on your own RPC. No API key, no account. There is also an SDK (npm i @blazephoenix/sdk) and an MCP endpoint if you are wiring up agents.
The trade-offs as I see them:
For the eth_call approach
- no key to rotate, no vendor rate limit
- deterministic per block, so you can replay a quote when a fill looks wrong
- the swap computes its route inside the executing transaction and reverts below your signed minimum
Against it
- you depend on your own RPC being healthy
- on-chain route search has to fit in gas, so it cannot be as wide as an off-chain solver
- we are pre-launch, and the contracts are not yet audited by an external firm; an independent external audit is scheduled
So the question: if you run a bot today, what would make you move one call path from a hosted API to an eth_call? Or what would stop you, regardless?
Not trying to recruit anyone. I would rather hear "this is pointless because X" now than after we have built the wrong thing.
Top comments (0)