> For the complete documentation index, see [llms.txt](https://hello-fun-1.gitbook.io/hello.fun-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hello-fun-1.gitbook.io/hello.fun-docs/risks-and-disclosures/disclosures.md). # Disclosures This page provides important information about Hello.Fun, its current functionality and the distinction between deployed features and planned ecosystem development. Users should review these disclosures together with the Risk Overview before interacting with Hello.Fun. ### Platform Function Hello.Fun provides smart contract infrastructure for creating tokens and establishing onchain markets on Robinhood Chain. The platform supports token creation, bonding curve trading, graduation into Uniswap v4 markets and permanent liquidity locking. > **Hello.Fun is also expanding through HELLO Intelligence, a suite of AI powered products designed to support creation, analysis, discovery, monitoring and project intelligence across the token lifecycle. HELLO Pilot forms part of the launch experience, while additional HELLO Intelligence products are being introduced progressively.** Hello.Fun does not guarantee the value, performance, liquidity, demand or success of any token launched through the platform. ### Current Network Hello.Fun is deployed on Robinhood Chain mainnet. Users should verify that their wallet is connected to the correct network before signing transactions. ### Current Pair Availability ETH is currently the live pairing asset on Hello.Fun. Additional pairing categories described throughout this documentation are planned and are not currently available within the deployed launch system. These planned categories include: * $HELLO * Supported tokenized stocks * Supported meme tokens Hello.Fun uses an approved pair system. Pairing assets must be supported and configured before they can be used for new launches. ### Launch Token Structure Standard Hello.Fun launch tokens use a fixed token structure. Each launch token has: * A total supply of 1,000,000,000 tokens * 18 decimals * Supply minted once at creation * No additional mint function * No burn function * No token owner * No blacklist * No privileged transfer freeze These characteristics apply to the standard Hello.Fun LaunchToken architecture. ### Token Metadata Token metadata is prepared as part of the launch process. The metadata reference written into the launch token is immutable. Creators should verify their token information carefully before launching because the metadata reference cannot be replaced after deployment. ### Market Structure A Hello.Fun launch begins on a bonding curve. For current ETH paired launches, reaching the **4.2 ETH graduation threshold** makes the launch ready to graduate. After graduation, the market transitions into Uniswap v4. ```mermaid flowchart LR A["Token Launch"] --> B["Bonding Curve"] B --> C["4.2 ETH Threshold"] C --> D["Graduation"] D --> E["Uniswap v4 Market"] E --> F["Permanent Liquidity"] ``` The 4.2 ETH threshold applies to the current ETH pair configuration. Other supported pairing assets can use their own configured graduation economics as they are introduced. The pairing asset selected for the launch remains the pairing asset of the graduated market. ### Graduation Graduation involves moving launch reserves and establishing the corresponding Uniswap v4 market. For current ETH paired launches, the launch becomes ready to graduate when it reaches the **4.2 ETH graduation threshold**. The system can attempt graduation automatically when the required state is reached. Graduation completion is also permissionless when the launch is eligible for completion. A restricted recovery path exists for a specific failed graduation state where reserves have already been swept but pool seeding has failed. That recovery path is subject to defined conditions and a delay. Eligible recovered funds are directed to the creator rather than the administrator. ### Liquidity Graduated liquidity is created using assets accumulated through the launch process. The resulting full range Uniswap v4 liquidity position is transferred to LiquidityLockerV4. The locker does not provide functions for: * Withdrawing the liquidity position * Unlocking the position * Transferring the position * Decreasing the locked liquidity * Removing the liquidity principal There is no scheduled unlock date for the graduated liquidity position. ### Liquidity Is Locked, Not Burned The graduated liquidity position is not sent to a burn address. It remains held by LiquidityLockerV4. Some third party services may not recognize a custom liquidity locker when determining whether liquidity is locked. The relevant protection is provided by the functionality of the locker contract itself. ### Residual Supply During graduation, token supply that cannot enter the pool without changing the intended opening market state can be transferred to the ResidualVault. The ResidualVault does not provide a withdrawal function. Residual supply is separate from the active Uniswap v4 liquidity position. ### Fees Hello.Fun currently has no Deployment Fee. Blockchain gas still applies and is separate from Hello.Fun trading fees. During the bonding curve stage, the trading fee structure is: * **1% Protocol Fee** * **Creator Fee** After graduation, the trading fee structure remains: * **1% Protocol Fee** * **Creator Fee** There is **no separate 1% liquidity fee** after graduation. The creator fee is established for a launch when that launch is created and does not increase later for that existing launch. ### Creator Earnings Creators can earn their configured Creator Fee from eligible trading activity. Creator Fee credits accrue through the Hello.Fun fee system and can be claimed by the creator. The 1% Protocol Fee is separate and does not form part of creator earnings. There is no separate liquidity fee that provides an additional creator earnings stream after graduation. Creator earnings do not provide ownership of the graduated liquidity position. The creator cannot withdraw graduated liquidity from LiquidityLockerV4. ### Wallet Control Hello.Fun uses wallet based interaction. Standard state changing actions require transactions signed by the user's wallet. ```mermaid flowchart LR A["User"] --> B["Wallet"] B --> C["Signed Transaction"] C --> D["Smart Contract"] ``` Hello.Fun does not hold user private keys. Users are responsible for securing their own wallets and reviewing transactions before signing them. Future autonomous products such as HELLO Paws can use separately funded wallets and user defined rules for authorized autonomous actions. This model is distinct from standard Hello.Fun wallet interactions where users authorize their own state changing transactions. ### Administrative Permissions Hello.Fun contains limited administrative roles for specific operational functions. These roles include responsibilities related to pair management, hook configuration, fee conversion and restricted graduation recovery. Administrative roles do not provide a general ability to: * Mint additional launch tokens * Blacklist token holders * Freeze launch token transfers * Withdraw graduated liquidity * Unlock graduated liquidity * Raise the fee on an existing launch * Globally pause all trading * Upgrade the deployed contracts * Take user funds * Take creator funds Administrative permissions should not be interpreted as having unrestricted control over deployed launches. ### Contract Architecture The deployed Hello.Fun contracts are non upgradeable. They do not use a proxy architecture that allows the deployed implementation to be replaced through an administrative upgrade. Hello.Fun also does not include a global administrative pause mechanism for all trading. ### Source Verification The deployed Hello.Fun contracts have source verification available through Sourcify and Blockscout. Sourcify reports full creation and runtime code matches. Source verification allows deployed bytecode to be compared with the corresponding source code. Source verification is not the same as an independent security audit. ### Audit Status The current Hello.Fun contract architecture has not completed an independent third party security audit. The current contract suite includes testing across launch lifecycle behavior, fees, graduation, liquidity locking and adversarial scenarios. Testing and source verification do not guarantee that the contracts are free from vulnerabilities. ### Market Data Hello.Fun indexes onchain activity and presents market information through its interface. This can include: * Price * Market capitalization * Rolling 24 hour volume * Liquidity * Holders * Transactions * Charts * Pair information Market information may be affected by indexing delays, infrastructure interruptions or temporary display issues. Users should not interpret displayed information as a guarantee of future market conditions. ### USD Display Values External ETH price information can be used to display market values in USD terms. These conversions are provided for display purposes. They do not change the underlying onchain denomination or settlement of a transaction. ### HELLO Intelligence HELLO Intelligence is the intelligence layer of the Hello.Fun ecosystem. It brings together AI powered products designed to support different parts of the token lifecycle and market experience. The suite includes: * **HELLO Pilot:** AI Launch Assistant that can help turn an idea into a structured Hello.Fun launch. * **HELLO Paws:** Autonomous Meme Opportunity Agent designed to identify token worthy moments and, when configured, execute launches using a separately funded wallet and user defined rules. * **HELLO Lens:** AI Token Intelligence system designed to analyze project and market information into scores, insights and risk signals. * **HELLO Mate:** Token AI Agent designed to answer questions, explain project information and help users understand token activity. * **The Scout:** AI Activity Radar designed to follow project activity, engagement, milestones and unusual movement. * **HELLO Match:** AI KOL Matching system designed to identify voices that may fit a project's narrative, category and positioning. * **Say Hello:** Project and market intelligence experience designed to bring token data, project information, market activity and HELLO Intelligence together in one place. HELLO Pilot is designed as an assisted route within the Hello.Fun launch experience. Manual launching remains available and does not require creators to use HELLO Pilot. Other HELLO Intelligence products are intended to be introduced progressively as the ecosystem expands. ### AI Generated Information Information, analysis, scores, summaries, classifications, recommendations and other outputs produced through HELLO Intelligence can be generated or assisted by artificial intelligence. AI generated information can be incomplete, inaccurate, outdated or based on imperfect source data. HELLO Lens scores, HELLO Mate responses, Scout activity signals, HELLO Match recommendations and other intelligence outputs should not be treated as guarantees of quality, legitimacy, performance or future market behavior. Users remain responsible for evaluating information before making decisions or signing transactions. ### Autonomous Actions HELLO Paws is designed to support autonomous activity under user defined rules. Where autonomous execution is enabled, actions can depend on external information, configured conditions, wallet funding and the rules selected by the user. Autonomous systems can misinterpret information, react to incomplete data or execute actions that do not produce the expected result. Users are responsible for reviewing their configuration, controlling wallet funding and understanding the actions they authorize. ### External Information HELLO Intelligence can rely on or analyze information from blockchain data, social platforms, project information and other external sources. Hello.Fun does not control all external information sources. External data can be delayed, incomplete, unavailable, inaccurate or changed by the original source. The presence of a project, token, account, signal or other information within HELLO Intelligence does not constitute an endorsement by Hello.Fun. ### $HELLO Status $HELLO is part of the planned Hello.Fun ecosystem. Planned roles for $HELLO include: * Pairing utility * Enhanced Creator Rewards * Participation in the Hello Economy $HELLO is not currently a live pairing asset within the deployed Hello.Fun launch system described in this documentation. ### Planned Hello Economy The proposed Hello Economy is designed to allocate platform revenue between $HELLO and selected Hello.Fun launches. The proposed allocation is: * **60%** to $HELLO Market Buybacks and Burn * **40%** to selected Launch Buybacks ```mermaid flowchart TD A["Platform Revenue"] --> B["60%"] A --> C["40%"] B --> D["$HELLO Market Buybacks"] D --> E["Burn"] C --> F["Selected Launch Buybacks"] ``` This revenue allocation, buyback system and burn mechanism are planned. They are not currently active within the deployed Hello.Fun protocol. ### Planned Project Selection The proposed Hello Economy includes a process for selecting Hello.Fun launches for Launch Buybacks. The planned evaluation factors are: * Volume * Holders * Bubblemaps * Tokenomics * Team * Market Cap This selection process is planned and is not currently implemented as an automated protocol system. No fixed public scoring formula, weighting system or guaranteed selection threshold is currently defined. ### Planned Pair Expansion Hello.Fun is designed to expand beyond ETH pairing. Planned pairing categories include: * $HELLO * Supported tokenized stocks * Supported meme tokens These categories should not be interpreted as currently deployed pairing options until they are introduced into the supported pair system. ### Planned Features May Change Features described as planned represent the intended direction of the Hello.Fun ecosystem. Implementation details, availability, supported assets and economic parameters may change before deployment. The current deployed functionality and future ecosystem plans should therefore be considered separately. ### No Guarantee of Token Performance Hello.Fun provides launch and market infrastructure. It does not guarantee: * Token price * Market capitalization * Trading volume * Liquidity demand * Holder growth * Creator performance * Project development * Future token value * Investment returns Past or current market activity should not be interpreted as a guarantee of future results. ### User Responsibility Users are responsible for reviewing the token, market, pair, fees, transaction details and associated risks before signing a transaction. Blockchain transactions can be irreversible. ```mermaid flowchart LR A["Review"] --> B["Understand"] B --> C["Sign"] C --> D["Onchain Execution"] ``` Users should only interact with Hello.Fun and individual token markets after understanding the relevant smart contract, blockchain and market risks. ### Final Disclosure Hello.Fun provides infrastructure for launching tokens, creating onchain markets and building an intelligence layer around the token lifecycle. Its smart contract protections can restrict specific actions, such as additional token minting or graduated liquidity withdrawal, but they cannot eliminate market volatility, smart contract risk, blockchain risk, AI generated information risk or the possibility of financial loss. HELLO Intelligence can assist with creation, analysis, discovery and monitoring, but its outputs and actions do not guarantee token quality, project legitimacy, market performance or successful outcomes. Users remain responsible for their own decisions, configurations and transactions. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hello-fun-1.gitbook.io/hello.fun-docs/risks-and-disclosures/disclosures.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.