ChainCatcher news, Satoshi Action Fund co-founder Dennis Porter announced on social media that he will no longer provide funding support for Bitcoin Core development.In his tweet, Porter stated that he has helped raise over $200,000 for core developers during his time in the Bitcoin space, but now he has lost confidence in the work of the core developers.

ChainCatcher news, according to Protos, the Bitcoin Core development team announced that it will modify the default settings of OP_RETURN in the upcoming Core 30 version to be released in October, raising the data carrier limit from 80 bytes to nearly 4 MB. This decision marks a phased victory for the reformists led by Antoine Poinsot in their long-standing dispute with conservatives like Luke Dashjr.Although the new version still allows node operators to manually revert to the smaller data limit, analysis indicates that most nodes will maintain the default settings. Conservatives criticize this move as contrary to the original design intent of Bitcoin as a value transfer network, potentially turning the blockchain into a data storage platform. Reformists argue that moderate expansion helps to enhance Bitcoin's functionality and have made compromises to allow for parameter adjustments. This change is expected to impact the on-chain data storage ecosystem but will not alter the fundamental transaction verification mechanism of Bitcoin.

According to a ChainCatcher message, a developer statement indicates that the next version of Bitcoin Core may abolish the limit of OP_RETURN outputs not exceeding 80 bytes.It states that the 80-byte limit for OP_RETURN is no longer suitable for current needs, as many private mining accelerators have already stopped enforcing these restrictions, which also creates distorted incentive mechanisms.

ChainCatcher message, Bitcoin Core released version v29.0, which improves the handling of P2P network and block synchronization, adds a new mechanism for handling orphan block transactions, and updates mining and mempool policies, among other things.

ChainCatcher message, Bitcoin core developer Luke Dashjr believes that ordinals/inscriptions are an attack on Bitcoin, and Trump's issuance of inscriptions on Bitcoin is an attack on Bitcoin, which is a national attack.

ChainCatcher news, according to Bitcoin Magazine, New York's Chaincode Labs has awarded 17-year-old Ishaana Misra the inaugural Bitcoin Scholarship, making her the youngest core code contributor in the 15-year history of Bitcoin technology. The scholarship was selected from 232 applicants worldwide, covering her tuition for one year and potentially renewable each year to support her entire undergraduate education.Misra started programming at the age of 12 and entered the Bitcoin space after reading the Bitcoin whitepaper before high school. She transitioned from running nodes to contributing to the Bitcoin Core codebase by self-learning C++. Misra stated that the Bitcoin community values work results over age, creating an environment that is particularly friendly to young developers.Chaincode Labs CEO Adam Jonas said that this scholarship aims to encourage young people to engage in Bitcoin open-source development and provide them with experience and educational support.

ChainCatcher news, according to Protos, Bitcoin developers recently disclosed details of a high-risk software vulnerability named CVE-2024-35202. According to senior core developers, over 13% of home and commercial computers executing Bitcoin rules globally are affected by a remote shutdown vulnerability.The vulnerability affects nodes running versions of Bitcoin Core prior to 25.0, allowing attackers to crash nodes by manipulating block transaction messages. The vulnerability originates from Core's compact block protocol, which uses shortened transaction identifiers to reduce internet bandwidth usage. Attackers can trigger conflicts in these identifiers, causing nodes to request complete blocks. While requesting complete, untruncated blocks is a security precaution, versions of the software prior to 25.0 have flaws in the logic for handling subsequent blocktxn messages.In short, nodes can be forced into an invalid state by manipulating logic gates, leading to a complete crash. Although there is no economic incentive for ordinary attackers, developers strongly recommend that node operators update to the latest version. The credit for discovering and disclosing this vulnerability goes to Niklas Gögge, and Bitcoin Core 25.0 has resolved this issue.

ChainCatcher news, according to Protos, Craig Wright seems to be representing himself in the latest lawsuit against Bitcoin Core and Jack Dorsey's payment company Square. Bitmex Research points out that the UK High Court case tracking shows that Wright recently filed a lawsuit as a "party," indicating that he may be pursuing the case without legal representation.Although the lawsuit specifically names the software used for distributing Bitcoin, Bitcoin Core, and Square Up Europe Ltd., the case tracking page does not specify the purpose of the lawsuit.Recently, Wright posted an article on X regarding the lawsuit and legal threats against MicroStrategy, but it is currently unclear whether this is related to the lawsuit.He is attempting to file three legal appeals in the UK, all of which are awaiting approval. Two of them are against the Crypto Open Patent Alliance (COPA), and one is against Peter McCormack.

