Filterms is a free, open-source tool for developers who use the Golem network as a requestor through the yapapi library. It sits between your code and the offers that providers send back, so you can whitelist or blacklist them before committing to a job. Despite its place in our trading bots category, it does not place trades or manage a portfolio; it filters compute offers.
The project works out of the box with yapapi 0.13.1 and supports filtering by CPU features, with network-level filtering planned for a later update. Its documentation mentions Windows alongside macOS and Linux, so Windows users can try it, but check the docs for any platform-specific steps. The sections below explain what it does, how to install it, and how it compares with other tools in this catalog.
What Is a Requestor on the Golem Network?
On the Golem network, a requestor is the side that needs computing power. It publishes a task, receives offers from providers who have machines available, and then chooses which providers to work with. The yapapi library is one way developers write that requestor logic in code.
Offers arrive as a stream of proposals that differ in hardware, price and reliability. Without filtering, your script has to evaluate every offer as it comes in. That is manageable for small experiments, but it becomes tedious when you run the same job repeatedly and want consistent results.
Filtering moves that decision earlier. You define rules once, and the tool applies them to each incoming offer. Understanding this flow makes it easier to see why a filter belongs in the requestor pipeline rather than in a separate application.
Who Needs an Offer Filter?
Offer filtering is most useful for developers who run requestor scripts regularly. A researcher who processes similar batches every week may want to keep only providers with hardware that has performed well before. A developer testing a new workload may prefer to exclude machines with features their code does not use.
Small teams can also use blacklists to avoid providers that caused failures in earlier runs. Keeping a short written list of accepted and rejected providers, along with the date of each decision, makes the process easier to review.
If you only want to try decentralized computing once, a simple script with default settings may be enough. A filter adds the most value when you care about repeatability and want to control which machines your tasks run on.
How Do Offer Filters Shape Task Results?
A filter changes the pool of providers your job can choose from, so it affects speed, reliability and cost indirectly. A narrow whitelist can produce more predictable runs, but it may also leave you with fewer options when demand is high. A broad blacklist keeps more providers available, but you accept more variation.
CPU feature filtering is a practical way to match hardware to code. If your program needs a specific instruction set, excluding providers without it prevents failures that would otherwise appear only after a task starts.
Test changes on a small job first. Compare the results with and without your filter so you can judge whether the narrower pool helps your specific workload.
Key features
Whitelist and Blacklist Filtering
CPU Feature Filtering
Built for yapapi 0.13.1
Open Source Code
Supported coins
Filterms works on compute offers from the Golem network rather than on coins or trading pairs, so the relevant choices are which providers and hardware profiles you accept. It is not a tool for selecting cryptocurrencies to trade.
How to install Filterms on Windows
- 1
Check the Version Requirement
Install yapapi 0.13.1 before setting up the filter, since that is the version the project is built to work with. Confirm your existing requestor script runs with that version before adding any filtering rules.
- 2
Get the Source From the Official Source
Download only from the official website or the project's GitHub repository at github.com/krunch3r76/filterms. If the project publishes a GitHub Releases page with packaged files, use the release that matches your yapapi version.
- 3
Verify the Download
If a SHA-256 checksum or signature is published for the release, compare it with your file before extracting anything. Where no checksum is listed, review the commit history and tag on GitHub so you know exactly which code you are running.
-
Install and Test With a Small Job
Install the package into the same environment as your yapapi requestor, then run a short test with a single whitelist or blacklist rule. Check that the filtered offer list looks right before running a larger task.
System requirements
- yapapi 0.13.1, the version the filter is designed to work with
- Windows is mentioned in the project documentation, so check the docs for platform-specific setup steps
How to use Filterms
Filterms is used inside a requestor script rather than as a standalone window. Start with a small, clearly defined rule set so you can see its effect before scaling up.
- Confirm that your requestor script runs correctly with yapapi 0.13.1.
- Decide whether you want a whitelist of accepted providers, a blacklist of rejected ones, or CPU feature criteria.
- Add the filter to your script so it checks each incoming offer before your logic accepts it.
- Run a short test task and review which offers were kept and which were excluded.
- Adjust the rules based on the results, and keep a written record of each change so you can repeat the setup later.
Pros & cons
- Free and open source, with the full code on GitHub
- Simple whitelist and blacklist logic that is easy to reason about
- Filters by CPU features in the current release
- Designed to work with yapapi 0.13.1 out of the box
- Recent code updates show ongoing maintenance
- Network-level filtering is still on the roadmap
- Tied to a specific yapapi version, so upgrades need checking
- Windows support is described in the docs but should be tested on your own machine
- Aimed at developers who are comfortable editing requestor scripts
Is Filterms safe?
Filterms is open source, so the safest path is to download it only from the official website or its GitHub repository and to avoid copies on unofficial mirrors. Compare the SHA-256 checksum or verify the signature when one is published, and review the commit or release tag before installing. The project's latest code update is from late October 2025, which suggests active maintenance, but changes should still be reviewed before you run them. The tool does not need a seed phrase or wallet keys to filter offers. Never enter a seed phrase on a third-party website, even if it claims to offer an update or add-on for Filterms. Check the latest version on the official website before you update.
- Official source only. Download from github.com/krunch3r76/filterms. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
Most tools in our trading bots and strategy testing categories focus on market activity. Gunbot and Moon Bot place orders on exchanges, ProfitTrailer and HaasOnline TradeServer manage trading strategies, and OctoBot offers a web interface for automated trading. Jesse is a framework for writing and testing strategies, and XTester and TestMyLogic focus on simulation and checking for overfitting. Filterms is different: it applies whitelist and blacklist rules to compute offers from the Golem network. If your goal is to test trading logic, one of the tools above fits better. If your goal is to control which Golem providers your requestor uses, Filterms addresses that narrower problem.
Specifications
- Price
- Free
- Type
- Open source
- License
- —
- Latest version
- —
- Last update
- 27 Oct 2025
- Windows support
- Unverified (Windows mentioned in docs)
- Source code
- github.com/krunch3r76/filterms
Frequently asked questions
No. Filterms is not a trading bot. It filters offers from the Golem network for requestors using yapapi, so it decides which providers your compute jobs can use. It does not place orders or manage funds on exchanges.
Yes, Filterms is listed as free and open source. You can read the source code on GitHub, check how offers are filtered, and use it without a paid license. Always verify the download before installing it on your system.
It can be, if you take basic precautions. Download it only from the official website or the GitHub repository, compare the SHA-256 checksum when one is published, and review the code or release tag before running it on your machine.
Yes. The project is built to work with yapapi 0.13.1 out of the box. You need a working yapapi requestor script before adding the filter, because Filterms operates on the offers that yapapi receives.
Not yet. The current version supports filtering by CPU features, and network filtering is described as coming soon. Watch the GitHub repository for release notes to learn when that capability is added.
A whitelist accepts only the providers you list, which gives you a narrow, controlled pool. A blacklist accepts everyone except the providers you exclude, which keeps more options open. Many developers start with a blacklist and move to a whitelist once they know which providers perform well.
Verdict
Filterms suits developers who already run yapapi requestor scripts on the Golem network and want more control over which providers they accept. Its whitelist, blacklist and CPU feature filtering are straightforward, and the code is open for review. It is not suitable for anyone looking for a trading bot, a backtester or a point-and-click app. Before relying on it, verify the download, test it on a small job, and check the latest version on the official website.