> For the complete documentation index, see [llms.txt](https://docs.valueqube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valueqube.io/lite-paper/6.-account-value-flow.md). # 6. Account Value Flow ValueQube account value flows around qAsset Certificates, not around a single dollar-denominated receipt. If a user subscribes with 1,000 USDC and the qSTRC reference value is 1.00 at confirmation, the user receives 1,000 qSTRC units. If the later reference value is 1.05, the account reference value is 1,050 USD. If the later reference value is 0.97, the account reference value is 970 USD. This example is not a return promise. It shows how account value is attributed by confirmed units and reference value. Different qAssets follow their own confirmation price, valuation method, fee rules, distribution rules, and redemption windows. New subscriptions are confirmed at the current reference value. Later users do not top up earlier users. Earlier users do not transfer hidden value to later users. Account value, distributions, risk, and exit rules are attributed by each user's own confirmation batch. The protocol also separates three flows: qAsset account value, platform service fees, and $54Q platform-token value feedback. These flows may connect by rule, but they should not be confused. #### Reference Value Formula The basic accounting logic can be expressed simply: ```  Confirmed qAsset Units = Confirmed Subscription Amount / Confirmation Reference Value  Account Reference Value = Confirmed qAsset Units x Current Reference Value ``` Fees, distributions, reinvestment, and redemption rules may modify what is claimable or withdrawable, but they should not erase the original confirmation batch. This protects the account record from becoming vague after multiple events. #### Batch Fairness Batch fairness is important because qAsset is an account certificate. Each user enters at a confirmation reference value and receives a unit record tied to that confirmation. Later subscriptions are priced by later reference values. This is what prevents the system from using new users to repair old accounts or allowing old accounts to absorb hidden value from new entries. The same principle applies to exits. Redemption windows, queues, and settlement timing should be visible in the qAsset state, not hidden in off-interface operations. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.valueqube.io/lite-paper/6.-account-value-flow.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.