Loading price
Liquidity ControllerPublic liquidity controller

Public 4TEEN Liquidity Controller

Automation can wake the route, but any wallet can still pull the bootstrapper when the contract gate is open.

This page should not read like a closed ops panel. It should make one thing obvious: controller-side TRX is visible, reserve-side inventory is visible, and the release rules still live on-chain.

If the UTC window is open, the controller is above threshold, and the signing wallet has enough network resources, liquidity can still execute from the wallet even if the automation layer misses a day.

  • PUBLIC TRIGGER. CONTRACT GATE.
  • AUTOMATION HELPS. CONTRACTS DECIDE.
  • BOOTSTRAP FIRST. EXECUTE ON-CHAIN.

Controller Balance

1k TRX

TRX currently waiting inside FourteenLiquidityController.

Next Release

64.46 TRX

Projected TRX release when the contract window is valid.

Trigger Floor

100 TRX

Minimum controller balance required before execution is valid.

Cadence

Once / UTC day

Once per UTC day. The gate is enforced by contract, not by automation.

4TEEN public liquidity controller mobile wallet preview

The website is the proof layer. The wallet is the execution surface for manual trigger, resource checks, and final signing.

The website is the proof layer. The wallet is the execution surface for manual trigger, resource checks, and final signing.

Controller Balance

1k TRX

TRX currently waiting inside FourteenLiquidityController.

Next Release

64.46 TRX

Projected TRX release when the contract window is valid.

Trigger Floor

100 TRX

Minimum controller balance required before execution is valid.

Cadence

Once / UTC day

Once per UTC day. The gate is enforced by contract, not by automation.

Public Route

Automation is configured. Public execution still belongs to the wallet.

The wallet app already carries the automation path, but the more important message is broader than that: this route is still public. A signing wallet can wake the bootstrapper when the contract conditions are already satisfied.

Public Liquidity Controller

Any wallet can wake the route. The controller still decides whether liquidity actually moves.

That is the right separation of powers. Automation is allowed to help with timing, but the controller and bootstrapper remain the authority layer. The execution path does not disappear if a bot pauses.

  • Direct 4TEEN buys send 90% of purchase TRX into the controller balance.
  • LiquidityBootstrapper prepares the token side from FourteenVault before the controller executes.
  • The once-per-UTC-day rule, the minimum balance, the release percentage, and the split stay on-chain.

Automation

The wallet repo already wires the wake-up path

The mobile flow exposes the liquidity trigger and the automation helper together. That makes the scheduler visible, but it does not turn the scheduler into a hidden operator.

Manual trigger

If automation misses, a user can still sign the route manually

The wallet can call bootstrapAndExecute() from a normal user session. If the gate is open and resources are available, liquidity still goes through.

This is why the page should speak about a public controller, not about a private back office. The route survives beyond the automation layer.

Live Controller State

What the controller says right now

Controller Balance1k TRX
Latest Funding9 TRX
Latest Funding At2026 M05 5 16:55:45 UTC
Last Execute2026 M05 19 15:33:45 UTC
Min Balance100 TRX
Daily Release6.43%
Target Split50 / 50
Window StateReady now
Next WindowOpen now
Snapshot Updated2026 M06 20 12:02:08 UTC

The snapshot is useful because it separates moving parts cleanly: controller TRX, funding cadence, release size, threshold, and time gate all stay visible at once.

Trigger Model

What actually happens when someone taps Trigger Liquidity

The route is simple when stated honestly: first the bootstrapper checks the day gate and tops up executor inventory, then the controller releases TRX, then the two market paths receive their split.

bootstrapAndExecute()

The trigger path is public, resource-aware, and still ruled by contracts.

This is not a fake admin button. The wallet has to satisfy normal network conditions, and the route only continues if the same controller rules still pass at execution time.

  • Step 1: bootstrapper checks the controller window and computes the allowed release size.
  • Step 2: bootstrapper tops up executor-side 4TEEN from FourteenVault before the market-side leg runs.
  • Step 3: controller executes the release and splits flow 50 / 50 across JustMoney and Sun.io V3.

