Actual version status
The new multiple-fixed-wall policy is being implemented and validated. It has not been redeployed on Sepolia. The connected dapp still uses an earlier version with 0.30% LP fees.
This guide edition is dated September 10, 2026. It relies on repository sources and reports, without performing a new real-time network attestation.
Three distinct states
| Scope | State described by this edition |
|---|---|
| Requested specification | Buy 3% team; sell 15% (12% walls, 3% team); LP fee 100 = 0.01%; target at time T; fixed walls; 7k base to calibrate in ETH |
| Solidity workspace | New implementation and API under development; compilation reported, full validation still in progress |
| Sepolia connected to the dapp | Old version: buy 15%, sell 3%, LP fee 3000 = 0.30%, with V2 registry and replaceable modules |
The new tax allocation replaces the allocation in code revision 991fca9 cited in the sources. That revision’s results do not validate this change. Changing local sources does not change already deployed contracts. Synchronizing documentation does not move funds from an old pool.
What historical reports attest
The Sepolia report describes deployment of a previous version, runtime and connection checks, acceptance-test purchases and sales, wall placement and checks that ineligible actions were rejected.
This evidence belongs to that version. It does not automatically test the tick index, preservation of multiple walls, their remainders or interfaces for the new policy.
Test counts published in roadmapdev.md and older reports are therefore not displayed as validation counters for the current workspace.
What does not constitute full validation
Successful compilation verifies bytecode production. Alone, it does not demonstrate accounting invariants, the behavior of a set of crossed walls, frontend consistency or a transaction on the selected network.
Likewise, comparing runtime hashes does not mean sources were published on an explorer. Automated frontend tests do not replace acceptance testing with a real browser or mobile wallet.
Outstanding conditions
The new version needs its own scenario, invariant, integration and deployment results. Compilation and initial targeted tests were reported during writing; they do not complete the full campaign. The 7k base calibration, linked libraries, ABIs and frontend views must be consistent with the final results.
At revision 991fca9, the full Solidity suite has 133 passes and 15 failures out of 148 tests. The 7 targeted multiple-wall tests pass in a separate campaign. These results and limitations appear in the published state report.
Before production opens, operational validation, an independent strict-burn and permissions review, wallet workflows, aggregator compatibility and absorption in a network environment or canonical fork also remain to be established.
This guide does not declare the project ready for mainnet.
Which source to follow
The starting point is the French report for revision 991fca9. Its banner on the new revision takes precedence over historical descriptions below it.
Public manifests under contracts/deployments/ identify deployments; their addresses and metadata must be compared with on-chain state. The guide does not manufacture a manifest for an unreleased version.
The Sources page explains the reading order and documents that have become historical.