# Proposal: crypto-utils-bytes-refactor

## Why

`@suaveplan/crypto-utils` duplicates hex/base64/utf8/bytes/concat encoding that now lives canonically in `@suaveplan/bytes`. Deduplication reduces maintenance surface and ensures consistent behaviour across the monorepo.

## What

Add `@suaveplan/bytes` as a `workspace:^` dependency to `crypto-utils`; replace the duplicate encoding utilities with direct imports from `@suaveplan/bytes`. `base58` stays in `crypto-utils` — it is blockchain-specific (Bitcoin address encoding) and not a general-purpose byte encoding concern.

## Impact

`crypto-utils` gains one new workspace dep; its exported surface is preserved (re-export or wrapping so consumers see no API change); downstream packages unaffected.