# “Passport Prime: Great Concept, Poor Execution

**URL:** <https://community.foundation.xyz/t/passport-prime-great-concept-poor-execution/1013>\
**Category:** Passport Prime\
**Created:** [April 15, 2026, 12:53am UTC](https://community.foundation.xyz/t/passport-prime-great-concept-poor-execution/1013 "2026-04-15T00:53:49Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Jack](https://community.foundation.xyz/user_avatar/community.foundation.xyz/jack/32/371_2.png) [@Jack](https://community.foundation.xyz/u/Jack)\
**Post date:** [June 13, 2026, 6:00am UTC](https://community.foundation.xyz/t/passport-prime-great-concept-poor-execution/1013/12 "2026-06-13T06:00:16Z")

</div>

Hey @Ke_James thank you for the followup. Last update was 10 days ago here: [When Use case for prime - #9 by Jack](https://community.foundation.xyz/t/when-use-case-for-prime/1083/9)

As mentioned there, we had a hiccup that forced us to change our release schedule. Users will now have to update to 1.2.2 then automatically get updated to 1.3.0. We have been pens down for 1.3.0 features for weeks now, but we want to make sure that the upgrade process is solid, building this “as soon as you unlock in 1.2.2 should trigger an update to 1.3.0” flow is not something we want to take lightly. So that was the root of the delay essentially, but you can expect a public beta this week.

---

_[View the full topic](https://community.foundation.xyz/t/passport-prime-great-concept-poor-execution/1013)._