Skip to content

Commit 7e26fee

Browse files
authored
feat: add EVES-006 Scaling Architecture (#22)
Signed-off-by: jdsika <carlo.van-driesten@vdl.digital>
1 parent 6beab60 commit 7e26fee

File tree

3 files changed

+116
-2
lines changed

3 files changed

+116
-2
lines changed

EVES/SUMMARY.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,3 +11,4 @@
1111
* [EVES-003: ENVITED-X Asset Definition and Upload Process](drafts/EVES-003/eves-003.md)
1212
* [EVES-004: ENVITED-X Roles and Responsibilities of EVES Editors](drafts/EVES-004/eves-004.md)
1313
* [EVES-005: ENVITED-X Contract Negotiation Process](drafts/EVES-005/eves-005.md)
14+
* [EVES-006: ENVITED-X Scaling Architecture](drafts/EVES-006/eves-006.md)

EVES/drafts/EVES-006/eves-006.md

Lines changed: 112 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,112 @@
1+
---
2+
eves-identifier: 006
3+
title: ENVITED-X Scaling Architecture
4+
author: Carlo van Driesten (@jdsika)
5+
discussions-to: https://github.com/ASCS-eV/smart-contracts/blob/main/etherlink-bridge/README.md
6+
status: Draft
7+
type: Process
8+
created: 2025-02-21
9+
requires: ["EVES-001", "EVES-002", "EVES-003"]
10+
replaces: None
11+
---
12+
13+
## Abstract
14+
15+
This specification defines the scaling architecture for the ENVITED-X Data Space.
16+
It outlines the integration of enshrined optimistic rollups with the Etherlink Layer 2 network, leveraging the Tezos ecosystem for scalable, secure, and cost-efficient transactions.
17+
This document details the bridging mechanism between Tezos Layer 1 and Etherlink, describing the role of FA2.1 tickets, smart rollups, and optimistic fraud proofs in ensuring trustless scalability.
18+
19+
## Motivation
20+
21+
As the ENVITED-X Data Space grows, scalability becomes a critical requirement.
22+
The limitations of Tezos Layer 1, particularly transaction throughput and gas fees, necessitate a Layer 2 solution.
23+
Etherlink, an enshrined optimistic rollup, provides the following benefits:
24+
25+
- **Low-Cost Transactions**: Reduced fees (nearly free) compared to Layer 1 Tezos.
26+
- **High Throughput**: Enables parallel execution and improved finality times.
27+
- **Ethereum Compatibility**: Supports EVM tooling, enhancing interoperability.
28+
- **Trustless Bridging**: Tezos tickets and rollup smart contracts ensure asset security without the need for multi-signature contracts.
29+
- **On-Chain Security**: The rollup is secured by Tezos Layer 1, inheriting its consensus guarantees.
30+
31+
## Specification
32+
33+
### 1. Scaling with Etherlink
34+
35+
Etherlink is an enshrined optimistic rollup within the Tezos ecosystem that enables scalable execution of smart contracts. Unlike external rollups, enshrined rollups benefit from direct protocol support, reducing costs and increasing security.
36+
37+
- **Batching Transactions**: Multiple operations are aggregated and submitted as a single transaction to Tezos Layer 1.
38+
- **Fraud Proofs**: Optimistic execution ensures validity unless proven otherwise.
39+
- **EVM Compatibility**: Smart contracts can be deployed using Solidity, facilitating Ethereum ecosystem integration.
40+
41+
### 2. Bridging Mechanism
42+
43+
#### 2.1 FA2 Token Bridge
44+
45+
ENVITED-X assets are tokenized using the FA2.1 standard on Tezos.
46+
The current bridge implementation allows for transfer of FA2 tokens as well which do not offer direct ticket export functionality.
47+
Bridging these tokens to Etherlink involves:
48+
49+
1. **Depositing Tokens**: Users send FA2 (FA2.1) tokens to a bridge contract on Tezos Layer 1.
50+
2. **Minting Tickets**: The bridge contract issues tickets representing the deposited tokens.
51+
3. **Submitting to Rollup**: The tickets are forwarded to Etherlink via the rollup inbox.
52+
4. **Minting on Layer 2**: Equivalent tokens are created on Etherlink and assigned to the user's wallet.
53+
54+
#### 2.2 Withdrawing Tokens
55+
56+
1. **Initiating Withdrawal**: The user submits a withdrawal request on Etherlink.
57+
2. **Optimistic Challenge Period**: The transaction remains open for dispute (fraud-proof verification).
58+
3. **Finalizing on Tezos**: If no fraud is detected, the Tezos contract releases the original tokens.
59+
60+
With the Rio upgrade, the withdrawal process from L2 to L1 will be significantly faster, improving efficiency for asset transitions.
61+
62+
### 3. Integration with ENVITED-X
63+
64+
#### 3.1 Asset Marketplace
65+
66+
- **Asset Registration**: Assets are initially registered on Tezos Layer 1 as FA2.1 tokens.
67+
- **Cross-Layer Trading**: Once bridged, assets can be transferred or traded within the Etherlink ecosystem.
68+
- **Metadata Preservation**: TZIP-21 metadata remains intact across layers.
69+
- **Future Transition**: At a later stage, all L1 tokens can be transitioned to L2 to maximize scalability, allowing existing contracts to function until scaling is necessary.
70+
71+
#### 3.2 Smart Contracts & Indexing
72+
73+
- **Marketplace Contracts**: Implemented on both Tezos and Etherlink.
74+
- **Indexer Support**: Taquito and Etherlink-compatible indexers track asset movements.
75+
- **Credential Validation**: User credentials remain valid across both layers via Verifiable Credentials.
76+
77+
## Future Improvements
78+
79+
### 1. Transition to ERC-721 Tokens
80+
81+
Currently, the bridge implementation for Etherlink Layer 2 uses ERC-20 tokens. Future implementations should adopt ERC-721 token contracts for better asset representation and compatibility with NFT standards. [ERC-721 Standard](https://ethereum.org/en/developers/docs/standards/tokens/erc-721/)
82+
83+
### 2. Improvements with the Tezos Rio Protocol
84+
85+
The upcoming Tezos protocol "Rio" will introduce enhancements in bridging mechanisms and significantly reduce the bridging time from L2 to L1. More details can be found in the [Rio Protocol Announcement](https://research-development.nomadic-labs.com/rio-announcement.html) and [Rio Protocol Changelog](https://octez.tezos.com/docs/protocols/022_rio.html).
86+
87+
### 3. Full Transition to Layer 2
88+
89+
At some point, all L1 tokens should be bridged to L2, allowing the system to fully transition to Layer 2 scaling while maintaining compatibility with existing contracts during the migration phase. The layer 1 contracts will then be read-only to not allow further token minting on layer 1.
90+
91+
### 4. FA2.1 Ticket Export Functionality
92+
93+
The FA2.1 contract contains a ticket export functionality that can be used to directly issue tickets. This can improve efficiency and user experience for cross-layer asset transfers.
94+
95+
## Backwards Compatibility
96+
97+
This specification extends ENVITED-X functionality without modifying existing contracts. All FA2.1 assets remain compatible with Tezos Layer 1, and bridging is optional until a full transition to L2 is enacted.
98+
99+
## References
100+
101+
1. [Etherlink Documentation](https://docs.etherlink.com/)
102+
2. [Tezos FA2.1 Standard](https://gitlab.com/tzip/tzip/-/blob/master/proposals/tzip-21/tzip-21.md)
103+
3. [Optimistic Rollups in Tezos](https://research.tezos.com/optimistic-rollups)
104+
4. [Bridging FA Tokens on Etherlink](https://docs.etherlink.com/bridging/bridging-fa)
105+
5. [ERC-721 Standard](https://ethereum.org/en/developers/docs/standards/tokens/erc-721/)
106+
6. [Rio Protocol Announcement](https://research-development.nomadic-labs.com/rio-announcement.html)
107+
7. [Rio Protocol Changelog](https://octez.tezos.com/docs/protocols/022_rio.html)
108+
109+
## Implementation
110+
111+
The initial bridge implementation follows the setup documented in the [ASCS smart contracts repository](https://github.com/ASCS-eV/smart-contracts/blob/main/etherlink-bridge/README.md).
112+
Future iterations may include direct ticket issuance for improved efficiency, leveraging Rio protocol enhancements for streamlined bridging.

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,8 @@ The process on how to write, submit or change specifications in defined in [EVES
1313
| Number | Title | Type | Status |
1414
| ------ | ----- | ---- | ------ |
1515
| [001](./EVES/drafts/EVES-001/eves-001.md) | ENVITED-X Ecosystem Specification Process | Process | Draft |
16-
| [002](./EVES/drafts/EVES-002/eves-002.md) | ENVITED-X Data Space Architecture Overview | Standards | Draft |
16+
| [002](./EVES/drafts/EVES-002/eves-002.md) | ENVITED-X Data Space Architecture Overview | Standards | Draft |
1717
| [003](./EVES/drafts/EVES-003/eves-003.md) | ENVITED-X Asset Definition and Upload Process | Standards | Draft |
1818
| [004](./EVES/drafts/EVES-004/eves-004.md) | ENVITED-X Roles and Responsibilities of EVES Editors | Process | Draft |
19-
| [005](./EVES/drafts/EVES-005/eves-005.md) | ENVITED-X Contract Negotiation Process | Process | Draft |
19+
| [005](./EVES/drafts/EVES-005/eves-005.md) | ENVITED-X Contract Negotiation Process | Process | Draft |
20+
| [006](./EVES/drafts/EVES-006/eves-006.md) | ENVITED-X Scaling Architecture | Process | Draft |

0 commit comments

Comments
 (0)