From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 21 Apr 2026 11:31:17 -0700 Received: from mail-oa1-f59.google.com ([209.85.160.59]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1wFFsS-0004Cf-9k for bitcoindev@gnusha.org; Tue, 21 Apr 2026 11:31:17 -0700 Received: by mail-oa1-f59.google.com with SMTP id 586e51a60fabf-42c125431f7sf4250119fac.3 for ; Tue, 21 Apr 2026 11:31:16 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1776796270; cv=pass; d=google.com; s=arc-20240605; b=ivLrfOdHFv41LMhcBohXngL65QBMKD6EbsNnxiowkx5bHGvezwC4FK+TLvhcVun+JX 04GH35nSDUjxtomVnmVy2vXlGVE7qS8oYymo0kuVimPzvm8678BtLlJ0maRvIbgUS+qF 4o033HVW6WNjzkoh3Pz0ZG4LVqfHr2VHuiDonIO76FWsr58KeNdVUE5EuHOK55tvglkE 0yfy4GUoe1/vOz019kL4GPKw7KuN0Jfmz9nEKIXC9ZnNToQtKYV4qSkkKme5Z9DbaCw+ TwfhLqaqAkPq8FanMTdLcmJi3o95w9LjJjrxrqorH3qD6vUF+mTqrXpMHuIK47OXKPEU KGaA== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to:content-transfer-encoding :mime-version:feedback-id:message-id:subject:from:to:date :dkim-signature; bh=fKY5TRXyUHuQIX81jDfxQWVeYONLzKIlYgJ1kLkZUL4=; fh=poZ3PIYorJGI8Xi9stJAFuPV5ewOhsuY+LYjpa9+xkI=; b=j/KZPpen1IEKa3JfMQovKMRzBYrc+0BqT2BjaEX0EI5FXAaVrFLqkQaRVrzZ3zEPkh 8fgW1fqh6f6mAmSwnXYg+UpIkC8BKlqqsBYWUJcoCVXJPfVFrATslJ5ADdwJ+D0M4IKN 9T/paMw1Elw4fZ13vjMjxLqxeR8Fo+bEbetLle5cy8Pno0RhcwtWF90XHacqyJ1W7/en cVZoKPZuZ9SxQnCldbLOvZTaoC7k3EG7fwsD/5ml+Hcn9BvB3EmD6JD+zRA/hqT20aHz f85zir8IyTn+jhpBBejj1wRejdxzq5uWvGy+KjmvNWd+qmI43GzKeGMpYBda1KSFqXEC LuKw==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@achow101.com header.s=protonmail header.b=dKEkcoxc; spf=pass (google.com: domain of lists@achow101.com designates 109.224.244.118 as permitted sender) smtp.mailfrom=lists@achow101.com; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=achow101.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1776796270; x=1777401070; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to :x-original-authentication-results:x-original-sender :content-transfer-encoding:mime-version:feedback-id:message-id :subject:from:to:date:from:to:cc:subject:date:message-id:reply-to; bh=fKY5TRXyUHuQIX81jDfxQWVeYONLzKIlYgJ1kLkZUL4=; b=xrSbc/1L8/c7BcHb6gPbas+DFdbH8qA7Zf8Dak149MwDnrpZjEj0vNnORk5//U+4CA gxGAXKUoBiNhmxMhy+8deME2F2fhBHo/pOzp6frgwD6o4aCubWyJfAALIGHyLvdBeBuf 3uHV9IViXyUomGQj55TfLSGKzGjyRoefKWytB1xWoQTQ0tRjq7EmJfe4a+lc6rTrfgU0 z+VujnZtCrOwwF5YnYzMnx2BX3U+5d2XvGxsleQRHln+2ENx56B1d0BBb3YkcA4xayZe FTvJ4dadmV59vyMJ52b2GpcyZzU3NJ/J+pUrBoKDi3yVSvJYA6NbB1PIkytpi3a+DfEP in/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776796270; x=1777401070; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to :x-original-authentication-results:x-original-sender :content-transfer-encoding:mime-version:feedback-id:message-id :subject:from:to:date:x-beenthere:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=fKY5TRXyUHuQIX81jDfxQWVeYONLzKIlYgJ1kLkZUL4=; b=NVWUob/rRe8Q+VskQJL7PI4QOWe30DB4s6LoPT1pMzoMknfS3jAMikO4NBut6OuHOG m25cos+Nhdu1Mo8PsXTdns+uc3m73Sc4ARWUGPWRWA5qm7a8UPw12ggaHyUfpWr5rLkQ Zq+dcfiyoTr6OYB5apdxmpKnPDLX7mRpMMuWrlzHCgpaXlN2pXBdeBBlmVSt6f/pDDQs LR2EZvqv6aZ6c4jICIk/VuZEY8p5wt5V2SC9fYkiuNrH9tRqNA+b28HsY9REqScQqDZp BJofGw3vu9JJnGQEASkRKtBvMKIvHw3nCL4a8ItqOgkFgkg5fgP4fOMVxy8bgyU6kdd0 4J0w== X-Forwarded-Encrypted: i=2; AFNElJ9+8oy1ntJrliwANn/17Sv7RBhue6cAus9tEukb/8x///HBoxs3rxE/svTnQdHH9v+BkPXmjVuhQr8j@gnusha.org X-Gm-Message-State: AOJu0Yy/hW+QArJcs1G89qcgxeVnIEt6KHwAuzP1x9N5qKDGIwMNujVj +9jnqO1h/pvvHor3YUHEFH86QEE0Dd46SmJtWeyAVKNB2aamu1xFT/kz X-Received: by 2002:a05:6871:8314:b0:423:6559:ae5d with SMTP id 586e51a60fabf-42adecf73c9mr10394767fac.20.1776796270024; Tue, 21 Apr 2026 11:31:10 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="AYAyTiKRe3gBXLObFGoSnsrCz3fz5uV9LIISe3tPiCNnw/nnJw==" Received: by 2002:a05:6871:8416:b0:42f:af07:ba3 with SMTP id 586e51a60fabf-42faf075f90ls174600fac.2.-pod-prod-07-us; Tue, 21 Apr 2026 11:31:03 -0700 (PDT) X-Received: by 2002:a05:6808:e695:b0:479:fbe5:3a4a with SMTP id 5614622812f47-479fbe54a14mr542739b6e.46.1776796263705; Tue, 21 Apr 2026 11:31:03 -0700 (PDT) Received: by 2002:a05:620a:a389:b0:8d0:26c1:4847 with SMTP id af79cd13be357-8e7927564b3ms85a; Tue, 21 Apr 2026 11:18:07 -0700 (PDT) X-Received: by 2002:a05:622a:8c04:b0:50f:bb01:9866 with SMTP id d75a77b69052e-50fbb019c2dmr30114811cf.23.1776795487063; Tue, 21 Apr 2026 11:18:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1776795487; cv=none; d=google.com; s=arc-20240605; b=d7MdpgK9X0HQSfPzJF3mJlQDTEeIFfFs9OAZLoyX1ZmPp5Yei7cKrkD3T7/djjo6ZU NSWPUOOhh491NGrzvPXq0/f63hH3trMbfNkedsJRue1ohfbxLjxOUfO90uaDc7RTCTWp RFPG0JLQPV+JX3dAn8PMqtg7nOd3RcPj60yKuBUuEbwoAaN+WPG7HLxop19u4vnLhE/X Qp1rzuY3H4Z1/Gn3LOsVc6pnS0kqUW5W6dWwMELRQxltijICXKcF7zxregRJimEHg2kp HZ+tX8PFIlCO6MoAhhBtVgkIUM+jtwCSYr6vBWa/QBM3rzISiYa24AsNxjV5su7haDT3 5CbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=content-transfer-encoding:mime-version:feedback-id:message-id :subject:from:to:date:dkim-signature; bh=aPbf3w3NWngJZi/sQdxDcJUac/DuvWt4Uf8Dkl3yFXM=; fh=VcGcg+Zjs9gw1uDcHbxsAILhBAcecnbJzZRdxgKVDIc=; b=ZlhfF3fkgg5uuw8Fk0/OYa0EQ2YcDnW5Sjxi9X4izIxKRLn2FTxFLtaVhElncEzJai uSJKcPC7sOoKanNJi7jQ7+EqI4mXEWOEPQIiINUcvR1/1nlXsCTAgHhFGNGp2owXMJ61 DzWTT62jiHYU2txz5rLZG5LI/bPf0rlLryN3X0F0or41RIZJEeb6c4X4sL3XOPvkVXRc llTIfM+FJJwCDf3EsiyK7sqmIB2sx1v/SFJaTCHvksOi1bz0SrQxHSNQ1uPn1N6SLDXY kSRIGKoBIA0EiU0HMmcDvJr1jXmOfSTiw5otf4+ZThaMTyD8IKu4fx4UpjiJA/3yhBcz Kf5w==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@achow101.com header.s=protonmail header.b=dKEkcoxc; spf=pass (google.com: domain of lists@achow101.com designates 109.224.244.118 as permitted sender) smtp.mailfrom=lists@achow101.com; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=achow101.com Received: from mail-244118.protonmail.ch (mail-244118.protonmail.ch. [109.224.244.118]) by gmr-mx.google.com with ESMTPS id d75a77b69052e-50e39139699si4323451cf.0.2026.04.21.11.18.06 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 21 Apr 2026 11:18:06 -0700 (PDT) Received-SPF: pass (google.com: domain of lists@achow101.com designates 109.224.244.118 as permitted sender) client-ip=109.224.244.118; Date: Tue, 21 Apr 2026 18:17:58 +0000 To: bitcoindev@googlegroups.com From: "'Ava Chow' via Bitcoin Development Mailing List" Subject: [bitcoindev] Bitcoin Core v31.0 Released Message-ID: <27c7294e-a958-4255-b0dc-3ef541811458@achow101.com> Feedback-ID: 53660394:user:proton X-Pm-Message-ID: 1fb1e9df7f78ea3b13bb87218a635f65d93a8e99 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Original-Sender: lists@achow101.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@achow101.com header.s=protonmail header.b=dKEkcoxc; spf=pass (google.com: domain of lists@achow101.com designates 109.224.244.118 as permitted sender) smtp.mailfrom=lists@achow101.com; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=achow101.com X-Original-From: Ava Chow Reply-To: Ava Chow 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: -1.0 (-) Bitcoin Core version 31.0 is now available from: =C2=A0 This release includes new features, various bug fixes and performance improvements, as well as updated translations. Please report bugs using the issue tracker at GitHub: =C2=A0 To receive security and update notifications, please subscribe to: =C2=A0 With the release of this new major version, versions `28.x` and older are at "End of Life" and will no longer receive updates. In accordance with the security policy, we will in two weeks disclose: * Medium and high severity vulnerabilities fixed in `29.0`. There is one=20 of these. * Low severity vulnerabilities fixed in `31.0`. There are none of these. How to Upgrade =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D If you are running an older version, shut it down. Wait until it has=20 completely shut down (which might take a few minutes in some cases), then run the=20 installer (on Windows) or just copy over `/Applications/Bitcoin-Qt` (on macOS) or `bitcoind`/`bitcoin-qt` (on Linux). Upgrading directly from a version of Bitcoin Core that has reached its=20 EOL is possible, but it might take some time if the data directory needs to be migrated. Old wallet versions of Bitcoin Core are generally supported. Compatibility =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Bitcoin Core is supported and tested on the following operating systems or newer: Linux Kernel 3.17, macOS 14, and Windows 10 (version 1903).=20 Bitcoin Core should also work on most other Unix-like systems but is not as=20 frequently tested on them. It is not recommended to use Bitcoin Core on unsupported systems. Notable changes =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The default `-dbcache` value has been increased to 1024 MiB from 450 MiB on systems where at least 4096 MiB of RAM is detected. This improves=20 performance but increases memory usage. On some systems (for example when running in containers), the detected RAM may exceed the memory actually available,=20 which can lead to out-of-memory conditions. To maintain the previous behavior, se= t `-dbcache=3D450`. See [reduce-memory.md](https://github.com/bitcoin/bitcoin/blob/master/doc/reduc= e-memory.md) for further guidance on low-memory systems. (#34692) Mempool ------- The mempool has been reimplemented with a new design ("cluster mempool"), t= o facilitate better decision-making when constructing block templates,=20 evicting transactions, relaying transactions, and validating replacement transaction= s (RBF). Most changes should be transparent to users, but some behavior=20 changes are noted: - The mempool no longer enforces ancestor or descendant size/count limits. Instead, two new default policy limits are introduced governing connected components, or clusters, in the mempool, limiting clusters to 64=20 transactions and up to 101 kB in virtual size.=C2=A0 Transactions are considered to be i= n=20 the same cluster if they are connected to each other via any combination of=20 parent/child relationships in the mempool. These limits can be overridden using=20 command-line arguments; see the extended help (`-help-debug`) for more information. - Within the mempool, transactions are ordered based on the feerate at whic= h they are expected to be mined, which takes into account the full set, or "chunk", of transactions that would be included together (e.g., a parent=20 and its child, or more complicated subsets of transactions). This ordering is=20 utilized by the algorithms that implement transaction selection for constructing=20 block templates; eviction from the mempool when it is full; and transaction relay announcements to peers. - The replace-by-fee validation logic has been updated so that transaction replacements are only accepted if the resulting mempool's feerate diagram i= s strictly better than before the replacement. This eliminates all known=20 cases of replacements occurring that make the mempool worse off, which was=20 possible under previous RBF rules. For singleton transactions (that are in clusters by themselves) it's sufficient for a replacement to have a higher fee and=20 feerate than the original. See [delvingbitcoin.org post](https://delvingbitcoin.org/t/an-overview-of-the-cluster-mempool-propo= sal/393#rbf-can-now-be-made-incentive-compatible-for-miners-11) for more information. - Two new RPCs have been added: `getmempoolcluster` will provide the set of transactions in the same cluster as the given transaction, along with the ordering of those transactions and grouping into chunks; and `getmempoolfeeratediagram` will return the feerate diagram of the entire mempool. - Chunk size and chunk fees are now also included in the output of `getmempoolentry`. - The "CPFP Carveout" has been removed from the mempool logic. The CPFP=20 carveout allowed one additional child transaction to be added to a package that's=20 already at its descendant limit, but only if that child has exactly one ancestor=20 (the package's root) and is small (no larger than 10kvB). Nothing is allowed to bypass the cluster count limit. It is expected that smart contracting=20 use-cases requiring similar functionality employ TRUC transactions and sibling=20 eviction instead going forward. - Some additional discussion can be found at [doc/policy/mempool-terminology.md](https://github.com/bitcoin/bitcoin/blob= /master/doc/policy/mempool-terminology.md) and [doc/policy/mempool-replacements.md](https://github.com/bitcoin/bitcoin/blo= b/master/doc/policy/mempool-replacements.md). P2P and network changes ----------------------- - Normally local transactions are broadcast to all connected peers with=20 which we do transaction relay. Now, for the `sendrawtransaction` RPC this=20 behavior can be changed to only do the broadcast via the Tor or I2P networks. A new boolean option `-privatebroadcast` has been added to enable this behavior. This=20 improves the privacy of the transaction originator in two aspects: =C2=A0 1. Their IP address (and thus geolocation) is never known to the=20 recipients. =C2=A0 2. If the originator sends two otherwise unrelated transactions, th= ey=20 will not =C2=A0 be linkable. This is because a separate connection is used for=20 broadcasting =C2=A0 each transaction. (#29415) - New RPCs have been added to introspect and control private broadcast: `getprivatebroadcastinfo` reports transactions currently being privately broadcast, and `abortprivatebroadcast` removes matching transactions=20 from the private broadcast queue. (#34329) - Transactions participating in one-parent-one-child package relay can=20 now have the parent with a feerate lower than the `-minrelaytxfee` feerate, even=20 0 fee. This expands the change from 28.0 to also cover packages of non-TRUC transactions. Note that in general the package child can have additional unconfirmed parents, but they must already be in-mempool for the new=20 package to be relayed. (#33892) - The release has asmap data embedded for the first time, allowing the asma= p feature to be used without any externally sourced file. The embedded map=20 [was created on 2026-03-05](https://github.com/bitcoin/bitcoin/pull/34696).=20 Despite the data being available, the option remains off-by-default. Users still=20 need to set `-asmap` or `-asmap=3D1` explicitly to make it possible to use a=20 peer's ASN (ISP/hoster identifier) in netgroup bucketing in order to ensure a higher diversity in their peer set. Updated RPCs ------------ - `gettxspendingprevout` has 2 new optional arguments: `mempool_only` and `return_spending_tx`. If `mempool_only` is true it will limit scans to the mempool even if `txospenderindex` is available. If `return_spending_tx`=20 is true, the full spending tx will be returned. In addition if `txospenderindex` is available and a confirmed spending transaction is found, its block hash=20 will be returned. (#24539) - The `getpeerinfo` RPC no longer returns the `startingheight` field=20 unless the configuration option `-deprecatedrpc=3Dstartingheight` is used. The `startingheight` field will be fully removed in the next major release.=20 (#34197) - The `getblock` RPC now returns a `coinbase_tx` object at verbosity=20 levels 1, 2, and 3. It contains `version`, `locktime`, `sequence`, `coinbase` and `witness`. This allows for efficiently querying coinbase transaction=20 properties without fetching the full transaction data at verbosity 2+. (#34512) REST API -------- - A new REST API endpoint (`/rest/blockpart/.?offset=3D&size=3D`)= =20 has been introduced for efficiently fetching a range of bytes from block=20 ``. (#33657) Build System ------------ - The minimum supported Clang compiler version has been raised to 17.0=20 (#33555). - The minimum supported GCC compiler version has been raised to 12.1=20 (#33842). Updated settings ---------------- - The `-paytxfee` startup option and the `settxfee` RPC are now deleted=20 after being deprecated in Bitcoin Core 30.0. They used to allow the user to set a static fee rate for wallet transactions, which could potentially lead to overpaying or underpaying. Users should instead rely on fee estimation or specify a fee rate per transaction using the `fee_rate` argument in RPCs=20 such as `fundrawtransaction`, `sendtoaddress`, `send`, `sendall`, and `sendmany`. (#32138) - Specifying `-asmap` or `-asmap=3D1` will load the embedded asmap data=20 instead of an external file. In previous releases, if `-asmap` was specified without a filename, this would try to load an `ip_asn.map` data file. Now loading an external asmap file always requires an explicit filename like `-asmap=3Dip_asn.map`. - The `-maxorphantx` startup option has been removed. It was previously deprecated and has no effect anymore since v30.0. (#33872) - `tor` has been removed as a network specification. It was deprecated=20 in favour of `onion` in v0.17.0. (#34031) - When `-logsourcelocations` is enabled, the log output now contains=20 just the function name instead of the entire function signature. (#34088) - The default `-dbcache` value has been increased to `1024` MiB from=20 `450` MiB on systems where at least `4096` MiB of RAM is detected. This is a=20 performance increase, but will use more memory. To maintain the previous behaviour, set `-dbcache=3D450`. (#34692) - `-privatebroadcast` is added to enable private broadcast behavior for `sendrawtransaction`. New settings ------------ - `-txospenderindex` enables the creation of a transaction output=20 spender index that, if present, will be scanned by `gettxspendingprevout` if a spending transaction was not found in the mempool. (#24539) GUI changes ----------- - The GUI has been updated to Qt 6.8. (#34650) - The `createwallet`, `createwalletdescriptor` and `migratewallet`=20 commands are filtered from the console history to improve security and privacy. (gui#901= ) - The Restore Wallet dialog shows an error message if the restored=20 wallet name is empty. (gui#924) Fee Estimation -------------- The Bitcoin Core fee estimator minimum fee rate bucket was updated from **1 sat/vB** to **0.1 sat/vB**, which matches the node=E2=80=99s default=20 `minrelaytxfee`. This means that for a given confirmation target, if a sub-1 sat/vB fee rate=20 bucket is the minimum tracked with sufficient data, its average value will be=20 returned as the fee rate estimate. Restarting a node with this change invalidates previously saved estimates in `fee_estimates.dat`, the fee estimator will start tracking=20 fresh stats. IPC Interface ------------- - The IPC mining interface now requires mining clients to use the latest `mining.capnp` schema. Clients built against older schemas will fail when calling `Init.makeMining` and receive an RPC error indicating the old minin= g interface is no longer supported. Mining clients must update to the latest schema and regenerate bindings to continue working. (#34568) - `Mining.createNewBlock` now has a `cooldown` behavior (enabled by default= ) that waits for IBD to finish and for the tip to catch up. This usually=20 prevents a flood of templates during startup, but is not guaranteed. (#34184) - `Mining.interrupt()` can be used to interrupt `Mining.waitTipChanged` and `Mining.createNewBlock`. (#34184) - `Mining.createNewBlock` and `Mining.checkBlock` now require a `context` parameter. - `Mining.waitTipChanged` now has a default `timeout` (effectively=20 infinite / `maxDouble`) if the client omits it. - `BlockTemplate.getCoinbaseTx()` now returns a structured `CoinbaseTx`=20 instead of raw bytes. - Removed `BlockTemplate.getCoinbaseCommitment()` and `BlockTemplate.getWitnessCommitmentIndex()`. - Cap=E2=80=99n Proto default values were updated to match the correspondin= g C++ defaults for mining-related option structs (e.g. `BlockCreateOptions`, `BlockWaitOptions`, `BlockCheckOptions`). Credits =3D=3D=3D=3D=3D=3D=3D Thanks to everyone who directly contributed to this release: - 0xb10c - Alexander Wiederin - Alfonso Roman Zubeldia - amisha - ANAVHEOBA - Andrew Toth - Anthony Towns - Antoine Poinsot - ANtutov - Anurag chavan - Ava Chow - bensig - Ben Westgate - billymcbip - b-l-u-e - Brandon Odiwuor - brunoerg - Bruno Garcia - Calin Culianu - Carl Dong - Chandra Pratap - Chris Stewart - Coder - Cory Fields - da1sychain - Daniela Brozzoni - Daniel Pfeifer - David Gumberg - dergoegge - Dmitry Goncharov - Enoch Azariah - Eugene Siegel - Fabian Jahr - fanquake - Fibonacci747 - flack - frankomosh - furszy - glozow - Greg Sanders - Hao Xu - Hennadii Stepanov - Henry Romp - Hodlinator - ismaelsadeeq - janb84 - jayvaliya - joaonevess - John Moffett - Josh Doman - kevkevinpal - l0rinc - Luke Dashjr - Mara van der Laan - MarcoFalke - marcofleon - Martin Zumsande - Matthew Zipkin - Max Edwards - Murch - Musa Haruna - naiyoma - nervana21 - Novo - optout - pablomartin4btc - Padraic Slattery - Pieter Wuille - Pol Espinasa - pythcoiner - rkrux - Robin David - Roman Zeyde - rustaceanrob - Ryan Ofsky - SatsAndSports - scgbckbone - Sebastian Falbesoner - sedited - seduless - Sergi Delgado Segura - Sjors Provoost - SomberNight - sstone - stickies-v - stratospher - stringintech - Suhas Daftuar - tboy1337 - TheCharlatan - Tim Ruffing - Vasil Dimov - w0xlt - WakeTrainDev - Weixie Cui - willcl-ark - Woolfgm - yancy - Yash Bhutwala - yuvicc - zaidmstrr As well as to everyone that helped with translations on [Transifex](https://explore.transifex.com/bitcoin/bitcoin/). --=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/= 27c7294e-a958-4255-b0dc-3ef541811458%40achow101.com.