Fergal

fix: delete contact by prefix

1

The [endpoint on KERIA](https://github.com/WebOfTrust/keria/blob/a1a9b02ceda45fb83885f8ad97cc8de78cb96e45/src/keria/app/aiding.py#L1526) doesn't return a JSON response, so deleting via contact is throwing an error: ``` SyntaxError: Unexpected end of JSON input at JSON.parse () ``` I can...

feat: single-sig IPEX apply, offer, agree

1

To accompany https://github.com/WebOfTrust/keria/pull/198.

Further X25519 cipher support

7

The Matter codex table in `signify-ts` only supports `X25519_Cipher_Seed` and `X25519_Cipher_Salt`. If it's OK, I'd like to add the other 18 or so - `X25519_Cipher_L0` -> `X25519_Cipher_QB2_Big_L2` [`encrypter.ts`, `decrypter.ts`, `cipher.ts`,...

HTTP query params are not signed

2

[siginput](https://github.com/WebOfTrust/signify-ts/blob/development/src/keri/core/httping.ts#L33) should accept query params to be signed when sending a HTTP request. Right now it's just the path of the URL. [fetch](https://github.com/WebOfTrust/signify-ts/blob/development/src/keri/app/clienting.ts#L167) and [signedFetch](https://github.com/WebOfTrust/signify-ts/blob/development/src/keri/app/clienting.ts#L244) (and any other calling functions...

For example, right now we have `1.2.0-dev11` for x86/x64 but `1.2.0-dev11-arm64` for arm. It would be better if we can have the same tag name for all architectures. I believe...

### Version 1.2.0-dev1 - 1.2.0-dev10 ### Environment Mac OS, Python 3.12.2 ### Expected behavior I think we should be able to check migrations on a higher dev tag for the...

Working towards TEL Observers - made some changes to make TSN behave same as KSN with a noticer that will fetch any remaining items. This isn't _fully_ complete as I...

### Version 1.2.0.dev11 (still there on main) ### Environment _No response_ ### Expected behavior If tel events are missing when processing a credential, the credential is escrowed and a telquery...

feat: get credential registry state (tever vcstate)

3

This corresponds to WebOfTrust/keria#304 - see description there for more details. Essentially can get credential state (iss/rev) without needing to already hold the credential (or even be the holder).

fix: send exn to actual recipient only

2

exn messages have a specific recipient (`rp` field). Right now for multi-sig: - creates first exn message with `rp` field of first member - this message is sent to all...