From: "Jorge Timón" <jtimon@monetize.io>
To: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP - Hash Locked Transaction
Date: Sat, 26 Apr 2014 13:11:37 +0200 [thread overview]
Message-ID: <CAC1+kJMJOB+OSkL1ZZ_DpGBnYoNPVX7eNR_=adqF6rMaM-LKSA@mail.gmail.com> (raw)
In-Reply-To: <CAE-z3OUM6_+qtxzcLg1FkUe8jxCLnJDya=eH9O5+LY_KRrhZpg@mail.gmail.com>
Does it make sense to implement a generic Policy interface (abstract
class) which StandardPolicy extends?
Maybe you can then implement a WhitelistPolicy,
ReplacebyFeeStandardPolicy, ReplacebyFeeWhitelistPolicy...
This would make it simpler for miners to implement their own policies
in general.
The following functions (maybe more) could become methods of Policy:
script IsStandard
main IsStandardTx
main AcceptToMemoryPool
next prev parent reply other threads:[~2014-04-26 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 18:49 [Bitcoin-development] BIP - Hash Locked Transaction Tier Nolan
2014-04-25 19:18 ` Luke-Jr
2014-04-25 19:37 ` Tier Nolan
2014-04-25 20:06 ` Alex Mizrahi
2014-04-25 20:14 ` Peter Todd
2014-04-25 20:19 ` Gregory Maxwell
2014-04-25 21:14 ` Peter Todd
2014-04-25 21:52 ` Tier Nolan
2014-04-26 11:11 ` Jorge Timón [this message]
2014-04-26 11:31 ` Tier Nolan
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='CAC1+kJMJOB+OSkL1ZZ_DpGBnYoNPVX7eNR_=adqF6rMaM-LKSA@mail.gmail.com' \
--to=jtimon@monetize.io \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=tier.nolan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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