Wallet settlement
docs(2j): vocab scrub — services/ + systems/ (9 files EN+ES)
@@ -12,13 +12,13 @@ editor: pointsav-engineering paired_with: service-wallet-settlement.es.md references: - id: 1 text: "Foundry Architecture claim #53 — Service-Wallet Settlement (ratified v0.1.0)" text: "PointSav Architecture claim #53 — Service-Wallet Settlement (ratified v0.1.0)" - id: 2 text: "Foundry Architecture claim #52 — Reverse-Flow Substrate" text: "PointSav Architecture claim #52 — Reverse-Flow Substrate" - id: 3 text: "Foundry Architecture claim #48 — Customer-Owned Graph IP" text: "PointSav Architecture claim #48 — Customer-Owned Graph IP" - id: 4 text: "Foundry Architecture claim #26 — WORM Ledger" text: "PointSav Architecture claim #26 — WORM Ledger" --- `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. @@ -29,11 +29,11 @@ This is the fundamental physics of 2030 hyperscaler infrastructure regarding Ser `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 - **Accounting ledger**: records credits, debits, and fees as signed JSONL entries; denominated in the operator's chosen unit of account; no funds in transit; PointSav holds no float - **Not a payment rail**: The platform does not route money between parties; the buyer's transaction goes directly to the destination address or through the smart contract; the platform fee is an accounting deduction at the time the incoming credit is recorded - **Not a custodial wallet**: The platform 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 platform 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. This architecture keeps the platform 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 @@ -84,7 +84,7 @@ The `platform_fee_amount` is deducted at credit time. The tenant's balance is `n | 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. Non-custodial: platform stores destination addresses (public keys only). The withdrawal transaction is signed by the tenant's wallet, not by the platform. 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. @@ -92,7 +92,7 @@ Circle Paymaster handles gas abstraction — tenants pay gas in USDC; no native 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." Industry reference: direct-payment-to-rights-holder models at scale validate that customers keeping a majority of revenue is a workable commercial structure. The platform's revenue split is an operator configuration; the intended default is "customer keeps majority." ## Audit and Public Anchoring