search

sablier-labs / v2-core

⏳ Core smart contracts of the Sablier V2 token distribution protocol
https://sablier.com
Other
307 stars 43 forks source link

Standard naming for custom chain branches #1023

Closed PaulRBerg closed 1 month ago

PaulRBerg commented 1 month ago

As we perform deployments to more and more EVM chains, it's becoming clear to me that we will need to maintain parallel branches, e.g. for zkSync (due to zkEVM) and IoTeX (due to them not supporting Solidity v0.8.26).

We should name the branches in a standardized way so that we can see the chains at a glance.

smol-ninja commented 1 month ago

How about just call it chain/blast instead of chain/blast-l2? Its official name is Blast.

smol-ninja commented 1 month ago

Resolved in:

  1. https://github.com/sablier-labs/v2-core/tree/chain/zkSync
  2. https://github.com/sablier-labs/v2-core/tree/chain/blast
  3. https://github.com/sablier-labs/v2-periphery/tree/chain/blast
  4. https://github.com/sablier-labs/v2-periphery/tree/chain/zkSync
  5. https://github.com/sablier-labs/v2-deployments/tree/chain/blast
  6. https://github.com/sablier-labs/docs/commit/bcd0e43a138a55d22b7e377d7ff974d2c1b4af61