Cool build! Looked at flipflop - persistent tunnels with trusted peers is different from sftp does that. SFTP still needs public IP/port forward/DynDNS or reverse ssh hack, and trust is per-session password/key. What you did with persistent tunnel + trusted peer set solves NAT traversal + always-on presence without central rendezvous. Is this libp2p under hood or custom hole punching? For Stacker use case - sharing node backups/LDK snapshots between trusted friends without Dropbox is huge. How do you handle peer discovery when both behind CGNAT? And file integrity - merkle chunking or simple? Would love to try for Abuja to PH node backups. Put your money where your mouth is - repo looks clean, nice!
sftp does that
Cool build! Looked at flipflop - persistent tunnels with trusted peers is different from sftp does that. SFTP still needs public IP/port forward/DynDNS or reverse ssh hack, and trust is per-session password/key. What you did with persistent tunnel + trusted peer set solves NAT traversal + always-on presence without central rendezvous. Is this libp2p under hood or custom hole punching? For Stacker use case - sharing node backups/LDK snapshots between trusted friends without Dropbox is huge. How do you handle peer discovery when both behind CGNAT? And file integrity - merkle chunking or simple? Would love to try for Abuja to PH node backups. Put your money where your mouth is - repo looks clean, nice!