its an old style multisig address thats how
yeah i did notice that the 1hb address funded all those 173 strange looking addresses and then apparently they got reconsolidated back into that address. never heard of "old style" multisig addresses and i even googled "m- bitcoin address" but i couldn't seem to find anything. so you're smarter than google franky!
m- is "strange" because its the explorer software putting the "m-" prefix. other explorers would translate it to a "4 prefix" which is less strange and pre-dates by a few months the "3" multisig prefix which became the common multisig
its not me being smart. its instead just knowing more about bitcoin and certain people on this forum using poorly expressive explorers, thus they are prevented from knowing more..
yep even blockchain.info became lame when their "more details" feature just became a lame json expression of a transaction which does not convert raw binary tx data to hex or into proper readable information (their json details put "null" into some of the json results(facepalm)). explorers are better when they know of all key formats and also read the binery/hex better to express the results in human readable form better (for those that dont want to parse binary/hex data via their full node and convert the manual way)
some other explorers do express tx data better. so its just a case of people finding a explorer that fits their needs
There was an idea for a protocol that floated around for a while that involved using signatures to prove ownership of IPFS IDs and the ID was transferred in each transaction, but that's hardly the same thing as recreating image data in each transaction.
well having a dead meme stored somewhere.. but have a hash of the dead meme store. where the HASH is the thing that then moves instead of the meme itself, can show proof of transfer without the major bloat, because if only the hash moves to only one output which moves to only one child and grandchild tx. then becomes a proof of transfer without the main bloat of moving whole files
as for "signature" well a base signature cannot be bruted to include the hash of file. but the "script" that explains how the signature is processed EG showing a 1 of 2 multisig where 1 is the signing key and 2 is the hash. would include the hash in the script process to signing proof. thus the hash would be in the blockchain, which then shows a taint path each time its spent
EG if you know the file hash. you choose a key you want as part of a multisig. and join the hash and key to create a multisig you then spend to that multisig to get the multisig into the blockchain. then when spending from it. each buyer gives you their receiver key. the seller joins the buyers receiver key with the file hash to give the file hash to the receiver. where the receiver can spend using 1 of 2 signing process. and they do this when its time for them to pass the hash to the next person by doing the same thing combining the net buyers key to the hash to create a multisig.
the file itself does not need to be in a bitcoin blockchain as long as bitcoin registers the ownership transfer
ofcourse bitcoin does not have any locks to ensure the original owners cant just later put a hash into another recipient and claim the first one is wrong(ordinals cant prove anyone ever took ownership, so even easier for ordinals to scam people ). but thats where legally the timestamp comes into play.. first sight of hash wins and its that chain of hashes that are the default path. because there is a clear seen path of hashes per spend
as for worries of UTXO bloat
utxoset does not store all keys of a multisig. so even if a multisig is 1 of 1 1of 2 or x of 15 the utxoset just saves the same length of output
yes spending a mutlisig utxo uses more data on the blockchain rather than a legacy address. but a 1 of 2 needing 2 key lengths + 1 sig is less bloaty then then transfering whole files
unlike ordinals that do not have a chain of hashes of the file or the file itself thus are nothing like any method of NFT as they miss out on anything that can be considered as proof of ownership/transfer