MAP record

MAP Unspendable

Key-value pairs that say what a transaction is for: its app, its type, and any fields the app needs.

What it is

MAP, the Magic Attribute Protocol, writes pairs of keys and values into an OP_RETURN output. A SET command adds pairs; apps use them to label a post, a like, a ticket or an object. Because MAP is a Bitcom protocol, it can follow another one in the same output after a pipe.

Script pattern

OP_FALSE OP_RETURN A data output.
"1PuQa7K62MiKCtssSLKy1kh56WWU7MtUR5" The MAP prefix.
"SET" The command.
<key> <value> … Pairs, such as app and type.

How it is spent

It cannot be spent.

Background

MAP was published in 2019 and became the shared vocabulary of many BSV apps. Its keys are free-form, so each app documents its own and readers agree on the common ones, such as app and type.

On chain

8af3c6f02d50ef71a0b9e281cfb5a32860452bf9af7d25c3ba0a66bc6e392d78 block 957,679
fd4c02466488f70de87232795864349449edb6c561a234dd40015601d3fd9922 block 957,679
5aba22a3690e7ddd1da0b0274c9746cc31cfb96cd2593c46e32b955ebcf824ea block 957,679
8ea61f0810c4c1ef323ae376bb554453af5ed520b6cf8481d823bec4bfbce643 block 957,679
dad2e641455f2809f8b9ca68d05482aaebde6d226ee9c20dba6980dec486fe67 block 957,679

Transactions our protocol detector tagged MAP. Transaction pages need sign-in.

Specification

MAP specification
See MAP in the Bitcom registry
/api/v1/types/map
/api/v1/txs?type=map every stored tx of this type, newest first, with an API key or signed in.