Xpr Network Dev

XPR Network Developer Skill

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

Policy for AI agents (applies skill-wide): All chain writes documented in this skill use the proton CLI keychain for signing — private keys stay in the CLI's encrypted on-disk keystore, never in the agent's process memory or context. Reads use direct RPC (get_table_rows, get_account, etc.) and the relevant project's REST API. Do not introduce signing patterns that pass raw private keys to the agent (e.g. new JsSignatureProvider(['PRIV_KEY']), wallet.import_key('...'), XPR_PRIVATE_KEY in environment). See backend-patterns.md → Security: Key Isolation and ../agent-bootstrap.md for the canonical signing path.

AI-generated contract code: smart contracts are immutable once deployed and hold real assets, so treat any contract code produced with this skill as a draft. Before it reaches mainnet it needs testnet runs, review by a developer who knows XPR Network/EOSIO contracts, and, for anything holding significant value, a professional audit. The full checklist lives in safety-guidelines.md → AI-Generated Code Disclaimer.

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

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") is accepted but not credited; there is no contract path to recover it, only a discretionary manual refund by MetalX operators. Treat as 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.