DEV Community: Ritik Kumar

I placed a perp order on Solana devnet and searched my wallet on an explorer. The deposit showed up and the position stayed hidden by design: the program verifies a proof and never reads it. Would you trust a proof over a readable account?

Ritik Kumar — Fri, 09 Oct 2026 21:32:33 +0000

I placed a perp order on Solana devnet, then tried to find my own position onchain

Ritik Kumar — Thu, 08 Oct 2026 21:00:10 +0000

I work on growth at Privora, so read this as an insider's test. I am also far from being one of the engineers, which is why I ran it the way a new user would. I placed one order on our devnet and then went looking for my own position on a public explorer.

Here is the short version, followed by three checks you can repeat in about ten minutes.

The short answer

Privora is a perpetual futures exchange on Solana with a public order book and private positions. It is live on devnet with free test funds. Anyone can see the price, side and size of an order on the book. Who placed it, and the position, collateral and leverage behind it, stay private and are verified with zero-knowledge proofs.

What you need

A Solana wallet set to devnet
Two minutes to claim free devnet USDC inside the app
The devnet app: dev.privora.xyz

No real money is involved at any step.

Check 1: place an order, then search your wallet

Connect your wallet, claim test USDC, deposit it and place a small order. Then paste your wallet address into a Solana explorer set to devnet.

What to expect: your funding activity is there, including the deposit. The order, the fill and the position are not listed under your wallet.

Why: your browser signs the order with a shielded session key. Your wallet does not sign or pay for the trade transaction, so the trade does not appear under your address.

Check 2: read the market as a stranger

Place an order and watch the order book and the recent trades the way another trader would.

What to expect: every order and trade shows its price, size and time. Nothing on the screen points back to the wallet behind it.

Why: the market itself is public. Matching uses public price, side, size and time priority. Privacy is applied to ownership and account state.

The position itself appears only inside your own private account.

Check 3: count the wallet prompts

Place three orders in a row and count how many times your wallet asks you to approve something.

What to expect: your wallet approves the deposit. Placing an order does not ask your wallet to sign a trade transaction.

Why: you deposit once with your wallet. After that, orders are signed as intents by the session key in your browser.

What Privora does not hide

A fair test includes the limits, so here they are.

Deposits and withdrawals are linkable to your wallet. These are the two points where funds cross between your public wallet and your private account.
The backend sees more than the public does. It receives your encrypted order package and learns the linkage it needs to prove and settle trades. It never receives your shielded signing secret.
The backend has to be online. If it stops, trading stops, although it cannot move funds or change balances on its own, because Solana verifies a proof for every state change.
This is devnet. Test funds, test conditions, and things can break.

Quick questions

What is Privora?
Privora is a ZK perpetual futures exchange on Solana. The order book is public, and each trader's position, collateral, leverage and liquidation level are private.

Is Privora live on mainnet?
No. Privora is live on Solana devnet, where trading uses free test USDC.

What can other people see when I trade on Privora?
They can see orders on the public book and the trades that happen. They cannot see which wallet placed an order or what position that wallet holds.

Does my wallet sign every trade?
No. Your wallet signs the deposit. Orders are signed by a shielded session key in your browser.

How does Solana know a private trade is valid?
Each state change comes with a Groth16 zero-knowledge proof that the Solana program verifies against live onchain state, covering authorization, margin and conservation of funds.

Do I need real money to try it?
No. You claim free devnet USDC inside the app.

I run marketing with 7 AI agents. The hardest part is keeping them on the same page.

Ritik Kumar — Sat, 26 Sep 2026 21:56:05 +0000

I handle growth for a small AI product. To keep up with LinkedIn, X, SEO articles and outreach, I set up a separate AI agent for each job. One writes LinkedIn posts, one writes replies on X, one plans blog articles, one helps with outreach, and one plans my day.

On paper this sounds like a small team. In practice, I spend a lot of my day doing one thing: explaining the same context again and again.

The problem I kept running into

Every agent starts with a blank head. Each time I open a new chat, I have to tell it:

What the product does
Who we are trying to reach
Which words we never use
What we posted yesterday
What changed in the plan this week

The LinkedIn agent does not know what the X agent wrote this morning. The planning agent does not know that a launch date moved. If I forget to mention something, the output looks fine but is wrong in small ways.

What I tried

1. One giant prompt with everything in it.
It worked for about a week. Then the plan changed, and I had to update the same text in five places. Half the time I forgot one.

2. Shared documents inside a project.
Better. Each agent could read the same master doc. But the docs got long, some parts went stale, and agents still had no idea what the other agents had done.

3. Writing a short "today" note by hand.
This helped the most, but it is manual work every morning. It also depends on me remembering everything.

What I learned

After a few weeks, I noticed the agents themselves were rarely the problem. The writing quality was fine. The problem was context:

Context lives in many places. The plan is in one doc, the rules in another, yesterday's posts somewhere else.
Context goes stale. A static brief from last week gives confident but outdated answers.
More context is not always better. When I gave an agent everything, it pulled in details that had nothing to do with the task.
Agents do not share what they know. Each one works alone, even when they serve the same goal.

What I think a better setup needs

If I could design the ideal system, it would have four things:

Selected sources. I choose what each agent can see.
A clear trail. When an agent uses a fact, I can see where it came from.
Fresh context. When the plan changes once, every agent sees the change.
Shared goals. Agents working on the same campaign see the same current picture, while private notes stay private.

Where I am now

I still use project docs and a daily note, and it works well enough for one person. But the more agents I add, the more time goes into keeping them in sync instead of doing actual work.

This problem is also the reason the team I work with is building Pryveo, a context and memory layer for people and AI tools.

If you use more than one AI agent or assistant in your work, how do you keep them all working from the same context?

This post was written with help from AI for drafting and editing. The experience and setup described are my own.