@btc-vision/transaction 1.0.97 → 1.0.99

package/.babelrc

@@ -1,7 +1,4 @@
-{
-    "sourceType": "module",
-    "presets": [
-        "@babel/preset-react",
-        "@babel/preset-env"
-    ]
-}
+{
+    "sourceType": "module",
+    "presets": ["@babel/preset-react", "@babel/preset-env", "@babel/preset-typescript"]
+}

package/.prettierrc.json

@@ -1,12 +1,12 @@
-{
-    "printWidth": 100,
-    "trailingComma": "all",
-    "tabWidth": 4,
-    "semi": true,
-    "singleQuote": true,
-    "quoteProps": "as-needed",
-    "bracketSpacing": true,
-    "bracketSameLine": true,
-    "arrowParens": "always",
-    "singleAttributePerLine": true
+{
+    "printWidth": 100,
+    "trailingComma": "all",
+    "tabWidth": 4,
+    "semi": true,
+    "singleQuote": true,
+    "quoteProps": "as-needed",
+    "bracketSpacing": true,
+    "bracketSameLine": true,
+    "arrowParens": "always",
+    "singleAttributePerLine": true
 }

package/CONTRIBUTING.md

@@ -1,71 +1,71 @@
-# Contributing Guidelines
-
-Thank you for considering contributing to our project! Please take a moment to
-review the following guidelines before submitting your contribution.
-
-## Pull Requests
-
-When submitting a pull request, please make sure to follow these guidelines:
-
-### Before You Begin
-
-1. **Fork the repository**: If you haven't already, fork the repository to your
-   GitHub account.
-
-2. **Create a new branch**: Create a new branch for your feature or bug fix.
-   This helps keep the main branch clean and makes it easier to review your
-   changes.
-
-3. **Ensure your code is up-to-date**: Before starting work, make sure your
-   forked repository is up-to-date with the latest changes from the main
-   repository.
-
-### Making Changes
-
-1. **Follow coding conventions**: Make sure your code follows the existing
-   coding style and conventions used in the project.
-
-2. **Write descriptive commit messages**: Write clear and descriptive commit
-   messages that explain the purpose of your changes.
-
-3. **Test your changes**: Before submitting your pull request, make sure to test
-   your changes thoroughly to ensure they work as expected.
-
-### Submitting the Pull Request
-
-1. **Create a descriptive title**: Use a clear and descriptive title for your
-   pull request that summarizes the purpose of your changes.
-
-2. **Provide a detailed description**: Include a detailed description of the
-   changes you've made and any relevant context that reviewers should know.
-
-3. **Link related issues**: If your pull request addresses a specific issue,
-   make sure to reference it in the description using GitHub's issue linking
-   syntax (`#issue_number`).
-
-4. **Review and address feedback**: Be responsive to any feedback or comments
-   you receive on your pull request and make any necessary changes.
-
-## Issues
-
-When submitting an issue, please provide as much information as possible to help
-us understand and address the problem. Follow these guidelines when creating an
-issue:
-
-1. **Use a descriptive title**: Use a clear and descriptive title that
-   summarizes the issue you're experiencing.
-
-2. **Provide detailed steps to reproduce**: Include detailed steps to reproduce
-   the issue, including any relevant code or configuration.
-
-3. **Include relevant information**: Provide any relevant information such as
-   error messages, screenshots, or logs that can help diagnose the problem.
-
-4. **Specify your environment**: If the issue is related to a specific
-   environment (e.g., operating system, browser), please specify it in your
-   issue description.
-
-5. **Check for existing issues**: Before submitting a new issue, please check if
-   a similar issue has already been reported to avoid duplicates.
-
-Thank you for your contributions!
+# Contributing Guidelines
+
+Thank you for considering contributing to our project! Please take a moment to
+review the following guidelines before submitting your contribution.
+
+## Pull Requests
+
+When submitting a pull request, please make sure to follow these guidelines:
+
+### Before You Begin
+
+1. **Fork the repository**: If you haven't already, fork the repository to your
+   GitHub account.
+
+2. **Create a new branch**: Create a new branch for your feature or bug fix.
+   This helps keep the main branch clean and makes it easier to review your
+   changes.
+
+3. **Ensure your code is up-to-date**: Before starting work, make sure your
+   forked repository is up-to-date with the latest changes from the main
+   repository.
+
+### Making Changes
+
+1. **Follow coding conventions**: Make sure your code follows the existing
+   coding style and conventions used in the project.
+
+2. **Write descriptive commit messages**: Write clear and descriptive commit
+   messages that explain the purpose of your changes.
+
+3. **Test your changes**: Before submitting your pull request, make sure to test
+   your changes thoroughly to ensure they work as expected.
+
+### Submitting the Pull Request
+
+1. **Create a descriptive title**: Use a clear and descriptive title for your
+   pull request that summarizes the purpose of your changes.
+
+2. **Provide a detailed description**: Include a detailed description of the
+   changes you've made and any relevant context that reviewers should know.
+
+3. **Link related issues**: If your pull request addresses a specific issue,
+   make sure to reference it in the description using GitHub's issue linking
+   syntax (`#issue_number`).
+
+4. **Review and address feedback**: Be responsive to any feedback or comments
+   you receive on your pull request and make any necessary changes.
+
+## Issues
+
+When submitting an issue, please provide as much information as possible to help
+us understand and address the problem. Follow these guidelines when creating an
+issue:
+
+1. **Use a descriptive title**: Use a clear and descriptive title that
+   summarizes the issue you're experiencing.
+
+2. **Provide detailed steps to reproduce**: Include detailed steps to reproduce
+   the issue, including any relevant code or configuration.
+
+3. **Include relevant information**: Provide any relevant information such as
+   error messages, screenshots, or logs that can help diagnose the problem.
+
+4. **Specify your environment**: If the issue is related to a specific
+   environment (e.g., operating system, browser), please specify it in your
+   issue description.
+
+5. **Check for existing issues**: Before submitting a new issue, please check if
+   a similar issue has already been reported to avoid duplicates.
+
+Thank you for your contributions!

package/LICENSE.md

@@ -1,62 +1,62 @@
-# Custom Software License Agreement
-
-## 1. Definitions
-
-- **"Licensor"** refers to the owner(s) and creator(s) of the software. The owner of the github organization "
-  btc-vision", "BlobMaster41".
-- **"User"** refers to any person or entity that accesses or uses the software.
-- **"Software"** refers to the source code, binaries, and documentation, whether in electronic or printed format, made
-  available by Licensor.
-
-## 2. Grant of License
-
-This License permits User to view the Software via the repository hosting the Software ("Hosting Service"). Except as
-provided in this Section, no other use of the Software is permitted. The User may not modify, copy, reproduce,
-republish, upload, post, transmit, or distribute the Software in any way.
-
-## 3. Restrictions
-
-- **Modification and Distribution**: User is prohibited from modifying, merging, distributing, sublicensing, and/or
-  selling copies of the Software.
-- **Commercial Use**: User is prohibited from using the Software for any commercial purposes.
-- **Reverse Engineering**: User is prohibited from reverse engineering, decompiling, or disassembling the Software.
-
-## 4. Termination
-
-This License is effective until terminated by the Licensor. It will terminate immediately without notice from the
-Licensor if User fails to comply with any provision of this License. Upon termination, User must destroy all copies of
-the Software.
-
-## 5. Release to Public
-
-This License restricts the above rights until the Software is officially released to the public by the Licensor. Upon
-such release, the terms of this License may be modified by the Licensor to allow broader use rights.
-
-## 6. Governing Law
-
-This License shall be governed by and construed in accordance with the laws of [Toronto, Canada]. Any legal action or
-proceeding arising under this License will be brought exclusively in the courts located in [Toronto], and the parties
-hereby consent to personal jurisdiction and venue therein.
-
-## 7. Limitation of Liability
-
-In no event will the Licensor be liable for any damages, including, without limitation, indirect, incidental, special,
-consequential, or punitive damages arising out of the use of or inability to use the Software.
-
-## 8. Indemnification
-
-User agrees to indemnify, defend, and hold harmless the Licensor and its affiliates, officers, agents, employees, and
-partners from any claim or demand, including reasonable attorneys' fees, made by any third party due to or arising out
-of User's use of the Software, User's violation of this License, or User's violation of any rights of another.
-
-## 9. Breach of License
-
-Any breach of this License will result in immediate termination of User's rights under this License. Additionally, the
-Licensor reserves the right to pursue any legal action against the User in the event of a breach of this License.
-
-## 10. Acknowledgment
-
-User acknowledges that they have read this License, understand it, and agree to be bound by its terms and conditions.
-User also agrees that this License is the complete and exclusive statement of the agreement between the Licensor and the
-User and supersedes all proposals or prior agreements, oral or written, and any other communications between the
-Licensor and the User relating to the subject matter of this License.
+# Custom Software License Agreement
+
+## 1. Definitions
+
+- **"Licensor"** refers to the owner(s) and creator(s) of the software. The owner of the github organization "
+  btc-vision", "BlobMaster41".
+- **"User"** refers to any person or entity that accesses or uses the software.
+- **"Software"** refers to the source code, binaries, and documentation, whether in electronic or printed format, made
+  available by Licensor.
+
+## 2. Grant of License
+
+This License permits User to view the Software via the repository hosting the Software ("Hosting Service"). Except as
+provided in this Section, no other use of the Software is permitted. The User may not modify, copy, reproduce,
+republish, upload, post, transmit, or distribute the Software in any way.
+
+## 3. Restrictions
+
+- **Modification and Distribution**: User is prohibited from modifying, merging, distributing, sublicensing, and/or
+  selling copies of the Software.
+- **Commercial Use**: User is prohibited from using the Software for any commercial purposes.
+- **Reverse Engineering**: User is prohibited from reverse engineering, decompiling, or disassembling the Software.
+
+## 4. Termination
+
+This License is effective until terminated by the Licensor. It will terminate immediately without notice from the
+Licensor if User fails to comply with any provision of this License. Upon termination, User must destroy all copies of
+the Software.
+
+## 5. Release to Public
+
+This License restricts the above rights until the Software is officially released to the public by the Licensor. Upon
+such release, the terms of this License may be modified by the Licensor to allow broader use rights.
+
+## 6. Governing Law
+
+This License shall be governed by and construed in accordance with the laws of [Toronto, Canada]. Any legal action or
+proceeding arising under this License will be brought exclusively in the courts located in [Toronto], and the parties
+hereby consent to personal jurisdiction and venue therein.
+
+## 7. Limitation of Liability
+
+In no event will the Licensor be liable for any damages, including, without limitation, indirect, incidental, special,
+consequential, or punitive damages arising out of the use of or inability to use the Software.
+
+## 8. Indemnification
+
+User agrees to indemnify, defend, and hold harmless the Licensor and its affiliates, officers, agents, employees, and
+partners from any claim or demand, including reasonable attorneys' fees, made by any third party due to or arising out
+of User's use of the Software, User's violation of this License, or User's violation of any rights of another.
+
+## 9. Breach of License
+
+Any breach of this License will result in immediate termination of User's rights under this License. Additionally, the
+Licensor reserves the right to pursue any legal action against the User in the event of a breach of this License.
+
+## 10. Acknowledgment
+
+User acknowledges that they have read this License, understand it, and agree to be bound by its terms and conditions.
+User also agrees that this License is the complete and exclusive statement of the agreement between the Licensor and the
+User and supersedes all proposals or prior agreements, oral or written, and any other communications between the
+Licensor and the User relating to the subject matter of this License.

package/README.md

@@ -1,76 +1,76 @@
-# OP_NET - Transaction Builder
-
-![Bitcoin](https://img.shields.io/badge/Bitcoin-000?style=for-the-badge&logo=bitcoin&logoColor=white)
-![TypeScript](https://img.shields.io/badge/TypeScript-007ACC?style=for-the-badge&logo=typescript&logoColor=white)
-![NodeJS](https://img.shields.io/badge/Node%20js-339933?style=for-the-badge&logo=nodedotjs&logoColor=white)
-![NPM](https://img.shields.io/badge/npm-CB3837?style=for-the-badge&logo=npm&logoColor=white)
-![Gulp](https://img.shields.io/badge/GULP-%23CF4647.svg?style=for-the-badge&logo=gulp&logoColor=white)
-![ESLint](https://img.shields.io/badge/ESLint-4B3263?style=for-the-badge&logo=eslint&logoColor=white)
-
-[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
-
-## Introduction
-
-The OP_NET Transaction Builder library allows you to create and sign transactions for the OP_NET network. Written in
-TypeScript, this library provides a comprehensive set of functions to facilitate the creation, reading, and manipulation
-of OP_NET transactions, smart contracts, and other OP_NET-related technologies.
-
-## Getting Started
-
-### Prerequisites
-
-- Node.js version 16.x or higher
-- npm (Node Package Manager)
-
-### Installation
-
-```shell
-npm i @btc-vision/transaction
-```
-
-### Documentation
-
-Documentation is available at [https://transaction.opnet.org](https://transaction.opnet.org) or in the `docs/` directory
-of the repository.
-
-#### Development
-
-1. Clone the repository:
-   ```bash
-   git clone https://github.com/btc-vision/transaction.git
-   ```
-2. Navigate to the repository directory:
-   ```bash
-   cd transaction
-   ```
-3. Install the required dependencies:
-   ```bash
-   npm i
-   ```
-
-## Deployments, Wrapping and Unwrapping
-
-WARNING: POSSIBLY OUTDATED
-
-To learn how to wrap and unwrap Bitcoin on OP_NET, please refer to
-the [Wrap.md](https://github.com/btc-vision/transaction/blob/main/Wrap.md) guide.
-
-To learn how to unwrap Bitcoin on OP_NET, please refer to
-the [Unwrap.md](https://github.com/btc-vision/transaction/blob/main/Unwrap.md) guide.
-
-To learn how to deploy smart contracts on OP_NET, please refer to
-the [Deploy.md](https://github.com/btc-vision/transaction/blob/main/Deploy.md) guide.
-
-## Usage
-
-OUTDATED EXAMPLE. New examples will be added soon.
-
-## Contribution
-
-Contributions are welcome! Please read through the `CONTRIBUTING.md` file for guidelines on how to submit issues,
-feature requests, and pull requests. We appreciate your input and encourage you to help us improve OP_NET.
-
-## License
-
-This project is open source and available under the [MIT License](LICENSE). If you have any suggestions or
-contributions, please feel free to submit a pull request.
+# OP_NET - Transaction Builder
+
+![Bitcoin](https://img.shields.io/badge/Bitcoin-000?style=for-the-badge&logo=bitcoin&logoColor=white)
+![TypeScript](https://img.shields.io/badge/TypeScript-007ACC?style=for-the-badge&logo=typescript&logoColor=white)
+![NodeJS](https://img.shields.io/badge/Node%20js-339933?style=for-the-badge&logo=nodedotjs&logoColor=white)
+![NPM](https://img.shields.io/badge/npm-CB3837?style=for-the-badge&logo=npm&logoColor=white)
+![Gulp](https://img.shields.io/badge/GULP-%23CF4647.svg?style=for-the-badge&logo=gulp&logoColor=white)
+![ESLint](https://img.shields.io/badge/ESLint-4B3263?style=for-the-badge&logo=eslint&logoColor=white)
+
+[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
+
+## Introduction
+
+The OP_NET Transaction Builder library allows you to create and sign transactions for the OP_NET network. Written in
+TypeScript, this library provides a comprehensive set of functions to facilitate the creation, reading, and manipulation
+of OP_NET transactions, smart contracts, and other OP_NET-related technologies.
+
+## Getting Started
+
+### Prerequisites
+
+- Node.js version 16.x or higher
+- npm (Node Package Manager)
+
+### Installation
+
+```shell
+npm i @btc-vision/transaction
+```
+
+### Documentation
+
+Documentation is available at [https://transaction.opnet.org](https://transaction.opnet.org) or in the `docs/` directory
+of the repository.
+
+#### Development
+
+1. Clone the repository:
+   ```bash
+   git clone https://github.com/btc-vision/transaction.git
+   ```
+2. Navigate to the repository directory:
+   ```bash
+   cd transaction
+   ```
+3. Install the required dependencies:
+   ```bash
+   npm i
+   ```
+
+## Deployments, Wrapping and Unwrapping
+
+WARNING: POSSIBLY OUTDATED
+
+To learn how to wrap and unwrap Bitcoin on OP_NET, please refer to
+the [Wrap.md](https://github.com/btc-vision/transaction/blob/main/Wrap.md) guide.
+
+To learn how to unwrap Bitcoin on OP_NET, please refer to
+the [Unwrap.md](https://github.com/btc-vision/transaction/blob/main/Unwrap.md) guide.
+
+To learn how to deploy smart contracts on OP_NET, please refer to
+the [Deploy.md](https://github.com/btc-vision/transaction/blob/main/Deploy.md) guide.
+
+## Usage
+
+OUTDATED EXAMPLE. New examples will be added soon.
+
+## Contribution
+
+Contributions are welcome! Please read through the `CONTRIBUTING.md` file for guidelines on how to submit issues,
+feature requests, and pull requests. We appreciate your input and encourage you to help us improve OP_NET.
+
+## License
+
+This project is open source and available under the [MIT License](LICENSE). If you have any suggestions or
+contributions, please feel free to submit a pull request.

package/browser/_version.d.ts

@@ -1 +1 @@
-export declare const version = "1.0.95";
+export declare const version = "1.0.96";

package/browser/bytecode/Compressor.d.ts

@@ -1,4 +1,3 @@
-/// <reference types="node" />
 export declare class Compressor {
     private static readonly zlibOptions;
     static compress(data: Uint8Array | Buffer): Buffer;

package/browser/crypto/crypto-browser.d.ts

@@ -1,33 +1,4 @@
-export function createHash(algo: any): import("@noble/hashes/utils").Hash<{
-    A: number;
-    B: number;
-    C: number;
-    D: number;
-    E: number;
-    F: number;
-    G: number;
-    H: number;
-    get(): [number, number, number, number, number, number, number, number];
-    set(A: number, B: number, C: number, D: number, E: number, F: number, G: number, H: number): void;
-    process(view: DataView, offset: number): void;
-    roundClean(): void;
-    destroy(): void;
-    readonly blockLen: number;
-    outputLen: number;
-    readonly padOffset: number;
-    readonly isLE: boolean;
-    buffer: Uint8Array;
-    view: DataView;
-    finished: boolean;
-    length: number;
-    pos: number;
-    destroyed: boolean;
-    update(data: import("@noble/hashes/utils").Input): any;
-    digestInto(out: Uint8Array): void;
-    digest(): Uint8Array;
-    _cloneInto(to?: any | undefined): any;
-    clone(): any;
-}> | import("@noble/hashes/utils").Hash<import("@noble/hashes/sha512").SHA512> | undefined;
+export function createHash(algo: any): import("@noble/hashes/utils").Hash<import("@noble/hashes/sha256").SHA256> | import("@noble/hashes/utils").Hash<import("@noble/hashes/sha512").SHA512> | undefined;
 export function createHmac(_algo: any, key: any): import("@noble/hashes/hmac").HMAC<any>;
 export function pbkdf2Sync(password: any, salt: any, iterations: any, keylen: any, _algo: any): Uint8Array;
 export function randomBytes(length: any): Uint8Array;

package/browser/crypto/crypto.d.ts

@@ -1,2 +1 @@
-/// <reference types="node" />
 export { createHash, createHmac, pbkdf2Sync, randomBytes } from 'crypto';

package/browser/generators/AddressGenerator.d.ts

@@ -1,4 +1,3 @@
-/// <reference types="node" />
 import { Network } from 'bitcoinjs-lib';
 export declare class AddressGenerator {
     static generatePKSH(sha256Hash: Buffer, network: Network): string;

package/browser/generators/Generator.d.ts

@@ -1,4 +1,3 @@
-/// <reference types="node" />
 import { Network } from 'bitcoinjs-lib';
 export declare abstract class Generator {
     static readonly DATA_CHUNK_SIZE: number;

package/browser/generators/builders/CalldataGenerator.d.ts

@@ -1,4 +1,3 @@
-/// <reference types="node" />
 import { Network } from 'bitcoinjs-lib';
 import { Generator } from '../Generator.js';
 import { Features } from '../Features.js';

package/browser/generators/builders/DeploymentGenerator.d.ts

@@ -1,4 +1,3 @@
-/// <reference types="node" />
 import { Network } from 'bitcoinjs-lib';
 import { Generator } from '../Generator.js';
 export declare class DeploymentGenerator extends Generator {

package/browser/generators/builders/MultiSignGenerator.d.ts

@@ -1,4 +1,3 @@
-/// <reference types="node" />
 export declare class MultiSignGenerator {
     static readonly MAXIMUM_SUPPORTED_SIGNATURE = 255;
     static compile(vaultPublicKeys: Buffer[], minimumSignatures?: number, internal?: Buffer): Buffer;