01/ the claim, and what was already known
Four numbers, each from a source you can fetch yourself.
The issuer publishes a feed of corporate actions. The chain publishes a multiplier. They are two independent records of the same events, and until you line them up, neither tells you what a holder was actually paid.
Built on
Solana's Token-2022 documentation describes the stale field, and ExDate published the withholding rate and a dollar total on 13 September 2026. Kamino's Scope oracle suspends a price for the 24 hours before an activation, and existing guards refuse execution inside a transition window.
What this adds
The count: 663 activations timed against the exchange's own calendar. The record: an ordered, permissionless account of each activation a crank writes, read from the mint itself rather than from an oracle. And, further down, which currency the reference price is really in.
02/ what the chain says
One raw token is not one share, and the obvious field is the previous value.
On EVM chains the contract adjusts balances for you, so balanceOf() is already right. On Solana the balance stays put and every app has to apply the multiplier itself. The extension hands you two candidate values, and only one of them is live.
multiplier
1.0268028385
The field you'd reach for first. It holds the value from before the most recent corporate action. For 386 of 1026 mints it is not the multiplier.
new_multiplier
1.0344000942
Live from unix 1788481800. This is the value a wallet must multiply a raw balance by, and the value this program records.
The rule is simple: the live value is new_multiplier once its timestamp has passed, and multiplier before that. It's what Token-2022's own process_update_multiplier does, and I didn't take it on trust. The issuer publishes its own view of the live value, and I compared the rule against it on every mint: 1026 agreed, 0 disagreed, 0 publishing nothing to compare against. Solana's runtime agrees on every mint too. Both comparisons are build checks, so the page won't build if either fails.
Why the balance cannot help you
Token-2022's scaled-ui-amount extension never touches the raw amount. Your balance is identical before and after a dividend, so a wallet that shows raw amounts shows a position that hasn't moved when it has.
Why the history is not on chain
A mint keeps the latest two multipliers and nothing older. No event log, no sequence, no account per activation. The only record of what a token has paid lives in an HTTP API and in transaction logs.
Why the pause needs a number
The issuer's own docs recommend that venues and protocols pause for fifteen minutes around each activation, and nothing in a mint account can enforce that. Kamino's oracle suspends a price for the 24 hours before one. Either way the venue has to know when the window is.
Quoted from docs.xstocks.fi/developers/multipliers, not paraphrased: “The multiplier is published on-chain before each corporate event takes effect… we recommend that trading venues and protocols pause all interactions with the token for a brief window (e.g., 15 minutes) before and after each activation timestamp.”
When the multiplier actually moves. Every one of the 663 activations the issuer has published, counted by the minute of the day it takes effect. 654 of them, 98.6%, fall outside the US regular session, and 93.5% of them land on the four minutes below.
I measured it two ways, so the answer doesn't depend on where I drew the line. The first is a generous UTC window, 13:00 to 21:00, wide enough to cover the session in both summer and winter time: by that measure 651 of 663, or 98.2%, are outside. The second is the exchange calendar Pyth publishes with its feed directory: America/New_York, a regular session of 09:30-16:00, and 12 holiday and half-day overrides, shared by 1045 of the 1074 US equity feeds Pyth carries. By that calendar 9 of 663 fall inside the session, so 654 are outside, or 98.6%. The build computes both separately and requires them to agree. Of the ones outside, 595 land on a trading weekday after hours and 59 on a day the market doesn't trade at all.
Nobody's code is broken here. The issuer schedules each activation for 00:30 UTC the day after the ex-date: four and a half hours after the US close, thirteen before the next open. So the multiplier changes when there's no live price to settle against and no closing auction to absorb it, and a fifteen-minute pause is all that stands in for both. A venue that doesn't pause isn't getting a number wrong. It's settling against a position whose entitlement moved while it wasn't looking.
The token trading while the stock is shut isn't a guess. The Solana Foundation's 13 September newsletter reports that 63% of tokenized-equity volume settles outside US market hours. Kamino, the first major lender to accept these as collateral, suspends its price for the 24 hours before an activation, and existing guards already turn the timestamp into a refusal. Record Date adds the count and the record behind it.
03/ what was taken
The dividend is reinvested net of tax, and the net is 74.3% of the gross.
Across the 581 scheduled cash dividends the issuer has published, the maths closes exactly: net = gross × (1 − rate) on all 574 records that carry both figures. The withheld part never reaches the token, so it never reaches the multiplier, so it never shows up anywhere a holder would look.
How this is counted. Per-share dividend times scaled supply, at today's price, over the window the issuer's feed covers. Supply is today's rather than averaged over time, so a token that minted heavily after its dividend is over-counted. The feed looks ahead, so the window runs a few days past today: $25,311,277 of the $26,756,904 gross is dated on or before today and $1,445,628 is still to come. Treat the annual figure as an order of magnitude, not a ledger. The full arithmetic is in scripts/fetch.py.
04/ the proof
Divide the net dividend by the multiplier step and you get the share price.
The issuer's feed and the mint account are separate records. If they describe the same event, then net per unit ÷ (new multiplier − previous multiplier) should be the price of one share on that date, recovered with no oracle and no price feed, from the chain and the issuer's feed alone.
That's a prediction you can test. The implied price is fixed on the activation date; the market price is today's. So the gap between them should be the stock's own movement since, which means it should grow as the activation gets older. If it were an accident of how the feed is written, the gap would be random and the same size in every bucket.
It does: a fresh activation reconciles at 2.8% within ten days against 6.5% beyond sixty, and the table below shows every bucket.
Which figure the chain reinvests, tested. The feed publishes a gross dividend and a net one, 30% apart, and everything here depends on the net one being what reaches the token. Divide either by the multiplier step and you get a share price. With the net figure it lands on the market at 1.036; with the gross it reads 1.480. The control is the 41 events with a 0% rate, where net and gross are the same number, so a fair test should have no preference between them. It doesn't: both read 1.006.
| Token | Activation | Multiplier step | Net dividend / unit | Implied price | Market price today | Gap |
|---|---|---|---|---|---|---|
| CINFx | 2026-09-230d | 0.003967919 | 0.658 | $165.83 | $165.17 | +0.4% |
| LRCXx | 2026-09-230d | 0.0007432269 | 0.231 | $310.81 | $307.62 | +1.0% |
| SATAx | 2026-09-230d | 0.0005407366 | 0.0516 | $95.43 | $95.38 | +0.1% |
| TQQQx | 2026-09-230d | 0.0027143027 | 0.1092084 | $40.23 | $40.12 | +0.3% |
| APHx | 2026-09-221d | 0.0021679881 | 0.0875 | $40.36 | $41.66 | -3.1% |
| AVGOx | 2026-09-194d | 0.0012785496 | 0.455 | $355.87 | $360.73 | -1.3% |
| DTEx | 2026-09-194d | 0.0063453159 | 0.8155 | $128.52 | $124.62 | +3.1% |
| ESx | 2026-09-194d | 0.0081401359 | 0.55125 | $67.72 | $65.84 | +2.8% |
The eight most recent activations, in order of age and not picked for how well they agree. The market price is the token's quoted price divided by the multiplier the chain reports, a third source neither of the other two has seen.
| Age of the activation | Events | Median gap against today's price |
|---|---|---|
| 0-2 days | 6 | 0.4% |
| 3-10 days | 56 | 2.9% |
| 11-30 days | 151 | 4.9% |
| 31-60 days | 158 | 6.8% |
| over 60 days | 94 | 6.5% |
Across 465 reconciliations on 366 names, the median gap is 2.8% when the activation is under ten days old (62 events) and 6.5% when it's over sixty (94). Same arithmetic in both buckets. The only difference is how long the stock has had to move, which is what makes this evidence rather than coincidence. The overall median is 5.1%.
05/ the ledger
The tokens where the most was withheld.
Withheld dollars per token over the window, from per-unit dividends the issuer published times the scaled supply the chain reports. The bar is scaled to the largest here.
- STRCx8 eventswithheld$223,344per unit0.4375multiplier1.0863570206price$99.04
- PFEx2 eventswithheld$165,753per unit0.258multiplier1.0537129709price$27.98
- NVOx2 eventswithheld$130,148per unit0.396956multiplier1.0370549907price$39.25
- CMCSAx2 eventswithheld$113,925per unit0.198multiplier1.087679741price$22.51
- TBLLx5 eventswithheld$113,672per unit0.451278multiplier1.0187608514price$105.48
- XOMx3 eventswithheld$112,965per unit0.927multiplier1.0176489705price$159.09
- MRKx3 eventswithheld$108,611per unit0.765multiplier1.0258591861price$151.35
- YLDEx4 eventswithheld$105,875per unit0.477105multiplier1.0194749277price$55.66
- CVXx2 eventswithheld$104,221per unit1.068multiplier1.0295541832price$202.48
- KOx3 eventswithheld$103,026per unit0.477multiplier1.0225601246price$88.73
- HDx3 eventswithheld$97,202per unit2.097multiplier1.0232993457price$305.28
- PEPx2 eventswithheld$95,765per unit0.888multiplier1.0344000942price$131.50
- FLBLx4 eventswithheld$91,403per unit0.172778multiplier1.0171047698price$23.05
- EWQx1 eventwithheld$88,751per unit0.326201multiplier1.0163263664price$44.25
- MSFTx3 eventswithheld$86,478per unit0.819multiplier1.0059033905price$502.10
- JAAAx5 eventswithheld$72,815per unit0.301846multiplier1.0111858841price$50.68
- EWGx1 eventwithheld$72,334per unit0.249474multiplier1.0137581352price$42.65
- UNHx2 eventswithheld$68,958per unit1.359multiplier1.0273478685price$373.48
- MCDx2 eventswithheld$62,269per unit1.116multiplier1.0211807005price$251.30
- FEZx1 eventwithheld$62,099per unit0.333488multiplier1.01110673price$69.03
- NLYx1 eventwithheld$59,907per unit0.225multiplier1price$21.68
- JNJx2 eventswithheld$58,697per unit0.804multiplier1.0195885202price$269.50
- QQQx3 eventswithheld$58,352per unit0.689313multiplier1.0034560759price$747.54
- TQQQx2 eventswithheld$56,726per unit0.098172multiplier2.0116905979price$80.71
- IBMx2 eventswithheld$56,149per unit1.011multiplier1.0204029188price$232.45
- SPYx1 eventwithheld$54,693per unit0.571055multiplier1.0057145603price$774.20
- CPETCx1 eventwithheld$53,631per unit0.01223multiplier1.024405765priceno quote
- EWUx1 eventwithheld$52,233per unit0.199876multiplier1.0098892366price$47.52
- FAAAx4 eventswithheld$52,153per unit0.2157multiplier1.0096041759price$50.38
- VGKx2 eventswithheld$51,745per unit0.42645multiplier1.0111651718price$89.43
06/ the program
Entitlement, as an account you can read in one call.
On Solana, a dividend changes what a balance means. This program reads the mint directly, picks the right multiplier, and turns each activation a crank brings it into a permanent, ordered receipt any protocol can read without an API.
// the whole trap, in one comparison // Token-2022's ScaledUiAmountConfig::current_multiplier, mirrored exactly: the // timestamp decides, and the stored value is not consulted at all. pub fn effective(&self, now: i64) -> f64 { if self.new_multiplier_effective_timestamp <= now { self.new_multiplier // live } else { self.multiplier // previous. not the multiplier. } }
Once per deployment. Holds the authority and the two counters.
Reads an xStock mint and stores the live multiplier alongside the value in the field the mint calls multiplier, so the gap between them is auditable.
Permissionless. If the multiplier has moved, writes a Receipt: previous, new, the issuer's own timestamp, the supply. Ordered by sequence and never edited.
Raw units in the units a wallet should display. Return data is a little-endian u128. Integer arithmetic throughout.
One byte: has the multiplier moved since this program last looked? A cranker calls this first so it does not pay for a transaction that reverts.
Seconds since the last activation. A protocol that wants to follow the issuer's advice to pause refuses to settle while that is inside 900.
Binds a registered mint to a Pyth feed id. The id is stored rather than the price account's address, because a PriceUpdateV2 account is rewritten on every publish and its address is not stable.
Reads a Pyth price account and refuses it if the receiver program does not own it, if it is for a different feed, if it is older than a limit the caller sets, or if it differs from the caller's price by more than a tolerance the caller sets. This is the only instruction here that compares against a number this program does not own.
The mint is read as raw bytes, not through the spl-token-2022 crate, because the program does not link against the program that owns it. The layout is not the one the docs describe: a mint account is a 165 byte base region, then the account-type byte, then the extensions. The mint fills only the first 82 of those bytes. So the header is computed rather than searched for, and a non-zero byte in the padding is an error. Asserted on all 1026 mints: the padding is zero in every one and the ScaledUiAmountConfig header is at byte 275 in every one. cargo test covers the parser, the read rule and the fixed-point arithmetic, and for the Pyth instructions it runs against two PriceUpdateV2 accounts captured from mainnet and devnet rather than fixtures written to match the parser, because a fixture built from the parser can never disagree with it.
07/ the checks
What has to be true for this page to be right.
Every figure on this page comes from one script that checks its own claims and refuses to write the page if any fail. Here are those checks, and what each one found.
100 symbols on page 0 of the issuer's asset API, 100 of them present in the 1026 mints read
1026 of 1026
1026 of 1026 padded with zeros, 1026 of 1026 type byte is 1, 0 rejected
275 x1026, across 1026 mints; the largest extension body stepped over is 205 bytes
1026 of 1026 exact, 0 overran, 0 undershot, at most 8 entries
574 of 574 records match exactly
93.7% of 430 symbols at 30%
3 rows collapsed to 581 distinct events, 0 survivors are not the highest version; the superseded rows carried 0.66% of the per-unit gross
581 scheduled cash dividends against 595 scheduled actions of all types
465 reconciliations across 366 names
663 activations, 12 (1.8%) inside 13:00-21:00 UTC; most common times 00:30 x427, 23:55 x177, 00:15 x11, 01:15 x5
9 of 663 (1.4%) inside 09:30-16:00 America/New_York, which is the session 1045 of 1074 USD equity feeds on Pyth carry, over 12 listed overrides
12 inside the UTC window against 9 inside the exchange calendar, a difference of 3 across 663 activations
Pyth puts the next open at Wed 23 Sep 09:30 and the next close at Wed 23 Sep 16:00, and 1045 feeds carrying this calendar agree on both; the parser matches at 5 of 5 boundary probes
median 2.8% on the 62 activations within 10 days against 6.5% on the 94 older than 60, so the residual is the stock moving, not the method
the implied price over the market reads 1.036 on the net figure against 1.480 on the gross across 421 events at a rate above 29%, so the net is the one landing on a share price; on the 41 zero-rate events, where the two figures are the same number, both read 1.006, which is the control
3 events where the two price fields differ by over 20%; the field this run used reconciles to a median error of 2.1%, the field it rejected to 66.3%
386 of 1026 mints differ
1026 agreed, 0 disagreed, 0 published no value
1026 agreed, 0 disagreed, 0 unavailable
386 listed against 386 counted, 0 unnamed
632 never, 308 exactly one, 86 two or more
unrounded $6,873,017.06 vs $6,873,017.06, difference $0.00
ledger $6,873,014 vs headline $6,873,017, drift $3.06 within $208 from 413 rounded rows
all rates $6,873,017 vs 30%-only $6,781,305, the rest is $91,712
$26,756,904 = $19,883,887 + $6,873,017
paid $25,311,277 of $26,756,904, forward $1,445,628
61 of 913 priced mints are non-dollar listings and every one is converted at the ECB rate for 2026-09-22; 0 converted by nothing
57 LSE mints priced, the published value is 74.8 times the dollar price on every one of them, because the ratio is pinned to 100 divided by the GBP rate of 1.336327 rather than varying with the share; drop the division and it reads 0.75
the London listings are 3.30% of the converted book and 100% of the gap between the converted and face-value totals
0.72% on $3,586,127,327 across the 402 mints that both pay and quote
913 of 1026 mints quoted
every figure matches
08/ scope
Scope, and one more finding.
The reference price is not always in dollars
174 of the 1026 mints track an equity that does not trade in dollars, and the reference price published beside them is quoted in the underlying's own currency. 61 of the priced mints are non-dollar, and 57 of those are London listings quoted in pence, so each is divided by 100 before it is converted at the ECB rate for 2026-09-22. Read as dollars instead, the same prices value the book at $24,213,432,467 rather than $7,045,572,594, a factor of 3.44, and the yield denominator with it.
The window is the feed's, not a clean year
2026-03-06 to 2026-09-30. The annual figure is that window scaled, not twelve measured months. Re-run the script and you get a different window and a slightly different number.
This is one issuer
1026 mints from Backed's own asset API, which is exhaustive over what Backed publishes on Solana.
09/ the sources
Everything, public, no key.
No API token, no account, no paid feed. Run python3 scripts/fetch.py and it re-fetches all of it and re-asserts the checks above.
One source is used for less than it offers, so here's which part. Pyth's feed directory is public, and the session definition in section 02 comes from it. Its prices are a different matter: the Hermes HTTP endpoint only serves equity prices to a key with a grant, but Pyth also posts every update to Solana as a PriceUpdateV2 account owned by its receiver program, and a posted account is public. Two of those accounts are committed as test fixtures, read with a plain RPC call and no credential, and the program's verify_against_pyth instruction reads one at settlement time.
https://api.xstocks.fi/api/v2/public/assetshttps://api.xstocks.fi/api/v2/public/corporate-actions/upcominghttps://api.xstocks.fi/api/v2/public/assets/{SYMBOL}/multiplier/historyhttps://api.mainnet-beta.solana.comhttps://api.jup.ag/price/v3https://api.frankfurter.app/latest?from=USDhttps://hermes.pyth.network/v2/price_feedshttps://docs.xstocks.fi/developers/multipliers