From: Alistair Mann <al@pectw•net>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Pre BIP: Solving for spam and other abuse with an HTLB
Date: Sun, 17 Mar 2019 20:27:35 +0000 [thread overview]
Message-ID: <2800869.rK7t1eu9ik@dprfs-d5766> (raw)
In-Reply-To: <12139028.TiJ4v5RR02@dprfs-d5766>
This update collects community feedback on my HTLB Pre-BIP
As reminder, I'm suggesting a BIP for a hitherto poorly supported class of
transactions: "Good Behaviour Bonds".
1. On this mailing list:
ZmnSCPxj notes HTLB over HTLC can improve privacy by obscuring whether a
transaction is, in fact, an HTLB or an HTLC. This requires that the
'redundant' <digest> and [HASHOP] be not standardised. I intend to follow that
advice.
2. On Reddit at http://tinyurl.com/yxdketdo:
/u/almkglor nudges me to consider if Bob could immediately fail the HTLB to
Alice's benefit. I believe he could with something like this script:
OP_IF
OP_DUP OP_HASH160 <seller pubkey hash>
OP_ELSE
OP_IF
[HASHOP] <digest> OP_EQUALVERIFY OP_DUP OP_HASH160 <buyer pubkey hash>
OP_ELSE
<num> [TIMEOUTOP] OP_DROP OP_DUP OP_HASH160 <buyer pubkey hash>
OP_ENDIF
OP_ENDIF
OP_EQUALVERIFY
OP_CHECKSIG
The second OP_IF is new and would mean Bob can give Alice a [HASHOP] and
<digest> that allows her to immediately redeem the funds. I will be modifying
the proof-of-concept code to investigate and prove this change.
At https://twitter.com/ChristopherA/status/1105153022206722048
3. @mappum observes the HTLB idea is "like proof-of-stake". Such a succint
comparison of HTLB with existing work is useful to me even though HTLB has
nothing to do with mining and PoS consensus. I'll be investigating if the PoS
penalty system has more that can inform this BIP.
I'm grateful to the above for their contributions, and also to the circa 60+
non-bot visitors to the berewic.com site: quiet interest is positive.
Assuming no other major changes my next update will be a formal write-up for
the BIP.
Cheers,
--
Alistair Mann
next prev parent reply other threads:[~2019-03-17 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 16:01 Alistair Mann
2019-03-12 4:14 ` ZmnSCPxj
2019-03-17 16:11 ` Alistair Mann
2019-03-18 4:22 ` ZmnSCPxj
2019-03-17 20:27 ` Alistair Mann [this message]
2019-03-19 0:22 ` ZmnSCPxj
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=2800869.rK7t1eu9ik@dprfs-d5766 \
--to=al@pectw$(echo .)net \
--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