mirror of
https://github.com/jackyzha0/quartz.git
synced 2025-12-27 14:54:05 -06:00
49 lines
3.2 KiB
Markdown
49 lines
3.2 KiB
Markdown
---
|
||
title: "blockchain-bursary"
|
||
aliases:
|
||
tags:
|
||
- project
|
||
---
|
||
|
||
# Questions for David
|
||
- what is on-chain vs off-chain governance
|
||
- confirm understanding of permissioned vs permissionless blockchain
|
||
- My understanding of the issue is that permissioned blockchains have no incentives for participant to validate transactions. So I am trying to create a permissioned blockchain with these incentives
|
||
- who are the nodes in a closed blockchain,
|
||
|
||
# Notes
|
||
- [412-lectures](notes/412-lectures.md)
|
||
- [governance](notes/governance.md)
|
||
- [decentralized-autonomous-organization](notes/decentralized-autonomous-organization.md)
|
||
- [DeFi](notes/DeFi.md)
|
||
- [dApps](notes/dApps.md)
|
||
- [sybil-problem](notes/sybil-problem.md)
|
||
- [smart-contracts](smart-contracts)
|
||
|
||
# Reading
|
||
- [ ] https://en.wikipedia.org/wiki/Cyberocracy
|
||
- [ ] https://en.wikipedia.org/wiki/Government_by_algorithm
|
||
- [ ] https://coopahtroopa.mirror.xyz/_EDyn4cs9tDoOxNGZLfKL7JjLo5rGkkEfRa_a-6VEWw
|
||
- [ ] https://101blockchains.com/permissioned-blockchain/
|
||
- [ ] http://eyler.freeservers.com/JeffPers/jefpco55.htm?ref=hackernoon.com
|
||
- [ ] https://medium.com/@Vlad_Zamfir/against-on-chain-governance-a4ceacd040ca
|
||
- [ ] https://medium.com/@FEhrsam/blockchain-governance-programming-our-future-c3bfe30f2d74
|
||
|
||
# Log
|
||
- 14/11
|
||
- starting today
|
||
- reviewing 412 lectures 7 and 9
|
||
- reading https://101blockchains.com/blockchain-governance/
|
||
|
||
# Abstract
|
||
Blockchain technology falls into two distinct classes: open (permissionless) blockchains such as those underlying bitcoin, Ethereum and Cardano; and closed (permissioned) blockchains such as implemented in the Hyperledger Fabric project. To motivate decentralised participation, open blockchains (presently) require an associated cryptocurrency, which can be a risky distraction. However, closed blockchains are considered by some to be insufficiently decentralised.This summer project aims to prototype a compromise: a closed blockchain system that encodes voting rules about self-governance, so that closed blockchain technology can be used in a more open manner. Experience in programming blockchain systems is not assumed. Depending on the student involved, the project will balance work between design and modelling of the blockchain governance rules, and implementation of such a rule set over an existing closed blockchain system.
|
||
|
||
# Terms
|
||
**Open Blockchain** — A public network that maintains an immutable record of transactions. Anyone can publish a transaction and participate in the network by adhering to a set of published rules. Examples: [Bitcoin](https://en.wikipedia.org/wiki/Bitcoin), [Litecoin](https://en.wikipedia.org/wiki/Litecoin)
|
||
|
||
**Closed Blockchain** — A private network that maintains a shared record of transactions. The network is accessible only to those who have permission and transactions can be edited by administrators. Examples: [Hyperledger](http://hyperledger.com/), [Ripple](https://ripple.com/), [Eris](https://erisindustries.com/)
|
||
|
||
**Governance** — A structure through which a participant or user of a system agrees to use the system. [governance](notes/governance.md) E.g., Governments.
|
||
|
||
# Sources
|
||
- https://medium.com/@WayneVaughan/open-vs-closed-blockchains-let-s-end-this-madness-8313e4095ead |