This week’s public library release covers one of the Rusk Smart Contract Platform libraries: RUSK-ABI. This is the first of several libraries pertaining to the Smart Contract Platform.
The RUSK Virtual Machine is an environment built with WebAssembly (WASM) in which all Dusk Network smart contracts are run. There are many pieces to this particular puzzle that, when combined, ensure efficiency, security, and user-friendliness.
One such puzzle piece is the RUSK-ABI, not to be confused with the DUSK-ABI detailed in a previous library release article. Both of these, however, are Application Binary Interfaces, adding specific functionalities to different domains. In the case of DUSK-ABI, it plays an important role in connecting the RUSK Virtual Machine with the smart contract platform, adding a number of general smart contract functionalities that are not unique to our Virtual Machine. Take for instance the handling of block height, gas, and certain elements of Zero-Knowledge.
RUSK-ABI: enabling features unique to our Virtual Machine
The RUSK-ABI, on the other hand, has a different purpose altogether. It is a higher-level interface built on top of the RUSK Virtual Machine and the DUSK-ABI, enabling access to host functions that are specific to our VM, and not native within WASM. Such functions include Poseidon hashing, proofs and Schnorr signature verification.
👉 Find out more about RUSK-ABI 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: