BTC $81,246.17 -0.35%
ETH $2,395.32 -1.05%
BNB $715.98 -0.69%
XRP $1.29 -1.58%
SOL $103.15 -1.12%
TRX $0.3333 -0.48%
DOGE $0.0791 -2.08%
ADA $0.2189 -2.98%
BCH $274.27 -0.68%
LINK $11.95 -3.12%
HYPE $77.94 -2.89%
AAVE $151.78 -2.13%
SUI $0.9743 -4.43%
XLM $0.1766 -2.54%
ZEC $1,124.69 -2.18%
AAPL $343.53 +0.13%
AMZN $248.36 -0.42%
GOOGL $338.45 -0.36%
MSFT $527.53 -0.02%
META $704.50 -0.32%
NVDA $213.66 -0.20%
TSLA $349.95 -0.85%
SNDK $1,264.35 -2.15%
INTC $88.56 -1.06%
SPCX $145.13 -0.34%
MU $861.60 -1.60%
AMD $527.23 -0.09%
BTC $81,246.17 -0.35%
ETH $2,395.32 -1.05%
BNB $715.98 -0.69%
XRP $1.29 -1.58%
SOL $103.15 -1.12%
TRX $0.3333 -0.48%
DOGE $0.0791 -2.08%
ADA $0.2189 -2.98%
BCH $274.27 -0.68%
LINK $11.95 -3.12%
HYPE $77.94 -2.89%
AAVE $151.78 -2.13%
SUI $0.9743 -4.43%
XLM $0.1766 -2.54%
ZEC $1,124.69 -2.18%
AAPL $343.53 +0.13%
AMZN $248.36 -0.42%
GOOGL $338.45 -0.36%
MSFT $527.53 -0.02%
META $704.50 -0.32%
NVDA $213.66 -0.20%
TSLA $349.95 -0.85%
SNDK $1,264.35 -2.15%
INTC $88.56 -1.06%
SPCX $145.13 -0.34%
MU $861.60 -1.60%
AMD $527.23 -0.09%

permi

All
Article
Flash

first_img XRP Ledger activates delegated permission functionality, supporting the separation of payment and compliance functions

On October 8, the XRP Ledger activated the PermissionDelegationV1_1 feature, allowing account owners to authorize other accounts to perform specific tasks without relinquishing control of the account's master key. According to the monitoring site XRPL Dashboard, such upgrades require over 80% support from trusted validators for two consecutive weeks; based on the current 35 validators, at least 29 must support it. The countdown for this feature was reset in September due to the support rate falling below the threshold.This feature allows enterprises to split permissions by function. Stablecoin issuers can authorize compliant accounts to approve new customers while keeping the master key offline. Authorized accounts use their own keys to sign and can only perform the granted operations; owners can change or revoke these permissions at any time. Each authorized account can receive up to 10 permissions, which limit the types of operations they can perform, rather than automatically setting spending limits. Banks have previously separated payment and compliance responsibilities at the employee level, and this upgrade enforces such division at the ledger level.According to a report shared by Evernorth, a subsidiary of XRP Treasury, the network held an average of $3.72 billion in tokenized assets and $539 million in Ripple's RLUSD stablecoin in the second quarter, totaling approximately $4.26 billion. Official guidance advises users not to delegate PaymentBurn permissions before separately fixing activation; this permission is intended for assistants to destroy tokens but, under certain conditions, also allows for the creation of new tokens. This warning pertains to tokens issued on the ledger rather than newly minted XRP.

first_img Matter Labs open-sources Prividium permission engine, German central bank tests self-hosted deployment

On September 8, the ZKsync development team Matter Labs announced that it has open-sourced the permission engine of its privacy blockchain platform Prividium for financial institutions under the Apache 2 license. This engine is responsible for managing roles and access permissions on the chain, determining who can read and write data. After the open-sourcing, institutions can run the permissioned chain in their own environment based on the public code without signing commercial agreements, and can independently inspect, run, and modify the core code, reducing reliance on a single vendor.The Deutsche Bundesbank became the first institution to test and deploy the open-source permission engine in its own infrastructure. Matter Labs stated that both parties will continue to collaborate on platform design and testing. Prividium achieves privacy by keeping transaction data within the institution, only recording zero-knowledge proofs that the ledger has been correctly updated on Ethereum or other compatible chains. Previously, the core of ZKsync OS, Atlas sequencer, Airbender prover, interoperability contracts, and block explorer and monitoring components have been open-sourced.Matter Labs CEO Alex Gluchowski stated that feedback from regulators indicated that relying solely on commercialized core components leads to unacceptable single vendor dependency, and the ability to run, inspect, and modify the code independently is a prerequisite for adoption. He also pointed out that this open-sourcing does not change the role of the ZK token, only adjusting which parts of the Prividium software are public code and which remain commercial products. Connectors such as management consoles, user access tools, and core banking system integrations remain paid products.

