Studio Dev rejects its own current v0.3 contract during schema extraction
Environment
- Studio Dev canonical RPC:
https://studio-dev.genlayer.com/api
- Chain ID:
61997
- Observed: 2026-09-04
Reproduction
- Fetch the current Studio repository example at:
https://raw.githubusercontent.com/genlayerlabs/genlayer-studio/main/examples/contracts/llm_erc20.py
- Submit that source unchanged to JSON-RPC method
gen_getContractSchemaForCode.
Expected result
The RPC returns the contract schema for Studio's own example.
Actual result
The RPC returns an internal error before schema parsing:
invalid_contract runner malformed
The GenVM log includes:
runner load
runner: chain:0x0000000000000000000000000000000000000000:d:q805cc3mbb7k055ay5hek4sg80r2s85yyftpzrpq7g50hy1cc45g
compilation_time: 0
compiled_modules: 0
The same result occurs for a separate single-file contract using the runner pin shown in current
GenLayer documentation. It therefore occurs before user contract compilation, imports, schema
extraction, constructor validation, or deployment fee estimation.
Impact
Studio Dev cannot extract schemas from either its own current example or a separately authored
single-file contract. This blocks contract deployment, transaction execution, and fee-profile
generation against the v0.6 preview.
Request
Please verify the runner-resolution configuration behind Studio Dev and restore a runner that can
load the current Studio example. A successful gen_getContractSchemaForCode response for the raw
example above would be a sufficient first confirmation.
Studio Dev rejects its own current v0.3 contract during schema extraction
Environment
https://studio-dev.genlayer.com/api61997Reproduction
https://raw.githubusercontent.com/genlayerlabs/genlayer-studio/main/examples/contracts/llm_erc20.pygen_getContractSchemaForCode.Expected result
The RPC returns the contract schema for Studio's own example.
Actual result
The RPC returns an internal error before schema parsing:
The GenVM log includes:
The same result occurs for a separate single-file contract using the runner pin shown in current
GenLayer documentation. It therefore occurs before user contract compilation, imports, schema
extraction, constructor validation, or deployment fee estimation.
Impact
Studio Dev cannot extract schemas from either its own current example or a separately authored
single-file contract. This blocks contract deployment, transaction execution, and fee-profile
generation against the v0.6 preview.
Request
Please verify the runner-resolution configuration behind Studio Dev and restore a runner that can
load the current Studio example. A successful
gen_getContractSchemaForCoderesponse for the rawexample above would be a sufficient first confirmation.