Contribute
Each participant submits a positive number. The procedure keeps inputs hidden until their authorized release.
RO-KA ENGINE · SOLANA IMPLEMENTATION
Deterministic by design.
Verifiable on Solana.
Participants supply hidden numbers. One fixed rule determines the winning position. Solana binds that result to a wallet and the digital prize.
Current preview: retained evidence. Hosted execution is not active.
Participant inputs, no RNGOne result ruleWinner-bound settlementIndependent verification
01 / RO-KA ENGINE
The result follows the inputs.
RO-KA replaces a random-number draw with a deterministic calculation. The same accepted inputs always produce the same winning position.
Aggregate
The engine processes contributions in their assigned order and updates the running state.
Resolve
The aggregate maps to one position. That position is bound to the participant’s wallet for settlement.
The rule, with a worked example
For N participants and aggregate D, Winner Position = (D − 1) mod N + 1. Positions are numbered from 1 to N; an exact multiple of N selects position N.
Illustrative calculation only. No transaction, prize or benchmark is created. This example does not establish equal winning probabilities.
02 / HYBRID ARCHITECTURE
One engine. Two execution carriers.
The deterministic rule stays fixed. Storage, proof and execution differ between the server product and the Solana implementation.
Hybrid Solana
Authenticated input commitments and membership proofs connect off-chain custody to ordered on-chain transitions, result publication and digital-prize settlement.
Implementation identity
HYBRID_SOLANA_V1 / SOLANA_COMPACT_REGISTRY_V1
Hybrid Server
The same engine is used in our Telegram and Mini App product with a durable server registry. It is presented separately from the Solana demonstration.
Implementation identity
HYBRID_SERVER_V1 / FULL_REGISTRY_V1
03 / DIGITAL PRIZE / NFT
A result must lead to a settled prize.
The competition workload includes the prize lifecycle. A calculation alone is not the full demonstration.
Prize custodyWinner-wallet bindingSettlementPublication & reclaim
Accepted run evidence ties the winning position to the exact winner wallet and the prize identity, then verifies settlement and working-account cleanup.
04 / LIVE HYBRID SOLANA LAB
Inspect the latest verified execution.
Choose any N from 2 to 100. Preview shows the latest retained run for that mode, with its network, date and execution parameters. Missing results stay explicit.
Latest verified run
—05 / RUN HISTORY
Run history
06 / COMPARE RUNS
Compare two runs
The network, participant count and source version stay visible. Comparing different conditions does not prove a speedup.
07 / ECONOMICS
Separate cost from locked capital.
Transaction fees, temporary state funding, reclaimed rent and final persistent state are different quantities.
Transaction fees
Execution costs from the retained run’s transaction evidence.
Temporary capital
Working-state funding and the amount recovered after cleanup.
Persistent state
The state and capital remaining after the complete prize lifecycle.
Run-specific values are available in verified reports. No projected value is presented as a measurement.
08–11 / SCALE, RECOVERY & RESEARCH
Compare execution, without changing the rule.
How does the full procedure scale?
The judge-facing range is N=2..100. Larger workloads need their own current, prize-inclusive evidence; historical figures are not imported as current results.
Inspect available runs →Can an interrupted procedure recover?
Recovery is a separate correctness claim. A recovered run cannot populate uninterrupted throughput or timing comparisons.
Correctness boundary
Custody retirement requires finalized wire proof. Original signatures, predecessor order and failure handling remain part of the execution contract.
Parallel execution, same result semantics.
Sealevel is a separate comparison profile. Compare matching participant counts, network and parameters before interpreting timing differences.
Select Sealevel in the lab →A research direction, not a measured speed claim.
ZK Lite is experimental and not implemented in this preview. It requires its own correctness and runtime acceptance.
ZK Lite only after implementation. No ZK run or performance result is implied.
12–13 / TESTS & ADVERSARIAL EVIDENCE
Evidence is part of the demonstration.
A result is useful only when someone else can check it. Retained reports expose what ran, what was measured and what passed verification.
Input & result integrity
Ownership, membership proofs, positioned processing and integer boundaries.
Prize & lifecycle integrity
Winner-wallet binding, settlement, publication, reclaim and recovery boundaries.
Measurement integrity
Source ancestry, exact build and evidence identities, benchmark eligibility and independent verification.
Technical verification — inspect the proof trail
Each published run carries its source HEAD/TREE, parameters, report and evidence manifest. Offline re-verification does not send a new Solana transaction.
Current test totals require a dedicated accepted manifest. Missing metrics remain NOT YET MEASURED FROM CURRENT PRIZE BRANCH.
14 / LIFECYCLE ARCHITECTURE
Stream → Prove → Publish → Erase
Process inputs, verify the transition, retain the result and its evidence, then retire eligible working material. Cleanup follows proof; it does not replace it.
15 / HYBRID SERVER PRODUCT
Experience the separate Telegram product.
Our Mini App demonstrates the user experience around the same engine. It is a separate PostgreSQL + Telegram + Mini App consumer Product; these are not Competition Web dependencies.
16 / PROJECT, AUTHORS & IP
Built by RO-KA.
A deterministic engine for digital procedures, with a Solana implementation that connects participant inputs, a verifiable result and digital-prize settlement.
Roman & Vladimir
Project co-authors. Authorship records cover the algorithm and board-game concept; they are distinct from a patent grant.
RO-KA project website ↗