[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance


View post   

File: 262 KB, 1920x1080, F-ahbqca4AAmgQq.jpg [View same] [iqdb] [saucenao] [google]
56992175 No.56992175 [Reply] [Original]

>Normal bridges are naïve, they are built using a lock and mint wrapping smart contract on two chains, where a token is deposited and locked into a smart contract on it's native chain, a message is sent to another smart contract on the external chain saying mint this token, and then the smart contract produces a synthetic replica of the original token, usually called "wrapped" whatever. This is vulnerable to exploits where the smart contracts are fooled into minting and exchanging far more tokens than they should, creating accounting errors and worst case, causing contagious ambiguity to run through the network.

>So CCIP is an interoperability protocol that tries to solve this using oracles as the basis for transferring tokens and messages. The problem is that oracles aren't cryptographically secured by anything, it's a trusted system. Data enters the blackbox, comes out the other side and we trust Chainlink that it's secure.

>Hyperbridge in comparison validates the state of the external chain using Polkadot cores, so it knows natively, exactly how many tokens should be where, within both the external chain and Polkadot itself. Adding more bridges to other chains expands it's view because you're concurrently verifying the states of multiple chains on Polkadot. There aren't any trusted components so the risk of hacking is massively reduced - you can't lie to the bridge to mint more tokens on one side, because it knows exactly how many tokens there should be on both. Previously this hasn't been possible because the throughput of blockchains have been single threaded - meaning computation of the validity of an external chain would have taken up the entire blockspace of whatever other chain was trying to do the work. Now, Polkadot is multithreaded with 50 cores, so it can concurrently process both it's own data and other chains data to provide this service.

>> No.56992179

tl;dr

>> No.56992247

>>56992179
It's over, isn't it?

>> No.56992374
File: 543 KB, 220x187, 5353253.gif [View same] [iqdb] [saucenao] [google]
56992374

>>56992247
>The problem is that oracles aren't cryptographically secured by anything

>> No.56993080

>>56992374
They’re secured by the Link token
Aka token very much needed