Talisman Portal

Unlock the Paraverse with Talisman Portal.
A Polkadot, Kusama & Parachain dashboard for the community.

With Talisman Portal you can buy DOT and KSM, contribute to crowdloans, view NFTs and more.

Want more?
Talisman Polkadot Wallet | Blog | Docs | Twitter | Discord

How to set up a development environment

1. Clone the repo:

git clone https://github.com/TalismanSociety/talisman-web.git

2. Use the project targeted Node version using nvm (Optional but will ensure no funny business with pnpm)

nvm use

3. Install pnpm. It downloads the version pinned in package.json on first use.

4. Install the project dependencies:

pnpm install

5. Copy .env.example to .env and update the values inside:

cp apps/portal/.env.example apps/portal/.env

6. Start the dev server:

pnpm dev

Test and verify

• pnpm test runs the unit tests. Tests sit next to their code as *.test.ts or *.test.tsx and run in jsdom. To run the tests of one file or folder, pass its path, as in pnpm test apps/portal/src/domains.
• pnpm verify runs Biome, typecheck, knip, the tests and the portal build. Run it before you push. It needs no env file. CI’s qa / validate job runs pnpm verify, then the audit gate pnpm audit --prod --audit-level high.
• For a change that a user can see, drive the portal in a real browser with the verify skill, .claude/skills/verify/SKILL.md, and run its visual parity check.
• knip ignores these on purpose: wrangler (Cloudflare Workers Builds runs it), dotenv (loaded by codegen:nova through --require), and @polkadot/api with @polkadot/util-crypto, which the verify skill’s smoke-chain.mjs loads from its own install under .tmp/ (the portal itself has no polkadot.js: Biome bans its imports and apps/portal/src/lockfile.test.ts fails if it reaches the lockfile).