Tari Pool Block Winners, updates every 5 mins:
Pools for last 100 blocks
Pools for last 250 blocks
Pools for last 500 blocks
Pools for last 1000 blocks
Pools for entire chain (10 min update)

Node Setup Optimizations:
Jagtech/Hatchling Node list + Sigs
To use this, add the values in the above file to your config.toml in the "peer_seeds" under mainnet.p2p.seeds, this adds them as seeds to find additional peers. This should be done when your tari node is stopped, once added, delete the peer_db folder from your install, then start the node back up

Proxy Bypass Addresses
The tor.proxy_bypass_addresses configuration allows you to set addresses that do not need to go over tor, this can drastically increase node sync speed, look for the [base_node.p2p.transport] section, then the tor.proxy_bypass_addresses subsection. Setting the following with the above node list will allow direct TCP connections to the hatchling/jagtech nodes for node sync

Chain Snapshots
Chain snapshots allow for the importing of a recent snapshot of the chain into your tari node setup. This can be much faster than syncing over the P2P network.
To use these, download the file from the link above, make sure your node is on the same version as the database listed in the download.
Stop your tari node, and extract the file (Windows users may find 7zip to be useful, linux users can use unzstd to decompress these)
Make sure your tari node is stopped again
Head into the tari database folder (Linux: ~/.tari/mainnet/data/base_node/db) and replace the data.mdb file
Start the node and it should pick up the new database and start syncing from the tip there.

P2Pool setup - Legacy:

ALL OF THESE NOW MINE TO default_0 DUE TO CHANGES IN THE TARI NETWORK. ALL SQUADS FOR TU ARE NOW default_0

P2Pool Mining Addresses:
http://default-0.tari.jagtech.io:18145/
http://default-1.tari.jagtech.io:18145/
http://default-2.tari.jagtech.io:18145/
http://eu-default-0.tari.jagtech.io:18145/
http://eu-default-1.tari.jagtech.io:18145/
http://eu-default-2.tari.jagtech.io:18145/

The above are for each of the 3 p2pool squads for Tari, they are best-effort nodes, have auto-reboots/etc enabled to handle memory leaks/connection hangs/etc.
Glytex command line: glytex --engine opencl -a < address > -u < p2pool mining address > --p2pool-enabled
IE: glytex --engine opencl -a 1215dapiKwqGxk9TAjELMf9gnH6iKM5B9gLbMBvtDSVATRtnBsKDN8bfxGECaPC1wwA8AwRLnq1Ycg28Qx71uW8pABi -u http://default-0.tari.jagtech.io:18145/ --p2pool-enabled

A tiny restart scrpt is published at: https://core.tari.jagtech.io/restart.sh, standard security says you shouldn't trust anything here, but yanno, usage follows:
wget https://core.tari.jagtech.io/restart.sh
chmod +x restart.sh
./restart.sh /path/to/glytex tari_address p2pool_address
Ex: ./restart.sh /home/impala/tari/glytex 1215dapiKwqGxk9TAjELMf9gnH6iKM5B9gLbMBvtDSVATRtnBsKDN8bfxGECaPC1wwA8AwRLnq1Ycg28Qx71uW8pABi http://default-0.tari.jagtech.io:18145/

P2Pool Share Databases, updates at the top of every hour, used to bootstrap/repair a bad p2pool instance, choose based on geographic region, data should be the same:
US Nodes:
default_0 P2Pool SHA3X block_cache
default_0 P2Pool RandomX block_cache
default_1 P2Pool SHA3X block_cache
default_1 P2Pool RandomX block_cache
default_2 P2Pool SHA3X block_cache
default_2 P2Pool RandomX block_cache
EU Nodes:
default_0 P2Pool SHA3X block_cache
default_0 P2Pool RandomX block_cache
default_1 P2Pool SHA3X block_cache
default_1 P2Pool RandomX block_cache
default_2 P2Pool SHA3X block_cache
default_2 P2Pool RandomX block_cache

Usage of these files is as follows:
1. Determine which squad your p2pool is in, these files are /unique/ to each squad, the easiest way for Tari Universe users is to access the experimental section of TU and pull the pool port, then in your browser, access http://127.0.0.1:port from TU/stats, the squad will be in the response. If you're running P2Pool directly, it's in your logs and/or port 19000
2. Download the bootstrap files you need, they should match your squad. They will both be downloaded as data.mdb, as this is the final filename you need.
3. Follow below where to copy them. Usage of these files is to find the block_cache:
Windows/Linux/Mac: This varies depending on how you've run your sha_p2pool instance
Tari Universe Windows: C:\Users\< username >\AppData\Local\com.tari.universe\block_cache
Once located, ensure p2pool is stopped, if you are trying to fix a TU, go into the settings, turn off pooled mining or exiting the instance, DO NOT EXIT TU OR IT WILL WIPE OUT THE CACHES, then copy the data.mdb's to the correct folders
Start the p2pool or re-enable pool mining in TU, check your sync heights once it's up.

Systemd/Daemon Setups/files:
Install Tari + Tor, currently 5.0.0-pre.7 - This disables libtor and enables normal tor. The torrc disables exit nodes - Version can be verified by checking here
Tari Systemd File
P2Pool Systemd File
The above files are systemd files, these are used to turn the tari code systems into proper daemons. They make some assumptions, so you may need the edit them for the following:
1. The tari-suite and p2pool zips have both been extracted to /home/tari/ and it's owned by the tari user
2. The node has been stood up once, and Y has been entered twice so that it sets up it's configurations.
3. They both have auto restarts to help deal with memory leaks
4. The P2Pool contains a squad override, set this to whatever squad you want it to be in.

Provided by:
Discord: Impala/Jagtech
Telegram: @Impala59
Github: Snipa22
Tari Addreess: 1215dapiKwqGxk9TAjELMf9gnH6iKM5B9gLbMBvtDSVATRtnBsKDN8bfxGECaPC1wwA8AwRLnq1Ycg28Qx71uW8pABi
XMR Address: 46XWBqE1iwsVxSDP1qDrxhE1XvsZV6eALG5LwnoMdjbT4GPdy2bZTb99kagzxp2MMjUamTYZ4WgvZdFadvMimTjvR6Gv8hL