Developer and Contributor Disclosure

Certain contributors or related wallets may interact with the protocol, public smart contracts, or interfaces in disclosed ways. Any such activity should be evaluated based on on-chain records, current contract permissions, and publicly available documentation. Contributor-held assets, if any, may be used only in disclosed ways permitted by the deployed contracts and related interfaces. Users should rely on on-chain records and current contract permissions when evaluating any such activity. Any contributor activity intended to interact with the protocol should be publicly observable through on-chain records where applicable. Automated Bot Functionality Public smart contracts may be callable by network participants; no promise is made that any person will continue operating auxiliary tools or interfaces. Protocol Automation These contracts are intended to operate according to their deployed code and publicly observable transactions. Automated contract interactions may include liquidity-related actions or other contract-defined functions. Such interactions may affect price, liquidity, and execution outcomes. The protocol includes public smart-contract functions that may be accessible to eligible participants under the contract rules. Refer to the DApp and contract documentation for details. Developer and Associate Roles Contributors or related wallets may receive or hold tokens through ordinary contract interactions, disclosed allocations, or other contract-permitted activity. Contributor-held assets, if any, should be disclosed transparently. No statement on this site should be understood as a promise of market support, value support, maintained outcomes, or similar effects. Contributors or service providers may receive token distributions in connection with disclosed development, operational, or ecosystem-related work, where applicable. Any such distributions should be disclosed transparently and evaluated based on their stated purpose, on-chain record, and current contract structure. Tokens held by any wallet may be subject to the same contract-defined mechanics that apply generally, depending on the deployed code and token design. Any contract-defined outputs, if present, depend on the deployed code, network activity, and protocol mechanics. No outcome is guaranteed. Contract behavior and any outputs depend on deployed code, network activity, market conditions, and user interaction.