BTC $79,718.78 -0.72%
ETH $2,304.52 -1.33%
BNB $739.44 -0.02%
XRP $1.29 -0.80%
SOL $100.10 -1.41%
TRX $0.3291 -0.35%
DOGE $0.0770 -0.17%
ADA $0.2043 -0.32%
BCH $277.76 -0.29%
LINK $11.29 -1.74%
HYPE $77.70 +1.38%
AAVE $134.47 -1.64%
SUI $0.9066 -1.61%
XLM $0.1674 -0.63%
ZEC $1,217.34 -0.01%
AAPL $343.54 -0.97%
AMZN $249.31 -0.04%
GOOGL $318.05 -1.18%
MSFT $531.91 +1.55%
META $632.79 -1.76%
NVDA $216.35 +1.49%
TSLA $392.38 +4.90%
SNDK $1,261.52 +0.13%
INTC $90.98 +3.92%
SPCX $147.93 -0.75%
MU $908.35 +1.08%
AMD $531.70 +1.91%
BTC $79,718.78 -0.72%
ETH $2,304.52 -1.33%
BNB $739.44 -0.02%
XRP $1.29 -0.80%
SOL $100.10 -1.41%
TRX $0.3291 -0.35%
DOGE $0.0770 -0.17%
ADA $0.2043 -0.32%
BCH $277.76 -0.29%
LINK $11.29 -1.74%
HYPE $77.70 +1.38%
AAVE $134.47 -1.64%
SUI $0.9066 -1.61%
XLM $0.1674 -0.63%
ZEC $1,217.34 -0.01%
AAPL $343.54 -0.97%
AMZN $249.31 -0.04%
GOOGL $318.05 -1.18%
MSFT $531.91 +1.55%
META $632.79 -1.76%
NVDA $216.35 +1.49%
TSLA $392.38 +4.90%
SNDK $1,261.52 +0.13%
INTC $90.98 +3.92%
SPCX $147.93 -0.75%
MU $908.35 +1.08%
AMD $531.70 +1.91%

wallet

Wallet is a user-friendly platform for effectively managing cryptocurrency assets. By leveraging the power of the Open Network (TON) blockchain and through mass distribution via Telegram Messenger, Wallet creates a simplified and accessible crypto gateway for the more than 800 million users of this Messenger. Wallet users can easily store, send, and receive digital assets, all within a single autonomous platform in the familiar Telegram interface.
All
Article
Flash

first_img Blink Wallet charges a monthly fee of 1 USD for idle custodial accounts, encouraging users to switch to self-custody

Blink Wallet, a Bitcoin wallet, announced a monthly idle fee of $1 for custodial accounts that have not logged into the app for 12 consecutive months. This adjustment was initiated at the beginning of September through a change in the terms of service and push notifications were sent to inactive users, with the first deduction completed in mid-October. According to a blog post released by the company, users who log back in within 12 months will have the deducted fees refunded.This fee applies only to custodial accounts and aims to alleviate the burden that inactive accounts place on the startup. The announcement stated that these accounts incur ongoing costs related to ledger and infrastructure maintenance, record verification retention, compliance monitoring and reporting, as well as support for claims, which were previously shared by active users through regular in-app transaction fees. Sources told Bitcoin Magazine that approximately 100,000 accounts met the criteria for inactivity at the time of the first deduction, with a total balance exceeding $800,000. The first deduction collected about $45,000, primarily from accounts that had been idle for over a year with small Bitcoin balances. Blink Wallet originated from the Bitcoin adoption wave in El Salvador, initially named Bitcoin Beach Wallet, and was an early custodial Lightning Network wallet that introduced the Stable Sats feature to hedge value against the US dollar. The wallet was spun off from the founding company Galoy in October 2024, operated by Lukas Duczko and a new board, with Duczko holding a controlling stake, while Galoy continues as a service provider and minority shareholder, also establishing the Bitcoin Beach Fund.In recent years, custodial wallets have faced overall pressure, with Wallet of Satoshi, Alby, and Blue Wallet successively halting custodial wallet services and shifting to self-custody infrastructures like Spark. The EU MiCA regulations regarding licensing and KYC compliance requirements are an important backdrop. Blink launched a self-custody wallet supported by Spark in June 2026, and its user base is still adapting to this transition. On September 19, hackers withdrew 6.61 Bitcoins from custodial wallet users through compromised management tools, and the company's investors subsequently announced that they would fully compensate affected users.

