Smart Contract Analysis Statement

Contract Analysis

The FlourYieldToken contract implements an ERC20 token with a fixed supply cap, burnable balances, EIP-2612 permits, a pause switch that stops transfers and mints while still allowing burns, and two owner-only rescue paths for stuck ERC20 and native HYPE. The design follows common patterns on Ethereum and the verified source matches the deployed bytecode exactly, but a few areas need attention:

• The owner is a single externally owned account, so every privileged action depends on one private key. A leaked or coerced key directly enables a 50 percent supply dilution and an indefinite market freeze.
• Ownership transfer is a single transaction with no acceptance step, which means a clipboard mistake on transferOwnership permanently relocates every admin power to the wrong address with no recovery path.
• There is no timelock on mint, pause, unpause, rescueERC20, sweepNative, or transferOwnership, so holders have no advance notice and no time to react before an admin action settles in the same block.
• The pause hook stops transfers and mints but lets burns through, including the allowance-based burnFrom path. An address that already holds a stale approval can therefore destroy a holder's balance during a pause, while the holder cannot move the same tokens out of harm's way. Choose the pause semantics deliberately and apply them consistently to burnFrom.

Ownership Privileges

The ownership of the contract has been set to an externally owned account at deployment and has not been renounced. The owner retains full privileges including:

• Minting up to the immutable cap of 1.5 billion FYT, which at the time of review represents room for another 500 million FYT on top of the 1 billion already in circulation.
• Pausing every transfer and every mint with a single transaction, with burns still allowed during the pause so holders can always exit by destroying their own tokens.
• Rescuing any other ERC20 the contract happens to hold to an arbitrary recipient, with the only restriction being that the contract refuses to drain its own FYT.
• Sweeping any native HYPE held by the contract to any address, although the contract has no receive function and is therefore unlikely to ever hold native balance in normal operation.
• Ownership cannot be split into separate pauser, minter, or rescuer roles in the current design; everything is held by the same key.
• There is no two-step ownership transfer, so the new owner does not have to accept the role before it takes effect.
• There is no on-chain timelock between an owner signature and its effect, so every admin action settles in the same block.
• The supply cap is enforced by an immutable value baked into the bytecode at deployment and cannot be raised by the owner under any circumstances.

Security Features

The contract implements several positive security features:

• A hard supply cap of 1.5 billion FYT enforced by ERC20Capped, so even a compromised owner key cannot mint beyond the documented maximum.
• The pause path blocks transfers and mints but explicitly allows burns, which preserves the right of holders to exit by destroying their own balance even while the rest of the market is frozen.
• EIP-2612 permits with EIP-712 typed data, including chain id in the domain separator, which prevents cross-chain replay of signed approvals and lets integrators avoid the classic approve-and-transferFrom race.
• Custom errors throughout the user code instead of revert strings, plus a clean inheritance chain built entirely on OpenZeppelin v5 components, which keeps the audit surface small and the gas footprint low.

Note - This Audit report consists of a security analysis of the FlourYieldToken smart contract. This analysis did not include economic analysis of the contract's tokenomics. Moreover, we only audited the main contract for the FlourYieldToken team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.