Table of contents
Most Elementum MRSP guides end the moment the addon installs. That’s the boring part. I wanted to know what this torrent engine does once it’s running on a Firestick: who can see your IP, how much it uploads behind your back, what it does to storage and RAM, and whether you can get rid of it cleanly afterward. So, is Elementum MRSP safe to run in 2026? Short answer: it depends heavily on how your network is set up. The long answer, with my test results, takes up the rest of this page.
A quick note on method. I only streamed public-domain and freely licensed material, mostly old films from the Internet Archive and Creative Commons titles like Big Buck Bunny (the Blender Foundation short that every streaming tester has watched far too many times). You can repeat every test below without touching anything copyrighted.
Elementum MRSP in Plain English
Elementum MRSP is a Kodi addon that streams video straight out of BitTorrent swarms. You pick a torrent. The addon then fetches pieces in playback order rather than the random order a normal client uses, and Kodi starts playing the file while the rest is still arriving.
Two parts do the work. You see the Python addon inside Kodi. Behind it sits a compiled background engine, usually called the “daemon,” which handles the actual torrenting.
How It Relates to the Original Elementum
The family tree goes back roughly a decade. The original Elementum, maintained by elgatito, descends from Quasar, which grew out of an older project called Pulsar around 2014–2015. Elementum became the default torrent engine for Kodi for three reasons: it was fast, it was built on libtorrent, and dozens of other addons could hook into it.
Elementum MRSP is a community-maintained continuation of that engine. As of this writing, [MAINTAINER NAME / GITHUB HANDLE] maintains it and publishes it at [OFFICIAL REPO URL]. I tested version [VERSION NUMBER], checked on [DATE]. I won’t make claims about features in other versions. Forks move fast, and the changelogs are often thin.
Why People Use It Instead of Scraper Addons
Scraper addons like Umbrella or Infinity hunt for hosted links, meaning HTTP files sitting on file lockers or debrid services, and play them like any other web video. Your Firestick downloads from one server. That’s it.
Torrent streaming works differently. No central server means no dead hoster links, and that’s the whole appeal. The cost? You become part of the distribution network yourself, which brings us to the part most tutorials skip entirely.
What Torrent Streaming Actually Does on Your Network
If you read one section before installing, make it this one. The privacy model of BitTorrent has almost nothing in common with Netflix or a typical IPTV stream.
You Are a Peer, Not Just a Viewer
When Elementum joins a torrent, it announces itself to trackers and to the DHT network. Every other peer in that swarm can see your public IP address and port. Not a bug. That’s how peers find each other in the first place.
Anyone can join a swarm, including companies that get paid to log every IP taking part. With HTTP streaming, only the server you’re pulling from sees your address, but with torrents, a popular swarm can mean hundreds of strangers have it within a few minutes.
Uploading While You Watch: Why It Matters
BitTorrent runs on reciprocity. You download pieces, and you serve pieces back. In my testing, Elementum MRSP uploaded data during playback on its default settings: over a [DURATION]-minute session it pushed out roughly [X MB] while pulling in [Y MB].
Two reasons this matters. Legally, many countries treat distribution (uploading) as more serious than downloading. Practically, it eats your upstream bandwidth, and plenty of US cable plans still cap upload somewhere around 10–35 Mbps, even on packages sold as “gigabit.”
Depending on configuration, the engine can also keep seeding after you stop watching. I’ll show you how to shut that down further below.
Legal and ISP Exposure: The Honest Version
I’m not a lawyer. The rules differ a lot by country, and they change. In the US, rights holders typically send notices through your ISP, and repeat notices can end in throttling or a cut connection. The UK, Germany, and parts of Europe have seen rights holders go after individual downloaders more aggressively. Germany is the famous one, with its “Abmahnung” warning letters, which come with a fee demand that Reddit users commonly report in the high hundreds of euros.
Torrenting public-domain or properly licensed content is legal almost everywhere. What you stream is on you. The tool is neutral, but the swarm doesn’t care what you meant to do. It just records your IP.
Our Test: IP Exposure With and Without a VPN
This was the heart of the audit. Everyone says “use a VPN.” But “I have a VPN” and “my torrent traffic is actually going through the VPN” are two very different statements, and I’ve seen the gap between them catch out people who really should know better.
Test Setup (Firestick 4K Max, Kodi, Torrent IP Checker)
- Device: Fire TV Stick 4K Max (2nd gen, the 2023 model with 16GB storage and 2GB RAM), Fire OS [VERSION]
- Kodi: [KODI VERSION] from the official Kodi site
- Elementum MRSP: [VERSION], default settings unless noted
- Connection: [ISP / SPEED] home fiber
- IP check: the torrent address detection tool at ipleak.net, which hands you a magnet link and then reports which IP the “swarm” sees
The checker torrent holds no real content. It’s a tracker that logs whoever connects, which makes it an ideal test case. I loaded the magnet in Elementum, waited two minutes, and refreshed the results page.
Results Without a VPN
No surprises. The checker logged my real ISP-assigned IP within about [X] seconds, and it identified the client as libtorrent-based. Anyone sitting in a real swarm would have seen exactly that.
Results With a VPN App vs Router-Level VPN
Next I tested three VPN configurations, plus one deliberate mistake.
| Setup | IP Seen by Swarm | Leak on VPN Drop? | Notes |
|---|---|---|---|
| No VPN | Real ISP IP | N/A | Full exposure |
| VPN app on Firestick, full tunnel | VPN IP | Yes, briefly, without kill switch | Fine while connected |
| VPN app, split tunneling, Kodi excluded | Real ISP IP | N/A | Silent leak: VPN icon still “on” |
| Router-level VPN (WireGuard) | VPN IP | Depends on router kill switch | Covers every device on the network |
| VPN app + Elementum bound to tun interface | VPN IP | No: traffic stopped | Most leak-resistant in my tests |
The split-tunneling row is the one that bothers me. Lots of people exclude Kodi from their VPN because some live TV source or sports addon blocks VPN IPs. The app still says “Connected.” So they assume they’re covered, and they aren’t.
Why? On Android-based systems like Fire OS, Kodi launches the Elementum daemon, and the daemon runs under Kodi’s app identity. Per-app split tunneling keys off that identity, so excluding Kodi excludes the torrent engine with it. I go through the routing logic step by step in my Kodi VPN split tunneling guide.
The router VPN did well, and it has one real advantage: the Firestick can’t “forget” to connect. The catch is policy routing. Many routers support it, and if your Firestick sits on the bypass list, you’re leaking again. My router VPN breakdown covers the trade-offs for IPTV and Kodi in more depth.
Binding Elementum to the VPN Interface
Elementum’s network settings let you choose which interface the engine listens on and sends traffic through. Labels shift between versions (and they’re tucked away in the advanced settings level, annoyingly), so look for something like “listen interfaces” or “outgoing interfaces” under the advanced or network section. When an Android VPN app connects, it usually creates an interface called tun0.
Once I bound Elementum to tun0, I killed the VPN mid-stream. The torrent just stalled. Nothing went out over my regular connection, and the checker never logged my real IP. That’s precisely what you want.
Two caveats. The interface name can change between VPN apps or after a reconnect, so retest after every VPN update (yes, really, every one). And if the VPN isn’t up when Kodi starts, Elementum may throw errors until it is. Irritating? Sure. Far better than leaking, though.
Protocol matters as well. Personally, I’ve found WireGuard handles torrent throughput noticeably better than OpenVPN on the Firestick’s modest quad-core chip, which makes sense given how much lighter its encryption overhead is. The actual figures are in my Kodi VPN protocol tests.
Firestick Resource Test: Storage, RAM and Heat
The other half of the audit looked at the hardware. Firesticks are not generous machines. Torrent engines love to cache.
Memory Buffer vs File Storage Mode
Elementum gives you two download modes. Memory mode keeps a rolling buffer of pieces in RAM and throws them away after playback. File mode writes the torrent to storage as it downloads.
| Metric | Memory Mode | File Mode |
|---|---|---|
| Free storage before session | [X GB] | [X GB] |
| Free storage after 1 film (~[SIZE] GB file) | [X GB] | [X GB] |
| Leftover files after stopping | [NONE / X MB] | [X GB] |
| Peak RAM used by Kodi + daemon | [X MB] | [X MB] |
| Seeking smoothness | [OBSERVATION] | [OBSERVATION] |
Memory mode was clearly kinder to storage. File mode handles skipping back and forth in long videos better, but on a 16GB device it can fill the disk in a single session if the file is big.
What Happens on 8GB Devices
Here’s where it gets tight. The Firestick Lite, the 3rd-gen Firestick, and the original 2021 4K Max all ship with 8GB of storage, and the first two only have 1GB of RAM. Once Fire OS and a few apps are installed, you often have 4–5GB free. A single 1080p film in file mode can blow straight past that.
I ran the same test on an 8GB [MODEL]. In file mode, [OBSERVATION: e.g. playback stalled / Kodi errored / Fire OS showed low-storage warning] once free space fell below [X MB]. Own one of these? Use memory mode and keep the buffer small. A full disk on Fire OS slows down the whole system, not just Kodi.
Buffering and Stability Observations
On the 4K Max, [OBSERVATION: e.g. number of crashes, Kodi slowdowns, menu lag while the daemon was active]. The stick ran [warm / noticeably hot] after [X] minutes of continuous torrent streaming, which is what you’d expect when the same chip is juggling VPN encryption, piece verification, and video decoding all at once.
For comparison I repeated the test on a [NVIDIA Shield TV Pro / Chromecast with Google TV]. [OBSERVATION: e.g. faster buffer fill, larger memory buffer without issue, no lag]. If you’re serious about torrent streaming, extra RAM makes a genuine difference, and the Shield Pro’s 3GB is still a comfortable step up from any Firestick.
Elementum MRSP Settings Worth Changing Before First Use
This isn’t an install walkthrough. These are the privacy and resource changes I’d make before streaming a single file. Setting names drift a little between versions, so pick the closest match.
Upload and Seeding Limits
- Cap the upload rate. A low limit shrinks your distribution footprint and takes pressure off your upstream bandwidth. Setting it to zero can slow some swarms, though, because peers favor clients that share.
- Disable seeding after playback. A Firestick has no business serving data once you’ve finished watching.
- Limit connections. Fewer max peers means less CPU load on budget sticks, and fewer strangers seeing your IP at the same moment.
Buffer Size and Storage Location
- Use memory mode on Firesticks. Keep the buffer to a few hundred MB on 2GB-RAM devices, and smaller on 1GB models like the Lite.
- If you need file mode, point it at a USB drive through an OTG adapter rather than internal storage.
Proxy and Network Interface Options
- Bind to the VPN interface (usually tun0), as covered above. Of everything on this list, this one matters most.
- SOCKS5 proxy is something a few VPN providers include. A proxy hides your IP from peers but leaves traffic unencrypted from your ISP’s point of view. Treat it as a fallback, not a VPN replacement.
- Disable UPnP/NAT-PMP port mapping when you’re on a VPN. It does nothing useful there and can open ports on your home router whenever the VPN drops.
Auto-Clearing Cache
- Turn on any option to delete files after playback or clear the cache on exit.
- Even then, peek at the download folder now and again. In my testing, [OBSERVATION: e.g. aborted sessions left partial files behind].
Red Flags: Verifying the Repo and Binaries
Most Kodi addons are plain Python you can open and read in a text editor. Elementum isn’t. That raises the trust bar considerably.
Why Elementum Ships Native Binaries
The torrent engine is compiled code, built separately for ARM, x86, and each operating system. It runs as its own process with full network access. You can’t skim it like a Python script, so you’re trusting whoever compiled it.
The original Elementum is open source, which means people can audit the code. A fork’s binary, however, is only as trustworthy as its build process and the person behind it. No need to panic. Just be picky about where you download it.
Checking the Source Before Installing
- Find the project’s GitHub page: [OFFICIAL REPO URL]. Look for recent commits, open issues with replies from the maintainer, and a visible history going back a while.
- Read the release notes for the exact version you’re installing. Vague or missing notes aren’t damning on their own, but they deserve a second look.
- Grab the repo zip from the official releases page, not from a random Kodi build or a re-upload.
- If the maintainer publishes checksums, compare them on a PC using
sha256sum(Linux/macOS) orGet-FileHash(Windows PowerShell). [NOTE: confirm whether MRSP publishes hashes.]
Want a broader method that also covers APKs? My Firestick malware check guide shows how to spot hidden RATs and suspicious permissions.
Spotting Impersonator Repos
Popular addons attract copycats. Be wary of any repo that:
- Bundles Elementum inside a “build” with dozens of other addons
- Uses a slightly misspelled name or an unfamiliar GitHub account
- Asks you to install a separate APK “to enable” the engine
- Comes from a YouTube description link rather than the project page
I’d also keep an eye on outbound traffic from the device every so often. My piece on Android TV apps phoning home shows a simple way to catch unexpected connections with a Pi-hole or your router logs.
Removing Elementum MRSP Cleanly
Uninstalling the addon is only half the job. The engine can leave data lying around.
Uninstalling the Addon and Repo
- In Kodi, go to Add-ons → My add-ons → Video add-ons, select Elementum, and choose Uninstall.
- Remove any addon that depends on it, or Kodi may quietly reinstall it.
- Go to Add-ons → My add-ons → Add-on repository and uninstall the Elementum MRSP repo.
- Restart Kodi properly. On a Firestick, use Settings → Applications → Manage Installed Applications → Kodi → Force Stop, then reopen it.
Clearing Leftover Torrent Data
After uninstalling, I checked storage with a file manager. [OBSERVATION: e.g. X MB remained in the userdata/addon_data/plugin.video.elementum folder]. Delete that folder by hand under Kodi’s userdata directory, plus any custom download path you set.
To confirm the daemon is really gone, reboot the Firestick and run the ipleak.net torrent check again. Nothing connects? Then the engine isn’t running. If you want to be thorough, you can also check for the engine’s local port (Elementum has traditionally used 65220) with a network tools app, but that step is optional.
Bodhi’s Verdict: Is Elementum MRSP Safe, and Who Should Run It?
So, is Elementum MRSP safe? Downloaded from the official source, the addon did nothing malicious in my testing. The risk sits with torrenting itself. Out of the box you’re a visible peer uploading to strangers, and a misconfigured VPN can leak all of that without a single warning on screen.
It suits you if: you enjoy tinkering, you’ll bind it to a VPN interface and retest after updates, and you either have a device with decent RAM or you’re happy living in memory mode.
Skip it if: you have an 8GB Firestick with little free space, you depend on split tunneling to keep other services working, or you want something you can set up once and forget about.
Like Kodi but not the peer exposure? Debrid-based setups are the lower-risk middle ground, typically running somewhere around $3–5 a month depending on the service and plan length. The debrid provider handles the torrent side on its own servers and sends you an ordinary HTTP stream, so your home IP never joins a swarm. That route has its own costs and trade-offs. The network footprint, though, is far smaller, and for most Firestick owners I think that’s the more sensible place to land.
⚖️ Legal Disclaimer: IPTV Wire does not own or operate any streaming service, application, or website mentioned in this article. We do not verify whether third-party services carry proper licensing. Users are responsible for ensuring they comply with copyright laws in their jurisdiction.
Frequently Asked Questions
Is Elementum MRSP safe to install on Kodi?
Reasonably, yes, as long as you download it from the official maintainer’s repo and verify the release. The bigger risk is network exposure. Torrenting shows your IP to every peer in a swarm unless your traffic actually runs through a VPN.
Does Elementum MRSP upload or seed while streaming?
Yes. Like any BitTorrent client, it uploads pieces to other peers during playback. You can cap the upload rate and turn off seeding after playback in the settings, but some uploading is simply how torrents work.
Do I need a VPN for Elementum MRSP?
If privacy matters to you, yes. Without one, your real IP is visible to the swarm and to anyone monitoring it. For the best protection, bind Elementum to the VPN’s interface so traffic stops dead if the VPN drops.
Will Elementum MRSP fill up my Firestick storage?
In file mode it can, especially on 8GB models. Memory mode keeps a rolling buffer in RAM and leaves very little on disk, so it’s the better pick for Firesticks.
What is the difference between Elementum and Elementum MRSP?
Elementum is the original torrent-streaming engine for Kodi. Elementum MRSP is a community-maintained continuation built on that codebase. Check the MRSP repo’s release notes for current differences, since forks change often.
Why does my VPN not protect Elementum traffic with split tunneling enabled?
On Fire OS and Android, the Elementum engine runs under Kodi’s app identity. Exclude Kodi from the VPN and the torrent traffic goes with it, even though the VPN app still shows as connected.



Comments
Leave a comment
Your email address will not be published. Comments are moderated before they appear.