← Back to Skills Marketplace
clawrencestreme

Streme Token Launcher

by clawrencestreme · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
1611
Downloads
1
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install streme-launcher
Description
Launch tokens on Streme (streme.fun) - the streaming token platform on Base. Use when deploying SuperTokens with built-in staking rewards, Uniswap V3 liquidity, and optional vesting vaults. Triggers on "launch token on streme", "deploy streme token", "create supertoken", or any Streme token deployment task.
README (SKILL.md)

Streme Token Launcher

Deploy SuperTokens on Base via Streme's V2 contracts. Tokens include automatic Uniswap V3 liquidity, Superfluid streaming staking rewards, and optional vesting vaults.

Quick Start

import { createWalletClient, http, parseEther, encodeAbiParameters } from 'viem';
import { base } from 'viem/chains';
import { privateKeyToAccount } from 'viem/accounts';

// See references/contracts.md for full ABIs
const DEPLOYER = '0x8712F62B3A2EeBA956508e17335368272f162748';

const tokenConfig = {
  _name: 'My Token',
  _symbol: 'MYTOKEN',
  _supply: parseEther('100000000000'), // 100B
  _fee: 10000, // 10%
  _salt: '0x0...', // from generateSalt()
  _deployer: walletAddress,
  _fid: 0n, // Farcaster FID or 0
  _image: 'https://example.com/image.png',
  _castHash: 'deployment',
  _poolConfig: {
    tick: -230400,
    pairedToken: '0x4200000000000000000000000000000000000006', // WETH
    devBuyFee: 10000
  }
};

// Deploy with 10% staking (1 day lock, 365 day stream)
const stakingAlloc = createStakingAllocation(10, 1, 365);
await deployWithAllocations(tokenConfig, [stakingAlloc]);

Contract Addresses (Base Mainnet)

Contract Address
STREME_PUBLIC_DEPLOYER_V2 0x8712F62B3A2EeBA956508e17335368272f162748
STREME_SUPER_TOKEN_FACTORY 0xB973FDd29c99da91CAb7152EF2e82090507A1ce9
STREME_ALLOCATION_HOOK 0xC907788f3e71a6eC916ba76A9f1a7C7C19384c7B
LP_FACTORY 0xfF65a5f74798EebF87C8FdFc4e56a71B511aB5C8
MAIN_STREME (for salt) 0x5797a398fe34260f81be65908da364cc18fbc360
WETH (Base) 0x4200000000000000000000000000000000000006

Deployment Flow

  1. Generate Salt - Call generateSalt() to get deterministic token address
  2. Upload Image - Host token image (see Image Hosting below)
  3. Build Config - Create tokenConfig and allocations
  4. Deploy - Call deployWithAllocations()

Image Hosting

Token images must be publicly accessible URLs. Options:

IPFS (Recommended)

// Using Pinata
const pinata = new PinataSDK({ pinataJwt: PINATA_JWT });
const { IpfsHash } = await pinata.pinFileToIPFS(fileStream);
const imageUrl = `https://gateway.pinata.cloud/ipfs/${IpfsHash}`;

Cloudinary

import { v2 as cloudinary } from 'cloudinary';

const result = await cloudinary.uploader.upload(imagePath, {
  folder: 'tokens',
  transformation: [{ width: 400, height: 400, crop: 'fill' }]
});
const imageUrl = result.secure_url;

Direct URL

Any publicly accessible image URL works:

const imageUrl = 'https://example.com/my-token.png';

Requirements

  • Format: PNG, JPG, GIF, WebP
  • Size: \x3C 5MB (\x3C 1MB recommended)
  • Dimensions: Square preferred (400x400 ideal)

Upload Script

# IPFS via Pinata
PINATA_JWT=xxx npx ts-node scripts/upload-image.ts pinata ./token.png

