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

# Integration Checklist

Integration checklist, UX patterns, and rollout guidance for product teams shipping MOSS in production. Optimized for product, engineering, and security leads working together before implementation kickoff.

## What This Checklist Covers

| Area                     | What to decide                                                                                                                       |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
| UX flows                 | Connect/auth, signing prompts, background actions, cancellation handling, fallback states.                                           |
| Data + permissions model | Session key scope, spend limits, contract allowlists, expiry windows, revocation defaults.                                           |
| Timeline + rollout       | Sandbox tests, pilot cohort, success criteria, rollback plan, release gates.                                                         |
| Gas strategy             | Default user-paid gas in ETH or enabled stablecoins; optional partner sponsorship via `sponsorUrl` + `sponsorMode` + `sponsorToken`. |
| Security + compliance    | Threat model, backend verification, key handling, logging controls, audit artifacts.                                                 |

## Gas Abstraction Options

Gas is abstracted through the relay and smart account infrastructure. Users can pay gas with ETH or enabled stablecoins (currently USDm and USDT0). Recommended default: `sponsorMode: 'app-only'` and `sponsorToken: 'native'`. Use `explicit` when you only want to sponsor selected app actions.

| Mode                                            | Who pays                          | Who controls logic                      |
| ----------------------------------------------- | --------------------------------- | --------------------------------------- |
| User-paid gas (default)                         | User (ETH or enabled stablecoins) | MegaETH relay                           |
| Partner sponsorship (`app-only` default)        | Developer                         | Sponsor endpoint + mode controls        |
| Partner sponsorship (`explicit` / `everything`) | Developer                         | Per-request or broad sponsorship policy |

## Integration Checklist

### 1. UX and Product Flows

* [ ] Define first-run journey: connect, sign, first transaction.
* [ ] Define cancellation behavior for all wallet prompts.
* [ ] Define silent/background operation boundaries and user consent language.
* [ ] Define fallback UX for disconnected state and RPC/network errors.

### 2. Permissions and Data Model

* [ ] Choose strict `grantPermissions` defaults (every `calls[]` entry includes both `to` and `signature`, low spend caps, short expiry).
* [ ] Decide session duration and automatic revocation policy.
* [ ] Define required on-chain contracts and method allowlists.
* [ ] Decide what wallet state is persisted client-side vs server-side.

### 3. Gas + Funding Strategy

* [ ] Choose primary path: user-paid token gas or partner sponsorship (`app-only`, `explicit`, `everything`).
* [ ] Define sponsorship budget ceilings and alert thresholds.
* [ ] If using external paymaster, define rate limits and contract policy checks.
* [ ] Confirm user messaging for "who pays gas" across all key flows.

### 4. Security and Compliance

* [ ] Use server-side ownership verification for auth/account linking.
* [ ] Confirm no private keys/session secrets are persisted in frontend storage.
* [ ] Validate logging policy excludes sensitive payloads.
* [ ] Create incident runbook for permission abuse or sponsorship drain attempts.

### 5. Launch Plan

* [ ] Stage in test environment, then run limited pilot rollout.
* [ ] Define launch KPIs (conversion, success rate, median completion time).
* [ ] Add monitoring for auth, transaction outcomes, and sponsorship spend.
* [ ] Prepare rollback criteria and decision owner.

## Related

* [Quickstart](/moss-docs/wallet/quickstart.md) — install through first transaction.
* [Paymaster Setup](/moss-docs/wallet/paymaster-setup.md) — implementation guide for built-in and external sponsorship paths.
* [Best Practices](/moss-docs/wallet/best-practices.md) — security patterns and permission defaults for production.

For scoping conversations: [integrations@megaeth.com](mailto:integrations@megaeth.com?subject=MOSS%20Integration%20Scoping%20Call).


---

# 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:

```
GET https://docs.megaeth.com/moss-docs/wallet/integration-checklist.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.