文件列表:

.env.example (211, 2023-07-18)
.gas-snapshot (75, 2023-07-18)
.npmignore (132, 2023-07-18)
broadcast/ (0, 2023-07-18)
broadcast/Deploy.s.sol/ (0, 2023-07-18)
broadcast/Deploy.s.sol/5/ (0, 2023-07-18)
broadcast/Deploy.s.sol/5/run-1689557645.json (10121, 2023-07-18)
broadcast/Deploy.s.sol/5/run-1689557660.json (11165, 2023-07-18)
broadcast/Deploy.s.sol/5/run-1689557780.json (11165, 2023-07-18)
broadcast/Deploy.s.sol/5/run-latest.json (11165, 2023-07-18)
foundry.toml (527, 2023-07-18)
git (0, 2023-07-18)
lib/ (0, 2023-07-18)
lib/ds-test/ (0, 2023-07-18)
lib/forge-std/ (0, 2023-07-18)
out/ (0, 2023-07-18)
out/AccessJBLib.sol/ (0, 2023-07-18)
out/AccessJBLib.sol/AccessJBLib.json (30159, 2023-07-18)
out/Address.sol/ (0, 2023-07-18)
out/Address.sol/Address.json (186714, 2023-07-18)
out/Base.sol/ (0, 2023-07-18)
out/Base.sol/CommonBase.json (41663, 2023-07-18)
out/Base.sol/ScriptBase.json (41663, 2023-07-18)
out/Base.sol/TestBase.json (41659, 2023-07-18)
out/Checkpoints.sol/ (0, 2023-07-18)
out/Checkpoints.sol/Checkpoints.json (922081, 2023-07-18)
out/Clones.sol/ (0, 2023-07-18)
out/Clones.sol/Clones.json (81770, 2023-07-18)
out/Context.sol/ (0, 2023-07-18)
out/Context.sol/Context.json (11907, 2023-07-18)
out/Counters.sol/ (0, 2023-07-18)
... ...

This delegate allows the project owner to give varying token bonuses based on someone's ETH contribution size via 3 adjustable tiers. Special Thanks to simplemachines92 (https://github.com/simplemachine92) for letting us use some of his test to help bootstrap our own delegate testing The original Readme file can be found below ////////////////////////////////////////////////////////////////////////// # juice-delegate-template Template used to code juicy solidity Delegate stuff - includes forge, libs, etc. This template is a good starting point for building solidity Delegate extensions to the Juicebox Protocol. Delegates define pockets of code that get called when a project receives payments and when token holders attempt to reclaim funds from a project. Forking this template may help you to avoid submodule related dependency issues down the road. Do not push straight on main, rather create a new branch and open a PR - your reviewer will love you for this. This repo includes an example delegate as well as utilites for deploying or reconfiguring a project that uses the delegate. # Getting started ## Prerequisites ### Install & Update Foundry Install Forge with `curl -L https://foundry.paradigm.xyz | bash`. If you already have Foundry installed, run `foundryup` to update to the latest version. More detailed instructions can be found in the [Foundry Book](https://book.getfoundry.sh/getting-started/installation). ### Install & Update Yarn Follow the instructions in the [Yarn Docs](https://classic.yarnpkg.com/en/docs/install). People tend to use the latest version of Yarn 1 (not Yarn 2+). ## Install Included Dependencies Install dependencies (forge tests, Juice-contracts-V3, OZ) via `yarn install` (the `preinstall` script will run `forge install` for you) # Adding dependencies ## With Yarn If the dependency you would like to install has an NPM package, use `yarn add [package]` where [package] is the package name. This will install the dependency to `node_modules`. Tell forge to look for node libraries by adding `node_modules` to the `foundry.toml` by updating `libs` like so: `libs = ['lib', 'node_modules']`. Add dependencies to `remappings.txt` by running `forge remappings >> remappings.txt`. For example, the NPM package `jbx-protocol` is remapped as `@jbx-protocol/=node_modules/@jbx-protocol/`. ## With Forge If the dependency you would like to install does not have an up-to-date NPM package, use `forge install [dependency]` where [dependency] is the path to the dependency repo. This will install the dependency to `/lib`. Forge manages dependencies using git submodules. Run `forge remappings > remappings.txt` to write the dependencies to `remappings.txt`. Note that this will overwrite that file. If nested dependencies are not installing, try this workaround `git submodule update --init --recursive --force`. Nested dependencies are dependencies of the dependencies you have installed. More information on remappings is available in the Forge Book. # Updating dependencies ## With Yarn Run `yarn upgrade [package]`. ## With Forge Run `foundryup` to update forge. Run `forge update` to update all dependencies, or run `forge update [dependency]` to update a specific dependency. # Usage use `yarn test` to run tests use `yarn test:fork` to run tests in CI mode (including slower mainnet fork tests) use `yarn size` to check contract size use `yarn doc` to generate natspec docs use `yarn lint` to lint the code use `yarn tree` to generate a Solidity dependency tree use `yarn deploy:mainnet` and `yarn deploy:goerli` to deploy and verify (see .env.example for required env vars, using a ledger by default). ## Code coverage Run `yarn coverage`to display code coverage summary and generate an LCOV report To display code coverage in VSCode: - You need to install the [coverage gutters extension (Ryan Luker)](https://marketplace.visualstudio.com/items?itemName=ryanluker.vscode-coverage-gutters) or any other extension handling LCOV reports - ctrl shift p > "Coverage Gutters: Display Coverage" (coverage are the colored markdown lines in the left gutter, after the line numbers) ## PR Github CI flow will run both unit and forked tests, log the contracts size (with the tests) and check linting compliance.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：