Resources

A normal wallet can cover the route with rent or preloaded energy

The app already frames this as a resource-aware action. The point is not a hidden server key. The point is that a public wallet can still finish the route cleanly.

Rule set

Scheduler convenience never overrides the contract rule set

Missing the bot window does not rewrite the cadence. Hitting the button early does not bypass the gate. Contracts still accept or reject the route.

That is the right market signal: public trigger, visible reserve prep, deterministic release rule.

Latest Executions

Confirmed liquidity executions from the live feed

This list stays intentionally tight. It shows the latest confirmed execution rows so a user can verify that the controller is alive without turning the page into a noisy block explorer clone.

Total ReleasedSplitHappenedUTC DaySource
Total Released68.89 TRX
Split
JM 34.45 TRXSUN 34.45 TRX
Happened2026 M05 19 15:33:45 UTC
UTC Day20592
SourceOpen tx
Total Released70.41 TRX
Split
JM 35.21 TRXSUN 35.21 TRX
Happened2026 M05 1 23:50:06 UTC
UTC Day20574
SourceOpen tx
Total Released75.25 TRX
Split
JM 37.62 TRXSUN 37.62 TRX
Happened2026 M04 28 03:31:57 UTC
UTC Day20571
SourceOpen tx
Total Released80.42 TRX
Split
JM 40.21 TRXSUN 40.21 TRX
Happened2026 M04 23 20:06:15 UTC
UTC Day20566
SourceOpen tx
Total Released85.95 TRX
Split
JM 42.97 TRXSUN 42.97 TRX
Happened2026 M04 22 16:51:06 UTC
UTC Day20565
SourceOpen tx
Total Released91.85 TRX
Split
JM 45.93 TRXSUN 45.93 TRX
Happened2026 M04 21 17:27:33 UTC
UTC Day20564
SourceOpen tx
Total Released96.62 TRX
Split
JM 48.31 TRXSUN 48.31 TRX
Happened2026 M04 6 03:35:30 UTC
UTC Day20549
SourceOpen tx
Total Released103.26 TRX
Split
JM 51.63 TRXSUN 51.63 TRX
Happened2026 M04 3 21:13:00 UTC
UTC Day20546
SourceOpen tx
Total Released90.19 TRX
Split
JM 45.1 TRXSUN 45.1 TRX
Happened2026 M03 27 22:23:54 UTC
UTC Day20539
SourceOpen tx
Total Released92.68 TRX
Split
JM 46.34 TRXSUN 46.34 TRX
Happened2026 M03 23 01:06:39 UTC
UTC Day20535
SourceOpen tx

Each row comes from confirmed LiquidityExecuted(day, totalAmount, amountA, amountB) events.

Reserve Path

Reserve tokens are inventory, not free circulation

Controller-side TRX is only half the route. The token side needs isolated inventory too, and that is why FourteenVault exists before the two execution paths receive their balances.

Reserve layer

FourteenVault backs the public liquidity route before market execution begins.

These 4TEEN balances should be read as reserve-side working inventory. They are not ordinary wallet balances and they should not be framed like freely circulating supply.

  • Vault inventory is topped into the bootstrapper path before the controller executes.
  • JustMoney and Sun.io V3 receive prepared balances only when the route is valid.
  • Reserve custody, controller TRX, and executor destinations are separate layers of the same engine.

2m 4TEEN currently shown in the reserve snapshot.

TNwkuH...2JEZTq

JustMoney path

7.2 4TEEN

Executor A takes half of the allowed release and runs the AMM-side liquidity path after its token inventory has been prepared.

TWrz68...xiHw7F

Sun.io V3 path

0 4TEEN

Executor B takes the other half and routes it through the concentrated-liquidity path with its own prepared token side.

TU8EwE...uR46xh

This is why the page should explain a route, not just print one vanity total. Reserve inventory, controller balance, and execution destinations do different jobs.

Next Step

Open the wallet when you want to wake the route yourself

The site is where you verify the state. The mobile wallet is where a real user can inspect resources, call the bootstrapper, and sign the route if the controller gate is already open.