GitHub/quartz
1
0
Fork 2
mirror of https://github.com/jackyzha0/quartz.git synced 2026-03-24 15:05:42 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

vault backup: 2022-12-02 09:48:47

Browse Source
This commit is contained in:
Jet Hughes 2022-12-02 09:48:47 +13:00
parent 47dc85244b
commit 95087f3fba
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/notes/think-writing.md
View File

@ -391,7 +391,7 @@ Within an existing closed BC with 10 participants. say we wanted to add another
- 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
- 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
# 02/12
@ -403,4 +403,4 @@ Yesterday
today
- get kernel to work
- read more papers
- tink about more scenarios
- tink about more scenarios+