From: George Burke <gb@geoburke•com>
To: Richard Greaser <thebitcoinbugle@gmail•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] HODL Tax Proposal
Date: Thu, 1 Aug 2024 16:38:11 -0700 [thread overview]
Message-ID: <CAHYx7Bu9SfTgmLoPJ-7v=rY+C9pS4p4gO3e7gqKurwRuij8ouA@mail.gmail.com> (raw)
In-Reply-To: <6512db18-bd15-462e-92fd-7549b5e885e7n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 2424 bytes --]
A tax on property already owned is something I'm fundamentally against.
Being charged for lack of usage erodes our concept of property ownership,
especially when usage itself sufficiently subsidizes the network. The
"network tax" was already paid on the acquisition of the asset by the
sender, and another network tax will be paid by the current owner upon
every subsequent sale or self-transfer.
My perspective: HODLers are indeed providing a valuable service to the
longevity and growth of network value. They're providing scarcity.
--
*George Burke *
*Co-founder, Portal <https://portaldefi.com/> *
Silicon Valley Bitcoin <https://svbtc.org/>, Organizer
Co-founder, FounderPool <https://founderpool.co/>
San Juan, PR / San Francisco, CA
Keybase <https://keybase.io/geoburke> || OneName
<https://onename.com/geoburke>
*For security, encrypt with my PGP key <https://onename.com/geoburke>*
On Thu, Aug 1, 2024 at 2:13 PM Richard Greaser <thebitcoinbugle@gmail•com>
wrote:
> 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
> <https://groups.google.com/d/msgid/bitcoindev/6512db18-bd15-462e-92fd-7549b5e885e7n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
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/CAHYx7Bu9SfTgmLoPJ-7v%3DrY%2BC9pS4p4gO3e7gqKurwRuij8ouA%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 4337 bytes --]
next prev parent reply other threads:[~2024-08-02 0:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 21:03 Richard Greaser
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 [this message]
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='CAHYx7Bu9SfTgmLoPJ-7v=rY+C9pS4p4gO3e7gqKurwRuij8ouA@mail.gmail.com' \
--to=gb@geoburke$(echo .)com \
--cc=bitcoindev@googlegroups.com \
--cc=thebitcoinbugle@gmail$(echo .)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