bishi, mianshi sol-mass-payouts – sol大规模支付区块链毕设代写
区块链毕设代写本文提供国外最新区块链项目源码下载，包括solidity,eth,fabric等blockchain区块链,sol-mass-payouts – sol大规模支付区块链毕设代写 是一篇很好的国外资料
sol-mass-payouts
Utilities enabling the mass distribution of assets, with a single funding transaction.
Summary example
A funder, such as a yield farming distribution, wishes to distribute 1,000,000 XYZ tokens to 50,000 addresses.
Off-chain, the funder builds a merkle tree of (address,amount) pairs for XYZ payouts.
The funder sends 1,000,000 XYZ tokens, and the Merkle root hash, to this MerkleBox contract for secure storage.
Then, at any time, users may claim their XYZ tokens by providing a Merkle proof of their (address,amount).
The end result is aggregating all the payouts into a single blockchain transaction from the funder. (Users must still individually issue claim transactions)
Public operations (APIs)
Anyone: Validate claim
Validate a supplied merkle receipt is associated with a valid, unspent claim.
User: Claim tokens
Present a valid merkle receipt, and receive the associated tokens.
User must be the address in the claim, and the claim must be unspent.
Funder: Create new claims group
Store a merkle root, and associated ERC20 funds, on chain.
WARNING: There is no on-chain validation that funds supplied equal the funds required to fully satisfy all claims. The funder may under-fund.
Anyone: Add more funds to claims group.
Supply additional quantity of asset to the claims group.
Usually the funder calls this operation, but that is not a requirement. Once a claims group is created, anyone may supply additional funds.
Funder: Withdraw funds from claims group.
The funder (owner) may withdraw funds from the claims group, if-and-only-if the Withdraw Lock is not locked.
Anyone: On-chain ERC20 mass-send
A separate MultiTransfer contract is provided, which provides the simple utility of
- Receive N amount of an ERC20 token
- Send tokens to a list of (address,amount) pairs.
This contract and function is not tied in any way to the above merkle-related operations, and is provided as an alternate mass-pay operation for ERC20 tokens.
Security notes
Under-funding
It appears prohibitively expensive to validate that a holding is fully funded. (Solutions welcome)
As a consequence, it is possible to under-fund a claims group.
Withdraw locking
The withdraw lock feature permits disabling of withdrawals until a specified time.
To disable this feature, simply set the lock time to zero, or some time in the past. To permanently lock the funds, set the lock time to a maximum, or an arbitrary time millions of years in the future.
Setup.
- Install packages
npm i -g truffle npm i - Update provider url in config/default.json
- Set DEPLOYMENT_ACCOUNT_KEY in env
create a .env file in root DEPLOYMENT_ACCOUNT_KEY = "my mnemonic phrase" - Deploy you own contracts if want to do arb-
truffle migrate --reset --network mainnet/ropsten
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products. Learn more.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
You can always update your selection by clicking Cookie Preferences at the bottom of the page. For more information, see our Privacy Statement.
Essential cookies
We use essential cookies to perform essential website functions, e.g. they’re used to log you in. Learn more
Always active
Analytics cookies
We use analytics cookies to understand how you use our websites so we can make them better, e.g. they’re used to gather information about the pages you visit and how many clicks you need to accomplish a task. Learn more
Merge pull request
sol-mass-payouts
Utilities enabling the mass distribution of assets, with a single funding transaction.
Summary example
A funder, such as a yield farming distribution, wishes to distribute 1,000,000 XYZ tokens to 50,000 addresses.
Off-chain, the funder builds a merkle tree of (address,amount) pairs for XYZ payouts.
The funder sends 1,000,000 XYZ tokens, and the Merkle root hash, to this MerkleBox contract for secure storage.
Then, at any time, users may claim their XYZ tokens by providing a Merkle proof of their (address,amount).
The end result is aggregating all the payouts into a single blockchain transaction from the funder. (Users must still individually issue claim transactions)
Public operations (APIs)
Anyone: Validate claim
Validate a supplied merkle receipt is associated with a valid, unspent claim.
User: Claim tokens
Present a valid merkle receipt, and receive the associated tokens.
User must be the address in the claim, and the claim must be unspent.
Funder: Create new claims group
Store a merkle root, and associated ERC20 funds, on chain.
WARNING: There is no on-chain validation that funds supplied equal the funds required to fully satisfy all claims. The funder may under-fund.
Anyone: Add more funds to claims group.
Supply additional quantity of asset to the claims group.
Usually the funder calls this operation, but that is not a requirement. Once a claims group is created, anyone may supply additional funds.
Funder: Withdraw funds from claims group.
The funder (owner) may withdraw funds from the claims group, if-and-only-if the Withdraw Lock is not locked.
Anyone: On-chain ERC20 mass-send
A separate MultiTransfer contract is provided, which provides the simple utility of
- Receive N amount of an ERC20 token
- Send tokens to a list of (address,amount) pairs.
This contract and function is not tied in any way to the above merkle-related operations, and is provided as an alternate mass-pay operation for ERC20 tokens.
Security notes
Under-funding
It appears prohibitively expensive to validate that a holding is fully funded. (Solutions welcome)
As a consequence, it is possible to under-fund a claims group.
Withdraw locking
The withdraw lock feature permits disabling of withdrawals until a specified time.
To disable this feature, simply set the lock time to zero, or some time in the past. To permanently lock the funds, set the lock time to a maximum, or an arbitrary time millions of years in the future.
Setup.
- Install packages
npm i -g truffle npm i - Update provider url in config/default.json
- Set DEPLOYMENT_ACCOUNT_KEY in env
create a .env file in root DEPLOYMENT_ACCOUNT_KEY = "my mnemonic phrase" - Deploy you own contracts if want to do arb-
truffle migrate --reset --network mainnet/ropsten
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products. Learn more.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
You can always update your selection by clicking Cookie Preferences at the bottom of the page. For more information, see our Privacy Statement.
Essential cookies
We use essential cookies to perform essential website functions, e.g. they’re used to log you in. Learn more
Always active
Analytics cookies
We use analytics cookies to understand how you use our websites so we can make them better, e.g. they’re used to gather information about the pages you visit and how many clicks you need to accomplish a task. Learn more
Merge pull request
部分转自网络，侵权联系删除区块链源码网
区块链知识分享网, 以太坊dapp资源网, 区块链教程, fabric教程下载, 区块链书籍下载, 区块链资料下载, 区块链视频教程下载, 区块链基础教程, 区块链入门教程, 区块链资源 » sol-mass-payouts – sol大规模支付区块链毕设代写
