From: "bitcoin-dev-ml.void867 via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] A Fool's Errand or should I try?
Date: Mon, 6 May 2024 10:09:14 +0200 [thread overview]
Message-ID: <171498296705.6.12161480431860578333.324011415@slmail.me> (raw)
In-Reply-To: <75628135-32ae-4df3-be52-9f7d054bc096n@googlegroups.com>
Are you aware of getrawtransaction verbosity=2? Refer to
https://bitcoincore.org/en/doc/27.0.0/rpc/rawtransactions/getrawtransaction/
for the RPC documentation.
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/171498296705.6.12161480431860578333.324011415%40slmail.me.
next prev parent reply other threads:[~2024-05-06 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 15:00 Fractal Encrypt
2024-05-05 11:55 ` [bitcoindev] " Ali Sherief
2024-05-05 15:03 ` Fractal Encrypt
2024-05-06 8:09 ` bitcoin-dev-ml.void867 via Bitcoin Development Mailing List [this message]
2024-05-06 23:51 ` [bitcoindev] " Fractal Encrypt
2024-05-07 5:15 ` bitcoin-dev-ml.void867 via Bitcoin Development Mailing List
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=171498296705.6.12161480431860578333.324011415@slmail.me \
--to=bitcoindev@googlegroups.com \
--cc=bitcoin-dev-ml.void867@slmail$(echo .)me \
/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