Smoltrade is a browser terminal announced by @wassie as built on Papertrade. Its public interface combines leveraged trading controls with chart analysis tools and the Smolting character.
During review, the BTC chart and market selector were accessible without a wallet. BTC, ETH and a split-screen BTC/ETH layout were visible; the split-screen view was opened for inspection. Drawing tools, portfolio-related navigation and a Rage-mode switch were also present. Rage mode is described by the interface as a way to grab and throw Smolting around the chart.
The 19 October launch post claims no additional fees and continued PAPER accrual on losing trades. These are the operator’s statements, not independently verified fee or reward results. Further incentives and NFT-holder features were announced separately as coming soon. The account later said stop-loss and trailing-stop support were not yet available and would be explored.
The Trading Desk / Live classification refers to the accessible public terminal, not tested financial execution. No wallet connection, deposit, order, execution, reward or withdrawal was tested. No separate native token has been established for this profile.
On 28 October 2026, @wassie announced Trigger Orders and No-Liq. During the 1 November disconnected public-page review, the Trigger ticket, single/ladder tabs, trigger expiry, optional stop-loss/take-profit on fill, and No LIQ controls were visible. No order or protection was activated. The initial loading state changed to Feed live / Protocol live, while Triggers remained off; this is an interface indicator, not a measured availability or execution guarantee.
A trigger requests later market execution and does not guarantee a fill at its trigger level. The No-Liq help describes a watcher arming a stop ahead of the bust price using a cushion based on distance to liquidation, market volatility and queue latency, recalculated at fill time. It still submits a market close through the queue: a price gap or long queue can defeat the cushion and liquidation remains possible. Watcher hosting, persistence with the browser closed, downtime handling, permissions, revocation, actual fills, complete fees and protection effectiveness remain unverified. Earlier statements that stops/triggers were exploratory are retained as dated history, superseded only by the later announcement and visible controls; no new trailing-stop functionality is inferred.
papergames
