Skip to content

Remediation History

The current source contains an unusually detailed change and audit-fix history. The list below summarizes the material issues rather than reproducing every source comment.

  • Fixed buy/sell tax detection so pair fee exclusions did not accidentally disable all trading taxes.
  • Prevented privileged pre-trading pair sales while still allowing required wallet-to-wallet launch distribution.
  • Replaced an unreliable manual trading-enable step with one-way automatic activation on the first real trade.
  • Added bounded max-wallet and max-buy configuration ranges.
  • Wrapped router swaps in try/catch so a swap failure does not intentionally revert the user’s sell.
  • Added an emergency swapEnabled control that pauses the auto-cycle without pausing buying or selling.
  • Added explicit failure events for token-to-BNB swaps and liquidity addition.
  • Excluded the pair, token contract, marketing wallet and other non-holder system addresses from dividends.
  • Added rollback-safe accounting when automatic BNB delivery fails.
  • Deferred reflection BNB when no eligible holders exist instead of losing or misallocating it.
  • Preserved the hold timer for already-qualified holders who add to their position.
  • Removed a router swap from the ordinary transfer-side cleanup path, reducing gas and external-call exposure.
  • Added holder-cycle estimates and a larger bounded batch ceiling for operational scaling.
  • Implemented true burn accounting through _burn.
  • Added owner-only manual burn from the owner balance.
  • Corrected liquidity retry accounting so already-swapped portions are not double-counted.
  • Sent tax-generated LP tokens to the dead address.
  • Added zero-address checks for critical constructor and update parameters.
  • Restricted the marketing recipient to an externally owned account in the supplied source.
  • Separated fee, limit and dividend exclusions.
  • Added transparent events for material administrative changes.

The current integrated source also documents staking-controller updates, vault registration and emergency vault recovery events. The staking system has its own controller, vault, adapter and upgradeability security model described under Staking Protocol.

Summaries can omit edge cases. Review the verified deployed source, current owner, exclusions, thresholds and transaction history before relying on any specific control.