This week’s public library release covers one of our Genesis Contracts: the Transfer Contract, otherwise known as DUSK Contract. This contract does not only make it possible to transfer DUSK by means of a smart contract, it also prevents the potential existence of concurrent blockchain states.
We've covered the Genesis Contracts and their significance to Dusk Network's Zero-Knowledge technology before; in particular, the Fee, Stake, Bid, and Transfer contracts, and already explained the zero-knowledge infused circuitry that makes the Transfer contract tick in our previous library release. This circuitry is why contract users are able to retain their anonymity when transferring DUSK on the network through the Transfer contract.
Why transfer DUSK by means of a smart contract?
The answer is fairly simple but nevertheless requires some explanation. We designed the Transfer Contract to streamline a single standard (and easy) way of interacting with any asset on-chain. In other words, thanks to the Transfer Contract, there is no longer a distinction between DUSK or any other asset deployed via smart contract on Dusk Network. In addition, this single standard method eases the synchronization of nodes in the network, in turn leading to increased network reliability. And last but not least, the Transfer Contract ensures that there is only one global state to manage.
The importance of one global state.
A state is nothing more than a snapshot of a set of data at a certain point in time. A great example of this is the state of your bank account, which would be your account balance. Without the addition of the Transfer Contract, we would have to manage two different states at the same time: one for all assets deployed on Dusk Network, and one for DUSK, the network fuel. Managing two concurrent states would come at great cost, as we would need to implement additional measures to prevent the possibility of race conditions. That is why the Transfer Contract is such a crucial component and part of our Genesis Contracts
👉 Read more on the Transfer Contract / DUSK Contract here.
The E2E RC Release schedule
The End-to-End Release Candidate is a feature-freeze, and signals the version of the blockchain protocol that we want to go live with. The Release Candidate includes various libraries, which together form the E2E Release Candidate. Alongside these announcement articles, we’ll also be increasing the specificity of the libraries being released to ensure full transparency.
👉 You can find the full schedule here.
Previously we released: