Software, not an investment recommendation
Scrip provides tools for creating and operating token projects, researching public markets, and preparing content. Information, generated ideas, market listings, and example strategies are not investment, legal, tax, or other professional advice. A listing, a Scrip badge, or use of Scrip by a project is not an endorsement of that project or a guarantee of its safety.
Evaluate projects and transactions independently. Scrip does not promise returns, price support, liquidity, successful launches, or recovery of funds. Roadmap descriptions are plans and may change; they do not mean a feature is available today.
Token and transaction risks
Tokens can lose all value. Markets may be illiquid, volatile, manipulated, or affected by concentrated holdings. Smart contracts, wallets, protocols, and service providers can fail or be exploited. A transaction may execute at an unexpected price, incur fees, fail, or be irreversible once confirmed.
Check the network, token address, recipient, permissions, and complete transaction before approving it in your wallet. Testnet assets and simulated balances have no cash value and are not evidence of trading performance. Never share your recovery phrase or private key to sign in to Scrip.
AI output needs judgment
Scrip can misunderstand instructions, invent facts, reuse visual elements, or drift from a project’s identity. Market data and social references may be incomplete or out of date. Review claims, images, links, permissions, and third-party rights before using or publishing generated material. An automated check is not a guarantee of accuracy, originality, or legal clearance.
Do not submit private keys or confidential information in prompts. Submit material you are entitled to use, and do not use Scrip to impersonate people, mislead users, manipulate markets, or publish unlawful content.
What “runs on Scrip” means
An operating plan describes requested work. Execution depends on the project’s available budget, approvals, account permissions, configured integrations, and provider availability. Jobs can be held, fail, or stop. A schedule or progress indicator is not proof that content has been published; use the job status and external receipt to check completion.
Scrip does not promise that every project will continue indefinitely, that a departing operator will always be replaced, or that generated activity will produce buyers. Any future rewards, buybacks, burns, or fee-funded services depend on the mechanism actually enabled and create no promised investment return.
Stock-linked and other quote assets
Pairing a project token with a stock-linked token or other quote asset does not, by itself, give holders of the project token ownership of the referenced stock, a redemption claim, dividends, or an affiliation with its issuer. The project token and its quote asset are separate assets with separate risks.
A stock-linked token may have issuer, custody, redemption, market-hours, transfer, and geographic restrictions. Its rights and eligibility depend on its issuer’s documents. A quoted price or accessible interface does not establish that you are eligible to acquire it. Check the specific asset and applicable restrictions before using it.
Fees and available features
Review the displayed price and fee breakdown before approving a paid action. Production is priced by Scrip; a displayed production price is not a representation of a provider’s wholesale cost. Network, trading, pool, and asset-specific fees may be separate. An estimate is not a guarantee of the final network cost or execution price.
A development or demonstration screen does not activate a mainnet market, publishing connection, fee collector, or recurring purchase. Only the feature’s actual status, approvals, and receipts establish what has happened. Provider outages, insufficient funding, or revoked permissions can interrupt service.
Platform authority, custody & control
Platform configuration and a token launch are separate transactions. An admin wallet may control fee destinations, platform rules, and settings allowed by the underlying protocol. The wallet receiving fees may also hold rights to liquidity-provider fees. Those rights do not by themselves allow withdrawal of permanently locked liquidity. Check the actual authorities and configuration onchain.
Scrip’s platform setup does not request or store your admin private key. Other project or bot features may have different authority models, which must be shown before enabling them. A login session, chat membership, generated takeover wallet, or operator badge is not permission to spend another wallet’s funds or take over a token. Approve each necessary transfer of authority separately.
Bots, subagents & scheduled work
A bot can be invited into a chat without giving every participant administrative authority. Instructions, uploaded files, scraped posts, and market data may contain misleading information or malicious instructions. Treat research as unverified input. Review the identity, permissions, budget, and approved project brief used for each action.
Queued posts and subagent plans can become stale. Automated checks cannot guarantee that a meme will retain its meaning, a claim remains accurate, or a connected account will stay available. Unattended work depends on the scopes and budget you authorized. Pausing a project may not cancel a job or post already accepted by an external service.
Data, providers & public records
Scrip processes account identifiers, wallet addresses, signed acknowledgments, project briefs, uploaded or generated material, job results, budgets, and operational records to provide the workspace. Connected chat integrations also process the identifiers and instructions needed for the requested bot actions. Do not put sensitive personal information, credentials, or recovery phrases into prompts or public chats.
Hosting, database, storage, AI generation, blockchain RPC, and connected social or chat providers process the data needed for their part of an action. Providers may apply their own terms and retention practices. Disconnecting a wallet or signing out does not delete saved projects, acknowledgment records, public posts, or blockchain history. A wallet address can be linked to other public activity; Scrip does not promise anonymity or end-to-end encryption.
A dedicated privacy-request contact and a complete retention and deletion policy still need to be published. This notice does not represent those arrangements as already available. Do not submit personal or confidential material on the assumption that an automated erasure process exists.
Wallet sign-in and your acknowledgment
Connecting a wallet shares its public address. Signing the Scrip login message proves control of that address and opens a time-limited browser session for its workspace. The login signature does not submit a blockchain transaction, charge a network fee, transfer funds, or grant token spending approval. Onchain actions require separate approval.
Scrip stores the signed login message, public wallet address, notice version, and acknowledgment time to record this sign-in and risk acknowledgment. A necessary session cookie keeps you signed in. Project content and job requests are stored to provide the workspace and are sent to the providers needed for an action you request. Blockchain addresses and transactions are public; wallet sign-in is not a promise of anonymity.
The current wallet sign-in message records your acknowledgment of this notice and agreement to the linked Terms of use, with a hash of both documents. Earlier acknowledgments remain records of the versions actually signed. Your acknowledgment does not waive rights that cannot be waived under applicable law, create a promise of returns, or establish permission to use a restricted asset. This risk notice does not contain an arbitration agreement or class-action waiver.