Tools › Entity types

Redact crypto wallet addresses from text, JSON, and CSV

Wallet addresses are permanent and public. Once one is tied to a person in a leaked document, every later transaction on it becomes attributable to them.

How Redactly detects crypto wallet addresses

• Matched by regex for Ethereum-style 0x addresses, Bech32 bc1 addresses, and Base58 Bitcoin addresses.
• Runs independently of the model, so an address in a bare JSON value is still found.
• Checksum casing is not required for a match, because not every source preserves it.

Why redact crypto wallet addresses?

Publishing a wallet address beside a name permanently links the two on a public ledger.

Example request

curl -X POST https://api.bitbanger.in/v1/redact \
  -H "X-API-Key: rdct_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"text": "Refund sent to 0x742d35Cc6634C0532925a3b844Bc454e4438f44e.", "style": "replace"}'

Every hit in the response carries entity, text, start, and end. The offsets index into the text you sent, so you can apply the redactions to your own copy of the document. The full response schema is in the API reference.

Questions

Related entity types

• Credit card numbersRedact card numbers from text and JSON with Luhn validation, so only real card numbers are flagged and order IDs are left alone.
• IBANsRedact International Bank Account Numbers with mod-97 validation across all SEPA countries.
• UsernamesRedact handles and account usernames from transcripts, exports, and community data.