- token deploy - Deploy a new Netr token
- token info - Get information about a Netr token

##### Token Deploy

Deploy a new memecoin with automatic Uniswap V3 pool creation and locked liquidity.

`bash
netp token deploy \
--name \
--symbol \
--image \
[--animation ] \
[--fid ] \
[--private-key <0x...>] \
[--chain-id <8453|9745|143|999>] \
[--encode-only]
`

Token Deploy Arguments:

- --name (required): Token name
- --symbol (required): Token symbol
- --image (required): Token image URL
- --animation (optional): Token animation URL
- --fid (optional): Farcaster ID
- --initial-buy (optional): ETH amount to swap for tokens on deploy (e.g., "0.001")
- --private-key (optional): Private key. Can also be set via NET_PRIVATE_KEY environment variable
- --chain-id (optional): Chain ID. Supported: Base (8453), Plasma (9745), Monad (143), HyperEVM (999)
- --encode-only (optional): Output transaction data as JSON instead of executing

Example:

`bash


Deploy token

`bash
netp token info \
--address \
[--chain-id <8453|9745|143|999>] \
[--json]
`

Example:

`bash
netp token info \
--address 0x1234567890abcdef1234567890abcdef12345678 \
--chain-id 8453 \
--json
`

#### Profile Command

Profile operations for managing your Net Protocol profile.

Available Subcommands:

- profile get - Get profile data for an address
- profile set-picture - Set your profile picture URL
- profile set-x-username - Set your X (Twitter) username
- profile set-bio - Set your profile bio
- profile set-canvas - Set your profile canvas (HTML content)
- profile get-canvas - Get profile canvas for an address

##### Profile Get

Read profile data for any address.

`bash
netp profile get \
--address \
[--chain-id <8453|1|...>] \
[--rpc-url ] \
[--json]
`

Profile Get Arguments:

- --address (required): Wallet address to get profile for
- --chain-id (optional): Chain ID. Can also be set via NET_CHAIN_ID environment variable
- --rpc-url (optional): Custom RPC URL. Can also be set via NET_RPC_URL environment variable
- --json (optional): Output in JSON format

Example:

`bash


Human-readable output

`bash
netp profile set-picture \
--url \
[--private-key <0x...>] \
[--chain-id <8453|1|...>] \
[--rpc-url ] \
[--encode-only]
`

Profile Set Picture Arguments:

- --url (required): Image URL for profile picture (HTTPS, IPFS, etc.)
- --private-key (optional): Private key. Can also be set via NET_PRIVATE_KEY environment variable
- --chain-id (optional): Chain ID. Can also be set via NET_CHAIN_ID environment variable
- --rpc-url (optional): Custom RPC URL. Can also be set via NET_RPC_URL environment variable
- --encode-only (optional): Output transaction data as JSON instead of executing

Example:

`bash


Set profile picture

`bash
netp profile set-x-username \
--username \
[--private-key <0x...>] \
[--chain-id <8453|1|...>] \
[--rpc-url ] \
[--encode-only]
`

Profile Set X Username Arguments:

- --username (required): Your X (Twitter) username (with or without @, stored without @)
- --private-key (optional): Private key. Can also be set via NET_PRIVATE_KEY environment variable
- --chain-id (optional): Chain ID. Can also be set via NET_CHAIN_ID environment variable
- --rpc-url (optional): Custom RPC URL. Can also be set via NET_RPC_URL environment variable
- --encode-only (optional): Output transaction data as JSON instead of executing

Example:

`bash


Set X username (@ is optional, will be stripped before storage)

`bash
netp profile set-bio \
--bio \
[--private-key <0x...>] \
[--chain-id <8453|1|...>] \
[--rpc-url ] \
[--encode-only]
`

Profile Set Bio Arguments:

- --bio (required): Your profile bio (max 280 characters, no control characters)
- --private-key (optional): Private key. Can also be set via NET_PRIVATE_KEY environment variable
- --chain-id (optional): Chain ID. Can also be set via NET_CHAIN_ID environment variable
- --rpc-url (optional): Custom RPC URL. Can also be set via NET_RPC_URL environment variable
- --encode-only (optional): Output transaction data as JSON instead of executing

Example:

`bash


Set bio

`bash
netp profile set-canvas \
--file | --content \
[--private-key <0x...>] \
[--chain-id <8453|1|...>] \
[--rpc-url ] \
[--encode-only]
`

Profile Set Canvas Arguments:

- --file (optional): Path to file containing canvas content (HTML, images, etc.)
- --content (optional): HTML content for canvas (inline). Must provide either --file or --content, but not both.
- --private-key (optional): Private key. Can also be set via NET_PRIVATE_KEY environment variable
- --chain-id (optional): Chain ID. Can also be set via NET_CHAIN_ID environment variable
- --rpc-url (optional): Custom RPC URL. Can also be set via NET_RPC_URL environment variable
- --encode-only (optional): Output transaction data as JSON instead of executing

Notes:
- Maximum canvas size is 60KB
- Binary files (images) are automatically converted to data URIs
- Content is compressed using gzip before storage

Example:

`bash


Set canvas from file

`bash
netp profile get-canvas \
--address \
[--output ] \
[--chain-id <8453|1|...>] \
[--rpc-url ] \
[--json]
`

Profile Get Canvas Arguments:

- --address (required): Wallet address to get canvas for
- --output (optional): Write canvas content to file instead of stdout
- --chain-id (optional): Chain ID. Can also be set via NET_CHAIN_ID environment variable
- --rpc-url (optional): Custom RPC URL. Can also be set via NET_RPC_URL environment variable
- --json (optional): Output in JSON format (includes metadata like size and type)

Notes:
- Binary content (data URIs) is automatically converted to binary files when using --output
- JSON output includes: canvas content, filename, size, and whether it's a data URI

Example:

`bash


Output to stdout

`bash
netp info [--chain-id ] [--json]
`

#### Chains Command

List supported chains.

`bash
netp chains [--json]
`

Storage Types

$3

For files up to 20KB, the tool uses normal storage:

- Stores data directly in Storage.sol
- Single transaction
- Simple key-value storage

$3

For files larger than 20KB or containing XML references, the tool uses XML storage:

- Breaks file into 80KB XML chunks
- Each XML chunk is stored in ChunkedStorage (compressed and chunked into 20KB pieces)
- XML metadata references all chunks
- Multiple sequential transactions (metadata first, then chunks)

Idempotency

The storage command includes built-in idempotency checks:

1. Pre-flight Checks: Before uploading, checks if data already exists
2. Content Comparison: For normal storage, compares file content with stored content
3. Chunk-Level Deduplication: For XML storage, checks each chunk individually
4. Per-Transaction Checks: Before sending each transaction, verifies data doesn't already exist

$3

If an upload fails mid-way:

- Retry the same command
- The tool will check which chunks already exist
- Only missing chunks will be uploaded
- Safe to retry multiple times

$3

`bash


First upload

`
src/
├── cli/
│ ├── index.ts # Main entry point, sets up commander program
│ └── shared.ts # Shared option parsing and validation
├── commands/
│ ├── storage/ # Storage command module
│ │ ├── index.ts # Storage command definition
│ │ ├── core/ # Upload and preview logic
│ │ ├── storage/ # Storage operations
│ │ ├── transactions/ # Transaction handling
│ │ ├── utils.ts # Storage-specific utilities
│ │ └── types.ts # Storage-specific types
│ ├── profile/ # Profile command module
│ │ ├── index.ts # Profile command definition
│ │ ├── get.ts # Profile get logic
│ │ ├── set-picture.ts # Set profile picture
│ │ ├── set-username.ts # Set X username
│ │ └── types.ts # Profile-specific types
│ ├── message/ # Message command module
│ └── token/ # Token command module
└── shared/ # Shared utilities across commands
└── types.ts # Common types (CommonOptions, etc.)
`

$3

- cli/index.ts: Main CLI entry point that sets up the commander program and registers all commands
- cli/shared.ts: Shared utilities for parsing common options (private-key, chain-id, rpc-url) that are available to all commands
- commands/{name}/index.ts: Each command module exports a register{Name}Command() function that defines the command's options and behavior
- shared/types.ts: Common types shared across commands (e.g., CommonOptions)

$3

Each command can have its own internal structure:

- core/: Core business logic for the command
- storage/: Storage-specific operations (if applicable)
- transactions/: Transaction preparation, filtering, and sending
- utils.ts: Command-specific utility functions
- types.ts: Command-specific types

Extensibility

$3

To add a new top-level command:

1. Create command directory: src/commands/{name}/
2. Create command index: src/commands/{name}/index.ts with a register{Name}Command(program: Command) function
3. Register in main CLI: Import and call register{Name}Command(program) in src/cli/index.ts
4. Add command-specific code: Create subdirectories as needed (core/, storage/, transactions/, etc.)

$3

To add a new subcommand to the storage command group:

1. Create subcommand: Use new Command("subcommand-name") in src/commands/storage/index.ts
2. Add options: Use .requiredOption() or .option() to define subcommand options
3. Add action: Use .action() to define the subcommand behavior
4. Register: Use storageCommand.addCommand(subcommand) to register it

Example:

`typescript
// In src/commands/storage/index.ts
const verifyCommand = new Command("verify")
.description("Verify storage integrity")
.requiredOption("--key ", "Storage key to verify")
.action(async (options) => {
// Implementation
});

storageCommand.addCommand(verifyCommand);
`

$3

`typescript
// src/commands/mycommand/index.ts
import { Command } from "commander";
import { parseCommonOptions } from "../../cli/shared";

export function registerMyCommand(program: Command): void {
program
.command("mycommand")
.description("Description of my command")
.option("--my-option ", "My option")
.action(async (options) => {
const commonOptions = parseCommonOptions({
privateKey: options.privateKey,
chainId: options.chainId,
rpcUrl: options.rpcUrl,
});

// Command logic here
});
}

// src/cli/index.ts
import { registerMyCommand } from "../commands/mycommand";

// ... existing code ...
registerMyCommand(program);
`

$3

All commands automatically have access to common options:

- --private-key (or NET_PRIVATE_KEY env var)
- --chain-id (or NET_CHAIN_ID env var)
- --rpc-url (or NET_RPC_URL env var)

These are parsed and validated by parseCommonOptions() from cli/shared.ts.

Security & Environment Variables

⚠️ Warning: Private keys are sensitive. Always use environment variables instead of passing the private key via command line:

`bash


Set environment variable

The tool supports both NET_PRIVATE_KEY and PRIVATE_KEY environment variables. If neither is set, you must provide --private-key flag.

Development

`bash


Install dependencies (from repo root)

- bazaar list-listings - List active NFT listings
- bazaar list-offers - List active collection offers
- bazaar list-sales - List recent sales
- bazaar owned-nfts - List NFTs owned by an address
- bazaar create-listing - Create an NFT listing
- bazaar create-offer - Create a collection offer
- bazaar submit-listing - Submit a signed listing
- bazaar submit-offer - Submit a signed offer
- bazaar buy-listing - Buy an NFT listing
- bazaar accept-offer - Accept a collection offer

##### Read Commands

`bash


List active listings (--nft-address optional for cross-collection)