public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Richard Greaser <thebitcoinbugle@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] HODL Tax Proposal
Date: Thu, 1 Aug 2024 14:03:01 -0700 (PDT)	[thread overview]
Message-ID: <6512db18-bd15-462e-92fd-7549b5e885e7n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 811 bytes --]

Hi everyone, 

It has become apparent to me that there is an issue where users of the 
network holding their coins, are not adding value to the network. 

As miners continue to get squeezed post halving, they would benefit 
tremendously from fees being taken from individuals refusing to move their 
coins, providing increased security to the network. 

I have written out a proposal more in depth and is attached below. 

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/6512db18-bd15-462e-92fd-7549b5e885e7n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1131 bytes --]

[-- Attachment #2: hodltax.md --]
[-- Type: text/markdown, Size: 4779 bytes --]

Richard Greaser Proposes BIP 432: HODL TAX
==========================================

BIP: 432   
Layer: Consensus (Hard Fork)  
  Title: HODL Tax  
  Author: Richard Greaser [thebitcoinbugle@protonmail.com.com](mailto:thebitcoinbugle@protonmail•com.com)  
  Comments-Summary: No Comments Yet   
  Status: Draft  
  Type: Informational  
  Created: 2024-07-31  
  License: BSD-3-Clause  
  Post History: None but I’m a credentialed journalist

### Abstract

This Bitcoin Improvement Proposal (BIP) suggests implementing an inactivity fee for Bitcoin addresses that do not engage in any outgoing transactions for over 60 days. The collected fees would be distributed to miners, incentivizing network security and promoting more active participation from Bitcoin holders.

### Motivation

The primary motivation behind this proposal is to encourage Bitcoin holders to engage actively with the network, thus promoting decentralization and security. This is also a response to Michael Saylor and PODCONF's attempts to limit Bitcoin to being a corporate treasury asset with Coinbase being a chief custodian. Currently, a significant portion of Bitcoin remains idle, potentially contributing to reduced network liquidity and less frequent fee contributions to miners. Udi is currently failing to sufficiently supplement miner incomes and thus action needs to be taken before Peter Todd's suggestion of tail emissions get any serious momentum. By introducing an inactivity fee, this proposal aims to:

1.  Encourage users to engage in the network instead of being rent seeking full time podcast listeners.
2.  Provide an additional revenue stream for miners, thus supporting network security and more Bitaxe circulation.
3.  Discourage the hoarding of coins without contributing to the network's operation.

### Specification

**Inactivity Fee Mechanism:**

1.  **Inactivity Period:** An address will be considered inactive if no outgoing transactions are detected for over 60 days.
2.  **Fee Calculation:** The inactivity fee will be a small percentage of the total balance of the inactive address. A proposed rate is 0.1% of the address balance per inactivity period.
3.  **Fee Collection:** The fee will be automatically deducted from the address at the end of each inactivity period and added to the mining reward pool of the next block.
4.  **Distribution to Miners:** The collected fees will be distributed to miners proportionally, based on the computational work contributed to mining the block.

**Implementation Considerations:**

1.  **Threshold and Rate Adjustments:** The inactivity threshold and fee rate can be adjusted based on community feedback and network conditions.
2.  **Exemptions:** Certain addresses, such as those holding funds for legal or institutional purposes, may be exempt from this fee, subject to criteria defined by the community.
3.  **Technical Challenges:** Implementation will require modifications to the Bitcoin protocol, particularly in how addresses and their activity are tracked.
4.  **Proper Permission:** We must also consult the President of Bitcoin, Dennis Porter, as well as FINCEN and other relevant agencies in order to remain compliant.

### Rationale

This proposal seeks to balance the need for increased network activity and miner incentives with the freedom of users to hold their assets without interference. The chosen fee rate and inactivity period aim to be minimal enough to avoid significant financial impact while still encouraging active participation. The HODL meme stands in stark contrast with Satoshi's original goal of Bitcoin acting as Peer to Peer cash.

### Backward Compatibility

This proposal introduces new rules that affect address balances, but does not impact the core transaction mechanisms of Bitcoin. However, it requires changes to the Bitcoin protocol and wallet software to track inactivity and implement fee deductions. Like Paul Sztorc's previous proposals, this one has zero negative trade offs.

### Security Considerations

Ensuring the security of the fee deduction process is crucial. It is vital to prevent unauthorized deductions and ensure that the fee mechanism does not introduce new vulnerabilities to the network. While individuals will likely question whether or not this change will cause issues to the network and change game theory, the more important security consideration is the negative impacts that will be caused for not adopting it.

### Conclusion

The proposed inactivity fee aims to enhance Bitcoin network security and activity by incentivizing regular transactions. Community feedback and further analysis are essential to refine this proposal and assess its potential impact on the network and users.

             reply	other threads:[~2024-08-01 21:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01 21:03 Richard Greaser [this message]
2024-08-01 21:59 ` José Edil Guimarães de Medeiros
2024-08-02  0:28   ` Keagan McClelland
2024-08-02  1:19     ` Jimmy Song
2024-08-02  2:03       ` George Burke
2024-08-02  5:08       ` 'hashnoncemessage' via Bitcoin Development Mailing List
2024-08-01 23:38 ` George Burke
2024-08-02  0:12 ` Keagan McClelland
2024-08-02  8:45 ` [bitcoindev] " Garlo Nicon
2024-08-01 21:55 [bitcoindev] " Christian Riley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6512db18-bd15-462e-92fd-7549b5e885e7n@googlegroups.com \
    --to=thebitcoinbugle@gmail$(echo .)com \
    --cc=bitcoindev@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox