Is PORTAL Safe? Smart Contract Security Analysis

Security Findings

1 Low2 Info

Low

Centralization Risk with Owner Privileges

L-01The contract owner, despite being a multisig, retains significant control over certain administrative functions. For instance, the owner can transfer ownership of the contract and utilize the `TokenRecovery` mechanism to recover accidentally sent ERC20 tokens. While a multisig mitigates single points of failure, the concentration of these powers still represents a centralization risk if the multisig signers are compromised or act maliciously.

IssueThe contract owner, despite being a multisig, retains significant control over certain administrative functions. For instance, the owner can transfer ownership of the contract and utilize the `TokenRecovery` mechanism to recover accidentally sent ERC20 tokens. While a multisig mitigates single points of failure, the concentration of these powers still represents a centralization risk if the multisig signers are compromised or act maliciously.

FixEnsure the multisig signers are highly trusted individuals or entities with robust security practices. Implement strict internal governance procedures for multisig operations. Consider time-locks or additional approval steps for critical actions like `transferOwnership` if the protocol's future evolution requires more decentralized control.

StatusUnresolved

Info

Dependency on External Forwarder Registry

I-01The contract relies on an external `IForwarderRegistry` for its meta-transaction functionality, specifically for overriding `_msgSender()` and `_msgData()`. The security, liveness, and immutability of this external registry are critical for the proper functioning and security of meta-transactions within the `ERC20FixedSupply` contract. A compromise or malfunction in the `IForwarderRegistry` could disrupt meta-transaction services.

IssueThe contract relies on an external `IForwarderRegistry` for its meta-transaction functionality, specifically for overriding `_msgSender()` and `_msgData()`. The security, liveness, and immutability of this external registry are critical for the proper functioning and security of meta-transactions within the `ERC20FixedSupply` contract. A compromise or malfunction in the `IForwarderRegistry` could disrupt meta-transaction services.

FixThoroughly audit the `IForwarderRegistry` contract and ensure it is deployed by a trusted entity and maintained securely. Monitor its operational status and any potential upgrade paths. Document the expected behavior and security assumptions related to this external dependency.

StatusUnresolved

Info

Criticality of Initial Token Distribution

I-02The entire fixed supply of tokens is minted and distributed during the contract's constructor via the `batchMint` function. This is a one-time, irreversible operation. Any errors in the `holders` addresses or `allocations` amounts provided during deployment would lead to an incorrect or unfair initial distribution of the token supply, which cannot be rectified post-deployment.

IssueThe entire fixed supply of tokens is minted and distributed during the contract's constructor via the `batchMint` function. This is a one-time, irreversible operation. Any errors in the `holders` addresses or `allocations` amounts provided during deployment would lead to an incorrect or unfair initial distribution of the token supply, which cannot be rectified post-deployment.

FixImplement rigorous pre-deployment checks and simulations for the `holders` and `allocations` arrays. Conduct multiple reviews of the deployment script and parameters by independent parties. Consider a dry-run deployment on a testnet with the exact parameters intended for mainnet to verify the outcome.

StatusUnresolved

Category Ratings

TechnicalLow10/10

The contract exhibits a robust technical architecture, leveraging well-tested OpenZeppelin components and a modular design with dedicated storage libraries (7.1 Architecture). Solidity 0.8.28 is used, mitigating common integer issues, and `ERC20SafeTransfers` ensures secure token operations (7.2 Code Security). Meta-transaction support via `ForwarderRegistryContext` is a valuable feature, enhancing user experience. The primary technical consideration is the reliance on the external `IForwarderRegistry` for meta-transaction functionality (7.6 External), whose security is paramount.

GovernanceMedium4/10

The economic model is straightforward, featuring a fixed supply token minted entirely during deployment, preventing future inflation (7.4 Economic). Access control is robust, with contract ownership managed by a 3/5 multisig, significantly reducing single points of failure and enhancing operational security (7.3 Access Control, 7.5 Governance, 7.8 Operations). The `TokenRecovery` mechanism provides a safeguard for accidentally sent *other* ERC20 tokens to the contract address (7.8 Operations).

UpgradesLow7/10

The `ERC20FixedSupply` contract is not designed as an upgradeable proxy, as indicated by the `is_proxy: false` flag in the provided information (7.7 Upgrades). This design choice simplifies the contract's lifecycle and inherently removes upgrade-related risks such as storage collisions, reinitialization vulnerabilities, or faulty upgrade logic. Any changes to the contract's logic would necessitate a new deployment and a migration process.

Security Checklist

3/5 checks passed

Contract VerifiedPass

Ownership RenouncedFail

No Mint FunctionPass

Liquidity LockedFail

Not a ProxyPass

Holder Composition

99.9% in top 10

0.6% in wallets99.3% in contracts

Effective Concentration40.3%

Share held by contracts — treasury, vesting, bridge or staking — is discounted against share held by wallets when the score is computed: a contract cannot decide to sell the way an anonymous holder can, though it can still be drained or voted to sell. Effective concentration is the figure the risk score is actually calculated from.

Liquidity Depth

$89.4K across 3 pairs

AerodromeUSDCanalysed$74.7K AerodromeUSDC$14.6K Uniswap v4ETH$107

The risk score reads depth across every pair. The volume figure and the volume-to-liquidity ratio elsewhere on this page describe only the pair this audit analysed, so the two are not directly comparable.

LP Distribution

Top-1 Unlocked Holder100.0%

Top-3 Unlocked100.0%

Key Addresses

2 addresses

Deployer

0x057f…e355

Unlocked LP Held By

0xb5a6…b002

No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.

What Raised This Score

6 factors

Ownership NOT renounced — strong Multisig (3-of-5)
Top-10 concentration > 30% (99.9% total → 40.3% effective; 0.6% in EOAs, 99.3% in contracts — moderate)
Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
LP top1 unlocked holder = 100.0% (independent LP — depth risk, pool = 84% of DEX liquidity)
LP top3 unlocked holders = 100.0% (independent LP — depth risk, pool = 84% of DEX liquidity)
1 Low finding(s) from audit

Each factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed

Is PORTAL Safe?

Security Findings

Centralization Risk with Owner Privileges

Dependency on External Forwarder Registry

Criticality of Initial Token Distribution

Category Ratings

Security Checklist

Holder Composition

Liquidity Depth

LP Distribution

Key Addresses

What Raised This Score

Related Audits

Would You Like a More Detailed Audit of PORTAL?