Skip to content

Labels tags and packs

thaneye edited this page Nov 9, 2026 · 7 revisions

Labels, tags and packs

Names, tags and notes: your own, the built-in list, label packs and the OFAC sanctions list.

  • Built-in packs - lists that come with the page, shown under Label packs > Built in: the OFAC and UK sanctions lists, switched on until you switch them off, and Ransomwhere, Mining pools and GraphSense, all switched off until you switch them on (the choices are kept in this browser, and the wallet overview follows them). The UK Sanctions List (published by the Foreign, Commonwealth & Development Office, Open Government Licence v3.0) has no field for a crypto wallet: when the UK names one it writes it into the free text of the entry. The pack is made by reading those two text fields of every designation, keeping what is shaped like a Bitcoin address and passes its checksum (an address the text gives as BCH, ETH and so on is left out; one marked USDT is kept, because Omni USDT is paid to an ordinary Bitcoin address, and the note says what the entry called it), and naming it UK Sanctions: <name of the entry>. Today that is 4 addresses (the list holds far more Ethereum and Tron ones, which Hopline does not read), 2 of them also on OFAC; it grows as the UK names more. It is a sanctions list, so a wallet on it gets the red ring, the banner and the line in the report like an OFAC one. The GraphSense list is a chosen part of the GraphSense public TagPacks (https://github.com/graphsense/graphsense-tagpacks, MIT): 188 Bitcoin addresses from ten packs, each linked to the document it comes from, namely a U.S. Department of Justice forfeiture complaint, an FBI press release, and the reserve wallets that some exchanges publish themselves. The repository's other packs are mostly bulk lists copied from elsewhere, whose own terms its licence cannot grant, so a pack is taken only after its tags' sources have been read; the list taken and the reasons are in sources.md. Ransomwhere (https://ransomwhe.re, CC BY 4.0, by Jack Cable and contributors) is a crowdsourced list of the Bitcoin addresses ransomware actors asked victims to pay, checked by hand against the ransom demand: 11,178 addresses from 136 families, up to October 2024. Each is named Ransomware: <family> (or Ransomware (family not known)), tagged RANSOM, with the payments the dataset recorded for it as the note (how many, when, how much in all) and a link to the dataset. It says the address was reported as a ransom address, not who is behind it, and a payment to an address is not proof about any other. Mining pools is the list mempool.space uses to name the miners of blocks (github.com/mempool/mining-pools, MIT, Copyright 2019 btc.com and contributors): the 212 mainnet addresses that block rewards of 104 pools are paid to, each named Mining pool: <name>, tagged MINING, and linked to the pool's own web address; testnet addresses and the coinbase text tags are not used. A reward address is not always the wallet the pool pays its miners from, and a name there is a claim by the people who keep the list, mostly the pools themselves. It is off as shipped because a named wallet stops Auto-expand, and tracing through a pool's payout would otherwise stop at it. Each row says how many wallets it holds, the date of its data (as of), a warning once the data is about two months old, its licence and a link to its source. They are read from files on the same site (public/packs/), so nothing is sent anywhere, and a pack's file is only loaded when it is on. A built-in pack is a snapshot made by python tools/build_packs.py --download (or --ofac <file>, and --download-ransomwhere or --ransomwhere <file> for Ransomwhere, and --download-miningpools for the mining pools, --download-uk or --uk <file> for the UK list, --download-graphsense for GraphSense), which writes public/packs/<id>.js with one wallet per line, sorted, so a refresh shows in a diff as the wallets that were added or removed, and updates the list the pages read, public/packs/index.js. A daily workflow runs it with --refresh and opens a pull request when a list changed (see Development). It refuses a list that shrinks to under 80% of the earlier one (--force overrides), and a list it could not read completely. The mining pools list and the GraphSense packs are taken from the newest commit, with the commit and its date written into the pack, after checking that the repository's licence text is still the MIT text the tool knows (if it changed, nothing is made until a person has read it); the pack file starts with that licence text, which the MIT licence asks to travel with copies. Ransomwhere is taken only from the release the tool is pinned to (its MD5 is checked against the one Zenodo publishes), because the pack states that release's licence; a newer release is adopted by reading its record and changing the pin. When several lists name one wallet, the built-in wallet list comes first, then your own packs, then the built-in packs. If you import a pack with the same name as a built-in one, yours is the one that counts, and the row says so.
  • Label packs - Label packs (left panel) imports lists of wallets and names from a CSV (address,label,category,url,note; common column names are understood, or just two columns) or a JSON file: an exchange's addresses, a sanctions list, your team's findings. Every address is checked, checksum included, and anything that is not a valid Bitcoin address, repeats, or has no label is counted and left out; text is cleaned and links must be plain http(s). A pack's wallets show as known (pack name) with a gold ring, stop an auto-expand like any known wallet, and feed the likely-change reasoning; two packs naming one wallet both show (the details list every claim, and the report says also listed as). A pack that says it is a sanctions list (the OFAC import does) gives its wallets a red ring and a SANCTIONS badge on the graph, a banner on the wallet overview and a line in the report. A pack can be switched off or removed, is kept in this browser, and is other people's claim, kept apart from your own labels. A JSON pack may also say where its data came from, all optional: licence, attribution (who to credit), asOf (the date of the data, YYYY-MM-DD) and sourceUrl; they are shown with the pack, and a claim carries the date. Share your own labels exports your labelled, tagged and annotated wallets (CSV or JSON) in the same format. The OFAC sanctions list is read directly: download SDN_XML.ZIP from https://sanctionslist.ofac.treas.gov/Home/SdnList and choose it in Import labels. SDN_ENHANCED.ZIP and SDN_ADVANCED.ZIP (or any of the three unzipped) work as well, give the identical pack, and are just several times larger. The page unzips and reads the file in your browser (nothing is sent anywhere) and makes a pack of the Bitcoin addresses it names, each linked to OFAC's page for its entry; it counts the address entries in the file and warns if it could not read them all. Do not use SDN.CSV: it cuts long entries and loses addresses (in October 2026 it held about half of the Bitcoin ones), and the page says so if you choose it. The list is public and needs no account or key. The built-in copy is only as new as its date; import the file to use a newer one (a pack with the same name replaces the built-in one, and importing it again replaces your earlier import). python tools/make_label_pack_ofac.py --download --out ofac.json (or --sdn <any of the files>) does the same from the command line and gives the same pack.
  • Tags - give a wallet or transaction a tag (EXCH, THREAT, VICTIM, PAYMENT, MIXER, MARKET, SERVICE, GAMBLING, SWAP for a swap or bridge service, WATCH, or your own text) with a colour and a shape of its own, next to the label in the details. A preset sets a colour and shape that you can then change separately (VICTIM is a blue triangle pointing down, the THREAT triangle turned over); the tag is drawn as a badge above the vertex, listed in the legend (click an entry to select everything carrying it) and written to the exports. Several selected vertices can be tagged at once.
  • Tags from the lists - when a wallet appears on the canvas and a list says what kind of service it is, it gets the matching tag with that tag's colour and shape: an exchange gets EXCH (a green hexagon). The built-in list carries the category Exchange on 869 of its 908 wallets (Binance, Coinbase, Kraken, Robinhood, Xapo and so on) and Swap on Fixed Float, which gets SWAP (an orange hexagon); the rest, such as Sygnia (asset management), Coinspaid (a payment gateway), the mining pools, Cash App, the hack addresses and the Luna Foundation Guard, have no category and are not tagged). A label pack can do the same through its category column: Exchange, Mixer (or Mixing service), Market (or Darknet market), Gambling, Swap (or Bridge) and Service (or Merchant, Payment processor) are understood, in any case and spelling; the GraphSense pack's EXCHANGE wallets are tagged this way. Nothing else is: a sanctions or ransomware entry keeps its own marking (the red ring and the SANCTIONS badge), and THREAT, VICTIM, PAYMENT and WATCH are your own judgement, so no list sets them. It happens once, when a wallet first appears: what you then change or remove stays as you left it, and a wallet that already has a tag, colour or shape of your own is never touched. A file, a saved session or a shared link you open is shown as it was saved. A tag that only repeats what the list said is not counted as yours: it stays out of Share your own labels, and the list's name (not the tag) remains the wallet's name in routes and lists; change its colour or shape, or replace the tag, and it becomes yours. When a wallet is on two lists, the first list that names a kind of service decides (your own labels, then the built-in list, then the packs). Under Label packs > Tags from the lists the switch Tag known wallets when they appear turns it off (kept in this browser), and Tag known wallets now tags the wallets already on the canvas that have no tag, for a canvas made before or after switching a list on. A tag from a list is a claim like the name it comes from, not a finding: check it before you rely on it.
  • Your own labels and notes on any vertex, kept in the exported file; the wallet overview reads them from the saved session too. A vertex that has a note carries a small yellow note at its lower right on the canvas, so the ones you wrote on stand out without opening them; hovering over the vertex shows the start of the note (the first 140 characters), and clearing the note removes the marker.

Clone this wiki locally