eIDAS 2 and the European Digital Identity Wallet
Bricks Technical Documentation
What the 2024 revision of eIDAS changes for an organisation on Bricks, where BricksID stands today, and what in its design already fits the European Digital Identity Wallet.
Regulation (EU) 2024/1183 revises eIDAS. Its central addition is the European Digital Identity Wallet: each Member State offers its citizens a wallet to identify themselves, share verified attributes and sign. The rules that apply today are in eIDAS.
What the revision changes
- Every Member State offers at least one wallet. Issuing, using and revoking it is free for natural persons.
- People can sign with it. The wallet lets a person make a qualified electronic signature, free of charge at least for non-professional purposes.
- Services that accept the wallet register. A relying party registers with its Member State and states the data it intends to request.
- Some private services must accept it. Private services that already require strong authentication in sectors including banking, financial services, health and social security must accept the wallet when the person asks; micro and small enterprises are exempt.
- Wallets work across borders. A service that accepts the wallet accepts every Member State's wallet, without a separate integration per country.
Where BricksID stands
Current limits. BricksID does not accept the European Digital Identity Wallet yet: it does not read identification or attributes from a wallet, does not let a person sign with one, and is not registered as a relying party. Acceptance depends on the wallets of the Member States opening to private services.
What already fits
- Identity belongs to the person. A BricksID is the person's own account, used across every organisation on Bricks; it is not an account inside one organisation. A verified identity from the wallet would attach to that account, whatever means verified it.
- Signatures and documents belong to the person. Signed documents and their evidence are kept in the person's BricksID, as the wallet keeps the person's attestations.
- Evidence does not depend on one provider. The evidence of a signature records what was signed, by whom and when, and is sealed by the platform. A qualified signature made through the wallet would be recorded and kept the same way.
- Verification outlives keys. Published keys are never deleted, so evidence remains verifiable after keys change, as long-term signature validation requires.