After doing a couple of hours reverse engneering work, I am now 95% certain that this is connceted with a GOS update (prosumedly in June). That affected private spaces.
I'll cc Final (nprofile…yg8t)
I tested with three devices. The setup I was testing is InviziblePro + Monfluo & Cakewallet
LineageOS + InviziblePro - expected behaviour
GOS (without private spaces) + InviziblePro - expected behaviour
GOS (with) private spaces + InviziblePro in both spaces - worked with Cakewallet and Monfluo each in both spaces up to the GOS update in June.
Since the GOS update .onion connections stopped working.
Back then I spotted some Tor (onion) connectivity issues in Cakewallet, but since that had been a common issue in the past I was not expecting GOS (private spaces) to be the issue.
Up to the update both Invizible instances created their own ("independent") connection.
Now doing some traffic analysis it seems they are somehow tied to each other with a parent - child relation. Which should result in a "Tor over Tor" situation that then breaks down. This affects only native .onion connections. Clearnet-Tor over InviziblePro is not affected.
After deinstalling the Monfluo app from private spaces, the Monfluo app in the main space starts to work as expected again connecting perfectly fine to .onion nodes.
The same applies to Cakewallet.
I will try to close down the private space completly and reopen anew as there was a third app that had a corrupted database after the GOS update. I will report back if that solves the problem or if something needs to be done on GOS side to have private spaces work again as before.
npub1ah…cl76e
2026-09-13 14:57:01 UTC
in reply to nevent1q…7ug0
Author Public Key
npub1ah3aj4mhfew4c7txfdd4paf3wr5syntkeyxenl9fxf9rejte2wpqwcl76eSeen on
wss://nos.lolPublished at
2026-09-13 14:57:01 UTCEvent JSON
{
"id": "4ff81aa71373476e93f44834b65eb7f534b9c92d853f9c53d37cc58107aa5ad2",
"pubkey": "ede3d957774e5d5c79664b5b50f53170e9024d76c90d99fca9324a3cc9795382",
"created_at": 1789311421,
"kind": 1,
"tags": [
[
"e",
"252c21dc61316556638924c7722382e5802b1073f6b26e75269ec8264bfc3aa5",
"wss://nostras.app/",
"root",
"ede3d957774e5d5c79664b5b50f53170e9024d76c90d99fca9324a3cc9795382"
],
[
"e",
"e9d2f5c0b6758c9655d5186c1288263254657cf3ca78723e4a94f59062b66d33",
"wss://relay.primal.net/",
"",
"ede3d957774e5d5c79664b5b50f53170e9024d76c90d99fca9324a3cc9795382"
],
[
"e",
"648d1f1e9552675086c03ee9d29f628c3943e0ba92d66311f2fc2dcd338dfeca",
"wss://relay.primal.net/",
"",
"465eb13404d7219cd91c2b4a8a7e308ad4e09bc1298dc08c5eec852e9bf5da09"
],
[
"e",
"a60a040c51d4f31f015628263cd2a0c03e4290873fcf49b29b411d6b13ebed8d",
"wss://relay.primal.net/",
"reply",
"ede3d957774e5d5c79664b5b50f53170e9024d76c90d99fca9324a3cc9795382"
],
[
"p",
"ede3d957774e5d5c79664b5b50f53170e9024d76c90d99fca9324a3cc9795382",
"wss://nos.lol/"
],
[
"p",
"465eb13404d7219cd91c2b4a8a7e308ad4e09bc1298dc08c5eec852e9bf5da09",
"wss://nos.lol/"
],
[
"p",
"b98ded4ceaea20790dbcb3c31400692009d34c7f9927c286835a99b7481a5c22",
"wss://relay.primal.net/"
]
],
"content": "After doing a couple of hours reverse engneering work, I am now 95% certain that this is connceted with a GOS update (prosumedly in June). That affected private spaces.\n\nI'll cc nostr:nprofile1qqstnr0dfn4w5grepk7t8sc5qp5jqzwnf3lejf7zs6p44xdhfqd9cgspzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpz3mhxue69uhhyetvv9ukzcnvv5hx7un89uq35amnwvaz7tmedehhxarj9eukzetv9eshgtm5v9hxwmc8lyg8t\n\n\nI tested with three devices. The setup I was testing is InviziblePro + Monfluo \u0026 Cakewallet\n\nLineageOS + InviziblePro - expected behaviour\n\nGOS (without private spaces) + InviziblePro - expected behaviour\n\nGOS (with) private spaces + InviziblePro in both spaces - worked with Cakewallet and Monfluo each in both spaces up to the GOS update in June.\n\nSince the GOS update .onion connections stopped working.\n\nBack then I spotted some Tor (onion) connectivity issues in Cakewallet, but since that had been a common issue in the past I was not expecting GOS (private spaces) to be the issue.\n\nUp to the update both Invizible instances created their own (\"independent\") connection.\n\nNow doing some traffic analysis it seems they are somehow tied to each other with a parent - child relation. Which should result in a \"Tor over Tor\" situation that then breaks down. This affects only native .onion connections. Clearnet-Tor over InviziblePro is not affected.\n\n\nAfter deinstalling the Monfluo app from private spaces, the Monfluo app in the main space starts to work as expected again connecting perfectly fine to .onion nodes.\n\nThe same applies to Cakewallet.\n\nI will try to close down the private space completly and reopen anew as there was a third app that had a corrupted database after the GOS update. I will report back if that solves the problem or if something needs to be done on GOS side to have private spaces work again as before.",
"sig": "884f37937f3b9945c9e3b6fc578c12554139bf175683f841a34f777276553a0db07ca1d2c8a9f6d6e231c9d4f0a61f87166dad53be18875bcfd75d517ebd9eff"
}