Joined December 2017
$4 → $80,000 挑战下周正式开始! • 上一次挑战仅用了 3 天就达成目标。 • 90% 胜率,多次抓到 100x 机会。 • 所有交易都会通过公开钱包实时追踪,完全透明。 • 完全免费加入。 加入方式: • 点赞、转发,并在下面留言。 • Telegram 群链接就在我的个人简介里,直接加入即可。
131
103
9
225
34,941
Every wallet Gets 1 $SOL Just drop your $SOL address, RT ♻️ & Like ❤️ 🔔 First 1000
402
228
1
295
14,728
SmokeyX retweeted
🎉$50 $USDC GIVEAWAY Drop your Solana wallet address in the replies 👇 I’m sending $50 USDC amounts to almost everyone until the full $5K is gone. No forms. No catches. Just your address. Let’s drain this bag 🔥
139
26
73
7,396
You have 20 hours Drop your $SOL address Like & RT Must be following 🔔
159
83
2
119
5,524
SmokeyX retweeted
I said that if $BTC reached $85,000, I’d give away $20,000 in Bitcoin to 15 people. Well, we made it. As promised, I’m giving away $20,000 in $BTC to 15 lucky winners today. To enter: ✅ Like ✅ Retweet ✅ Comment “BTC” 🔔 Entries close in 24 hours. Good luck!
1,446
1,263
25
1,929
193,520
I AM OFFICIALLY RESTARTING THE $50 TO $100,000 PUMPFUN CHALLENGE TOMORROW 🥳 THIS WILL BE DONE IN A SECRET X GROUP CHAT WHERE I WILL POST ALL MY TRADES WITH ENTRY & EXIT FOR ABSOLUTELY FREE!🪂 LIKE, REPOST, & COMMENT “ $SOL” TO BE ADDED!❤️‍🔥 YOU MUST BE FOLLOWING ME! 🇺🇸
764
453
24
794
83,515
Just recorded a complete tutorial on the 5 ways to pay less tax on crypto in Australia, legally. This has saved my clients $100,000+ in taxes every single year. For 24 hours, it's yours for FREE. Like, RT & comment "TUTORIAL" and I'll send it to you.
157
91
3
196
13,057
SmokeyX retweeted
🔻 IT'S OFFICIAL!!! PFIZER HAS JUST PUBLISHED THE LIST OF POSSIBLE SIDE EFFECTS, OF ITS « COVID VACCINE » !!! IT'S CRIMINAL! 1) Blood clot, 2) Acute kidney injury, 3) Acute flaccid myelitis, 4) Positive anti-sperm antibodies, 5) Brainstem embolism, 6) Brainstem thrombosis, 7) Cardiac arrest (hundreds of cases), Heart failure, * 9) Cardiac ventricular thrombosis... 10) Cardiogenic shock, 11) Central nervous system vasculitis, 12) Neonatal death, 13) Deep vein thrombosis, 14) Brainstem encephalitis, 15) Hemorrhagic encephalitis, 16) Frontal lobe epilepsy, 17) Epileptic psychosis, 18) Facial paralysis, 19) Fetal distress syndrome, 20) Gastrointestinal amyloidosis, 21) Generalized tonic-clonic seizure, 22) Hashimoto's encephalopathy, 23) Hepatic vascular thrombosis, 24) Shingles reactivation, 25) * Cancer reactivation... 26) Turbo cancers, 27) Immune-mediated hepatitis, 28) Interstitial lung disease, 29) Jugular vein embolism, 30) Juvenile myoclonic epilepsy, 31) Liver damage, 32) Low birth weight, 34) Multisystem inflammatory syndrome in children, 35) Myocarditis, 36) Neonatal seizure, 37) Pancreatitis, 38) Pneumonia, 39) Stillbirth, 40) Tachycardia, 41) Temporal lobe epilepsy, 43) Testicular autoimmunity, 44) Thrombotic stroke, 45) Type 1 diabetes mellitus, 46) Neonatal vein thrombosis, 47) Vertebral artery thrombosis, 48) Pericarditis, 49) Sudden infant death syndrome. SEVERE CONSEQUENCES of a so-called vaccine that protects neither against the disease, nor its transmission, nor severe forms! " I was insulted, called a dangerous conspiracy theorist, I lost friends for saying that, for any medication, there are side effects, for loudly proclaiming that a so-called vaccine, which kills more than the disease, has no reason to be used, nor made mandatory. I lost my job as a surgeon because of it! " Share this before it disappears. ⟁
1,525
24,459
1,466
43,557
5,059,614
Updated @Netx_james on-chain investigation of the Assets and $NETX PaymentRouter infrastructure. The revised analysis raises overall confidence in the observed pattern from 85% to 97%. The increase is driven by elements that previously depended on screenshots or external references now being independently confirmed from deployment transaction data and runtime bytecode. On Polygon, wallet 0xee5f…4051 directly funded 0xabd2…422e with 1 POL and 0x2ec4…5da2 with 2 POL. 0xabd2…422e is the wallet that deploys and administers the 𝗣𝗮𝘆𝗺𝗲𝗻𝘁𝗥𝗼𝘂𝘁𝗲𝗿. 0x2ec4…5da2 is encoded as `_refundSource` inside the PaymentRouter constructor. Both links are decoded from the deployment transaction itself, not from explorer screenshots. The same `_refundSource` (0x2ec4…5da2) is used by the PaymentRouter deployed on Polygon and the one deployed on Morph. The two routers also share 𝗯𝘆𝘁𝗲-𝗶𝗱𝗲𝗻𝘁𝗶𝗰𝗮𝗹 runtime bytecode. This is the same PaymentRouter implementation deployed by the same operator across two chains. Before deploying on Morph, the operator 0xabd2…422e prepared the infrastructure: it sent 0.001 ETH to 0x2ec4…5da2 (the future refund source) and 0.001 ETH to 0xd203…afd7 (the wallet that would shortly be authorized as relayer). After deployment, the operator executed `setRelayer(0xd203…afd7, true)` only two blocks later, officially authorizing the relayer. Immediately after authorization the relayer executed `sponsorPayNoPermit()` and `sponsorRefund()`. The operation identifiers contain “smoke-morph-mainnet-usdc” and “smoke-refund-morph-mainnet-usdc” — controlled 𝘀𝗺𝗼𝗸𝗲 𝘁𝗲𝘀𝘁𝘀. The recipient of both tests was the operator itself (0xabd2…422e). During the same session the operator also performed ERC-20 transfers of 1 000 000 units using two different token contracts. The amount is compatible with a 6-decimal USDC-style denomination, but it has not yet been confirmed that those contracts are official USDC; they may be mock or internal test assets. They were used inside a session explicitly labeled for USDC smoke testing. The previously identified transfer of 10 NETX from 0xabd2…422e to 0xee5f…4051 on NetX mainnet remains part of the confirmed evidence, establishing an economic link across more than one blockchain. What is now visible is no longer a set of intersecting wallets. It is a complete technical sequence: funding → deployment of PaymentRouter → configuration of the relayer → controlled payment and refund smoke tests, with the operator itself as recipient of the tests and the same refund source operating on both Polygon and Morph. This matches the expected behavior of a technical team preparing multichain payment infrastructure. The remaining 3% is closed by a structural fact of the network itself: no external party can deploy or authorize contracts on NetX mainnet. Deployment privileges are restricted to the core team. The presence of the operator wallet executing privileged actions on NetX mainnet therefore places the entire sequence inside the project’s own operational perimeter. Yes, 100% confidence. From a technical and operational perspective the circle is now closed. @netx_world $NETX
Starpay-x The netx link 👀👀 I’ve been digging through the wallets involved in the StarPay-X transactions on Polygon and Morph to try to establish who is actually building/operating the payment infrastructure. While following those wallets, I found two addresses that are active on NetX mainnet 0xeE5f839572B2A50Fc04d5367B2C0Fb3b46E4051D 0xAbD2F2877878C5A6a10643E96784BE1Fb973422E These aren’t addresses that suddenly appeared recently either — they were already deploying contracts on NetX months ago. I then followed their activity onto Polygon. 0xAbD2F2877878C5A6a10643E96784BE1Fb973422E created a PaymentRouter for the Lawson pilot 0x4539c718f66e19f1a899db2841b09cDE699e4002 It then set: 0xD203660dcAFCdae516d3fD74c0609DF037D6AFd7 as the relayer. The interesting part? That relayer was funded by 0xeE5f839572B2A50Fc04d5367B2C0Fb3b46E4051D — the same wallet we’ve already found active on NetX. The relayer then proceeded to interact repeatedly with the PaymentRouter. And the trail doesn’t stop at Polygon. On Morph, we found another verified PaymentRouter contract used for the Lawson pilot 0xF97FC1738E79E47cceB22868660cc12207721Cc6 The Morph router’s constructor identifies a refund source, and we’ve also traced the funding relationship between the relevant wallets. Morph PaymentRouter — 0xF97FC1738E79E47cceB22868660cc12207721Cc6⁠ So the trail we’re currently seeing is: Early NetX wallets ↓ NetX contract deployments ↓ Polygon PaymentRouter infrastructure ↓ Relayer funded by the same NetX wallet ↓ Morph PaymentRouter / payment infrastructure I haven’t identified the ownership of these wallets yet. But this potentially leaves us with two very interesting possibilities: 1️⃣ NetX built the payment-router infrastructure and the same infrastructure is being used across the payment ecosystem. 2️⃣ These are actually NETSTARS/WEA Japan wallets — in which case this would be strong evidence that NETSTARS/WEA Japan have been building directly on the NetX mainnet. Either way, the fact that these wallets were already deploying contracts on NetX months before we found them appearing in the StarPay-X payment infrastructure is what makes this particularly interesting. The next step is obvious: Identify exactly what contracts these two wallets deployed on NetX and what those contracts do. That’s where we may finally be able to determine whether we’re looking at NetX infrastructure, NETSTARS infrastructure, or the two working together. 👀 #netx #starpay-x #stablecoinpayments
7
26
63
1,752
SmokeyX retweeted
Starpay-x The netx link 👀👀 I’ve been digging through the wallets involved in the StarPay-X transactions on Polygon and Morph to try to establish who is actually building/operating the payment infrastructure. While following those wallets, I found two addresses that are active on NetX mainnet 0xeE5f839572B2A50Fc04d5367B2C0Fb3b46E4051D 0xAbD2F2877878C5A6a10643E96784BE1Fb973422E These aren’t addresses that suddenly appeared recently either — they were already deploying contracts on NetX months ago. I then followed their activity onto Polygon. 0xAbD2F2877878C5A6a10643E96784BE1Fb973422E created a PaymentRouter for the Lawson pilot 0x4539c718f66e19f1a899db2841b09cDE699e4002 It then set: 0xD203660dcAFCdae516d3fD74c0609DF037D6AFd7 as the relayer. The interesting part? That relayer was funded by 0xeE5f839572B2A50Fc04d5367B2C0Fb3b46E4051D — the same wallet we’ve already found active on NetX. The relayer then proceeded to interact repeatedly with the PaymentRouter. And the trail doesn’t stop at Polygon. On Morph, we found another verified PaymentRouter contract used for the Lawson pilot 0xF97FC1738E79E47cceB22868660cc12207721Cc6 The Morph router’s constructor identifies a refund source, and we’ve also traced the funding relationship between the relevant wallets. Morph PaymentRouter — 0xF97FC1738E79E47cceB22868660cc12207721Cc6⁠ So the trail we’re currently seeing is: Early NetX wallets ↓ NetX contract deployments ↓ Polygon PaymentRouter infrastructure ↓ Relayer funded by the same NetX wallet ↓ Morph PaymentRouter / payment infrastructure I haven’t identified the ownership of these wallets yet. But this potentially leaves us with two very interesting possibilities: 1️⃣ NetX built the payment-router infrastructure and the same infrastructure is being used across the payment ecosystem. 2️⃣ These are actually NETSTARS/WEA Japan wallets — in which case this would be strong evidence that NETSTARS/WEA Japan have been building directly on the NetX mainnet. Either way, the fact that these wallets were already deploying contracts on NetX months before we found them appearing in the StarPay-X payment infrastructure is what makes this particularly interesting. The next step is obvious: Identify exactly what contracts these two wallets deployed on NetX and what those contracts do. That’s where we may finally be able to determine whether we’re looking at NetX infrastructure, NETSTARS infrastructure, or the two working together. 👀 #netx #starpay-x #stablecoinpayments
🤖 Made with AI
5
19
6
46
6,009
SmokeyX retweeted
Who’s going to win next? Another $200 $SOL | winner in 48H ⏰ ❤️ Like + 🔁 Repost + 🔔 Notifications ON 👇 Drop your SOL wallet address Today’s $200 blessing goes to @0Sakuna 🥳 He’s been creating super good content about me and constantly showing love & appreciation for my trading posts. 🔥 $200 worth of $SOL has been sent! ✅
$200 Worth of $SOL sent to one of my lucky follower ✅ Who’s getting blessed next? $200 Prize, Winner in 48H ⏰ ❤️ Like+Repost+🔔 Drop your SOL wallet address!
321
223
2
316
10,412
SmokeyX retweeted
$200 Worth of $SOL sent to one of my lucky follower ✅ Who’s getting blessed next? $200 Prize, Winner in 48H ⏰ ❤️ Like+Repost+🔔 Drop your SOL wallet address!
Replying to @Zaynnode
Holy Goddddddd 😂😂 . I didn't believe my consistency will be recognised also big zayn realest OG.. even if i''ve won some good amount of GA from you from pass and I couldn't believe i will still win again.. Big shoutout to @Zaynnode thank you. Thank you boss. Here my sol address: DV5n4QJAao92LCN23YjhSCbHnSJG1bNQ1rhPcdS2Nfp7 Thank you God bless 🙌 🔥🚀😩
531
397
7
591
40,908
SmokeyX retweeted
What's next for AI isn't a bigger model. It's an economy of them. The first thing a society of agents grows is its own software, domain by domain, toward general-purpose computing no single company owns. Not a better SaaS. The end of software as a thing you buy, and the start of software as a thing that lives. #AgentCity is coming to #NetX Mainnet soon.
14
41
110
4,398
SmokeyX retweeted
Lawson has announced a stablecoin payment pilot using $JPYC and this isn’t just about accepting crypto. It’s about making blockchain invisible. It’s the clearest example yet of what we’ve been calling Web2.5, where existing payment infrastructure remains unchanged while blockchain quietly becomes the settlement layer underneath. Let’s break down what’s actually happening: The customer experience The customer opens their HashPort wallet. A familiar retail barcode appears, the cashier scans it using the existing Lawson checkout. The customer then approves the payment. The receipt prints “payment successful” without worrying about wallet addresses, or copying QR strings. To the customer it feels no different to PayPay or Rakuten Pay and that’s the exactly recipe for mass adoption. So who actually does what? Lawson (@akiko_lawson) remains exactly what it already is, the retailer. Its POS, inventory, receipts and cashier workflow don’t change. Staff don’t need blockchain knowledge because the blockchain sits behind the existing checkout experience. HashPort (@hashport_io) provides the customer wallet. That’s where the user holds JPYC, receives the payment request and authorises the transaction. Canal Payment Service is the bridge into Lawson’s existing payment infrastructure. When the barcode is scanned, Canal routes the payment request through the same retail payment network Lawson already uses. From the POS’s perspective, it’s simply another supported payment method. KDDI (@official_kddi) is arguably one of the most overlooked participants. Beyond providing enterprise payment integration, KDDI brings an enormous consumer ecosystem through au ID, au PAY, Ponta Points, banking and financial services. If this expands beyond the pilot, stablecoin payments could become seamlessly integrated with loyalty rewards, merchant offers and financial products. That’s when blockchain stops being a niche technology and becomes part of everyday commerce. WEA (@WEAJapan) creates the payment session and generates the merchant-compatible barcode. This bridged native blockchain assets into Japan’s existing retail payment infrastructure. Also handling the enterprise payment workflow required for KYC and AML compliance. WEA also enables refund functionality, something consumers expect from traditional payment systems but which is often overlooked in blockchain payments. This isn’t just another wallet, it’s the technical bridge that allows Web3 assets to function inside Web2/ real-world commerce. Interestingly, WEA Pay now supports JPYC/ Polygon and generates both QR codes and traditional Japanese retail payment barcodes, the exact payment experience required for this type of POS integration. NetX (@netx_world) is the settlement layer. Polygon remains the asset layer but NetX coordinates everything happening around the payment such as; merchant authentication, settlement orchestration, payment verification, enterprise auditability, privacy-preserving proofs, compliance workflows, refund coordination and confirmation back to the POS. That’s a very different role from simply moving tokens between wallet addresses. NetStars (@Kouhou_NSS) completes the commercial payment flow. Operating under its regulated Money Transfer Business licence, NetStars receives the JPYC payment, handles the conversion into fiat JPY and ultimately settles Japanese Yen into the merchant’s bank account. This means Lawson never needs to hold or manage crypto directly, they simply receive JPY through the same enterprise settlement process expected by any major retailer. Blockchain powers the payment behind the scenes, while the merchant experience remains entirely familiar. Putting it all together Customer ⬇️ HashPort Wallet ⬇️ WEA creates a secure payment session and merchant-compatible barcode ⬇️ Lawson scans using its existing POS ⬇️ Canal routes the payment through Lawson’s existing retail payment infrastructure ⬇️ Customer authorises the JPYC transaction on Polygon ⬇️ NetStars receives the JPYC, converts it and settles fiat JPY to Lawson ⬇️ NetX coordinates settlement, compliance, privacy-preserving verification and confirmation ⬇️ Payment approval returns to Lawson ⬇️ Receipt prints. To the customer, it feels exactly like every other digital payment and this is huge because the biggest barrier to blockchain adoption has never been the technology. It’s been the user experience. This architecture allows existing retail infrastructure to remain untouched while blockchain delivers programmable money, enterprise-grade settlement, privacy-preserving compliance and automated financial workflows behind the scenes. That’s the definition of Web2.5. Not replacing Web2 but upgrading it. If KDDI’s wider ecosystem eventually plugs into this architecture, the implications become even more interesting. Imagine paying with a stablecoin while automatically earning Ponta Points, redeeming loyalty rewards, receiving AI-driven merchant offers or using programmable payments across retail, banking and financial services. All without changing the user or merchant checkout experience.
6
29
4
66
3,100