Multisig page DANGER banner (ton-community#945)

* multisig-banner

* upd

* Update multisig.md

* Resolving conversations

* yellow

* Resolving conversations

Author: memearchivarius

docs/v3/guidelines/smart-contracts/howto/multisig-js.md

@@ -4,10 +4,16 @@ description: At the end of this guide you will deploy multisig wallet and send s
 
 # Interact with multisig wallets using TypeScript
 
+:::warning
+This page is heavily outdated and will be updated soon.
+See the [multisig-contract-v2](https://github.com/ton-blockchain/multisig-contract-v2), the most up-to-date multisignature contract on TON.
+Use npm and do not update.
+:::
+
 ## Introduction
 If you don't know what is multisig wallet in TON, you can check it out [here](/v3/guidelines/smart-contracts/howto/multisig)
 
-Following this steps you will learn how to:
+Following these steps you will learn how to:
  * Create and deploy multisig wallet
  * Create, sign and send transactions with that wallet
 
@@ -24,7 +30,7 @@ The full code of this guide is available here:
 ## Create and deploy multisig wallet
 Let's create a source file, `main.ts` for example. Open it in your favorite code editor and follow this guide!
 
-At first we need to import all important stuff
+At first, we need to import all important stuff
 ```js
 import { Address, beginCell, MessageRelaxed, toNano, TonClient, WalletContractV4, MultisigWallet, MultisigOrder, MultisigOrderBuilder } from "ton";
 import { KeyPair, mnemonicToPrivateKey } from 'ton-crypto';

docs/v3/guidelines/smart-contracts/howto/multisig.md

@@ -14,6 +14,7 @@ This tutorial help you learn how to deploy your multisig contract.
 Recall, that (n, k)-multisig contract is a multisignature wallet with n private keys holders, which accepts requests to send messages if the request (aka order, query) collects at least k signatures of the holders.
 
 Based on original multisig contract code and updates by akifoq:
+
 - [original TON Blockchain multisig-code.fc](https://github.com/ton-blockchain/ton/blob/master/crypto/smartcont/multisig-code.fc)
 - [akifoq/multisig](https://github.com/akifoq/multisig) with fift libraries to work with multisig.
 
@@ -37,12 +38,10 @@ Before we begin our journey, check and prepare your environment.
 ```bash
 git clone https://github.com/akifoq/multisig.git
 cd ~/multisig
-``` 
-
+```
 
 ## 🚀 Let's get started!
 
-
 1. Compile the code to fift.
 2. Prepare multisig owners keys.
 3. Deploy your contract.
@@ -56,8 +55,8 @@ Compile the contract to Fift with:
 func -o multisig-code.fif -SPA stdlib.fc multisig-code.fc
 ```
 
-
 ### Prepare multisig owners keys
+
 #### Create participants keys
 
 To create a key you need to run:
@@ -66,7 +65,7 @@ To create a key you need to run:
 fift -s new-key.fif $KEY_NAME$
 ```
 
-* Where `KEY_NAME` is the name of the file where the private key will be written.
+- Where `KEY_NAME` is the name of the file where the private key will be written.
 
 For example:
 
@@ -107,8 +106,8 @@ After that, you need to run:
 fift -s new-multisig.fif 0 $WALLET_ID$ wallet $KEYS_COUNT$ ./keys.txt
 ```
 
-* `$WALLET_ID$` - the wallet number assigned for current key. It is recommended to use a unique `$WALLET_ID$` for each new wallet with the same key.
-* `$KEYS_COUNT$` - the number of keys needed for confirmation, usually equal to the number of public keys
+- `$WALLET_ID$` - the wallet number assigned for current key. It is recommended to use a unique `$WALLET_ID$` for each new wallet with the same key.
+- `$KEYS_COUNT$` - the number of keys needed for confirmation, usually equal to the number of public keys
 
 :::info wallet_id explained
 It's possible to create many wallets with the same keys (Alice key, Bob key). What to do if Alice and Bob already have treasure? That's why `$WALLET_ID$` is crucial here.
@@ -128,7 +127,7 @@ Bounceable address (for later access): kQBLuyZgCX21xy3V6QhhFQEPD4yFAeC4_vH-MY2d5
 (Saved wallet creating query to file wallet-create.boc)
 ```
 
-:::info 
+:::info
 If you have "public key must be 48 characters long" error, please make sure your `keys.txt` has unix type word wrap - LF. For example, word wrap can be changed via Sublime text editor.
 :::
 
@@ -166,7 +165,6 @@ sendfile ./wallet-create.boc
 
 After that, the wallet will be ready to work within a minute.
 
-
 ### Interact with multisig wallet
 
 #### Create a request
@@ -177,9 +175,9 @@ First you need to create a message request:
 fift -s create-msg.fif $ADDRESS$ $AMOUNT$ $MESSAGE$
 ```
 
-* `$ADDRESS$` - address where to send coins
-* `$AMOUNT$` - number of coins
-* `$MESSAGE$` - name of file for compiled message.
+- `$ADDRESS$` - address where to send coins
+- `$AMOUNT$` - number of coins
+- `$MESSAGE$` - name of file for compiled message.
 
 For example:
 
@@ -198,21 +196,23 @@ Next you need to choose a wallet to send a coins from:
 ```
 fift -s create-order.fif $WALLET_ID$ $MESSAGE$ -t $AWAIT_TIME$
 ```
+
 Where
-* `$WALLET_ID$` — is an ID of wallet backed by this multisig contract.
-* `$AWAIT_TIME$` — Time in seconds that smart contract will await signs from multisig wallet's owners for request.
-* `$MESSAGE$` — here is a name of message boc-file created on the previous step.
+
+- `$WALLET_ID$` — is an ID of wallet backed by this multisig contract.
+- `$AWAIT_TIME$` — Time in seconds that smart contract will await signs from multisig wallet's owners for request.
+- `$MESSAGE$` — here is a name of message boc-file created on the previous step.
 
 :::info
 If time equals `$AWAIT_TIME$` passed before the request signs, the request becomes expired. As usual, $AWAIT_TIME$ equals a couple of hours (7200 seconds)
 :::
 
 For example:
+
 ```
 fift -s create-order.fif 0 message -t 7200
 ```
 
-
 Ready file will be saved in `order.boc`
 
 :::info
@@ -227,8 +227,8 @@ To sign, you need to do:
 fift -s add-signature.fif $KEY$ $KEY_INDEX$
 ```
 
-* `$KEY$` - name of the file containing the private key to sign, without extension.
-* `$KEY_INDEX$` - index of the given key in `keys.txt` (zero-based)
+- `$KEY$` - name of the file containing the private key to sign, without extension.
+- `$KEY_INDEX$` - index of the given key in `keys.txt` (zero-based)
 
 For example, for our `multisig_key.pk` file:
 
@@ -239,12 +239,15 @@ fift -s add-signature.fif multisig_key 0
 #### Create a message
 
 After everyone has signed the order, it needs to be turned into a message for the wallet and signed again with the following command:
+
 ```
 fift -s create-external-message.fif wallet $KEY$ $KEY_INDEX$
 ```
+
 In this case, will be enough only one sign of wallet's owner. The idea is that you can't attack a contract with invalid signatures.
 
 For example:
+
 ```
 fift -s create-external-message.fif wallet multisig_key 0
 ```
@@ -267,6 +270,7 @@ If everyone else signed the request, it will be completed!
 
 You did it, ha-ha! 🚀🚀🚀
 
-## What's next?
+## See also
 
-- [Read more about multisig wallets in TON](https://github.com/akifoq/multisig) from akifoq
+- [Read more about multisig wallets in TON](https://github.com/akifoq/multisig) — _[@akifoq](https://t.me/aqifoq)_
+- [Multisig wallet v2](https://github.com/ton-blockchain/multisig-contract-v2)