-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add missing singleton deployments #226
Conversation
Uxio0
commented
Sep 8, 2023
•
edited
Loading
edited
- Closes New network request - LightLink #205
- Closes New network request - Hedera #206
- Closes Add Japan Open Chain Mainnet #208
- Closes Add Manta Pacific Testnet #212
- Closes Add Japan Open Chain Testnet #213
- Closes New network request - Beam testnet #214
- Closes New Network: Base Mainnet #216
- Closes Support Orderly L2 based OP Stack #218
- Closes New network: U2U Solaris Mainnet #219
- Closes New network: Unicorn Ultra Nebulas Testnet #220
- Closes New network request: Arbitrum Nova #221
- Closes New network request: Arbitrum Sepolia #222
- Closes New network request: Canxium Mainnet #223
- Closes New network request: Canxium Testnet #224
- Closes Request support for Arthera Testnet #232
7f96330
to
2a5601c
Compare
43d6503
to
ee2a56f
Compare
|
7c4967b
to
e7c1d12
Compare
Thanks for adding Scroll Sepolia artifact here! Would it be possible to merge and publish a new npm package in the next week? We're hoping to get Safe Core contracts deployed to promote in the next ETHGlobal hackathon on Oct 6th 🤞 |
I will mentor an hackathon in Madrid from October 7th to 8th so if we could get the updated npm package released to be able to deploy the contracts from this singleton it would help to get hackers try it. |
e7c1d12
to
1c7cdbf
Compare
Hi @bertux , I think the package that you need deployed is https://github.com/safe-global/safe-deployments and not this one |
@mmv08 @akshay-ap I would like to merge this |
5b6be17
to
8e16c00
Compare
8e16c00
to
01f1b1c
Compare
Hello, I found later the problem was the naming of the package because it was still using the old naming with old versions and not the new one with the new versions. After updating the naming it found the new version without problem. |