# ATAK, Cryptocurrency, Iphone App

_General · started by Quackman1 on Thu, Nov 19, 2026 12:24 PM_

Tags: Question

---

## Original post

**Quackman1** · Thu, Nov 19, 2026 12:24 PM

Hi Everyone,

Hope you are well.

Forgive me for posting multiple questions in one thread, if this violates any rules in this forum please excuse my lack of formality.

I wanted to ask whether ATAK Integration with Reticulum, violates the Zen of Reticulum. This is because it could theoretically violate the harm principle. I'm not talking about the license and distribution of LLM-Generated ATAK Bridges with Reticulum, but the underlying principle and does anything of this nature already exist. 

Similarly with cryptocurrency integration, does it violate the Zen of Reticulum? There is no monetary incentive from the founder, however I still wanted to know whether a well-thought of, distinct, verified & licensed implementation would violate any principles and does this exist?

Finally on an unrelated note is there an Iphone app to connect to Reticulum and Rnodes which has good network node behaviour? I remember seeing a post about some nodes having multiple announces and relaying messages unnecessarily hence the reason why I'm asking about a verified one.

Kindest Regards,
Le Quack

---

## Reply 1

**Mark** · Thu, Nov 19, 2026 1:11 PM

Having an actual, true Reticulum instance running on iOS is *fiendishly* difficult to do, because the operating system very strictly enforces applications not actually being allowed to function as a real application, but only as something more akin to a display surface, that is only allowed to do anything when the user is looking at it. Almost any "background work" that is still left possible on iOS have to go through managed APIs and external, central servers.

Needless to say, this is pretty catastrophic for a networking stack, which actually needs to stay running to receive packets from the various interfaces. If that is not possible, connectivity dies. The iOS "operating system" is very adversarial against any communication that is not funneled through the approved services.

But, I know that @Torlando (in the Columba app) is actually working on a proper solution here, that allows the full stack to run in the background as a VPN/networking extension. As far as I am aware, this is the *only* way currently possible to do it correctly, and it is not very straight-forward to get right, so hat's off to him for working on it.

But from what I understand, he actually has a test build of this, where it works. You could maybe ask him for a beta invite or something.

---

## Reply 2

**K8** · Thu, Nov 19, 2026 4:38 PM

**Mark** wrote:
> But, I know that @Torlando (in the Columba app) is actually working on a proper solution here, that allows the full stack to run in the background as a VPN/networking extension. As far as I am aware, this is the *only* way currently possible to do it correctly, and it is not very straight-forward to get right, so hat's off to him for working on it.
> 
> But from what I understand, he actually has a test build of this, where it works. You could maybe ask him for a beta invite or something.

Can confirm, Columba iOS is coming along very well. Torlando has been doing awesome work getting this running. The entire stack has to fit within 50MB of memory and is brutally murdered if it exceeds the limit. The storage and path culling improvements in RNS 1.6.0 made a big difference to the stability of the network extension, and it usually hovers around 45MB memory now. It’s still really tight, though, and things like large Resource transfers can push it past the limit.

---

## Reply 3

**Mark** · Thu, Nov 19, 2026 5:52 PM

And @Torlando, if you're reading this and there's anything additional I can do here to get this running smoothly, let me know. It's possible that we could add a memory-optimized mode/flag, that changes parts of the core behaviour towards a much more aggressively memory-optimized profile.

There's several instances of low-hanging fruit, where this could be applied quite effectively, I think. Especially now with the new DB-backed storage backend, and for a client application, almost everything can be kept out of live memory.

It's always a balance with these things though, since a when you *do* have the memory available, you want to actually use it constructively, which is very much needed on transport nodes, and such.

But there's a very good possibility we can squeeze this down *a lot* more by some simple tweaks with a dedicated, memory-optimized mode.

And jeez, 50MB of memory as a hard-kill limit. That's *harsh* man.

---

## Reply 4

**123321** · Thu, Nov 19, 2026 6:05 PM

The way Columba is using the VPN extension is a workaround that Apple won't approve in the App Store. This is not to say it is wrong, or that we should be catering to Apple's rules and monopoly, but it is something to consider.

I say this because, if the purpose is to build it with the idea that it can never escape TestFlight or local builds, then I think Apple offers better extensions and workarounds that can be used which won't be so limiting to just 50MB.

And of course if the plan is to eventually escape TestFlight, before putting too much time or thought into the workaround, perhaps consider the likelihood of Apple allowing it under how it works now, and their written policies.

Hopefully this is all known, though.

---

## Reply 5

**K8** · Thu, Nov 19, 2026 6:17 PM

@Mark I've been hoping that the sqlite-backed storage could be used to move most things out of memory, beyond just being used for persistence. That would be really ideal for this application. Skip the Python tables, let sqlite handle page caching, and have the cache size be configurable for applications with specific needs. I'd expect it to be an order of magnitude slower than plain, in-memory tables, though, so having it be a different memory-optimized mode makes a lot of sense to me.

