2 computers on the same (NAT enabled) LAN, both running nodes and wallets, both running over TOR.
Question: If someone sends grin over TOR to one of my 2 wallets should it land in the correct wallet without issue, or will the second wallet on the same IP cause issues? Thanks
From my past experience with 2 syncing nodes from same IP I got a ban at p2p server, could not get any peer from any seed after.
thanks for the reply
/me shuts one down
For your second node, just set peers_allow to the first node’s LAN IP in grin-server.toml. Then you’ll only sync from the first node, and only appear as one peer further downstream.
Got it.
Using this method a person (peer) could have several wallets running (talking on TOR) but sharing the same WAN (IPV4) IP?
[IIRC there exists at least one service which hosts nodes, or something to this effect, so that therefore running many wallets on 1 IP should be doable I suppose, right?]
I don’t know if it’d work with the same wallet since the listener address is deterministically generated and that could confuse the TOR routing?
If you have different wallets it definitely would though, and they could even share the same node if you run the node with the API listener enabled and the wallets using the remote node flag.
Yup this, and thanks - that config setting makes sense - and in hindsight the idea Grin addresses would be limited to connection by available IPV4 space (less so IPv6 but still) is loco
I think this only further illustrates the problems with tor transactions. With slate packs of course the recipient can just open the wallet they intend to receive the transaction on. Operating multiple wallets simultaneously may not be possible with current clients but should have no technical limitation preventing it from being possible in the future.
Tor is a bit overhead and you need to stay online, I suggested an idea for GRIN storage to share Slatepack with receiver, you just need to lock/burn GRIN and get space in the Cloud, DDoS protection is total amount of GRIN. This is like IPFS or SBBS analogue in Beam near GRIN node, this storage can have post-quantum encryption, need to think about price/size, I suggested something like 1 grin - 100kb. We need to find ways to lock/burn grin at this case.
Assuming that two users who are using grin wallet (with embedded node) in same network, one will be banned? It looks weird for a payment app.
im assuming his comment referred to the p2p mining pool. i’m also assuming there is no technical limitation preventing this. not sure how IPV6 plays with tor, but even without this i’d have thought a NAT + uPNP enabled LAN should support multiple tor enabled grin wallets
i tested grin node with ipv6 only. It can’t find any peers, I suppose we’re not supporting ipv6 yet.