> For the complete documentation index, see [llms.txt](https://cifer.gitbook.io/cifer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/web3-integration/wallet-integration.md).

# Wallet integration

Cifer signs messages through a small adapter interface. The standard browser path uses `Eip1193SignerAdapter`.

```typescript
import { Eip1193SignerAdapter } from 'cifer-sdk/adapters';

const signer = new Eip1193SignerAdapter(window.ethereum);
const address = await signer.getAddress();
const signature = await signer.signMessage('message');
```

The SDK can therefore sit behind MetaMask, WalletConnect, wagmi, Thirdweb, Coinbase Wallet, embedded-wallet providers, or another EIP-1193 implementation.

## Application responsibilities

* Request accounts only in response to clear user intent.
* Verify the wallet chain before submitting an on-chain transaction.
* Present the transaction intent and expected value before confirmation.
* Treat account and chain changes as state changes.
* Never log signatures that could authorize a replayable action.
* Keep RPC configuration and controller addresses tied to the intended chain.

For server-side or automated use, implement the signer adapter or use the SDK private-key adapter with an appropriate key-custody system.


---

# 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://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/web3-integration/wallet-integration.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.