@perp/curie-deployments
Advanced tools
Perpetual Protocol Curie (v2) contract artifacts (ABIs) and deployed addresses
@perp/curie-deployments contains the contract artifacts and metadata (deployed addresses) of all contracts in Perpetual Protocol Curie (v2).
The folder structure of this package:
node_modules/@perp/curie-deployments/
├── optimism/
│ ├── core/
│ │ ├── artifacts/
│ │ │ └── contracts/
│ │ ├── dependencies.json
│ │ └── metadata.json
│ ├── periphery/
│ │ ├── artifacts/
│ │ │ └── contracts/
│ │ ├── dependencies.json
│ │ └── metadata.json
│ └── liquidity-mining
│ ├── artifacts/
│ │ └── contracts/
│ ├── dependencies.json
│ └── metadata.json
├── optimism-goerli
└── ...
You could find the deployed contract addresses inside metadata.json under each network.
If possible, it's recommended to publish a new npm version first and use that version to deploy contracts.
When using git+ssh://git@github.com:perpetual-protocol/perp-xxx.git#GIT_COMMIT_SHA to deploy contracts, every time we deploy, we must increase the version of package.json in perp-xxx to avoid version conflicts of yarn install. For instance, change to 2.0.0-rc1, 2.0.0-rc2 and so on. Otherwise, yarn might not install the correct version.
Please use yarn --network-concurrency 1 to install packages.
You may encounter problem such as ENOENT: no such file or directory... if using yarn directly.
FAQs
Perpetual Protocol Curie (v2) contract artifacts (ABIs) and deployed addresses
The npm package @perp/curie-deployments receives a total of 167 weekly downloads. As such, @perp/curie-deployments popularity was classified as not popular.
We found that @perp/curie-deployments demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 7 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Rust’s crates.io team is advancing an RFC to add a Security tab that surfaces RustSec vulnerability and unsoundness advisories directly on crate pages.
Security News
/Research
Socket found a Rust typosquat (finch-rust) that loads sha-rust to steal credentials, using impersonation and an unpinned dependency to auto-deliver updates.
Research
/Security Fundamentals
A pair of typosquatted Go packages posing as Google’s UUID library quietly turn helper functions into encrypted exfiltration channels to a paste site, putting developer and CI data at risk.