All 12 answers

An ERC-20 standing for a claim on a vault. One Tablet is worth totalAssets / totalSupply of the underlying, and because totalAssets is a storage variable that moves on harvest, that number does not fall.

It is an ordinary token, so a wallet, a DEX or a lending market can handle it without special support — which is a claim about ERC-20, not about ERC-4626. See the next answer.

That is a question with a checkable answer, which is why it is here. ERC-4626 requires maxDeposit, maxMint, maxWithdraw and maxRedeem, and requires that they MUST NOT revert. Vaults in this category routinely ship without them and claim the standard anyway; an integrator's first call then reverts.

Nacre's vault implements all four. Nothing is deployed, so the honest form of the claim is: the interface is written and it is not running anywhere.

It does not arrive as a reward you claim. Harvested fees are credited to the vault while the share supply is unchanged, so each share redeems for more than before. Sell the share and the accrual goes with it, priced in.

No, and this is the most important answer on the site. The share price is denominated in the pool asset and moves only when fees are credited. It does not include the asset's own price, and under storage accounting it cannot include divergence loss on the position underneath.

A monotone price is an accounting artefact. Your return is on /tablet, it has three negative terms, and the share price is one positive term inside it.

Nothing. Not a vault, not a hook, not a token. The deployments table on /security has a row per component and every row says so.

There has been no external review of anything, and the guarantee most worth attacking — that no privileged call can reach principal — is the one that most needs it.

No. contractAddress in the brand configuration is an empty string and the address pill removes itself rather than printing zeroes. A copyable address in a hero with no stated utility is a purchase prompt, and that is rule 15.

There are none. Every figure here is either a published parameter, a derived count of something on the page, or a real measurement of the optics behind the palette and the hero. No price, TVL, APY or volume appears anywhere, because none of them would be real.

Yes. You hold the pool's underlying exposure including the asset's own price risk, and a liquidity position gives up value against simply holding whenever the price moves. A share token changes the liquidity of the position, not its risk.

Narrower than it sounds, and the narrow version is the honest one. Signing an intent instead of a swap keeps the order out of the public mempool before it settles. It does not make the settlement private: the fill is a transaction on a public chain and anybody can read it afterwards.

Aperture is unset. The batch interval, the solver set and the slippage bound are all undecided and listed as such on /umbo.

Because the pricing question has no accepted answer and pretending otherwise is the failure mode. A US equity's reference venue is open 32.5 hours of 168. For the other 135.5 the token trades against nothing, and every design either quotes a stale price or quotes one nobody can arbitrage against.

It is a patch of nacre, seen from above, and each cell is one aragonite tablet. The colour is computed — the reflectance of a 32-bilayer stack by transfer matrix, integrated against the CIE 1931 colour matching functions — and it changes because the stack is getting thicker.

It is there because it is the argument. Interference is periodic in optical thickness, so the map from thickness to colour is not one-to-one: two stacks 160nm apart in tablet thickness are the same colour to an OKLab difference of 0.011. The observable does not tell you how much is underneath it, which is exactly what a monotone share price does not tell you about a position.

The hues are. Every accent is the colour a real nacre stack reflects at a stated tablet thickness, and node tools/palette.mjs reproduces each one after running twelve self-checks. Lightness and chroma are chosen, because a reflectance spectrum fixes a chromaticity and has no opinion about how bright a swatch should be.

The provenance, including the three things that could make every hex wrong and which of them actually matters, is on /umbo.