BTC $61,537.01 -3.64%
ETH $1,736.33 -3.99%
BNB $567.30 -4.16%
XRP $0.9445 -4.48%
SOL $70.98 -5.05%
TRX $0.3055 -2.22%
DOGE $0.0564 -5.27%
ADA $0.1464 -5.56%
BCH $196.11 -6.25%
LINK $8.75 -5.24%
HYPE $63.18 -8.27%
AAVE $101.30 -7.29%
SUI $0.6822 -6.73%
XLM $0.1314 -4.81%
ZEC $811.31 -14.50%
AAPL $350.36 -1.24%
AMZN $251.69 -8.35%
GOOGL $270.88 -7.96%
MSFT $487.99 -5.78%
META $575.07 -8.40%
NVDA $141.22 -7.95%
TSLA $366.41 -6.77%
SNDK $747.36 -4.58%
INTC $53.21 -7.11%
SPCX $129.88 -11.10%
MU $654.49 -11.56%
AMD $457.07 -15.89%
BTC $61,537.01 -3.64%
ETH $1,736.33 -3.99%
BNB $567.30 -4.16%
XRP $0.9445 -4.48%
SOL $70.98 -5.05%
TRX $0.3055 -2.22%
DOGE $0.0564 -5.27%
ADA $0.1464 -5.56%
BCH $196.11 -6.25%
LINK $8.75 -5.24%
HYPE $63.18 -8.27%
AAVE $101.30 -7.29%
SUI $0.6822 -6.73%
XLM $0.1314 -4.81%
ZEC $811.31 -14.50%
AAPL $350.36 -1.24%
AMZN $251.69 -8.35%
GOOGL $270.88 -7.96%
MSFT $487.99 -5.78%
META $575.07 -8.40%
NVDA $141.22 -7.95%
TSLA $366.41 -6.77%
SNDK $747.36 -4.58%
INTC $53.21 -7.11%
SPCX $129.88 -11.10%
MU $654.49 -11.56%
AMD $457.07 -15.89%

engine

All
Article
Flash

first_img Binance Chinese Community Head Sisi: Binance takes responsibility for the stolen platform, not shifting blame to engineers and technical standards

On November 4, the head of the Binance Chinese community, Sisi, responded to the security incident at the end of October, stating that approximately $6.3 billion was transferred out of the Binance system, and the responsibility lies with Binance, not with any individual engineer or technical standard. She stated that the related losses would be compensated by the platform, and users could verify themselves on the reserve proof page; the frozen and intercepted portions would be recovered one by one in cooperation with law enforcement and on-chain institutions.Sisi mentioned that after the withdrawal was reopened, the platform focused on ensuring that every withdrawal was processed. She stated that the scale of withdrawals in the past two days was on the same level as the stolen amount, and every transaction had been fulfilled, with user assets remaining intact; the platform did not misappropriate user assets. She also stated that the company's decision-making body requested that the investigation report be unembellished and truthfully disclosed, with timelines, attack paths, malicious script operations, and internal shortcomings all included in the report.Sisi cited an FBI report stating that the adversary was a nation-state actor, and since the beginning of this year, Binance had intercepted 57 suspected attacks from the same source. She indicated that all intrusion points mentioned in the report had been blocked; as of November 3, the affected wallet system had been rebuilt in a new environment, internal AI tools had been rebuilt and permissions tightened, affected devices had been replaced, relevant credentials and tokens had been invalidated, and a comprehensive device security scan and wallet risk control upgrade had been completed. She also mentioned that some defensive lines would not be made public and that an independent third-party security agency had been hired for review, with the conclusions to be announced externally. Binance's preliminary investigation previously indicated that the incident involved assets of approximately $6.34 billion, with about $2.85 billion frozen or intercepted, and the losses would be borne by the platform.

first_img Proton CTO: Programming is dead, engineers should help models write code

