You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The EEA Community Project’s L2 WG has drafted a proposal for a standard for a Token List for L1s, L2s, and Sidechains to address the current ecosystem problem of defining and listing of tokens on any Layer 1 (L1), Layer 2 (L2), and Sidechain systems because there needs to be a consensus on the “canonical” token on chain B that corresponds to some token on chain A. When one wants to bridge token X from chain A to chain B, one must create some new representation of the token on chain B. It is worth noting that this problem is not limited to L2s – every chain connected via bridges must deal with the same issue.
The L2 WG is soliciting input from the wider Ethereum ecosystem interested to contribute to this proposal and ensure that when the standard is released, it will be widely adopted.
We thought it would be great to cross-post here to get your feedback and invite you to participate in the WG meetings. The next meeting is on 8/24.
@moodysalem @haydenadams
The EEA Community Project’s L2 WG has drafted a proposal for a standard for a Token List for L1s, L2s, and Sidechains to address the current ecosystem problem of defining and listing of tokens on any Layer 1 (L1), Layer 2 (L2), and Sidechain systems because there needs to be a consensus on the “canonical” token on chain B that corresponds to some token on chain A. When one wants to bridge token X from chain A to chain B, one must create some new representation of the token on chain B. It is worth noting that this problem is not limited to L2s – every chain connected via bridges must deal with the same issue.
The L2 WG is soliciting input from the wider Ethereum ecosystem interested to contribute to this proposal and ensure that when the standard is released, it will be widely adopted.
We thought it would be great to cross-post here to get your feedback and invite you to participate in the WG meetings. The next meeting is on 8/24.
Looking forward to hearing from you,
the L2 WG
cc @Tasd @dshaw
The text was updated successfully, but these errors were encountered: