Introduction to Peerplays
Consensus Mechanisms Compared
Peerplays Technical Summary
Intro to Peerplays Tokens
Intro to Peerplays Liquidity Pools
Staking (PowerUp) in Peerplays
Gamified User Namespaces and Subject Matter Expert Committees
Peer-to-Peer Autonomous Organizations: Flow Diagram
Delegated Proof of Stake (DPOS)
Gamified Proof of Stake (GPOS)
Sidechain Operator Nodes (SONs)
NFTs and Marketplace
What is a Peerplays Witness?
Becoming a Peerplays Witness
Obtaining private keys for cli_wallet
Witness Node Hardware Requirements
Witness Node Docker Install
Witness Node GitLab Artifact Install
Setting up a Witness Node
Updating a Witness Node
Setting up a Witness Node with Docker
Setting up the faucet
Bookie Oracle Suite (BOS)
Introduction to BOS
Manual Intervention Tool (MINT)
Introduction to Data Proxies
How Data Proxies Work
Data Proxy Set Up
Creating Your Own Data Proxy
Proxy Payment Considerations
Random Number Generator (RNG)
RNG Technical Summary
Peerplays Core API
Market Maker API
Connecting Elasticsearch to a blockchain node
GitLab Ticket Templates
Peerplays Disaster Recovery Plan
Sept 2021 Mainnet Outage - Postmortem Report
The scoped labels (ending with ::) are mutually exclusive. Only one of these labels can be assigned at a time to an issue.
All issues should have a
scoped label attached to them. The following is a proposed lifecycle an issue should have:
Pending - Issues that are newly created and haven't been reviewed.
Accepted - Issues that are newly created and have been accepted after review.
In Progress - Issues that are currently being worked on.
In Review - Issues that require a proposed solution to be reviewed.
In Testing - Issues that require a proposed solution to be tested.
Completed - Issues that are closed with a working solution.
This will cover a standard lifecycle of an issue. There are other
labels for issues that are not being worked on:
On Hold - Issues that were at least accepted, that should not be worked on at the moment.
Blocked - Issues that cannot be worked on due to other factors linked to it.
Revision Needed - Issues that need to be revised before being accepted.
(optional) Issues that are marked as low priority.
(optional) Issues that are marked as medium priority.
(optional) Issues that are marked as high priority.
(optional) Issues that are marked as critical priority. Should be taken care of ASAP.
Issues that are newly created and haven't been reviewed.
Issues that are newly created and have been accepted after review.
Issues that are currently being worked on.
Issues that require a proposed solution to be reviewed.
Issues whose proposed solution is being tested.
Issues that are closed with a working solution.
Issues that were at least accepted, that should not be worked on at the moment.
Issues that cannot be worked on due to other factors linked to it.
Issues that need to be revised before being accepted.
Issues that are an unexpected, or incorrect result in the project.
Issues that bring new functionality to the project.
Issues that relate to the documentation of the project.
Issues that are questions related to the project.
Issues that require maintenance on the project.
(optional) Issues that are duplicates of existing issues in the same project.
(optional) Issues that discuss specific project changes.
(optional) Issues that relate to the security of the project.
GitLab - Previous
GitLab Ticket Templates
Next - GitLab
Export as PDF