# AgenticPad

**AgenticPad is an asset issuance and trading protocol with Agent ID as its participation gate, built for direct execution by each user's Agent.**

AgenticPad aims to build a fairer, more transparent on-chain environment for real users and their Agents. Identity verification and fair-launch rules support verifiable participant identities and traceable trading activity. Users work through their own Agents to launch assets, trade and manage liquidity.

To launch, give your Agent a name and symbol; it returns the confirmed token contract address (CA). To trade, provide the CA and a buy or sell intent. Metadata and a first buy are optional. You can learn about the project without installing or logging in to a wallet.

## Participation rules

Contracts check the eligible Agent ID bound to each participating wallet. Automated trading follows the same identity and launch rules.

- The fair-launch period lasts 192,000 BSC blocks, about 24 hours. Ordinary pool buys have a cumulative 0.2% supply allowance per wallet and token during this period.
- The Creator's first buy in the creation transaction has a separate 2% supply cap. Later Creator buys use the ordinary allowance.
- Recommended buy budgets are 0.01 BNB for an ordinary buy, 0.001 BNB for a small buy, and an optional 0.1 BNB Creator first buy. Launch costs an additional 0.001 BNB, plus gas.

Use the user's amount or an already authorized strategy. An omitted first buy stays zero. See [launch](launch.md) and [trade](trade.md) for cumulative accounting, live quotes and wallet authorization.

## Project economics

Production launch parameters are 1 billion tokens, initial tick -191200 (about 5 BNB fully diluted value), a 0.001 BNB launch fee, and a 1% pool trading fee. Initial liquidity uses the new project token alone and needs no paired BNB deposit. That initial LP is permanently locked. Graduation tracks whether WBNB principal in the initial locked position reaches 10 BNB; trading stays in the same pool and the fair-launch period continues on its own schedule. Personal liquidity positions stay separate, and their owners can add, increase, reduce and collect their positions.

## Revenue connected to AGENTIC

| Revenue source or position | Allocation |
| --- | --- |
| Initial locked-LP trading fees, first-release rule | 70% Creator, 30% protocol |
| Personal-LP trading fees | Belong to the position owner |
| Launch fees | Protocol treasury income |
| Protocol treasury income, for each asset | 80% buyback budget, 20% operations budget |

The fee split is snapshotted when each initial position is locked. The Locker can set the split for future launches. The treasury's 80/20 allocation is fixed in the contract.

Creator fees go to the recorded identity-qualified Creator address in the original project token and WBNB. Collection does not require converting them into a platform token.

Agentic (AGENTIC) is the platform token. It uses the same issuance template and Agent ID participation rules as other protocol tokens. AGENTIC has been issued on BSC at `0xd1Ab31ebeDCB6177E17891d7CE3331E61D5c15bC`, and the Vault has bound it as the platform-token target. This binding can be set only once. Buyback budgets are executed in batches: protocol assets are converted through the supported routes, AGENTIC is acquired, and the resulting AGENTIC is sent to the fixed dead address. Protocol usage funds these buybacks; sending tokens to the dead address retires them from circulation while the token's totalSupply remains unchanged.

## Auto buybacks

AgenticPad uses keeper-triggered batches to execute its on-chain buyback policy. Protocol revenue funds the Vault's buyback budget. An authorized keeper submits each batch; the Vault enforces the available budget and its price checks, buys AGENTIC, and sends the purchased tokens to the fixed dead address in the same transaction. Funds remain under the Vault's rules throughout execution.

The [verified RevenueVault contract on BSC](https://bscscan.com/address/0x9226Cf108683513B761D5d7a11345F88FFedb465#code) contains the allocation, conversion, buyback and retirement logic. Read `platformToken`, `buybackBudget`, `keeper` and `totalRetired` for live state; `Converted` and `Retired` events record completed execution. The platform-token target is AGENTIC at the address above.

## Deployment

Mainnet contracts are deployed, and AGENTIC has been issued and bound to the Vault. The production configuration contains the official BSC mainnet addresses. Read live contract state before use; `prepare launch` checks the launch gate, wallet whitelist and configuration. Start with [the Skill](../SKILL.md) for operations and [installation and CLI usage](../../../docs/USAGE.md) for the kit.