Fergal

Makes sense, so the acknowledgement is effectively on the REST side. Would be nice to be event by event too and not just resume from event number, in case there...

I guess all of the time these have been e2e tests not integration. At least for me, integration is usually in between where you are still mocking some things or...

> The problem I want to solve is to ensure updates to keria are compatible with signify. I want to avoid the situation we had for several months this year...

@edeykholt Yeah that was a problem but has already been fixed - we use dev releases now. That keeps Signify stable but I mean if KERIA changed dramatically and we...

Thanks @2byrds I added a screenshot and note to the description. Yeah based on recommendations from Phil, migrations should be manual, hence the cli. Regarding testing - I think we...

Based on discussions yesterday and https://github.com/WebOfTrust/keripy/issues/824 more thought should be put into this. If SignifyGroupHab and other files move to KERIA, we may need a separate set of migrations for...

@kentbull I hadn't had the time to revisit this since we had the discussion that parts of keripy need to be moved here, in which case this migration needs to...

Thanks @m00sey it's currently `keri.app.connecting`. So we can remove from the `app` package for sure. While we can have `keri.organizing`, maybe `keri.wallet.organizing` might be better in case we have further...

Thanks @pfeairheller! We'll make these changes shortly.

@Sotatek-DukeVu Please see the recently merged: https://github.com/cardano-foundation/veridian-wallet/pull/1441 which handles the verification in the core, and tracks the actions a user has done etc. @sdisalvo-crd This will solve the issue of...