Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Agent Wallet: document private support and recovery for ambiguous server-wallet swaps

Aperta
  • Qualcosa non va?
#3,070 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
markdown
Ambito
documentation, security

Direzione di ricerca

Start by locating the Agent Wallet troubleshooting documentation and identify its current support links and recovery guidance. The issue asks for verified private escalation and authoritative recovery semantics for ambiguous server-wallet swaps, including job identifiers, transaction status, and nonce behavior. Done means documenting a verified support route and recovery process; the issue does not name specific files or tests.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Scope: support routing and recovery documentation

Please route this to the Agent Wallet documentation/server-wallet owner. This issue requests a verified private engineering support channel and documented recovery semantics. It does not request a trade, cancellation, wallet reset or policy change.

Observed problem

With @metamask/agent-wallet 7.0.0, using an EVM server wallet, our outer subprocess timeout interrupted a swap command after the approval transaction had confirmed. Our old wrapper discarded partial output, leaving no recorded trade request/polling ID or trade transaction hash. We have prepared and offline-tested a local output-preservation repair, but have not deployed it or retried the swap: that repair cannot resolve a previously accepted remote job.

The supported swap-status projection returned QUOTED with no hashes. An empty/local request listing or unchanged on-chain state is not sufficient to establish that the server never accepted a job.

Support route is unclear/inaccessible

The official MetaMask Support chat received the report but said it could not transfer the request or take action for Agent Wallet. It directed us to the generic https://github.com/MetaMask organization page.

The installed package advertises:

  • Repository: https://github.com/MetaMask/agentic.git
  • Issues: https://github.com/MetaMask/agentic/issues
  • Homepage: https://github.com/MetaMask/agentic-cli#readme

The MetaMask/agentic and MetaMask/agentic-cli repository API lookups both return 404 to our already-authenticated GitHub account. They may be private or unavailable; signing in alone does not resolve the routing gap.

Requested documentation / engineering guidance
  1. Identify the official private channel for correlation of a server-wallet execution by wallet, chain, quote ID and execution interval when no trade polling ID reached the client.
  2. Document how to recover an accepted job's public ID, payload/nonce, broadcast hash and authoritative terminal status, or obtain correlation-backed confirmation that no job was accepted.
  3. Clarify whether an explicit transaction nonce remains immutable through server retries/nonce-conflict handling, and whether an accepted job can be re-prepared or re-signed at a fresh nonce without a new client request.
  4. Link that support/recovery route from the Agent Wallet troubleshooting documentation, rather than leaving users to infer cancellation from a CLI timeout or resubmit an ambiguous swap.

No wallet addresses, quote/request IDs, transaction hashes, account details, balances, credentials or raw logs are included in this public report. Exact correlation identifiers can be supplied through a verified private MetaMask channel. We have not retried, cleared the unknown-submission guard or changed wallet policy.

Lingua principale
MDX
Stelle
864
Fork
2.1k
Merge medio
1h 27m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di MetaMask/metamask-docs

Tutte le issue di MetaMask/metamask-docs

Issue simili

Altre issue su Documentation

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.