# Cloudinary
CLOUDINARY_CLOUD_NAME=xxx CLOUDINARY_API_KEY=xxx CLOUDINARY_API_SECRET=xxx \
  npx ts-node scripts/upload-image.ts cloudinary ./token.png

# imgBB (free)
npx ts-node scripts/upload-image.ts imgbb ./token.png

Allocations

Staking Allocation (Type 1)

Streams tokens to stakers over time.

function createStakingAllocation(
  percentage: number,    // % of supply (e.g., 10)
  lockDays: number,      // min stake duration
  flowDays: number,      // reward stream duration
  delegate?: string      // optional admin address
) {
  const lockSec = lockDays * 86400;
  const flowSec = flowDays * 86400;
  
  return {
    allocationType: 1,
    admin: delegate || '0x0000000000000000000000000000000000000000',
    percentage: BigInt(percentage),
    data: encodeAbiParameters(
      [{ type: 'uint256' }, { type: 'int96' }],
      [BigInt(lockSec), BigInt(flowSec)]
    )
  };
}

Vault Allocation (Type 0)

Locked tokens with optional vesting.

function createVaultAllocation(
  percentage: number,     // % of supply
  beneficiary: string,    // recipient address
  lockDays: number,       // lockup (min 7 days)
  vestingDays: number     // vesting after lock
) {
  const lockSec = Math.max(lockDays, 7) * 86400;
  const vestSec = vestingDays * 86400;
  
  return {
    allocationType: 0,
    admin: beneficiary,
    percentage: BigInt(percentage),
    data: encodeAbiParameters(
      [{ type: 'uint256' }, { type: 'uint256' }],
      [BigInt(lockSec), BigInt(vestSec)]
    )
  };
}

Allocation Rules

  • Staking + Vault percentages must be ≤100%
  • Remaining % goes to Uniswap V3 LP
  • Vault lock minimum: 7 days
  • Standard config: 10% staking, 90% LP

Token Config Defaults

Parameter Value
Supply 100,000,000,000 (100B)
Creator Fee 10000 (10%)
Dev Buy Fee 10000 (10%)
Tick -230400
Paired Token WETH

API Endpoints

# Get tokens by deployer
GET https://api.streme.fun/api/tokens/deployer/{address}

# Search all tokens
GET https://api.streme.fun/api/tokens

# Token details
GET https://api.streme.fun/api/tokens/{address}

Full Implementation

See scripts/deploy-token.ts for complete deployment script.

See references/contracts.md for full ABIs and type definitions.

Common Patterns

Standard Launch (10% staking)

const allocations = [createStakingAllocation(10, 1, 365)];

With Team Vault (10% staking + 10% vested)

const allocations = [
  createStakingAllocation(10, 1, 365),
  createVaultAllocation(10, teamAddress, 30, 365)
];

Max Liquidity (no allocations)

