USDD Update. Running strong for 6+ months since December — Binance Wallet USDD Strategy Phase 6 is coming soon.

29 May 2026, 11:47
🚀 USDD Update 🔥 Running strong for 6+ months since December Binance Wallet USDD Strategy Phase 6 is coming soon! 💰 800,000 USDD reward pool 50-day campaign No cap, flexible access 🔍 Fully transparent Stay tuned. 🚀 🔗

Same news in other sources

9
Ethereum
EthereumETH #2
Telegram
29 May 2026, 12:30
🇺🇸📝 USA - Trade Balance (Apr - Prelim) = -$82.4 Billion (Expected -$86.7 Billion / Previously -$87.45 Billion)
USA - Trade Balance (Apr - Prelim) = -$82. 4 Billion (Expected -$86. 7 Billion / Previously -$87. 45 Billion).
🇺🇸📝 USA - Trade Balance (Apr - Prelim) = -$82.4 Billion (Expected -$86.7 Billion / Previously -$87.45 Billion)
Ethereum
EthereumETH #2
Telegram
29 May 2026, 12:16
👮 Texas announces the creation of the "Texas Strategic Bitcoin Reserve Advisory Committee." Texas is now also looking for a qualified firm to custody their $BTC for when they buy more.
Texas announces the creation of the "Texas Strategic Bitcoin Reserve Advisory Committee.
👮 Texas announces the creation of the "Texas Strategic Bitcoin Reserve Advisory Committee." Texas is now also looking for a qualified firm to custody their $BTC for when they buy more.
MarsDAO
MarsDAOMDAO #2198
Telegram
29 May 2026, 12:13
🔊 Right now, a mega tournament is underway on MDAO Arena, where we’re giving away a massive prize pool! The best part is that there’s absolutely no entry barrier. To qualify and be eligible for rewards, all you need to do is make at least one $1 swap. That’s right, just one dollar separates you from participating in the prize pool distribution: 1️⃣ Go to MDAO Arena. 2️⃣ Connect your wallet. 3️⃣ Make a minimum swap for your chosen meme fighter to activate your participation. Don’t miss your chance while the clock is ticking! This is a one-time event with such a large prize pool 🏁 Most importantly, the total number of users who activate your referral link counts toward your total. You can get your referral link here 🔴 🏆 Follow the results here: 🌐 arena.daomars.com
Right now, a mega tournament is underway on MDAO Arena, where we're giving away a massive prize pool.
🔊 Right now, a mega tournament is underway on MDAO Arena, where we’re giving away a massive prize pool! The best part is that there’s absolutely no entry barrier. To qualify and be eligible for rewards, all you need to do is make at least one $1 swap. That’s right, just one dollar separates you from participating in the prize pool distribution: 1️⃣ Go to MDAO Arena. 2️⃣ Connect your wallet. 3️⃣ Make a minimum swap for your chosen meme fighter to activate your participation. Don’t miss your chance while the clock is ticking! This is a one-time event with such a large prize pool 🏁 Most importantly, the total number of users who activate your referral link counts toward your total. You can get your referral link here 🔴 🏆 Follow the results here: 🌐 arena.daomars.com
Dogecoin
DogecoinDOGE #9
Telegram
29 May 2026, 12:12
Copper prices hit new record highs, marking a significant milestone for the metal's market value.
Copper prices hit new record highs, marking a significant milestone for the metal's market value.
HOPR
HOPRHOPR #1104
Telegram
29 May 2026, 12:05
It's time for your tri-weekly DevUpdate 🛠️🟡 Our developers have been working intensively over the past three weeks. Let's check out the updates 🟡 We unified channel management and derived funding from on-chain metrics across core, hoprd, and edge-client, while adding safeguards against redundant opens and fixing capacity accounting for tighter path de-duplication github.com/hoprnet/hoprd/pull/26 github.com/hoprnet/hoprnet/pull/8106 github.com/hoprnet/edge-client/pull/60 github.com/hoprnet/edge-client/pull/61 github.com/hoprnet/hoprnet/pull/8125 github.com/hoprnet/hoprnet/pull/8121 github.com/hoprnet/hoprnet/pull/8093 🟡 Overhauled the transport pipeline into a node-specific builder pattern for better reliability, adding 38 integration tests, starvation avoidance helpers, and explicit intermediate-path sessions with matching hoprd API support. github.com/hoprnet/hoprnet/pull/8097 github.com/hoprnet/hoprnet/pull/8098 github.com/hoprnet/hoprnet/pull/8100 github.com/hoprnet/hoprnet/pull/8114 github.com/hoprnet/hoprnet/pull/8103 github.com/hoprnet/hoprnet/pull/8122 github.com/hoprnet/hoprnet/pull/8118 github.com/hoprnet/hoprd/pull/20 🟡 We finalized the RFC-0010 v1.1.0 probing spec and enforced strict path validation by rejecting non-adjacent duplicate on-chain addresses to strengthen correctness and slashing assumptions. github.com/hoprnet/rfc/pull/77 github.com/hoprnet/hopr-types/pull/53 🟡 We migrated the edge-client to hopr-lib/hopr-reference to tighten chain operations and fix wxHOPR withdrawals, while also generalizing e2e session testing with a shared harness and a new Rotsee test suite. github.com/hoprnet/edge-client/pull/57 github.com/hoprnet/edge-client/pull/59 github.com/hoprnet/edge-client/pull/63 🟡 Upgraded the on-chain indexer to align with Rotsee defaults and prevent crashes, while also modernizing contracts to include xHOPR and updating types to alloy 2.0 builders with new keypair and telemetry features. github.com/hoprnet/blokli/pull/351 github.com/hoprnet/blokli/pull/349 github.com/hoprnet/blokli/pull/346 github.com/hoprnet/blokli/pull/345 github.com/hoprnet/blokli/pull/342 github.com/hoprnet/blokli/pull/341 github.com/hoprnet/blokli/pull/338 github.com/hoprnet/blokli/pull/354 github.com/hoprnet/blokli/pull/353 github.com/hoprnet/blokli/pull/352 github.com/hoprnet/blokli/pull/348 github.com/hoprnet/blokli/pull/269 github.com/hoprnet/contracts/pull/93 github.com/hoprnet/contracts/pull/92 github.com/hoprnet/contracts/pull/101 github.com/hoprnet/hopr-types/pull/49 github.com/hoprnet/hopr-types/pull/47 github.com/hoprnet/hopr-api/pull/62 github.com/hoprnet/hopr-api/pull/65 github.com/hoprnet/hopli/pull/75 github.com/hoprnet/hoprnet/pull/8104 🟡 To simplify release management, we prepared RC releases, consolidated the core workspace to 13 public crates, and extracted hoprd into a dedicated repository aligned with the latest core dependencies. github.com/hoprnet/hoprnet/pull/8108 github.com/hoprnet/hoprnet/pull/8109 github.com/hoprnet/hoprnet/pull/8112 github.com/hoprnet/hoprd/pull/16 🟡 We hardened Docker/Nix builds and addressed RUSTSEC advisories while significantly improving deployment and observability through jemalloc-based memory profiling, enriched localcluster ergonomics, and better REST API error surfacing. github.com/hoprnet/hoprnet/pull/7510 github.com/hoprnet/hoprd/pull/37 github.com/hoprnet/hoprd/pull/35 github.com/hoprnet/hoprd/pull/31 github.com/hoprnet/hoprd/pull/30 github.com/hoprnet/hoprd/pull/29 github.com/hoprnet/hoprd/pull/28 github.com/hoprnet/hoprd/pull/23 github.com/hoprnet/hoprd/pull/32 github.com/hoprnet/hoprd/pull/22 github.com/hoprnet/hoprd/pull/21 github.com/hoprnet/hoprd/pull/18 github.com/hoprnet/hoprd/pull/17 github.com/hoprnet/hoprd/pull/13 github.com/hoprnet/hoprd/pull/11 github.com/hoprnet/hoprd/pull/2 github.com/hoprnet/hoprnet/pull/8102 github.com/hoprnet/hoprd/pull/25 🟡 We expanded our API surface to broaden future ecosystem integrations by officially adding PIX protocol-related API types and events. github.com/hoprnet/hopr-api/pull/66
It's time for your tri-weekly DevUpdate. Our developers have been working intensively over the past three weeks.
It's time for your tri-weekly DevUpdate 🛠️🟡 Our developers have been working intensively over the past three weeks. Let's check out the updates 🟡 We unified channel management and derived funding from on-chain metrics across core, hoprd, and edge-client, while adding safeguards against redundant opens and fixing capacity accounting for tighter path de-duplication github.com/hoprnet/hoprd/pull/26 github.com/hoprnet/hoprnet/pull/8106 github.com/hoprnet/edge-client/pull/60 github.com/hoprnet/edge-client/pull/61 github.com/hoprnet/hoprnet/pull/8125 github.com/hoprnet/hoprnet/pull/8121 github.com/hoprnet/hoprnet/pull/8093 🟡 Overhauled the transport pipeline into a node-specific builder pattern for better reliability, adding 38 integration tests, starvation avoidance helpers, and explicit intermediate-path sessions with matching hoprd API support. github.com/hoprnet/hoprnet/pull/8097 github.com/hoprnet/hoprnet/pull/8098 github.com/hoprnet/hoprnet/pull/8100 github.com/hoprnet/hoprnet/pull/8114 github.com/hoprnet/hoprnet/pull/8103 github.com/hoprnet/hoprnet/pull/8122 github.com/hoprnet/hoprnet/pull/8118 github.com/hoprnet/hoprd/pull/20 🟡 We finalized the RFC-0010 v1.1.0 probing spec and enforced strict path validation by rejecting non-adjacent duplicate on-chain addresses to strengthen correctness and slashing assumptions. github.com/hoprnet/rfc/pull/77 github.com/hoprnet/hopr-types/pull/53 🟡 We migrated the edge-client to hopr-lib/hopr-reference to tighten chain operations and fix wxHOPR withdrawals, while also generalizing e2e session testing with a shared harness and a new Rotsee test suite. github.com/hoprnet/edge-client/pull/57 github.com/hoprnet/edge-client/pull/59 github.com/hoprnet/edge-client/pull/63 🟡 Upgraded the on-chain indexer to align with Rotsee defaults and prevent crashes, while also modernizing contracts to include xHOPR and updating types to alloy 2.0 builders with new keypair and telemetry features. github.com/hoprnet/blokli/pull/351 github.com/hoprnet/blokli/pull/349 github.com/hoprnet/blokli/pull/346 github.com/hoprnet/blokli/pull/345 github.com/hoprnet/blokli/pull/342 github.com/hoprnet/blokli/pull/341 github.com/hoprnet/blokli/pull/338 github.com/hoprnet/blokli/pull/354 github.com/hoprnet/blokli/pull/353 github.com/hoprnet/blokli/pull/352 github.com/hoprnet/blokli/pull/348 github.com/hoprnet/blokli/pull/269 github.com/hoprnet/contracts/pull/93 github.com/hoprnet/contracts/pull/92 github.com/hoprnet/contracts/pull/101 github.com/hoprnet/hopr-types/pull/49 github.com/hoprnet/hopr-types/pull/47 github.com/hoprnet/hopr-api/pull/62 github.com/hoprnet/hopr-api/pull/65 github.com/hoprnet/hopli/pull/75 github.com/hoprnet/hoprnet/pull/8104 🟡 To simplify release management, we prepared RC releases, consolidated the core workspace to 13 public crates, and extracted hoprd into a dedicated repository aligned with the latest core dependencies. github.com/hoprnet/hoprnet/pull/8108 github.com/hoprnet/hoprnet/pull/8109 github.com/hoprnet/hoprnet/pull/8112 github.com/hoprnet/hoprd/pull/16 🟡 We hardened Docker/Nix builds and addressed RUSTSEC advisories while significantly improving deployment and observability through jemalloc-based memory profiling, enriched localcluster ergonomics, and better REST API error surfacing. github.com/hoprnet/hoprnet/pull/7510 github.com/hoprnet/hoprd/pull/37 github.com/hoprnet/hoprd/pull/35 github.com/hoprnet/hoprd/pull/31 github.com/hoprnet/hoprd/pull/30 github.com/hoprnet/hoprd/pull/29 github.com/hoprnet/hoprd/pull/28 github.com/hoprnet/hoprd/pull/23 github.com/hoprnet/hoprd/pull/32 github.com/hoprnet/hoprd/pull/22 github.com/hoprnet/hoprd/pull/21 github.com/hoprnet/hoprd/pull/18 github.com/hoprnet/hoprd/pull/17 github.com/hoprnet/hoprd/pull/13 github.com/hoprnet/hoprd/pull/11 github.com/hoprnet/hoprd/pull/2 github.com/hoprnet/hoprnet/pull/8102 github.com/hoprnet/hoprd/pull/25 🟡 We expanded our API surface to broaden future ecosystem integrations by officially adding PIX protocol-related API types and events. github.com/hoprnet/hopr-api/pull/66
Solidus Ai Tech
Solidus Ai TechAITECH #961
Telegram
29 May 2026, 12:00
The next ACN token burn is scheduled to take place in 3 days. As part of AITECH Cloud Network’s ongoing supply management framework, a defined amount of ACN will be permanently removed from circulation through a fully transparent and verifiable on-chain burn.
The next ACN token burn is scheduled to take place in 3 days.
The next ACN token burn is scheduled to take place in 3 days. As part of AITECH Cloud Network’s ongoing supply management framework, a defined amount of ACN will be permanently removed from circulation through a fully transparent and verifiable on-chain burn.
Solidus Ai Tech
Solidus Ai TechAITECH #961
Telegram
29 May 2026, 12:00
The next ACN token burn is scheduled to take place in 3 days. As part of AITECH Cloud Network’s ongoing supply management framework, a defined amount of ACN will be permanently removed from circulation through a fully transparent and verifiable on-chain burn.
The next ACN token burn is scheduled to take place in 3 days.
The next ACN token burn is scheduled to take place in 3 days. As part of AITECH Cloud Network’s ongoing supply management framework, a defined amount of ACN will be permanently removed from circulation through a fully transparent and verifiable on-chain burn.
Metacade
MetacadeMCADE #1306
Telegram
29 May 2026, 11:56
Metacade Update. It's not a short one but needed to be said. 🤝
Metacade Update. It's not a short one but needed to be said.
Metacade Update. It's not a short one but needed to be said. 🤝
Shido
ShidoSHIDO #9225
Telegram
29 May 2026, 11:48
telegram news 29 May 2026 11:48
https://x.com/ShidoNetwork/status/2060327291729625357?s=20