From a6ff7eb3f632d131c7eb32da7a226ac4d247f702 Mon Sep 17 00:00:00 2001 From: Jet Hughes Date: Thu, 1 Dec 2022 15:37:02 +1300 Subject: [PATCH] vault backup: 2022-12-01 15:37:02 --- content/notes/think-writing.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/notes/think-writing.md b/content/notes/think-writing.md index 81662d1f4..c9fd0c905 100644 --- a/content/notes/think-writing.md +++ b/content/notes/think-writing.md @@ -387,4 +387,9 @@ Today Within an existing closed BC with 10 participants. say we wanted to add another participant as a validator node. they run the node software on a machine. this node is fully priviledged. they new member had to go through a screening and sign a legal contract to ensure they are not a bad actor. this node recieves a copy of the blockchain so far, and begins participating in the consensus algorithm and submitting transactions. their contract is added to the blockchain as their first transaction (maybe. or it can be stored somewhere else). **Scenario 3** - \ No newline at end of file + The new participant makes a mistake and puts the entire document instead of just a hash. this document is sensitive and contains data that should be kept private. + - automatically perform some checks to ensure the data lodged during a transaction is always just a hash. + - is this the responsibility of the participant or the network to prevent. should be participant but that doesn't mean there shouldn't be some checks that the network can do + - do we want to store data other than hashed documents. + - if the document is lodged on the BC can the consortium agree to remove it by + - i guess thats a lot easier in a closed BC than an open one \ No newline at end of file