Bitcoin Forum
June 17, 2024, 06:15:14 PM *
News: Voting for pizza day contest
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Altcoins penalizing double-spends  (Read 155 times)
alkan (OP)
Full Member
***
Offline Offline

Activity: 149
Merit: 103


View Profile
March 13, 2017, 09:57:58 PM
 #1

Long time ago, several users of this forum suggested to punish double-spends by burning the amount:
https://bitcointalk.org/index.php?topic=3168
https://bitcointalk.org/index.php?topic=3441.msg49447#msg49447
https://bitcointalk.org/index.php?topic=208167.20
https://bitcointalk.org/index.php?topic=54746.0

If a miner can come up with a new signed TX including an input already used as input in the previous block he can claim the input as an additional transaction fee.
The TX in the previous block becomes invalid!
Transactions that only changed the transaction fee must be excluded.

There are just two possible outcomes:
1) Merchant receives their money. Buyer payed merchant.
2) Merchant receives nothing. Miner receives payment. Buyer payed miner.
There is no penalty for the buyer but also no incentive. I think that should be enough.

This change makes single confirmation TXs less secure than now but removes the incentive to double spend. With the current system I don't see a use case for single confirmation TXs other than preventing double spends anyway. TXs with two or more confirmations are as secure as today.

A problem is that it is necessary to make 100% sure never to broadcast modified TXs (with the exception of increased fees).

Even Gavin Andresen played with the idea:
Again, it seems to me some rules that make attempted double-spends more costly to those who attempt to pull off double-spends might be a good idea.

Is there any altcoin out there that applies a penalty in case of double-spend attempts? Do you know of any research papers about the topic?
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!