first_img XRP Ledger restarts upgrade, allowing accounts to split payment and compliance permissions

The PermissionDelegationV1_1 upgrade of the XRP Ledger entered a 14-day activation countdown on September 21, having received support from 29 of the 35 trusted validator nodes. If the support rate remains above 80% during this period, the upgrade could officially activate as early as October 5 at 11:18 UTC; at least 28 validator nodes must continue to support it, or the countdown will reset.This feature allows accounts to split permissions by role. For example, a stablecoin issuer can allow a connected compliance system to approve customer accounts holding its tokens while keeping the keys with full control offline; operational accounts can gain payment permissions but cannot change keys or delegate authority to others. Each trustee can have up to 10 permissions, and the main account can modify or revoke them at any time.This is the network's second attempt to introduce this feature. The original version had vulnerabilities that attackers could exploit to make others pay transaction fees with improperly signed transactions, and by repeatedly submitting high-fee transactions, they could deplete the victim's XRP balance. This vulnerability was reported by community testers on September 15, 2025, and validator nodes were advised to reject the amendment, so it was never activated. The fixed version was released with xrpld 3.3.0, changing the way unauthorized transactions are rejected, ensuring that fees are not deducted before signature verification.

first_img Polygon plans to deploy a permissionless burn contract, with the first round burning 100 million POL

Sandeep Nailwal, CEO of the Polygon Foundation, stated that Polygon is preparing to deploy a permissionless burn contract that allows anyone to permanently burn 100 million POL, which accounts for approximately 83% of the 121 million tokens held by the Polygon base fee collector. The contract is currently live on the testnet and will be deployed to the mainnet after the security committee completes the final signature.The first round of burns will permanently destroy 100 million POL, after which community members can trigger burns every quarter. Polygon's documentation indicates that the base fee is determined by the network and will be burned, with Nailwal stating that each base fee will inject POL into the collector. Based on the above data, approximately 21 million POL will remain in the collector after the initial burn.This burn represents about 1% of the initial supply of 10 billion POL, and based on a total supply of approximately 10.716 billion as shown by Blockscout, it accounts for about 0.93%. The burn will not set a hard cap on POL, which will continue to be issued, with an annual issuance rate of about 2% after June 2025. Nailwal also mentioned that POL has entered deflation starting January 2026, citing data from his "ChatGPT Analyst" that Polygon's revenue in 2026 will be $24.5 million, higher than Arbitrum's $8.41 million and Near's $5.6 million.

macOS malware can bypass Telegram's two-factor authentication to steal cryptocurrency wallets and account permissions

According to FinanceFeeds, security researchers have discovered an information-stealing malware targeting macOS devices that is attacking cryptocurrency users. This malware can hijack Telegram Desktop sessions, steal passwords and wallet databases, further controlling user accounts and stealing digital assets. Currently affected wallets and applications include software wallets like Exodus, Atomic, Electrum, Wasabi, and Monero.The malware is capable of extracting sensitive information from macOS Keychain, Safari Cookies, Apple Notes, Telegram Desktop, and multiple cryptocurrency wallet-related databases, including login credentials, authenticated session files, wallet data, and browser extension information. Security analysis points out that the danger of this attack chain lies in its reliance not on a single wallet vulnerability, but on collecting various types of data from the device, linking device intrusion, account takeover, wallet cracking, and mnemonic phrase theft together. Among these, Telegram Desktop sessions have become a key target.Attackers can copy authenticated Telegram local session data and restore the login on another Mac device without needing to enter a phone number, verification code, or Telegram two-factor authentication password. This means that Telegram 2FA cannot provide complete protection in this attack scenario, as the attacker is not performing a new login but is exploiting an already trusted local session. For cryptocurrency users, the risks are further amplified. Since Telegram is widely used for exchange customer service, project communities, OTC trading, and wallet communication, once attackers gain access to user session permissions, they could impersonate the victim, read private chats, locate asset information, and even spread malicious links to contacts.
app_icon
ChainCatcher Building the Web3 world with innovations.