Skip to content

PointSav Documentation

The engineering library for the PointSav platform — operating systems and services for regulated businesses that own their data, their AI, and their record-keeping outright. Where the monorepo holds the code, this wiki holds the reasoning: architecture, services, security, and the governance commitments that bind future development.

PointSav Digital Systems

Revision as of · f99f9774

Historical revision — this record as it stood on 6 August 2026, not the current version. View the current record →

Authenticate binary downloads

Prerequisites

  • The transaction hash of your Polygon USDC payment, if you placed a paid order
  • A browser, or curl configured to follow redirects
  • Nothing else — no local verification tool, key file, or signature utility is needed

Purpose

Obtain a release from software.pointsav.com through the signed download path, and understand which part of that path actually authenticates the file — about two minutes once your payment has confirmed on-chain.

Note: every product currently listed is priced at $0 for the BETA period and requires no license or payment today. The order-and-token path below is working code and is what a paid order will use, but at present you can download any current release without going through a paid order at all. Steps 1 and 2 apply only if you have placed one.

Procedure

  1. Open your order page at https://software.pointsav.com/order/<tx_hash>, where <tx_hash> is your payment transaction hash. The order reads as pending until tool-wallet confirms the payment on-chain.

  2. Reload the page once confirmation lands. A receipt code appears — a deterministic identifier derived from the transaction. Keep it for your records; no download step asks for it, and it is not a download credential.

  3. Follow the download link at https://software.pointsav.com/order/<tx_hash>/download. That request mints a fresh Ed25519-signed token and redirects straight to the release download with the token already attached as a URL parameter. There is no separate token to copy.

  4. Let the download run to completion. The release service verifies the token's Ed25519 signature server-side before it streams a single byte, so there is no client-side verification command to run afterward.

  5. Optional: address a release directly rather than through an order page, using the release URL pattern:

    https://software.pointsav.com/releases/<product>/<version>/<platform>
https://software.pointsav.com/releases/<product>/latest/<platform>

    The latest form redirects to the resolved current version.

Expected outcome

You hold the release file, and the fact that you hold it is the proof that its download token verified: a request carrying a missing, malformed, or badly-signed token does not produce a release file. The token's wire format is base64url(signature || payload_json), unpadded, and it is checked with Ed25519 on the server before the response body begins.

Verification

Confirm you received a release file rather than an error page — check the file's size and type against what the release page advertised. The signature check itself has already happened at that point; it is not a step you repeat locally.

To inspect the platform's public signing key independently, the release service publishes it at /verify-key.pub as a plain hex string: 32 raw bytes, 64 hex characters.

Warning: that path is not currently reachable through the public software.pointsav.com domain. The underlying service serves it correctly, but a routing gap in front of the public domain means a request to it there does not reach the handler. Treat independent key retrieval as unavailable over the public domain until that routing is fixed.

Rollback

Downloading changes nothing on the server and nothing on your host outside the file you fetched, so there is nothing to reverse. Delete the file and start again from step 3 if a download is incomplete or corrupted.

Do not reuse a saved download URL from an earlier session. The token is minted fresh on each visit to the order page's download link, so a stale link is repaired by returning to the order page rather than by editing the URL.

Next steps

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is currently a trade name of Woodfine Capital Projects Inc. ("Woodfine"), planned to become a wholly-owned Woodfine subsidiary upon incorporation. 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. The full trademark notice appears in the footer of every page on this site.

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 →