mirror of
https://github.com/ipdb/website.git
synced 2024-11-13 16:54:50 +01:00
Added Operations.md
File setting out Rules and Processes for IPDB Foundation. Will invite Caretakers to collaborate and contribute once we have feedback from internal team.
This commit is contained in:
parent
79a850906a
commit
3dd7d3a8c6
2
FAQ.md
2
FAQ.md
@ -74,7 +74,7 @@ No. IPDB has native assets but those assets are not a currency. Instead, anyone
|
||||
Yes. Anyone can see the transactions made on IPDB. IPDB is a public instance of BigchainDB.
|
||||
|
||||
### Can IPDB talk to other blockchains?
|
||||
BigchainDB has already been integrated into other services (see our Integrations section). Other integrations are waiting to be created. If you have a request, or better still, if you want to help out, you can head over to the [BigchainDB developer community](https://github.com/bigchaindb/bigchaindb) at Github.
|
||||
BigchainDB has already been integrated with other services (see our Integrations section). Other integrations are waiting to be created. If you have a request, or better still, if you want to help out, you can head over to the [BigchainDB developer community](https://github.com/bigchaindb/bigchaindb) at Github.
|
||||
|
||||
### Why is IPDB better than IPFS, Ethereum, Bitcoin, Dogecoin…?
|
||||
IPDB is not a replacement for decetralized computation platforms such as Ethereum, file storage from IPFS, or cryptocurrencies such as Bitcoin. IPDB is *complimentary* to them. We see IPDB as filling a gap in the decentralized stack.
|
||||
|
134
OPERATIONS.md
Normal file
134
OPERATIONS.md
Normal file
@ -0,0 +1,134 @@
|
||||
# IPDB Operation and Rules
|
||||
March 17, 2016
|
||||
|
||||
## Definitions
|
||||
- **ascribe** means ascribe GmbH, a corporation registered in Berlin.
|
||||
- **BigchainDB** means the software project operated by ascribe and available at https://github.com/bigchaindb/bigchaindb.
|
||||
- **Board** means the Board of Directors of the Foundation.
|
||||
- **Caretakers** means the member organizations of the Foundation.
|
||||
- **Caretaker Nodes** means the instance of BigchainDB operated by a Caretaker.
|
||||
- **Foundation** means the IPDB Foundation e.V., registered in Germany.
|
||||
- **IPDB** means the decentralized database based on BigchainDB and operated by the Foundation and its Caretakers.
|
||||
- **Keys** means a public-private key pair generated by a Caretaker and used in IPDB.
|
||||
- **Transaction** means a write operation to IPDB.
|
||||
- **User** means an individual using IPDB, as defined by a unique Key.
|
||||
|
||||
## Roadmap
|
||||
- May 2016 - Announcements of a “public BigchainDB” at various conferences: re:publica (Berlin), csv,conf,v2 (Berlin), OuiShare (Paris), including the announcement of some Caretakers and a private test net.
|
||||
- June 8, 2016 - Announcement of IPDB at Internet Archive event, including announcement of additional Caretakers and a public test net.
|
||||
- September 1, 2016 - Launch of public production net, along with billing system.
|
||||
|
||||
## Structure
|
||||
### Mission Statement
|
||||
-The Foundation’s mission is:
|
||||
|
||||
To support an open Internet by developing and operating a decentralized database based on BigchainDB that anyone can use.
|
||||
|
||||
### Overview
|
||||
- The Foundation is governed by its members. Caretakers will elect a board
|
||||
|
||||
### Rules
|
||||
|
||||
### Member Organizations: Caretakers
|
||||
|
||||
#### General Requirements
|
||||
- A majority of Caretakers must be charitable organizations, not-for-profit organizations, or organizations with structures that are substantially the same as the structures listed above.
|
||||
- To vote in favour of a new Caretaker, the existing Caretaker must have a good faith belief that the new Caretaker has demonstrated a commitment to the values of an open, transparent, and decentralized Internet. This commitment should be stated in the new Caretaker’s mandate or mission statement, or demonstrated by the new Caretaker’s track record and current operations.
|
||||
|
||||
#### Adding Caretakers
|
||||
- Caretakers can be added by a 2/3 majority vote of existing Caretakers.
|
||||
- Organizations that wish to become Caretakers can:
|
||||
- be nominated by an existing Caretaker or the Board.
|
||||
- apply to be considered as a Caretaker.
|
||||
|
||||
#### Removing Caretakers
|
||||
- Caretakers can be removed by a 2/3 majority vote of existing Caretakers if the subject Caretaker has:
|
||||
- Violated the Rules.
|
||||
- Manipulated or attempted to manipulate voting or the BigchainDB software to accept or reject a transaction inappropriately.
|
||||
- Manipulated or attempted to manipulate a past transaction.
|
||||
- A Caretaker can be removed for any reason with a 3/4 vote of all Caretakers.
|
||||
|
||||
#### Term Limit
|
||||
- Initial Caretakers will be provided with a
|
||||
- Caretakers are elected for one term with a two year duration.
|
||||
- Caretakers are automatically nominated for reelection at the end of their term unless they ask to be excluded.
|
||||
- Caretakers can serve a maximum of 4 terms.
|
||||
|
||||
### Board of Directors
|
||||
|
||||
#### Number of Directors
|
||||
- At any given time there will be no more than 5 Directors.
|
||||
- The Directors will include at least one individual who is employed by ascribe and at least one individual who is not employed by or a director of any of the Caretakers.
|
||||
|
||||
#### Electing Directors
|
||||
- Directors can be nominated by the Caretakers or by the Board.
|
||||
- The Directors will be elected by the Caretakers.
|
||||
|
||||
## Operations
|
||||
|
||||
### Keys
|
||||
|
||||
#### Generating Keys
|
||||
- Caretakers will generate Keys using [PROCESS].
|
||||
|
||||
#### Securing Keys
|
||||
- Caretakers will provide their public key to the Foundation and will secure their private key.
|
||||
- Private keys will be secured by [PROCESS]
|
||||
|
||||
#### Invalidating Keys
|
||||
- Caretakers can vote by a 2/3 majority to invalidate Keys if:
|
||||
- They have reason to believe the Key has been compromised.
|
||||
- [OTHER]
|
||||
|
||||
### Caretaker Nodes
|
||||
|
||||
#### Operating a Caretaker Node
|
||||
- Caretaker Nodes can be operated virtually on a cloud service provider, or in hardware.
|
||||
|
||||
#### Caretaker Node Security
|
||||
- Caretakers must abide by the following Security requirements in the operation of their Caretaker Node:
|
||||
- [DETAILS].
|
||||
|
||||
### Transactions
|
||||
|
||||
#### Transaction Processing
|
||||
- New Transactions are processed in accordance with BigchainDB.
|
||||
|
||||
#### User Transactions
|
||||
- Anyone can send a Transaction to IPDB if that Transaction is signed with their Key.
|
||||
- Users get [NUMBER] free transactions per month.
|
||||
- Users who want more than [NUMBER] transactions can buy addional transactions from the Foundation or through a Transaction Agents.
|
||||
|
||||
#### Transaction Agents
|
||||
- Users can purchase additional Transactions from Transaction Agents at a price negotiated with a Transaction Agent.
|
||||
- Transaction Agents pay for Transactions at a rate set by the Foundation.
|
||||
- Transaction Agents compete with one another on price and services.
|
||||
|
||||
#### Legal Requests
|
||||
- Caretakers may only comply with duly issued legal requests for information, backed with documentation such as a court order or warrant.
|
||||
- If any Caretaker or the Foundation receives a request invoving its role as a Caretaker, the recipient must notify the other Caretakers and the Foundation immediately.
|
||||
|
||||
#### Transaction Security
|
||||
- If a Caretaker repeatedly votes against the majority of Caretakers, the Caretaker’s Key will be automatically revoked.
|
||||
- [DETAILS]
|
||||
- If a Caretaker attempts to modify a past Transaction, the Caretaker’s Key will be automatically revoked. The Caretaker can apply for a new key after 30 days, including an explanation of the incident.
|
||||
- [DETAILS]
|
||||
|
||||
### Governance
|
||||
|
||||
#### Board Meetings
|
||||
- The Board will meet at least every 90 days. Board meetings must be conducted in person or by tele- or videoconference.
|
||||
A quorum of 4 Board members is required to call the meeting to order.
|
||||
- Votes by the Board pass with a simple majority, except for votes to add or remove Caretakers
|
||||
|
||||
#### Votes by Board
|
||||
|
||||
- Votes by the Board must be conducted in person or by tele- or videoconference.
|
||||
- Votes by the Board pass with a simple majority.
|
||||
|
||||
#### Votes by Caretakers
|
||||
- Votes by the Caretakers must be conducted in person, by tele- or videoconference, or through the IPDB voting system.
|
||||
- Votes taken by Caretakers will be binding on the Board if the vote passes with a 75% majority.
|
||||
|
||||
#### Changes to the Rules
|
||||
- Changes to the Rules must be approved by a majority of the Board and a majority of the Caretakers.
|
Loading…
Reference in New Issue
Block a user