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: seth/README.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -813,11 +813,12 @@ With `SETH_LOG_LEVEL=trace` we will also log to console all traffic between Seth
813
813
814
814
### Read-only mode
815
815
It's possible to use Seth in read-only mode only for transaction confirmation and tracing. Following operations will fail:
816
-
* contract deployment
817
-
*gas estimations (we need the pk/address to check nonce)
816
+
* contract deployment (we need a pk to sign the transaction)
817
+
*new transaction options (we need the pk/address to check nonce)
818
818
* RPC health check (we need a pk to send a transaction to ourselves)
819
819
* pending nonce protection (we need an address to check pending transactions)
820
820
* ephemeral keys (we need a pk to fund them)
821
+
* gas bumping (we need a pk to sign the transaction)
821
822
822
823
The easiest way to enable read-only mode is to client via `ClientBuilder`:
823
824
```go
@@ -831,3 +832,10 @@ The easiest way to enable read-only mode is to client via `ClientBuilder`:
831
832
```
832
833
833
834
when builder is called with `WithReadOnlyMode()` it will disable all the operations mentioned above and all the configuration settings related to them.
835
+
836
+
Additionally, when the client is build anc `cfg.ReadOnly = true` is set, we will validate that:
0 commit comments