From 3c3d1a190796eed6541b62fe4233735ac0d2f708 Mon Sep 17 00:00:00 2001 From: Jet Hughes Date: Fri, 2 Dec 2022 11:50:35 +1300 Subject: [PATCH] vault backup: 2022-12-02 11:50:35 --- content/notes/think-writing.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/content/notes/think-writing.md b/content/notes/think-writing.md index 0a2eb5eab..2e14dac39 100644 --- a/content/notes/think-writing.md +++ b/content/notes/think-writing.md @@ -392,7 +392,8 @@ Within an existing closed BC with 10 participants. say we wanted to add another - 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 doing basically a hard fork - - i guess thats a lot easier in a closed BC than an open one + - what happens to the other side of the fork? just stops. + - i guess thats a lot easier in a closed BC than an open one # 02/12 Yesterday @@ -403,4 +404,6 @@ Yesterday today - get kernel to work - read more papers -- tink about more scenarios+ \ No newline at end of file +- tink about more scenarios+ + +**Scenario 3 cont.**