The Seven
+0.05%7 assets · official
AAPLx · MSFTx · NVDAx
Liquidity
$5.27M
Weights
100.00
Any set of verified Solana mints becomes a single pack. Baskr will not print a figure it cannot read from 100% of that pack’s weight — not a clamped one, not an average of whatever resolved.
PRICES LIVE · 7 of 7 mints read from Jupiter at slot 448,161,033, refreshed every 30s. Buying is live on mainnet and signed by your own wallet — selling and position tracking are not built.
Every pack defined on Baskr. Weights sum to 100 and the mints were checked against their own on-chain metadata. Each 24h figure is a weighted change over all of a pack’s weight, or it is not printed.
7 assets · official
AAPLx · MSFTx · NVDAx
Liquidity
$5.27M
Weights
100.00
3 assets · official
NVDAx · MSFTx · AAPLx
Liquidity
$3.13M
Weights
100.00
2 assets · official
GOOGLx · METAx
Liquidity
$682.3K
Weights
100.00
3 assets · official
MSFTx · AMZNx · GOOGLx
Liquidity
$1.16M
Weights
100.00
6 assets · community
NVDAx · MSFTx · AAPLx
Liquidity
$4.04M
Weights
100.00
2 assets · community
GOOGLx · AMZNx
Liquidity
$612.3K
Weights
100.00
2 assets · community
AAPLx · TSLAx
Liquidity
$1.84M
Weights
100.00
2 assets · tokenized
NVDAx · MSFTx
Liquidity
$2.52M
Weights
100.00
3 assets · community
NVDAx · MSFTx · AAPLx
Liquidity
$3.13M
Weights
100.00
showing 9 of 9 packs
All four run on mainnet today. Anything on this site that does not is tagged, because a product page describing an unbuilt flow in the present tense is the overstatement this project was built after finding.
Link a Solana wallet. Non-custodial from the first click: your key never leaves your wallet, and this project has no keypair on the server or in this page.
RUNNINGWeights that sum to exactly 100 over mints checked against their own on-chain metadata, priced live from Jupiter. Browse them below, today.
RUNNINGA pack is more transactions than fit in one — seven assets build seven, about 4.9 KB against a 1232-byte cap. You approve once, the batch goes out, and a partial fill is named as one.
RUNNINGEvery figure is read from 100% of its weight or it is not printed — and the reason is always the specific one, never a shrug. Running now, against a live feed.
RUNNINGThese seven mints were not pasted from a list. Each one was read from its own Token-2022 metadata and refused if the chain called it something other than expected — because two projects in this workspace once disagreed about which mint was NVIDIA and which was Meta, and a wrong character is not a typo, it is a phishing rail.
Baskr does not issue any of them and is not their custodian — and that is not the whole story, so the powers the issuer keeps over them are read from the chain and printed next to the buy button.
7 of 7
symbols verified
49
issuer authorities, read not assumed
Token-2022
read, never typed
AAPLx
$334.93
MSFTx
$493.72
NVDAx
$219.41
GOOGLx
$350.08
AMZNx
$253.25
METAx
$672.15
TSLAx
$362.33
read from 100% of weight · slot 448,161,033
Pool liquidity
$5.27M
Constituents priced
7/7
A figure is read from 100% of its weight, or it is not read at all.
type Figure =
| { read: number; coverage: 100; at: string }
| { unreadable: string };There is no bare number in that union, so a clamp has nothing to reach: the numeric field does not exist until read has already been granted. And coverage is the literal 100, so { read: x, coverage: 52 } is a compile error rather than a code-review comment somebody loses an argument about.
Each strand’s width is its weight, so the band is 100 wide by construction. An unpriced strand is not greyed or badged — it is absent. The hairline underneath runs the full 100: it is what the holes are missing from, and without it a gapped weave would just look like a narrower one.
Every strand carries a price.
SLOT PRINTS · 100%Three do not. Nothing is averaged around them.
SLOT REFUSES · 64%ILLUSTRATION · abstract strands, mechanism only. No price and no percentage that could be mistaken for market data appears here, because none has been read.
Neither is hypothetical. Both were read out of a live basket product’s own shipped JavaScript.
clamp = c => Math.max(-99, Math.min(999, c))A constituent reporting 195,257% over 24 hours has not moved 195,257%. Clamping it to +999.00% does not fix that, it disguises it — two decimal places is what a measurement looks like. Baskr refuses past 300% and names the strand.
if (!hn) continue; // no price -> skip
bs += weight;
chg24 = ss / bs // divided by weight FOUNDDivide by the weight you found and a pack priced from 39% of itself prints a number that looks like the whole. Baskr divides by 100 or does not divide.
Everything people ask before their first pack.
There is no path to hold them yet. When there is, a pack buy will be a batch of swaps signed by your own wallet — no pool wallet, no stored key, nothing of yours in a database. The dissection that started this project found a public table with a column named encrypted_private_key next to a headline reading “Non-custodial from the first click.” It was empty, and the claim held. This project will not put the column there in the first place.
A list of mints with weights that sum to exactly 100. Nothing else qualifies: a set of weights summing to 99.4 is refused before anything is priced, and a pack listing the same mint twice is refused too. Both are checked by scripts/check.mjs, not by anyone remembering.
Because there is no backend yet, so no constituent carries a price. Null is not zero. A pack with an unpriced strand cannot produce a figure, including ours, and the site would rather look empty than look confident. This is the rule applied to us first.
Green and red are the up/down axis, and they drag the eye to the wrong question. This site answers a different one first: can the figure be read at all? So the palette carries exactly two state colours, and the sign of a number is carried by its glyph. A read figure is the same blue at +40% and at −40%.
Nothing prints. The common shortcut is to divide the weighted change by the weight you found, which makes a pack priced from 39% of itself display a number that looks like the whole. Here the divisor is the constant 100 or there is no division.
It did not move 195,257% — it listed yesterday from about zero. Clamping that to a tidy +999.00% does not fix it, it disguises it. Past 300% the whole figure is refused and the strand responsible is named.
Yes. Create a Baskr, pick from the verified mints, set weights that sum to 100, and publish. Your wallet signs a readable sentence naming the pack and you as its creator — nothing is spent, it is a message, not a transaction. The server checks every field again before storing anything: a pack whose weights do not sum to 100, or that names a mint this project has not verified, is refused rather than saved for a renderer to refuse later.