# Import public keys

**URL:** <https://forum.delta.chat/t/import-public-keys/1759>\
**Category:** Feature Proposal\
**Created:** [July 10, 2021, 8:24am UTC](https://forum.delta.chat/t/import-public-keys/1759 "2021-07-10T08:24:50Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Jikstra](https://forum.delta.chat/user_avatar/forum.delta.chat/jikstra/32/928_2.png) [@Jikstra](https://forum.delta.chat/u/Jikstra)\
**Post date:** [March 7, 2022, 3:06pm UTC](https://forum.delta.chat/t/import-public-keys/1759/5 "2022-03-07T15:06:43Z")

</div>

Supporting this, had some talks with @cyBerta@link2xt @nami and @r10s about this. We all want this, including an option to attach our own public key as an attachment. There’s still some open questions, if i remember it correctly they were:

- how is the state handled internally. We currently already have I think 3 priorities of keys, gossip keys, autocrypt header keys and verified keys. Somehow attached/manually loaded keys need to be put in to one of those categories, or opening a fourth.
- what happens if we receive a different autocrypt/gossip later after we manually imported a public key? Simply overloading has security implications, completely blocking it could render the chat unusable if the contact switched to deltachat/changed their key.

---

_[View the full topic](https://forum.delta.chat/t/import-public-keys/1759)._