Near intents blogpost#3063
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
|
||
| These pieces are not independent products glued together, they form a stack where each layer builds on the one below: | ||
|
|
||
| 1. **MPC Network** (the backbone of [Chain Signatures](/chain-abstraction/chain-signatures)) — a set of participants that collectively derive addresses and sign transactions for other chains, without any single party ever holding the full private key. This is what lets NEAR control accounts on `Ethereum`, `Solana`, and other chains. |
There was a problem hiding this comment.
this line is identical to "Chain Signatures" section below, probably we need to re-think where to put this section - or it can be a single paragraph that only explain relationships between MPC network, bridge and smart contract
| These pieces are not independent products glued together, they form a stack where each layer builds on the one below: | ||
|
|
||
| 1. **MPC Network** (the backbone of [Chain Signatures](/chain-abstraction/chain-signatures)) — a set of participants that collectively derive addresses and sign transactions for other chains, without any single party ever holding the full private key. This is what lets NEAR control accounts on `Ethereum`, `Solana`, and other chains. | ||
| 2. **PoA Bridge** — uses the MPC Network to control deposit addresses and treasuries on each chain. When you deposit, it mints a bridged representation on NEAR, when you withdraw, it asks the MPC Network to sign the real transfer out. It is the layer that actually moves assets in and out of NEAR. |
There was a problem hiding this comment.
I'd like to see more details in here, since it's dedicated to explaining how MPC and bridge work together
the deposit flow is PoA Bridge owns many addresses on the source chain, so when you send tokens to one of them, it picks up the transfer and does two things: mints the equivalent amount of tokens for your account on NEAR and sends the received amount to their treasury account on the source chain
the withdraw flow is similar process, just in reverse
|
|
||
| 1. **MPC Network** (the backbone of [Chain Signatures](/chain-abstraction/chain-signatures)) — a set of participants that collectively derive addresses and sign transactions for other chains, without any single party ever holding the full private key. This is what lets NEAR control accounts on `Ethereum`, `Solana`, and other chains. | ||
| 2. **PoA Bridge** — uses the MPC Network to control deposit addresses and treasuries on each chain. When you deposit, it mints a bridged representation on NEAR, when you withdraw, it asks the MPC Network to sign the real transfer out. It is the layer that actually moves assets in and out of NEAR. | ||
| 3. **NEAR Intents** — sits on top of the bridge. It finds a counterparty and executes the swap atomically inside `intents.near`, relying on the bridge (and therefore the MPC Network) for everything that crosses a chain boundary. |
There was a problem hiding this comment.
I think it's worth clarifying that NEAR Intents is just a smart contract that validates and executes atomic swaps inside NEAR, it doesn't really know anything about bridges/MPCs, it only works with assets
2 participants
Close #2889