The privacy email and VPN service provider Proton publicly shared an internal memo titled "AI @ Proton, Engineering Manifesto," written by Chief Technology Officer Bart Butler about a month ago. The memo states that software engineering has undergone irreversible changes this year, as large language models and their tools can now write code. A senior Proton engineer indicated that no one in their business unit is writing code by hand anymore. Butler believes that the era of manually writing excellent code is over; time-consuming tasks such as documentation, testing, and boilerplate code can be handled by models, which can also participate in architecture and system design discussions.Butler pointed out that although engineers are widely using large language models, Proton's productivity has not significantly improved for three reasons. First, the engineering culture needs to shift; the work of engineers is no longer to write code but to help models write better code faster. Each engineer should become a team leader for models and agents, promoting their autonomous and continuous work, and reducing repetitive failures through repository-level context, shared skills, and prompts. Second, the company is still in the first phase of using models to accelerate existing processes and needs to enter the second phase, which involves eliminating bottlenecks across continuous integration, design, approval, specifications, and code review, with the expectation that most manual code reviews will come to an end. Third, there is a collective action problem between individual use of models and the overall transformation of company processes, as the organization has not invested enough resources.The memo emphasizes that this is not the end of expertise or good engineering practices; maintainability, documentation, and testing remain critical, but best practices will adjust with changes in cost and capability. Butler wrote, "Programming is dead," but engineering and professional skills have not vanished. The new responsibility of engineers is to continuously optimize and maximize automation as builders, and Proton will organize and allocate resources to complete this transformation. Proton stated that the memo is not an in-depth discussion of engineering documents related to security, reliability, or infrastructure. It also mentioned that technology companies have laid off over one million people in recent years, and Microsoft proposed 60,000 buyout offers last week.

hot_img Binance: Security incident possibly involving an engineer's laptop being hacked, affecting approximately 6.3 billion USD

Binance released preliminary investigation results on its official X account, stating that the security incident may involve the laptop of a DevOps engineer being compromised. The attacker used this to access the service container and submitted unauthorized withdrawal transactions. Binance stated that there is currently no evidence of wallet private key leakage and will publish a detailed technical review after the investigation is complete and the facts are fully verified.Binance estimated the total impact of the incident to be approximately $6.3 billion. The platform has frozen related assets in collaboration with blockchain partners, with about $3 billion currently frozen on-chain. Binance stated that it will cover all losses through the SAFU fund and company funds, ensuring user fund safety, and will release updated proof of reserves after the resolution is complete.As an immediate measure, Binance has suspended deposits and withdrawals until security checks are completed, revoked the authorization of affected addresses, and has contacted law enforcement and blockchain intelligence partners to track and recover funds. Binance stated that the team is working with law enforcement partners to confirm the identities of the relevant individuals and reminds users to obtain updates only through official channels.

first_img Lido engineer warns of Glamsterdam staking deposit hijacking risk

Dmitry Gusakov, the engineering lead of the Ethereum liquid staking protocol Lido, warned at the developer conference ACDC #189 that the one-time builder access mechanism introduced by the Glamsterdam upgrade could interfere with the existing deposit protection logic of the staking protocol, leading to the hijacking of staking deposits. This issue involves multiple deposits sharing the same validator public key.According to Ethereum's current deposit rules, the first valid deposit determines the withdrawal credential, and staking protocols typically leverage this feature to prevent credential manipulation, such as initially depositing a small amount of ETH and then topping up the remaining funds once the expected credential appears. However, the special access mechanism introduced for builders by Glamsterdam may change the interpretation of subsequent pending deposits under the same public key during the fork transition period, putting the staking protocol at risk of a third outcome: the validator does not appear, and the deposited ETH is credited to the builder.Lido's proposed fix is to maintain the distinction between validator deposits and builder deposits during the one-time access process. However, core developers rejected this modification on the grounds of timing, mainly because the Sepolia testnet has already been activated according to existing specifications, and the Hoodi client version is also in preparation. Changing the behavior at this point could require redeploying Sepolia and conducting additional testing. The issue affects the access process during the fork transition period, rather than the ongoing deposit processing rules, but its consequences could impact deposits waiting in the queue.
app_icon
ChainCatcher Building the Web3 world with innovations.