What is Sceptre?
Sceptre is a Telegram first trading terminal plus automation stack for Hyperliquid, manual execution, strategy subnoscriptions, risk and sizing, position management, monitoring, plus optional web or miniapp steps for the Hyperliquid permission flow, fully non custodial
Non custodial means your funds stay on Hyperliquid, we never hold custody, you grant and revoke permissions in Hyperliquid’s own UI anytime, Sceptre is an execution and automation layer, not an exchange, not a broker
Onboarding is designed so we never touch your main wallet private key, approvals and builder code signing happens inside your wallet, in your browser, we generate the transaction, your wallet signs locally, your private key is never transferred to us, never viewed by us
Each user gets their own API Wallet keypair, generated per user, you authorize that API Wallet in Hyperliquid, it becomes the dedicated trading signer, your main wallet stays untouched, you can revoke the API Wallet instantly in Hyperliquid if you ever want to hard stop
What we can do with the API Wallet key, sign trading actions, place orders, cancel orders, close positions, manage protective logic like SL and TP placement, what we cannot do, withdraw, move funds off Hyperliquid, or bypass Hyperliquid’s permission model, control stays with you
Manual trading from Telegram keeps terminal level controls, market or limit, long or short, leverage, pair selection, trade preview, confirmation, limit orders prompt for entry price immediately, sizing is rule based using real equity, risk percent, fixed margin, account percent, plus minimum order guards
Risk and exits are first class, SL by fixed price, percent, or ATR multiple, TP by percent or derived from R:R when sizing off stop distance, optional trailing, plus fast position management flows, view, adjust, close, and shareable PnL cards on closes
Automation is a core pillar, we have 100 plus strategies and we’re adding more, strategies are subnoscription based per user and per pair, evaluation runs on a consistent schedule, designed to scale without per user socket explosions
Backtesting is part of the workflow, not a toy, parity is the intent, you backtest the same strategy architecture you deploy live, with fees and slippage modeled, so results don’t live in fantasy land, then you deploy when it earns it
Next step is the builder framework, users will be able to create strategies from scratch, and use Programs to merge and smash together modules, rules, filters, risk settings, and execution behavior, one click backtest, then deploy the exact same config live, share it with friends or followers
We’re also frameworking machine learning into this as an optional overlay, regime detection, setup scoring, trade gating, filters, even sizing, treated as a measurable module you can test, reproduce, and share, not “AI did it” hype
Under the hood it’s reliability first, Hyperliquid WebSockets handled server side in decoupled channels for market data and position monitoring, designed so user growth doesn’t multiply sockets linearly, security is strict, encrypted at rest, decrypted only to sign, sensitive values redacted in logs
Use Sceptre if you want a Hyperliquid terminal that’s actually built for daily use, Telegram first execution, real risk controls, live monitoring, and automation that doesn’t pretend trading is magic, you keep custody, you can revoke access instantly, you can backtest before deploying, and as you use it you earn Favour, which ties your activity into the broader Court system and future perks, instead of being just another disconnected bot
https://x.com/JestTech/status/2009710761577460173
Sceptre is a Telegram first trading terminal plus automation stack for Hyperliquid, manual execution, strategy subnoscriptions, risk and sizing, position management, monitoring, plus optional web or miniapp steps for the Hyperliquid permission flow, fully non custodial
Non custodial means your funds stay on Hyperliquid, we never hold custody, you grant and revoke permissions in Hyperliquid’s own UI anytime, Sceptre is an execution and automation layer, not an exchange, not a broker
Onboarding is designed so we never touch your main wallet private key, approvals and builder code signing happens inside your wallet, in your browser, we generate the transaction, your wallet signs locally, your private key is never transferred to us, never viewed by us
Each user gets their own API Wallet keypair, generated per user, you authorize that API Wallet in Hyperliquid, it becomes the dedicated trading signer, your main wallet stays untouched, you can revoke the API Wallet instantly in Hyperliquid if you ever want to hard stop
What we can do with the API Wallet key, sign trading actions, place orders, cancel orders, close positions, manage protective logic like SL and TP placement, what we cannot do, withdraw, move funds off Hyperliquid, or bypass Hyperliquid’s permission model, control stays with you
Manual trading from Telegram keeps terminal level controls, market or limit, long or short, leverage, pair selection, trade preview, confirmation, limit orders prompt for entry price immediately, sizing is rule based using real equity, risk percent, fixed margin, account percent, plus minimum order guards
Risk and exits are first class, SL by fixed price, percent, or ATR multiple, TP by percent or derived from R:R when sizing off stop distance, optional trailing, plus fast position management flows, view, adjust, close, and shareable PnL cards on closes
Automation is a core pillar, we have 100 plus strategies and we’re adding more, strategies are subnoscription based per user and per pair, evaluation runs on a consistent schedule, designed to scale without per user socket explosions
Backtesting is part of the workflow, not a toy, parity is the intent, you backtest the same strategy architecture you deploy live, with fees and slippage modeled, so results don’t live in fantasy land, then you deploy when it earns it
Next step is the builder framework, users will be able to create strategies from scratch, and use Programs to merge and smash together modules, rules, filters, risk settings, and execution behavior, one click backtest, then deploy the exact same config live, share it with friends or followers
We’re also frameworking machine learning into this as an optional overlay, regime detection, setup scoring, trade gating, filters, even sizing, treated as a measurable module you can test, reproduce, and share, not “AI did it” hype
Under the hood it’s reliability first, Hyperliquid WebSockets handled server side in decoupled channels for market data and position monitoring, designed so user growth doesn’t multiply sockets linearly, security is strict, encrypted at rest, decrypted only to sign, sensitive values redacted in logs
Use Sceptre if you want a Hyperliquid terminal that’s actually built for daily use, Telegram first execution, real risk controls, live monitoring, and automation that doesn’t pretend trading is magic, you keep custody, you can revoke access instantly, you can backtest before deploying, and as you use it you earn Favour, which ties your activity into the broader Court system and future perks, instead of being just another disconnected bot
https://x.com/JestTech/status/2009710761577460173
🔥7🖕1
We are on the verge of moving from Alpha to beta. To date we have done 4.5M in volume, and recent patches were about making SCEPTRE hit Harder, Better, Faster, Stronger, and more consistent end to end.
Our next patch (v0.2.6) patch brings backtests and live trading ato the same pipeline, fewer mismatches, more trust in results, cleaner reports, less overwriting, and better pruning of old runs.
Automation reliability got hardened, strategy pause and disable actually stick, pair selection and staged changes persist, fewer phantom states, and now no “why didn’t it trade” moments.
Programs and progression upgrades, program system improvements, sizing and timeframe bugs fixed, daily and overall stats unified, more transparency with failed execution messages.
Favour groundwork is in, executed volume now uses real fills, favour display fixes, scaffolding for volume based favour calculations, rewards attribution is getting real.
Under the hood scaffolding for machine learning system groundwork added, plus refactors to keep everything maintainable as we step into beta.
We also have a new system "Crucible" which we anticipate will see a large amount of usage when we drop the miniapp/terminal...
But more on that later.
Oh yeah...
Mini-app?
https://x.com/JestTech/status/2013034996555296816
Our next patch (v0.2.6) patch brings backtests and live trading ato the same pipeline, fewer mismatches, more trust in results, cleaner reports, less overwriting, and better pruning of old runs.
Automation reliability got hardened, strategy pause and disable actually stick, pair selection and staged changes persist, fewer phantom states, and now no “why didn’t it trade” moments.
Programs and progression upgrades, program system improvements, sizing and timeframe bugs fixed, daily and overall stats unified, more transparency with failed execution messages.
Favour groundwork is in, executed volume now uses real fills, favour display fixes, scaffolding for volume based favour calculations, rewards attribution is getting real.
Under the hood scaffolding for machine learning system groundwork added, plus refactors to keep everything maintainable as we step into beta.
We also have a new system "Crucible" which we anticipate will see a large amount of usage when we drop the miniapp/terminal...
But more on that later.
Oh yeah...
Mini-app?
https://x.com/JestTech/status/2013034996555296816
🔥3
Moving to Beta, what it really means, why it’s hard, and how we’re auditing Sceptre...
Most products don’t die because the idea was bad, they die in the alpha → beta gap, when real users show up, load shows up, and the market punishes anything brittle.
Alpha is “does it work at all.” Ship fast, learn fast, rebuild fast, interfaces move, sharp edges are normal.
Beta is “can people rely on it.” Core loops stop shifting, guardrails become default, reliability becomes the baseline, not a lucky outcome.
The annoying part? Beta work looks like nothing from the outside. Correctness, multi instance consistency, cache safety, refusal paths, observability, recovery tooling.
You grind a week to remove one failure mode, and it looks like you shipped zero, but that’s how platforms get real.
Our beta audit is relatively simple and brutal. Every capability goes into a bucket, shipped and dependable, shipped but needs hardening, partial or gated, planned.
Then we check, does it work every time, does it fail loudly, does it behave the same on every instance, can ops recover fast.
Multi instance correctness is the boring stuff that saves you later. Shared state, shared caches, fewer race paths, consistent Telegram session routing, shared backtest results. Outcomes don’t depend on which box you hit, scaling doesn’t create “random bugs.”
We also split rigs so the UX stays snappy. Frontend rigs run Telegram, onboarding, monitoring, execution. Compute rigs have no user connectivity, pure backtests, parameter sweeps, Crucible runs, ML workloads. Same centralized data, compute scales without slowing the terminal.
100+ strategies isn’t to confuse you. Markets rotate, edges decay, one setup won’t fit everything. Presets are the on ramp. The direction is Programs, strategy + pair + risk + rules, like lego, build, test, deploy, share.
Backtesting is discipline, not marketing. Strict vs relaxed modes, parity intent, fees and slippage modeled, deterministic windows, cache first results. We also generate synthetic price history to stress test and catch overfit “lucky” configs.
Crucible goes deeper, Bayesian search across parameters, patterns, triggers, across historic plus synthetic datasets, to find combos that survive variation. ML is optional, not a black box, with overlays for regime detection, scoring, gating, filters, sizing, with execution still explicit.
Why Sceptre over alternatives?
Because it’s built like a platform. Execution, automation, receipts, non custodial permissions, governed signals, tier and Favour gates that stay consistent under load, operator tooling, and a builder roadmap that keeps tightening around a single core.
https://x.com/JestTech/status/2014496762078351729
Most products don’t die because the idea was bad, they die in the alpha → beta gap, when real users show up, load shows up, and the market punishes anything brittle.
Alpha is “does it work at all.” Ship fast, learn fast, rebuild fast, interfaces move, sharp edges are normal.
Beta is “can people rely on it.” Core loops stop shifting, guardrails become default, reliability becomes the baseline, not a lucky outcome.
The annoying part? Beta work looks like nothing from the outside. Correctness, multi instance consistency, cache safety, refusal paths, observability, recovery tooling.
You grind a week to remove one failure mode, and it looks like you shipped zero, but that’s how platforms get real.
Our beta audit is relatively simple and brutal. Every capability goes into a bucket, shipped and dependable, shipped but needs hardening, partial or gated, planned.
Then we check, does it work every time, does it fail loudly, does it behave the same on every instance, can ops recover fast.
Multi instance correctness is the boring stuff that saves you later. Shared state, shared caches, fewer race paths, consistent Telegram session routing, shared backtest results. Outcomes don’t depend on which box you hit, scaling doesn’t create “random bugs.”
We also split rigs so the UX stays snappy. Frontend rigs run Telegram, onboarding, monitoring, execution. Compute rigs have no user connectivity, pure backtests, parameter sweeps, Crucible runs, ML workloads. Same centralized data, compute scales without slowing the terminal.
100+ strategies isn’t to confuse you. Markets rotate, edges decay, one setup won’t fit everything. Presets are the on ramp. The direction is Programs, strategy + pair + risk + rules, like lego, build, test, deploy, share.
Backtesting is discipline, not marketing. Strict vs relaxed modes, parity intent, fees and slippage modeled, deterministic windows, cache first results. We also generate synthetic price history to stress test and catch overfit “lucky” configs.
Crucible goes deeper, Bayesian search across parameters, patterns, triggers, across historic plus synthetic datasets, to find combos that survive variation. ML is optional, not a black box, with overlays for regime detection, scoring, gating, filters, sizing, with execution still explicit.
Why Sceptre over alternatives?
Because it’s built like a platform. Execution, automation, receipts, non custodial permissions, governed signals, tier and Favour gates that stay consistent under load, operator tooling, and a builder roadmap that keeps tightening around a single core.
https://x.com/JestTech/status/2014496762078351729
🔥4❤1👏1
JEST! what is it good for?
Absolutely something, say it again!
$JEST (0xA4Bc2B90743294E5E6fd3321A9A131947f7785dB) is the utility token that underpins our ecosystem, it funds development, incentivizes usage, and powers the loop that turns platform activity into buybacks, then into Spoils distributed to the Court.
>tldrl; $JEST is an ERC 20 on Ethereum, max supply 1,000,000, there is no minting, our liquidity burnt, and we have a transfer tax is 2%.
The real point, the flywheel
The system is designed so activity inside the product creates fees, those fees are converted into $JEST buybacks, then a large portion of those buybacks becomes Spoils distributed based on Favour share.
So you get three layers working together
1, trading drives fees, fees drive buybacks
2, holding drives multipliers and stipend snapshots
3, referrals drive growth, growth drives more trading
ad infinitum
Favour is the loyalty currency, you earn it by trading, referrals, and holding JEST, then at the end of each Season your share of total Favour determines your share of Spoils, then it resets so the next cycle stays competitive.
How you earn it?
• Trading, earn 1 Favour per $100 traded through the bot
• Referrals with 3 level depth (don't be scared to share your code), with current rewards of 100, 25, 10 Favour, plus a new user bonus on verification
• Guilds; build a guild of followers who copy trade you, and earn a portion of the favour they earn on your trades
Holding, multipliers, snapshots, and staying power
Holding $JEST is not framed as fee discounts (at least not yet). Instead it is framed as leverage on your participation
• Multipliers, your tier multiplies the Favour you earn
• Snapshot stipends, each Season has 4 random snapshots, hit them and you collect the stipend, miss them and you miss that stipend.
Essentially, a "soft staking" system using our custom user management bot.
Spoils, where buybacks become distribution
Each Season, roughly 70 percent of fees are routed directly into $JEST buybacks, and 100% of those buybacks are distributed as Spoils, with the remainder reserved for things like strategic liquidity adds or OTC buybacks. There is also a 5% ceiling per wallet per Season, anything above the cap gets redistributed to the rest.
That ceiling matters, it keeps the pool wide, it keeps the middle tiers relevant, it stops the whole system from turning into whales only.
Why buybacks instead of fee reductions
The docs lay this out bluntly, fee discounts are linear, buybacks are reflexive, the buy pressure can lift the price curve, then Spoils are distributed, the intent is to return more value per dollar of fee than discounts ever could.
Does this flywheel work?
The current Sceptre spoils pool has a DCA of ~$2.80.
Current $JEST price is ~$4.00
Let that sink in.
Seasons, culture, cadence, and “fresh tournament” energy
Seasons roll through the year, each Season ends with Spoils distribution, Favour resets to zero, referrals remain tied to you but must be active again to keep generating value. It is designed to keep the game from going stale, and to avoid runaway permanent winners.
Token tax, treasury, and the practical funding layer
A 2 percent tax applies to token transactions, directed to the project treasury, used for salaries, ongoing development, and maintenance.
To long didn't read?
• A fixed supply token tied to an ecosystem loop
• A loyalty engine where activity is measured
• Buybacks that aim to scale with usage
• Spoils distribution based on a share of your activity
• Holding mechanics that reward consistency, multipliers plus random snapshot stipends
• Referral mechanics that grow the Court, without letting referrals overshadow real trading activity
Important note
$JEST is documented as a utility token for accessing services, it is not presented as ownership, governance, or a promise of returns.
Trading, tokens, and on chain activity carry real risk, do your own due diligence.
https://x.com/JestTech/status/2015147244274508144
Absolutely something, say it again!
$JEST (0xA4Bc2B90743294E5E6fd3321A9A131947f7785dB) is the utility token that underpins our ecosystem, it funds development, incentivizes usage, and powers the loop that turns platform activity into buybacks, then into Spoils distributed to the Court.
>tldrl; $JEST is an ERC 20 on Ethereum, max supply 1,000,000, there is no minting, our liquidity burnt, and we have a transfer tax is 2%.
The real point, the flywheel
The system is designed so activity inside the product creates fees, those fees are converted into $JEST buybacks, then a large portion of those buybacks becomes Spoils distributed based on Favour share.
So you get three layers working together
1, trading drives fees, fees drive buybacks
2, holding drives multipliers and stipend snapshots
3, referrals drive growth, growth drives more trading
ad infinitum
Favour is the loyalty currency, you earn it by trading, referrals, and holding JEST, then at the end of each Season your share of total Favour determines your share of Spoils, then it resets so the next cycle stays competitive.
How you earn it?
• Trading, earn 1 Favour per $100 traded through the bot
• Referrals with 3 level depth (don't be scared to share your code), with current rewards of 100, 25, 10 Favour, plus a new user bonus on verification
• Guilds; build a guild of followers who copy trade you, and earn a portion of the favour they earn on your trades
Holding, multipliers, snapshots, and staying power
Holding $JEST is not framed as fee discounts (at least not yet). Instead it is framed as leverage on your participation
• Multipliers, your tier multiplies the Favour you earn
• Snapshot stipends, each Season has 4 random snapshots, hit them and you collect the stipend, miss them and you miss that stipend.
Essentially, a "soft staking" system using our custom user management bot.
Spoils, where buybacks become distribution
Each Season, roughly 70 percent of fees are routed directly into $JEST buybacks, and 100% of those buybacks are distributed as Spoils, with the remainder reserved for things like strategic liquidity adds or OTC buybacks. There is also a 5% ceiling per wallet per Season, anything above the cap gets redistributed to the rest.
That ceiling matters, it keeps the pool wide, it keeps the middle tiers relevant, it stops the whole system from turning into whales only.
Why buybacks instead of fee reductions
The docs lay this out bluntly, fee discounts are linear, buybacks are reflexive, the buy pressure can lift the price curve, then Spoils are distributed, the intent is to return more value per dollar of fee than discounts ever could.
Does this flywheel work?
The current Sceptre spoils pool has a DCA of ~$2.80.
Current $JEST price is ~$4.00
Let that sink in.
Seasons, culture, cadence, and “fresh tournament” energy
Seasons roll through the year, each Season ends with Spoils distribution, Favour resets to zero, referrals remain tied to you but must be active again to keep generating value. It is designed to keep the game from going stale, and to avoid runaway permanent winners.
Token tax, treasury, and the practical funding layer
A 2 percent tax applies to token transactions, directed to the project treasury, used for salaries, ongoing development, and maintenance.
To long didn't read?
• A fixed supply token tied to an ecosystem loop
• A loyalty engine where activity is measured
• Buybacks that aim to scale with usage
• Spoils distribution based on a share of your activity
• Holding mechanics that reward consistency, multipliers plus random snapshot stipends
• Referral mechanics that grow the Court, without letting referrals overshadow real trading activity
Important note
$JEST is documented as a utility token for accessing services, it is not presented as ownership, governance, or a promise of returns.
Trading, tokens, and on chain activity carry real risk, do your own due diligence.
https://x.com/JestTech/status/2015147244274508144
🔥8🫡1
We now support HIP-3 end to end!
Want to trade $XAU, $SILVER, $TSLA, $AAPL, etc ?
Want to farm, automate, and trade @HyperliquidX AND @tradexyz AND @JestTech ALL at the same time?
Now you can.
https://x.com/JestTech/status/2019109876807659886
Want to trade $XAU, $SILVER, $TSLA, $AAPL, etc ?
Want to farm, automate, and trade @HyperliquidX AND @tradexyz AND @JestTech ALL at the same time?
Now you can.
https://x.com/JestTech/status/2019109876807659886
🔥2❤1🎉1