@123321 This has been an open question, for sure. I can say that Orbot, the Tor client, is implemented in exactly this way with a Network Extension, and it has been approved by Apple. By my reading of Apple's policies and intentions for NEs, I think there is a very good chance it will be approved. The NE framework is intended to be used for "interesting" networking applications. Still, Apple *is* fickle and unpredictable...

---

## Reply 6

**K8** · Thu, Nov 19, 2026 6:56 PM

@123321 This is Apple’s guidance: https://developer.apple.com/documentation/technotes/tn3120-expected-use-cases-for-network-extension-packet-tunnel-providers

On one hand: “Do use a packet tunnel provider to access secure resources on an isolated network.”

On the other: “Do not use a packet tunnel provider to host a network listener or proxy server.”

So… 🤷‍♀️. Only one way to find out! I’m not aware of any other frameworks they offer that might be more suitable, do you know of alternatives? If this doesn’t pan out, I think the only other option for some kind of background operation over Internet links is, as Mark said, to have things go through an external server, and use Apple’s APNs for push notifications.

---

## Reply 7

**oatmilk!** · Fri, Nov 20, 2026 9:04 AM

**Quackman1** wrote:

> I wanted to ask whether ATAK Integration with Reticulum, violates the Zen of Reticulum. This is because it could theoretically violate the harm principle. I'm not talking about the license and distribution of LLM-Generated ATAK Bridges with Reticulum, but the underlying principle and does anything of this nature already exist. 


annddd, the forum ate my reply but basically
- https://github.com/markqvist/Reticulum/discussions/1062 says no killing people with your (intended) use of it, communication use is ok 
- https://reticulum.network/manual/brandolinis.html#who-is-restricted-by-which-license says no killing people with it

what i get from this is atak-civ is fine, atak-mil isn't. 

if @mark weighs in and goes "naw fuck atak" then we also now know

---

## Reply 8

**Torlando** · Fri, Nov 20, 2026 5:16 PM

**Mark** wrote:
> And @Torlando, if you're reading this and there's anything additional I can do here to get this running smoothly, let me know. It's possible that we could add a memory-optimized mode/flag, that changes parts of the core behaviour towards a much more aggressively memory-optimized profile.
> 
> There's several instances of low-hanging fruit, where this could be applied quite effectively, I think. Especially now with the new DB-backed storage backend, and for a client application, almost everything can be kept out of live memory.
> 
> It's always a balance with these things though, since a when you *do* have the memory available, you want to actually use it constructively, which is very much needed on transport nodes, and such.
> 
> But there's a very good possibility we can squeeze this down *a lot* more by some simple tweaks with a dedicated, memory-optimized mode.
> 
> And jeez, 50MB of memory as a hard-kill limit. That's *harsh* man.

Thanks Mark! As K8 mentioned, incoming resources are something to look at. Not sure if it could be written to disk and freed per packet or something but receiving a ~30MB attachment indeed gets it killed (I haven't tested thoroughly to find the maximum file size that works, but I figure this will depend on whether the user is connected to a busy TCP server anyway). I do think a low memory mode would be useful regardless.

**123321** wrote:
> The way Columba is using the VPN extension is a workaround that Apple won't approve in the App Store. This is not to say it is wrong, or that we should be catering to Apple's rules and monopoly, but it is something to consider.
> 
> I say this because, if the purpose is to build it with the idea that it can never escape TestFlight or local builds, then I think Apple offers better extensions and workarounds that can be used which won't be so limiting to just 50MB.
> 
> And of course if the plan is to eventually escape TestFlight, before putting too much time or thought into the workaround, perhaps consider the likelihood of Apple allowing it under how it works now, and their written policies.
> 
> Hopefully this is all known, though.

I have tried several different approaches and the Network Extension seems to be the least-bad way to get it working. The LLMs also tell me Apple might not approve it since their wording is a bit contradictory, but as K8 said I'm hoping the existence of Orbot is enough of a precedent. If not, well... iOS may have to go through a similar route as Meshtastic by requiring an external device paired on bluetooth to act as a transport node. I do have a toggle in the app that switches the RNS runtime to be entirely in-app. This is much less ideal for a lot of reasons, and can get the user blocked by the default Backbone fast flapping settings pretty easily. I do have both of the blueteooth background modes enabled, so it may be the case that simply having an RNode connected will keep the app's RNS instance alive indefinitely, but these things take a lot of experimentation, trial, and error to find something that works. There's also a scheduled background job that will sync from propagation nodes on a shorter-than-usually-recommended timer to get around the fact that if RNS lives in-app it won't reliably be online to get messages directly. All of that becomes unnecessary if the Network Extension runs RNS though. 

Anyway, @123321 definitely don't assume that I know of a better extension for this, because I don't :) This is my first iOS app and my daily driver is android.

---
