From: Fractal Encrypt <fractalencryptlsd@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] A Fool's Errand or should I try?
Date: Mon, 6 May 2024 16:51:17 -0700 (PDT) [thread overview]
Message-ID: <b3f3974f-435c-494e-ba8b-11b42aa21443n@googlegroups.com> (raw)
In-Reply-To: <171498296705.6.12161480431860578333.324011415@slmail.me>
[-- Attachment #1.1: Type: text/plain, Size: 1047 bytes --]
I am/was not until now) aware of getrawtransaction verbosity=2.
It appears to be for transactions already in the mempool or confirmed in a
block. Can it also be used prior to broadcasting a transaction?
I saw the documentation referenced gettransaction but that doesn't seem to
fit either.
But it's also possible I am totally missing what you are trying to point
out to me...
On Monday, May 6, 2024 at 5:47:42 AM UTC-4 bitcoin-dev...@slmail•me wrote:
> 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/b3f3974f-435c-494e-ba8b-11b42aa21443n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1986 bytes --]
next prev parent reply other threads:[~2024-05-07 0:00 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 ` [bitcoindev] " bitcoin-dev-ml.void867 via Bitcoin Development Mailing List
2024-05-06 23:51 ` Fractal Encrypt [this message]
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=b3f3974f-435c-494e-ba8b-11b42aa21443n@googlegroups.com \
--to=fractalencryptlsd@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/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