Private Keys Sample Clauses

The Private Keys clause defines the responsibilities and obligations related to the management and security of cryptographic private keys used in a contractual relationship. Typically, it specifies which party is responsible for generating, storing, and safeguarding private keys, and may outline procedures for reporting loss or compromise. This clause is essential for ensuring the integrity and security of digital transactions or assets, as it allocates risk and clarifies accountability in the event of unauthorized access or misuse of private keys.
Private Keys. ▇▇▇ ▇▇▇▇▇▇ purchased by Buyer may be held by ▇▇▇▇▇ in Buyer’s digital wallet or vault, which requires a private key, or a combination of private keys, for access. Loss of requisite private key(s) associated with Buyer’s digital wallet or vault storing WUN Tokens will result in loss of access to Buyer’s WUN Token balance and/or loss of such WUN Tokens. Any third party that gains access to such private key(s), including by gaining access to login credentials of a hosted wallet or vault service Buyer uses, may be able to misappropriate Buyer’s WUN Tokens. Seller is not responsible for any such losses. Seller is not responsible for a direct or indirect loss of WUN tokens purchased from Wunbit and/or biweekly token owner rewards, or non-receipt of WUN tokens or rewards, in case if Buyer uses a third-party wallet without access to his/her private keys for purchase or receipt of WUN tokens and token owner rewards. Buyer acknowledges, understands and accepts the risk related to the loss of private keys.
Private Keys. WINS Tokens purchased by Buyer may be held by ▇▇▇▇▇ in Buyer’s digital wallet or vault, which requires a private key, or a combination of private keys, for access. Loss of requisite private key(s) associated with ▇▇▇▇▇’s digital wallet or vault storing WINS Tokens will result in loss of access to Buyer’s WINS Token balance and/or loss of such WINS Tokens. Any third party that gains access to such private key(s), including by gaining access to login credentials of a hosted wallet or vault service Buyer uses, may be able to misappropriate Buyer’s WINS Tokens. Seller is not responsible for any such losses. Buyer acknowledges, understands and accepts the risk related to the loss of private keys.
Private Keys. Tokens purchased by Purchaser may be held by Purchaser in Purchaser’s digital wallet or vault, which requires a private key, or a combination of private keys, for access. Accordingly, loss of requisite private key(s) associated with Purchaser’s digital wallet or vault storing Tokens will most likely result in loss of such Tokens. Moreover, any third party that gains access to such private key(s), including by gaining access to login credentials of a hosted wallet or vault service Purchaser uses, may be able to misappropriate Purchaser’s Tokens. Token Generator is not responsible for any such losses.
Private Keys. Immutable will not have access to, or keep any copies of any Private Key in respect of any NFT minted using the Protocol, nor will Immutable have any title or interest in the NFTs which are listed, minted or traded by the Licensee using the Protocol other than the right to the Fees set out in this agreement.
Private Keys. The tokens and NFTs held by you in a digital wallet or vault of any blockchain, requires a private key, or a combination of private keys, for access. Accordingly, loss of requisite private key(s) associated with your digital wallet or vault and the password to our SUPACharge mobile application may result in your inability to access and use of our Services and App. Moreover, any third party that gains access to such private key(s), including by gaining access to login credentials, may be able to access your SUPACharge mobile application to use the Services and App. You are responsible to backup and secure your own private key(s), and SUPACharge will not be responsible for loss or theft of your private key(s) including any loss associated with this. SUPACharge does not store any of your private key(s) on our servers.
Private Keys. 9.1 Your mobile device securely stores all supported Cryptocurrency private keys (“Private Keys”) associated with Your Account. You accept and agree that you shall retain full ownership and control of the Private Keys associated with your Account and that You shall have full control of, access to, or the ability to use, such Private Keys. For example, but without limiting the generality of the foregoing, We will not: (i) be able to access your on-chain wallets and or any of the balances associated with any of the addresses associated derivable from the keys owned by you; (ii) be able to assist, refund, return or replace any crypto-currency or any wallet or any address related balance as a result of lost private keys, misplaced device or similar; 9.2 When you use Your lastbit Wallet to send or receive Cryptocurrency, the transaction must be confirmed and recorded in the public ledger associated with the relevant Cryptocurrency network (e.g. the Bitcoin network or the Ethereum network). That network is solely responsible for verifying and confirming any such transactions. We cannot confirm, cancel or reverse any transaction on a Cryptocurrency network, other than confirming to You through the user interface that the network has completed the transaction. 9.3 The mnemonic displayed on application setup is the root of all derived keys and credentials to use the lastbit mobile application. Any individual with access to this mnemonic can access all funds related to your bitcoin, lightning and debit card accounts. Lastbit will not be responsible for lost, misplaced, stolen or otherwise misused mnemonics. You consent to storing this mnemonic safely and understand that this mnemonic is a single point of failure if not used with a passphrase. Lastbit recommends best security practices by using a passphrase in addition to the mnemonic. 9.4 The mnemonic cannot be changed or otherwise modified once created. Every new mnemonic as per the Bitcoin Improvement Proposal 39 wordlist, will lead to the generation of a new, valid and unique wallet. Lastbit cannot control, influence or modify this outcome in the case of lost mnemonics, stolen private keys or other security breaches.

Related to Private Keys

  • Public/Private Information The Borrower shall cooperate with the Administrative Agent in connection with the publication of certain materials and/or information provided by or on behalf of the Borrower. Documents required to be delivered pursuant to the Loan Documents shall be delivered by or on behalf of the Borrower to the Administrative Agent and the Lenders (collectively, “Information Materials”) pursuant to this Article and the Borrower shall designate Information Materials (a) that are either available to the public or not material with respect to the Borrower and its Subsidiaries or any of their respective securities for purposes of United States federal and state securities laws, as “Public Information” and (b) that are not Public Information as “Private Information”.

  • Public Use The Recipient will ensure that Infrastructure resulting from any Eligible Project that is not sold, leased, encumbered, or otherwise disposed of, remains primarily for public use or benefit.

  • Public Works Installation work which is considered public works is excluded from purchase under this Contract. Historically, the New York State Bureau of Public Works has maintained that installation, maintenance, and repair of equipment attached to any wall, ceiling, or floor, or affixed by hard wiring or plumbing is public work. In contrast, installation of a piece of equipment which is portable or a “plug-in” free-standing unit would not be considered public work. Thus, this Contract does not authorize installation where the equipment becomes a permanent part of the building structure, or is otherwise incorporated into the fabric of the building (e.g. installation on a wall, ceiling, or floor in a fixed location, or affixed by hard-wiring or plumbing). See ▇▇▇▇▇▇▇▇ ▇, §▇▇ Prevailing Wage Rates – Public Works

  • Rule 144 Information The Company covenants that it will use its reasonable best efforts to timely file all reports and other documents required to be filed by it under the Securities Act and the Exchange Act and the rules and regulations promulgated by the SEC thereunder (or, if the Company is not required to file such reports, it will, upon the request of any Warrantholder, make publicly available such information as necessary to permit sales pursuant to Rule 144 under the Securities Act), and it will use reasonable best efforts to take such further action as any Warrantholder may reasonably request, in each case to the extent required from time to time to enable such holder to, if permitted by the terms of this Warrant and the Purchase Agreement, sell this Warrant without registration under the Securities Act within the limitation of the exemptions provided by (A) Rule 144 under the Securities Act, as such rule may be amended from time to time, or (B) any successor rule or regulation hereafter adopted by the SEC. Upon the written request of any Warrantholder, the Company will deliver to such Warrantholder a written statement that it has complied with such requirements.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.