For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connect wallets with Particle Connect

You want users to connect a smart-account wallet (social login, embedded wallet, or a standard EOA wallet) to your app on Lumia through Particle Connect.

Who this is for: developers adding wallet connection to a Lumia app. Prerequisites: Account Abstraction & Intents (concept: read this first for what a smart account is and why you'd want one; this page doesn't re-explain it); Networks & Endpoints.

About this integration

Particle Connect is Particle Network's third-party wallet and account-abstraction SDK (see /reference/sdks). It is a distinct product from Lumia's own internal account-abstraction work.

Steps

1

Install Particle Network's Connect SDK

For your framework. Consult Particle Network's own current published docs for the exact package name and version, since that's their product, not Lumia's.

2

Register a project with Particle Network

This gives you a project ID and client key. You create this account directly with Particle Network, outside Lumia's own systems.

3

Initialize the SDK's provider/connect-kit component

With your project credentials and Lumia's network config:

  • Chain ID: use the confirmed mainnet or Beam testnet chain ID from /reference/networks; never substitute the retired chain ID 1952959480.

  • RPC URL: from /reference/networks for the network you're targeting.

4

Configure which wallet connectors you want available

Social login, embedded/smart wallet, injected EOA wallets.

5

Render the SDK's connect button/modal

Read the connected address once a user completes the flow.

Verify it worked

After connecting, the SDK should return an address. Confirm that the relevant explorer (explorer.lumia.org or beam-explorer.lumia.org; see /reference/networks) shows activity matching what you expect, and that a test transaction sent from the connected account lands on the network you configured, not a different chain ID.

Troubleshooting

Connect modal opens but the resulting address is on the wrong chain

Double-check the chain ID passed at initialization against /reference/networks; a copy-pasted example from another chain's Particle Connect integration is the most common cause.

No connectors appear in the modal

The connector list is a project-level configuration in your Particle Network project dashboard, not something set purely client-side.

Last updated

Was this helpful?