A comparison of five crypto mass payout services for 2026: NOWPayments, Binance Pay, Crypto.com Pay, BTCPay Server, and Coinbase Business. Each is evaluated on fee structure, settlement speed, and custody model. NOWPayments is ranked first for its ChangeNOW PRO email payouts with zero network and service fees and sub-second settlement. Binance Pay and Crypto.com Pay offer zero transaction fees within their closed ecosystems. BTCPay Server is the only self-hosted, non-custodial option with no platform fees. Coinbase Business provides free stablecoin transfers between accounts with strong regulatory compliance.
Nguồn: https://www.sitepoint.com/best-mass-payouts-service. 8sync News chỉ tóm tắt và dẫn link; bản quyền nội dung thuộc tác giả và nguồn gốc.
Coinspaid Dev, the engineering team behind Coinspaid Solutions, has launched as an independent brand after over 11 years of building blockchain infrastructure. With 120+ engineers, the team has experience across 20+ blockchain networks, covering distributed systems, backend architecture, cloud infrastructure, cybersecurity, and reliability engineering. The new brand aims to become a center of competence for blockchain infrastructure engineering and contribute practical expertise to the broader digital asset ecosystem.
Polymarket confirmed hackers stole approximately $3 million in cryptocurrency from over 11 users after a third-party vendor was compromised, injecting malicious code into the prediction market's frontend. The stolen funds were bridged from Polygon to Ethereum and converted into roughly 1,893 ETH. Polymarket says it has contained the incident and is refunding affected users in full. The attack was a supply chain compromise — no core smart contracts were exploited. The breach is the latest in a string of bad news for Polymarket, which also faced a separate $520K smart contract drain in May, a Wall Street Journal investigation into deceptive promotional videos, a Google engineer insider trading charge, regulatory blocks in multiple countries, and a $345 million governance dispute.
The Ethereum Foundation (EF) has completed a major reorganization, reducing its workforce by 54 people (roughly 20%) and restructuring into five domain clusters: Protocol Layer, Access Layer, User Layer, Community Layer, and Institutional Layer, plus operations and management clusters. The Protocol Layer focuses on hardening and scaling Ethereum's core protocol while preserving censorship resistance, privacy, and security. The Access Layer ensures self-sovereignty is practically available for key user actions. The User Layer grounds EF work in real user needs. The Community Layer manages EF's public presence and external relationships. The Institutional Layer engages enterprises, governments, and nonprofits on Ethereum adoption. Departing employees receive severance of one month per year worked (or local legal minimum, whichever is higher) plus transition support including career coaching grants.
Digital information can be copied infinitely, but money requires exclusive ownership — this is the double-spending problem that made decentralized digital currency seem impossible for years. Centralized systems like banks solve it via a trusted ledger, but Bitcoin's 2008 breakthrough eliminated the need for a central authority by combining a distributed blockchain ledger, cryptographic digital signatures, and a Proof of Work consensus mechanism. The result: thousands of strangers can agree on who owns what without trusting any single party. Residual risks remain — unconfirmed transactions, 51% attacks, and weakly secured networks — but the core problem is largely solved, forming the foundation for every blockchain that exists today.
A security researcher details the discovery of a chain-halting DoS vulnerability in Injective's Peggy Bridge during a Code4rena audit. The bug stems from unbounded state accumulation in the rate limiting module: every bridge transfer appends to an uncapped slice, and the Cosmos SDK EndBlocker iterates over all tokens × all transfers on every block, creating O(N×M) complexity. An attacker can bloat state with dust transactions across many tokens, causing CPU exhaustion that exceeds consensus timeouts and halts the chain. A PoC unit test confirmed 100% CPU spike. The recommended fix involves hard caps on the Transfers slice and efficient KVStore indexing using composite keys for range-based pruning.