{"id":11660,"date":"2022-10-28T06:50:25","date_gmt":"2022-10-28T06:50:25","guid":{"rendered":"https:\/\/coingrafter.com\/index.php\/2022\/10\/28\/lightning-analytics-firm-amboss-unveils-data-sharing-feature-the-end-of-privacy\/"},"modified":"2022-10-28T06:50:26","modified_gmt":"2022-10-28T06:50:26","slug":"lightning-analytics-firm-amboss-unveils-data-sharing-feature-the-end-of-privacy","status":"publish","type":"post","link":"https:\/\/coingrafter.com\/index.php\/2022\/10\/28\/lightning-analytics-firm-amboss-unveils-data-sharing-feature-the-end-of-privacy\/","title":{"rendered":"Lightning Analytics Firm Amboss Unveils Data Sharing Feature. The End Of Privacy?"},"content":{"rendered":"

[ad_1]
\n<\/p>\n

\n

Is this new Amboss function as harmful because it seems? The analytics firm unveiled \u201cReported Channel Balances\u201d and the bitcoin world instantly reacted with extreme criticism. Were they overreacting or did they’ve some extent? Is bitcoin\u2019s Lightning Network in danger? Let\u2019s research precisely what occurred and discover out. It all begins with the notion {that a} node\u2019s capability just isn’t the identical as a node\u2019s liquidity.\u00a0<\/span><\/p>\n

\n

We’ve additionally given node operators the flexibility to share and analyze their node standing, together with channel balances. This will permit us to ship higher insights, notifications, and valuations for bought channels. pic.twitter.com\/YgJmxFokS8<\/a><\/p>\n

\u2014 AMBOSS \ud83d\udd33 \ud83d\udc7e (@ambosstech) October 26, 2022<\/a><\/p>\n<\/blockquote>\n

In <\/span>the medium post announcing<\/span><\/a> the \u201cReported Channel Balances\u201d function, Amboss expands on the concept:\u00a0<\/span><\/p>\n

\n

\u201cOne major piece of information that has been missing since the beginning of the lightning network is the difference between lightning\u2019s capacity and its liquidity. To find the difference, we need a piece of information that (thankfully) is private by default: channel balances.\u201d<\/span><\/p>\n<\/blockquote>\n

Since that\u2019s nonetheless a key piece of data, many actors discover out channel balances through the use of the probing approach, \u201cwhich is an attempted payment designed to fail, reveals private information about channel balances without consent. It is, in a way, an attack on the privacy of nodes.\u201d So, Amboss is aware of that the Lightning Network\u2019s privateness is at stake. The sender\u2019s funds are additionally a stake, since they \u201cmay get locked, temporarily.\u201d And it\u2019s even worst for the goal.<\/span><\/p>\n

Amboss\u2019 Idea: Reported Channel Balances<\/span><\/h2>\n

So, to part out probing, Amboss enabled a manner for nodes to voluntarily report their balances. \u201cwe\u2019ve created a single endpoint that users can send this data to and it will be displayed on the node\u2019s Amboss page.\u201d There\u2019s the potential for sharing the information simply with Amboss, however nodes can go public with their data if they need. \u201cThe settings span from Private (shared only to Amboss), Range (balance shown publicly as 25%, 50%, or 75%), or Public (the specific percentage is shown to Amboss visitors).\u201d<\/span><\/p>\n

In common, the concept behind the function appears slightly naive, and nowhere is that extra evident than in the way in which they\u2019ll deal with mendacity nodes. \u201cIn truth, anyone can write a script to lie about their balances. Instead of trying to rout out the liars from our data set, we\u2019ll try a different approach: deliver services based solely on the information we\u2019re told.\u201d The Amboss individuals took \u201ckill them with kindness\u201d to a brand new stage.<\/span><\/p>\n

\n

\u201cWe\u2019re building tools to help node operators whether it be through providing notifications and alerts or through providing insights that help users make good decisions with their nodes. The best way that we can help is if users are sharing their balances honestly.\u201d<\/span><\/p>\n<\/blockquote>\n

So, the inducement to be sincere is the precious data that Amboss provides you with? Sounds frail.\u00a0<\/span><\/p>\n

\"BTCUSD<\/p>\n

BTC value chart for 10\/28\/2022 on Kraken | Source: BTC\/USD on TradingView.com<\/a><\/pre>\n
The Case Against Reporting Channel Balances<\/span><\/h2>\n
Lightning developer Openoms, whose twitter bio says \u201cBuilding nodes for Security, Privacy and Freedom,\u201d lead the cost in opposition to Amboss\u2019 new self-policing function. \u201cIf this data sharing and aggregation by Amboss gets widespread and accurate we\u2019ll have a huge problem with Lightning privacy.\u201d He additionally supplied options, doable guidelines, and a transparent plan of action. \u201cGood it is open-source, let\u2019s make it not possible to share more than 2 bits of data.\u201d<\/span><\/p>\n
\n
Some mitigations for now:
cannot actually inform if somebody is sharing privately, nonetheless:
* do not peer with sharing nodes
* keep away from paying via sharing nodes
* look out for CLN friends who cannot run Thunderhub
* feed it random information if something
* use aggressive MPP and longer routes<\/p>\n
\u2014 openoms (@openoms) October 27, 2022<\/a><\/p>\n<\/blockquote>\n
Openoms additionally breaks the already frail logic behind the function and poses that as an alternative of constructing \u201cdata sharing the norm because probing is already possible\u201d we must always \u201cmake probing more difficult, expensive and inconclusive.\u201d As for the actionable gadgets, Openoms affords \u201csome mitigations for now:\u201d<\/span><\/p>\n