> For the complete documentation index, see [llms.txt](https://docs.zipwire.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zipwire.io/fundamentals/security/attestations/zipwires-master-attester-wallet-address-and-public-key.md).

# Zipwire's Master Attester Wallet Address and Public Key

## Overview

**This is the official, authoritative source for Zipwire's master attester wallet address and public key.** These details are used to issue attestations on the Base blockchain and should be referenced from this page rather than repeated elsewhere in the documentation.

Zipwire issues attestations, such as "IsAHuman," to Ethereum wallets using a master attester wallet address and public key. This page provides these details for verification purposes, ensuring users and platforms can confirm the authenticity of Zipwire-issued attestations on the Base blockchain.

## Master Attester Details

Below are Zipwire's official master attester wallet address and public key, used to issue attestations:

* **Ethereum Address**: `0x2651ef3d909828eff9a9bdd6454eb5f98b045e76`
* **Public Key**: `0x04f585f43d96b93c921d4a9d2307f36a4fe1faea39a3c737a1e228295c3bcbef4813f69674b467de30e67888f1e63c13c0e12e2decd5fd623f08f7ef7959cd4b64`

These details are critical for verifying attestations, as described in [Verifying Attested Wallets](/fundamentals/security/wallet-verification-guide/verifying-attested-wallets.md).

## Verifying Authenticity

To ensure these details haven't been compromised (e.g., by a hacked documentation site), cross-reference them with trusted sources:

* **Zipwire's GitHub**: Check the official repository for the latest public key and address: <https://github.com/zipwireapp/zipwireapp/blob/master/PUBLICKEYS.md>.
* **EAS Scan (Base Blockchain)**: Review the attestation history for the master address (`0x2651ef3d909828eff9a9bdd6454eb5f98b045e76`) to confirm its activity: <https://base.easscan.org/>.

A mismatch between this page and GitHub or EAS Scan may indicate a security issue. Report discrepancies to Zipwire immediately.

## Usage Guidelines

When referencing these details in other documentation or applications:

1. **Link to this page** rather than copying the address and public key
2. **Cross-reference with GitHub** for additional verification
3. **Check EAS Scan** to verify the address is actively issuing attestations
4. **Report any discrepancies** immediately

## Why It Matters

Zipwire's master attester details enable users and platforms to verify the legitimacy of attestations, such as those used in sleeper wallets or identity checks. By confirming the attester's address and public key, you ensure trust in the verification process, protecting against fraudulent or compromised wallets. For more on attestations, see [How Sleeper Wallets Are Created](/fundamentals/security/wallet-verification-guide/how-sleeper-wallets-are-created.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zipwire.io/fundamentals/security/attestations/zipwires-master-attester-wallet-address-and-public-key.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
