Skip to content
PointSav Digital Systems

Revision as of · 3f1e0da5

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

PointSav Software Distribution Substrate

The PointSav software distribution substrate is a three-component system that handles binary release hosting, storefront and license issuance, and on-chain payment verification. The three components — a release server, a marketplace storefront, and a payment watcher — run as separate services accessible at software.pointsav.com. Each component has a single, bounded responsibility, and together they form a custodian-free distribution path: no customer accounts are required, and a customer can move from payment to binary download in a single session.

The three components

Release server. The release server delivers compiled binaries and enforces Ed25519 license token verification before any download takes place. It also exposes product and version indexes that allow tooling to discover what releases are available, and can redirect requests for the latest version of a product to the appropriate versioned path. The server is stateless: it holds no payment records and no customer data. Its only responsibility is to verify that a token is genuine and authorises the requested product, then stream the file.

Storefront. The storefront presents a product catalog to browsers, verifies incoming Polygon USDC payments by cross-referencing confirmed on-chain transfers with a local flat-file receipt store, and issues Ed25519-signed license tokens once payment is confirmed. The storefront is the vendor-side infrastructure — it runs the business logic of the distribution layer. The software products it sells carry Ed25519 license keys and marketplace listings; they are what the store distributes, not what the store is.

Payment watcher. The payment watcher monitors the Polygon PoS network for inbound USDC transfers to the vendor wallet address, writes a structured receipt for each confirmed payment, and provides key-management utilities: Ed25519 keypair generation, BIP-39 mnemonic seed generation, and per-order hierarchical deterministic (HD) address derivation. Receipts are the authoritative record of purchase; the storefront will not issue a license token without one.

License token format

A license token is an Ed25519 signature over a JSON payload, base64url-encoded. The 64-byte signature is prepended to the payload bytes before encoding, producing a single opaque string. The payload records the product identifier, an expiry date, and a list of entitlements that encode the license tier. The release server holds only the public half of the signing keypair. Verification requires no network call and no shared state — the server decodes the token, verifies the signature, and checks the product and expiry entirely from the token itself.

Payment and license flow

A purchase proceeds through five stages:

  1. The customer visits the storefront, selects a license tier, and sends USDC to the vendor wallet on Polygon PoS — either to the static vendor address or to a per-order derived address for order tracking.
  2. The payment watcher detects the confirmed on-chain transfer and writes a receipt identifying the product and the buyer's transaction hash.
  3. The customer polls the storefront's license endpoint with the transaction hash; the storefront locates the receipt and issues a signed download token.
  4. The customer presents the token to the release server via an HTTP header or query parameter; the release server verifies the token and streams the binary.
  5. On subsequent use, the binary or installer can re-verify its own token against the release server's public key endpoint without contacting the storefront.

License tiers

Two tiers are available. The open-source tier is licensed under Apache 2.0. The commercial tier is licensed under the Functional Source Licence (FSL). Both tiers are one-time purchases; there are no subscriptions. The tier is encoded in the token's entitlements field and in the payment receipt. Current pricing is published at software.pointsav.com.

What this system is not

The substrate handles payments, token issuance, and binary delivery. It does not manage subscriptions — all purchases are perpetual one-time transactions. It does not create customer accounts. It does not restrict access to source code: the GitHub repository is separately public under the Apache 2.0 licence. Customers who purchase the commercial FSL tier receive a license key that unlocks the binary distribution; source-code terms are governed by the respective licence, not by this system.

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 →