I'm developing (mostly for fun) a protocol on top of UDP to reliably connect peer-2-peer using udp hole punching and with encryption of transferred data.
The protocol use an identity system like #nostr (will work with nostr keys).
Each peer willing to be reachable should contact a third party called signaling server (better namings are welcome 😅) that will store his current endpoint and share it with other known signaling server (private networks are possible).
To maximize connection probability each peer should contact 2 or 3 signaling servers (more than 3 are not even needed) but one can be enough if you're not behind a nat.
When willing to connect with another, a peer have to ask a signaling server to coordinate the udp hole punch between the two.
One of the (probably many) downsides is that since the endpoint detection must be done by the signaling server, this can dox your ip, but with a vpn everything should be good enough (the same problem occur with nostr).
Also, you can create a small private web of signaling servers between you and your already trusted third parties, implementing a public keys whitelist and keeping secret the signaling server's endpoints.
As i said is mostly for fun, but if anybody could give an opinion/ask questions it could help me to learn new things.
#asknostr
Smaciu
npub1d5…qxpr6
2024-04-03 19:56:26
Author Public Key
npub1d57clc5wacyga7xyat2dkpzptedwza8ufucgr5p6hq5ecsrr5m8sjqxpr6Published at
2024-04-03 19:56:26Event JSON
{
"id": "c68479b2d310cccf8157727c1df4e142f98ce090348761672ea1740e2bea4ab4",
"pubkey": "6d3d8fe28eee088ef8c4ead4db04415e5ae174fc4f3081d03ab8299c4063a6cf",
"created_at": 1712174186,
"kind": 1,
"tags": [
[
"t",
"nostr"
],
[
"t",
"nostr"
],
[
"t",
"asknostr"
],
[
"t",
"asknostr"
]
],
"content": "I'm developing (mostly for fun) a protocol on top of UDP to reliably connect peer-2-peer using udp hole punching and with encryption of transferred data.\n\nThe protocol use an identity system like #nostr (will work with nostr keys).\n\nEach peer willing to be reachable should contact a third party called signaling server (better namings are welcome 😅) that will store his current endpoint and share it with other known signaling server (private networks are possible).\n\nTo maximize connection probability each peer should contact 2 or 3 signaling servers (more than 3 are not even needed) but one can be enough if you're not behind a nat.\n\nWhen willing to connect with another, a peer have to ask a signaling server to coordinate the udp hole punch between the two.\n\nOne of the (probably many) downsides is that since the endpoint detection must be done by the signaling server, this can dox your ip, but with a vpn everything should be good enough (the same problem occur with nostr).\n\nAlso, you can create a small private web of signaling servers between you and your already trusted third parties, implementing a public keys whitelist and keeping secret the signaling server's endpoints.\n\nAs i said is mostly for fun, but if anybody could give an opinion/ask questions it could help me to learn new things.\n\n#asknostr",
"sig": "aaf622dbedf5ef6cb86b81229a598e8a6e8b9d9c5353a7f8ac931d6bf814a49b1cf4efbfbd1a1374ef638775f24c22f0c15633a9fcb20f817ab08b39c01fa2cf"
}