From a75cb6ec59a4b1e76711a56444532ad98010a534 Mon Sep 17 00:00:00 2001
From: Kshitij Chaudhary
 <78124453+KshitijChaudhary666@users.noreply.github.com>
Date: Wed, 15 Nov 2023 22:35:34 +0530
Subject: [PATCH] Update 20231005-Adding-bluesign-as-multi-sig.md

Adding bluesign's keys for transparency
---
 governance/20231005-Adding-bluesign-as-multi-sig.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/governance/20231005-Adding-bluesign-as-multi-sig.md b/governance/20231005-Adding-bluesign-as-multi-sig.md
index 742740e2..7203a522 100644
--- a/governance/20231005-Adding-bluesign-as-multi-sig.md
+++ b/governance/20231005-Adding-bluesign-as-multi-sig.md
@@ -50,7 +50,13 @@ This proposal does not introduce new dependencies to the Flow blockchain. It is
 
 ### Engineering Impact
 
-There is no direct engineering impact associated with this proposal. The addition of @bluesign as a signer involves administrative and governance considerations.
+There is no direct engineering impact associated with this proposal. The addition of @bluesign as a signer involves administrative and governance considerations. The key details are below - 
+
+projects/flow-352513/locations/us-east1/keyRings/flow/cryptoKeys/hc/cryptoKeyVersions/1
+
+Public Key         475aac6dc9e0a045323f8e24f0aa8ebbec9dfedc34a5cc47bbb206f8d639f03812231731a9608edab6582056ab0a3281350666330daca384c7dff777cc6823be
+Signature Algorithm     ECDSA_P256
+Hash Algorithm         SHA2_256
 
 ### Best Practices