@terminal3/t3n-sdk 3.1.0 → 3.3.0

package/dist/index.d.ts

@@ -1433,6 +1433,27 @@ declare class T3nClient {
      * 3. Sends `SubmitIdToken` with the nonce-bearing token → receives DID.
      */
     authenticate(authInput: AuthInput): Promise<Did>;
+    /**
+     * Add an Ethereum wallet as an additional authenticator on the
+     * already-authenticated account.
+     *
+     * Proves control of the wallet via SIWE and links it to the session's
+     * EXISTING DID (resolved server-side from the session) — it does NOT
+     * mint a new DID and does NOT change the session: `this.did` and
+     * `this.status` are left untouched, and no new cookie is issued.
+     *
+     * Requires a completed {@link authenticate} first (e.g. an OIDC
+     * login). Only Ethereum is supported — OIDC/email identities are
+     * established at login, not added afterwards.
+     *
+     * Reuses the same client-side eth state machine as login, but posts
+     * to the authenticated `auth.add-authenticator` route. If the wallet
+     * is already linked to a different account, the server rejects with a
+     * typed `eth_auth_map_conflict` error (resolve via account merge).
+     *
+     * @returns the existing DID the wallet was linked to.
+     */
+    addAuthMethod(authInput: EthAuthInput): Promise<Did>;
     /**
      * OIDC two-step authentication with session-binding nonce.
      *
@@ -2418,6 +2439,13 @@ interface OrgDataClientOptions extends ExecuteOrgDataActionOptions {
      * auth challenge flow automatically.
      */
     handlers?: GuestToHostHandlers;
+    /**
+     * Extra headers added to every `/api/rpc` request the internal
+     * `T3nClient` makes. Mirrors `T3nClientConfig.headers` — needed when
+     * the node sits behind an edge policy that gates `/api/rpc` on a
+     * header (e.g. the staging Cloud Armor bypass token).
+     */
+    headers?: Record<string, string>;
 }
 /**
  * Client for session-authenticated org-data contract execution.