0

It seems Deepbit uses a strange format for it’s transactions on the addresses it owned. For example, in this transaction all inputs but 3 comes from Deepbit. Even Bitcoin core can’t decode addresses or scripts from transactions launched by Deepbit. This seems to apply to all transactions

That time it’s not SegWit. It’s not even Pay to Script since they didn’t exists at that time (and it’s about1Vaddresses). How those inputs are specials, and what’s the purpose ?

3

Those transactions spend Pay-To-Pubkey outputs. These are not special or strange and are actually the very first kind of outputs to ever exist in Bitcoin. These outputs simply do not have an associated address type which is why block explorers do not show an address for them.

Also, just because a block explorer can't show an address type does not mean that Bitcoin Core can't parse it. Block explorers don't just use Bitcoin Core, and Bitcoin Core actually does not display addresses for inputs.

  • Ah, it’s because they are pay to pubkey input addresses can’t be decoded ? – user2284570 Apr 6 at 22:26
  • Yes. P2PK outputs do not have associated addresses. – Andrew Chow Apr 6 at 23:07
  • 1
    Non-standard is still valid. Standardness is a node relay policy, not a consensus rule. Non-standard just means a node will not relay the transaction. However it is still valid and can be included in a block and nodes will accept it. – Andrew Chow Apr 7 at 20:40
  • 1
    By mining it yourself, or having an agreement with a miner/pool to include it. – Pieter Wuille Apr 7 at 21:00
  • 1
    @user2284570 Standardness is a local policy; anyone is free to run modified software with different standardness rules. And several miners historically have offered including nonstandard transactions for payment. – Pieter Wuille Apr 8 at 12:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.