Company: IPST
Filing Date: 2025-10-16
Form Type: S-1/A
Source: 0001213900-25-099309
Chunk: 200

Company: Heritage Distilling Holding Company, Inc.
Filing Date: 2025-10-16
Form: S-1/A
Chunk 200
---
 based on utilization of the network (which adjusts the frequency by which new blocks are created). The supply of $IP tokens is reduced when the base fee for transactions is burned. Additionally, certain actions by validators and delegators require one $IP token to be burned. The initially created one billion $IP tokens were distributed as follows: • Ecosystem and Community: approximately 384 million $IP tokens, or 38.4% of the initial supply, was allocated towards promoting ecosystem growth and community development by supporting developers, community members, and users of the Story Network across marketing, events, grants, and other activities. • Initial Incentives: approximately 100 million $IP tokens, or 10% of the initial supply, was issued to be disbursed as rewards to incentivize the growth of the Story ecosystem. • Story Foundation: approximately 100 million $IP tokens, or 10% of the initial supply, was allocated to Story Foundation to support its team, educational services, and growth efforts related to the Story Network. • Early Contributors: approximately 216 million $IP tokens, or 21.6% of the initial supply, was retained by early contributors and advisors to compensate for their early efforts in the development of the Story Network. • Core Contributors: approximately 200 million $IP tokens, or 20% of the initial supply, was allocated to be used as compensation for team members contributing to the development of the Story protocol. 118 Modifications to the Story Network The Story Network is open -sourceand community -governed. Its development is overseen by Story Foundation and supported by core developers and independent contributors. These stakeholders can propose protocol upgrades, but adoption requires widespread acceptance among validators and users, consistent with decentralized governance norms. The release of updates to the Story Network’s source code does not guarantee that the updates will be automatically adopted. As with other blockchain protocols, proposed upgrades are implemented only if a critical mass of validators and participants update their software. Users and nodes must accept any changes made to the Story source code by downloading a software implementation of the proposed modification. A modification of the Story Network’s source code is only effective with respect to the Story Network users that download it. If a modification is accepted only by a percentage of users and validators, a division in the Story Network may occur such that one network will run the pre -modificationsource code and the other network will run the modified source code. Such a division is known as a “fork.” Consequently, as a practical matter, a modification to the source