## Release notes
**Release notes and unreleased changes can be found in the [CHANGELOG](CHANGELOG.md)**
## Example
Wrap a struct in `#[unc]` and it generates a smart contract compatible with the Utility blockchain:
```rs
use unc_sdk::{unc, env};
#[unc(contract_state)]
#[derive(Default)]
pub struct StatusMessage {
records: HashMap,
}
#[unc]
impl StatusMessage {
pub fn set_status(&mut self, message: String) {
let account_id = env::signer_account_id();
self.records.insert(account_id, message);
}
pub fn get_status(&self, account_id: AccountId) -> Option {
self.records.get(&account_id).cloned()
}
}
```
## Features
### Unit-testable
Writing unit tests is easy with `unc-sdk`:
```rust
#[test]
fn set_get_message() {
let mut contract = StatusMessage::default();
contract.set_status("hello".to_string());
assert_eq!("hello".to_string(), contract.get_status("bob".to_string()).unwrap());
}
```
Run unit test the usual way:
```bash
cargo test --package status-message
```
### Asynchronous cross-contract calls
Asynchronous cross-contract calls allow parallel execution of multiple contracts in parallel with subsequent aggregation on another contract. `env` exposes the following methods:
* `promise_create` -- schedules an execution of a function on some contract;
* `promise_then` -- attaches the callback back to the current contract once the function is executed;
* `promise_and` -- combinator, allows waiting on several promises simultaneously, before executing the callback;
* `promise_return` -- treats the result of execution of the promise as the result of the current function.
Follow [examples/cross-contract-high-level](examples/cross-contract-calls/high-level)
to see various usages of cross contract calls, including **system-level actions** done from inside the contract like balance transfer (examples of other system-level actions are: account creation, access key creation/deletion, contract deployment, etc).
### Initialization methods
We can define an initialization method that can be used to initialize the state of the contract. `#[init]` verifies that the contract has not been initialized yet (the contract state doesn't exist) and will panic otherwise.
```rust
#[unc]
impl StatusMessage {
#[init]
pub fn new(user: String, status: String) -> Self {
let mut res = Self::default();
res.records.insert(user, status);
res
}
}
```
Even if you have initialization method your smart contract is still expected to derive `Default` trait. If you don't
want to disable default initialization, then you can prohibit it like this:
```rust
impl Default for StatusMessage {
fn default() -> Self {
unc_sdk::env::panic_str("Contract should be initialized before the usage.")
}
}
```
You can also prohibit `Default` trait initialization by using `unc_sdk::PanicOnDefault` helper macro. E.g.:
```rust
#[unc(contract_state)]
#[derive(PanicOnDefault)]
pub struct StatusMessage {
records: HashMap,
}
```
### Payable methods
We can allow methods to accept token transfer together with the function call. This is done so that contracts can define a fee in tokens that needs to be payed when they are used. By the default the methods are not payable and they will panic if someone will attempt to transfer tokens to them during the invocation. This is done for safety reason, in case someone accidentally transfers tokens during the function call.
To declare a payable method simply use `#[payable]` decorator:
```rust
#[payable]
pub fn my_method(&mut self) {
...
}
```
### Private methods
Usually, when a contract has to have a callback for a remote cross-contract call, this callback method should
only be called by the contract itself. It's to avoid someone else calling it and messing the state. Pretty common pattern
is to have an assert that validates that the direct caller (predecessor account ID) matches to the contract's account (current account ID).
Macro `#[private]` simplifies it, by making it a single line macro instead and improves readability.
To declare a private method use `#[private]` decorator:
```rust
#[private]
pub fn my_method(&mut self) {
...
}
/// Which is equivalent to
pub fn my_method(&mut self ) {
if unc_sdk::env::current_account_id() != unc_sdk::env::predecessor_account_id() {
unc_sdk::env::panic_str("Method my_method is private");
}
...
}
```
Now, only the account of the contract itself can call this method, either directly or through a promise.
## Pre-requisites
To develop Rust contracts you would need to:
* Install [Rustup](https://rustup.rs/):
```bash
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
```
* Add wasm target to your toolchain:
```bash
rustup target add wasm32-unknown-unknown
```
## Writing Rust Contract
You can follow the [examples/status-message](examples/status-message) crate that shows a simple Rust contract.
The general workflow is the following:
1. Create a crate and configure the `Cargo.toml` similarly to how it is configured in [examples/status-message/Cargo.toml](examples/status-message/Cargo.toml);
2. Crate needs to have one `pub` struct that will represent the smart contract itself:
* The struct needs to implement `Default` trait which
UNC will use to create the initial state of the contract upon its first usage;
* The struct also needs to implement `BorshSerialize` and `BorshDeserialize` traits which UNC will use to save/load contract's internal state;
Here is an example of a smart contract struct:
```rust
use unc_sdk::{unc, env};
#[unc(contract_state)]
#[derive(Default)]
pub struct MyContract {
data: HashMap
}
```
3. Define methods that UNC will expose as smart contract methods:
* You are free to define any methods for the struct but only public methods will be exposed as smart contract methods;
* Methods need to use either `&self`, `&mut self`, or `self`;
* Decorate the `impl` section with `#[unc]` macro. That is where all the M.A.G.I.C. (Macros-Auto-Generated Injected Code) happens;
* If you need to use blockchain interface, e.g. to get the current account id then you can access it with `env::*`;
Here is an example of smart contract methods:
```rust
#[unc]
impl MyContract {
pub fn insert_data(&mut self, key: u64, value: u64) -> Option {
self.data.insert(key)
}
pub fn get_data(&self, key: u64) -> Option {
self.data.get(&key).cloned()
}
}
```
## Building Rust Contract
### [cargo-unc](https://github.com/utnet-org/cargo-unc)
This can be used as an alternative, to allow building while also generating an [abi](https://github.com/utnet-org/abi)
```bash
# Install the unc extension if you haven't already
cargo install cargo-unc
# Builds the wasm contract and ABI into `target/unc`
cargo unc build --release
```
### Using cargo build
```bash
RUSTFLAGS='-C link-arg=-s' cargo build --target wasm32-unknown-unknown --release
```
## Building with reproducible builds
Since WebAssembly compiler includes a bunch of debug information into the binary, the resulting binary might be
different on different machines. To be able to compile the binary in a reproducible way, we added a Dockerfile
that allows to compile the binary.
**Use [contract-builder](https://github.com/utnet-org/utility-sdk-rs/tree/master/contract-builder)**
## Utility contract standards
[`unc-contract-standards` crate](https://github.com/utnet-org/utility-sdk-rs/tree/master/unc-contract-standards) provides a set of interfaces and implementations for UNC's contract standards:
* Upgradability
* Fungible Token (UIP-141). See [example usage](examples/fungible-token)
* Non-Fungible Token (UIP-171). See [example usage](examples/non-fungible-token)
## Versioning
### Semantic Versioning
This crate follows [Cargo's semver guidelines](https://doc.rust-lang.org/cargo/reference/semver.html).
State breaking changes (low-level serialization format of any data type) will be avoided at all costs. If a change like this were to happen, it would come with a major version and come with a compiler error. If you encounter one that does not, [open an issue](https://github.com/utnet-org/utility-sdk-rs/issues/new)!
### MSRV
The minimum supported Rust version is currently `1.78`. There are no guarantees that this will be upheld if a security patch release needs to come in that requires a Rust toolchain increase.
## Contributing
If you are interested in contributing, please look at the [contributing guidelines](CONTRIBUTING.md).
