# Censoring crypto address
**URL:** https://meta.discourse.org/t/censoring-crypto-address/391893
**Category:** Support
**Created:** [December 22, 2025, 8:21am UTC](https://meta.discourse.org/t/censoring-crypto-address/391893 "2025-12-22T08:21:08Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@Salocin](https://meta.discourse.org/u/Salocin)
#### Post date: [December 22, 2025, 8:21am UTC](https://meta.discourse.org/t/censoring-crypto-address/391893/1 "2025-12-22T08:21:08Z")
Hello guys,
Do you think it’s possible to censor crypto address in topics? Not even sure a regex can do that… am I right?
Thanks.
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [December 22, 2025, 8:22am UTC](https://meta.discourse.org/t/censoring-crypto-address/391893/2 "2025-12-22T08:22:15Z")
What’s a crypto address?
What do you mean by “censor” - hide? block? force review/approval?
---
### Author:  [@Salocin](https://meta.discourse.org/u/Salocin)
#### Post date: [December 22, 2025, 8:28am UTC](https://meta.discourse.org/t/censoring-crypto-address/391893/3 "2025-12-22T08:28:18Z")
Ok, this is a example of a crypto address : _0x6dD9EF7464A3c28f1285bCCB95bE83dC4A9De3ca_
Not easy to detect by a regex imho. What I would like is that if a member tries to publish an address of this type it is obfuscated in the public message. And possibly visible for moderation but this is not necessarily the most important.
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [December 22, 2025, 9:04am UTC](https://meta.discourse.org/t/censoring-crypto-address/391893/4 "2025-12-22T09:04:09Z")
> [@Salocin](#):
>
> Not easy to detect by a regex imho
Very easy to detect by a regex since it’s always 0x and then 40 characters a-f and numbers.
`/^0x[a-fA-F0-9]{40}$/g`
BTC addresses would be `^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$` (`13` followed by 25 to 34 characters, excluding `l`, `I`, `O` and `0`)
Add this to watched words and don’t forget to enable settings - posting - “watched words regular expressions”.
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [December 22, 2025, 9:20am UTC](https://meta.discourse.org/t/censoring-crypto-address/391893/5 "2025-12-22T09:20:34Z")
> [@RGJ](#):
>
> `/^0x[a-fA-F0-9]{40}$/g`
Depending on which regexp engine you’re using it can be written as
`/^0x\h{40}$/`
😉
---
### Author:  [@Salocin](https://meta.discourse.org/u/Salocin)
#### Post date: [December 22, 2025, 9:57am UTC](https://meta.discourse.org/t/censoring-crypto-address/391893/6 "2025-12-22T09:57:03Z")
Thanks both.
If I’m not mistaken, there are as many sequences of addresses as crypto tokens. The example I provided is for the LINK token, but for ETH, BTC, XRP… and hundreds of others how to do it?
But in general it is easy to recognise a crypto address visually, this long sequence of characters is rather typical, so I was wondering if AI could not solve this problem more widely.
It seems feasible to you in Discourse (a plugin maybe?)
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [December 22, 2025, 10:28am UTC](https://meta.discourse.org/t/censoring-crypto-address/391893/7 "2025-12-22T10:28:39Z")
> [@Salocin](#):
>
> I was wondering if AI could not solve this problem more widely
I don’t think this is so complicated that we would need AI to solve it.
What they all have in common is that they’re a pretty long string of characters without any spaces, so `^[a-zA-Z0-9]{25,60}$` would get you pretty far.
---
### Author:  [@Salocin](https://meta.discourse.org/u/Salocin)
#### Post date: [December 22, 2025, 11:14am UTC](https://meta.discourse.org/t/censoring-crypto-address/391893/8 "2025-12-22T11:14:58Z")
> [@RGJ](#):
>
> so `^[a-zA-Z0-9]{25,60}$` would get you pretty far.
You’re right, I assume that this regex can detect 99% of the addresses. Thank you very much for your help.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [January 21, 2026, 11:15am UTC](https://meta.discourse.org/t/censoring-crypto-address/391893/9 "2026-01-21T11:15:32Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.