Your first Hashtree remote

1. Install the helper

You need Git first. On macOS or Linux, use the published installer:

curl -fsSL https://upload.iris.to/npub1xdhnr9mrv47kkrn95k6cwecearydeh8e895990n3acntwvmgk2dsdeeycm/releases%2Fhashtree/latest/install.sh | sh

The installer adds htree, htree-cashu, and git-remote-htree to ~/.local/bin by default. Make sure that directory is on your PATH.

If you use Rust, you can instead build the tools with Cargo:

cargo install hashtree-cli git-remote-htree

On Windows, use the prebuilt Windows archive and add its executables to your PATH; the shell installer above does not support Windows. See the installation documentation.

2. Clone a public repository

In Iris Git, open a repository and choose Code to copy its clone command. For example, this is the Hashtree source repository:

git clone htree://npub1xdhnr9mrv47kkrn95k6cwecearydeh8e895990n3acntwvmgk2dsdeeycm/hashtree

Cloning needs access to repository announcements and a server or peer holding the data.

3. Add a remote to your own project

In an existing Git repository with at least one commit, use an unused remote name and choose a repository name. This example publishes a public repository called my-project:

git remote add hashtree htree://self/my-project
git push hashtree HEAD

self refers to the CLI’s local signing identity. If there is no identity yet, the helper creates one. This may be different from the account signed into your browser. Keep a secure backup of your signing keys.

Your existing origin remote stays in place. To publish later commits, run git push hashtree HEAD again.

4. Check the result

Open the published repository in Iris Git. Use its Code menu to clone it into a fresh directory. Compare git log -1 in both copies to confirm the expected commit is available.

For direct peer-to-peer sharing, run htree start in another terminal. Git operations use the local daemon when it is running. Keep an available copy of your data; publishing a name alone is not a backup.

For scripts and coding agents

Use the same Git commands once the helper is installed. Configure a deliberate signing identity for writes, keep each pusher’s keys separate, and verify the remote and visibility before publishing. No separate Iris Git API is needed for clone, fetch, or push.

Private or link-visible repositories?

Choose visibility before the first push. The helper documentation covers #private and #link-visible, including the extra key setup for secret links. Anyone with a link-visible repository’s secret link can read it.

Read how it works → · Compare with GitHub →