-
I've just run across the bug here #2059, which alerted me to there being ethereum / block chain code inside crossbar and autobahn. I searched around for some documentation on this and couldn't find any. I can't think of any way that ethereum would be related to WAMP (my first reaction was that someone snuck a miner into the code somehow). Can someone enlighten me? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
sure! here is an example. imagine
all 3 are independent actors. to establish trust relations for above scenario, they need a common trust anchor. and to do that without 2 of them relying on the 3rd or any other centralized party they can use a programmable blockchain: Ethereum the code in autobahn/crossbar already goes a long way, but is still experimental, as there are yet unsolved questions, the most important one: with Ethereum integration, Alice, Bob and Joe can establish trust relations in non-centralized fashion, but why would they want to? Alice has the need for a routing realm, because she supposedly has a need for her application. But why would Bob and Joe have a motivation to provide their routing services to Alice's realm? IOW: besides the trust relations, what about economic relations? |
Beta Was this translation helpful? Give feedback.
-
Yes, you are on the right track! Mastodon or generally federated systems are a good category of systems to compare this experimental feature to. However, it goes quite a bit further. To begin with, there is a distinction made between "operationally dependent on" and "trust wrt to some function". And continuing my example with Alice, Joe and Bob:
and so on, I guess you get the idea. Next, rgd "performance": all of above is essentially providing information to configure WAMP routing nodes, as eg Crossbar.io contains in its node key and node config file - but in a decentralized database (Ethereum). Thus, there is no performance impact at the messaging level. Finally, the experimental code goes beyond in yet another way: it provides end-to-end encrypted application traffic. That is, WAMP client connecting to Alice's realm communicate in a privacy preserving manner without even Bob or Joe able to read. This feature is a mini-world to explain .. so unless you really want to know .. I'm skipping this for now;) |
Beta Was this translation helpful? Give feedback.
-
So for completeness, here is the list of actors in my example:
Alice wants to control her realm, but doesn't want to host routing services, and doesn't want to depend on a centralized party (only on Bob or only on Joe). Carol and Homer trust Alice, but do not want to operationally depend on Bob only or on Joe only. Carol and Homer want to use WAMP routing to have their apps in Alice's realm talk to each other, but they do not want anyone other to read or modify that app traffic (this includes the WAMP router nodes!). And so on .. |
Beta Was this translation helpful? Give feedback.
Yes, you are on the right track! Mastodon or generally federated systems are a good category of systems to compare this experimental feature to. However, it goes quite a bit further.
To begin with, there is a distinction made between "operationally dependent on" and "trust wrt to some function". And continuing my example with Alice, Joe and Bob: