libchat/Cargo.toml


[workspace]
resolver = "3"

members = [
    "libchat/conversations",
    "libchat/crypto",
    "libchat/double-ratchets",
    "libchat/storage",
]

[workspace.dependencies]
blake2 = "0.10"
storage = { path = "libchat/storage" }

# Panicking across FFI boundaries is UB; abort is the correct strategy for a
# C FFI library.
[profile.release]
panic = "abort"
Add Project scaffolding (#1) 2025-12-22 09:40:46 -08:00
			`[workspace]`
			`resolver = "3"`
Implement double ratchet (#9) 2026-01-15 08:47:02 +08:00
Add Project scaffolding (#1) 2025-12-22 09:40:46 -08:00			`members = [`
Update workspace 2026-03-22 07:45:10 -07:00			`"libchat/conversations",`
			`"libchat/crypto",`
			`"libchat/double-ratchets",`
			`"libchat/storage",`
Add Project scaffolding (#1) 2025-12-22 09:40:46 -08:00			`]`
PrivateV1 Convo Initialization via Inbox (#13) * Load orginal protofiles * Change package name * Add prost generation * Remove placeholders * Add generated files + imports * replace with chat-proto * Add XK0 * auto formatting * Initial implementation of PrivateV1 initialization * Add ConvoFactory trait * Hook up indentity placeholder * Remove RemoteInbox until it’s needed * Simplify Identity ownership * Clean up x3handshake * Move inbox encryption * Simplify inbox encryption * Cleanup warnings * Add todos * Update chat-proto crate * Publickey Handling * Reorg Inbox handshake * Update Inbox convoId * Remove file structure headers * Update ConvoID * Add Domain Separator trait * Remove Convo trait functions * Rename Context * Add SecretKey * Add workspace dependency * update KE name * Update comments for clarity * Remove Xk0 references * Bump chat_proto version and relock 2026-01-22 06:39:09 +07:00
			`[workspace.dependencies]`
			`blake2 = "0.10"`
Update workspace 2026-03-22 07:45:10 -07:00			`storage = { path = "libchat/storage" }`
fix(nim-bindings): add all-endpoints test and fix installation_name ABI (#66) Add nim-bindings/tests/test_all_endpoints.nim which imports bindings directly and calls every FFI proc, forcing the linker to include all symbols. This catches link-time and runtime issues that the pingpong example missed because unused symbols were optimised out. Running the new test revealed an ABI mismatch in installation_name: the Rust function used an explicit out-parameter but ReprCString has only flat fields, so Nim emits it as a C return value. CI now runs nimble test next to nimble pingpong. 2026-02-28 21:03:55 +01:00
			`# Panicking across FFI boundaries is UB; abort is the correct strategy for a`
			`# C FFI library.`
			`[profile.release]`
			`panic = "abort"`