Skip to content

Commit 3d57deb

Browse files
Update agglayer.md
1 parent d6786bc commit 3d57deb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/learn/agglayer.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
!!! info
44

5-
This post is a direct reproduction of [**the original blog post**](https://hackmd.io/@QOKsDTFRSd-1oYqrNQ3fIA/Hkx9X3jah) made by Brendan Farmer, Co-founder @ Polygon
5+
This post is a direct reproduction of [**the original blog post**](https://hackmd.io/@QOKsDTFRSd-1oYqrNQ3fIA/Hkx9X3jah) authored by Brendan Farmer, Co-founder @ Polygon
66

77
Polygon 2.0 envisions a protocol layer that seamlessly connects any ZK-enabled Layer-2 (L2) or Layer-1 (L1) chain. This layer of interoperability is referred to as the **aggregation layer**, or **AggLayer**.
88

@@ -16,7 +16,7 @@ In this post, we'll be looking at:
1616

1717
At this point, interoperability protocols rely heavily on bridging to connect what are essentially isolated networks. This translates to fragmented liquidity, and makes for a less than ideal user experience.
1818

19-
Polygon 2.0's AggLayer proposes a solution to that problem by acting as the service layer that aggregates ZK proofs generated by different chains, and co-ordinates cross-chain transactions. We're working with the assumption that ***atomic cross-chain transaction execution is necessary for cross-chain asset exchange***.
19+
Polygon 2.0's AggLayer proposes a solution to that problem by acting as the service layer that aggregates ZK proofs generated by different chains, and co-ordinates cross-chain transactions. The AggLayer is not an L2, It is an independent protocol. We're working with the assumption that ***atomic cross-chain transaction execution is necessary for cross-chain asset exchange***.
2020

2121
!!! tip
2222

0 commit comments

Comments
 (0)