Your token is static.
Make it alive.
Where the token is born. After graduation its main pool lives on PumpSwap. SENTIENT never launches tokens.
DLMM bins and DAMM v2 pools. Where engine liquidity actually lives.
Autonomous, risk-bounded engines that read the market and manage engine-owned liquidity.
Engines
Five first-party engines. Each one is a versioned, bounded program you install on a token's market.
Engine animations are illustrations of each engine’s behavior, not market data.
Engine proposes · Risk validates · Executor executes
No language model builds transactions. No step can be skipped.
- 1ObserveDexScreener · GeckoTerminal · Pump · Meteora
- 2Engine proposesdeterministic regime + mode logic
- 3Risk validatesbounds, venue, sizing, allowlist
- 4Dry-runtested against live chain state first
- 5Execute autonomouslyno human in the loop · Meteora SDKs only
- 6Recordevery step in the public log
Network
Summed from installations, engine treasuries and positions the keeper reads on-chain.
- Installations
- 0
- Operating
- 0
- Liquidity managed
- 0.00 SOL
- Permanently locked
- 0.00 SOL
- Liquidity created
- 0.00 SOL
- Confirmed transactions
- 0
Live activity
No engine activity yet. Events appear here as the keeper evaluates installations.
What SENTIENT will never claim
SENTIENT does not create tokens, bonding curves or pools. It begins after a token exists.
Engines manage liquidity. They do not cause, guarantee or protect price.
Liquidity is only called locked after a DAMM v2 permanent-lock transaction confirms on-chain.
Creator fees reach an engine only if the creator configures Pump fee sharing to its treasury.