4TEEN Liquidity Execution bootstrapAndExecute() · Controller History · Fully On-Chain

Public execution point for the 4TEEN liquidity path.

This page is not a fake dashboard. It is the live execution surface for the 4TEEN liquidity system. The widget sends the real bootstrap-and-execute transaction through the executor layer, while showing controller-side history for liquidity execution and incoming TRX.

In the 4TEEN architecture, liquidity does not move directly from user purchase into DEX pools. TRX first accumulates in the liquidity controller, daily release follows contract rules, and execution is pushed downstream through the liquidity execution stack. What you see here is the practical public entry point into that system.

Execution Entry

bootstrapAndExecute()

The widget now triggers the executor-side bootstrap-and-execute flow instead of a shallow controller-only call.

Controller Role

Accumulation + daily release logic

The controller remains the visible liquidity accumulation layer and the balance base for the daily release rule.

Execution Targets

JustMoney + Sun.io

Liquidity execution is routed across supported DEX paths rather than treated as one opaque action.

Visibility

Executions + TRX received

The module surfaces recent controller events so liquidity behavior stays publicly readable and verifiable.

Source of Funds

TRX from direct minting

Liquidity funding begins with the liquidity-designated share of direct protocol purchases

Daily Rule

6.43%

Released once per UTC day from controller balance under on-chain rules

Execution Model

Permissionless

Anyone with a connected wallet can trigger the flow when contract conditions are satisfied

How the flow works

Controller first. Execution downstream.

1

Direct-buy TRX enters the liquidity path

FourteenToken forwards the liquidity-designated share of user purchase value into the liquidity system instead of sending it straight to DEX pools.

2

TRX accumulates inside FourteenLiquidityController

The controller becomes the visible holding layer for liquidity-side TRX and the contract base for the daily release rule.

3

The page triggers bootstrap-and-execute

The connected wallet sends a real on-chain transaction through the executor path, not a fake backend request.

4

Liquidity is routed through the downstream stack

Bootstrap preparation and execution continue across the deeper liquidity architecture instead of stopping at one controller action.

5

Controller-side history remains publicly readable

Recent Liquidity Executed and TRX Received events are still surfaced here so users can inspect what the system has been doing.

What this page really is

Not just a stats page

Live wallet-based execution surface
Controller summary and recent activity view
Recent liquidity execution history
Recent TRX received history
Public entry point into the downstream liquidity chain

What stays true

The liquidity model is still rule-based

Execution follows on-chain conditions
Release is tied to daily controller logic
The process is permissionless rather than private-admin only
Recent behavior can be inspected through public event history

Important: this page is the practical execution gate, but it does not change the architecture. Controller accumulation, rule-based release, and downstream execution still remain separate roles in the liquidity system.

Why it matters

One click here can start a real on-chain liquidity cycle.

The value of this page is not cosmetic. It exposes the execution gate for the liquidity path while preserving public visibility into controller-side behavior. That makes the system easier to understand, easier to monitor, and harder to fake.

Liquidity Execution FAQ

Quick answers before using the execution page

Question

Does this page call the controller or the executor?

The execution button now calls the executor-side bootstrap-and-execute function, while the visible history on the page is still based on controller-side event reading.

Question

Why does the page still say controller?

Because the controller remains the accumulation and event-visible liquidity layer. The execution surface now reaches deeper into the downstream stack, but the controller is still part of the operational reading model.

Question

Do I need a wallet?

Yes. Reading the page is public, but triggering bootstrap-and-execute requires a connected wallet capable of sending the transaction.

Question

Can I verify what happened after execution?

Yes. The page exposes recent events and transaction references so the recent liquidity cycle can be checked directly on-chain.