{"type":"rich","version":"1.0","title":"ZmnSCPxj [ARCHIVE] wrote","author_name":"ZmnSCPxj [ARCHIVE] (npub1g5…3ms3l)","author_url":"https://yabu.me/npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3l","provider_name":"njump","provider_url":"https://yabu.me","html":"📅 Original date posted:2019-01-02\n📝 Original message:\nGood morning CJP,\n\n\n\u003e This, and the rest of your proposal, sounds like a lot of trouble,\n\u003e while it hardly solves anything.\n\u003e\n\u003e RM can have its node surrounded by other nodes also controlled by\n\u003e itself. So it is possible that RM controls all nodes that can possibly\n\u003e fulfill the 'G' role, and thereby stop any evidence being generated\n\u003e against the RM node. If you then want to build evidence against the G\n\u003e nodes, you end up recursively involving every single Lightning node in\n\u003e trying to solve your problem. Maybe it is possible, but I'd like not to\n\u003e do that. I like to see the exchange function as a higher layer (layer\n\u003e 3) on top of the Lightning layer, and have each layer solve its own\n\u003e problems in a clean and elegant way. I prefer that nodes that aren't\n\u003e involved in exchanging assets don't need to deal with its complexities\n\u003e either.\n\nWhich is why I later say:\n\n\u003e \u003e Note that since the path from S to RM is selected by RM, though, S must serve as G, and every node in-between that is honestly not a sockpuppet of RM should be prepared to shut down their channels immediately in case of slow response from the next node.\n\nAssuming S is a payee, it has every incentive to follow this protocol.\n\nOf course, now OM needs to know G, and thus knows S, the payee, and now has the power to censor payments.\nHeavy sigh.\n\nFurther, if S is not a payee, but is secretly a sockpuppet of F who is setting up an American Call Option, S can simply not forward to RM until much later.\nHeavy sigh.\n\nRegards,\nZmnSCPxj"}