From 5faa774432b7012f0c9ede9783e2f59afe9e2966 Mon Sep 17 00:00:00 2001
From: Arturo Beccar-Varela <107512933+arturoBeccar@users.noreply.github.com>
Date: Tue, 21 Nov 2023 16:11:54 -0300
Subject: [PATCH] Added reference to implementation PR

---
 test-cases/set-contract-storage/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test-cases/set-contract-storage/README.md b/test-cases/set-contract-storage/README.md
index 51b1a8e..1b11193 100644
--- a/test-cases/set-contract-storage/README.md
+++ b/test-cases/set-contract-storage/README.md
@@ -35,4 +35,4 @@ This feature is practically complete, it's just missing a size check. Implementi
 
 The function `set_contract_storage()` sets the storage in a contract. There was a missing validation in integration tests that was present in e2e. This validation checked that the `size` of the storage set did not exceed 16380 bytes.
 
-We added a validation to the function `set_contract_storage()` in integration tests that checks the size of the input value against the same limit set in e2e test: 16380 bytes. In case this limit is exceeded, a panic is raised with the message: "Value too large to be stored in contract storage, maximum size is {} bytes".
+In our proposed implementation in [PR #1961](https://github.com/paritytech/ink/pull/1961), we added a validation to the function `set_contract_storage()` in integration tests that checks the size of the input value against the same limit set in e2e test: 16380 bytes. In case this limit is exceeded, a panic is raised with the message: "Value too large to be stored in contract storage, maximum size is {} bytes".