[UX/Docs BUG] Disconnect between Passkey Accounts and Faucet/Remix Flow

[Isaaco3349]

Describe the bug

Hi Tempo Team,

I am representing a community of testers currently interacting with the Moderato testnet. We’ve identified a significant point of confusion in the current documentation/UX flow that is causing high user drop-off.

The Issue: "Address Fragmentation"
Website/UI Flow: When users follow the "Send a Payment" guide, the website prompts them to create a Passkey account. This generates a new Smart Account address (e.g., 0x123...).

Faucet Flow: The Faucet section currently triggers a connection to an EVM Wallet (MetaMask/OKX). This claims funds to the EOA address (e.g., 0xabc...).

Remix/Dev Flow: Documentation for deploying contracts still points to using the EVM wallet method via Remix.

The Result:
Users claim funds to their MetaMask address but find their Passkey-based "Payment" account has 0 balance. They are unable to carry out the transactions described in the "Send a Payment" guide because the faucet does not easily fund the Passkey account.

Suggested Fixes for Docs:
Faucet Clarity: Update the Faucet guide to explain that if using Passkeys, users must manually copy their Passkey address into the faucet instead of just clicking "Connect Wallet."

Remix Guide: Add a section on how to interact with Passkey-deployed contracts, or clarify that Remix and the Website use two distinct account types.

Unified Onboarding: A warning note in the "Payments" guide explaining the difference between the EOA (MetaMask) and the Smart Account (Passkey).

I am happy to help provide "User Feedback" logs or help draft a "Common Misconceptions" FAQ for the docs to help clear this up for new testers!

Steps to reproduce

Steps to Reproduce
Initialize Passkey Account: Go to the official Tempo Payments Guide and follow the steps to create a new account using the Passkey method.

Identify Passkey Address: Once the Passkey account is created, note the unique Smart Account address generated by the website (e.g., 0x123...).

Attempt to Fund via Faucet: Navigate to the Faucet section of the documentation to claim testnet tokens.

Observe Wallet Conflict: Notice that the Faucet triggers a "Connect Wallet" prompt (MetaMask/OKX), which connects to a traditional EOA address (e.g., 0xabc...) instead of the Passkey address created in Step 1.

Execution Failure: Attempt to "Send a Payment" using the website interface.

Result: The transaction fails or cannot be initiated because the Passkey account has a 0 balance, while the testnet funds are sitting in the unconnected MetaMask/EOA wallet.

Logs

I do not have specific contract event logs as the issue is a logical disconnect between the Documentation and the UI flow. However, the 'Address Mismatch' can be verified by observing the different addresses in the browser console.

Platform(s)

Windows (x86)

Container Type

Not running in a container

What version/commit are you on?

Latest live version of the official documentation (docs.tempo.xyz) as of February 24, 2026.

If you've built from source, provide the full command you used

N/A - Using the live hosted version at docs.tempo.xyz

Code of Conduct

• I agree to follow the Code of Conduct