Chain abstraction overview update #2420
Conversation
render
bot
temporarily deployed
to
2379-doc-improve-chain-abstraction-overview - near-docs PR #2420
render
bot
temporarily deployed
to
2379-doc-improve-chain-abstraction-overview - near-docs PR #2420
| :::tip | ||
| In NEAR the relayers simply attach NEAR to cover gas fees, and pass the transaction to the network. There, the transaction is executed as if the **user had sent it**. | ||
| ::: | ||
| NEAR's ecosystem vision is to facilitate interactions across all blockchain networks and the larger internet. This transformative approach aims at enhancing the user experience and developer capabilities through advanced technologies, specifically in the realm of decentralized finance (DeFi) and artificial intelligence (AI). |
There was a problem hiding this comment.
This sounds like another intro, maybe we don't need it, or we need to merge it above
|
|
||
| <hr subclass="subsection" /> | ||
| Central to this vision is the concept of **chain abstraction**, which is designed to provide seamless access to a wider range of crypto assets, smart contracts, and blockchain states. This is achieved through a trio of key technologies: the intent layer, [chain signatures](chain-signatures/chain-signatures.md), and the [omnibridge](#). |
There was a problem hiding this comment.
This also reads like introduction, and more importantly, here we say that chain abstraction is:
- intent layer
- chain signatures
- omni bridge
But above we say that chain abstraction is:
- email login
- relayers (covering gas)
- chain signatures
So we need to either remove it, or change what is above, or merge it
There was a problem hiding this comment.
Agree with this comment and the one above. I suggested a new introduction above and think we should better summarize this section as to what the core components of Chain Abstraction are and how they work together at a high level. Then, proceed with separate sections that continue to break down the CA stack.
|
|
||
| :::warning | ||
| FastAuth is being deprecated, stay tuned for updates | ||
| ### Bitcoin Use Cases |
There was a problem hiding this comment.
I wonder if we have links for all of these use-cases, I'm afraid right now it sounds super "marketing", and not oriented to helping devs learn something
Otherwise maybe we make a blog post?
There was a problem hiding this comment.
Interesting, Proximity has actually made a blogpost that I think talks about all of this https://medium.com/@ProximityFi/building-bitcoin-native-dapps-with-nears-abstraction-stack-fb4aeb448eee
There was a problem hiding this comment.
Good call, @bucanero I think you can draw some inspiration from this BP on better summarizing the CA stack here.
|
|
||
| <hr subclass="subsection" /> | ||
| Central to this vision is the concept of **chain abstraction**, which is designed to provide seamless access to a wider range of crypto assets, smart contracts, and blockchain states. This is achieved through a trio of key technologies: the intent layer, [chain signatures](chain-signatures/chain-signatures.md), and the [omnibridge](#). |
There was a problem hiding this comment.
Agree with this comment and the one above. I suggested a new introduction above and think we should better summarize this section as to what the core components of Chain Abstraction are and how they work together at a high level. Then, proceed with separate sections that continue to break down the CA stack.
|
|
||
| :::warning | ||
| FastAuth is being deprecated, stay tuned for updates | ||
| ### Bitcoin Use Cases |
There was a problem hiding this comment.
Good call, @bucanero I think you can draw some inspiration from this BP on better summarizing the CA stack here.
Co-authored-by: Josh Ford <[email protected]>
fixes #2379