Read before interactingNOT INVESTMENT ADVICE

Readable mechanics are not safe mechanics.

JUSTYPE can make a configuration easier to inspect. It cannot turn a token into a good investment, remove economic risk, or guarantee future contract behavior.

01Token value

A token can lose all of its value. Clear mechanics do not create demand, liquidity, honest creators, or a market floor.

02Configuration

A supported and valid rule set can still be confusing, aggressive, contradictory in ways the validator does not check, or economically harmful.

03Incentives

Fees, rewards, buybacks, burns, limits, and milestones can change trading behavior in unintended ways and may benefit some participants over others.

04Representation

Behavior Score explains active structured rules. It does not rate safety, predict price, verify a creator, or prove execution.

05Local state

Current profiles and drafts live in one browser. They can disappear when storage is cleared and are not public or onchain records.

06Wallet and transactions

Connecting exposes a public address and provider session. Any activated launch, approval, Permit2 signature, or swap is an irreversible user-controlled request with its own risk.

07Canonical contracts

Classic V1 depends on external Uniswap launcher, token, strategy, PoolManager, FeeSplitter, Permit2, and router contracts. Canonical does not mean risk-free.

08Future hooks

A later JUSTYPE Hook Engine introduces additional callback, accounting, custody, upgrade, access, oracle, and integration risk.

09External systems

Chains, wallets, RPCs, pools, tokens, indexers, browsers, and linked sites can fail or behave unexpectedly outside JUSTYPE’s control.

Current product risk

The production Classic launch flag remains off, so the current public UI cannot broadcast that launch. The repository nevertheless contains a real transaction path that can be activated separately; do not treat an unexpected wallet prompt as harmless. Check Robinhood Chain, target, value, and action, and reject anything that does not match Review.

The wallet layer persists connector/session state and contacts Reown/WalletConnect plus a configured Robinhood RPC. Launch and market routes send public addresses, transaction hashes, token addresses, PoolIds, and log queries to configured infrastructure. Trading additionally depends on Uniswap's API when its server key is present.

Read the normalized rules instead of trusting the original sentence. Rewrite anything unrecognized. Treat every example as documentation, not a market.

Classic and programmable risk are different

Classic V1 uses external canonical contracts and a hookless pool. Transactions are still irreversible, tokens can fail economically, liquidity and RPC/API infrastructure can fail, and external contracts or dependencies can contain bugs. Fork tests reduce uncertainty for covered paths; they are not an audit.

A future JUSTYPE hook can affect swap accounting and adds an entirely new contract surface. External data dependencies may be manipulated or unavailable. Audits reduce risk but never eliminate it.

Your responsibility

Creators are responsible for what they configure and how they communicate it. Users are responsible for inspecting rules, verifying any future deployment evidence, understanding external contracts and approvals, and deciding whether the risk is acceptable. Read every future wallet signature or transaction before approving it.

Nothing on JUSTYPE is investment, legal, accounting, or tax advice. Read Security before treating any future integration as production-ready.