
Core contributor @kalqix | Advisor @QuickSwapDex | Big time Ethereum fan
New Delhi, India
Joined July 2009
- Tweets1.6K
- Following640
- Followers6.1K
- Likes6.2K
Pinned Tweet
2 years of hard work finally coming to fruition. I am really excited about tomorrow. Are you??
Every exchange says it matches orders fairly.
Almost none can show you.
Price-time priority is a simple rule: best
price first, and at the same price, whoever
came first. The hard part has always been
checking it. You see your fill. You never see
the queue.
On KalqiX, every batch of trades gets a
zero-knowledge proof that orders were matched
by price-time priority, with nothing reordered
or front-run. A contract on Base verifies it.
Trade data goes to Avail, so anyone can
rebuild the state.
Fairness you can't check is a promise.
Fairness you can verify is a property.
Your wallet's security model includes every
website you copy an address from.
An Optimizely signup flaw let an attacker
plant address-swapping code on 178 major
sites, including HSBC, the BBC and Ledger.
No key needed. No contract bug needed. Just a
page showing the wrong address.
For users: check the address in your wallet
before you sign, not the one on the screen.
For builders: every address a page gets to
choose is attack surface. On KalqiX, a
withdrawal has one destination: your own
wallet.
Fewer choices for the page. Fewer places to
lie.
Writing is how I find out I don't understand
something yet.
In my head, every plan is complete. On a page,
the gaps show up by the second paragraph: the
edge case nobody owns, the step that assumes
someone is online, the number I was hoping not
to check.
I'd rather find that in a doc than in
production. Rewriting a page costs an hour.
Rewriting shipped code costs a quarter.
A plan in your head is a feeling.
A plan on a page is a claim.
An exit that can be paused is a permission,
not a right.
A proposed emergency pause for Lido Lend would
block repayments, but not interest. It would
also stop lender exits and liquidations. A
separate governance mechanism could remove its
automatic expiry.
Emergencies are real. Pauses have their place.
The question is what stays open while
everything else is frozen.
On KalqiX, that answer lives in the contract.
An escape hatch lets you withdraw directly on
Base even if every other component goes
offline.
Pause the engine if you must. Never pause the
exit.
For years, trading on-chain meant choosing
which cost to accept.
A CEX gives you speed and a deep book.
You give it your funds.
An AMM lets you keep your funds. You pay in
slippage, and your swap waits in a public
mempool for bots to sandwich.
Zero-knowledge proofs ended the choice.
On KalqiX, orders are encrypted until matched.
The engine matches by price-time priority in
under 10 ms. Every batch is proven and
verified
on Base. Funds stay in a contract, not with
us.
The CEX asks for your funds.
The AMM asks for your edge.
A proof asks for nothing.
Raise on proof, not on promise.
We started building KalqiX around the start of
2024 and took no outside capital until the
product was built.
A deck can claim anything. A working matching
engine can only show what it does.
Money raised on a promise comes with a story
you now have to defend. Money raised on a
product comes with a question you've already
answered.
Decks persuade. Products prove.
A sevenfold jump in phishing alerts is partly
a sevenfold jump in seeing them.
Bitget Wallet flagged about 37,000 signing
requests a week for phishing in Q3. It said
better monitoring likely contributed to the
increase.
The useful lesson isn't the multiplier. Most
drains don't need your keys. They need one
signature you didn't read.
That's why I like boring exit paths. On
KalqiX, withdrawals only ever go back to your
own wallet.
Hold your keys. Read what you sign. Revoke
what you forgot.
Every new exchange starts with the same
problem: an empty order book.
You can ship the best frontend in crypto. If
the book behind it is thin, traders pay for it
in spread and slippage, and they leave.
So we built KalqiX as one shared book. A
partner keeps its own brand, frontend, token
and community. Its flow lands in the same
order book as everyone else's, so liquidity is
pooled instead of split.
The thousandth exchange shouldn't start from
zero.
Own the frontend. Share the depth.
Great conversations at Devcon Mumbai! 🇮🇳🔥
KalqiX's @nitin7dc, @prateek_si, and @sameepsi catching up with @0xPolygon co-founder @sandeepnailwal.
From scaling DeFi to building better trading infrastructure, there's plenty to discuss when builders get together.
Good to reconnect, exchange ideas, and explore what's next.
More building. More power. 🚀
Things are shaping up
Order books are coming to QuickSwap 👀
QuickX is live in beta - a new CLOB DEX from @QuickswapDEX.
Want an early look? Head to the official QuickSwap Telegram and ask for access. 🐉
Sameep Singhania retweeted
QuickX is now live in beta mode.
The revolutionary CLOB DEX to change the game in DeFi.
Want to try it out?
Send a message in the official QuickSwap Telegram group for access to the beta link 👀
Mumbai, the KalqiX crew has landed! 🇮🇳🔥
One team. One mission. Rethinking how exchanges are built.
@sameepsi (CEO),
@nitin7dc (CTO),
@prateek_si (CMO) &
Alan Hung (CBO) are here for @EFDevcon !
Launching a token? Want your own white-label exchange? Exploring liquidity, market making, or trading infrastructure partnerships?
We should talk.
📍 Devcon India, Mumbai
📩 DM us to meet the team!
Focus isn't what you work on. It's what you
refuse to.
Every good idea asks for a slice of the team.
Each one looks cheap alone. Together they're
how a startup ends up with ten half-built
products and nothing finished.
We launched mainnet with spot and two markets.
Perps are in development, and they'll ship
when they're right, not when they'd look good
on a slide.
My test: if this works perfectly, does the
core get better? If not, it waits.
A yes spends the year. A no protects it.
The venue that matches your trade shouldn't be
the one holding your money.
Standard Chartered says it's providing
digital-asset custody for LMAX across
Luxembourg and the DIFC. A separate collateral
link would let clients trade against tokens
that stay in bank custody.
Traditional markets have kept custody and
execution apart for decades. Crypto bundled
them and called it convenience.
We split them on KalqiX. The engine matches.
Funds sit in our contract on Base, not with
us, and withdrawals only go back to your own
wallet.
Banks separate them with legal entities. We do
it with a contract and a proof.
Can't agree more to it.
Replying to @milesdeutscher
Safe is a stack: self-custody, verifiable settlement, and opsec. No single layer does it alone.
This is a hard time and entire industry should come together.
We stand with @binance and its community.
Hats off to Binance’s security team and industry partners for acting quickly to freeze affected assets.
This is a time for our industry to stand as one, put users first, and support the recovery efforts. 🤝
An order book is only as good as the people
quoting on it.
Traders show up for tight spreads. Tight
spreads show up because someone runs a bot
around the clock.
So we never treated algo traders as a later
audience. KalqiX has a REST API and an
official Hummingbot connector, so a market
maker can point the strategies they already
run at our book instead of writing an
integration from scratch.
Limit and market orders. GTC, IOC,
fill-or-kill. Price-time priority, matched in
under 10 milliseconds, every batch ZK-proven
on Base.
Frontends bring traders. Market makers keep
them.
Nobody opens a store by building a card
network.
Yet most teams that want an exchange start by
building a matching engine.
Matching, proving, settlement, data
availability, audits. Each is a company's
worth of work. Our contracts alone went
through a Hexens audit before mainnet: 9
findings, zero critical, zero high, every
medium fixed.
A project that plugs into KalqiX keeps what
makes it different: its brand, frontend, token
and community. The engine underneath is
shared, and so is the order book.
Build what your users see.
Plug into what they need to trust.
Writing is the cheapest way to find out you're
wrong.
In my head, every plan is airtight. On paper,
the gaps show up by the third paragraph.
A vague idea survives a meeting. Everyone
nods, nobody wants to ask the obvious
question, and the hole ships with the product.
It doesn't survive a page.
So I write before I build anything that
matters. What it does, what it won't do, what
breaks if I'm wrong.
Half the time the page kills the idea. That's
the page doing its job.
Meetings hide the gaps. Pages find them.











