Publish the technical specifications of the PoC and what is technically defined for the E-ID?

[damienbod]

Would it be possible to publish the security context and the technical specifications used in the PoC and the future E-ID? This knowledge should be public if you want to succeed with the project.

Technical answers for the following would be interesting (not marketing)

1. Is the PoC (future E-ID) built using the legacy Hyperledger Aries specifications?
2. Is Didcomm V1, Didcomm V2, SIOP supported (PoC and future E-ID)? (Didcomm V2, SIOP must be supported if you want interop.)
3. How do you prevent phishing (Scanning a QRCode to start any process is not safe, phishing resistant authentication is required for most business flows)
4. What VC specifications will be supported? BBS+? etc
5. How do you replace your mobile device in a secure way? (technical process details)
6. How do you technically implement a wallet (open specifications or a monopoly for the team creating the Bund wallet)?
7. How do you technically create a Verifier? (open specifications or are we forced to use ledger X from Company X)?
8. How do you invalidate a wallet which was stolen or is being abused?
9. How do you protect users from over consent credential theft? (some type of technical solution and law solution is probably required)
10. How does the user authenticate into his/her wallet? (technical specifications that will be supported)
11. How do you invalidate a set of VCs from a wallet? (kid turns 18 and is fighting with the parents use case )

Please only technical responses