-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathHow to Decrease Client DataCap Allocation
129 lines (85 loc) · 5.15 KB
/
How to Decrease Client DataCap Allocation
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
## Instructions
### 1. Download Lotus Binary
1. Open the [Lotus v1.31.0 Release](https://github.com/filecoin-project/lotus/releases/tag/v1.31.0) page in your web browser.
2. Scroll down to the **Assets** section and download the appropriate Lotus binary for your operating system.
### 2. Extract the Archive
1. Once the download is complete, extract the contents of the archive to a desired location.
### 3. Navigate to the Lotus Directory
1. Open a terminal or command prompt.
2. Navigate to the folder where the extracted Lotus binary is located.
### 4. Start the Lotus Daemon
Run the following command in the terminal:
```sh
env FULLNODE_API_INFO=wss://wss.node.glif.io/apigw/lotus ./lotus daemon --lite
```
### 5. Modify the Configuration File
1. Open the `~/.lotus/config.toml` file.
2. In the `[Wallet]` section, remove the `#` symbol from the `EnableLedger` line and set it to `true`:
```toml
[Wallet]
# type: string
# env var: LOTUS_WALLET_REMOTEBACKEND
# RemoteBackend = ""
# type: bool
# env var: LOTUS_WALLET_ENABLELEDGER
EnableLedger = true
# type: bool
# env var: LOTUS_WALLET_DISABLELOCAL
# DisableLocal = false
```
### 6. Restart the Lotus Daemon
1. Stop the Lotus daemon by pressing `Ctrl+C` in the terminal.
2. Run the Lotus daemon again.
### 7. Open a New Terminal Window
1. Navigate to the folder where the extracted Lotus binary is located.
2. Keep the first terminal running the Lotus daemon, and use the second terminal to enter commands.
### 8. Prepare Your Ledger Device
1. Unlock your Ledger device.
2. Open the Filecoin app on the Ledger and ensure it remains connected to your computer.
### 9. Create a Ledger-Backed Wallet
Use the following command to create a new Ledger-backed wallet (`secp256k1-ledger`):
```sh
./lotus wallet new secp256k1-ledger
```
On your Ledger device, confirm the creation of the wallet.
Keep running the command until you see the ledger wallet addresses that you use to sign the multisig transaction.
Copy the response from the command as it will be needed later to create the Lotus multisig propose.
### 10. Prepare calldata
1. Visit [abi.hashex.org](https://abi.hashex.org).
2. Manually enter your parameters as required:
- For **Function**, select **your function** and set `decreaseAllowance` as a function name.
- Add the first argument and set **Address** with the input as the client EVM address.
- To parse the client address, go to [Open-RPC Playground](https://playground.open-rpc.org/?url=https://api.node.glif.io), find `Filecoin.FilecoinAddressToEthAddress` on the left side, expand it, and click **TRY IT NOW**.
- As **params**, enter `["client filecoin address", null]`, click **play**, and copy the result representing the Filecoin address as an EVM address.
- Add the second argument and set **Uint256**, with the input as the DataCap amount in bytes (e.g., `281474976710656 = 256TiB`). Use the [data unit converter](https://www.dataunitconverter.com/byte-to-tebibyte/) for assistance.
3. Copy the **Encoded data**.
### 11. Prepare "value" for Lotus multisig propose
1. Visit [cbor.me](https://cbor.me/).
2. On the left side, enter copied encoded data:
```
h'encoded data'
```
3. Select the checkbox **plain text**, then click **Convert to bytes**.
4. Copy the converted data from the right side.
### 12. Create Lotus multisig propose
Run the following command to create a multisig proposal:
```sh
lotus msig propose --from=proposerAddress walletAddress destinationAddress value method params
```
Where:
- `proposerAddress` is the address of your ledger wallet.
- `walletAddress` is the address of the allocator multisig.
- `destinationAddress` is the `Client Contract Address` from the client's JSON.
- `value` – the amount of FIL to send; should always be set to `0`.
- `method` – the numeric identifier of the called method; should be set to `3844450837`.
- `params` is the converted data from CBOR.
Executing the command will generate a transaction CID, which can be used to verify the transaction on Filfox. If the multisig requires more than one approval, log in to your multisig account, complete the signing process, and then check the returned CID by multisig on Filfox to confirm the transaction's success.
https://filfox.info/en/message/<returned_cid>
Once the transaction is completed, go to the **Internal Transfer** section, expand **InvokeContract**, and check if `exitCode` equals 0. If not, an error has occurred at some stage.
### Important Information
Removing DataCap does not directly return it to the allocator but remains on the contract. To utilize this DataCap, you must repeat the steps from **Prepare calldata**, but instead of setting `decreaseAllowance`, set `increaseAllowance`.
Allocator should post an issue on the github informing the client about changes for book keeping