📅 Original date posted:2011-10-24
🗒️ Summary of this message: A developer is trying to extend the 'gettransaction' call to include an extra field "inputaddresses" in Bitcoin transactions, but it is not encouraged.
📝 Original message:On Mon, Oct 24, 2011 at 10:29:57AM +0200, Jan Vornberger wrote:
> Hi there!
>
> As part of my green address endeavor, I'm currently trying to extend the
> 'gettransaction' call to include an extra field "inputaddresses" which
> should return a list of the Bitcoin addresses associated with the inputs
> of the transaction.
Bitcoin transactions do not have input addresses - they optionally have addresses
the input coins were last sent to. I understand that being able to have a
'from' address on a transaction is useful in certain cases, but it encourages
using such 'from' addresses to identify transactions - which is imho the wrong
way to go.
As far as your green transactions idea is concerned, maybe we could provide an interface
to mark certain addresses as 'trusted', and have an RPC call to request all incoming
transaction that originate from trusted sources?
--
Pieter
Pieter Wuille [ARCHIVE] /
npub1tj…jtl6r
2023-06-07 02:34:45
in reply to nevent1q…9qlx
Author Public Key
npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6rPublished at
2023-06-07 02:34:45Event JSON
{
"id": "08f7a7132fb6da1c69b3f619225e04dc278db9ee631502f9324e6a36ca6f1fd6",
"pubkey": "5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6",
"created_at": 1686105285,
"kind": 1,
"tags": [
[
"e",
"30f32a4839f3515f22b5206d3110e202b851ce295fc65c5314c19fc43658750b",
"",
"root"
],
[
"e",
"10511d84cd407e24803db2dde64d77aedd9207be75188716e3db3342da35a63d",
"",
"reply"
],
[
"p",
"afb2dfc96bfe44c3ee8de2048adba7c222ff46515aae0adcf3c1ba22c37483b8"
]
],
"content": "📅 Original date posted:2011-10-24\n🗒️ Summary of this message: A developer is trying to extend the 'gettransaction' call to include an extra field \"inputaddresses\" in Bitcoin transactions, but it is not encouraged.\n📝 Original message:On Mon, Oct 24, 2011 at 10:29:57AM +0200, Jan Vornberger wrote:\n\u003e Hi there!\n\u003e \n\u003e As part of my green address endeavor, I'm currently trying to extend the\n\u003e 'gettransaction' call to include an extra field \"inputaddresses\" which\n\u003e should return a list of the Bitcoin addresses associated with the inputs\n\u003e of the transaction.\n\nBitcoin transactions do not have input addresses - they optionally have addresses\nthe input coins were last sent to. I understand that being able to have a\n'from' address on a transaction is useful in certain cases, but it encourages\nusing such 'from' addresses to identify transactions - which is imho the wrong\nway to go.\n\nAs far as your green transactions idea is concerned, maybe we could provide an interface\nto mark certain addresses as 'trusted', and have an RPC call to request all incoming\ntransaction that originate from trusted sources?\n\n-- \nPieter",
"sig": "5f4ebda2ae5d143a6294e1b2478e79968e0844ef4eaf918dcc27e93221fd31812b0ed4eee0e01a0991cb80caa5fd00d5309b2e162cf4d49279f54bf92272c0da"
}