You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+137-1Lines changed: 137 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,6 +159,7 @@ For user needs there are the following contracts:
159
159
* NonceHolder
160
160
* ERC20Contract & ERC20FunctionEncoder
161
161
* ContractDeployer
162
+
* PaymasterFlowEncoder
162
163
163
164
164
165
#### NonceHolder
@@ -234,7 +235,26 @@ Methods:
234
235
| compute_l2_create_address | Address, Nonce | Address | Accepts address of deployer and current deploing nonce and returns address of contract that is going to be deployed by `encode_create` method |
235
236
| compute_l2_create2_address | Address, bytecode, ctor bytecode, salt | Address | Accepts address of deployer, binary representation of contract, if needed it's constructor in binary format and salf. By default constructor can be b'0' value. Returns address of contract that is going to be deployed by `encode_create2` method |
236
237
238
+
#### PaymasterFlowEncoder
237
239
240
+
PaymasterFlowEncoder is utility contract for encoding Paymaster parameters.<br>
241
+
Construction contract needs only Web3 Module object. It can be Eth or ZkSync.<br>
242
+
243
+
Example:
244
+
```python
245
+
from zksync2.manage_contracts.paymaster_utils import PaymasterFlowEncoder
246
+
from zksync2.module.module_builder import ZkSyncBuilder
0 commit comments