Bitcoin Forum

What are "d-...", "m-..." and "s-..." addresses in Bitcoin?

Op I think you are mistaking a public key for an address.
Public keys use kind of random characters compared to Bitcoin addresses that  usually start with;
1 - for legacy addresses
3 - for SEGWIT compatible addresses
bc - for the native SEGWIT addresses.
 
Public keys on the other hand can start with those characters or even others but the facts is only very old wallets use public keys to receive Bitcoin. The Bitcoin wallet address is gotten from that public key via a special algorithm for wallet address generation. That is partly why HD wallets are possible because multiple addresses can be generated from a single public key.
 Here is a link with better explanation  (https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://en.bitcoin.it/wiki/List_of_address_prefixes&ved=2ahUKEwii1KKGvt2EAxWkU0EAHWJMAfUQFnoECBsQAQ&usg=AOvVaw0DenhaAE0YnvSxU_rCTeqL)
Even when you try generating a custom address you still end up with an address starting with 1, 3 or b.

We have testnet addresses starting with m, but there is no bitcoin address starting with d or s.


Even public keys don't start with the characters mentioned by OP.
Public keys start with 02 or 03, if they are compressed and 04, if they are uncompressed.

I found these addresses in LoyceV's dumps, for Bitcoin. Seems like they are real.

OP's question is technically right, but it's not Bitcoin specific.

D = dogecoin addresses
m = testnet pubkey hash
S = That's a tricky one... The stacks network (https://www.stacks.co/) uses addresses that start with an 'S'. It's the mainnet pay-to-pubkey hash. It's essentially a Bitcoin layer-2 implementation for smart contracts etc. Here is a github post to verify what I am saying: https://github.com/stacks-network/stacks-core/issues/832#issuecomment-400393291

They're not :P It's something Blockchair made up:

they are nonstandard ways to identify transaction scripts that don't follow the standard address formats. I assume m- is multisig, not sure abut the others.

WOW!

That's wild!

Looks like D is not the same as d and S is not the same as s.

Sorry, my answer above (https://bitcointalk.org/index.php?topic=5487666.msg63762912#msg63762912) is correct, but not accurate to your point.

After seeing this topic (https://bitcointalk.org/index.php?topic=5487786.0) (which points to transaction 1 (https://blockchair.com/bitcoin/transaction/60e00d2ddf8990f02c6dc41d0d068e4514ae4838f3af3334557a712e1a00ab52) and transaction 2 (https://blockchair.com/bitcoin/transaction/65f8ac99b7167283abc5cef4dcedd82f6e86cc6e6ec9c266990d42c1d2357f55)), I am now curious what the difference is. This looks like someone with mining-access playing around (1 sat/vbyte and 0 sat/vbyte), but I don't know why.

Somebody needs to email blockchair support, preferably without using a Proton or tutanota email addresses as Blockchair is using Yandex (who's filtering those mail servers) as their email service, and ask them what these prefixes are supposed to mean or if they are just for internal use. There is no trace of these addresses in their Github docs: https://github.com/Blockchair/Blockchair.Support

This is actually incorrect, unfortunately. However, this is actually an implementation used by blockchair, and the format is unique to them. Confusion seems to stem from the fact that people think that these are addresses and not representation of scripts on Blockchair.

There are three different types as correctly identified, d-, m-, s-. d- is for OP_return and m- is for multisig and s- is for non-standard script. S- is relevant to that transaction mentioned is because the script is just OP_NOP OP_NOP OP_NOP OP_NOP OP_NOP OP_PUSHNUM_1. Not a standard that Blockchair recognizes, and thus the s- prefix.

There was an FAQ on this previously, but the only reference I can find currently is here: https://github.com/Blockchair/Blockchair.Support/issues/273.