Yeah. I'll gladly rename it so there's less confusion.
The way I handled the NIP is that it is still primarily Nostr, but I specified a deterministic way to encode the Nostr event into MeshCore packet and back - in a way that the Nostr event is fully reconstructed, including the valid signature.
Basically keep only the most precise geohash (although we include less precise for easy queriability), etc. The goal is to be able to pack everything into as small packet as possible, but also be able to unwrap it back into original Nostr event.
Do you have a specification of events that you use? We might do it the other way around - if it is possible, we can use your event type and I can devise a way to compress it into meshcore packets. And I'll change my apps to use your event type. My app has no users, it's a demo at this point, so I'm totally OK with continuing with yours, if we can keep this property and extend it to MeshCore.
My app is also primary Nostr, MeshCore is not yet implemented (I need a bit of work on MeshCore side as well, so it is user friendly - currently you can connect only one MeshCore app to a node, so we need a MeshCore app that can take and send events from other apps, so users don't have to choose "now I'm driving, I am opening app X, now I want to chat, I am opening app Y"). But I'll solve that part easily.
Juraj / Juraj🏴💛🌘
npub1m2…lr8p9
2026-10-11 20:37:02 UTC
in reply to nevent1q…7fdk
Author Public Key
npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9Seen on
wss://nostr.cypherpunk.todayPublished at
2026-10-11 20:37:02 UTCEvent JSON
{
"id": "f83b77dbb5d6d0707dbd2e8b6109b576d31c589b19c7f100e6d75e3d825a39ea",
"pubkey": "dab6c6065c439b9bafb0b0f1ff5a0c68273bce5c1959a4158ad6a70851f507b6",
"created_at": 1791751022,
"kind": 1,
"tags": [
[
"e",
"7b37f599dafda58358e2463f460d14336fcec62c3fb51b5e93184f015ea722ff",
"",
"root"
],
[
"e",
"f0b7a75622734a28577803fbf73370b2dc95ddabb1ece4f578e2be0bc1f22225",
"",
"reply"
],
[
"p",
"dab6c6065c439b9bafb0b0f1ff5a0c68273bce5c1959a4158ad6a70851f507b6"
],
[
"p",
"c392b7b76b7510b75f7ca0d493a64173ff44bdfaca2074efeb6e232198d80e74"
],
[
"p",
"648c0f5302c75f38382a4d2c85a482b927cc61b2828a0794e36c6cc796de86a6"
],
[
"r",
"wss://relay.primal.net/"
],
[
"r",
"wss://nostr.cypherpunk.today/"
],
[
"r",
"wss://relay.damus.io/"
],
[
"client",
"Primal Web"
]
],
"content": "Yeah. I'll gladly rename it so there's less confusion.\n\nThe way I handled the NIP is that it is still primarily Nostr, but I specified a deterministic way to encode the Nostr event into MeshCore packet and back - in a way that the Nostr event is fully reconstructed, including the valid signature.\n\nBasically keep only the most precise geohash (although we include less precise for easy queriability), etc. The goal is to be able to pack everything into as small packet as possible, but also be able to unwrap it back into original Nostr event.\n\nDo you have a specification of events that you use? We might do it the other way around - if it is possible, we can use your event type and I can devise a way to compress it into meshcore packets. And I'll change my apps to use your event type. My app has no users, it's a demo at this point, so I'm totally OK with continuing with yours, if we can keep this property and extend it to MeshCore.\n\nMy app is also primary Nostr, MeshCore is not yet implemented (I need a bit of work on MeshCore side as well, so it is user friendly - currently you can connect only one MeshCore app to a node, so we need a MeshCore app that can take and send events from other apps, so users don't have to choose \"now I'm driving, I am opening app X, now I want to chat, I am opening app Y\"). But I'll solve that part easily.",
"sig": "81d70640abc2bf815df8d6526ded12b885e1f0c55ee02b0df152b9f2f9199b00fb29525bfa6c7467b5580f99c3a1a3c4cd7dd1a8de1b793c783d262999fdae4f"
}