From: Fractal Encrypt <fractalencryptlsd@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Re: A Fool's Errand or should I try?
Date: Sun, 5 May 2024 08:03:39 -0700 (PDT) [thread overview]
Message-ID: <74ae96f5-4ea4-4afa-8321-e09e4ad9f97an@googlegroups.com> (raw)
In-Reply-To: <91d3be30-a672-4407-8d11-902df8ff4f54n@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 4227 bytes --]
Thanks Ali, I will investigate these avenues you've pointed out. Most
appreciated!
On Sunday, May 5, 2024 at 9:30:48 AM UTC-4 Ali Sherief wrote:
> Currently the only way you can fetch the previous input addresses and
> amounts is if you use the getblock RPC call with a verbosity of 3. This
> will obviously cause it to print a lot of raw transactions. But since
> decoderawtrasnsaction is independent of the blocks that are actually stored
> on your disk, you'd have to modify it to locate each input inside the
> blocks.dat folder, and then assemble an equivalent "prevout" structure as
> in getblock.
>
> There is also the issue of the txo not actually existing in the
> blockchain, which means that such a prevout structure would not exist in
> the first place.
>
> I think it would be better to create a separate RPC for this, maybe
> 'getfulltransaction' or something like that since gettransaction for
> in-walet txs already exists, to implement such functionality.
>
> -Ali
>
> On Saturday, May 4, 2024 at 3:40:24 PM UTC Fractal Encrypt wrote:
>
>> TLDR: I'd like to investigate the possibilities of extending
>> decoderawtransaction to include the fee (and maybe even sats per v/b).
>>
>> I'm hoping it will be a good project for me to work on and build at least
>> a tiny understanding of bitcoin development.
>>
>> ------------------------------------------------------------------------
>>
>> I use the createrawtransaction function to create transactions, and
>> before broadcasting, I always like to use decoderawtransaction to see if I
>> made any mistakes.
>>
>> I've sometimes messed up on the fee calculation, as I do that myself with
>> a calculator.
>>
>> Unfortunately decoderawtransaction doesn't give me the fee information
>> (for a very good reason, it is not aware of the value of the inputs in the
>> tx).
>>
>> So to double check the fees, instead of using createrawtransaction, I'll
>> use createpsbt and then go through the process of finalizing it so I can
>> run decodepsbt, which does give the fee along with all the other relevant
>> data.
>>
>> But the createpsbt process is more work for a simple transaction where
>> all UTXOs are in the wallet I am creating the rawtx in.
>>
>> My goal would be to modify decoderawtransaction to perform these
>> additional steps:
>>
>> 1. Fetch UTXO details for each input.
>> 2. Calculate the total input value.
>> 3. Subtract the total output value to determine the fee.
>>
>> Additionally there are the considerations about whether the inputs in the
>> transaction are in your wallet or not.
>>
>> If I run listunspent it gives me the info I need to create the raw tx or
>> psbt, and it has the values of the UTXOs that will be used as inputs in my
>> tx.
>>
>> But I understand decoderawtransaction is meant to be used whether or not
>> the keys are in your wallet (so I was thinking to make a command argument
>> T/F to show the fee value only if keys are in your wallet).
>>
>> Alternatively if you are running the command in a node with txindex, then
>> you have the full chainstate to look up txids (whether unspent or not) - so
>> this needs to be addressed too.
>>
>> Doing this within my own node would be cool enough and I don't
>> necessarily need it to go farther than that. However if I do get it
>> working, I'd certainly try to submit a PR.
>>
>> I have no idea if any of this is possible, so I wanted to ask here for
>> some guidance and maybe mentorship in this self-interest driven project.
>> Also looking for this to be shot down mercilessly if it's just ridiculous.
>>
>> My abilities and skills are very low. My interest and persistence are
>> high.
>>
>> Any help or ridicule invited ;)
>>
>
--
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/74ae96f5-4ea4-4afa-8321-e09e4ad9f97an%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 5113 bytes --]
next prev parent reply other threads:[~2024-05-06 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 15:00 [bitcoindev] " Fractal Encrypt
2024-05-05 11:55 ` [bitcoindev] " Ali Sherief
2024-05-05 15:03 ` Fractal Encrypt [this message]
2024-05-06 8:09 ` [bitcoindev] " bitcoin-dev-ml.void867 via Bitcoin Development Mailing List
2024-05-06 23:51 ` 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=74ae96f5-4ea4-4afa-8321-e09e4ad9f97an@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