You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user connected to a federated grinbox relay, I want my true public key to be to be obfuscated as it's passed to other relays, so that other relays cannot associate certain interactions on their servers with my address specifically.
This improves privacy. Suppose there are two relays in operation, @relay-x.com and @relay-y.com. Relay X only needs to know to send a transaction to Relay Y, but does not need to know where exactly the transaction should be routed from there, only Relay Y needs to know this.
The text was updated successfully, but these errors were encountered:
I wonder if it'd be possible to implement a onion routing or garlic routing protocol into grinbox directly. This could turn it into a dedicated private communication network for grin. Though it's initial purpose would be for grin transactions, it could become a useful general purpose communication network in the future. The question is, can it effectively be done?
As a user connected to a federated grinbox relay, I want my true public key to be to be obfuscated as it's passed to other relays, so that other relays cannot associate certain interactions on their servers with my address specifically.
This improves privacy. Suppose there are two relays in operation,
@relay-x.com
and@relay-y.com
. Relay X only needs to know to send a transaction to Relay Y, but does not need to know where exactly the transaction should be routed from there, only Relay Y needs to know this.The text was updated successfully, but these errors were encountered: