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
3. Edit `$IOTEX_HOME/etc/config.yaml`, look for `externalHost` and `producerPrivKey`, uncomment the lines and fill in your external IP and private key. If you leave `producerPrivKey` empty, your node will be assgined with a random key.
3. Edit `$IOTEX_HOME/etc/config.yaml`, look for `externalHost` and `producerPrivKey`, uncomment the lines and fill in your external IP and private key. If you leave `producerPrivKey` empty, your node will be assgined with a random key.
v2.3.4 is a **recommended** maintenance release that adds a default blacklist configuration to improve network security.
6
+
7
+
**Note:**
8
+
The mainnet `config.yaml` now includes a default blacklist for enhanced security. You only need to restart your node with the new v2.3.4 image to apply these changes.
9
+
10
+
## Key Features and Enhancements
11
+
12
+
### Default Blacklist Configuration
13
+
v2.3.4 introduces a default blacklist configuration to improve network security. This blacklist contains a list of malicious or problematic EOA (Externally Owned Account) addresses that will be filtered by the node.
14
+
15
+
-**Recommended Upgrade**: All node operators are strongly encouraged to upgrade to benefit from the enhanced security protections
16
+
-**Account Filtering**: The default blacklist filters transactions and interactions from known malicious addresses
17
+
-**No Manual Configuration Required**: The blacklist is pre-configured in the default config files
18
+
19
+
## Upgrade Priority
20
+
21
+
v2.3.4 is a **recommended** release due to the addition of the default blacklist configuration for improved network security.
0 commit comments