preprint Open access

Griefing-Penalty: Countermeasure for Griefing Attack in Bitcoin-compatible PCNs.

  • arXiv (Cornell University)
  • Cornell University
Research footprint

At a glance

Citations
4
References
0
Comments
0
Paper overview

Öz

Payment Channel Networks or PCNs have gained prominence ensuring faster relaying of transactions. However, this Layer-two solution has its own fair share of problems. Topological analysis on Lightning Network reveals that Griefing Attack is a major problem whereby an adversary intentionally exhausts the channel capacity of the network. It can be used for mounting series of targeted attacks like Denial-of-Service Attack, Node Isolation Attack and Channel Exhaustion Attack on honest participants as well. Though the attack does not always result in a direct monetary gain of the attacker, blocking of channel capacity for several days prevented several nodes from processing any future transaction request, leading to substantial collateral damage. Certain portions of the payment channel network get stalled which hampers the throughput and utility of the network. Mitigating Griefing Attack still remains an open problem. In this paper, we propose an efficient countermeasure for the attack, known as Griefing-Penalty. Mounting such an attack requires the attacker to pay a penalty proportional to the collateral cost of executing a payment. The penalty is used for compensating parties who incurred loss by locking funds. Our proposed strategy works for any timelock based payment protocol and ensures faster resolution of payments. To illustrate it, we propose a new payment protocol HTLC-GP or Hashed Timelock Contract with Griefing-Penalty. It not only preserves privacy but also ensures that an attacker cannot ascribe blame on any honest intermediary present in the path relaying a payment.

Record transparency

Publication details

OpenAlex
W3028195733
Document type
preprint
Language
EN
Source
arXiv (Cornell University)
Last metadata update
Community

Comments

Oturum Açın to join the discussion.

  1. No comments yet. Start the discussion.