Wallet Update

You are helping a contributor populate or update feature data for a wallet in the Walletbeat project. The wallet they want to work on is: $ARGUMENTS (if blank, ask them which wallet before proceeding).

You have explicit permission to create and edit files inside data/contributors/ and data/ (including all subdirectories).

Your first actions

Before doing anything else:

1. If $ARGUMENTS is blank, ask: "Which wallet would you like to add feature data for?"
2. Identify the wallet type (software / hardware / embedded) if not obvious from the name.
3. Check that the wallet file already exists:
   • Software: data/software-wallets/[wallet-name].ts
   • Hardware: data/hardware-wallets/[wallet-name].ts
   • Embedded: data/embedded-wallets/[wallet-name].ts
   • If it does not exist, let the contributor know and suggest using /wallet-create first to register the wallet.
4. Ask: "What wallet data would you like to add or update?" (e.g., a specific feature, all null fields, a particular group of fields)
5. Ask: "What is your preferred display name or nickname?" and "Do you already have a contributor file in data/contributors/?"
   • If yes — confirm it exists. You only need to ensure they appear in the contributors: [] array of the wallet file.
   • If no — also ask for their affiliation (company / role, if any) and a URL to their profile. You will create the contributor file in Step A below.
6. Read the following files in parallel (skip files that don't exist):
   • The existing wallet file
   • The completed reference example: data/software-wallets/completed.tmpl.ts
   • The contributor guide: resources/docs/contribute/wallet-data/wallet-data.md
   • The example contributor file: data/contributors/example.ts (only if they need a new contributor file)

After reading these files, greet the contributor, summarize which wallet and fields you'll be working on, and begin.

Step A — Contributor file

Handle this before touching any feature data.

If the contributor already has a file

Confirm it exists and note the exported constant name. Make sure they appear in the wallet file's contributors: [] array. If not, add them.

If the contributor does not have a file yet

Create data/contributors/[their-nickname].ts using data/contributors/example.ts as the template.

Key rules:

• Affiliation must always be disclosed. If they work for or have equity in the wallet's company, set affiliation accordingly. If they have no affiliation, set affiliation: 'NO_AFFILIATION' — do not use [] or omit the field.
• Import the entity constant if they have an affiliation (it must already exist in data/entities/).

Example for an affiliated contributor:

import type { Contributor } from '@/schema/wallet'
import { myWalletCorp } from '@/data/entities/my-wallet-corp'

export const chainMonkey: Contributor = {
	name: 'Chain Monkey',
	affiliation: [
		{
			developer: myWalletCorp,
			hasEquity: true,
			role: 'EMPLOYEE', // or 'FOUNDER', 'ADVISOR', 'CONTRACTOR'
		},
	],
}

Example for an unaffiliated contributor:

import type { Contributor } from '@/schema/wallet'

export const chainMonkey: Contributor = {
	name: 'Chain Monkey',
	affiliation: 'NO_AFFILIATION',
}

Once the contributor file exists (confirmed or newly created), make sure they appear in the wallet file's contributors: [] array. Also update lastUpdated to today's date.

Step B — Populate feature fields

The goal is to replace every null field (or the specific fields the contributor identified) with real data gathered by testing the wallet and/or inspecting its source code.

General workflow for each field

For every null field:

1. Explain what the field measures (use TSDoc from the type definition — Control+Click on the field name in the editor to navigate to the type)
2. Describe how to test or verify it
3. Show the completed example value from data/software-wallets/completed.tmpl.ts if applicable
4. Let the contributor fill it in with a ref