const allocations = [];
// 100% goes to Uniswap V3 LP
Usage Guidance
This package appears to implement a legitimate Streme token deployment flow, but there are two things you should not ignore: (1) The registry metadata claims no required environment variables, yet deploy-token.ts demands a PRIVATE_KEY (and upload-image.ts uses PINATA_JWT / CLOUDINARY_* / IMGBB keys). Supplying a private key lets the script sign and send real transactions — only use a key/wallet you control and are willing to risk (preferably a throwaway wallet with minimal funds), or use a safer signing workflow (hardware wallet, remote signer, or pre-signed transactions). (2) The source/homepage are unknown; you should manually review the included TypeScript before running it (especially the deploy script) and confirm contract addresses and RPC endpoints match official Streme/Base documentation. If you need higher assurance, ask the publisher for provenance (source repo, audit, or maintainer identity) or require the registry metadata be corrected to declare PRIMARY env vars. Additional info that would increase my confidence: an official upstream repository, a maintainer identity, registry metadata updated to list PRIVATE_KEY as the primary credential, or an audit/verification that the deployer address and contract ABIs are authentic.
Capability Analysis
Type: OpenClaw Skill Name: streme-launcher Version: 1.0.0 The skill is designed to deploy tokens on the Base blockchain and optionally upload images to hosting services. It requires sensitive environment variables like `PRIVATE_KEY` and API keys for image hosting, which are high-risk capabilities but are explicitly stated and necessary for its core function. All external network interactions are with legitimate blockchain RPCs, block explorers (e.g., `basescan.org`), or well-known image hosting services (e.g., `api.pinata.cloud`, `api.cloudinary.com`, `api.imgbb.com`). There is no evidence of prompt injection attempts in `SKILL.md` to subvert the agent, nor any indication of data exfiltration to unauthorized endpoints, persistence mechanisms, or other malicious intent. The code (`scripts/deploy-token.ts`, `scripts/upload-image.ts`) uses standard libraries and practices for its stated purpose.
Capability Assessment
Purpose & Capability
Name/description (launch tokens on Streme) match the included scripts (deploy-token.ts, upload-image.ts) and contract ABIs. However the registry metadata declares no required environment variables or primary credential, while the deployment script requires PRIVATE_KEY (and the upload script optionally requires PINATA_JWT / CLOUDINARY_*/IMGBB key). The missing declaration of sensitive creds is an important inconsistency.
Instruction Scope
The SKILL.md instructions are focused on deploying tokens and hosting images. Runtime steps (generating salt, uploading images, building config, calling deployWithAllocations) are within the stated purpose. The instructions do require running local scripts (npx ts-node) and setting environment variables, but they do not try to read unrelated system files or exfiltrate data to unexpected endpoints.
Install Mechanism
No install spec (instruction-only) and included code files — there is no download of remote binaries or archives, which reduces supply-chain risk. Users will execute the included TypeScript locally (requires Node/ts-node). This is low technical install risk but means you must trust the shipped code before running.
Credentials
The actual code requires a sensitive PRIVATE_KEY env var to sign and send chain transactions, plus optional third‑party upload credentials (PINATA_JWT, CLOUDINARY_API_KEY/SECRET, IMGBB_API_KEY). Those are reasonable for a deployer/uploader, but the skill's declared requirements list no env vars or primary credential — a mismatch that could mislead users about what secrets they'll need to provide. Requesting a deployer private key is high sensitivity; ensure you only use a wallet with minimal funds or a secure signing approach.
Persistence & Privilege
The skill does not request persistent platform privileges (always:false), does not modify other skills, and includes no autonomous installation behavior. It operates as a local invocation script when run, which is appropriate for its purpose.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install streme-launcher
  3. After installation, invoke the skill by name or use /streme-launcher
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
streme-launcher 1.0.0 – Initial Release - Launch tokens on Streme (streme.fun) using V2 contracts on Base. - Supports deploying SuperTokens with built-in Uniswap V3 liquidity, Superfluid staking rewards, and optional vesting vaults. - Provides allocation helpers for staking and vesting configurations. - Includes deployment guides, contract addresses, image hosting instructions, and API endpoints. - Example scripts and patterns for standard, team-vested, and LP-max launch scenarios.
Metadata
Slug streme-launcher
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Streme Token Launcher?

Launch tokens on Streme (streme.fun) - the streaming token platform on Base. Use when deploying SuperTokens with built-in staking rewards, Uniswap V3 liquidity, and optional vesting vaults. Triggers on "launch token on streme", "deploy streme token", "create supertoken", or any Streme token deployment task. It is an AI Agent Skill for Claude Code / OpenClaw, with 1611 downloads so far.

How do I install Streme Token Launcher?

Run "/install streme-launcher" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Streme Token Launcher free?

Yes, Streme Token Launcher is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Streme Token Launcher support?

Streme Token Launcher is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Streme Token Launcher?

It is built and maintained by clawrencestreme (@clawrencestreme); the current version is v1.0.0.

💬 Comments