The June 15 Apyx 2.0 post described a forthcoming RFQ system for approved counterparties. Current capitalization documentation now says Apyx offers that RFQ route, although the reviewed materials do not independently demonstrate completed executions. The same official materials conflict on mint price: the June post says minting and redemption occur at Redemption Value, while the current framework says new issuance is always $1. Redemption is described as a sale of preferred shares followed by USDC payment at the prevailing Redemption Value. The published RedemptionPoolV0 design requires ROLE_REDEEMER, but the official address registry does not identify a deployed pool. General holders usually trade through external permissionless markets.
Per-apxUSD Total Collateral Value is the full basket's market value divided by circulating units; per-apxUSD Redemption Value is the basket value assigned to routine redemption. Apyx's June 15 example put them at $1.02 and $1.00 respectively, making the $0.02 difference a per-token buffer. A collateral ratio above 100% therefore does not create an unconditional $1 redemption right. Apyx says that in a catastrophic event or wind-down the full reserve, including the buffer, would be distributed pro rata to remaining holders, while future APYX governance could deploy part of it during intermediate stress. This is Apyx's published framework, not independently verified execution, a legal title, or a guaranteed $1 payment.
apxUSD does not natively accrue dividends. A user seeking the yield product deposits it into apyUSD, a separate ERC-4626 vault. apyUSD's share price can rise as yield vests, while exits use separate receipt, delay and fee rules. Those vault mechanics should not be attributed to a plain apxUSD balance.
The Ethereum token is a UUPS proxy. On 2026-09-05 its implementation slot pointed to 0xdd71fd677fde2ed2579a3c45204f41a11016ccb4. The published ApxUSD.sol design places minting, upgrades, the supply cap, transfer pause, deny-list replacement and CCIP administration behind AccessManager roles, but function selectors do not identify the current role holders. RedemptionPoolV0 is a published design with separate rate, liquidity and pause controls; the reviewed registry did not list its deployment address. These are operational powers, not rights granted to every token holder.