GitHub/quartz
1
0
Fork 2
mirror of https://github.com/jackyzha0/quartz.git synced 2025-12-27 23:04:05 -06:00
Code Issues Actions Packages Projects Releases Wiki Activity

vault backup: 2022-12-15 15:57:19

Browse Source
This commit is contained in:
Jet Hughes 2022-12-15 15:57:19 +13:00
parent 3e731c7e35
commit a248b6f8d9
3 changed files with 92 additions and 85 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -4,89 +4,10 @@ tags:
---
[[veracity-week01]]
[[veracity-week02]]
[[veracity-week03]]
# 5/12
Week Review
- Got the prolog notebook to work.
- Read some interesting papers, tethering to public chain, reciprocal hyribd on/off chain governance
- thought about some scenarios
- kick out participant
- add new participant
- mistakently add senstitive data to chain
- one participant finds a security bug
This week
- try to implement some scenarios with a demo network
- add new participant: off-chain or on-chain voting? Should store some record of vote outcome on-chain
- consider more scenarios
- read more papers
More about adding new member
- Existing members vote to add new member
- on or off chain vote?
- store record of vote outcome on-chain
- consider special cases
- details of vote cutoff time
- parameters of vote change during vote
- hyperledger
- The purpose of add peer command is to write into ledger the fact of peer addition into the peer network. After a transaction with AddPeer has been committed, consensus and synchronization components will start using it.
- transaction to remove peer requires the node making the transaction to have the can-remove-peer permission
- can nodes with this perssion remove peers at will?
- not 1:1 nodes:accounts
- with HL Burrow you can use Solidity smart-contracts on Iroha
- iroha would either have to be off-chain voting then a trusted peer (or initial) would add them
- or: will need to look into HL Burrow but there might a way to have an on-chain smart contract voting system which automatically adds them depending on the vote
- I could think about how to implement such a smart contract
# 6/12
yesterday
- didn't get a lot done
- trying to get notebook to work with pyswip 0.2.10
- some thoughts about adding a new person to the chain
- looked at how to do it within hyperledger
- one existing peer needs permission to add another peer
what about removing a person from the chain?
- within hyperledger.
should i be using iroha2 - much better docs, newer version.
https://github.com/hyperledger/iroha/blob/iroha2-dev/docs/source/iroha_2_whitepaper.md
Im going to try to add a fifth peer to the four node demo network while its running
# 7/12
yesterday
- tried to get HL iroha to add a node
- think i got but i need to add some logs to check
what i did yesterday didn't work. spend some time this morning to try to get it to work. the docs are not very helpful. might give up on that for now.
brain is fried. will do some light (ish) reading.
---
# 8/12
https://doi.org/10.1016/j.pmcj.2019.101050
https://doi.org/10.1016/j.im.2021.103444
https://doi.org/10.1016/j.giq.2021.101625 [[Vulnerabilities on Hyperledger Fabric]]
I was able to start a network with three nodes and add a fourth. Next I will try to set up integration with hyperledger burrow so I can use smart contracts.
Changed docker container to use iroha-burrow instead of haydens own docker image. All works so far. installed solidity compiler and started trying to add a smart contract
---
# 9/12
https://doi.org/10.3390/admsci12030096
https://doi.org/10.1016/j.cities.2021.103325 [[Blockchain-based smart contracts as new governance tools for the sharing economy]]
---
- [[veracity-week01]]
- [[veracity-week02]]
- [[veracity-week03]]
- [[veracity-week04]]
# 12/12
https://doi.org/10.1109/DTPI52967.2021.9540069 [[Parallel Governance for Decentralized Autonomous Organizations enabled by Blockchain and Smart Contracts]]
@ -132,7 +53,7 @@ How could we use this for veracity? We could make a holochain app.
https://doi.org/10.1016/j.icte.2020.09.002
https://doi.org/10.1016/j.techfore.2020.120465
www.kaleido.io
www.kaleido.io: blockchain as a service
meeting
- removing participant
@ -142,4 +63,7 @@ meeting
- less protections
- tradeoff availablility vs confidentiality
I need to have a more skeptical mindset.
I need to have a more skeptical mindset.
Why cant we use blockchain as a service (blockstream, kaleido, alchemy, aws, IBM). Is it up to me to look into this and decide if we can rule it out?

79
content/notes/veracity-week04.md Normal file
View File

@ -0,0 +1,79 @@
# 5/12
Week Review
- Got the prolog notebook to work.
- Read some interesting papers, tethering to public chain, reciprocal hyribd on/off chain governance
- thought about some scenarios
- kick out participant
- add new participant
- mistakently add senstitive data to chain
- one participant finds a security bug
This week
- try to implement some scenarios with a demo network
- add new participant: off-chain or on-chain voting? Should store some record of vote outcome on-chain
- consider more scenarios
- read more papers
More about adding new member
- Existing members vote to add new member
- on or off chain vote?
- store record of vote outcome on-chain
- consider special cases
- details of vote cutoff time
- parameters of vote change during vote
- hyperledger
- The purpose of add peer command is to write into ledger the fact of peer addition into the peer network. After a transaction with AddPeer has been committed, consensus and synchronization components will start using it.
- transaction to remove peer requires the node making the transaction to have the can-remove-peer permission
- can nodes with this perssion remove peers at will?
- not 1:1 nodes:accounts
- with HL Burrow you can use Solidity smart-contracts on Iroha
- iroha would either have to be off-chain voting then a trusted peer (or initial) would add them
- or: will need to look into HL Burrow but there might a way to have an on-chain smart contract voting system which automatically adds them depending on the vote
- I could think about how to implement such a smart contract
# 6/12
yesterday
- didn't get a lot done
- trying to get notebook to work with pyswip 0.2.10
- some thoughts about adding a new person to the chain
- looked at how to do it within hyperledger
- one existing peer needs permission to add another peer
what about removing a person from the chain?
- within hyperledger.
should i be using iroha2 - much better docs, newer version.
https://github.com/hyperledger/iroha/blob/iroha2-dev/docs/source/iroha_2_whitepaper.md
Im going to try to add a fifth peer to the four node demo network while its running
# 7/12
yesterday
- tried to get HL iroha to add a node
- think i got but i need to add some logs to check
what i did yesterday didn't work. spend some time this morning to try to get it to work. the docs are not very helpful. might give up on that for now.
brain is fried. will do some light (ish) reading.
---
# 8/12
https://doi.org/10.1016/j.pmcj.2019.101050
https://doi.org/10.1016/j.im.2021.103444
https://doi.org/10.1016/j.giq.2021.101625 [[Vulnerabilities on Hyperledger Fabric]]
I was able to start a network with three nodes and add a fourth. Next I will try to set up integration with hyperledger burrow so I can use smart contracts.
Changed docker container to use iroha-burrow instead of haydens own docker image. All works so far. installed solidity compiler and started trying to add a smart contract
---
# 9/12
https://doi.org/10.3390/admsci12030096
https://doi.org/10.1016/j.cities.2021.103325 [[Blockchain-based smart contracts as new governance tools for the sharing economy]]
---

4
content/notes/veracity.md
View File

@ -18,6 +18,10 @@ Blockchain technology falls into two distinct classes: open (permissionless) blo
# Notes
- [think-writing/log](notes/think-writing.md)
- [[veracity-week01]]
- [[veracity-week02]]
- [[veracity-week03]]
- [[verac]]
- [[isolated scenarios]]
- [veracity-chain](notes/veracity-chain.md)
- [reading-papers](notes/reading-papers.md)