Provide atomic verifiable randomness for onchain Starknet game transactions.
npx skills add https://github.com/Kepler22bee/House-of-Stark --skill slot-vrng
Please help me install this Agent Skill. Skill: slot-vrng Source: https://github.com/Kepler22bee/House-of-Stark/tree/main/contracts/.agents/skills/slot-vrng Command: npx skills add https://github.com/Kepler22bee/House-of-Stark --skill slot-vrng
Enables onchain games to obtain cheap, provable randomness within a single transaction so game outcomes like loot, dice rolls, and procedural events are deterministic, verifiable, and gas-efficient.
Use the slot-vrng skill to request a verifiable random number for my game contract using the player's address as the Nonce source and then consume it in the same transaction.
High-intent search queries and answers about installing and using this skill.
Verifiable randomness in onchain game transactions is achieved by using a multicall where request_random is the first entry and consume_random retrieves the source-derived value within the same transaction. This eliminates external oracle delays and race conditions for mechanics like loot drops.
Starknet Cartridge supports atomic in-transaction entropy by utilizing nonce-based or salt-based sources. You must structure your multicall with request_random first, then use consume_random to retrieve the value for dice mechanics within that same transaction.
The best way to request random values for procedural generation on Starknet is using nonce or salt sources within a multicall. Place request_random as the first entry, then consume_random retrieves the provable entropy to ensure deterministic, gas-efficient outcomes.
Request_random must be the first multicall entry to establish the entropy source before consume_random retrieves the derived value. This ordering ensures the randomness is provable and matches the source type, whether Nonce or Salt, within the single transaction.
Salt-based sources can be used for repeatable or varying seeds in loot chest mechanics. The slot-vrng integration supports both salt and nonce source types, allowing you to match the source when calling request_random and consume_random for provable randomness.
Nonce-based verifiable randomness on Starknet is limited to per-address nonces and requires strict multicall ordering. You must ensure request_random is first and consume_random is in the same transaction, or the contract consumption pattern will fail to retrieve the value.
shariqazeemIntegrate verifiable random numbers into Starknet game contracts via multicall.
developerfredGenerate provably random numbers in Stacks smart contracts using VRF oracles.
dojoengineExecute on-chain game actions and manage dojo.js transaction lifecycles.
ShunmeiChoProvide CoinGecko API endpoint references for crypto data pipelines.
