XPR Network Developer Skill

This skill provides comprehensive knowledge for developing on XPR Network, a fast, gas-free blockchain with WebAuthn wallet support.

IMPORTANT DISCLAIMER: AI-Generated Smart Contract Code

Smart contracts handle real assets and are immutable once deployed. AI-generated code, including code produced with this skill, should always be reviewed by an experienced developer before deployment to mainnet.

• Test thoroughly on testnet before any mainnet deployment
• Have code reviewed by someone familiar with XPR Network/EOSIO smart contracts
• Audit critical contracts - consider professional security audits for contracts handling significant value
• Understand the code - don't deploy code you don't fully understand

Claude can accelerate development and help with patterns, but it does not replace proper code review, testing, and auditing practices.

XPR Network Overview

XPR Network is an EOS-based blockchain optimized for payments and identity:

Name Change: Proton → XPR Network

The blockchain was rebranded from Proton to XPR Network in 2024. You may see legacy references to "Proton" in:

• Package names (@proton/cli, @proton/web-sdk, proton-tsc)
• GitHub organization (XPRNetwork, formerly ProtonProtocol)
• Documentation and code comments
• Explorer (now explorer.xprnetwork.org, formerly protonscan.io and proton.bloks.io)

The token symbol remains XPR and all functionality is unchanged.

Chain IDs

Progressive Disclosure

Load specialized modules based on your task:

Core Development

Token & Identity

DeFi & Trading

Integration Patterns

Infrastructure

Safety & Reference

CRITICAL: Before Modifying Contracts

Read: safety-guidelines.md

• NEVER modify existing table structures with data
• Pre-deployment checklist
• Recovery procedures

Quick Reference

Common CLI Commands

# Install CLI
npm i -g @proton/cli

# Set network
proton chain:set proton          # Mainnet
proton chain:set proton-test     # Testnet

# Account info
proton account myaccount -t      # With token balances

# Query table
proton table CONTRACT TABLE

# Execute action
proton action CONTRACT ACTION 'JSON_DATA' AUTHORIZATION

# Deploy contract
proton contract:set ACCOUNT ./assembly/target

Common RPC Query

import { JsonRpc } from '@proton/js';
const rpc = new JsonRpc('https://proton.eosusa.io');

const { rows } = await rpc.get_table_rows({
  code: 'CONTRACT',
  scope: 'CONTRACT',
  table: 'TABLE',
  limit: 100
});

Basic Contract Structure

import { Contract, Table, TableStore, Name, requireAuth } from 'proton-tsc';

@table("mydata")
class MyData extends Table {
  constructor(
    public id: u64 = 0,
    public owner: Name = new Name(),
    public value: string = ""
  ) { super(); }

  @primary
  get primary(): u64 { return this.id; }
}

@contract
class MyContract extends Contract {
  dataTable: TableStore<MyData> = new TableStore<MyData>(this.receiver);

  @action("store")
  store(owner: Name, value: string): void {
    requireAuth(owner);
    const row = new MyData(this.dataTable.availablePrimaryKey, owner, value);
    this.dataTable.store(row, this.receiver);
  }
}

Basic Frontend Login

import '@proton/link';  // Required for mobile wallet support
import ProtonWebSDK from '@proton/web-sdk';

const { link, session } = await ProtonWebSDK({
  linkOptions: {
    chainId: '384da888112027f0321850a169f737c33e53b388aad48b5adace4bab97f437e0',
    endpoints: ['https://proton.eosusa.io']
  },
  selectorOptions: { appName: 'My App' }
});

// session.auth contains { actor, permission }
// Use session.transact() for transactions

Key Packages

Official Resources

• Documentation: https://docs.xprnetwork.org
• GitHub: https://github.com/XPRNetwork
• Block Explorer: https://explorer.xprnetwork.org
• Resources Portal: https://resources.xprnetwork.org (buy RAM, etc.)

Safety Reminders

1. NEVER modify existing table structures once deployed with data - this breaks deserialization
2. Always test on testnet before mainnet deployment
3. Verify the target account before deploying - wrong account = overwrite existing contract
4. Back up ABIs before deploying changes
5. Use new tables for new features instead of modifying existing ones
6. DEX deposits MUST use empty memo ("") — any other memo (e.g. "deposit") causes permanent, irrecoverable fund loss. See metalx-dex.md.
7. All-numeric account names (e.g. 333555) cause silent data loss in get_table_rows — see rpc-queries.md for workarounds.