Digging into the random beacon contract’s methods and events
In Part 1 we’ve showed you how to bootstrap a simple web app that uses our random beacon’s alpha API contract. In this post we’ll try to give you a more detailed guide how to communicate with the contract and an overview of its methods defined by our alpha API.
KeepRandomBeacon.sol
This contract is the interface to our “threshold relay”, a secure mechanism based on a threshold signature scheme, and it allows us to randomly select providers for a new keep. The threshold relay is a fairly complex subject and deserves a separate post, but in the meantime you can check…
Presenting a fun web app to play with randomness on the blockchain
Keep’s random beacon
One of the first components of the Keep Network that we have been working on is the random beacon. Because this component can be a great boon to other projects, we would like to encourage developers and those working on dApps that require randomness to have a glimpse into how Keep’s random beacon works.
What’s hard about random numbers on the blockchain?
You can trust a blockchain, but you can not get trusted randomness since it’s a deterministic system where you still have to rely on a 3rd party for the random source. It’s not ideal, of course, and you want to be sure that no one has…
A tool in our decentralized toolbox
This is the third article in a series exploring the concepts and tools behind the Keep network and other decentralized systems.
Software engineering is a mix of craft and science. In contrast to a traditional engineering discipline, like civil engineering, the problems in software engineering are poorly defined. Often, they are a mix of technology (“How does it work?”) and people (“How should it work? How can we make it work?”).
Compared to building a bridge, building a software system is difficult to estimate, plan, and execute reliably. The construction of decentralized software systems is an even less mature study…
