Nois

• Name: Nois
• URL: https://nois.network/
• Category: drand delivery middleware / IBC randomness relay / CosmWasm callback plumbing
• Tags: cosmos-ecosystem
• Summary: Nois is a Cosmos delivery layer for drand, not a new randomness primitive. The useful surface is the relay chain and app plumbing around the beacon: request funding, bot pickup, onchain verification, IBC routing, and callback delivery into CosmWasm apps. That makes it a good note for transport and operator dependence, not for randomness-source novelty.
• What it does:
  • Lets CosmWasm applications on IBC-enabled chains request randomness through a local Nois proxy contract and receive callbacks once the requested round is available
  • Uses Nois-chain contracts such as nois-gateway, nois-payment, and nois-drand to queue requests, verify drand beacons, manage balances, and route callbacks
  • Bridges verified randomness back to consumer chains through nois-proxy contracts, so dapps do not need to manage the underlying IBC flow directly
  • Incentivizes offchain drand bots to submit requested drand rounds to Nois, with rewards depending on speed, allowlisting status, and whether a round was actually requested by a dapp
  • Publishes a standard library and toolbox for integrating randomness requests and callback handling into CosmWasm contracts and JavaScript simulations
• Key claims:
  • The docs market Nois as a PoS randomness protocol for IBC-connected chains, but the sharper read is narrower: drand remains the randomness source while Nois packages verification, funding, transport, and callback handling around it.
  • The contracts split makes that layering clear. nois-payment decides whether a request is fundable, nois-gateway queues and routes work, nois-drand verifies beacon material, nois-proxy sits on the consumer side, and nois-icecube adds reward reserves for bot participation.
  • The drand-bot docs expose the real operational choke point. Bots do not choose the randomness, but they do shape liveness and delivery speed, and rewards favor operators who are fast enough and, in some cases, allowlisted.
  • That makes Nois more interesting as delivery middleware than as a randomness note. It turns a public beacon into a paid relay path with queueing, IBC transport, and app-callback semantics that downstream CosmWasm apps can depend on.
  • The useful comparison question is not whether Nois beats drand on entropy quality. It is whether a consumer app is really relying on an upstream public beacon or on a narrower Nois-operated delivery market with its own funding, bot, and routing assumptions.
• Whitepaper: No classic Nois whitepaper dominated this pass. The clearest primary materials were the official site, docs repository, contracts repository, standard-library README, and organization overview. Those sources were enough to map the delivery architecture and incentive/control surfaces without relying on secondary explainers; see ../whitepapers/nois-primary-sources-2026-05-12.md.
• Sources:
  • https://nois.network/
  • https://docs.nois.network/
  • https://github.com/noislabs
  • https://raw.githubusercontent.com/noislabs/docs/main/src/what_is_nois.md
  • https://raw.githubusercontent.com/noislabs/docs/main/src/how_it_works.md
  • https://raw.githubusercontent.com/noislabs/docs/main/src/drand.md
  • https://raw.githubusercontent.com/noislabs/docs/main/src/drand_bots.md
  • https://raw.githubusercontent.com/noislabs/nois-contracts/main/README.md
  • https://raw.githubusercontent.com/noislabs/nois/main/README.md

Internal linkages

• Keep this note on drand and pyth-entropy.
• That is enough to separate source beacon, IBC delivery chain, and provider-mediated reveal middleware.

Control surface

• Practical authority sits in funding policy, gateway and proxy deployment, bot participation and allowlisting, IBC routing, and callback completion on the consumer chain.

• Read Nois as drand delivery infrastructure for CosmWasm apps, not as a fresh randomness primitive.

• Last reviewed: 2026-06-18 UTC