From c20b2b5eb6d3e399846e43adb0f36c7cbc8b5ea4 Mon Sep 17 00:00:00 2001
From: Valentin Madrid <94240868+valentinmadrid@users.noreply.github.com>
Date: Tue, 26 Sep 2023 11:40:29 +0200
Subject: [PATCH 1/3] Add a responsibility section

---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index 7701ace9..79dae7ae 100644
--- a/README.md
+++ b/README.md
@@ -19,6 +19,10 @@ The Squads Protocol V4 program is deployed to:
 
 Both deployments can be verified using the [Ellipsis Labs verifiable build](https://github.com/Ellipsis-Labs/solana-verifiable-build) tool.
 
+## Responsibility
+
+By interacting with this program, users acknowledge and accept full personal responsibility for any consequences, regardless of their nature. This includes both potential risks inherent to the smart contract, also referred to as program, as well as any losses resulting from user errors or misjudgment.
+
 ### Compiling and testing
 
 You can compile the code with Anchor.

From c59eff3757715a9b30071fbbff4b877219a52e90 Mon Sep 17 00:00:00 2001
From: Valentin Madrid <94240868+valentinmadrid@users.noreply.github.com>
Date: Tue, 26 Sep 2023 11:41:31 +0200
Subject: [PATCH 2/3] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 79dae7ae..87ee0214 100644
--- a/README.md
+++ b/README.md
@@ -23,7 +23,7 @@ Both deployments can be verified using the [Ellipsis Labs verifiable build](http
 
 By interacting with this program, users acknowledge and accept full personal responsibility for any consequences, regardless of their nature. This includes both potential risks inherent to the smart contract, also referred to as program, as well as any losses resulting from user errors or misjudgment.
 
-### Compiling and testing
+## Compiling and testing
 
 You can compile the code with Anchor.
 ```

From ddfed3acbc32686d57aace0b43398e1a3c361938 Mon Sep 17 00:00:00 2001
From: Valentin Madrid <94240868+valentinmadrid@users.noreply.github.com>
Date: Tue, 26 Sep 2023 12:02:45 +0200
Subject: [PATCH 3/3] Update README.md

---
 README.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 87ee0214..a868a27c 100644
--- a/README.md
+++ b/README.md
@@ -23,6 +23,13 @@ Both deployments can be verified using the [Ellipsis Labs verifiable build](http
 
 By interacting with this program, users acknowledge and accept full personal responsibility for any consequences, regardless of their nature. This includes both potential risks inherent to the smart contract, also referred to as program, as well as any losses resulting from user errors or misjudgment.
 
+By using a multisig, it is important to acknowledge certain concepts. Here are some that could be misunderstood by users:
+ - Loss of Private Keys: If a participant loses their private key, the multisig may not be able to execute transactions if a threshold number of signatures is required.
+ - Single Point of Failure with Keys: If all keys are stored in the same location or device, a single breach can compromise the multisig.
+ - Forgetting the Threshold: Misremembering the number of signatures required can result in a deadlock, where funds cannot be accessed.
+ - No Succession Planning: If keyholders become unavailable (e.g., due to accident, death), without a plan for transition, funds may be locked forever.
+ - Transfer of funds to wrong address: Funds should always be sent to the multisig vault account, and not the multisig account address. Due to the design of the Squads Protocol program, funds deposited to the multisig account may not be recoverable.
+
 ## Compiling and testing
 
 You can compile the code with Anchor.
@@ -78,7 +85,6 @@ Instructions on how to interact with the Squads V4 program can be found in [the
 ## Security
 The Squads protocol has undergone various independent audits by leading cybersecurity and blockchain smart contract auditing firms.
 
-
 ## License
 
 The primary license for Squads Multisig Program V4 is the Business Source License 1.1 (`BUSL-1.1`), see [LICENSE](./LICENSE). The following exceptions are not licensed under the BULS-1.1, but are licensed separately as follows: