@tari-project/tarijs 0.5.5 → 0.8.0

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -7,21 +7,11 @@ Motivation and Context
 How Has This Been Tested?
 ---
 
-What process can a PR reviewer use to test or verify this change?
----
-
-<!-- Checklist -->
-<!-- 1. Is the title of your PR in the form that would make nice release notes? The title, excluding the conventional commit
-tag, will be included exactly as is in the CHANGELOG, so please think about it carefully. -->
-
-
 Breaking Changes
 ---
 
 - [x] None
-- [ ] Requires data directory on base node to be deleted
-- [ ] Requires hard fork
-- [ ] Other - Please specify
+- [ ] Please specify
 
 <!-- Does this include a breaking change? If so, include this line as a footer -->
-<!-- BREAKING CHANGE: Description what the user should do, e.g. delete a database, resync the chain -->
+<!-- BREAKING CHANGE: Describe the breaking change -->

package/.github/workflows/check-package-versions.yml

@@ -0,0 +1,22 @@
+# Check package versions
+name: Check Package Versions
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    types:
+      - opened
+      - reopened
+      - synchronize
+
+jobs:
+  check_versions:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Check package.json versions
+        run: ./scripts/check_versions.sh

package/Dockerfile

@@ -19,9 +19,9 @@ RUN apt-get update && apt-get install -y \
     && /bin/bash -c "source ~/.bashrc && source ~/.profile"
 
 
-# Clone tari-dan repo at the same level (required for building)
+# Clone tari-ootle repo at the same level (required for building)
 WORKDIR /
-RUN git clone https://github.com/tari-project/tari-dan.git
+RUN git clone https://github.com/tari-project/tari-ootle.git
 
 # Set up project
 WORKDIR /app

package/README.md

@@ -12,7 +12,7 @@ Please read the [TODO](TODO.md) file for upcoming features.
 
 ## Library building
 
-You must have the [tari-dan](https://github.com/tari-project/tari-dan) repo cloned at the same folder level as this repo.
+You must have the [tari-ootle](https://github.com/tari-project/tari-ootle) repo cloned at the same folder level as this repo.
 
 ### Option 1: Local Build
 

package/docusaurus/tari-docs/docs/provider-vs-signer.md

@@ -0,0 +1,27 @@
+---
+sidebar_position: 1
+title: Providers vs Signers
+---
+
+# Introduction to Providers and Signers
+
+Tari.js provides two methods of interaction with the Ootle via built-in providers and signers.
+
+## What is a provider?
+
+A provider provides a bridge of communication between the application and the Ootle network for the purpose of retrieving publically accessible information from the chain. The provider allows a developer to call information from the Ootle without necessarily requiring a wallet or performing a transaction. Likewise, this means that a developer cannot use a provider to write or commit changes to the Ootle network.
+
+In Tari.js, the `Indexer Provider` class is provided for this purpose. You can read more about [the Provider here](./providers/indexer-provider.md).
+
+## What is a signer?
+
+A signer provides for one or more methods for authenticating a transaction or action, and for accessing additional functionality for interacting with the Ootle. In this way, a signer allows the user to perform specific actions via a verifiable manner.
+
+Tari.js provides three different signers for interacting with the Ootle, depending on the client you are using to interact with the Ootle. All of these utilise the `TariSigner` interface:
+
+- **WalletConnect Signer**: This class is to be used to connect a wallet that is compatible with the WalletConnect protocol to your application.
+- **Tari Universe Signer**: This class relies on the use of the Ootle wallet built into the [Tari Universe](https://airdrop.tari.com) application.
+- **Tari Wallet Daemon Signer** this class uses the Tari Wallet Daemon service for facilitating transactions, account management and more.
+
+You can read more about the [signers here](./category/signers)
+

package/docusaurus/tari-docs/docs/wallet/submit-transaction/transaction-builder/inputs.md

@@ -13,7 +13,6 @@ A required substate has one of the following types:
 - Vault
 - UnclaimedConfidentialOutput
 - NonFungible
-- NonFungibleIndex
 - TransactionReceipt
 - Template
 - ValidatorFeePool