Splitter contract
Splitter Contracts
Constructor
constructor(address[] memory _payees, uint256[] memory _shares)
PaymentSplitter(_payees, _shares)
{}
| Index | Name | Description |
|---|---|---|
| 0 | _payees | List of Payees |
| 1 | _shares | List of shares for each Payee |
Functions
Legend
| Field | Meaning |
|---|---|
| 🛠 | Function can modify state |
| 💵 | Function is payable |
| Public | public functions can be called internally from within the contract or externally via messages |
| External | External functions are part of the contract interface, which means they can be called from other contracts and via transactions. An external function f cannot be called internally (i.e. f() does not work, but this.f() works) |
Description
| Function Name | Visibility | Mutability | Description |
|---|---|---|---|
| totalPayees | Public | - | Returns the total number of payees |
| isPayee | Public | - | Returns true if a supplied address is a payee |
| addPayee | Public | 🛠 | Adds a single address with a share to the payee list |
| addPayees | Public | 🛠 | Adds a list of addresses, each with a share, to the payee list |
| releaseAll | Public | 🛠 | Releases all ETH in the contract to the payees |
| releaseAll | Public | 🛠 | Releases all ERC-20 tokens in the contract to the payees |
Architecture
Want to see an example of how the math works out for a Splitter contract? See the Distributing Proceeds Example
Feedback
Something not quite right, unclear or can't find what you are looking for? Please let us know at support.moonpay.com and we will get back to you as soon as we can.
Updated 8 months ago