From 4b62d6bd19a8cd50e1eda6973fb08bf163590259 Mon Sep 17 00:00:00 2001
From: Ishaan <51675727+ishaan0x@users.noreply.github.com>
Date: Fri, 5 Sep 2025 10:50:19 -0700
Subject: [PATCH] Update blazar.md

Secure -> Trustless
---
 docs/products/eigenda/releases/blazar.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/products/eigenda/releases/blazar.md b/docs/products/eigenda/releases/blazar.md
index f162e847..c9e16b25 100644
--- a/docs/products/eigenda/releases/blazar.md
+++ b/docs/products/eigenda/releases/blazar.md
@@ -399,7 +399,7 @@ Rollups will need to perform the following upgrade actions:
 1. **Update data routing**. Deploying a version of https://github.com/Layr-Labs/eigenda-proxy that supports Blazar (internally this new release will use the [EigenDA clients](https://github.com/Layr-Labs/eigenda/tree/master/api/clients/v2)) will enable use of the Blazar endpoints. We will make an announcement once such a release is ready.
    1. Once you do so, all blob POST request submitted to proxy will be dispersed to the Blazar disperser, and encoded using a commitment with a [0x1 version byte](https://github.com/Layr-Labs/eigenda-proxy?tab=readme-ov-file#commitment-schemas) (as opposed to 0x0 for V1).
    2. GET requests will be [routed](https://github.com/Layr-Labs/eigenda-proxy/blob/44191c1a1b3149d52a80f2fa82690f4a92ac62db/server/routing.go#L22) to the correct network based on their commitment version byte.
-2. **Implement Secure Verification**. We are in the process of individually updating each rollup stack in order to support secure integration strategies (such as fault proofs or validity proofs) for Blazar.
+2. **Implement Trustless Verification**. We are in the process of individually updating each rollup stack in order to support trustless integration strategies (such as fault proofs or validity proofs) for Blazar.
 
 ## Action Plan