Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add a note about audit in multisig SC #123

Merged
merged 2 commits into from
Nov 22, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions contracts/multisig/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,10 @@ As an example, let us imagine the following scenario. An institution launches a

Thus, essentially the multisig SC (we will refer to it, from now on, as MSC) enables multiple parties to sign or approve an action that takes place - typically a requirement for certain wallets, accounts, and smart contracts to prevent a rogue or hacked individual from performing detrimental actions.

## Developer's note

The release version v0.45.5 of mx-contracts-rs, contains the audited of for the multisig contract. It can be found here: https://github.com/multiversx/mx-contracts-rs/releases/tag/v0.45.5

## Multisig transaction flow
On-chain multisig wallets are made possible by the fact that smart contracts can call other smart contracts. To execute a multisig transaction the flow would be:

Expand Down
Loading