Contract
BidWall
BaseScan
Verify BidWall
Simple Live View
Progressive Bid Wall
$ODAI uses Flaunch's Progressive Bid Wall. Treasury and BidWall are separate by design. PBW is funded automatically by trading activity, not by manual treasury deployment, and every 0.1 ETH forms a new bid wall below spot. This page exists to show that structure live on-chain.
Proof
Verify On-Chain
If you want the shortest path to proof, use these explorer surfaces. They cover the vault, the treasury, the latest full trigger, and the live transfer feed.
4 direct proof surfaces
Open the contract, treasury, trigger trail, and transfer feed directly on Base. This section is here to reduce proof to the shortest possible path.
Base Mainnet
Separate Treasury
Live Trigger Trail
Treasury
Treasury Path
Separate ledger
Verify Treasury
Execution
Latest Full Trigger
Threshold event
Verify Latest Trigger
Transfers
Live Transfer Feed
Current movement
Verify Live Transfers
Fee Flow
How Flaunch Feeds BidWall
This is the path in one line: trades happen, a slice of the fee goes to PBW, the bucket fills, the trigger hits, and buy orders appear below price.
1% swap fee
20% of fee -> PBW
0.1 ETH trigger
01
People Trade
Every $ODAI trade on Flaunch starts the flow.
02
Fee Splits
A small part goes to Treasury and a small part goes to PBW.
80% Treasury
20% PBW
03
Bucket Fills
The PBW side collects in flETH. It is a bucket, not a parked $ODAI wallet.
04
Trigger Hits
When the bucket reaches 0.1 ETH, BidWall fires by itself.
auto execute
05
Buy Wall Shows Up
That value turns into buy orders below price, which helps support the floor.
Main line shows the PBW path. Treasury is separate and is not the BidWall contract.
Next Trigger
When It Fires Next
Next Auto-Buy
This bar shows the live bucket. After BidWall fires, the bucket can go back to zero.
That does not mean the system is off. It just means it spent the bucket.
Triggers at 0.1 ETH
Accumulated: -- ETH
|
Remaining: -- ETH
|
Balance is the running module 0.1 ETH accumulation
Recent PBW Transactions
- Loading recent PBW transactions...
Simple Version
How It Works
Short version: trading fees fill a bucket, the bucket hits 0.1 ETH, and BidWall auto-places buys below market.
1
Trades Fill The Bucket
Every $ODAI swap adds to the fee flow. The PBW side collects in flETH,
so the BidWall is not sitting there with a preloaded bag of $ODAI. This page shows
both resting flETH and native ETH at the BidWall contract
0x66681f...8aa8 ↗.
That balance can drop back to zero right after a trigger.
2
0.1 ETH Hits
When the bucket reaches 0.1 ETH, BidWall fires automatically. No one has to push a button.
3
Buy Wall Appears
That value is placed into buy orders below price. More trading means the bucket fills more often, so support can rebuild faster over time.
Current State
Simple Read
This is the fast answer. Is the bucket holding anything right now? When was the last full trigger? And what does this page prove on-chain?
Visual
Floor Ratchet Effect
Each bid wall trigger creates a new price floor. Subsequent walls stack above previous ones, illustrated below as a step-function floor that only moves upward.
Structural Floor Build-Up
Illustrative, not to scale
Technical View
Detailed Metrics
This is the deep-dive version for anyone who wants the raw numbers, sources, and freshness metadata.
Fund Metrics
Current trigger asset
--
Current native ETH
--
Lifetime PBW (Flaunch)
--
Trigger asset USD (est.)
--
Latest flETH movement
--
Last full trigger
--
Trigger threshold
0.1000 ETH
Progress to next
--%
Native balance source
--
Trigger asset source
--
ETH/USD source
--
Flaunch source
--
Events source
--
Activity scope
--
Data age
--
Snapshot state
--
Protocol Parameters
Protocol
Flaunch V1.2
Chain
Base (8453)
Fee rate
1% of swap volume
Order type
Limit-buy (auto)
On-Chain Activity
Recent Contract Transfers
These are the latest transfers touching BidWall on Base. You can switch between all tokens and only $ODAI. If the $ODAI view is blank, that can still be normal because the bucket fills on the flETH side first.
Recent Transfers
- Loading recent activity...
On-Chain
Addresses To Watch
Core contract
BidWall
0x66681f10BA90496241A25e33380004f30Dfd8aa8
Progressive Bid Wall contract on Base. This is the support module, not the treasury.
View on Basescan ↗
Separate path
Treasury
0x14926224168492CdC06461713b3011cd25d8C901
Treasury-side actions stay separate from the wall and can be inspected on their own ledger.
View on Basescan ↗
Holder path
Creator-side Holder
--
Tracks the creator-side holder separately from the wall bucket and treasury route.
Token
$ODAI
0x0086cff0c1e5d17b19f5bcd4c8840a5b4251d959
Fair launch, fixed supply, and the asset that receives support below spot once PBW fires.
View on Basescan ↗
Trigger asset
flETH Bucket
0x000000000D564D5be76f7f0d28fE52605afC7Cf8
The fee side fills in
View on Basescan ↗
flETH. Each 0.1 ETH threshold turns into fresh bid support below spot.Protocol
Flaunch V1.2 · Uniswap V4 hooks · Base Mainnet
Launch
Fair launch · 100B fixed supply · 0% pre-mine
Read this right
BidWall and Treasury are separate. BidWall holds the fee-funded buy-support module, Treasury is not the wall.
Different Model
Why PBW Is Not A Treasury Buyback
The common critique is valid for projects that spend treasury manually trying to support price. That is not the $ODAI structure. Progressive Bid Wall is a separate Flaunch path funded automatically by trading activity.
Treasury Buyback
Manual Capital Decision
A team chooses to spend treasury capital on market buys. That is a discretionary strategy choice.
Flaunch PBW
Automatic Market Structure
$ODAI uses Flaunch's PBW path. Fees route into flETH, and each 0.1 ETH trigger forms a new bid wall below spot.
Design Outcome
Separate Objective
Treasury stays separate for building and growth. PBW handles the structural support path on its own logic.
Structural conclusion
Different mechanism. Different objective.
The right comparison is not "$ODAI versus treasury buybacks." The right comparison is discretionary treasury spending versus a separate, protocol-level support path. $ODAI uses the second model.
FAQ
Common Questions
These are the three biggest misunderstandings people keep having.
Why is the $ODAI feed empty?
Because BidWall does not fill as a parked $ODAI bag. Fees build up in flETH first,
so the $ODAI list can stay blank between triggers.
Does zero balance mean PBW is off?
No. It means the bucket is empty right now. It does not prove the system never fired before.
What should I verify on-chain?
Check the BidWall contract, the flETH bucket, and the last full trigger.
That tells the real story faster than a raw $ODAI transfer scan.
Investor Tools