From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Fri, 28 Aug 2026 14:26:23 -0700 Received: from mail-oa1-f55.google.com ([209.85.160.55]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1x045f-0007Rx-6M for bitcoindev@gnusha.org; Fri, 28 Aug 2026 14:26:23 -0700 Received: by mail-oa1-f55.google.com with SMTP id 586e51a60fabf-455cf15f8b5sf2732596fac.0 for ; Fri, 28 Aug 2026 14:26:22 -0700 (PDT) ARC-Seal: i=3; a=rsa-sha256; t=1787952377; cv=pass; d=google.com; s=arc-20260327; b=KYA6kp5DKkDp8fFUjtCbkq3Kb3NzOaiSSei+uvWOU+bg+7HoNuT9P9/+JhRway0sFT RdrRVRxs3QB5rWG45QFqoMpNuwNUWkSLwGNZzuR44A5LtBRA8rYNg9dNZT/qS4MvO04x 3zGR3CINh3fUfxsUZmpnGJbNHXr9sK0Tz67ANS6mY4068Is3RI8RT9yVyjMuglQWFmFM z/U4lRMso9p2OaLhaxMiHTuRS/YzPDNvfT8geHL5QWzAj+rVqMl3bqHkSxmNPIbQjCG6 pUC09Sql+uFX4vwXGUmhiP6o6h/C6ojqVwz/lCXmCnAqEszswIvKPyqy2vfYx0gnZmP4 /iHg== ARC-Message-Signature: i=3; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:content-transfer-encoding:cc:to :subject:message-id:date:from:in-reply-to:references:mime-version :sender:dkim-signature:dkim-signature; bh=7XGiaC8awreVSe8NpSIR/ksKW5i0ZBt/2prme+Siutc=; fh=uLJNoTsvny+/2XTK0StwYrgqUWjOg3bBwdYe8OiCGjA=; b=Qge/RgvT1NrIrIR91vPqT1/iAFjU92B136nKYK3a5wiD7Oq3hq1q4jTDTnGibHlXEY 25fvhVadOaF8ccNLC8qgwllZ9NNiTZjdDE0sczl5l8TaKR/UYuBVyyo4uM1Ch2GH/PID VrvPhR5mR1AI+Zq7C8Bzm2GR5SWg9GweUj48U4gBYOog16Awe7z6jPfSGjeKc2HjRbIB /+hy/HVuZNkK0cdOByctxlY6T/llgF98ev1cok+i2BBzSyV+/HQ5OApEk/8v3FMxFZ+l vdaQYLEl9J42qChCbTZQ3UZvsUkE6YHbv75BjMqESFqg2BmgL6ixUto0jfOwgZ95lrP1 9RwA==; darn=gnusha.org ARC-Authentication-Results: i=3; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20251104 header.b=Sy2LLB1n; arc=pass (i=1); spf=pass (google.com: domain of xiangliao@gmail.com designates 2607:f8b0:4864:20::32c as permitted sender) smtp.mailfrom=xiangliao@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1787952377; x=1788557177; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:content-transfer-encoding:content-type:cc:to :subject:message-id:date:from:in-reply-to:references:mime-version :sender:from:to:cc:subject:date:message-id:reply-to:content-type; bh=7XGiaC8awreVSe8NpSIR/ksKW5i0ZBt/2prme+Siutc=; b=WDFmiSxGrS63BMfESTRoUH0JxNFMVNmL93LFUTaCzfQSgFphflAENUqqQMnZiMd2ah 0G7Us51hsO8a3uNngntJ2Z8dvxiQk0kyyc0RA/tSqpT02f3YEExveAOKWM0V3LxsYMPa MLl/lACqTEB1xerXZfCrfFqXo0llDDEyJB+d8RPGVE6eXexvRpeXTsMgP5Ky8BJonGwq 5/6u2uakLG7BEsztXo4JNSLmOApqreCqrj+CELCLCkpd2r0fmWyUjrZckD+hHJLJZDle I3cw1VbSqIKkJYBHC+FBj1jiGxY3Va6ttOfHcViwPjxOUQSd1RHsIsYKjOxvz7M+uX+9 JpBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1787952377; x=1788557177; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:content-transfer-encoding:content-type:cc:to :subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to:content-type; bh=7XGiaC8awreVSe8NpSIR/ksKW5i0ZBt/2prme+Siutc=; b=Tn08ZAcBIvSVmpiToc47BFHheU0vMRjVMbHZrxipsm5TfD2LIaWFCk9PbQRCNkScK+ gwFv9TH5cVdm+o0qA93hIS1r7inLeHR8R87t9pyELzyBQArIHyPzW84cBihIUXrZkvmn SIOkxE7mgwfslnazl9QVyTcPeHKVYSuZOg7RT+XW28PEZJowxaa65xfAvgH0n7hjtWTT qyRuArwUQN43E9BNZUEoFp7qpAQXvrxsX0mLWKZhYpvpJtCyu5Bimw7ZMhu5XIE3qMWt I45p2IV9kpBRv8PPN9vEfQOaVWEIZAOkbf0DFjEQvKMdmeZ0wL8yBUkGuCr6M9hbvo7a XC2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1787952377; x=1788557177; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:content-transfer-encoding:content-type:cc:to :subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-gg:x-beenthere:x-gm-message-state:sender:from:to:cc:subject :date:message-id:reply-to:content-type; bh=7XGiaC8awreVSe8NpSIR/ksKW5i0ZBt/2prme+Siutc=; b=F7B0iwffMPSioNtKjXyocZjLPtxt0QMykTuCyvKfEn0gQYR+LOJPBig3CKQ6Q9aanQ Qrq1Mb29YPTQl6oJZpf5wVHeSTIpOIZkWxJjxWXkfRb78Ki/T2B7U14QIStNn6oU6vNH 2sRWvUgboIeF+E/KReenap9I5LCZqxueAPX6eYteAfUI+dIfBR+MmQmwiCbD/0zWEnB/ CY0cs6hmo7DJQKlGa6gvGAj4t9c3N/5nAkqyeb3Vwovc+Bu7OriBusZtZBCWiPvWVPRC sJvhNuY76yckyzfNuh39MR0QtSNu3VMrN4Y1LiUpc6KLf0o+4kbZdbT6FgC45EVa6HsP Ow9Q== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=3; AHgh+RpkA/N2nXhaPub7QDqPNud3/ThQ0HEChEvFW4YDknZHtVllXoMjeHRZWEbbb3sNngx1bVpBjiXIn3Tz@gnusha.org X-Gm-Message-State: AFuF++l3jtuqYQrZUeCCQ7UQW4kYCAF/iRms/PJt6rZBqHowovai/D1u B3PO5MW5OpP21ZMg+DJ1s5GsvxY2CWTjh0BzL/VkfDoH88yABHIyN53Z X-Received: by 2002:a05:6870:b2c7:b0:45e:d645:e03d with SMTP id 586e51a60fabf-466e887ddccmr15201252fac.11.1787952377001; Fri, 28 Aug 2026 14:26:17 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="ATskLdfgxMJI8rZc1HQlZwfA30seJ4jxehRE+NXYMokCThg6SQ==" Received: by 2002:a05:6871:a80d:10b0:45e:ecb5:9948 with SMTP id 586e51a60fabf-465c7fdafc8ls1378824fac.1.-pod-prod-00-us-canary; Fri, 28 Aug 2026 14:26:11 -0700 (PDT) X-Received: by 2002:a05:6808:6703:b0:4b3:3e1:499b with SMTP id 5614622812f47-4b3af003fbdmr3676058b6e.6.1787952371843; Fri, 28 Aug 2026 14:26:11 -0700 (PDT) Received: by 2002:a05:6808:2d12:b0:495:e116:a399 with SMTP id 5614622812f47-4b3b4d820famsb6e; Fri, 28 Aug 2026 14:16:32 -0700 (PDT) X-Received: by 2002:a05:6a00:178d:b0:84e:c851:a058 with SMTP id d2e1a72fcca58-854c8334f46mr19086422b3a.10.1787951791283; Fri, 28 Aug 2026 14:16:31 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1787951791; cv=pass; d=google.com; s=arc-20260327; b=VajE5L8q7WQQHoIRnkhgH1t0/M6CwiW+N/pkBp7NDfUWERl+m9q5XA0p9iX8SPM5pW dfNbRIc6XgHnEf6E4HEry3oPLLX2lTBcpqTYgbdzNHOvqjK797rYeTxk2Lk6QGVqwtbc wn7BcsSMe9fiuPAlPiZkIKO6rWAp+9SHePNZy4v6W7DaGpE++XmcuIv91gcvIdFiFd5a 1BjosOi94R5JVAKctE5ZZSmlcr/MV0g5xyfNnR3kp4pWCIbHw6YG3Hk2lbQzyut7JDzM mn2pSn3MnCOX6D2jjRzKr2LP2k/xMYEOt5VL8Xa81F4NAFS9iPohClRzlxctNnGHscjb rkBQ== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=woC4IYuaGWNqNRW+liEAaS9NE0J6JKGagywVJ7I+5lA=; fh=IEPLWoyJKcVvSmoA1ytbY29vMgb09bRNcxsIV5rxU6U=; b=HsGl9tuo2CzMpHJnkyFHj7Ap1lQJwMogAeW64TTQQWf1uPUhLgJinvwJ5KuS4XPc5z RKgBTnnZBMPiwC9BigP8Mv9LF49WMSeYw4CEbK4W228dHQmOaXTD+3+T0Be9eREvRQxE XkbF6u3qxnuw0r17KJdsqNFAElpKEurfN31OYM3co8Ao8DPeZzElDxt9Rp8c3zaYNjcC 4ynDJnjZNaOBtoz6mmiGyoyFV/N4EiYYBm4ar3HMMAwfDiHqhftj1nIsUbLdbit93+dY oumqy2/z9yYoPmIBEtgXsF+P2UJdLE6pfBry3JcquwAYenn7cOMR02KKntQS0XywUQPP Yinw==; dara=google.com ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20251104 header.b=Sy2LLB1n; arc=pass (i=1); spf=pass (google.com: domain of xiangliao@gmail.com designates 2607:f8b0:4864:20::32c as permitted sender) smtp.mailfrom=xiangliao@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com. [2607:f8b0:4864:20::32c]) by gmr-mx.google.com with ESMTPS id d2e1a72fcca58-856a3d6ea0asi77314b3a.8.2026.08.28.14.16.31 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 28 Aug 2026 14:16:31 -0700 (PDT) Received-SPF: pass (google.com: domain of xiangliao@gmail.com designates 2607:f8b0:4864:20::32c as permitted sender) client-ip=2607:f8b0:4864:20::32c; Received: by mail-ot1-x32c.google.com with SMTP id 46e09a7af769-7ee4f241f42so2451373a34.1 for ; Fri, 28 Aug 2026 14:16:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1787951790; cv=none; d=google.com; s=arc-20260327; b=mTO8XKqC75SL1J9YYCQDVV/OLI0/iBIcBIBb26in0yelRY+UmLxDE05fK25/GzVfjr LkImQnqcjGZkLzxIIxFwqJqV4eZnkf8ChtQvBAzxX/2y2fOd6vEQhLTnxyTCB9DPP64i rwnw3h84nV0kpaobCgZl7gz8aV7SnLdnACpV+qrAUEZMEy4ArEA2lexDNvQJPJHvmIlu yZvV0W5SDIuXVSvew62ScP6EqX6YpOW/Ig14KJKvud3Vle3u3rx5WZv32G6wvQos+CK0 u9IdWRPwtD5rkb2ThrVihvMnXpJJMHL0v6H4UXWIYLSjFqzgFvWrkC9EUa9KSe64Nnkb SPNQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=woC4IYuaGWNqNRW+liEAaS9NE0J6JKGagywVJ7I+5lA=; fh=IEPLWoyJKcVvSmoA1ytbY29vMgb09bRNcxsIV5rxU6U=; b=TOxafeRVd0qpKR0GZwqQoV4HUfA1vrbrxSDlc8Kz64qjkY3zNsq5sD8Jg2UWHJcBsh ndvn985GcSLP9KFf+PN53qbBy+DNdnsrkLT/losb75is34F+bi5lGQFm9KWZH85akBdg IKbn5pYEqqFnpRVae0O0cSKwEAzGIzTCfOeKReg69Fbc3SFOr4XNiVPZZJZ+jG/rtnhd 3AkNdkVryDiemH6YKtc5mQKb489OZdJMKmZnkcQO+3nn8l0RKHU1ZTOMwRsR3ARSN+2E BkmgkggGqmtQkxqfbnwBABGECYTTUk7AC/R3ZERfqmEbwLZDYP+49Qyaeg6jYP/3SSGu u9Lg==; dara=google.com ARC-Authentication-Results: i=1; mx.google.com; arc=none X-Gm-Gg: AR+sD10rrFSMXYspLv0uVTRHkNu0ygfdbDbB7nFTMG7cuQnfPGjayPVoDrnNtS7JYGN 0qrlzexqHNTYJrVETBNRC6ONdImbo4mwhQ0E+2S495jcrQ6WANfTBI3OddTvr54GEfaYYGZGn64 Drm8L9t90iqN+z+lotN8GUfw/zNr75bWZbkQpAeRe13MxTTfOSslBUbQNuGbd91otzVfdhLTrT/ 0dsRcc1o/c7EwTL6dTeeI9nd/pyQO0+TUXpU/3l0FinNiAD9AgmAVPmIBikK6Ox/q3j7psadhSc csi127i8bDnArYy/L5rD1O/ClaT1DpVqfvmCBPbGIpviEa2rdDpGZ9gzZGtedcHidPURLpu/M9e He4whyFGD6P0= X-Received: by 2002:a05:6820:4c14:b0:6ae:4959:e1ba with SMTP id 006d021491bc7-6b1b00bdbbcmr13466700eaf.10.1787951790333; Fri, 28 Aug 2026 14:16:30 -0700 (PDT) MIME-Version: 1.0 References: <4bbb1017-8080-4916-8f85-082d2ebf5eacn@googlegroups.com> In-Reply-To: From: Jack Liao Date: Sat, 29 Aug 2026 05:16:18 +0800 X-Gm-Features: AcwNN1UyeH5CNUecsLIIp_bja6lncj3C4ofC4uB6JOWF_gN9ETcXl6IbPKnEp1w Message-ID: Subject: =?UTF-8?Q?Re=3A_=5Bbitcoindev=5D_=5Bbitcoin=2Ddev=5D_Draft_BIP_for_discuss?= =?UTF-8?Q?ion=3A_Time=2DShifted_Proof_of_Work_=28TSPOW=29_=E2=80=94_an_informational?= =?UTF-8?Q?_consensus=2Ddesign_proposal?= To: Saint Wenhao Cc: Bitcoin Development Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Original-Sender: xiangliao@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20251104 header.b=Sy2LLB1n; arc=pass (i=1); spf=pass (google.com: domain of xiangliao@gmail.com designates 2607:f8b0:4864:20::32c as permitted sender) smtp.mailfrom=xiangliao@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) Subject: Re: [bitcoin-dev] Draft BIP for discussion: Time-Shifted Proof of = Work Subject: Re: [bitcoin-dev] Draft BIP for discussion: Time-Shifted Proof of = Work (TSPOW) =E2=80=94 an informational consensus-design proposal Hi, I appreciate the review and the decision on the bips repository. Rather tha= n re-litigating scope, I want to put the technical case on record, because I believe TSPOW addresses flaws in the existing single-stage PoW model that h= ave been known for years but never fixed by a design that stays on one chain. T= here are three structural improvements worth a serious look. 1. BLOCK-TIME STABILITY =E2=80=94 fixing the variance. Bitcoin binds "find a hash below target" and "author the block" into a si= ngle event. The block interval is a single exponential arrival: mean =3D 1/lam= bda, variance =3D 1/lambda^2, i.e. a unit coefficient of variation. Real PoW c= hains inherit exactly that variance =E2=80=94 blocks arrive in bursts and on oc= casion with long gaps, which is the source of wide confirmation-latency variance and = of the persistent "lucky vs unlucky" mining outcomes. TSPOW separates warrant issuance from block authorship and lets block production wait for k *accumulated* warrants. The block interval then fol= lows a Gamma(k, lambda) distribution whose variance is divided by k (Section 3= .1 of the whitepaper; cross-checked in Rust, C++, and Python simulations in the repo). With k =3D sqrt(S), even a modest pool gives a variance reduction = of an order of magnitude or more. This is an improvement to the chain's own scheduling behaviour =E2=80=94 no second chain, no peg, no bridge. 2. REMOVING THE SELFISH-MINING SURFACE. In single-stage PoW a valid proof can be withheld and revealed later to f= orce a reorganization. Selfish mining uses exactly this: an adversary with < 5= 0% hash power can amplify its share of produced blocks by withholding, lower= ing the effective security threshold of the network. This is a known, measure= d weakness of the current model. TSPOW makes withholding economically self-defeating: warrants expire (L) = and rewards are deferred, so holding a proof past its validity window yields nothing. And because the elected producer is chosen by argmin H(h, R, PrevBlockHash) over an immutable chained pool, a withheld = proof can no longer be inserted to rewrite the pool state. The design removes t= he amplification vector rather than patching around it. 3. DECENTRALIZING WHO PRODUCES BLOCKS. In single-stage PoW, the fastest hash wins, which structurally rewards th= e largest pools and concentrates eventual authorship in a few entities. TSP= OW decouples "who did the work" from "who writes the block": - warrants (who earned the subsidy) are created by proof of work; - authorship (who writes the block and earns fees) is elected by argmin o= ver the mature pool, seeded by an external randomness beacon R with the pre= vious block hash as the chain-derived fallback. The producer-staking, challenge-window, and deferred-fee mechanics are ai= med directly at incentive collusion among block producers, reducing the centralizing pull of the largest mining entities without creating a separate network. WHY I FILE THIS AS INFORMATIONAL The Informational label reflects a maturity posture =E2=80=94 this is a research proposal with a formalized spec and security analysis, not a recommendation to activate on Bitcoin today. I understand the bips repository's scope policy is targeted = at adoption proposals, and I accept that as a policy decision. The technical point I want on the public record is simply that TSPOW is an in-chain, consensus-authoring modification with three concrete improvements over the existing PoW model: Gamma-scheduled, low-variance block times; elimination of the withholding / selfish-mining amplification; and a more decentralizing separation of work = from authorship. Full spec, whitepaper, security analysis, and cross-checked simulations: https://github.com/corepool/timeshiftpow Thanks for reading. On Fri, Aug 28, 2026 at 5:51=E2=80=AFPM Saint Wenhao wrote: > > > Hard fork. > > I guess it could be turned into a no-fork, if you would just create a min= ing pool, working with your rules. > > > changes the block header > > If it is compatible, then it doesn't matter. For example: locally, each n= ode could extract the difficulty out of the block header, and have a chain = of difficulty periods, stored separately, and copy-pasted into the actual h= eader, when needed. Then, every two weeks, instead of having "80 * 2016 byt= es", it could be "4 + (76 * 2016) bytes", when it comes to the way it is st= ored locally. Will it change the header? Sure. Will it be backward-compatib= le? Of course. > > > replaces direct block authorship with pool-based selection > > Existing mining pools already did de-facto that. Miners are paid per shar= es, there are not that many solo miners anymore. > > > and reallocates rewards > > Again, in practice, miners create blocks, sending coins to the pool opera= tor, and later, they are splitted, based on sent shares. > > czw., 27 sie 2026 o 17:37 Jack Liao napisa=C5=82(a)= : >> >> Hi all, >> >> I am sharing a draft BIP for feedback before submitting it to the bips >> repository. It is classified as Informational: it documents a consensus-= design >> pattern and its security analysis. It does NOT recommend activating a ha= rd fork >> on the Bitcoin main chain. >> >> WHAT THE PROPOSAL IS >> >> Time-Shifted Proof of Work (TSPOW) separates the three roles Bitcoin bin= ds into >> a single event =E2=80=94 finding a hash below target, earning the block = reward, and >> authoring the block =E2=80=94 into two stages: >> >> 1) Stage 1 (warrant issuance): miners produce a valid initial-hash warra= nt H_n >> (H(header, nonce) < D1), which carries the right to the new-coin rewa= rd. >> Rewards are deferred and warrants expire. >> >> 2) Stage 2 (selection): once k warrants accumulate (an adaptive Gamma ba= tch), >> the protocol elects a block producer from the candidate pool via >> argmin H(h, R, PrevBlockHash), where R is an external-beacon output (= with the >> previous block hash as the chain-derived fallback seed). >> >> Two claimed properties, both backed by the whitepaper and by cross-check= ed >> simulation (Rust / C++ / Python; see the repository): >> >> - Block-time stability: the block interval becomes a Gamma(k, lambda) su= m >> instead of a single exponential arrival, dividing block-time variance = by 1/k. >> - Withholding economics: warrant expiry plus deferred reward make privat= ely >> mining / withholding a warrant strictly suboptimal (expected payoff st= rictly >> decreasing in delay). >> >> WHAT THE PROPOSAL HONESTLY DOES NOT CHANGE >> >> - A >50% adversary still dominates warrant generation and thus pool >> composition; 51%-attack security is unchanged natively. >> - Without the external beacon, the long-run double-spend probability rem= ains >> (q/p)^z, identical to traditional PoW. >> >> KNOWN COSTS / RISKS (TO BE TRANSPARENT) >> >> - External beacon =3D a new trust assumption. The election only fully el= iminates >> private mining when an honest beacon is present; a compromised or cens= ored >> beacon degenerates to the weaker chain-derived seed. >> - Hard fork. Adopting TSPOW changes the block header, replaces direct bl= ock >> authorship with pool-based selection, and reallocates rewards. This is= by >> construction a severe backward-incompatible change =E2=80=94 another r= eason this is an >> informational document, not an activation proposal. >> - Pool-flooding within a window is mitigated (chained FIFO, per-owner ca= ps) but >> not eliminated; residual risk should be stress-tested. >> >> MATERIALS >> >> - BIP draft: bip-corepool-timeshiftpow (source in the repository below) >> - Reference implementations, verification scripts, and numerical checks: >> https://github.com/corepool/timeshiftpow >> - Whitepapers (CN + EN) and formal security analysis in the same reposit= ory. >> >> I would welcome scrutiny of the Gamma block-time argument, the >> withholding-economics model, and the beacon trust model in particular, b= oth on >> this list and in the BIP's security-considerations section. >> >> Comments-Summary: No comments yet. >> >> Thanks, >> corepool >> >> -- >> You received this message because you are subscribed to the Google Group= s "Bitcoin Development Mailing List" group. >> To unsubscribe from this group and stop receiving emails from it, send a= n email to bitcoindev+unsubscribe@googlegroups.com. >> To view this discussion visit https://groups.google.com/d/msgid/bitcoind= ev/4bbb1017-8080-4916-8f85-082d2ebf5eacn%40googlegroups.com. --=20 BR. Jack. --=20 You received this message because you are subscribed to the Google Groups "= Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= CAB8jPP4Pw%2BvuDvi4ruznvOQGUMMTq9gdm7EdJn4Ms-ZGUGQArw%40mail.gmail.com.