𝗣𝗮𝗿𝗶𝘀, 𝗙𝗿𝗮𝗻𝗰𝗲 — 𝗢𝗰𝘁𝗼𝗯𝗲𝗿 𝟮𝟯, 𝟮𝟬𝟮𝟱 — 𝗕𝗣𝗩𝗲𝗻𝘁𝘂𝗿𝗲𝘀 and 𝗟𝗶𝗴𝗵𝘁𝗘𝗰𝗵𝗼 today announced the availability of a new randomness feed in their oracle network that is 𝗖𝗵𝗮𝗶𝗻𝗹𝗶𝗻𝗸-𝗰𝗼𝗺𝗽𝗮𝘁𝗶𝗯𝗹𝗲 and SEP-40 compliant, enabling game developers to consume verifiable 32-byte random “words” through a single, standard interface. The feed is exposed under the 𝗦𝗘𝗣-𝟰𝟬 SYMBOL: RANDOM identifier, so any Soroban smart contract that speak SEP-40 can read it without custom glue code.

“Games need simple, unbiased, and interoperable randomness,” said a spokesperson for BPVentures. “By speaking both Chainlink’s uint256 [ ] word format and SEP-40’s Oracle Consumer Interface, we help teams plug in fast—on Soroban today, for EVM titles plan to port and already expect VRF-style data.”

“Our goal is developer ergonomics with strong security guarantees,” added a LightEcho representative. “RANDOM as a standard symbol keeps contracts clean, while our oracle network focuses on reliability, throughput, and transparent proofs.”

What’s New

• 𝗖𝗵𝗮𝗶𝗻𝗹𝗶𝗻𝗸-𝗰𝗼𝗺𝗽𝗮𝘁𝗶𝗯𝗹𝗲 𝗼𝘂𝘁𝗽𝘂𝘁: Each “word” is a 𝟯𝟮-𝗯𝘆𝘁𝗲 𝘂𝗻𝘀𝗶𝗴𝗻𝗲𝗱 𝗶𝗻𝘁𝗲𝗴𝗲𝗿 (uint256), matching the format most EVM based games already expect for loot tables, rarity rolls, raffles, and mints.

• 𝗦𝗘𝗣-𝟰𝟬 𝗰𝗼𝗺𝗽𝗹𝗶𝗮𝗻𝘁 𝗰𝗼𝗻𝘀𝘂𝗺𝗽𝘁𝗶𝗼𝗻: Read randomness via the 𝗢𝗿𝗮𝗰𝗹𝗲 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 𝗜𝗻𝘁𝗲𝗿𝗳𝗮𝗰𝗲 using Asset::Other(Symbol::from_str("RANDOM")). No bespoke adapters required.

• 𝗚𝗮𝗺𝗲-𝗿𝗲𝗮𝗱𝘆 𝗨𝗫: Batch “words” for multi-roll mechanics; deterministic, ABI-friendly layout makes mapping to ranges straightforward.

How It Works (At a Glance)

• 𝗢𝗻 𝗦𝗼𝗿𝗼𝗯𝗮𝗻 (𝗦𝗘𝗣-𝟰𝟬):
  Contracts call the oracle’s lastprice(env, asset) (or history methods) with asset = Asset::Other(Symbol("RANDOM")).

  ∘ price carries the 𝟮𝟱𝟲-𝗯𝗶𝘁 𝘄𝗼𝗿𝗱 as an integer payload.
  ∘ timestamp lets consumers enforce freshness/slippage windows.
  ∘ Decimals are defined to preserve the full 256-bit space without loss; treat the value as a raw uint256 “word” in consumer logic.

Developer Notes

• 𝗦𝘆𝗺𝗯𝗼𝗹: RANDOM (SEP-40 Asset::Other)

• 𝗪𝗼𝗿𝗱 𝗳𝗼𝗿𝗺𝗮𝘁: 32-byte big-endian uint256 (one or many words per request)

• 𝗧𝘆𝗽𝗶𝗰𝗮𝗹 𝘂𝘀𝗮𝗴𝗲:
  ∘ 𝗨𝗻𝗶𝗳𝗼𝗿𝗺 𝗺𝗮𝗽𝗽𝗶𝗻𝗴: Use rejection sampling to avoid modulo bias when mapping uint256 to small ranges (e.g., 1–100).
  ∘ 𝗙𝗿𝗲𝘀𝗵𝗻𝗲𝘀𝘀 𝗰𝗵𝗲𝗰𝗸𝘀: Compare the timestamp in PriceData vs. the current ledger time to avoid stale reads.
  ∘ 𝗕𝗮𝘁𝗰𝗵𝗶𝗻𝗴: For multi-draw features, request/consume multiple words in a single call.

Soroban (Rust) Sketch

use soroban_sdk::{contractimpl, Address, Env, Symbol, Vec as SVec}; 
pub fn read_random_word(env: Env, oracle: Address) -> (i128, u64) { 
  // asset = Other(Symbol("RANDOM")) 
  let asset = Asset::Other(Symbol::short("RANDOM")); 
  // lastprice returns Option<PriceData> { price: i128, timestamp: u64 } 
  if let Some(pd) = PriceFeedClient::new(&env, &oracle).lastprice(&asset) { 
   // Interpret pd.price as a raw 256-bit word carried losslessly in i128/decimals scheme per 
  oracle docs. 
   return (pd.price, pd.timestamp); 
  } 
  panic!("No randomness available"); 
}

Availability

The randomness feed is live on the LightEcho oracle network and available to partners integrating 𝗴𝗮𝗺𝗲 𝗺𝗲𝗰𝗵𝗮𝗻𝗶𝗰𝘀, 𝗺𝗶𝗻𝘁𝘀, 𝗿𝗮𝗳𝗳𝗹𝗲𝘀, and 𝗽𝗿𝗼𝗰𝗲𝗱𝘂𝗿𝗮𝗹 𝗴𝗲𝗻𝗲𝗿𝗮𝘁𝗶𝗼𝗻. Documentation, SDKs, and sample contracts are provided for both Soroban (SEP-40) and Soroban consumers.

About BPVentures

BPVentures builds compliant, production-grade blockchain infrastructure—wallets, payments rails, and oracle services—for real-world and gaming applications.

About LightEcho

LightEcho operates a high-reliability oracle network focused on simple developer interfaces, verifiable data delivery, and multi-chain compatibility.

Media & Developer Inquiries

Visit lightecho.io for documentation, integration guides, or email sales@bpventures.us for support options.

Trademarks and brands are the property of their respective owners. This announcement does not imply endorsement by third parties.