From: Eric Lombrozo <elombrozo@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Adding callback hooks to the satoshi client
Date: Sat, 24 Mar 2012 01:41:25 -0700 [thread overview]
Message-ID: <CABr1YTcpoRT3k1Bqjz_m48RrDuGciD4nJmsE1RiGJ4g_2z22Ww@mail.gmail.com> (raw)
In-Reply-To: <CABr1YTd4+KES75cHqKSa0Gwz62nJnMVsTANVh_qzuSXqoYZAew@mail.gmail.com>
I'd also like to be able to get detailed information of message format
errors for debugging other nodes that connect to bitcoind. For
instance, if a transaction is rejected because the signature is
invalid, I want to know this. If it's because the amount is out of
range or because the output couldn't be connected, I want to know
this, too. I especially want to know if it was because the transaction
is claiming an output that has already been claimed by another
transaction.
For now, I've had to resort to sticking tracers and stubs into
bitcoind. It would be really nice to not only be able to write an
error log but to also let the connecting node know what went wrong.
Obviously these types of messages should *not* be part of the bitcoin
protocol itself since it invites all kinds of attacks. But it would be
wonderful to have a side channel for this type of data, and it could
also be done using callbacks.
The callback mechanism could be configurable in a similar fashion to
the RPC in the bitcoin.conf file.
-Eric Lombrozo
prev parent reply other threads:[~2012-03-24 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 5:13 Eric Lombrozo
2012-03-22 5:24 ` Matt Corallo
2012-03-22 5:39 ` bitcoin-list
2012-03-22 9:56 ` Michael Grønager
2012-03-22 14:00 ` Luke-Jr
2012-03-22 15:23 ` Eric Lombrozo
2012-03-24 8:41 ` Eric Lombrozo [this message]
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=CABr1YTcpoRT3k1Bqjz_m48RrDuGciD4nJmsE1RiGJ4g_2z22Ww@mail.gmail.com \
--to=elombrozo@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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