Skip to content

docs: clarify intelligent contract size expectations #450

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
MuncleUscles wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs: clarify intelligent contract size expectations #450

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions pages/developers/intelligent-contracts/deploying.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,21 @@ Follow this recommended progression:
Start with CLI deployment for simple contracts, then graduate to deploy scripts as your projects become more complex.
</Callout>

## Contract Size and Packaging Notes

Intelligent Contracts are Python contracts executed by GenVM; they are not compiled to EVM bytecode. That means the usual EVM contract bytecode-size limit is not the right model when planning a GenLayer deployment.

Still keep deployed contracts reviewable and lightweight:

- Split large applications into focused Python modules or cooperating contracts instead of one generated monolith.
- Keep prompts, schemas, and fixtures concise; put bulky off-chain data behind stable URLs or content hashes when possible.
- Use deploy scripts for multi-contract or multi-step deployments so addresses and constructor arguments are recorded repeatably.
- If a contract is large because it contains mostly deterministic business logic, consider moving deterministic reads, indexing, caching, or UI-only aggregation outside consensus and only call GenLayer for decisions that require subjective or web-aware validation.

<Callout emoji="⚠️">
If a deployment fails with a payload-size, package, or RPC error, treat it as a tooling or network-specific limit and reduce the deployment artifact before retrying. Do not assume Solidity patterns such as diamond proxies are required unless you are separately interacting with EVM contracts.
</Callout>

## What's Next?

After deploying your contracts:
Expand Down
Loading