Company: IPST
Filing Date: 2025-12-12
Form Type: S-1/A
Source: 0001213900-25-121277
Chunk: 188

Company: Heritage Distilling Holding Company, Inc.
Filing Date: 2025-12-12
Form: S-1/A
Chunk 188
---
 to any restrictions implemented by the application developer. Using these programs, users can create decentralized applications covering a variety of categories and subsectors, including games, marketplaces, AI agents and many more. In order to own, transfer or use $IP Tokens directly on the Story Network, a person generally must have internet access to connect to an access point on the Story Network and set up a third -partywallet, which is the software that safeguards a user’s key pair (public key plus secret key). $IP Token transactions may be made directly between end -userswithout the need for an intermediary. To transact on the Story Network, a user, typically through an application such as a wallet or smart contract, will broadcast the transaction to the current leader, who will organize the transactions into shards before the network processes and validates such transactions. Using cryptography and its proof -of-stakeconsensus mechanism, the Story Network can come to a shared state of the network in a decentralized fashion and without a centralized leader. Prior to transacting on the Story Network, a user generally must first install on its computer or mobile device a software program that will allow the user to generate a private and public key pair such as a wallet. The wallet also enables the user to connect to the Story Network, interact with decentralized applications, and transfer or swap $IP Tokens with other users or applications. Each user has its own key pair that is stored in such software, like a wallet. To receive $IP Tokens in a peer -to-peertransaction, the $IP Token recipient must provide its public key to the party initiating the transfer. This activity is analogous to a recipient for a transaction in U.S. dollars providing a routing address in wire instructions to the payor so that cash may be wired to the recipient’s account. The payor approves the transfer to the address provided by the recipient by “signing” a transaction that consists of the recipient’s public key with the private key of the address from where the payor is transferring the $IP Tokens. The recipient, however, does not make public or provide to the sender its private key (though the network can still verify the validity of the signature — i.e., that it was signed by the holder of the private key — using cryptography). As we are the custodian for all of our $IP Tokens, we maintain all of the private keys. We do not currently have insurance that would cover any loss of our $IP Tokens. Story Network validators record and confirm transactions when they validate and add blocks of information to