From: alicexbt <alicexbt@protonmail•com>
To: Aaradhya Chauhan <chauhanansh.me@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Regarding setting a lower minrelaytxfee
Date: Tue, 26 Jul 2022 12:19:32 +0000 [thread overview]
Message-ID: <Ue6CCWgdkGc1VPF4yAP252kg3h-6U6xCZZ7hs9w6vDM7LBWsAaksRkLIpkrE39HLmI35Fu3cHC3-WA8Q9Ij3Z7YhAqzJbkytBqU9ZbfruB0=@protonmail.com> (raw)
In-Reply-To: <CAGHFe1BXdTkPZn4r_KTxYoz0sqcMsV830dm5JTTFURxDezBnDQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
Hi Aaradhya,
> As it's not a consensus rule, I think it can be done easily, just needing support from full node operators
A few miners will need to use a lower minrelaytxfee for this to work. I don't think miners would want to lower their profits.
/dev/fd0
Sent with [Proton Mail](https://proton.me/) secure email.
------- Original Message -------
On Tuesday, July 26th, 2022 at 1:56 PM, Aaradhya Chauhan via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
I know this might be a sort of repetition for a previous question, but I do want to know from enthusiasts in this group that while Bitcoin was trading at much lower price in its early days, 1 sat/vB was a good dust protection measure. But now, I think it's a bit high for merely a dust protection measure, and should be lowered slightly. Even if not, it should be lowered to half when prices go double than today and keeps oscillating at that point. As it's not a consensus rule, I think it can be done easily, just needing support from full node operators. I support LN but I think transaction affordability should remain constant in the future. If I'm okay to wait in a queue, I should have the option for same affordability for minimum fees in the future as it is today. (Like we still have posts today while email still exists).
Awaiting your response.
Regards
Aaradhya Chauhan
[-- Attachment #2: Type: text/html, Size: 2443 bytes --]
next prev parent reply other threads:[~2022-07-26 12:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 8:26 Aaradhya Chauhan
2022-07-26 12:19 ` alicexbt [this message]
2022-07-26 14:27 ` Peter Todd
2022-07-26 19:14 ` alicexbt
2022-07-26 12:45 ` Peter Todd
2022-07-27 4:10 ` vjudeu
2022-07-27 11:50 ` Peter Todd
2022-07-27 12:18 ` vjudeu
2022-07-29 3:38 ` David A. Harding
2022-07-29 18:59 ` Aaradhya Chauhan
2022-07-30 7:55 ` Aaradhya Chauhan
2022-07-30 17:24 ` alicexbt
2022-08-01 10:30 ` Peter Todd
2022-08-01 13:19 ` aliashraf.btc At protonmail
2022-08-01 13:37 ` Peter Todd
2022-08-03 15:40 ` Aaradhya Chauhan
2022-08-03 17:07 ` vjudeu
2022-08-03 18:22 ` Aaradhya Chauhan
2022-08-04 1:21 ` Billy Tetrud
2022-07-30 10:20 ` Peter Todd
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='Ue6CCWgdkGc1VPF4yAP252kg3h-6U6xCZZ7hs9w6vDM7LBWsAaksRkLIpkrE39HLmI35Fu3cHC3-WA8Q9Ij3Z7YhAqzJbkytBqU9ZbfruB0=@protonmail.com' \
--to=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=chauhanansh.me@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