ChainCatcher news, former Bitcoin Core developer Peter Todd denied being Bitcoin founder Satoshi Nakamoto on the eve of HBO's upcoming documentary about Satoshi Nakamoto. Peter Todd stated in an interview that the accusations from documentary producer Cullen Hoback are baseless.It is reported that there was a leaked video suspected to be from the HBO documentary, in which HBO believes Bitcoin Core developer Peter Todd is the Bitcoin founder Satoshi Nakamoto. However, the authenticity of the leaked video has not been officially confirmed, and there is a possibility of false information.

ChainCatcher news, according to Protos, Bitcoin Core developers have issued a new high-risk warning, stating that one in every six Bitcoin nodes has a software vulnerability. On Thursday, the staff responsible for maintaining the open-source Bitcoin Core project, which runs on over 98% of reachable full nodes, disclosed that the software running on 17% of the nodes in the network has significant security issues. Specifically, all software versions below Bitcoin Core 24.0.1 are at risk. According to monitoring estimates from Bitnodes, this denial-of-service vulnerability affects approximately 3,330 of the 19,200 self-identified user agents of accessible Bitcoin full nodes.In Bitcoin Core software prior to version 24.0.1, malicious actors could spam nodes with low-difficulty header chains. By forcing nodes to download and store extremely long header chains, the attack could crash nodes by consuming excessive bandwidth or device storage space. Developers fixed this vulnerability in Bitcoin Core pull request (PR) number 25717 and merged it into production with the release of v24.0.1 on December 12, 2022. The current version of Bitcoin Core node software (now 27.1) includes fixes for this vulnerability and others.Although this vulnerability is quite serious, there are few known cases of attacks exploiting it in public records. The cost of generating and broadcasting block header chains to execute a denial-of-service attack is relatively high, making the vulnerability of little economic benefit to attackers.

ChainCatcher news, according to official sources, the Arthur Hayes family office Maelstrom has announced that it has awarded the first grant of its Bitcoin developer program to contributor Rkrux. This funding will support Rkrux in working full-time on Bitcoin Core, with the specific amount of funding not yet disclosed.

ChainCatcher news, according to Cointelegraph, Bitcoin Core developers have launched a "Critical Bug" disclosure policy aimed at more effectively communicating about Bitcoin security vulnerabilities.In a letter sent on July 3 to members of the Bitcoin Development mailing list, Bitcoin Core developer Antoine Poinsot and five others stated: "The project has historically performed poorly in publicly disclosing security-critical vulnerabilities, whether reported externally or discovered by contributors. There is a dangerous perception that Bitcoin Core has no bugs, which is dangerous and, unfortunately, not accurate."

ChainCatcher news, according to Bitcoin.com, the Bitcoin Core Optech Newsletter #306 advises users to "upgrade to Bitcoin Core 25.0 or higher within the next two weeks, with the latest version being 27.0."Several Bitcoin Core project members discussed a new policy regarding vulnerability disclosure. If Bitcoin Core releases a new version, low-severity vulnerabilities will be disclosed approximately two weeks after the new version is released, while most other vulnerabilities will be disclosed after the affected version reaches its end of life.

ChainCatcher news, Bitcoin Core developer Peter Todd posted on platform X that Starknet's foray into Bitcoin's scaling layer is a good reason to oppose enabling OP_CAT. Starknet could bring destructive MEV shenanigans to Bitcoin, just like Ethereum, and pouring large amounts of funds into the nascent STARKS is unreliable; Eli's Zcash has repeatedly (maliciously) exploited token inflation.

ChainCatcher news, the proposal "datacarriersize: Match more datacarrying #28408" initiated by Bitcoin Core developer Luke Dashjr discussed the issue of whether to restrict inscriptions. After discussions among several Bitcoin Core developers, it was not approved, and the proposal is currently marked as closed.It is reported that Bitcoin Core developer Ava Chow summarized and closed this PR, stating that it is clear this proposal is controversial, and given the current situation, it is impossible to reach a conclusion that satisfies everyone, believing there is no need to continue the discussion.Additionally, another Bitcoin Core code maintainer, gloria, summarized this PR.Supporting Luke's viewpoint are:Stop inscriptions; they are spam;Inscriptions and embedded data can harm the network;People want this: there is user demand and specific use cases that Bitcoin Core should provide; another option is for people to write and run patches, but this may be unsafe;This is just fixing the data carrier size to work as intended;Opposing Luke's viewpoint are:This will not stop inscriptions; miners are unlikely to adopt this strategy as it is incompatible with incentives;We cannot write code to detect all embedded data;This PR changes the default mempool policy, posing potential harm to individual node operators and the network;Other opposing viewpoints include:Generally speaking, using mempool policies to block usage is ineffective;Attempting to "review" transactions based on usage is inappropriate; the free market determines the use of Bitcoin;This also changes the operation of -datacarriersize executed from underlying users.