Write your first HybridScript
A small language for deterministic computation, explicit capabilities, and inspectable state transitions.
Language reference 0.1 · preview
HybridScript is Python-derived, but it is not a general Python environment. The reference interpreter walks a validated syntax tree; it does not execute CPython bytecode. This manual documents the hybridscript-0.1-preview profile (profile version 0.1.0). Documentation version 0.1 does not mean that every target deployment enables that runtime.
This section explains program behavior. The API reference remains authoritative for requests, authentication, publication, deployment, and execution access. SDKs, supported installation packages, and GitHub release downloads are a separate forthcoming workstream; this manual does not announce a library release.
A complete example
This example adds an integer to private contract state and emits a demonstration event. It does not transfer funds. Entrypoints take exactly two arguments: the supplied context and input value.
from hybrid import contract, state, event
@contract.entrypoint
def accumulate(ctx, payload):
previous = state.get("total")
if previous == None:
previous = 0
total = previous + int(payload["amount"])
state.put("total", total)
event.emit("demo.accumulated", {"total": total})
return {"total": total}
Declare the package boundary
The manifest must identify the exact profile, entrypoints, execution budget, and capabilities. This JSON object is the manifest representation used by the registry. The source tooling also reads equivalent fields from hybrid.toml.
{
"profile": "hybridscript-0.1-preview",
"entrypoints": [
"accumulate"
],
"execution_limit": 50000,
"capabilities": {
"state": [
"private:read",
"private:write"
],
"events": [
"demo.*"
]
}
}Check the outcome
These results were checked with the pinned reference interpreter. Validate the source, build the package, and simulate with the declared capabilities before requesting an enabled execution. A simulation result is not a deployed contract or a payment.
| Item | Value |
|---|---|
| Input | {"amount":7} |
| Initial state | {"total":5} |
| Output | {"total":12} |
| Resulting state | {"total":12} |
| Event | demo.accumulated with {"total":12} |
From source to evidence
| Step | What to check |
|---|---|
| Validate | Syntax, imports, entrypoints, and profile diagnostics. |
| Package | Source, manifest, policy, capability, and schedule commitments. |
| Simulate | Expected output, state transition, events, and rejected cases. |
| Integrate | Use the current Execution Studio API contract and admitted environment. |
| Inspect | Retain the receipt and any independently verifiable node attestation. |