Build on the supported package contract
Use @absolutejs/secure-messaging-federation-delivery through its supported public entry points.
@absolutejs/secure-messaging-federation-delivery
@absolutejs/secure-messaging-federation-deliveryv0.0.1betaMessagingDeliveryService bridge from AbsoluteJS secure messaging to authenticated federation transports.
#Installation
BASH
bun add @absolutejs/secure-messaging-federation-delivery#Capabilities
Overview
An adapter from AbsoluteJS secure messaging's DeliveryService to an authenticated, interchangeable federation transport. It carries the actual protected messaging frame as opaque bytes; it does not replace MLS or decrypt application content.
Security boundary
Outbound application routing is converted into a provider-local opaque routeId. Inbound code resolves only a preconfigured session before checking the remote-domain signature. The application conversation and recipient route are resolved only after authentication and replay checks succeed.
The selected strict-e2ee or managed-recovery mode must exactly match the negotiated federation session. Modes are never inferred or silently downgraded.
Use random, non-semantic conversation and route identifiers. MLS authenticated data can be visible to a delivery provider even though application plaintext is encrypted; do not place email addresses, usernames, or other personal data in identifiers.
Usage
Pass delivery to createSecureMessagingClient. The directory is the policy boundary: it must return negotiated, unexpired sessions and opaque routes for the current tenant.
Protocol position
This package is an AbsoluteJS bridge, not a claim of independent MIMI interoperability. Use the revision-pinned MIMI adapter for experiments with the active Internet-Drafts and the HTTPS adapter for the hardened network hop.
Outcomes
What you can build
Hardening checklist
Production guidance
Make every external boundary explicitPin the deployed @absolutejs/secure-messaging-federation-delivery version, replace example or memory-backed dependencies with durable implementations, bound external calls, protect credentials, and emit enough evidence to retry or recover safely.
Follow in order
Troubleshooting path
1
Trace from the first failed boundary
Reproduce the smallest canonical @absolutejs/secure-messaging-federation-delivery example, confirm the supported entry point and version in the API explorer, then inspect the first boundary that did not produce its documented result.
#Usage
Partial snippetWorking example for Usage.
TS
import { createFederatedDeliveryService } from "@absolutejs/secure-messaging-federation-delivery";
const delivery = createFederatedDeliveryService({
directory,
limits,
localDomain: "alice.example",
maximumMessagesPerReceive: 100,
replayStore,
signatureProvider,
transport,
});#Public entry points
Supported entry points declared by this package manifest.
Package entry point declared in package.json.
@absolutejs/secure-messaging-federation-delivery@absolutejs/secure-messaging-federation-delivery/manifest@absolutejs/secure-messaging-federation-delivery/manifest.json
#Package commands
Scripts declared by this package manifest.
bun run buildrm -rf dist && bun build src/index.ts src/manifest.ts --outdir dist --root src --sourcemap --target=browser --external @absolutejs/e2ee --external @absolutejs/secure-messaging-federation --external @absolutejs/manifest --external @sinclair/typebox && tsc --project tsconfig.build.json && absolute-manifest emit
bun run check:packagebun run format:check && bun run typecheck && bun run test && bun run build && bun run verify-package
bun run format:checkprettier --check "./**/*.{ts,json,md}"
bun run testbun test tests/
bun run typechecktsc --noEmit
#API reference
Search the declarations exported by the current package type files. Expand a symbol to inspect its source-backed signature.