Intro Video

https://youtu.be/9FZMjFbcW3Q

A project by Rock Stable, purveyors of ROKS, a stablecoin currently used exclusively for cross-border money transfers (https://sendroks.com).

Inflation-Resistant Medium of Account (IRMA)

This a set of Solana contracts written in solang that implement an inflation-resistant stablecoin using OpenBook. It is submitted as an entry to the Renaissance Hackathon run by Colosseum.

For dev contributors

If you are new to Solana, it helps to read a good intro: Link

Programming directly on Solana involves lots of complicated details. Using the Anchor library helps simplify things like figuring out the instructions that form a transaction. Here is a good documentation on Anchor: Link

We come from the Microsoft side of the programming fence, but the tools necessary for building a Solana app are all native to Linux. In order to make things simpler and less risky we decided to use Linux for our workstation; however, we kept Windows as part of our environment, but only for its great UI and VS Code. The Windows Subsystem for Linux has been crucial in allowing us to use Linux CLI tools and yet use VS Code for editing and debugging. However, using Linux alone should work too.

We decided against using Rust mainly for the same reason: we come from Microsoft. We want to use Anchor but not Rust, so at first we thought C or C++ would be good. Alas, C / C++ does not have a good externals file (dot h file) for Anchor. We finally decided to use solang; solang is simple (not much clutter) and the resulting contracts can link with Anchor. Besides, we've done a lot of EVM Solidity programming and solang looks and feels like Solidity (but for Solana).

Here is a great intro on how to use solang in the Solana environment: Link

Here is some documentation on using solang with some info on how to use Anchor: Link

This site has nothing about solang, but it is useful for setting up a WSL environment: Link

How to install the tools in your Linux workstation

1. Installing Solana, Cargo, and Anchor

# Using Ubuntu WSL

@ Install solana cli
sh -c "$(curl -sSfL https://release.solana.com/v1.18.4/install)"

# Cargo installation
sudo apt install cargo

# Anchor installation
cargo install --git https://github.com/coral-xyz/anchor avm --locked --force

# Below is optional if cargo install fails
sudo apt-get update && sudo apt-get upgrade && sudo apt-get install -y pkg-config build-essential libudev-dev libssl-dev

# Install the latest version of the CLI using avm and set to latest
avm install latest
avm use latest

Add the /home/<username>/.cargo/bin to the $PATH.

Verify installation by:

avm --version
anchor --version

Source: here

Anchor is installed at this point

anchor init hello-world

this prepares files for Rust - not what we need - but good enough to start somewhere.

2. Solang Installation

https://solang.readthedocs.io/en/latest/index.html

https://solang.readthedocs.io/en/latest/targets/solana.html

Solang Solidity Compiler v0.3.3-38-g22d6217 documentation

Follow Option 2 - Download the binary (click "Linux x86-64" which works in WSL Ubuntu)

mkdir ~/.local/share/solana/install/solang

mkdir ~/.local/share/solana/install/solang/bin

cp /mnt/c/Users/<user>/Downloads/solang-linux-x86-64 ~/.local/share/solana/install/solang/bin/solang

# Copy from your Download folder to ~/.local/share/solana/install/solang/bin/solang
export PATH=/home/<user>/.local/share/solana/install/active_release/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:~/.local/share/solana/install/solang/bin/solang
solang --version

(Note: solang is also installed when solana sdk is installed.)

To integrate with a pre-existing, external contract:

anchor idl fetch --out openbook.idl <address of OpenBook program>
solang idl --output filename.txt openbook.idl
cargo add openbook.idl

To compile all TypeScript source files

The tsc config file tsconfig.json must be used, and the only way I found to do this (that also transpiles the .ts files) is to simply do the CLI command "tsc".

3. Possible Issues

If your contract increases in size as you develop it, "anchor deploy" can fail with "Error: Deploying program failed: RPC response error -32002: Transaction simulation failed: Error processing Instruction 0: account data too small for instruction [3 log messages]". Anchor deploy calculates the necessary data size, but if you modify the contract, memory size requirement of your contract can increase. This is the reason for this error. Another error that can come up during testing is "Error: failed to send transaction: Transaction simulation failed: Error processing Instruction 0: incorrect program id for instruction".

To fix:

Delete the target folder

Run "anchor build --solana-version 1.18.4" this will add a new keypair to target/deploy

Start localnet solana-test-validator in another WSL instance

Run "anchor deploy" in the first WSL instance

Run "anchor keys list", this will give you the new program ids

Copy the id(s) to the top of your solang contract(s) and also to Anchor.toml

Delete the target folder again

Run anchor build again to get the correct id(s) in target/types folder

Stop the solana-test-validator, then run "anchor test"

Note: The program ids of all contracts should be in the following places: in the sol source file (above "contract" keyword), in the target/idl json files (bottom), in the target/types files (bottom), and in Anchor.toml.

It can be confusing because "anchor deploy" outputs program ids which can be different from "anchor keys list". If this happens, use the ids output by "anchor deploy".

Also, the Solana address to which the program is deployed must have some minimum SOL! Not only the account that deployed the program, but also the program address itself must have some SOL (because of the rent rule for any address: an address does not exist if it has no SOL). This issue shows up when you try to "anchor run node":

failed, error:  SendTransactionError: failed to send transaction: Transaction simulation failed: Error processing Instruction 0: incorrect program id for instruction
    at Connection.sendEncodedTransaction (/home/ctapang/source/inflation-resistant-stablecoin/anchor-solang/node_modules/@solana/web3.js/lib/index.cjs.js:8026:13)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Connection.sendRawTransaction (/home/ctapang/source/inflation-resistant-stablecoin/anchor-solang/node_modules/@solana/web3.js/lib/index.cjs.js:7992:20)
    at async sendAndConfirmRawTransaction (/home/ctapang/source/inflation-resistant-stablecoin/anchor-solang/node_modules/@coral-xyz/anchor/dist/cjs/provider.js:247:23)
    at async AnchorProvider.sendAndConfirm (/home/ctapang/source/inflation-resistant-stablecoin/anchor-solang/node_modules/@coral-xyz/anchor/dist/cjs/provider.js:98:20)
    at async MethodsBuilder.rpc [as _rpcFn] (/home/ctapang/source/inflation-resistant-stablecoin/anchor-solang/node_modules/@coral-xyz/anchor/dist/cjs/program/namespace/rpc.js:15:24) {
  logs: [
    'Program 4b6V88qC7MXuvFhnTf1wSTQVJj7eswky6WkETaNqTJtm invoke [1]',
    'Program log: program_id should be 2VN914zCR1WkHwXeP8vRdimBWMYuNGL9MqJbbQ28SmMy',
    'Program 4b6V88qC7MXuvFhnTf1wSTQVJj7eswky6WkETaNqTJtm consumed 1672 of 200000 compute units',
    'Program 4b6V88qC7MXuvFhnTf1wSTQVJj7eswky6WkETaNqTJtm failed: incorrect program id for instruction'
  ],
  programErrorStack: ProgramErrorStack {
    stack: [
      [PublicKey [PublicKey(4b6V88qC7MXuvFhnTf1wSTQVJj7eswky6WkETaNqTJtm)]]
    ]
  }
}

To fix this issue, first find out what the address of the program is (program id), by issuing the following CLI:

solana-keygen pubkey target/deploy/openbookv_2_interface-keypair.json

and then

solana airdrop 1 <program id obtained above>

then you'd have to edit four files to put this same address as the program id.

However, the program CreateMarket could still fail to run, display the same error message as above. What finally worked for me was the following:

1. Go to the other WSL instance and stop solana-test-validator.
2. Issue the command "solana-test-validator --reset" in order to start clean.
3. In the first WSL instance, issue the following commands:
    anchor build --solana-version 1.18.4
    solana-keygen pubkey target/deploy/openbookv_2_interface-keypair.json
    anchor deploy -p openbookv_2_interface --program-keypair target/deploy/openbookv_2_interface-keypair.json
4. The command "anchor run node" should then output the following:

Your transaction signature 4ycYnpRui2x1hMHtNRWrPE3dRFt4KToZvgm2vmWSCwoCCmV7325sSGF7m1PBqd7ZCtUgH7HFBRshFnzwaX4Tb72h
state {
  side: { bid: {} },
  priceLots: <BN: 400>,
  maxBaseLots: <BN: 800>,
  maxQuoteLotsIncludingFees: <BN: 54bd2>,
  clientOrderId: <BN: bacf>,
  orderType: { market: {} },
  expiryTimestamp: <BN: 8a8310>,
  selfTradeBehavior: { abortTransaction: {} },
  limit: 80
}
size:  44

Finally, it is recommended not to use "anchor deploy". Instead, use "solana program deploy":

solana program deploy target/deploy/openbookv_2_interface.so -k /home/ctapang/.config/solana/id.json

If you make a mistake, you can start all over with the localnet cluster by issuing the command: "solana-test-validator --reset" which would delete the blockchain and start from genesis.