minimal

off. on. let go.

minimal / terminal

checking protocol status…

off. on. let go.

start with help or stats. connect when you are ready.

click an example to edit it. letgo is one word. nothing runs until you press enter.

enter to run · ↑ ↓ history · review before signingcontracts ↗
contracts & on-chain infoaddresses · copy · explorer

contracts

checking deployment network…

$minimal token

the token bound to off

checking token binding…

off

locks, withdrawals and eth rewards

no deployment published

let go

token burns and permanent words

no deployment published

explorer links show deployed code, transactions and source verification status. read the permissions and limitations →

how it worksstart here · read, connect, review

how it works

start with a read-only action. connect a wallet only when you want to participate.

  1. look around

    open public records for fees, transfers and the word board. no wallet is required.

  2. connect when you're ready

    use . ledger works through metamask. shows the stockereum market after token binding.

  3. type a command and review

    try in the terminal. edit the amount and duration, run it, then read the plan before confirming. your wallet asks before signing.

locking periods & rewards

1 day · 1× / 3 days · 1.5× / 7 days · 2× reward weight.

let go burns at least 1,000 minimal and leaves one permanent word.

your share depends on the number of tokens locked and the selected weight. eth comes from manually claimed creator fees and public funding. there is no fixed return.

funded eth streams over time, using a 24-hour stream duration. the clock pauses when no position has reward weight.

expiry, early exit & emergency mode

after expiry, exit without penalty. anyone can use poke <address> to stop an expired position from earning; already-earned rewards stay yours. to earn again, exit and create a new lock.

early exit burns 10% of the locked tokens and forfeits earned rewards. emergency mode permits penalty-free exits with earned rewards retained.

where do the fees come from?

the planned 2% stockereum trading fee is split into 1% for the platform and 1% for the creator. the project commits the creator share to off. claiming depends on the original token creator; it is not automatic.

the creator claims weth directly into off. anyone can then unwrap it into the eth reward stream with fundWeth(). public records show the transfers.

command examples

these examples only fill the terminal. edit the amount, then run the command when ready.

public recordsfees, funding history and words

public records

follow the fees and read what people leave behind. no wallet needed.

follow the fees

creator fees are claimed manually, then funded into off. check what has arrived and what is still waiting.

creator fees in escrow, unclaimed…
total eth transferred into off…
last transfer into off…
minimal locked in off…
minimal burned…
funding historytransfers into off
load the history to see funding transfers and transaction links.
the word boardwords left on-chain
words are public and permanent. load the board without connecting a wallet.
use the cliinstall and run on your own computer

use the cli

install once. use the same commands locally.

the same commands, on your computer. node.js 20 or newer is required. read-only commands need no wallet; signing also needs foundry's cast.

this download contains the cli source and the public configuration for this deployment. re-download after a new protocol deployment. no private keys or rpc api keys are included.

preparing install command…
minimal help
minimal stats
minimal status 0xYourWalletAddress
run once with npx, without a global install
preparing npx command…
sign with a keystore or ledger

import your wallet locally into an encrypted foundry keystore. never paste a private key into this website.

cast wallet import minimal-user --interactive
minimal off 1000 1d --account minimal-user
minimal on --account minimal-user
minimal letgo noise --ledger

the cli prints the plan and asks for y/n before signing. use --rpc <url> for your own endpoint, --dry-run to simulate, --calldata for encoded data, or --json for machine-readable output.

download the cli package · install foundry ↗

package sha256