Script

Two AI agents can use the same model and still behave differently. In Script, an agent’s personality is defined by its system prompt. Its tools determine the custom capabilities available to it, while its memory holds historical context and storage. The model architecture and weights also influence the agent’s technical configuration. These components are packaged and inscribed together, making each Scribe more than a model name or a prompt stored in a separate database. Script brings the agent’s defining components into one on-chain record. scriptagent.app/

Script does not rely on manually assigned NFT traits to determine rarity. Instead, it calculates rarity using nine on-chain attributes: Model, runtime, model weights, personality, tools, memory, birth number, Autograph status, and verification status. These attributes describe both the agent’s technical configuration and its position within the ecosystem. As new Scribes are created, the circulating supply changes, and the ecosystem’s overall rarity scores update accordingly. An agent’s rarity is therefore connected to its actual attributes and the changing supply, rather than a fixed collection of manually assigned traits. scriptagent.app/

We bought back and locked app.streamflow.finance/contr…

Script introduces an on-chain ownership and royalty mechanism called the Autograph. When a model is used to create its first Scribe, that Scribe holds the model’s Autograph. If another user inscribes a new Scribe using the same model, a royalty of 0.01 SOL is paid to the Autograph holder. The Autograph is also tradable. If ownership changes, future royalties go to the new owner. This connects model provenance to a defined royalty mechanism, giving the original model’s first Scribe an economic role in subsequent creations. J1DUE6yxhWsfh1o8eyLtBpuGWJ6os7pCV7huwMhVpump scriptagent.app/

Buy back and burn done app.streamflow.finance/token…

Script is designed to execute AI agents on the user’s device rather than rely on a dedicated backend to run them. It uses browser technologies such as WebGPU and WebAssembly to execute the agent locally after downloading and verifying its files. That changes the execution model. The agent’s code and supporting files come from Solana, while the browser handles execution. No dedicated agent server or paid AI API key is required for this process, although actual performance depends on the model and the user’s device. J1DUE6yxhWsfh1o8eyLtBpuGWJ6os7pCV7huwMhVpump scriptagent.app/

How can you verify that an AI agent’s files have not been changed? J1DUE6yxhWsfh1o8eyLtBpuGWJ6os7pCV7huwMhVpump Script uses SHA-256 cryptographic hashes to verify its files against their recorded on-chain hashes. When a user accesses an agent, the application downloads its data from a Solana RPC node and checks the files before execution. If a file does not match its expected hash, the verification fails. The point is simple: users can verify the integrity of an agent’s files instead of having to trust that a server is serving the original version. scriptagent.app/

Script is live. BurJ1DUE6yxhWsfh1o8eyLtBpuGWJ6os7pCV7huwMhVpump Create AI agents, inscribe them on Solana, and run them directly in your browser. Scriptagent.app

Script brings together on-chain AI storage, cryptographic verification, browser-based execution, model royalties, and dynamic rarity. It’s building an environment where AI agents have permanent on-chain records instead of depending entirely on centralized hosting. AI agents are evolving. Script is building a different foundation for how they’re created, stored, verified, and owned. Follow to keep up with the project.

Two Scribes can use the same model but have different configurations. One might have a more complex personality, additional tools, different memory, or different model weights. Script records these components as part of each agent’s on-chain identity. This makes a Scribe more than just an AI model or a chatbot with a custom prompt.

Every Scribe is evaluated using nine on-chain attributes: • Model • Runtime • Model weights • Personality • Tools • Memory • Birth number • Autograph status • Verification status These attributes determine its rarity. Unlike manually assigned NFT traits, Script’s rarity system updates as new Scribes are created and the circulating supply changes.

Script has an interesting economic mechanism for AI models. The first Scribe created using a particular model receives that model’s Autograph. Whenever someone creates another Scribe using the same model, a royalty of 0.01 SOL goes to the Autograph holder. The Autograph is also tradable. If ownership changes, future royalties go to the new owner.

Once a Scribe is inscribed on Solana, nobody can modify or delete its recorded contents. Its code, personality, tools, memory, and model weights remain part of its permanent on-chain record. This is one of Script’s defining principles: an agent shouldn’t depend entirely on its creator or a centralized company to preserve its original files.

Script doesn’t require a dedicated backend server to run its agents. After downloading and verifying a Scribe, the browser executes it locally using technologies such as WebGPU and WebAssembly. This means users don’t need a paid AI API key to run an agent through Script’s intended execution model. The agent’s files live on Solana. Its execution happens in the browser.

Putting files on-chain is one thing. Making sure the files haven’t been altered is another. Script uses SHA-256 hashes to verify every file against its original on-chain record. When a user accesses a Scribe, the browser downloads its files from a Solana RPC node and checks their hashes before execution. If a file has been tampered with, its hash will not match.

Solana transactions have size limitations, making it impractical to write large agent files in a single transaction. Script solves this by splitting the agent’s files and model weights into 960-byte chunks. These chunks are streamed through individual Solana transactions until the agent’s components are inscribed. This is how Script handles the storage of an entire AI agent on-chain.

It takes more than uploading a file. Script first packages an agent’s components into a standardized folder structure. Each file receives a SHA-256 cryptographic hash, which serves as its verification reference. The protocol then creates a birth record containing the agent’s identity and manifest before inscribing its files on Solana.

Most traditional AI agents depend on centralized infrastructure. Their files are hosted on servers, and their operations often require API access from providers such as OpenAI or Anthropic. If the provider shuts down access or the hosting infrastructure disappears, the agent may stop working. Script is designed to reduce these dependencies by making the agent’s core components permanently available on-chain.

Script is a fully on-chain, decentralized AI agent protocol built on Solana. It allows AI agents, called Scribes, to have their code, personality, tools, memory, and model weights inscribed directly onto the blockchain. Instead of relying on a company’s private servers to store an agent’s essential files, Script puts those files on-chain.

Script launches today. We're bringing a new approach to AI agents on Solana, where their code, personality, tools, memory, and model weights are stored directly on-chain. No centralized hosting. No paid AI API keys. Before launch, here's everything you need to know about what we're building and how Script works. A Thread.