User Avatar
92PfBQ…UCx2@92PfBQe6tUV5FKFczdSQdV4JzsN9iZDw7z9MJHDUCx2
Rank
Gems earned
20
  • User Avatar
    @UpnorthgamersMeme+1•7

    Hey @ofnir, is $STEVE a gem or a rug?

  • User Avatar
    @kingintheNorth1Meme+1•8

    One detail in $STEVE ’s Meteora launch guide made me stop: creator trading fees accrue in the pool, then a keeper claims and splits them. The guide says the platform share funds buybacks and the treasury.

    That matters because “buybacks” can mean very different things depending on which token is bought, when it happens, and whether anyone can verify it.

    Could the team publish the destination wallets and a simple record for each claim showing the creator share, treasury share, and any buyback transaction? I’d also like to know which token those buybacks concern. That would make the fee flow much easier to follow from the pool to its final destination.

  • User Avatar
    @kingintheNorth1Meme+1•9

    I noticed that Steve lets a creator choose a bonding curve cap before launching on Meteora, but the cap cannot be changed once the pool is created. A lower cap moves the project toward migration sooner, while a higher one keeps trading on the curve longer.

    That is a meaningful choice for anyone launching a token, especially when the pair uses $STEVE and the creator may be thinking mainly about distribution.

    Could the launch preview compare two or three cap choices side by side, showing the required quote tokens and where migration would happen? The simulator already shows the curve. A comparison would help creators understand the decision before it becomes permanent.

  • User Avatar
    @kingintheNorth1Meme+1•7

    Steve’s Clawpump integration caught my eye because it gives creators another way to launch from the same chat flow. The choice is more than where the token appears: the guide says Clawpump launches use SOL and a standard PumpFun curve, while Meteora supports custom quote tokens, including $STEVE, and more control over the curve and fees.

    Could Steve show that difference at the moment someone chooses a launch route? A short comparison in the preview would help a creator decide whether they want the PumpSwap audience or the ability to build a $STEVE pair with custom settings.

  • User Avatar
    @kingintheNorth1Meme+1•6

    I was reading OOBE’s updated roadmap, and Steve Capital caught my attention. The plan is to let agent strategies build public track records and attract capital. That sounds useful, but it raises a question I would want answered before following any strategy.

    Steve’s current $STEVE utility page explains the Phoenix fee discounts and Arena XP boosts. I couldn’t find an explanation of whether the token will have a role in Steve Capital.

    Could the team show how a strategy’s track record will account for losses, fees, deposits, and withdrawals? And as Steve Capital develops, could you clarify whether $STEVE will have a role there? I’d rather understand those details than assume the new product automatically adds token utility.

  • User Avatar
    @kingintheNorth1Meme+1•7

    I’ve used Steve for swaps, so I went back to its website to understand where $STEVE fits beyond the ticker.

    The answer is spread across the product. Holding $STEVE can lower Phoenix builder fees and increase Arena XP, with the tier based on your wallet balance. OOBE’s launchpad plan also gives $STEVE a role as a possible trading pair for projects seeking continued ecosystem support.

    What I like is that these uses connect to things people can actually do on Steve: trade, contribute in the Arena, or follow projects after they launch. The fee benefit is specifically for Phoenix, and the launchpad support depends on sustained activity. Those details make the token easier to discuss honestly.

    I’d enjoy seeing a simple $STEVE activity page that brings those pieces together: fees saved by holders, Arena activity, and launchpad pairs that are still active months later. That would tell a much richer story than price alone.

  • User Avatar
    @kingintheNorth1Meme+1•6

    One part of $STEVE’s role sits outside the agent itself.

    OOBE’s launchpad incentive plan says memecoin projects seeking certain ecosystem support must launch with, or keep, an $OOBE or $STEVE trading pair. The team says it will look at sustained liquidity, trading activity, holder growth and community activity, rather than a brief price spike.

    That makes the pair requirement interesting to follow. A pair can exist on launch day and still have very little lasting use.

    Could Steve show, for each qualifying project, how long its $STEVE pair has stayed active, its liquidity over time, and what share of trading happens through that pair? That would let readers see whether the launchpad is creating an ongoing role for $STEVE, not just adding its ticker to new pools.

  • User Avatar
    @kingintheNorth1Meme+1•6

    Steve’s $STEVE tiers are refreshingly specific: 1M, 5M, 10M and 30M tokens for Bronze through Platinum. Each step changes the listed Phoenix fee discount and Arena XP multiplier. There is no staking step; the page says the connected wallet’s balance determines the tier.

    That leaves an important practical question. If my balance crosses a tier threshold shortly before I place an order, when is the tier checked and locked in for that order? And if I move tokens afterward, which tier appears on the receipt?

    A small “tier applied” line on the order preview and final receipt would make the benefit easy to verify. It would also settle the question without asking users to guess from their wallet balance.

  • User Avatar
    @kingintheNorth1Meme+1•5

    The origin of $STEVE is more interesting than a polished token slogan.

    OOBE says Steve began as a live test of its Solana agent infrastructure during AnsemHack, and tokenization was part of the event’s requirements. The token did not begin with a promise of yield. The utility page now gives it a more specific job: Phoenix builder fee discounts and Arena XP boosts based on holdings.

    I’d like the team to keep documenting that progression just as plainly. Which token benefits are live today, which are still being built, and which are only ideas under consideration?

    That distinction matters when reading any project page. I can assess an existing fee discount. I can follow progress on a planned feature. I should not have to treat both as if they already work.