01
Watching it yourself
A position out of range earns nothing until you act. That vigilance scales badly past two positions.
Poolcentric — non-custodial, automated liquidity management for Uniswap V3
── Non-custodial automation for Uniswap V3
Your pools. Your keys. Your machine.
Automated rebalancing for Uniswap V3, executed by a daemon on your own hardware. The cloud never signs a transaction.
── Invite-only · Arbitrum & Base first
↓ Scroll
Uniswap V3 5 EVM chains Invite-only release candidate
01 The vigilance tax
Every escape from the vigilance tax costs you something.
02
Handing over the trigger
Most automation keeps your assets but takes the trigger — a vendor's bot fleet decides when your position moves.
03
Rolling your own loop
Without simulation, cooldowns and caps, a hand-written rebalancer just makes mistakes faster than you would.
02 The execution boundary
One thing crosses the line, and it is not a key.
The platform decides and signs an intent. Your executor holds the only wallet key, and re-checks everything before it acts.
Poolcentric cloud
Decides · never signs txsObserve
Positions, ranges and pool state.
Evaluate
One decision against your policy: hold, rebalance or exit.
Emit signed intent
Constraints, nonce and expiry, signed with an ed25519 intent key — never a wallet key.
Your machine
Verifies · signs · broadcastsVerify + check policy
Signature, freshness and nonce, then your local limits.
Simulate
A failed simulation is a declined intent.
Sign, broadcast, report
Your key signs locally. Every check lands in your audit log.
03 Guardrails
Automation should be able to say no.
Your limits are enforced locally, before a signature exists. A declined intent is a normal, logged outcome.
max_gas_usd
max_slippage_bps
cooldown_seconds
max_rebalances_per_day
allowed_chains
allowed_wallets
allowed_kinds
dry_run
simulate before broadcast
nonce + expires_at
pause / resume
audit log
$ poolcentric-executor run --chain arbitrum
[9f1b] verify signature .... ok ed25519
[9f1b] policy: gas ........ ok $3.41 < $20.00
[9f1b] policy: slippage ... ok 42 < 100 bps
[9f1b] simulate .......... ok rebalance 1 position
[9f1b] sign + broadcast ... sent 0x7c…e2 (local wallet)
[c44a] policy: gas ........ declined $26.80 > $20.00
[c44a] reported to platform · nothing signed
$ poolcentric-executor policy show
{
"max_gas_usd": 20.0,
"max_slippage_bps": 100,
"allowed_chains": [42161, 8453],
"allowed_kinds": ["exit", "rebalance"],
"allowed_wallets": ["0x4f…c1a2"]
}
── Illustrative. Your policy lives on your disk; the platform cannot widen it.
04 Custody & surface
Trust-minimised is an architecture, not a promise.
01
No custom contracts
We call Uniswap's own canonical
NonfungiblePositionManager. No vault, no operator
contract, no pooled funds.
02
Only your machine can act
There is no bot fleet with authority over your position, and no allowlist we can add ourselves to.
03
The cloud's key can't move funds
It signs intents so your executor can verify them. Wallet keys never reach the platform, its logs or its API.
04
Inspectable by design
No inbound ports, append-only audit log. Open-sourcing the executor and intent protocol is planned.
05 Decision layer
Four outcomes, and a reason for each.
HOLD
Stay put. No intent is emitted.
PARTIAL_REBALANCE
Move part of the position toward the target range.
FULL_REBALANCE
Reposition the whole range.
EXIT
Close out on your policy's terms.
Intelligence engine · beta
Our decision-assist track is advisory and in beta. It suggests; it never holds authority, and we make no performance claims for it.
06 Plans
Start with no trust ask at all.
Monitor & Simulate
Free- 1 wallet, 1 chain
- Monitoring, analytics, 10 backtests a month
- Dry-run decisions with full guard checks
- No live execution, no signing surface
Trust ask: none
Autopilot
Pro- 5 wallets, 5 chains
- Live execution via your local executor
- 90-day analytics, 100 backtests a month
- Kill switch and audit log export
Trust ask: run the executor — you stay sole signer
Enterprise
Teams- Unlimited wallets and chains
- Approval workflow before execution
- Direct onboarding support
Trust ask: same boundary, more seats
── Pricing is set with the first design partners. Nothing here is a price commitment.
07 Straight answers
The questions an operator actually asks.
Do you ever hold my keys?
No. Wallet keys exist only on the machine running your executor, and the platform has no code path that loads one.
What if the platform were compromised?
A malicious instruction still has to pass signature verification, your local limits and a successful simulation on your machine. Anything outside your policy is declined locally — or pause the executor and nothing runs at all.
Which chains and protocols?
Uniswap V3 on Ethereum, Arbitrum, Base, Optimism and Polygon. Onboarding starts on Arbitrum and Base. Uniswap V4 and other AMMs are not supported.
Will this make me more money?
We don't claim that. Poolcentric sells operational reliability, not alpha — you keep the strategy, and providing liquidity still carries market, impermanent-loss and execution risk.
How ready is it, and what do I need?
It's an invite-only release candidate — experimental software, so start in dry run. Running it needs a machine that stays online, an RPC endpoint and comfort with a command line. No inbound ports.
Automate the vigilance.
Keep the custody.
A small group of design partners on Arbitrum and Base. Direct line to the founder, dry run until you decide otherwise.
── No drip sequence, a real reply