so you mean calculate back the pubkey through the pubkey-hash which is in inputscript of transaction? i can write one for you when you need this i described. off course free. only confirm: so basically you want have "sending" address/es of tx inputs. do i understand correct?
Yes, it would be wonderful if it would work across different altcoins.
Hello i have now check this in detail and its not accurate or i say its not secure for you because its NO sending address 100%. So often its many sending addresses when you have many inputs but you CAN NEVER know when its the REAL sender then only proof the person control NEW OUPUT. So maybe you have then WRONG pubkey. Conclusion: With RPC-bind its not work proper. I see also a opensoucre C# wrapper[1] which use this schematic like you explain, and the DEV say:
// which might not actually be the sender
also you can see in this thread[2] a discussion for THIS problem.
[1]https://github.com/GeorgeKimionis/BitcoinLib (title: .net RPC Wrapper in C#)
[2]https://bitcointalksearch.org/topic/get-sender-address-from-rpc-api-413939 (title: get sender address from RPC api )
i hope this help you.
thank you.
ca333