From: Joost Jager <joost.jager@gmail•com>
To: alicexbt <alicexbt@protonmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Transaction Relay over Nostr
Date: Tue, 23 May 2023 17:26:18 +0200 [thread overview]
Message-ID: <CAJBJmV9sCCtyWS=yXuj9uG15t+d+hCcB-CrkNXL-Tk1UdaXVFg@mail.gmail.com> (raw)
In-Reply-To: <FVGoJA8LiudZ3BF2LRmy1w2tF-8IpZDKA49w56skRoerZ96j-qkxw-DUjSxZ3m-APMI_V-Wojn-rD3juO3IcBYRNAh9JwKFlyDWz3vwERS0=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
Hi fd0,
> - Transactions could be encrypted when published as nostr events initially
> except size, fee rate and offer. This can be used by different clients to
> show them as external mempool with transactions sorted by fee rate without
> affecting privacy of users.
>
I don't think this will work because those encrypted transactions could all
be fake and distort the view clients have on this 'mempool'?
> - Mining pools will be incentivized to include these transaction in their
> blocks if they are using a higher fee rate compared to transactions in
> normal mempool used by bitcoin nodes or there is a mechanism to accept
> published offers, NIP4 is used to privately coordinate everything between
> user and pool. User can lock some sats in a 2of2 multisig and release it to
> mining pool on confirmation.
>
I believe you are suggesting out-of-band payment in case the fee included
in the transaction itself is insufficient and CPFP/RBF is impossible or
impractical? The question is why would the miner trust you to indeed
release after confirmation? The 2-of-2 presumably has a clawback clause
with a timeout that could be used by the user to avoid paying.
Joost
[-- Attachment #2: Type: text/html, Size: 1610 bytes --]
next prev parent reply other threads:[~2023-05-23 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 7:19 Joost Jager
2023-05-23 13:25 ` alicexbt
2023-05-23 15:26 ` Joost Jager [this message]
2023-05-28 2:37 ` David A. Harding
2023-05-30 12:30 ` Joost Jager
2023-05-30 13:30 ` Greg Sanders
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='CAJBJmV9sCCtyWS=yXuj9uG15t+d+hCcB-CrkNXL-Tk1UdaXVFg@mail.gmail.com' \
--to=joost.jager@gmail$(echo .)com \
--cc=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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