
Security News
Risky Biz Podcast: Making Reachability Analysis Work in Real-World Codebases
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.
@pier-wallet/contracts
Advanced tools
.env.sample
to .env
and fill in all the required variables. You will get an error if you don't specify all required env variables.yarn
to install dependenciesyarn dev:build
to setup the project.Starts a fork of harmony mainnet on http://localhost:8545 and deploys all contracts. The addresses of smart contracts should not change, unless the deploy scripts are changed.
yarn dev:serve
yarn test:unit
If in doubt - run yarn dev:typechain
Deploy: Available networks:
localhost
harmonytestnet
polygontestnet
bsctestnet
fantomtestnet
harmonymainnet
polygonmainnet
bscmainnet
fantommainnet
yarn deploy:wallet-factory --network [network] --gasprice [gas price in wei]
yarn deploy:v3 --network [network] --gasprice [gas price in wei]
yarn deploy:periphery --network [network] --gasprice [gas price in wei]
yarn deploy:products --network [network] --gasprice [gas price in wei]
Build NPM Package
for testnet: preid= alpha
npm version patch/minor/major [prerelease --preid=...]
To verify on explorer
yarn hardhat verify --network harmonymainnet [contract address]
Close PR!
contract SmartWallet[NEW_VERSION] is SmartWallet[PREVIOUS_VERSION] {...}
IF
In any case
function version() external pure override returns (uint256) {
return [NEW_VERSION]
}
deploy:v[NEW_VERSION]: ".... --tags v[NEW_VERSION]"
const SMART_WALLET_CONTRACTS_MAP = [
...PREVIOUS_VERSIONS,
{
name: SmartWallet[NEW_VERSION],
version: [NEW_VERSION],
},
] as const;
do this on etherscan / polygonscan / etc
Calculate percentages, then on ..scan, add. Example:
[
["0x1BFD67037B42Cf73acF2047067bd4F2C47D9BfD6", 500000000000],
["0x7ceB23fD6bC0adD59E62ac25578270cFf1b9f619", 200000000000],
["0x7DfF46370e9eA5f0Bad3C4E29711aD50062EA7A4", 100000000000],
["0xeCDCB5B88F8e3C15f95c720C51c71c9E2080525d", 150000000000],
["0xB85517b87BF64942adf3A0B9E4c71E4Bc5Caa4e5", 50000000000]
]
OR
[
{
"token": "0x1BFD67037B42Cf73acF2047067bd4F2C47D9BfD6",
"percentage": 500000000000
},
{
"token": "0x7ceB23fD6bC0adD59E62ac25578270cFf1b9f619",
"percentage": 200000000000
},
{
"token": "0x7DfF46370e9eA5f0Bad3C4E29711aD50062EA7A4",
"percentage": 100000000000
},
{
"token": "0xeCDCB5B88F8e3C15f95c720C51c71c9E2080525d",
"percentage": 150000000000
},
{
"token": "0xB85517b87BF64942adf3A0B9E4c71E4Bc5Caa4e5",
"percentage": 50000000000
}
]
To set the Management fee (e.g. 2% per annum):
Calculate hourly management Fee using wolfram alpha
(1-x)^(24*365) = (1-0.02)
Where 0.02 is the annual mgmt fee and x is the hourly mgmt fee
https://www.wolframalpha.com/input?i=%281-x%29%5E%2824*365%29+%3D+%281-0.02%29
Evaluate expression (e.g. 2% per year --> 2.30624246818947 10^-6)
2.30624246818947*10^-6 => 0.000002306242468
Set the management fee
yarn hardhat --network polygontestnet product:set-product-reference-data-fees --product-name SimpleIndexProduct --management-fee-per-hour 0.000002306242468 --gasprice 5000000000
FAQs
pier wallet smart wallet and integration contracts
The npm package @pier-wallet/contracts receives a total of 0 weekly downloads. As such, @pier-wallet/contracts popularity was classified as not popular.
We found that @pier-wallet/contracts demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 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
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.
Security News
/Research
Malicious Nx npm versions stole secrets and wallet info using AI CLI tools; Socket’s AI scanner detected the supply chain attack and flagged the malware.
Security News
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.