# No farmer rewards on Taurus Apr-07 **URL:** \ **Category:** Support\ **Created:** [April 22, 2025, 8:28pm UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787 "2025-04-22T20:28:47Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![micar](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/micar/32/3037_2.png) [@micar](https://forum.autonomys.xyz/u/micar)\ **Post date:** [April 22, 2025, 8:28pm UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/1 "2025-04-22T20:28:47Z")
## Issue Report I have been running node operator and farmer for 3 days but did’t recive any vote/block rewards. Before Apr-07 release farmer rewads works fine. ### Environment i7-13700/64GB/4tb SSD/Windows 11 24H2 > **Details** > > .\subspace-node-windows-x86\_64-skylake-taurus-2025-apr-07 run --chain taurus --farmer --name “micar-taurus-operator” --base-path C:\Subspace\nodes\taurus --blocks-pruning archive-canonical --state-pruning archive-canonical --sync full – --domain-id 0 --operator-id 511 --blocks-pruning archive-canonical --state-pruning 28800 > > .\subspace-farmer-windows-x86\_64-skylake-taurus-2025-apr-07 farm --reward-address sudnwCpwwBF2EiGuRvoMoeE97PZMuyKdGqNXFRA3chX12NMyS path=C:\Subspace\farms\0,size=1000GB path=D:\Subspace\farms\0,size=1000GB path=E:\Subspace\farms\0,size=1000GB > > ![taurus-farmer](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/4/4cf1ac6d5b8e2bb18dd17f97e05947e805643d8f.png) > ![taurus-node](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/6/69232711b65d4cf7302bc4152d07e07fec0120ec.png) ---
**Author:** ![vexr](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/vexr/32/3498_2.png) [@vexr](https://forum.autonomys.xyz/u/vexr)\ **Post date:** [April 23, 2025, 12:02am UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/2 "2025-04-23T00:02:35Z")
You won’t be able to farm until your node is fully synced. Your node still has a long way to go, and it may be faster to delete your `db` and `domains` directories and start over using the `--sync snap` parameter. Make sure you’re using the latest `apr-22` release, as snap sync was not available prior to today’s update. If you’re also running an operator, be sure to back up the `keystore` directory located inside `domains` **before** deleting the `domains` directory, and restore it after your node is in sync. ---
**Author:** ![micar](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/micar/32/3037_2.png) [@micar](https://forum.autonomys.xyz/u/micar)\ **Post date:** [April 23, 2025, 5:01am UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/3 "2025-04-23T05:01:24Z")
Thank you, I will try new apr-22. Actualy because of high memory consumption before run apr-07 release I deleted my taurus c:\node\taurus folder and started sync from scratch (keystore was inside ☹). For the first couple days db grows fast until ~10GB and for the last 3 days size did’t changed thats why I decided that its fully synced. Can you please advise how i can understaned actualy sync progress (like 80%) and why db my size didn’t grow for 3 days? What now i need to do with operator, unregister and create new? ---
**Author:** ![vexr](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/vexr/32/3498_2.png) [@vexr](https://forum.autonomys.xyz/u/vexr)\ **Post date:** [April 23, 2025, 6:24am UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/4 "2025-04-23T06:24:54Z")
You should be able to recreate the private key as long as you backed up the seed phrase, using a command like `./subspace-node domain key insert --keystore-suri`. You can get help with the parameters by running `./subspace-node domain key insert --help`. As for progress, using snap sync should be considerably faster. It will “snap” to the latest finalized block and only needs to sync from there. You’ll know you’re fully synced when `best` is equal to `target`. There are some issues with syncing that still need to be addressed when doing a full sync, but snap sync should allow you to get back in sync quickly and should take up considerably less space in the process. ---
**Author:** ![vexr](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/vexr/32/3498_2.png) [@vexr](https://forum.autonomys.xyz/u/vexr)\ **Post date:** [April 23, 2025, 6:25am UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/5 "2025-04-23T06:25:50Z")
To use snap sync, you will need to remove the `db` and `domains` directories first, as mentioned above. ---
**Author:** ![micar](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/micar/32/3037_2.png) [@micar](https://forum.autonomys.xyz/u/micar)\ **Post date:** [April 23, 2025, 9:01am UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/6 "2025-04-23T09:01:08Z")
My steps with Apr-22 release: 1. I have tried to continue with -sync **full**. For 2 hours sync successfully progressed from best block 320k-\>370k and then stuck (best block didn’t changed for several hours). 2. I deleted db and domains as recomended and started with -sync **snap**. After few minues it stoped with error. > **Error** > > ![taurus-node](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/e/e6c5fc380dae4c4c887320b9c83ad850901ba329.png) > > .\subspace-node-windows-x86\_64-skylake-taurus-2025-apr-22 run --chain taurus --farmer --name “micar-taurus-operator” --base-path C:\Subspace\nodes\taurus --blocks-pruning archive-canonical --state-pruning archive-canonical --sync snap – --domain-id 0 --blocks-pruning archive-canonical --state-pruning 28800 ---
**Author:** ![vexr](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/vexr/32/3498_2.png) [@vexr](https://forum.autonomys.xyz/u/vexr)\ **Post date:** [April 23, 2025, 2:41pm UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/7 "2025-04-23T14:41:36Z")
Can you share the full log as a text? If using powershell, something like this should work. `subspace-node run | Tee-Object -FilePath "log.txt"` ---
**Author:** ![vexr](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/vexr/32/3498_2.png) [@vexr](https://forum.autonomys.xyz/u/vexr)\ **Post date:** [April 23, 2025, 8:50pm UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/8 "2025-04-23T20:50:23Z")
It appears I jumped the gun in recommending snap sync. There are still some issues with snap sync and setting up a domain node. While it works fine for consensus, it still doesn’t work for domains. Your peer count seemed low from your screenshots. It should eventually sync, but in its current state, it could take around 5 to 7 days. Properly port forwarding your ports is crucial to ensure you’re connectable to more peers and to help the process move forward. > **[Port Forwarding & Firewall | Farm from Anywhere](https://docs.autonomys.xyz/farming/guides/port-config/)** > > A comprehensive guide on port forwarding and firewall rules for Autonomys Network Make sure you set unique ports if you are also running a mainnet node on the same network. **Before** `--` ```auto --listen-on /ip4/0.0.0.0/tcp/ --dsn-listen-on /ip4/0.0.0.0/tcp/ ``` **After** `--` ```auto --listen-on /ip4/0.0.0.0/tcp/ ``` ---
**Author:** ![micar](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/micar/32/3037_2.png) [@micar](https://forum.autonomys.xyz/u/micar)\ **Post date:** [April 24, 2025, 8:16am UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/9 "2025-04-24T08:16:34Z")
Ok, understood. FYI here is log of my second attemp of running sync snap. This time there is no errors but it also stuck after reached 2GB db. > **Snap Log** > > [log.txt](https://forum.autonomys.xyz/uploads/short-url/sUss9IbCxSU2Ewy2DTXoWcvsYYZ.txt) (1.8 MB) I have 3 PC under my home router (2 for mainnet and 1 for testnet). I have checked on mainnet PCs number of peers are ~12-14 and on testnet ~1-2. It looks like your are right and problem is in low peers number for taurus. So, as I understand now i need to delete db and network one more time and set unique node port before restart taurus sync full? ---
**Author:** ![vexr](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/vexr/32/3498_2.png) [@vexr](https://forum.autonomys.xyz/u/vexr)\ **Post date:** [April 24, 2025, 8:22am UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/10 "2025-04-24T08:22:23Z")
Yes, you will want to set `--sync full` and remove the `db` and `domain` directories first. Make sure you explicitly set the ports as shown in the example above to ensure your node can connect to peers on the network. If you plan to farm with this node, it’s important to set a unique RPC port if there is more than one node running on the same machine. Use `--rpc-listen-on 0.0.0.0:9955` for the node, and configure the farmer with `--node-rpc-url ws://127.0.0.1:9955`. ---
**Author:** ![micar](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/micar/32/3037_2.png) [@micar](https://forum.autonomys.xyz/u/micar)\ **Post date:** [April 27, 2025, 5:43pm UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/11 "2025-04-27T17:43:54Z")
After 3 days of sync full with apr-22 release I’m still far way from compelete sync. Moreover it just synced 703 blocks. I tried different PC and completely different router. For 2 weeks I can sync taurus node and its abosolutly disapointing result. > **Apr-22** > > ![taurus-node](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/a/a096b57a77149b2457b535940eb35c35f4e47abe.png) For test purpose I run march-05 release which works perfect for me before. After 30 minutes of work it have much better results and more available peers. > **Mar-05** > > ![taurus-node2](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/4/4d318a7584987b7c6cf0e90576b552610c6c7275.png) So, I could conclude that problem not with my environmet or cofiguration and comes from april release changes. ---
**Author:** ![Jim-Autonomys](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/jim-autonomys/32/2922_2.png) [@Jim-Autonomys](https://forum.autonomys.xyz/u/Jim-Autonomys)\ **Post date:** [April 28, 2025, 8:01am UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/12 "2025-04-28T08:01:54Z")
Are you using exactly the same start command you originally provided with both releases? Could you supply the latest version please? I assume it’s changed to handle port overrides. Thanks. ---
**Author:** ![micar](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/micar/32/3037_2.png) [@micar](https://forum.autonomys.xyz/u/micar)\ **Post date:** [April 28, 2025, 5:44pm UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/13 "2025-04-28T17:44:07Z")
I repeated tests one more time so you can check logs below. Folder C:\Subspace\nodes\taurus was deleted before each test. > **Apr-22** > > .\subspace-node-windows-x86\_64-skylake-taurus-2025-apr-22 run --chain taurus --name “micar-core-operator” --base-path C:\Subspace\nodes\taurus --blocks-pruning archive-canonical --state-pruning archive-canonical --sync full --farmer – --domain-id 0 --blocks-pruning archive-canonical --state-pruning 28800 > > [log-apr-22-3.txt](https://forum.autonomys.xyz/uploads/short-url/rvbKaNUszApoPFHKrSPkNS9EKBC.txt) (142.6 KB) > **March-05** > > .\subspace-node-windows-x86\_64-skylake-taurus-2025-march-05 run --chain taurus --name “micar-core-operator” --base-path C:\Subspace\nodes\taurus --blocks-pruning archive-canonical --state-pruning archive-canonical --sync full --farmer – --domain-id 0 --blocks-pruning archive-canonical --state-pruning 28800 > > [log-mar-05-3.txt](https://forum.autonomys.xyz/uploads/short-url/lAJtmfTzj6jXiKkE92csmBjtfiT.txt) (267.3 KB) ---
**Author:** ![Jim-Autonomys](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/jim-autonomys/32/2922_2.png) [@Jim-Autonomys](https://forum.autonomys.xyz/u/Jim-Autonomys)\ **Post date:** [April 29, 2025, 11:44am UTC](https://forum.autonomys.xyz/t/no-farmer-rewards-on-taurus-apr-07/4787/14 "2025-04-29T11:44:55Z")
Unfortunately I don’t have actionable feedback for you beyond waiting for the next release I’m afraid. Here’s what the engineer who checked your logs said: > The initial failure in the last logs with the latest version is: > > `2025-04-28T15:05:13.845253Z WARN Consensus: subspace_service::sync_from_dsn: Error when syncing blocks from DSN error=Other: Failed to download segment pieces: Not enough (127) pieces` > > We could add a retry for this, but it won’t solve the underlying issue. > Either their network connectivity is poor, or the network itself is overloaded. I’m pretty sure this will get better as we roll out the fix for the substream limit bug, multiple fixes for slow block processing, and snap sync fixes. (Because snap sync downloads less data, it will be more reliable.) > > I’m not sure what to recommend in the meantime. Adding another fully synced peer to the substrate and DSN reserved peers would probably help. But it’s not a scalable solution. Are you noticing any connectivity issues elsewhere?