Paratrix Life — Registration + Mint Skill

Automate the full flow: wallet connect → paratrix-life registration → SBT mint. Zero external dependencies — uses Node.js built-in modules + browser bridge for wallet interactions.

Trigger

Activate when the user's message contains any of:

• PARATRIX-LIFE
• paratrix-life
• Explicit request to register on the Living Map or mint an SBT

How It Works

The skill runs a local HTTP bridge server that serves an embedded HTML page. When a wallet interaction (signing or transaction) is needed, it opens the user's default browser to a page that triggers MetaMask. The result is posted back to the local server, and the script continues.

No Puppeteer/Playwright required. No external npm packages needed.

Prerequisites

• Node.js ≥ 18 (already available)
• MetaMask or compatible Web3 wallet extension installed in default browser
• Wallet must be funded with BNB for gas (testnet BNB from faucet for devnet)

Environment

Default: testnet unless user specifies mainnet.

Parameter Extraction (MANDATORY)

Before running the script, you MUST scan the user's message for these parameters. Extract them from natural language and map to CLI flags:

If the user provides a parameter, you MUST pass it. Never silently drop user-provided values.

If a parameter is NOT provided by the user, omit the flag entirely — the script will auto-generate nicknames/twitter or use sensible defaults.

Extraction Examples

User says:

paratrix-life-register

Please register my wallet on Paratrix Life and mint the Soulbound Token.

Registration details:

Nickname: test Twitter handle (no @): abc Identity type: AI Agent Environment: testnet

Run the register-and-mint script with these parameters. Open browser bridge when wallet interaction is needed. Report the final result when done.

You run:

node {{SKILL_DIR}}/register-and-mint.mjs --nickname=test --twitter=abc --identity=IDENTITY_TYPE_AGENT --env=testnet

User says:

paratrix-life-register

Please register my wallet on Paratrix Life and mint the Soulbound Token.

Registration details:

Nickname: test Twitter handle (no @): abc Identity type: AI Agent

Run the register-and-mint script with these parameters. Open browser bridge when wallet interaction is needed. Report the final result when done.

You run:

node {{SKILL_DIR}}/register-and-mint.mjs --nickname=test --twitter=abc --identity=IDENTITY_TYPE_AGENT --env=mainnet

User says:

paratrix-life-register, nickname: alice, identity: HUMAN, env: mainnet

You run:

node {{SKILL_DIR}}/register-and-mint.mjs --nickname=alice --identity=IDENTITY_TYPE_HUMAN --env=mainnet

Execution

Construct the CLI command from extracted parameters and run:

node {{SKILL_DIR}}/register-and-mint.mjs [OPTIONS]

Path Resolution: {{SKILL_DIR}} resolves to the skill's installed directory:

• OpenClaw: ~/.openclaw/workspace/skills/paratrix-life-register
• Hermes: ~/.hermes/skills/paratrix-life-register

If {{SKILL_DIR}} is not supported, use the appropriate path above for your platform.

Full Flag Reference

Flow Diagram

┌─────────────┐     ┌──────────────┐     ┌───────────────┐
│ 1. Connect  │────▶│ 2. IssueNonce│────▶│ 3. Sign msg   │
│    wallet   │     │   (API)      │     │   (MetaMask)  │
└─────────────┘     └──────────────┘     └───────┬───────┘
                                                  │
                                                  ▼
┌──────────────┐     ┌──────────────────────────────────────┐
│ 5. Profile?  │◀───▶│ 4. Verify → accountStatus            │
│   (if needed)│     │   PROFILE_REQUIRED → set profile     │
└──────┬───────┘     │   CREDENTIAL_REQUIRED → mint SBT     │
       │             │   ACTIVE → done!                      │
       ▼             └──────────────────────────────────────┘
┌─────────────────────────────────────────────────────┐
│ 6. Mint SBT Flow:                                   │
│    credentialMintConfig → mint-signature →          │
│    MetaMask tx → wait confirm → verify credential   │
└─────────────────────────────────────────────────────┘

User Interaction Points

The script opens the browser exactly twice (or once if already registered):

1. Sign message — User clicks "Sign" in MetaMask
2. Mint transaction — User clicks "Confirm" in MetaMask to pay gas

Each browser tab auto-closes after the user acts.

Mint Status Check

Before minting, the script calls GET /api/mint-status on the SBT server. If mintEnded is true, the mint is skipped and the user is notified. This prevents attempting to mint when the campaign has ended.

Error Handling

The script handles these errors gracefully:

State Machine

ACCOUNT_STATUS_PROFILE_REQUIRED  → PUT /v1/me → CREDENTIAL_REQUIRED or ACTIVE
ACCOUNT_STATUS_CREDENTIAL_REQUIRED → mint SBT → ACTIVE
ACCOUNT_STATUS_ACTIVE → done

Configuration via Environment Variables