Component IDs are already unique identifiers (secured through secure randomness + cryptography by being generated from a per-component private key). Having an additional UUID field is a bit redundant, and we could reduce overall complexity by using component IDs instead.
Note that this change will require changes in brave-core to migrate UUIDs in local preference storage, so that users' enabled filter lists are not reset: see brave/brave-browser#27708.
Component IDs are already unique identifiers (secured through secure randomness + cryptography by being generated from a per-component private key). Having an additional UUID field is a bit redundant, and we could reduce overall complexity by using component IDs instead.
Note that this change will require changes in brave-core to migrate UUIDs in local preference storage, so that users' enabled filter lists are not reset: see brave/brave-browser#27708.