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
Since we can’t provide baseFeePerGas to firmware, we should calculate **_effective gas price_** on the suite side and pass the selected price to maximum_fee. Priority fee is being passed just for the purpose of displaying it, in fact it's being already included into effective gas price.
30
+
31
+
### Misc
32
+
33
+
I have some thought processes documented [here](https://excalidraw.com/#json=0l28PPN7iSp-ekzch1igV,iQnn7yW7gpQ-6mWcK1nUAw), although it's not complete, it can help you to understand how I reasoned about the forms. Which is the most challenging part about implementing this feature.
34
+
35
+
While testing, I recommend having a list of each part of the app where you have the fees component and after you test it document the send transaction.
36
+
37
+
### Staking
38
+
39
+
#### Stake
40
+
41
+
#### Unstake/Claim
42
+
43
+
### Send
44
+
45
+
### Swap
46
+
47
+
#### Approval tx for tokens on DEX
48
+
49
+
#### The swap tx on DEX
50
+
51
+
#### CEX
52
+
53
+
### Sell
54
+
55
+
Each of the above scenarios has to be tested with:
56
+
57
+
- legacy fees with backend disconnected/returning only normal fee level (standard and custom)
58
+
- legacy fees when the network feature is turned off
0 commit comments