Why is there no one to call when a foreign verifier misuses my domestic credential?
Возможность
Digital identity wallets are built around issuer-state jurisdiction: if a Dutch-issued credential causes a dispute, Dutch authorities are the expected recourse. When that credential is accepted by an employer in Singapore or a bank in Canada, the issuing jurisdiction has no legal reach and the foreign verifier has no obligation under that framework. A 2026 European Financial Review analysis identified the UK-EU verification gap as a specific and growing commercial friction point, and a cross-jurisdictional redress study published in May 2026 found that every deployed digital identity architecture assumes the issuer jurisdiction and the redress jurisdiction are the same entity, an assumption that cross-border wallet use immediately breaks. No bilateral recognition agreement covers what happens when an accepted foreign credential leads to fraud, a data error, or a revocation dispute, and t
Почему это важно
Without enforceable cross-border redress, the global portability promised by digital identity wallets is a technical fact with no legal substance the moment it matters most.
Как я оцениваю возможность
Оценка возможности отражает моё личное суждение, а не точное измерение: насколько проблема болезненна, как часто она встречается и насколько мало существует решений сегодня. Чем выше оценка, тем более достойной реализации я считаю эту задачу.
Насколько серьёзные проблемы это создаёт.
Как часто люди с этим сталкиваются.
Насколько мало хороших инструментов для этого существует сегодня.
Ещё задачи, достойные решения
Почему программное обеспечение, от которого мы зависим больше всего, так неудобно использовать?
TechПочему я по-прежнему не владею ни одними из данных, которые генерирую?
TechThis is a fundamental limitation of how most data deletion works today, and it comes down to a few core problems: **Deletion is an absence, not a presence** A receipt is a positive artifact -- proof that something *happened*. Proving a negative ("this data no longer exists anywhere") is cryptographically and architecturally much harder than proving a positive ("this file was signed at time T"). **No standard audit trail** Most systems are not built to emit a verifiable, tamper-proof log of what was deleted, when, and from which storage layer. Even if a company tells you "your data was deleted," that statement lives in their system, which they control. **Backups and replication** Data often lives in dozens of places: primary DBs, read replicas, backups, logs, caches, CDN edge nodes, analytics pipelines. A deletion receipt would need to account for all of them -- and companies rarely track this end-to-end. **No legal requirement to provide one** GDPR Article 17 gives you the right to erasure, and Article 19 requires notification to recipients -- but neither mandates a cryptographically verifiable receipt. Companies only have to confirm deletion, not *prove* it in a way you can independently verify. **Technical proof would require architectural changes** A trustworthy receipt would need something like: a Merkle-tree deletion proof, a signed timestamp from an independent witness, and a commitment scheme proving the original data existed before deletion. Almost no consumer product is built this way. The gap here is a policy and incentive problem as much as a technical one -- companies have little motivation to build verifiable deletion infrastructure when regulators don't require it.
TechПочему я не могу знать, соответствует ли то, что запущено, тому, что задекларировано в моём SBOM?
TechПочему мой сканер безопасности не обнаруживает тот класс уязвимостей, который чаще всего указывает мой ИИ-помощник?
TechПочему мой ИИ-агент без предупреждения направляет европейские медицинские данные через сервер в США?