Transaction

jM{"protocol":"TSW-IP-Proof","version":"2.0","type":"SystemDocumentationProof","challenge":"1 Cent to 1 BSV to $1Million Proof Of Skill","entry_number":64,"entry_date":"2026-02-15","document_title":"TruthStamp System Documentation - Audit Trail","description":"SYSTEM DOCUMENTATION: 1 Cent to 1 BSV to $1Million Proof Of Skill Challenge\nSYSTEM_DOC_VERSION: 2026-02-15-v3\n\n=== WALLET TRANSITION ===\nEntries 1-49: Recorded on legacy/testnet wallet during early development.\nEntry #50: Wallet Transition Proof (non-financial bridge record).\nEntries 51+: Recorded on new mainnet wallet with HD key derivation.\n\n=== FROZEN BASELINE (Entries 1-49) ===\nCumulative ZAR: R589,352.06\nCumulative USD: $34,456.12\nTotal Miner Fees: 68,570 sats burned\nRemaining Balance: 99,931,430 sats\nLast Legacy Entry: #49\nlastEntryNumber in challenge_stats: 49 (PERMANENTLY FROZEN)\n\n=== CUMULATIVE CALCULATION ===\nNew Cumulative = Baseline + Sum of post-legacy transactions (entries 51+)\nThe 'legacy' section in every stamp references entries 1-49 baseline.\n\n=== ENTRY TYPES ===\n1. Financial Entries: Income, Expense, Refund (affect cumulative totals)\n2. IP Proof: Content documentation (blogs, videos, courses, ebooks)\n3. Activity: Work performed (emails, social posts, meetings)\nChallenge Entries = 49 legacy + highest entry number above 49\n\n=== KNOWN ON-CHAIN CORRECTIONS ===\n\n1. Entry #51 Cumulative Discrepancy (2026-02-11):\n On-chain cumulative shows baseline values repeated instead of baseline + #51 net.\n Cause: Bug using stored cumulative instead of dynamic calculation.\n Impact: Metadata only - actual financial record is correct.\n\n2. Blockchain Stamps Duplicate Entry Numbers (2026-02-13):\n Three stamps got entry #51, one got #52.\n Cause: getNextEntryNumber() only checked transactions table.\n Fix: Now checks both transactions AND blockchain_stamps tables.\n\n3. Entries #51-53 TEXT/JSON Discrepancy (2026-02-13):\n TEXT shows 'Entry #50' but JSON correctly shows #51, #52, #53.\n Cause: Client-side text used challengeStats.lastEntryNumber (49) + 1.\n Fix: Both TEXT and JSON now use server-side getNextEntryNumber() API.\n\n4. lastEntryNumber Updated Incorrectly (2026-02-11):\n Field was being incremented from 49 during stamping.\n Fix: lastEntryNumber now permanently stays at 49.\n\n5. Challenge Entries Count Inflated (2026-02-15):\n Dashboard showed 65 instead of 60 entries.\n Cause: Counting all blockchain stamp rows instead of unique entry numbers.\n Fix: Now uses highest entry number across both tables.\n\n=== IMMUTABILITY RULES ===\n- Never re-stamp existing on-chain entries\n- Never reset/delete stamped transaction data\n- Corrections create NEW entries referencing original TXID\n- Format changes only affect future entries\n- Baseline values are permanently frozen\n\nThis document serves as permanent on-chain audit documentation.","creator":"Dr Hannes Dreyer","timestamp_utc":"2026-02-15T09:50:43.451Z","--- LEGACY (Entries 1-49) ---":{"lastEntry":49,"totalMinerFeesSats":87379},"--- NEW SYSTEM (Entries 50+) ---":"Transactions and values start from Entry #50","minerFee":{"thisTxSats":1692,"estimatedBytes":3134,"totalBurnedAfterSats":89071}}