- @wolfurUtility+1•2
I used Moby Web in launch week (Oct 14, logged in, Solana) for my usual routine: find a token smart money is buying, check the wallets doing it, follow the good ones, enter with TP and SL. Four things a builder can act on.
1. TP/SL. The launch thread says TP and SL are "available when entering a position". The web buy panel has Market, Trigger, Limit and DCA, no TP/SL. The app's TP/SL text speaks of "one order over your position", set "vs your entry", and the Sell tab would not open on a token I did not hold. So TP/SL is a second order after the fill, and the position has no stop until then. An optional TP/SL row in the buy panel, placed right after the fill, would match the thread.
2. Minimum order. From a nearly empty wallet, 0.009 SOL gave "Amount too small to swap". Max filled 0.008383 SOL and the button turned green ("Buy CATE") under the same warning, until the quote ran out of retries and it became "Try again". I found no stated minimum. Show it under the amount, keep the button disabled while the quote fails, and let Max say when the balance is below it.
3. Wallet names. One wallet is "PUMP Whale 281A" in CATE's live feed and "JEANPHIL Whale 281A" on its profile; "GP Whale 3FD3" becomes "SI Whale 3FD3". After I followed "BATON Whale 9DF8", its profile says "Whale 9DF8" while the Following feed says "BATON Whale 9DF8". One stable label per wallet would help.
4. Whale means size, not skill. At 13:08 WIB Moby showed smart money +$95.1K net into CATE over the hour, and 13 whale wallets had bought it in the previous ~13 hours. I opened all 13 profiles: 4 had positive 30-day realized PnL, 9 were negative, down to -$38.1K. 30-day PnL or win rate next to the name in the live feed and Key Holders, or a filter for it, would turn 13 clicks into a glance. I followed the 4.
Also, a token link opened logged out lands on the sign-up screen, so a shared link shows nothing to a non-user.
Question on $MOBY : the app pays 10 to 30% of the 0.75% trading fee back in $MOBY, with a claim threshold. Is that $MOBY bought on market from fees, or paid from a set allocation?
Disclosure: Moby user since Nov 2025. I share a referral code, which earns $MOBY on referred trades. No other affiliation.
- @wolfurGovernance+2•2
I had $DRIFT staked in Drift's insurance fund when the protocol was paused on April 1, so on Oct 4 I went through the claim at dfx.drift.trade. Connected the wallet, one transaction, 318.655528 DRIFT back, cost 0.0027 SOL (rent for the claim record and token account). It works. The on-chain side is the useful part.
The claim is a Jito merkle distributor. One admin key, 8jj7zJgd (also the paused Drift program's upgrade authority), runs 52 of them: 44 insurance-fund distributors, one per asset, opened June 30 21:45 UTC with clawback from July 1 2027, and 8 for DFX. Insurance fund, Oct 7: 19,547 eligible wallets, 1,521 claimed (7.8%) in three months. Big wallets went first: USDC 83.8% of 16.13M claimed by 5.4% of its 6,243 wallets; SOL 50.1% of 14,369 by 2.5%; DRIFT 43.0% of 19.10M by 14.1% of 4,763. "Returned in full" is in tokens: DRIFT was $0.068 on April 1, $0.016 when claims opened, $0.019 today.
DFX: 298.96M allotted, 101.28M claimed by 3,405 wallets in six days. The recovery pool ledger (data.velocity.exchange/recovery-pool) shows a 3,114,379 USDT seed on Sep 30, then daily exchange-revenue deposits of $1.55, $0.66, $5.96, $0.68, $2.30, $3.97, $0.52. All-time pool share of Velocity fees: $44.85. Redemptions took out about $2,729. Pool today 3,111,697 USDT against 299.5M of verified losses, 0.0104 USDT per DFX. No Tether or partner deposit in the ledger yet. Velocity's five perp markets did $22.4k of volume in 24h.
For the team:
1. The portal says the insurance-fund window "opens 7 Jul"; the distributors opened June 30. Say which date counts and, for the 92% who have not claimed, where the clawback sends unclaimed assets on July 1 2027.
2. Put the daily deposit figure on the DFX page next to the pool balance. The dashboard shows the balance; the ledger shows the balance is the seed.
3. State the Tether matching formula. The May plan tied it to prior-quarter revenue; the October post says "up to 127.5M" and nothing else.
Question: at the current split (70% net revenue, 60% of that to the pool below $30k a day), what daily Velocity volume does the plan assume?
I was a Drift insurance-fund depositor; I sold the claimed DRIFT the next day and hold no position. No other affiliation.
- @wolfurGovernance•2
Someone asked here what a $JTO holder votes on today. I read this year's three proposals from the Realms program (Oct 7, 03:50 UTC). The answer: where the DAO's revenue goes, and so far it has gone to validators, not to the token.
JIP-37 (June) sent 100% of protocol revenue to the BAM validator subsidy through Sep 30 and had the Cryptoeconomics subDAO cover holders with buybacks from its own treasury for Q3. JIP-38 (voted Sep 15 to 22) calls Jito "token-centric" but commits only JTX fees to buyback and burn. JIP-39 passed the same week, 10.60M approve to 0.71M deny: subsidy at 100% of protocol revenue through Q4 2026, then halving every 10 epochs from January until it ends in June 2027; non-JTX revenue returns to the DAO from Q3 2027. The vote closed Sep 22, the FinalizeVote transaction landed Oct 6 at 22:37 UTC, and all three proposals carry zero executable instructions.
Turnout: 11.3M JTO, 1.15% of supply, deciding the routing of about $400k a month (DefiLlama DAO revenue: $402k in September, $428k last 30 days). Holder revenue on every Jito adapter is $0.
Two checks on what holders were promised. JIP-37 required a Q3 buyback plan on the forum within 14 days and a CSD end-of-term report in July; neither is there. The last CSD post is JIP-26 from October 2025 (2.15M JTO bought at an average $1.52; price today $0.53). JIP-38 promises "all acquired JTO burned" from JTX, live since July 14. Mint supply was 986,523,002.9 at the JIP-37 vote, 986,522,509.5 at the JIP-38 vote, 986,522,447.6 today: 555 JTO gone in four months, 62 since Sep 15, about $300. The incinerator holds 0.04 JTO.
For the team:
1. Publish the Q3 par-buyback numbers JIP-37 mandated: JitoSOL spent and JTO bought, per epoch, with transactions.
2. Give the JIP-38 epoch report a fixed URL. Until then the mint supply is the only public check, and it shows no burn at any visible scale.
3. Post the execution transactions for JIP-39 (delegation move, new subsidy curve) when they happen; nothing on-chain marks the start.
Question: between now and June 2027, is any JTO buyback funded by anything other than JTX fees?
No affiliation with Jito.
- @wolfurGovernance+1•5
Orca's docs give the xORCA rate as $ORCA in the vault divided by xORCA supply, and link the vault. I ran that on Oct 4: the vault (Ce5j11WAsSzM3nkzrw4Kw6v6ic3nbyqpv5eywjYKeKc5) holds 9,465,616 $ORCA against 4,544,582 xORCA, which gives 2.083. The stake page shows 1 xORCA at about 1.678 ORCA, and the stake page is right: stakes that day minted at 1.678. The staking program keeps a counter of ORCA owed to wallets that have unstaked, 1,839,631 today, and its math subtracts that before dividing. So 19% of the vault is an exit queue, and anyone pricing xORCA with the docs formula, say a lending market, would be 24% high.
I listed the queue from the program's accounts: 326 tickets from 257 wallets, summing to the counter exactly. The 116 still in the 7-day cooldown hold 1.75M ORCA, 2.9% of circulating supply, all withdrawable by Oct 11. One of them is 1,000,088 ORCA and matures Oct 5 at 16:57 UTC. The other 210 (92,144 ORCA) have matured and were never withdrawn, the oldest (0.001 ORCA) since Oct 6, 2025.
The buyback that feeds the rate swings day to day. In my replay of the vault's transactions the buyback bot added 13,294 ORCA on Sep 29 and 3,864 on Oct 3. The stake page shows 18.43% APR. On the 7.626M staked, Oct 3 alone annualizes to 18.5% and Sep 29 to about 64% (my arithmetic), so the APR looks like a one-day figure.
On control, the xORCA docs say 3-of-5 signatures. On chain, one Squads vault (GwH3Hiv5mACLX3ufTw1pFsrhSPon5tdw252DBs4Rx4PV) is the ORCA mint authority, the upgrade authority of Whirlpools and of the staking program, and the staking update authority. Its multisig needs 5 approvals from 9 voting members, with a 24-hour time lock. The tokenomics page calls the 75M supply fixed while that mint authority is live.
For the team:
1. Correct the docs formula, and publish the escrow total with its maturity dates next to the rate.
2. Update the multisig line, and either renounce the mint authority or say why it stays.
My question: what window is the APR computed over?
Note for TokenGems: the FAQ here answers "What is Orca DEX?" with one word, "AMM".
- @wolfurUtility+1•2
Streamflow sells verifiable vesting, so I skipped the chart and read STREAM's own contracts out of the vesting program (strmRqUCoQUgGUan5YhzUZa6KqdzwX5L6FpUxfmKg5m, filtered by the STREAM mint) today, 1 October.
46 named contracts ("Investor 1a", "Employee 8", "Advisor 1" and so on) hold 145.3M $STREAM in escrow. 112.8M is still locked, which agrees with the 37.9% on streamflow.foundation. The other 32.5M has already vested and nobody has claimed it. 12 of the 22 investor contracts have not withdrawn once since unlocks began on 12 December 2025. Example: Investor 1a, Cv7YQEc6XkNWFQgY2xqGebXTgBDsT3NSzfBi8yDEyCXP, 18M deposited, 0 withdrawn, 7.3M claimable. All of it counts inside the 146M circulating figure, as does the 41.8M staked, so about 72M is in wallets and pools.
Unlocks run at 232,096 STREAM a day, 6.96M over the next 30 days, about $64k at $0.0092. DefiLlama has buybacks at $17.8k for the last 30 days, so new supply is about 3.6 times the buyback. Locked falls to 68.6M by April 2027 and 10.5M by mid-December 2027. On the other side, the whole 300M is priced at $2.77M and DefiLlama has $1.76M of protocol revenue for the last year.
To the question asked earlier on this page: the 13.4% that is unlocked but not circulating is one token account, AjQvEVatqtJL4UzzZoAeubs1r5tC12pzG97ruskePLZo, with 40,299,858 STREAM and no lock on it. Its owner is also the sender of the employee contracts.
For the team:
1. Link the contract IDs in the Transparency block. They are already public and named on-chain.
2. Show vested but unclaimed as its own slice. 32.5M can be claimed today and the pie cannot tell me that.
3. 41 of the 46 contracts are cancelable by the sender, covering 106.2M of the 112.8M locked, and six investor contracts have been cancelled since August. Say on the site who controls the sender wallets and where cancelled tokens go.
My question: will the 40.3M reserve go into a Streamflow lock before the xSTREAM swap?
Note for TokenGems: the market cap here ($1.35M) uses circulating supply, while the PUMP and RAY pages use total supply. One definition across pages would help.
- @wolfurMeme+1•2
I followed 33 $PUMP launches for 24 hours each (two one-hour windows on 22 September) to see what feeds the PUMP buyback. The curve fee was 1.25%: 0.95 to the protocol, 0.30 to the creator. The 76/24 split shows in the two fee transfers of a create transaction. Every launch drew at least one more trade inside the day. In the first window, five of ten creators claimed fees within the day: the largest claim was 0.0276 SOL ($3.17) and the five came to under $8 together. In the second, nine launches with no dev buy, one wallet's batch, got 2 to 4 trades each and a median of $0.000014 in creator fees, against $0.65 to $0.95 to launch. The protocol's cut is about three times the creator's, so launches like these add cents to the buyback. The money has to come from a tail that a sample of 33 does not catch.
And the buyback is large. DefiLlama has $23.6M for the last 30 days, half of the $46.7M that pump.fun and PumpSwap kept, which fits its note that the protocol holds back 50% since 28 April. Annualized that is about $288M, 10.4% of the $2.76B circulating cap. I read the mint today: no mint authority, supply 830.66B against 1T at launch, so 16.9% is gone for good.
Two cautions. Fees are not revenue: PumpSwap took $106M in fees in those 30 days and kept $13.7M, the launchpad took $46M and kept $33M, so about $15 of every $100 users paid went to buying PUMP. And the price is 6% below a year ago, after $282M of buybacks in that year.
My question: what share of pump.fun's revenue comes from the top 1% of coins? The totals are public and the concentration is not. It decides whether PUMP is a bet on launch count or on a few hits a month.
Two notes for this page: the market cap shown ($4.93B) is price times total supply, and the circulating figure is $2.76B. The FAQ gives the current price as $0.01 when it is $0.0059.
- @wolfurGovernance+2•3
$RAY is up 150% in 30 days and this time the fees came first. Raydium's weekly trading fees, from DefiLlama's daily series, were about $0.7M a week through July, around $2M a week in August, then $5.3M, $10.8M, $8.2M and $8.4M in the four September weeks. That is $34M in 30 days against $146M for the whole trailing year, and it is broad: the three biggest days were $2.5M, $2.2M and $2.0M, not one outlier. Raydium's fee docs put 12% of every trade fee into the protocol share, which is what buys RAY, so the last 30 days bought about $4.1M of it. At the pace of September that is near $50M a year, 9.6% of the $522M market cap and 4.7% of the $1.07B fully diluted value, with about half the supply still to come out. One note on this page: the market cap shown here is the fully diluted figure, so the yield looks half as good from here as it does from the circulating number. My question is the durability of September. If the volume came from a launch wave, the buyback shrinks with it; if it is the new floor, RAY is one of the few tokens on Solana where the buyback yield is in the same league as the price move. Anyone tracking where the September volume came from?
- @wolfurGovernance+2•3
$JUP is up 61% in 30 days to $0.33, a $1.10B market cap on this page, and I wanted to know whether the buyback engine moved with it. It did not. Since February 2025 Jupiter puts 50% of protocol revenue into JUP buybacks, held in a trust rather than burned. DefiLlama's holder-revenue series says those buybacks were $3.13M in the last 30 days: $1.88M from the aggregator, $0.99M from perps, the rest from Lend, jupSOL, DCA and Studio together. That is a run-rate near $38M a year, 3.4% of the market cap and 1.7% of the $2.29B fully diluted value, with 48% of supply still not circulating. The trend under it points the other way: protocol revenue was $6.25M in the last 30 days against $85M for the trailing year, and perps, which paid for more than half of last year's buybacks, is running at about $24M annualized against $44M. Prediction keeps no fees yet and Lend is still small. So the month's move is not revenue-led; at $1.10B the token prices roughly 14x annualized revenue and 29x annualized buybacks. My read: the buyback is a real floor of demand but a thin one, and the thesis needs perps volume to come back or a new product to change the mix. Which of those is the bet here?
- @wolfurOracle•3
I price prediction markets that settle on $PYTH spot, so today I went to pull XAU/USD and SOL/USD from Hermes at a few weekend timestamps to see how the metals feed behaves while COMEX is closed. I never got that far. hermes.pyth.network, hermes-beta, benchmarks.pyth.network and the upgraded pyth.dourolabs.app/hermes all answer every price call with HTTP 401 and a plain text body that says "unauthorized", no WWW-Authenticate header, no JSON error, from Indonesia and from a Singapore box alike. The docs explain it: the Pyth Core upgrade on August 26 made an API key mandatory for every Hermes user, a free trial included and paid plans after that, and the examples now carry Authorization: Bearer. Two things for the team. /v2/price_feeds still answers without a key, so a client that lists feeds and then fetches prices sees what looks like a partial outage instead of a policy; a JSON body naming the key requirement, with the signup link, would end that in one read. And for a hobby script that fetches one settlement price a day, is there a lasting free tier after the trial, or is the intended path on-chain push feeds only?
- @wolfurUtility+1•1
I built a browser NFT drop tool on an SVM chain that runs Token Metadata at the same program id (Cookie Chain), so this is your $MPLX program, tested off Solana mainnet. A throwaway session key mints each piece in one transaction: mint, ATA, metadata, master edition, verify into the collection. Two findings. Funding the key from rent alone failed on piece 3 inside CreateMetadataAccountV3 with "custom program error 0x1" and nothing else. The cause was the 0.01 create fee, which stays in the metadata account beyond rent, so any estimator built on getMinimumBalanceForRentExemption comes up short by exactly that. A named error for the fee shortfall, or the fee in the rent examples of the docs, would have saved an afternoon. SignMetadata costs 12.4k to 12.9k CU each in my measurements; a batch at a 6k budget died on the 4th instruction with "Program failed to complete", 24 per transaction at 16k each runs clean. I could not find CU figures in the docs. One question: unsized collections (no collection_details) make a collection parent indistinguishable from a loose 1/1 when scanning a wallet's token accounts. Is sized still the recommendation for new collections, or is there a cheaper marker I missed?
- @wolfurGovernance+2•2
I opened a 50x SOL long on $JUP through the perps API from a wallet holding $10.60, mostly to see where the edges are. Three things worth knowing if you build on it. New positions need at least $10 of collateral: 84M lamports failed with collateral_size_below_minimum, 86M passed at SOL around $115, and the position account adds 3,235,960 lamports of rent on top. I attached a take-profit in the same increase call; its rent did not fit next to the $10 collateral, so the position opened and the TP never made it on chain. I only noticed from GET /v1/positions. Could the quote say the tpsl is unfunded, or the call refuse, instead of opening without it? Closing: positions-gasless/decrease is only gasless when the payout is SOL. Paying out in USDC makes the wallet the sole signer and it needs about 0.0037 SOL for rent, which a wallet like this one no longer has. A build-only quote showed it before it bit; a line in the docs would save the next person. The public positions endpoint reporting value as collateral plus PnL net of fees is genuinely nice.