Network Security

Search…
Network Security
Wallets
Exchange account (hot)
Social wallet: SWAPI​
Mobile: Fearless​
Good practices to remember
1.
Never share the security details of either accounts or wallets
2.
Never share the security details of either accounts or wallets
3.
Past performance is not necessarily indicative of future results
4.
DYOR
5.
Diversify
6.
Manage Risk & Use backups
Network Security
Proof of Revenue Distribution
​PoRD is a protocol tailored for the needs of Self-Decentralization, and the features of CryptoArena's techical architecture. It is, in essence, an automated accounting & distribution protocol. 
A custom flavor of PoA generating probabilistic finality about how much and when should be distributed in the next period through the computation of collections of timestamped transactions history. The Nodes also continuously corroborate the previous block's expectation with deterministic proof that the amounts distributed were at least equal to the expectation (and may exceed it only), allowing the system to achieve proven finality (irreversible entries in a distributed ledger).
Fork Choice Rule
Longest Chain is best. 
Shared security
Shared security, sometimes referred in documentation as pooled security, is one of the unique value propositions for chains considering to become a parachain and join the Polkadot network. On a high level, shared security means that all parachains that are connected to the Polkadot Relay Chain by leasing a parachain slot will benefit from the economic security provided by the Relay Chain validators.
The notion of shared security is different from interchain protocols that build on an architecture of bridges. For bridge protocols, each chain is considered sovereign and must maintain its own validator set and economic security. One concern in these protocols is on the point of scalability of security. For example, one suggestion to scale blockchains is that of scale by altcoins, which suggests that transaction volumes will filter down to lower market cap altcoins as the bigger ones fill their blocks. A major flaw in this idea is that the lower market cap coins will have less economic security attached, and be easier to attack. A real life example of a 51% attack occurred recently ( Ethereum Classic attack on January 10 ), in which an unknown attacker double spent 219,500 ETC (~1.1M USD). This was followed by two more 51% attacks on ETC.
Polkadot overcomes security scalability concerns since it gravitates all the economic incentives to the Relay Chain and allows the parachains to tap into stronger guarantees at genesis. Sovereign chains must expend much more effort to grow the value of their coin so that it is not easily attackable by well-funded attackers.
Example
Let's compare the standard sovereign security model that exists on current proof-of-work (PoW) chains to that of the shared security of Polkadot. Chains that are secured by their own security model like Bitcoin, Zcash, Ethereum, and their derivatives all must bootstrap their own independent network of miners and maintain a competitive portion of honest hashing power. Since mining is becoming a larger industry that increasingly centralizes on key players, it is becoming more real that a single actor may control enough hash power to attack a chain.
This means that smaller chains that cannot maintain a secure amount of hash power on their networks could potentially be attacked by a large mining cartel at the simple whim of redirecting its hash power away from Bitcoin and toward a new and less secure chain. 51% attacks are viable today with attacks having been reported on Ethereum Classic (see above), Verge, Bitcoin Gold, and other cryptocurrencies.
On Polkadot, this disparity between chain security will not be present. When a parachain connects to Polkadot, the Relay Chain validator set become the securers of that parachain's state transitions. The parachain will only have the overhead of needing to run a few collator nodes to keep the validators informed with the latest state transitions and proofs/witness. Validators will then check these for the parachains to which they are assigned. In this way, new parachains instantly benefit from the overall security of Polkadot even if they have just been launched.
FAQ
Is security correlated to the number of validators? What about the number of parachains?
Security is independent of the number of parachains that are connected to the Polkadot Relay Chain. The correlation of security and the number of validators exists as the higher number of validators will give the network stronger decentralization properties and make it harder to try to take down. However, the biggest indicator of the security of the network is the economic signal of the number of DOT that are bonded and staked. The greater the number of DOT staked by honest validators and nominators, the higher the minimum amount of DOT an attacker would need to acquire a validator slot.
Will parachains ever need their own security? In what scenarios do parachains need their own security?
Most parachains will not need to worry about their own security, since all state transitions will be secured by the Polkadot Relay Chain validator set. However, in some cases (which are considered more experimental), parachains may require their own security. In general, these cases will revolve around lack of data available to Relay Chain validators.
One example is if the state transition function is some succinct or zero-knowledge proof, the parachain would be responsible for keeping its data available as the Relay Chain won't have it. Additionally, for chains with their own consensus, like the one that enables fast payments on Blink Network, there would probably need to be a Byzantine agreement between stakers before a parachain block is valid. The agreement would be necessary because the data associated with the fast consensus would be unknown to Relay Chain validators.
​
Technology - Previous
APIs
Next - Technology
Foundational Concepts
Last modified 6mo ago
Copy link
Contents
Wallets
Good practices to remember
Network Security
Proof of Revenue Distribution
Fork Choice Rule
Shared security
FAQ