i know how to engineer it, but it does require NIP-42 support on all hops, and ... well.. the client... so it would telescope just like Tor, you open to one, then once you get auth you use it to open to 2, and then to 3, and then you push your request through the chain
on my list of things to do in the future, but just putting it out there
also it would not go well to make it into a general trasport, unless your hops have full bandwidth accounting, and you would have to segregate your first, second and third hops by always paying them through the prior layer and it would require... haha... keysend/AMP to keep your location private
lots there in that but i'm just gonna focus on one hop because of the bandwidth benefits
yeah, not even talking about pseudonyms for the hops
i already wrote much of this stuff last year but without the extra layer of encoding it into events
also, making rendezvous paths for hidden relays is not a big extra step too...
i think if the traffic volume is low, and it's primarily for internal access and you don't have a concept of outbound routing it could be quite interesting project
i know i could build all the pieces but it would probably take me a year to get to a decent beta product, maybe less if i happen to be able to find some competent golang/bitcoin/lightning/nostr devs to work with me
