Skip to content

Commit 98bd4a7

Browse files
authored
Revert "Email obfuscation fix test"
1 parent 7a27fcb commit 98bd4a7

File tree

1 file changed

+21
-33
lines changed

1 file changed

+21
-33
lines changed

docs/pos/how-to/full-node/full-node-ansible.md

Lines changed: 21 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11

2-
An [Ansible playbook](https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html) is used to configure and manage a full node.
2+
An [Ansible playbook](https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html) is used to
3+
configure and manage a full node.
34

45
## Prerequisites
56

@@ -12,7 +13,8 @@ An [Ansible playbook](https://docs.ansible.com/ansible/latest/user_guide/playboo
1213
- You will also need to ensure that Go is **not installed** in your environment. You will run into issues if you attempt to set up your full node through Ansible with Go installed as Ansible requires specific packages of Go to be installed.
1314
- You will also need to make sure that your VM / Machine does not have any previous setups for Polygon Validator or Heimdall or Bor. You will need to delete them as your setup will run into issues.
1415

15-
!!! info "Heimdall source enhancements"
16+
!!!info
17+
Heimdall source enhancements
1618

1719
The latest Heimdall version, **[v1.0.3](https://github.com/maticnetwork/heimdall/releases/tag/v1.0.3)**, contains a few enhancements.
1820
The delay time between the contract events of different validators **has been increased** to ensure that the mempool doesn't get filled quickly in case of a burst of events that could hamper the chain's progress.
@@ -69,44 +71,30 @@ An [Ansible playbook](https://docs.ansible.com/ansible/latest/user_guide/playboo
6971

7072
- Please **ensure that the value of seeds and bootnodes mentioned below is the same value as mentioned in Heimdall and Bor `config.toml` files**. If not, change the values accordingly.
7173

72-
### Heimdall seed nodes
74+
- Heimdall seed nodes:
7375

74-
```bash
75-
moniker=<enter unique identifier>
76-
```
77-
Copy the following line and add it to the config file to define the seed node addresses.
78-
79-
seeds="<!--email_off-->1500161dd491b67fb1ac81868952be49e2509c9f@52.78.36.216<!--/email_off-->:26656,<!--email_off-->dd4a3f1750af5765266231b9d8ac764599921736@3.36.224.80<!--/email_off-->:26656,<!--email_off-->8ea4f592ad6cc38d7532aff418d1fb97052463af@34.240.245.39<!--/email_off-->:26656,<!--email_off-->e772e1fb8c3492a9570a377a5eafdb1dc53cd778@54.194.245.5<!--/email_off-->:26656,<!--email_off-->6726b826df45ac8e9afb4bdb2469c7771bd797f1@52.209.21.164<!--/email_off-->:26656"
80-
81-
**Mainnet**
82-
83-
- 1500161dd491b67fb1ac81868952be49e2509c9f@52.78.36.216:26656
84-
- dd4a3f1750af5765266231b9d8ac764599921736@3.36.224.80:26656
85-
- 8ea4f592ad6cc38d7532aff418d1fb97052463af@34.240.245.39:26656
86-
- e772e1fb8c3492a9570a377a5eafdb1dc53cd778@54.194.245.5:26656
87-
- 6726b826df45ac8e9afb4bdb2469c7771bd797f1@52.209.21.164:26656
76+
```bash
77+
moniker=<enter unique identifier>
8878

89-
**Testnet**
79+
# Mainnet:
80+
seeds="1500161dd491b67fb1ac81868952be49e2509c9f@52.78.36.216:26656,dd4a3f1750af5765266231b9d8ac764599921736@3.36.224.80:26656,8ea4f592ad6cc38d7532aff418d1fb97052463af@34.240.245.39:26656,e772e1fb8c3492a9570a377a5eafdb1dc53cd778@54.194.245.5:26656,6726b826df45ac8e9afb4bdb2469c7771bd797f1@52.209.21.164:26656"
9081

91-
- 9df7ae4bf9b996c0e3436ed4cd3050dbc5742a28@43.200.206.40:26656
92-
- d9275750bc877b0276c374307f0fd7eae1d71e35@54.216.248.9:26656
93-
- 1a3258eb2b69b235d4749cf9266a94567d6c0199@52.214.83.78:26656
82+
# Testnet:
83+
seeds="9df7ae4bf9b996c0e3436ed4cd3050dbc5742a28@43.200.206.40:26656,d9275750bc877b0276c374307f0fd7eae1d71e35@54.216.248.9:26656,1a3258eb2b69b235d4749cf9266a94567d6c0199@52.214.83.78:26656"
84+
```
9485

9586
!!! tip
87+
The following Heimdall seed can be used for both mainnet and Mumbai testnet: `8542cd7e6bf9d260fef543bc49e59be5a3fa9074@seed.publicnode.com:27656`
9688

97-
The following Heimdall seed can be used for both mainnet and Mumbai testnet:
98-
99-
8542cd7e6bf9d260fef543bc49e59be5a3fa9074@seed.publicnode.com:27656
89+
- Bootnodes:
10090

101-
### Bootnodes
102-
103-
```bash
104-
# Mainnet:
105-
bootnode ["enode://b8f1cc9c5d4403703fbf377116469667d2b1823c0daf16b7250aa576bacf399e42c3930ccfcb02c5df6879565a2b8931335565f0e8d3f8e72385ecf4a4bf160a@3.36.224.80:30303", "enode://8729e0c825f3d9cad382555f3e46dcff21af323e89025a0e6312df541f4a9e73abfa562d64906f5e59c51fe6f0501b3e61b07979606c56329c020ed739910759@54.194.245.5:30303"]
91+
```bash
92+
# Mainnet:
93+
bootnode ["enode://b8f1cc9c5d4403703fbf377116469667d2b1823c0daf16b7250aa576bacf399e42c3930ccfcb02c5df6879565a2b8931335565f0e8d3f8e72385ecf4a4bf160a@3.36.224.80:30303", "enode://8729e0c825f3d9cad382555f3e46dcff21af323e89025a0e6312df541f4a9e73abfa562d64906f5e59c51fe6f0501b3e61b07979606c56329c020ed739910759@54.194.245.5:30303"]
10694
107-
# Testnet:
108-
bootnodes ["enode://bdcd4786a616a853b8a041f53496d853c68d99d54ff305615cd91c03cd56895e0a7f6e9f35dbf89131044e2114a9a782b792b5661e3aff07faf125a98606a071@43.200.206.40:30303", "enode://209aaf7ed549cf4a5700fd833da25413f80a1248bd3aa7fe2a87203e3f7b236dd729579e5c8df61c97bf508281bae4969d6de76a7393bcbd04a0af70270333b3@54.216.248.9:30303"]
109-
```
95+
# Testnet:
96+
bootnodes ["enode://bdcd4786a616a853b8a041f53496d853c68d99d54ff305615cd91c03cd56895e0a7f6e9f35dbf89131044e2114a9a782b792b5661e3aff07faf125a98606a071@43.200.206.40:30303", "enode://209aaf7ed549cf4a5700fd833da25413f80a1248bd3aa7fe2a87203e3f7b236dd729579e5c8df61c97bf508281bae4969d6de76a7393bcbd04a0af70270333b3@54.216.248.9:30303"]
97+
```
11098

11199
- To check if Heimdall is synced
112100
- On the remote machine/VM, run `curl localhost:26657/status`
@@ -143,6 +131,6 @@ journalctl -u bor.service -f
143131

144132
## Ports and Firewall Setup
145133

146-
Open ports 22, 26656, and 30303 to world (0.0.0.0/0) on sentry node firewall.
134+
Open ports 22, 26656 and 30303 to world (0.0.0.0/0) on sentry node firewall.
147135

148136
You can use VPN to restrict access for port 22 as per your requirement and security guidelines.

0 commit comments

Comments
 (0)