Skip to content
Historical revision — this record as it stood on 1 July 2026, not the current version. View the current record →

How to authenticate binary downloads

The PointSav private distribution endpoint at software.pointsav.com issues Ed25519-signed binary releases. Every download is verified against the publisher's public key before the binary executes. This guide covers requesting a licence token, downloading a release, and verifying the signature.

For the architecture behind the distribution system, see private-git-paid-customer-endpoint and software-distribution-substrate.

Before you begin

You need:

  • A verified account at software.pointsav.com
  • An active licence for the product you are downloading
  • A Linux or macOS host with curl installed

Step 1: Obtain your licence token

Log in to software.pointsav.com and navigate to Licences. Each active licence displays an Ed25519-signed token in the format psv1_<product>_<ulid>.<signature>. Copy the full token string.

The token encodes the product identifier, expiry date, and a cryptographic binding to your account key. The distribution endpoint returns 401 for an expired token and 403 if the token does not cover the requested product.

Step 2: Download the release archive

Pass the licence token as a bearer credential in the download request:

curl -fsSL \
  -H "Authorization: Bearer <your-licence-token>" \
  "https://software.pointsav.com/releases/<product>/<version>/linux-x86_64.tar.gz" \
  -o release.tar.gz

Replace <product> and <version> with the values shown on the Releases page for your licence. Available platforms appear alongside each release.

Step 3: Fetch the detached signature

Each release archive has an accompanying .sig file signed with the publisher's Ed25519 private key:

curl -fsSL \
  -H "Authorization: Bearer <your-licence-token>" \
  "https://software.pointsav.com/releases/<product>/<version>/linux-x86_64.tar.gz.sig" \
  -o release.tar.gz.sig

Step 4: Import the publisher's public key

The signing key is pinned at a well-known path on the distribution endpoint:

curl -fsSL \
  "https://software.pointsav.com/.well-known/pointsav-signing-key.pub" \
  -o pointsav-signing-key.pub

Confirm the key fingerprint matches the value listed in the release notes for the version you are downloading before proceeding to verification.

Step 5: Verify the Ed25519 signature

Create an allowed-signers file and run ssh-keygen -Y verify:

echo "releases@pointsav.com $(cat pointsav-signing-key.pub)" > allowed_signers

ssh-keygen -Y verify \
  -f allowed_signers \
  -I releases@pointsav.com \
  -n release \
  -s release.tar.gz.sig \
  < release.tar.gz

A successful verification prints: Good "release" signature for releases@pointsav.com

If the command prints Signature verification failed, the archive has been modified in transit or the signature file does not match the archive. Do not proceed — re-download both files and verify again before use.

Step 6: Extract and run the binary

tar -xzf release.tar.gz
chmod +x <product>
./<product> --version

The binary validates its licence token at startup. If the token has expired since the download, the process exits with a message indicating the specific expiry date. Renew the token at software.pointsav.com and restart.

See also

Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. See TRADEMARK.md in this repository for the full trademark notice.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →