Ideal Network: The Randomness Layer for Polkadot's World Computer

Medium Spender
3d ago
10 Comments
Deciding
Content
AI Summary
Reply
Up
Share
Request
300.25KUSDC
Status
Decision28d
Confirmation4d
Attempts
0
Tally
95.6%Aye
4.4%Nay
Aye
217.66KDOT
Nay
10.12KDOT
  • 0.0%
  • 0.0%
  • 0.0%

Threshold

Support0.01%
113.68KDOT
Issuance
1.52BDOT
Votes
Nested
Flattened
Calls
Call
Metadata
Timeline3
Votes Bubble
Statistics
Comments

This seems to be a similar project to Nois on Cosmos. Randomness is something that projects will require in order to ensure fairness in their applications. Based on the previous case, Nois, we would like to ask some questions about adoption, compatibility and future support which were the main issues that this approach had on Cosmos.

  1. Adoption. The adoption of Nois was limited mostly due to the Luna collapse which affected Cosmos the most and it never recovered. But the most evident issue outside the macro picture was that some blockchains like Stargaze used Nois as a source of randomness whereas others, specially dapps just went straight to the Drand API to connect to the source of randomness thus bypassing the blockchain completely. This makes it evident that the clients for Ideal would also be limited to parachains and large projects. A secondary limiting factor was that Nois was compatible mostly for IBC blockchains. How is Ideal Network planning to reach as many projects as possible? Within Polkadot and outside of it (more on this on paragraph 2).
  2. Compatibility. Based on the paragraph 1, compatibility outside of IBC chains was the second most important factor against the expansion of Nois. Would Ideal Network be considering actively integrating with Hyperbridge and/or Snowbridge to also "export" randomness from Ideal Network into supported EVM chains? It seems like the latency and transfer times would make it possible to relay a message through Hyperbridge to EVM chains. We need to put an emphasis on actively integrating as some referenda in the past have just agreed to some terms without ever delivering them.
  3. Future Support. We have seen other projects to move goalposts after funding as well as abandoning the project completely as soon as it's delivered so we need to have crystal clear assurances about the future development costs of Ideal network and the maintenance and support costs both in human terms and monetary terms. We are policing heavily against abandonware, unknown maintenance costs and against increase of costs of future deliveries. So knowing these costs in advance would help. In the same vein, is Ideal considering funding through a token launch like Nois did? Or does it plan to remain a common goods project within Polkadot's treasury support? Tokenization after failed public funding is understandable but tokenization without treasury swaps and with treasury support is hard to vouch for.

Looking forward to hearing your answers and future plans.

Reply
Up

Hey,
From proposal:
"Ideal Labs will maintain a public Kanban board on GitHub to provide real-time tracking of progress, complementing the regular communication updates."

Can you link this kanban/github board?

Reply
Up

Another question:
How have you guys collaborated with NIST?
The link(https://csrc.nist.gov/Projects/interoperable-randomness-beacons) mentions Cloudflare and Crypto reading club

Reply
Up