Sallar

We express our gratitude to the Astral Holding OU team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.

The Sallar ecosystem is a network of community projects that use Sallar as their payment method. With Sallar, you can pay for products and services, such as clothing, and use it as the currency on the Marketplace Community.

The system users should acknowledge all the risks summed up in the risks section of the report

This program manages creation, emission and distribution of a fungible token. Its maximum supply is 12,000,000,000 of which:

• 2,600,000,000 is distributed to a special “organization” account.

• 9,400,000,000 is distributed in batches of so-called “blocks”.

There are 470,000 blocks, which are distributed in a game-like fashion one by one in two ways: top-to-bottom (starting from block 1, aka “mining”), and bottom-to-top (starting from block 470,000, aka “staking”). Each block needs to be exhausted (for the next one to become available) by user requests, which the off-chain code posts to the contract on behalf of the users; each such request causes transferring a portion of the block tokens to the user that corresponds to the request. The rules and requests are different for the two directions - the details are in the official documentation →.

Once all the blocks have been consumed, two distribution modes become available: “final mining” and “final staking”. Each mode has a designated account (exclusively managed by the contract) which can be funded by anybody using the previously distributed funds; funds in the special accounts are distributed according to yet new games, whose rules are described in the official documentation →. The two final distribution games are played in cycles, and there can be indefinitely many cycles - as long as there are funds in the special accounts. Like in the normal block distribution modes, the games are played with user requests, which the off-chain code posts to the contract on behalf of the users; each such request causes transferring a portion of the block tokens to the user that corresponds to the request.

Each distribution game has a significant part of its logic outside the contract - which is out of the scope.

The smart contract has the following API:

• initialize — Sets up program-related accounts and performs initial mint. Can be called at most once.

• initialtokendistribution — Distribute 2,600,000,000 tokens to the “organization” account, provided by the owner. Can be called at most once.

• solvetopblock — The owner executes a set of user requests to play the “mining” game.

• solvebottomblock — The owner executes a set of user requests to play the “staking” game.

• finalmining_ — The owner executes a set of user requests to play the “final mining” game.

• finalstaking_ — The owner executes a set of user requests to play the “final staking” game.

• changeauthority_ — The owner changes the contract authority to the new one.

Privileged roles

• The only user of the program is owner - an account registered by the initialize() function and can be changed using change_authority().

The total Documentation quality score is 10 out of 10.

• The functional documentation covers everything in satisfactory detail.

• Technical description is provided.

The total Code quality score is 7 out of 10.

• Redundancies are found (I-2023-0418).

• Some confusing points are found (I-2023-0422).

• Floating point numbers math is used.

Code coverage of the project is 90% (branch coverage).

• final_mining and final_staking instructions are tested but their effects are not checked during testing.

• The solve_top_block and solve_bottom_block instructions that take a lot lines of code (due to redundancies and code duplications) are successfully tested.

Upon auditing, the code was found to contain 1 critical, 2 high, 5 medium, and 1 low severity issues. Out of these, 6 issues have been addressed and resolved, leading to a security score of 10 out of 10.

All identified issues are detailed in the “Findings” section of this report.

The comprehensive audit of the customer's smart contract yields an overall score of 9.1. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.