Skip to content
PointSav Digital Systems

Revision as of · 7bb084e0

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

Service-Wallet Settlement

service-wallet (Ring 2) is the per-tenant internal accounting ledger that records and settles all reverse-flow revenue from the data marketplace and ad exchange.

This is the fundamental physics of 2030 hyperscaler infrastructure regarding Service-Wallet Settlement.1

Structural Accounting Isolation

service-wallet is an accounting ledger, not a payment rail and not a custodial wallet. The distinction matters legally and structurally:

  • Accounting ledger: records credits, debits, and fees as signed JSONL entries; denominated in the operator's chosen unit of account; no funds in transit; Foundry holds no float
  • Not a payment rail: Foundry does not route money between parties; the buyer's transaction goes directly to the destination address or through the smart contract; Foundry's fee is an accounting deduction at the time the incoming credit is recorded
  • Not a custodial wallet: Foundry never holds the tenant's private keys; the tenant's balance in service-wallet is an accounting balance representing amounts owed, not a pool of funds under Foundry's control

This architecture keeps Foundry structurally outside regulated money-transmitter and custodial-wallet territory. Tenants should obtain local legal counsel on their own payment activities; this is directional, not legal advice.

Cryptographic Ledger Records

Every credit, debit, and fee entry is a signed JSONL record:

{
  "schema": "foundry-wallet-entry-v1",
  "entry_id": "<ulid>",
  "tenant_id": "<module_id>",
  "type": "credit | debit | fee_deduction | withdrawal",
  "amount": "<decimal string>",
  "currency": "USDC | USD | CAD | <operator-configured>",
  "chain": "polygon-pos | solana | fiat | null",
  "tx_hash": "<on-chain tx hash if applicable>",
  "source_service": "service-market | service-exchange",
  "platform_fee_pct": "<decimal string>",
  "platform_fee_amount": "<decimal string>",
  "net_tenant_amount": "<decimal string>",
  "signed_at": "<ISO 8601>",
  "ledger_seq": "<monotonic integer>"
}

The platform_fee_amount is deducted at credit time. The tenant's balance is net_tenant_amount accumulated across credits minus debits.

Settlement Flow Execution

1. Revenue event occurs (data purchase or ad impression/win)
2. Incoming credit recorded in service-wallet ledger
   Platform fee deducted at this step (accounting deduction)
3. Tenant's net balance increases
4. Tenant initiates withdrawal (tenant-controlled; not automatic)
   Options:
   (a) Crypto withdrawal → tenant's pre-registered address (EVM or Solana)
   (b) Fiat withdrawal → tenant's bank account (via Stripe Connect or equivalent)
   (c) Tier B credit → balance reinvested as Yo-Yo compute budget
5. Withdrawal event recorded in ledger
   Receipt anchored to Sigstore Rekor
   WORM ledger entry in service-fs closes the accounting cycle

Settlement Payment Rails

Chain Typical fee Role
Polygon PoS approximately $0.002/tx Primary — lowest fees, proven micropayment volume
Solana approximately $0.0005/tx Secondary — fastest settlement, sub-cent fees

Non-custodial: platform stores destination addresses (public keys only). The withdrawal transaction is signed by the tenant's wallet, not by Foundry. Platform cannot move funds without the tenant's signature.

Circle Paymaster handles gas abstraction — tenants pay gas in USDC; no native Polygon/Solana token required for SMB operators.

Fee Deduction Mechanism

The platform fee percentage is an operator configuration at deployment time, applied uniformly across all reverse-flow transactions for that tenant. It is an accounting deduction, not a separate transaction. The specific percentage is an open operator decision.

Industry reference: direct-payment-to-rights-holder models at scale validate that customers keeping a majority of revenue is a workable commercial structure. Foundry's split is an operator configuration; the intended default is "customer keeps majority."

Audit and Public Anchoring

Every withdrawal receipt is anchored to Sigstore Rekor. The anchor record includes: tenant ID, ledger sequence at withdrawal, amount, chain, and transaction hash. This provides a tamper-evident external timestamp suitable for accounting and legal purposes.

The full ledger history is queryable by the tenant at any time. The export format is JSONL — the same format as the ingestion record. Portability is unconditional; the ledger travels with the tenant on exit per the fundamental physics of 2030 hyperscaler infrastructure.2

See also

  1. Foundry Architecture claim #53 — Service-Wallet Settlement (ratified v0.1.0) ↩

  2. Foundry Architecture claim #48 — Customer-Owned Graph IP ↩

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 →