Commit 4284cb31 authored by packetflow's avatar packetflow 💬

fixed reference errors

parent da978d54
---
title: In Depth Review by the Altlook
weight: 1
pre: "<b>1. </b>"
chapter: true
---
{{< imagesurlsheaders "images_headers/Pressreleases.png" >}}
<object data="https://loved-eel.cdn.pirl.live/ipns/QmVKFJs81erni4KV6Hzt2xVwGtC2P1WtE9A4MxNThFVFVh/images/cloud/PIRL_-_In_Depth_Review.pdf" type="application/pdf" width="1400px" height="1400px">
<embed src="https://loved-eel.cdn.pirl.live/ipns/QmVKFJs81erni4KV6Hzt2xVwGtC2P1WtE9A4MxNThFVFVh/images/cloud/PIRL_-_In_Depth_Review.pdf">
<p>This browser does not support PDFs. Please download the PDF to view it: <a href="cloud/PIRL_-_In_Depth_Review.pdf">Download PDF</a>.</p>
</embed>
</object>
---
Author(s):
@dptelecom
Contributor():
---
title: Proof of review
weight: 2
pre: "<b>2. </b>"
chapter: true
---
{{< imagesurlsheaders "images_headers/Pressreleases.png" >}}
<object data="https://loved-eel.cdn.pirl.live/ipns/QmVKFJs81erni4KV6Hzt2xVwGtC2P1WtE9A4MxNThFVFVh/images/cloud/Pirl-v1.pdf" type="application/pdf" width="1400px" height="1400px">
<embed src="https://loved-eel.cdn.pirl.live/ipns/QmVKFJs81erni4KV6Hzt2xVwGtC2P1WtE9A4MxNThFVFVh/images/cloud/Pirl-v1.pdf">
<p>This browser does not support PDFs. Please download the PDF to view it: <a href="https://loved-eel.cdn.pirl.live/ipns/QmVKFJs81erni4KV6Hzt2xVwGtC2P1WtE9A4MxNThFVFVh/images/cloud/Pirl-v1.pdf">Download PDF</a>.</p>
</embed>
</object>
---
Author(s):
@dptelecom
Contributor():
---
title: Press releases PirlGuard
weight: 3
pre: "<b>3. </b>"
chapter: true
---
{{< imagesurlsheaders "cloud/pirlguard.png" >}}
## Press releases
But first in short what is PirlGuard
PirlGuard - Innovative Solution against 51% Attacks
### you can read the whole Kb here [PirlGuard]({{< ref "/development/core/PirlGuard" >}})
#### You can also watch this video:
<iframe width="560" height="315" src="https://www.youtube.com/embed/Q-f01eFYlig" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
### How PirlGuard works?
In order to disrupt the mechanics behind 51% attack that allows an attacker to be successful, we have deployed a core solution with a modified consensus algorithm that will defend our blockchain and many others in the near future from virtually all 51% attacks.
### PirlGuard System
With the PirlGuard Protocol deployed the chances of an attack succeeding are vastly reduced. As we know once the attacker has created a longer chain through privately mining a separate chain they will then have to broadcast it to the network. Once the attacker opens their node for peering it will attempt to peer with rest of the nodes on the network, telling them that they are wrong. However, once this happens PirlGuard will drop the peer and penalize them by sentencing them to mine X amount of penalty blocks due to their un-peered mining. The amount of penalty blocks assigned depends on the amount of blocks that the malicious miner mined in private.
The PirlGuard security protocol greatly deters attackers from attempting malicious peering giving the main network a much needed boost in security. This new security mechanism reduces the chances to approximately 0.03%.
### Open Source
Pirl has so far contributed to blockchain by developing the first Ethash code based masternode network, the first private IPFS implementation running over a masternode network and is currently working on their own private encrypted blockchain storage solution.
The PirlGuard Security Protocol will be added to our open source library along with the core of the project.
At Pirl we are developing to revolutionize and streamline blockchain technology for the entire blockchain industry. This means our code will be available to anyone to study, educate, test, modify or apply towards their own blockchain network security against future 51% attacks.
[Source Code:](https://git.pirl.io/community/pirl)
[Website:](https://pirl.io/en)
### <span style="color:red">Press releases PirlGuard:</span>
[CCN.com](https://www.ccn.com/pirlguard-innovative-solution-against-51-attacks)
### <span style="color:green">Other projects using the PirlGuard solution:</span>
#### EtherGem (EGEM)
<img src="cloud/egem1.png" align="left"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
[EGEM website](https://egem.io)
### Here is the official announcement from the EGEM lead dev Riddlez666
{{< imagesurlsheaders "cloud/edgemdev.jpg" >}}
{{< imagesurlsheaders "cloud/egem4.jpg" >}}
<br>
<br>
<br>
<br>
#PirlTogetherStrong
Yours,
Pirl Team
---
Author(s):
The Pirl Team
Contributor():
@dptelecom
---
title: Press releases
weight: 6
pre: "<b>5. </b>"
chapter: true
---
{{< imagesurlsheaders "images_headers/Pressreleases.png" >}}
{{< imagesurlsheaders "cloud/pressrelease-image-1024x682.jpg" >}}
## Press releases
#### 1.) [In Depth Review by the Altlook ]({{< ref "/Press releases/Altlook" >}})
#### 2.) [Proof of review ]({{< ref "/Press releases/POR" >}})
#### 3.) [PirlGuard at the press and other projects using the PirlGuard solution ]({{< ref "/Press releases/PirlGuard" >}})
---
Author(s):
@dptelecom
Contributor():
---
title: Attack Aftermaths & Securing Funds
weight: 4
pre: "<b>4. </b>"
chapter: true
---
{{< imagesurlsheaders "images_headers/aftermath.png" >}}
## Dear Community,
As you are all aware the Pirl network suffered a 51% and Double Spend attack,
which was mitigated shortly after it was discovered. However,
during the week prior to discovery,
the attacker managed to double spend 1,961,500 PIRL and deposit them across multiple exchanges,
mainly Cryptopia.
Now that Cryptopia has concluded their audit,
there are two paths forward to get the market reopened:
### 1) The exchange can adjust users’ account balances to account for the PIRL that was double spent on Cryptopia (thereby leading to a loss of funds for PIRL community members)
Or
### 2) We can generate a one-time Superblock that will cover all Community members accounts AND recover all remaining PIRL in the Attackers addresses.
Even though the majority of the Dev Fund have not been spent,
we still do not have enough to cover the 1,961,500 PIRL deficit caused by the attacker and forcing the community to pay for the attacker's actions is not an option.
As such, the only viable option for us at this stage is to create the reimbursement coins with the fork that will recover the attacker's funds and help prevent future attacks of this type.
We want to do this completely transparently and allow everyone to monitor the creation and transfer of the funds back to Cryptopia.
The funds will be created in complete transparency through a superblock,
which will zero the 825 000 Pirl found in attackers possession and add the 1,1 million PIRL that was already maliciously sold to the Pirl community on Cryptopia.
The 1,961,500 PIRL that was double spent has already impacted the market by being sold on Cryptopia,
this Superblock will not be adding to inflation, it will actually lead to a deflation of the 825,000 PIRL that will be recovered from the attacker.
To explain how this is not adding inflation,
it should be added that due to the changes to the difficulty algorithm done with block 2,000,000, the intended blocktime of 13 seconds erroneously went from 13 seconds to 18 seconds since then.
This difference in the blocktime after its implementation from 13s to 18s we have generated 142,734 blocks less than we would have. Which is 1,427,342 PIRL deflation over the period since block 2,000,000
Pirl has met many challenges in the past year, we have overcome everything and not only survived but thrived with new technology and features development.
This is just another step on our rough journey, and we must make it, together as we always did.
The PIRL Team
---
Author(s):
@dptelecom
Contributor():
---
title: Fork 2018-11
weight: 5
pre: "<b>5. </b>"
chapter: true
---
{{< imagesurlsheaders "images_headers/hardfork.png" >}}
### Pirl Community!
Winter is coming. So is the anticipated fork for Pirl.
More security, higher rewards, more innovation. Sometimes bad things happen for a good reason.
### What do we introduce to the network with the fork?
#### Security
The fork will give birth to an innovative solution against a well-known problem in blockchain infrastructure.
Pirl has developed and successfully tested a penalty system which directly impacts the mechanics of a 51% attack making it hard and unworthy to achieve. Any attempt on double spending on Pirl network after the update will have a failure rate of approximately 99.997%.
As extra security layers, notary contracts will be deployed both on Pirl and Ethereum chains. These layers are being added to make sure that if someone by a very slim approximate 0.003% chance manages to succeed with a future 51% attack they will be unable to liquidate their balance accrued from the attack.
Just to be completely sure, there is also a monitoring system going into place that will notify us if someone is attempting an attack. So we can follow their status.
Complete details on the security and source code will be available after the successful fork.
### Difficulty Adjustments
In order to consolidate fixes and limiting the amount of forks needed to perform different tasks we have also been using this time to test new difficulty settings with the goal of more accurate block times. Our new difficulty setting also being initiated in this fork should bring us closer to the 13s block time target. As a result of this more accurate block time we will see an increase of rewards. The expected daily reward gains are approximately 23.52% for both our miners and masternode owners.
###v Super Block
Detailed information here: [Attack Aftermath & Securing Funds]({{< ref "/development/core/Followup 51 percent attack" >}})
### When will the new node be provided, what is the action plan?
-The hulk security update node will be brought to light on Tuesday, November 13th a mandatory update for all the masternode and pool operators.
-After the node is made available everyone will have to be done with the node update by November 17th
-The fork will take place @ block 2442442 estimated to occur on November 20th based on current block time.
-Exchanges shall reopen shortly after successful fork and node update.
### What do I have to do as a Pirl User?
As Pirl User, you will get a wallet update which you will have to download and install. The wallet will notify you about a new update.
Just simply download and install the update and you are ready to go.
Note: Web wallet will be updated on our side.
### What do I have to do as a Pirl Node Operator?
As node operator or pool admin, you will have to update your node.
If you don’t do this, Pirl will fork and you will not be part of the main network.
It is vital that you update your node at the time of the fork.
### What do I have to do as a Masternode Operator?
One-Click Masternodes DO NOT require any action! They will be updated automatically by Poseidon.
The owners of a Manual setup masternode need to update their masternode by installing the new binaries.
We recommend that you install the new binaries as soon as possible.
Binaries will be available [Downloads]({{< ref "/Downloads" >}})
#PirlTogetherStrong
Yours,
Pirl Team
---
Author(s):
@dptelecom
Contributor():
This diff is collapsed.
---
title: Core
weight: 1
pre: "<b>1. </b>"
chapter: true
---
{{< imagesurlsheaders "images_headers/development.png" >}}
## Updates about development for PirlCore
Updates about development for PirlCore can be found on the next pages.
#### 1.) [Changelog Core]({{< ref "/development/core/changelog" >}})
#### 2.) [51% attack on the Pirl network]({{< ref "/development/core/hulk" >}})
#### 3.) [TestNetwork]({{< ref "/development/core/testnetwork" >}})
#### 4.) [Attack Aftermath & Securing Funds]({{< ref "/development/core/Followup 51 percent attack" >}})
#### 5.) [Hard Fork 2018-11-20]({{< ref "/development/core/Fork 2018-11" >}})
#### 6.) [PirlGuard]({{< ref "/development/core/PirlGuard" >}})
{{< imagesurlsheaders "cloud/Pirl_Energy.gif" >}}
---
Author(s):
@dptelecom
Contributor():
---
title: Changelog Core
weight: 1
pre: "<b>1. </b>"
chapter: true
---
{{< imagesurlsheaders "images_headers/development.png" >}}
## All notable changes to this project will be documented in this file.
## Version <span style="color:green">v---------</span>
## Added
## Changed
## Removed
-
## Unreleased
-
---
Author(s):
@dptelecom
Contributor():
---
title: ATTACK & HULK
weight: 2
pre: "<b>2. </b>"
chapter: true
---
{{< imagesurlsheaders "images_headers/hulk.jpg" >}}
Pirl Community!
A 51% attack on the Pirl network was identified on 10/14/2018. As soon as it was discovered we conducted an investigation to verify the findings and asked exchanges to place their Pirl wallets into maintenance, until a more detailed analysis could be completed.
Once the attack was mitigated, we took the necessary steps to completely lock out the attackers and make sure that the exchange wallets were safe. We are now just steps away from deploying our remedial actions to the Pirl Blockchain, which will help prevent this kind of attack from happening in the future.
How ? (by using the HULK)
The network security solution we code named “Hulk” will be deployed in 2 stages:
Stage 1: Fork -
Remediate the consequences of the attack and remove all artificially created PIRL while deploying Notary Smart Contracts both on the Pirl and Ethereum chains, adjust validation block count on exchanges, and the setting up of an O.M.S (Orphan Monitoring System) which will invalidate any node attempting an attack on the network.
Stage 2: Masternode update -
Pirl Masternodes will become a firewall against any bad actor. With this new code the masternode network will be an active participant in ensuring the authenticity of transactions on the Pirl Blockchain.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The information above is far from detailed but, in order to be safe until “Hulk” first step is implemented, we will keep the blueprints of our security private.
We are extremely happy to have your support, reading the messages in discord have done a lot for the team motivation during the entire operation. We shouldn’t forget to mention Cryptopia and STEX as well for their fast and professional reaction which was also a critical factor for a successful outcome.
This is just a quick update, more information will follow!
#PirlTogetherStrong
Yours,
Pirl Team
---
Author(s):
@dptelecom
Contributor():
---
title: PirlTestNetwork
weight: 3
pre: "<b>3. </b>"
chapter: true
---
{{< imagesurlsheaders "images_headers/testnetwork.png" >}}
### Pirl Community!
A 51% attack on the Pirl network was identified on 10/14/2018.
Once the attack was mitigated, we took the necessary steps to completely lock out the attackers and make sure that the exchange wallets were safe.
We are now just steps away from deploying our remedial actions to the Pirl Blockchain, which will help prevent this kind of attack from happening in the future.
How ? (by using the HULK)
The network security solution we code named “Hulk” will now be tested on the PirlTestNetowrk
### if you want to participate in the future grow and security you can join in with you hash power:
### [PirlTestNetwork Pool](http://testnetpool.pirl.io/#/ "PirlTestNetwork Pool").
### [PirlTestNetwork Stats](http://devstats.pirl.io/ "PirlTestNetwork Stats").
### how to setup mining
### [Mining]({{< ref "/mining" >}})
{{% notice warning %}}
The testnetwork is not paying real Pirl because its a testnetwork keep this in mind!!!
{{% /notice %}}
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The information above is far from detailed but, in order to be safe until “Hulk” first step is implemented, we will keep the blueprints of our security private.
We are extremely happy to have your support, reading the messages in discord have done a lot for the team motivation during the entire operation.
This is just a quick update, more information will follow!
#PirlTogetherStrong
Yours,
Pirl Team
---
Author(s):
@dptelecom
Contributor():
---
title: Wallets
weight: 2
pre: "<b>2. </b>"
chapter: true
---
{{< imagesurlsheaders "images_headers/development.png" >}}
## Updates about development for PirlWallets
Updates about development for PirlWallets can be found on the next pages.
{{< imagesurlsheaders "cloud/Pirl_Energy.gif" >}}
---
Author(s):
@dptelecom
Contributor():
---
title: Mining
weight: 4
pre: "<b>3. </b>"
chapter: true
---
{{< imagesurlsheaders "images_headers/Mining.png" >}}
## Mining
Mining is the process of adding transaction records to PIRL public ledger of past transactions ( a „mining rig“ is a collo- quial metaphor for a single computer system that performs the necessary computations for „mining“).
This ledger of past transactions is called the “block-chain” as it is a chain of blocks. The blockchain serves to confirm transactions to the rest of the network as having taken place.
PIRL nodes use the blockchain to distinguish legitimate PIRL transactions from attempts to re-spend coins that have already been spent el- sewhere.
Mining is intentionally designed to be resource-intensive and difficult so that the number of blocks found each day by mi- ners remains steady.
Individual blocks must contain a proof of work to be considered valid. This proof of work is verified by other PIRL nodes each time they receive a block.
PIRL uses the ethash proof-of-work algorithm.
The primary purpose of mining is to set the history of transac- tions in a way that is computationally impractical to modify by any one entity.
By downloading and verifying the blockchain, PIRL nodes are able to reach consensus about the ordering of events in PIRL.
Mining is also the mechanism used to introduce PIRL coins into the system: Miners are paid any transaction fees as well as a „subsidy“ of newly created coins.
This both serves the purpose of disseminating new coins in a decentralized man- ner, as well as, motivating people to provide security for the system.
PIRL mining is so called because it resembles the mining of other commodities: it requires exertion (proof of work POW) and it slowly makes new units available to anybody who wi- shes to take part.
## EZminer
PIRL has a goal to be as user-friendly as possible while provi- ding a state of the art platform for developers.
All aspects of the network are carefully analyzed and under development to reach a simple use for everyone without requiring advan- ced technical knowledge to operate.
For example, in regards to mining, we created the EZminer, so anyone who owns a GPU is able to mine in 3 easy steps that do not require any advanced technical knowledge.
PIRL EZminer is a simple ap- plication that guides you through 3 easy steps to mine PIRL with your AMD or Nvidia GPU. The application takes care of all the necessary modules that need to be installed in the background and setups the miner.
The user simply needs to pick his pool and the address to mine to.
EZminer Features:
• Easy setup of eZminer.
• Windows 64bit / Linux / Mac Os X.
• Direct Link to wallet creation.
• PIRL Wallet recognition in the system Oystr/Nautilus.
• Pool list.
• Manual override of wallet address in case of wallet detec- tion.
• Advanced settings including Intensity and miner output with dashboard in e-miners case.
• On applications UI links for everything related to PIRL and the project.
• Direct linking via the UI to pool site for monitoring the user mining status.
Download and mine Pirl with ezMiner v2.0 [Downloads]({{< ref "/Downloads" >}})
#### [🇧🇪 Pirl Team Pool 🇲🇺](https://pool.pirl.network/)
<iframe width="1309" height="802" src="https://www.youtube.com/embed/PhXsLhLuQE8" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
<iframe width="1309" height="802" src="https://www.youtube.com/embed/N0M1ssDD6QI" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
---
Author(s):
@dptelecom
Contributor(s):
---
title: Technical Documentation
weight: 13
pre: "<b>12. </b>"
chapter: true
---
{{< imagesurlsheaders "images_headers/technicaldoc.png" >}}
#### 1.) [Create-token]({{< ref "/solidity/create-token" >}})
#### 2.) [JSON-RPC-API]({{< ref "/solidity/json-rpc-api" >}})
#### 3.) [Command-line-interface]({{< ref "/solidity/command-line-interface" >}})
#### 4.) [Management-APIs]({{< ref "/solidity/management-api" >}})
#### 5.) [Smart-ContractsI]({{< ref "/solidity/smart-contracts1" >}})
#### 6.) [RPC Subscribtions]({{< ref "/solidity/rpc-sub" >}})
#### 7.) [P2P Protocol]({{< ref "/solidity/p2p-protocol" >}})
#### 8.) [Pirl Node - Installing on Windows]({{< ref "/solidity/install-win" >}})
#### 9.) [Pirl Node - Installing on Mac]({{< ref "/solidity/install-mac" >}})
#### 10.) [Installing from source]({{< ref "/solidity/install-arch" >}})
---
Author(s):
@Fawkes
Contributor(s):
@Dptelecom
This diff is collapsed.
This diff is collapsed.
---
title: Installing from source
weight: 10
pre: "<b>10. </b>"
chapter: true
---
## Installing from source
Download and build pirl node
```shell
git clone https://git.pirl.io/community/pirl
cd pirl
make pirl
```
---
Author(s):
@Fawkes
Contributor(s):
@Dptelecom
\ No newline at end of file