Update README.md

This commit is contained in:
dr. mia von steinkirch, phd 2023-02-07 16:22:03 -08:00 committed by GitHub
parent c8181198cc
commit 2449c860e0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -1,9 +1,11 @@
## Bridges
## bridges
<br>
### Centralized Bridge
### centralized
<br>
* Centralized bridges are essentially hot wallets straddling the fence between multiple chains.
* They hold a users assets on one chain and issue them a corresponding amount of tokens on another chain.
@ -12,8 +14,11 @@
* The security risks of a centralized bridge are the same security risks that exist for exchanges and custodians.
* Their primary responsibility is securing private keys (key management), and as a result centralized bridges have proven to be pretty secure.
<br>
### Proof of Stake Bridge
### proof-of-stake bridge
<br>
* Proof of Stake bridges are like little blockchain networks narrowly focused on facilitating cross-chain activity.
* Whereas centralized bridges are managed by a single entity, proof of stake bridges are managed by a group.
@ -21,8 +26,11 @@
* Because POS bridges involve both smart contracts and a group of centralized gatekeepers, they inherit all the code risk of Web 3 and the traditional security risks of Web 2 (key management, access controls).
* POS bridges have the most attack vectors, and have unfortunately been the victims of most of the major exploits.
<br>
### Decentralized Bridge
### decentralized bridge
<br>
* Decentralized bridges take a proof of deposit from one chain and validate it on the other chain (ex: Polygon Plasma Bridge).
* Decentralized bridges are all code. They dont rely on centralized signers/validators, so while theres more code risk, they dont have to worry about the traditional security risks that POS bridges deal with.