The Sequence Enchanter is a Web Application that allows users to create and interact with Sequence Wallets. Sequence Wallets are Smart Contract Wallets that exist across all fully compatible EVM Networks.
A hosted version of the application can be found at: https://0xsequence.github.io/enchanter/
To run the application locally, follow these steps:
git clone https://github.com/0xsequence/enchanter.git
cd enchanter
pnpm install
pnpm dev
The application will be available at http://localhost:5174.
Creating a wallet is as simple as clicking the "Create Wallet" button on the home page. This will generate a new Sequence Wallet for you to interact with. The Sequence wallet is ready to be used from the moment it is created, there is no need to deploy it to the network.
The creation form supports both Sequence v3 and v2 wallets and defaults to v3. This selects the contracts used by the new counterfactual wallet; it does not migrate or otherwise change existing wallets. Imported v2 and v3 wallets continue to use their original protocol.
By default, there is a list of compatible networks that the wallet can be used on. The wallet can be used on any network that is fully compatible with the EVM, if the network is not listed, please double check compatibility before using the wallet.
Wallets can be imported by other users just by sharing the wallet address, notice that the name of the wallet is not shared, it is only stored locally on the user's device.
Sequence Wallets are fully determinist, this means that two wallets with identical configurations will have the same address. To avoid this, Sequence implements a "salt" (internally mapped to the 'checkpoint' of the wallet). The salt randomizes the wallet address, making it unique.
By default the application will generate a different salt every second, making it in essence unique. A custom salt can be provided during wallet creation.
To send a transaction, click the "Send Transaction" button on the wallet page, notice that a wallet must be created/imported and selected before sending a transaction.
Transactions are order-independent by default, this means that they can be signed and executed in any order.
Transactions don't automatically synchronize across devices, when a transaction is signed on one device, the data of the transaction must be exported and imported on all other devices for the signatures to be synchronized. This can be done by clicking the "Export" and "Import" buttons on the transaction page.
The Playwright suite covers the supported UI, real v2 tracker and v3 Keymachine flows, portable data, authorization states, and deterministic NFT composition. The complete flow inventory is in tests/FLOWS.md.
Install Chromium once, then run the non-funded suite:
pnpm exec playwright install chromium
pnpm test:e2eFunded tests deploy fresh v2 and v3 wallets on Polygon Amoy, transfer native value, and commit signer updates on-chain. Use a dedicated Amoy-only test key; never use a production or mainnet key:
E2E_PRIVATE_KEY=0x... pnpm test:e2e:fundedThe injected browser provider receives only the account address and chain ID. Private-key signing and transaction submission remain in the Playwright Node fixture. Funded tests run serially and intentionally consume testnet POL.