Post #454

Revised condition: The stablecoin is 1:1 backed by cash, short-term US treasuries, and tokenized US treasury or money market funds to the extent permitted under applicable regulatory frameworks. Aligned issuers must also provide par redemption at all times, with a publicly disclosed and timely redemption service consistent with their applicable regulatory regime. These conditions can be revisited by the validators, in the spirit of building a regulatorily compliant chain for payments and banking opportunities. The guiding requirement is that a large percentage of the world's circulating dollars could compliantly be converted to the aligned stablecoin in the context of existing businesses and use cases in the financial world. 2. Full supply natively minted on HyperEVM. Any supply on other chains or offchain must first be minted on HyperEVM as the source chain. There was feedback here that this is overly restrictive technically. To clarify, crosschain transfers through any bridging protocols would not violate this requirement, as long as the supply is first minted on HyperEVM. Many chains use a designated source chain for minting, while offering a seamless multichain experience for users. The motivation behind the requirement is not restriction, but rather ease of technical accounting on the protocol level. It is difficult for validators to report the crosschain supply of a token, but it is more straightforward to slash on the condition that all supply must be minted first on HyperEVM. As long as this requirement is met, the protocol yield share can be computed as part of onchain execution. 3. The issuer exclusively issues this one asset. The issuer may work on other products, but they must synergize with the aligned stablecoin. Examples include neobanks and payments denominated in the stablecoin. & 4. The issuer cannot benefit from any other form of yield income or asset issuance. One clarification here is that "issuer" can be distinct from the "deployer." Many teams will build on top of technical infrastructure for issuance. Here and elsewhere, "issuer" has been replaced with "deployer" to broaden the scope. The intention behind this requirement is that the deployer shares half of its yield income with the protocol, and focuses its entire effort on supporting the aligned stablecoin. Revised condition (for 3&4): The deployer can only deploy assets that directly support the aligned stablecoin. For example, the underlying treasuries could be issued onchain. The net effect is that the deployer must share half of its yield income through the existence of the aligned stablecoin. The deployer and its affiliates may not receive any economic benefits tied to conversion of the aligned stablecoin into another asset. "Benefit" includes but is not limited to revenue share, order-flow payments or any form of rate-linked compensation. In sum, the updated requirements would be as follows: Onchain requirements: 1. Enabled as a permissionless quote token 2. 800k additional staked HYPE by deployer, meaning a total of 1M staked HYPE including the 200k staked HYPE for the quote token deployment. This is to give builders and users assurance to use the aligned stablecoin. 3. 50% of the deployer’s offchain reserve income must flow to the protocol. Validators may vote to update the calculation methodology as regulatory standards evolve. There will be follow-up work on the precise definition of risk-free rate, which will be updated according to an onchain stake-weighted median of validator reported values. A CoreWriter action will allow the deployer to reflect the exact minted balance from HyperEVM directly to HyperCore, which will allow a fully automated fee share mechanism as part of L1 execution.