Hello again, everyone! We really appreciate all the support we have received so far. Let's start by taking a look at our | Hanami
Hello again, everyone! We really appreciate all the support we have received so far. Let's start by taking a look at our first public building block: Atlas.
Atlas is a small smart contract registry that manages a list of names. Each entry names a service and includes the address of the contract that provides it.
An Atlas instance is deployed for a specific purpose. Each project maintains its own list on its Atlas instance, and another project deploys a separate one, so many lists exist on the chain at the same time. A contract only follows the Atlas instance whose address it carries. This instance is deployed first. The contracts that use it are deployed afterwards, each carrying the correct Atlas address. When one of these contracts requires a service, it queries Atlas for the name and receives the assigned address. Later, a new contract can be connected to the same name. When the deployed contracts query Atlas again, they find the new address.
Someone has to be authorized to update that list. This role is assigned to the guardian, as specified in the Atlas contract itself. The guardian can be replaced at a later date, and this takes effect after a waiting period. If the guardian is a key, they can change the name on the list and Atlas will then apply the change immediately.
To delay a name change and/or enable MultiSig decisions, the guardian role is given to a warden instead. The warden holds the change and writes it onto Atlas after a set waiting period. This process is based on our Knot BLS MultiSig implementation, which we will discuss next time.
For Rust, the call types are the crate nocturne-atlas-encoding, and the event decoder is nocturne-atlas-event-decoder. The Atlas contract is built from the repository: https://t.co/QSMDPAwfQM
Our first product, Vigil, keeps your $DUSK in a secure vault. The vault asks Atlas which contract to call for each purpose, and it asks again on every call, so that contract can be replaced while the vault stays put.
So far, we have only deployed and tested Atlas on Nocturne and it has not yet been audited.
Take a look at the docs for more information https://t.co/O79fYvYUZS
Retweeted by @DuskFoundation from @nocturne_stds