first_img Immunefi CEO: PHP vulnerability confirms the arrival of the AI vulnerability apocalypse as scheduled, urging vigilance against wallet risks

The vulnerability bounty platform Immunefi's CEO Mitchell Amador warned that internet users still face the risk of cyberattacks triggered by PHP vulnerabilities, especially small websites that are slow to adopt emergency upgrades, which may take weeks to patch. He stated, "The vulnerability apocalypse" is coming as planned, where the cost of discovering vulnerabilities becomes cheap while the cost of fixing them remains high. He advised users to treat any websites they log into in the coming weeks as potentially compromised, avoid reusing passwords, exercise caution when connecting to encrypted wallets, and revoke token authorizations that are unrecognizable.Previously, the PHP Foundation admitted that it delayed fixing a critical security vulnerability first discovered in 2024 due to resource shortages. PHP developers released emergency patches for two critical vulnerabilities on the same day, but each website still needs to complete the upgrade on its own. Cloudflare CEO Matthew Prince stated that within 24 hours of the PHP vulnerability being publicly disclosed, the web recorded millions of exploitation attempts, with thousands of attempts even before the disclosure. According to W3Techs, PHP supports about 69% of websites with known server-side programming languages, and these vulnerabilities could allow attackers to spread malware or inject malicious scripts into websites.The FBI's Cyber Division also warned that these vulnerabilities could allow malicious actors to "remotely execute code in the PHP core, potentially compromising sensitive data and networks." Amador warned in an interview with Cointelegraph in June that the proliferation of cutting-edge AI models has changed the cybersecurity landscape, giving attackers an advantage, leading to the emergence of the "vulnerability apocalypse," and triggering a resurgence of DeFi hacking attacks. Immunefi is the world's largest vulnerability bounty platform, having paid out $140 million in bounties to 650 protocols to date.

first_img Electrum Bitcoin wallet fixes the theft vulnerability with a fee increase

On October 24, the Bitcoin lightweight wallet Electrum disclosed a malicious server attack targeting transaction fee increases and fixed it in version 4.8.3, corresponding to GitHub security advisory GHSA-6jp4-8v48-cc5v. Users may inadvertently sign funds over to the attacker when performing regular fee increases on transactions. Developers stated that the issue arose after users reported losing funds after signing fee increases.The results of two reports differed: one person discovered that transactions in the wallet history were replaced after broadcasting a payment and claimed that the original payment did not enter the Bitcoin peer-to-peer network and was withheld by the server; another person, Raju-K12, reported losing funds due to the fee increase on the replaced transaction. In the attack, the malicious server withheld new transactions broadcasted by the client and inserted a conflicting transaction into the history, replacing the original output with the attacker's address. The replacement transaction was signed invalidly at that time, but the lightweight client did not verify these signatures before displaying unconfirmed transactions; after the user manually increased the fee and signed through RBF, the attacker received the funds. Both individuals claimed that the last four digits of the attacker's address were the same as those of the legitimate receiving address. The announcement did not disclose the amount stolen, transaction identifiers, or the attacker's address.The patch corresponds to commit 90fe308, which checks the signatures of the wallet's own inputs before writing memory pool transactions to local history, but does not overwrite inputs from external addresses of the wallet and does not perform complete consensus verification. The announcement suggests that users who have not upgraded should verify the output address and amount each time they sign; clients connected to their own or trusted servers are not affected by this attack. On the timeline, the issue was first privately disclosed on October 11, received reports of fee loss on October 18, the fixed version was tagged on October 23, and the binary and public disclosure occurred on October 24.
app_icon
ChainCatcher Building the Web3 world with innovations.