Skip to content
RISCy Docs

Smart Contracts

RISCy Network runs a general-purpose RISC-V virtual machine, so contracts are compiled to standard RISC-V bytecode rather than a proprietary or EVM-specific format. If your language can target RISC-V, it can run on RISCy.

Supported languages

  • Rust — primary, first-class target.
  • C — supported via a RISC-V toolchain.
  • Zig — supported via its RISC-V backend.
  • Anything else that compiles to RISC-V.

SDKs, standard libraries, and contract templates are under active development. The commands below are placeholders and will be finalized as tooling ships.

The contract model

RISCy inherits Nexa’s UTXO ledger, so contract execution follows a UTXO/script model rather than a single global-state account model. Practical consequences:

  • Transactions can be validated in parallel — no global-state bottleneck.
  • Contract logic is enforced through Pay-to-Script-Template outputs (inherited from Nexa).
  • Native tokens / groups are available at the base layer (inherited from Nexa).

A detailed explanation of how the RISC-V VM maps onto the UTXO model is TBD and will be documented here.

Workflow (preview)

The intended developer flow:

  1. Write your contract in Rust, C, or Zig.
  2. Compile to RISC-V bytecode.
  3. Deploy the contract to RISCy.
  4. Interact by sending transactions that invoke it.

Compile

Terminal window
# Coming soon

Deploy

Terminal window
# Coming soon

Interact

Terminal window
# Coming soon

Fees & builder rewards

RISCy is designed so builders can capture up to 70% of the fees that their contracts generate, paid directly on-chain. Exact mechanics, eligibility, and payout schedule are TBD and will be documented here.

The native coin used for fees is RISCY.

Next steps