Nocturne Standards

Open Source Projects on DUSK

[Nocturne Standards @nocturne_stds]

@thisisryanking @boersestuttgart Good points. Perhaps the arrival of AI has levelled the playing field of tech development, setting a new baseline and every system has to start from "zero" again. Hopefully, govt's will think ahead and invest more in blockchain research, experimentation and fitting regulation.

[Nocturne Standards @nocturne_stds]

@halfseal_dusk We are also very excited what Halfseal will bring on-chain! If you need anything, feel free to dm.

[Nocturne Standards @nocturne_stds]

Hello everyone,
We would like to introduce ourselves to the public by sharing a few handwritten words, as a contrast to our AI polluted timelines.
We are developing services, smart contracts, tooling, and more across DuskDS and DuskEVM, with the aim of providing valuable building blocks for our ecosystem.

Security is a cornerstone of our agenda, and the first upcoming release will be Vigil, a $DUSK Vault, that allows you to control your funds and interact with the chain in a secure environment.

It uses two open source building blocks:
- Atlas, a contract registry https://t.co/QSMDPAwfQM (credit to @tminus_dusk for making us aware of the concept)
- Knot, a BLS multisig contract implementation https://t.co/4o3JwFRzMY.

We will test on Nocturne (DuskDS Testnet) and see where we can go from there, one step at a time. We are very excited to show you the first version of our vision.

We have already collaborated with the Dusk Foundation on small enhancements to the Dusk stack, identified through exploring use cases on DuskDS. We want to continue this work, and we also want to encourage other developers to join us in demonstrating Dusk's potential to the world.

This project began purely out of curiosity, leading to the development of a solid knowledge base that we are continuing to build on and share as open source. We are currently building a clean workflow and set up our infrastructure, so excuse us if you encounter any issues when exploring our organization on the website and beyond.

We will leave you with the website, where you can find out more about us. Thank you for reading.
https://t.co/MnllhU8xqG

[Nocturne Standards @nocturne_stds]

@FoneTzu this is the tldr we should have posted

[Nocturne Standards @nocturne_stds]

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

[Nocturne Standards @nocturne_stds]

Timing is indeed important, so perhaps it's not so bad that we have to wait until next year. With security issues popping up left and right, the adoption of current blockchain technology could have been very difficult to roll out. Do you think that this year's security incidents have changed the views of the DLTR's decision-makers? Might they be more inclined to adopt new technology to replace older systems? I'm very curious to see what @boersestuttgart is going to do within the current DLTR boundaries.

[Halfseal @halfseal_dusk]

1/ Halfseal is a registry for invoice claims on @duskfoundation. Every invoice gets one fingerprint and one holder. A factor checks it before buying, buys the claim on chain, and the payment goes to whoever holds it. Building it in public in T-Minus 90.

[Hein Dauven @HeinDauven]

Dusk Domains is live on Dusk mainnet.

One readable .dusk name for your Dusk address, from 10 DUSK a year.

https://t.co/1eT7ypwbCD