opnet 1.8.0 → 1.8.1-beta.1

package/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,90 @@
+name: Bug Report
+description: Report a bug in opnet
+title: "[Bug]: "
+labels: ["bug", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report a bug.
+
+        **Security Notice**: If this is a security vulnerability, DO NOT create a public issue. Report it privately via [GitHub Security Advisories](https://github.com/btc-vision/opnet/security/advisories/new).
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Bug Description
+      description: A clear and concise description of the bug.
+      placeholder: Describe the bug...
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to Reproduce
+      description: Steps to reproduce the behavior.
+      placeholder: |
+        1. ...
+        2. ...
+        3. ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What did you expect to happen?
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: What actually happened?
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: opnet Version
+      description: What version of opnet are you using?
+      placeholder: "1.8.0"
+    validations:
+      required: true
+
+  - type: input
+    id: node-version
+    attributes:
+      label: Node.js Version
+      description: What version of Node.js are you using?
+      placeholder: "22.0.0"
+    validations:
+      required: true
+
+  - type: textarea
+    id: code
+    attributes:
+      label: Code Example
+      description: Minimal code that reproduces the issue.
+      render: typescript
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant Logs
+      description: Please copy and paste any relevant log output.
+      render: shell
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Checklist
+      options:
+        - label: I have searched existing issues to ensure this bug hasn't been reported
+          required: true
+        - label: This is NOT a security vulnerability (those should be reported privately)
+          required: true

package/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Security Vulnerability
+    url: https://github.com/btc-vision/opnet/security/advisories/new
+    about: Report a security vulnerability privately. DO NOT create a public issue for security vulnerabilities.
+  - name: OPNet Website
+    url: https://opnet.org/
+    about: Visit the OPNet homepage for documentation and support.

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,43 @@
+## Description
+<!-- Brief description of the changes in this PR -->
+
+## Type of Change
+<!-- Mark the relevant option with an "x" -->
+
+- [ ] Bug fix (non-breaking change that fixes an issue)
+- [ ] New feature (non-breaking change that adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+- [ ] Performance improvement
+- [ ] Refactoring (no functional changes)
+- [ ] Documentation update
+- [ ] CI/CD changes
+- [ ] Dependencies update
+
+## Checklist
+
+### Build & Tests
+- [ ] `npm install` completes without errors
+- [ ] `npm test` passes all tests
+
+### Code Quality
+- [ ] Code follows the project's coding standards
+- [ ] No new compiler warnings introduced
+- [ ] Error handling is appropriate
+
+### Documentation
+- [ ] Code comments added for complex logic
+- [ ] Public APIs are documented
+- [ ] README updated (if applicable)
+
+### Security
+- [ ] No sensitive data (keys, credentials) committed
+- [ ] No new security vulnerabilities introduced
+
+## Testing
+<!-- Describe how you tested these changes -->
+
+## Related Issues
+<!-- Link any related issues: Fixes #123, Relates to #456 -->
+
+---
+By submitting this PR, I confirm that my contribution is made under the terms of the project's license.

package/.github/changelog-config.json

@@ -0,0 +1,45 @@
+{
+  "categories": [
+    {
+      "title": "### Breaking Changes",
+      "labels": ["breaking", "breaking-change", "BREAKING-CHANGE"]
+    },
+    {
+      "title": "### Features",
+      "labels": ["feature", "feat", "enhancement"]
+    },
+    {
+      "title": "### Bug Fixes",
+      "labels": ["bug", "fix", "bugfix"]
+    },
+    {
+      "title": "### Performance",
+      "labels": ["performance", "perf"]
+    },
+    {
+      "title": "### Documentation",
+      "labels": ["documentation", "docs"]
+    },
+    {
+      "title": "### Dependencies",
+      "labels": ["dependencies", "deps"]
+    },
+    {
+      "title": "### Other Changes",
+      "labels": []
+    }
+  ],
+  "sort": {
+    "order": "ASC",
+    "on_property": "mergedAt"
+  },
+  "template": "#{{CHANGELOG}}",
+  "pr_template": "- #{{TITLE}} (#{{NUMBER}}) by @#{{AUTHOR}}",
+  "empty_template": "- No changes",
+  "max_tags_to_fetch": 200,
+  "max_pull_requests": 200,
+  "max_back_track_time_days": 365,
+  "tag_resolver": {
+    "method": "semver"
+  }
+}

package/.github/workflows/ci.yml

@@ -3,10 +3,10 @@ name: CI for OPNET
 on:
   push:
     tags:
-      - '*'
+      - 'v*'
 
 jobs:
-  build_and_publish:
+  publish:
     runs-on: ubuntu-latest
 
     permissions:
@@ -15,10 +15,12 @@ jobs:
 
     steps:
       - name: Checkout code
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
 
       - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version: '24.x'
           registry-url: 'https://registry.npmjs.org'
@@ -35,16 +37,157 @@ jobs:
       - name: Build browser assets
         run: npm run browserBuild
 
+      - name: Determine npm tag
+        id: npm_tag
+        run: |
+          VERSION="${{ github.ref_name }}"
+          if [[ "$VERSION" == *"-alpha"* ]]; then
+            echo "tag=alpha" >> $GITHUB_OUTPUT
+          elif [[ "$VERSION" == *"-beta"* ]]; then
+            echo "tag=beta" >> $GITHUB_OUTPUT
+          elif [[ "$VERSION" == *"-rc"* ]]; then
+            echo "tag=rc" >> $GITHUB_OUTPUT
+          else
+            echo "tag=latest" >> $GITHUB_OUTPUT
+          fi
+          echo "Determined npm tag: $(cat $GITHUB_OUTPUT | grep tag | cut -d= -f2)"
+
       - name: Publish to npm
-        run: npm publish --access public
+        run: npm publish --access public --tag ${{ steps.npm_tag.outputs.tag }}
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+  release:
+    runs-on: ubuntu-latest
+    needs: publish
+
+    permissions:
+      contents: write
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Generate changelog
+        id: changelog
+        uses: mikepenz/release-changelog-builder-action@v6
+        with:
+          configurationJson: |
+            {
+              "categories": [
+                {
+                  "title": "### Breaking Changes",
+                  "labels": ["breaking", "breaking-change", "BREAKING-CHANGE"]
+                },
+                {
+                  "title": "### Features",
+                  "labels": ["feature", "feat", "enhancement"]
+                },
+                {
+                  "title": "### Bug Fixes",
+                  "labels": ["bug", "fix", "bugfix"]
+                },
+                {
+                  "title": "### Performance",
+                  "labels": ["performance", "perf"]
+                },
+                {
+                  "title": "### Documentation",
+                  "labels": ["documentation", "docs"]
+                },
+                {
+                  "title": "### Dependencies",
+                  "labels": ["dependencies", "deps"]
+                },
+                {
+                  "title": "### Other Changes",
+                  "labels": []
+                }
+              ],
+              "sort": {
+                "order": "ASC",
+                "on_property": "mergedAt"
+              },
+              "template": "#{{CHANGELOG}}",
+              "pr_template": "- #{{TITLE}} ([##{{NUMBER}}](#{{URL}})) by @#{{AUTHOR}}",
+              "empty_template": "- No changes",
+              "max_tags_to_fetch": 200,
+              "max_pull_requests": 200,
+              "max_back_track_time_days": 365,
+              "tag_resolver": {
+                "method": "semver"
+              }
+            }
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Update CHANGELOG.md
+        env:
+          CHANGELOG_CONTENT: ${{ steps.changelog.outputs.changelog }}
+        run: |
+          TAG="${{ github.ref_name }}"
+          DATE=$(date +%Y-%m-%d)
+          NEW_HEADER="## [$TAG] - $DATE"
+
+          # Write changelog content to temp file using env var (avoids shell escaping)
+          printf '%s\n' "$CHANGELOG_CONTENT" > /tmp/new_entry.md
+
+          if [ -f CHANGELOG.md ]; then
+            # Create new file with entry inserted after header line
+            {
+              head -n 1 CHANGELOG.md
+              echo ""
+              echo "$NEW_HEADER"
+              echo ""
+              cat /tmp/new_entry.md
+              echo ""
+              tail -n +2 CHANGELOG.md
+            } > /tmp/CHANGELOG_NEW.md
+            mv /tmp/CHANGELOG_NEW.md CHANGELOG.md
+          else
+            # Create new CHANGELOG.md
+            {
+              echo "# Changelog"
+              echo ""
+              echo "All notable changes to this project will be documented in this file."
+              echo ""
+              echo "This changelog is automatically generated from merged pull requests."
+              echo ""
+              echo "$NEW_HEADER"
+              echo ""
+              cat /tmp/new_entry.md
+            } > CHANGELOG.md
+          fi
+
+          rm -f /tmp/new_entry.md
+
+      - name: Commit changelog
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          git add CHANGELOG.md
+          git diff --staged --quiet || git commit -m "docs: update CHANGELOG.md for ${{ github.ref_name }}"
+          git push origin HEAD:main || echo "No changes to push or push failed"
+
+      - name: Determine if prerelease
+        id: prerelease
+        run: |
+          VERSION="${{ github.ref_name }}"
+          if [[ "$VERSION" == *"-alpha"* ]] || [[ "$VERSION" == *"-beta"* ]] || [[ "$VERSION" == *"-rc"* ]]; then
+            echo "is_prerelease=true" >> $GITHUB_OUTPUT
+          else
+            echo "is_prerelease=false" >> $GITHUB_OUTPUT
+          fi
 
       - name: Create GitHub Release
-        uses: actions/create-release@v1
+        uses: softprops/action-gh-release@v2
         with:
           tag_name: ${{ github.ref_name }}
-          release_name: Release ${{ github.ref_name }}
-          body: |
-            Automated release for OPNET.
+          name: Release ${{ github.ref_name }}
+          body: ${{ steps.changelog.outputs.changelog }}
+          prerelease: ${{ steps.prerelease.outputs.is_prerelease == 'true' }}
+          generate_release_notes: false
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-

package/CHANGELOG.md

@@ -0,0 +1,20 @@
+# Changelog
+
+## [v1.8.1-alpha.0] - 2026-01-21
+
+### Other Changes
+
+- Refactor ABI interfaces and events for OPNet and stablecoins ([#110](https://github.com/btc-vision/opnet/pull/110)) by @BlobMaster41
+- Update docs for mnemonic-based wallet usage and add tables of contents ([#114](https://github.com/btc-vision/opnet/pull/114)) by @BlobMaster41
+- Bump version to 1.8.0 ([#115](https://github.com/btc-vision/opnet/pull/115)) by @BlobMaster41
+- Add security policy, templates, and extended ABI support ([#118](https://github.com/btc-vision/opnet/pull/118)) by @BlobMaster41
+- update motochef factory and template motochef abi/interface ([#117](https://github.com/btc-vision/opnet/pull/117)) by @icedevera
+- Bump version to 1.8.1-alpha.0 ([#119](https://github.com/btc-vision/opnet/pull/119)) by @BlobMaster41
+- ⬆️(deps-dev): Bump vite-plugin-node-polyfills from 0.24.0 to 0.25.0 in the dev-deps group ([#116](https://github.com/btc-vision/opnet/pull/116)) by @dependabot[bot]
+
+
+
+
+All notable changes to this project will be documented in this file.
+
+This changelog is automatically generated from merged pull requests.

package/CONTRIBUTING.md

@@ -1,71 +1,78 @@
 # Contributing Guidelines
 
-Thank you for considering contributing to our project! Please take a moment to
-review the following guidelines before submitting your contribution.
+Thank you for considering contributing to OPNet! Please take a moment to review the following guidelines before submitting your contribution.
+
+## Security
+
+**DO NOT** open public issues for security vulnerabilities. Report them privately via [GitHub Security Advisories](https://github.com/btc-vision/opnet/security/advisories/new).
+
+See [SECURITY.md](./SECURITY.md) for our full security policy.
 
 ## Pull Requests
 
-When submitting a pull request, please make sure to follow these guidelines:
+When submitting a pull request, please use our [pull request template](./.github/PULL_REQUEST_TEMPLATE.md) and follow these guidelines:
 
 ### Before You Begin
 
-1. **Fork the repository**: If you haven't already, fork the repository to your
-   GitHub account.
+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.
+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.
+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.
+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.
+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.
+3. **Test your changes**: Before submitting your pull request, make sure to test your changes thoroughly:
+   ```bash
+   npm install
+   npm test
+   npm run build
+   ```
 
 ### 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.
+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.
+2. **Complete the PR template**: Fill out all sections of the pull request template, including the type of change and checklist items.
 
-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`).
+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 (`Fixes #123` or `Relates to #456`).
 
-4. **Review and address feedback**: Be responsive to any feedback or comments
-   you receive on your pull request and make any necessary changes.
+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:
+When submitting an issue, please use the appropriate template:
+
+- **Bug reports**: Use the [bug report template](https://github.com/btc-vision/opnet/issues/new?template=bug_report.yml)
+- **Feature requests**: Use the [feature request template](https://github.com/btc-vision/opnet/issues/new?template=feature_request.md)
+
+### Guidelines for Issues
+
+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**: Include your Node.js version and opnet version in bug reports.
 
-1. **Use a descriptive title**: Use a clear and descriptive title that
-   summarizes the issue you're experiencing.
+5. **Check for existing issues**: Before submitting a new issue, please check if a similar issue has already been reported to avoid duplicates.
 
-2. **Provide detailed steps to reproduce**: Include detailed steps to reproduce
-   the issue, including any relevant code or configuration.
+## Development Setup
 
-3. **Include relevant information**: Provide any relevant information such as
-   error messages, screenshots, or logs that can help diagnose the problem.
+```bash
+git clone https://github.com/btc-vision/opnet.git
+cd opnet
+npm install
+npm run build
+```
 
-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.
+## License
 
-5. **Check for existing issues**: Before submitting a new issue, please check if
-   a similar issue has already been reported to avoid duplicates.
+By contributing, you agree that your contributions will be licensed under the project's [Apache-2.0](./LICENSE) license.
 
 Thank you for your contributions!

package/README.md

@@ -9,6 +9,27 @@
 
 The official client library for building Bitcoin-based applications on OPNet. Full TypeScript support with type-safe contract interactions.
 
+## Security Audit
+
+<p align="center">
+  <a href="https://verichains.io">
+    <img src="https://raw.githubusercontent.com/btc-vision/contract-logo/refs/heads/main/public-assets/verichains.png" alt="Verichains" width="100"/>
+  </a>
+</p>
+
+<p align="center">
+  <a href="https://verichains.io">
+    <img src="https://img.shields.io/badge/Security%20Audit-Verichains-4C35E0?style=for-the-badge" alt="Audited by Verichains"/>
+  </a>
+  <a href="./SECURITY.md">
+    <img src="https://img.shields.io/badge/Security-Report-22C55E?style=for-the-badge" alt="Security Report"/>
+  </a>
+</p>
+
+This library has been professionally audited by [Verichains](https://verichains.io).
+
+See [SECURITY.md](./SECURITY.md) for details.
+
 ## Installation
 
 ```bash
@@ -104,15 +125,29 @@ npm install
 npm run build
 ```
 
-## Links
+## Contributing
 
-- [OPNet Website](https://opnet.org)
-- [GitHub](https://github.com/btc-vision/opnet)
+1. Fork the repository
+2. Create a feature branch
+3. Make your changes
+4. Run tests: `npm test`
+5. Submit a pull request
 
-## Contributing
+See the [pull request template](./.github/PULL_REQUEST_TEMPLATE.md) for requirements.
 
-Contributions welcome! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
+## Reporting Issues
+
+- **Bugs**: Use the [bug report template](https://github.com/btc-vision/opnet/issues/new?template=bug_report.yml)
+- **Security**: See [SECURITY.md](./SECURITY.md) - do not open public issues for vulnerabilities
 
 ## License
 
 [Apache-2.0](LICENSE)
+
+## Links
+
+- [OPNet](https://opnet.org)
+- [Documentation](./docs/)
+- [GitHub](https://github.com/btc-vision/opnet)
+- [npm](https://www.npmjs.com/package/opnet)
+- [Verichains](https://verichains.io)

package/SECURITY.md

@@ -0,0 +1,70 @@
+# Security Policy
+
+<p align="center">
+  <a href="https://verichains.io">
+    <img src="https://raw.githubusercontent.com/btc-vision/contract-logo/refs/heads/main/public-assets/verichains.png" alt="Verichains" width="150"/>
+  </a>
+</p>
+
+<p align="center">
+  <a href="https://verichains.io">
+    <img src="https://img.shields.io/badge/Security%20Audit-Verichains-4C35E0?style=for-the-badge" alt="Audited by Verichains"/>
+  </a>
+</p>
+
+## Audit Status
+
+| Component | Status  | Auditor                             |
+|-----------|---------|-------------------------------------|
+| opnet     | Audited | [Verichains](https://verichains.io) |
+
+## Supported Versions
+
+| Version | Status        |
+|---------|---------------|
+| 1.8.x   | Supported     |
+| < 1.7   | Not supported |
+
+## Reporting a Vulnerability
+
+**DO NOT** open a public GitHub issue for security vulnerabilities.
+
+Report vulnerabilities through [GitHub Security Advisories](https://github.com/btc-vision/opnet/security/advisories/new).
+
+Include:
+- Description of the vulnerability
+- Affected version(s)
+- Steps to reproduce
+- Potential impact
+- Suggested fix (if any)
+
+### Response Timeline
+
+| Action                   | Timeframe   |
+|--------------------------|-------------|
+| Initial response         | 48 hours    |
+| Vulnerability assessment | 7 days      |
+| Patch development        | 14-30 days  |
+| Public disclosure        | After patch |
+
+## Security Scope
+
+### In Scope
+
+- Provider implementations (JSON-RPC, WebSocket)
+- Contract interactions and ABI encoding/decoding
+- Transaction building and signing
+- UTXO management
+- Cryptographic operations
+
+### Out of Scope
+
+- Third-party dependencies (report to respective maintainers)
+- User application logic errors
+- Issues in development/test environments only
+
+## Contact
+
+- **Security Issues**: [GitHub Security Advisories](https://github.com/btc-vision/opnet/security/advisories)
+- **General Issues**: [GitHub Issues](https://github.com/btc-vision/opnet/issues)
+- **Website**: [opnet.org](https://opnet.org)

package/browser/_version.d.ts

@@ -1 +1 @@
-export declare const version = "1.8.0";
+export declare const version = "1.8.1-beta.1";

package/browser/abi/shared/interfaces/motoswap/IMotoChefFactory.d.ts

@@ -79,14 +79,14 @@ export type OnOP20Received = CallResult<{
 }, []>;
 export interface IMotoChefFactory extends IOP_NETContract {
     owner(): Promise<Owner>;
-    initialize(motoTokenAddress: Address): Promise<InitializeFactory>;
+    initialize(): Promise<InitializeFactory>;
     pauseFactory(): Promise<PauseFactory>;
     unpauseFactory(): Promise<UnpauseFactory>;
     isPaused(): Promise<IsPaused>;
     getTokenDeployer(tokenAddress: Address): Promise<GetTokenDeployer>;
     getTokenOwner(tokenAddress: Address): Promise<GetTokenOwner>;
     deployToken(maxSupply: bigint, decimals: number, name: string, symbol: string, initialMintTo: Address, initialMintAmount: bigint, freeMintSupply: bigint, freeMintPerTx: bigint, tokenOwner: Address): Promise<DeployToken>;
-    deployMotoChef(devAddress: Address, tokenPerBlock: bigint, bonusEndBlock: bigint, bonusMultiplier: bigint, BTCAllocPoint: bigint, tokenAddress: Address, tokenAllocPoint: bigint, userBTCFeePercentage: bigint, userFeeRecipient: string, farmName: string, farmBanner: string, additionalPoolTokens: Address[], additionalPoolAllocPoints: bigint[]): Promise<DeployMotoChef>;
+    deployMotoChef(tokenPerBlock: bigint, bonusEndBlock: bigint, bonusMultiplier: bigint, BTCAllocPoint: bigint, tokenAddress: Address, tokenAllocPoint: bigint, userBTCFeePercentage: bigint, userFeeRecipient: string, farmName: string, farmBanner: string, additionalPoolTokens: Address[], additionalPoolAllocPoints: bigint[]): Promise<DeployMotoChef>;
     updateTokenOwner(tokenAddress: Address, newOwner: Address): Promise<UpdateTokenOwner>;
     getUserTokens(deployer: Address): Promise<GetUserTokens>;
     getDeploymentInfo(deployer: Address): Promise<GetDeploymentInfo>;