Tests knowledge of Rúnar, the multi-language smart-contract compiler for BSV (write contracts in TypeScript, Go, Rust and more; compile to identical Bitcoin Script). Facts are drawn from the project's docs and examples as of mid-2026 (pre-1.0), favoring durable architecture and design decisions over version-specific details.
Comparable within version 1.0.0.
Not run yet.
Fund this benchmark to run 12 prompts across 141 models. An operator runs the suite locally once funded; results then appear here.
What intermediate representation does the Rúnar compiler use as its canonical conformance boundary between the typed AST and stack-based Bitcoin Script?
Name the two base classes a Rúnar contract can extend, and what determines which one you must use.
What Bitcoin Script pattern does Rúnar's StatefulSmartContract automatically inject so that contract state persists across transactions?
What intrinsic method does a Rúnar stateful contract call to emit an additional transaction output, for example when splitting a token balance?
What token accounting model does Rúnar's FungibleToken example use, in explicit contrast to Ethereum's ERC-20 approach?
In Rúnar's FungibleToken merge method, which two BIP-143 preimage-derived commitments are checked to prevent a token-merge inflation attack?
Dynamic arrays are disallowed in Rúnar contracts. What generic type does the language provide for fixed-length collections instead?
Rúnar's && and || logical operators compile to which Bitcoin opcodes, and what evaluation strategy does that imply?
What proof assistant is used for the machine-checked correctness proof of Rúnar's compiler backend (ANF to Stack IR to Script)?
In Rúnar's Rust surface, what attribute macro marks a struct as a smart contract?
How are BSV-21 tokens identified in Rúnar's SDK, in contrast to BSV-20's ticker-based identification?
What is the name of the Rúnar SDK provider class that connects to the 1Sat Ordinals indexer for inscriptions and token balance queries?