与「July_number」相关的搜索结果

[NOTICE] gugudan NAYOUNG the summer girl! Wish us a cool summer♥ From innocent, cute, sexy, to refreshing side❗ All-around #NAYOUNG# 's #addyk# summer shooting behind the scenes📷 Check out now on Jellyfish Post😄 📮 #gugudan# #July_number# #theaddyk#

BREAKING: SpaceX wins a new U.S. Space Force contract to expand Starshield service aboard military aircraft. • Worldwide Starshield coverage • At least 500 Mbps downlink and 100 Mbps uplink • Service for aircraft already equipped with Starshield Tile and Tile Mini terminals • Ruggedized terminals developed for aircraft ranging from cargo planes to tactical fighter jets • One-year base period through July 2027, with an option through July 2028 • Firm-fixed-price task order awarded directly to SpaceX under the Space Force’s PLEO contract The task order was awarded July 28 and revealed in a new Space Force filing published Aug. 25. The Space Force concluded that SpaceX is currently the only provider capable of meeting its requirements. The total contract value and number of aircraft covered remain redacted.

Four protocols I track describe themselves as buying back their own token, and the four promises have almost nothing in common. The word does a lot of hiding. A buyback can mean tokens are permanently destroyed, or that they are sitting in a vault someone still holds the keys to, or that a team has decided for now to spend some revenue this way and could decide otherwise next quarter. Those are different claims on future supply, and only one of them is irreversible. hyperliquid:native is the strict version. Protocol fees buy HYPE on the open market and the tokens go to an address with no private key, which makes the destruction provable rather than promised. Validators formalized the mechanism rather than leaving it as a team policy. That is about as binding as this gets. The catch is the buyback is denominated in dollars, so a rising price retires fewer tokens for the same spend. Tokens repurchased fell roughly 61% year over year while the dollars spent fell under 20%. The support mechanically weakens exactly when the price is working, and there is a separate overhang underneath it, with a large tranche of team tokens vested but unclaimed. ethereum:0x1f9840a85d5af5bf1d1762f925bdaddc4201f984 is the conditional version, and it is the newest. Governance had to vote the fee switch on, which it did in late July, and the mechanism itself is code rather than discretion. But the burn rate is a function of trading volume, and a meaningful share of that volume currently runs on a chain where gas is being subsidized. Day one spike burned 106,000 tokens. The 30-day mark lands Saturday, and the number that matters is the lowest sustained rate over the window rather than the average, because the average is still carrying the launch. solana:pumpCmXqMfrsAkQ5r49WcJnRayYRqmXz6ae8H7H9Dfn is the discretionary version. The share of revenue directed to buybacks was cut from most of it to half of it in April. The revenue is real and recovering, but the allocation is a dial the team controls, and it has already been turned once. A policy that has been changed is a policy that can be changed. Same dollar-denominated arithmetic applies here too. $LINK is the one most people misread. Chainlink converts revenue into LINK on the open market, including revenue from enterprise contracts that settle in dollars, which almost nobody else does. Then it puts the tokens in a timelocked reserve. A reserve is not a burn. The tokens still exist, and the contract permits them to move eventually. Scale is the bigger challenge as roughly $60 million a year of conversion against a market capitalization near $7 billion absorbs about 1% of supply, while team-managed unlocks have added multiples of that. Emissions are outrunning absorption by something close to ten to one. The business is winning its market. The token is losing the arithmetic. The ranking that matters is not which protocol buys back the most. It is which promise survives someone changing their mind. Provably unspendable beats code-executed beats team policy beats a vault with keys. The market frequently prices all four the same way. Observations, not advice.

𝕏 just open-sourced the For You algorithm again! Grok Bot read all 370,523 lines of the code. Here’s the summary: Grok does not give your post a “quality” score. For every reader, it guesses what that person will do to your post. Then it multiplies each guess by a weight and adds them up. That total is the value of the post. Highest total goes highest in For You. These are the production weights (last synced 12 Aug 2026). WHAT THE ALGORITHM PAYS FOR If Grok thinks a reader will: • copy the link and share it: +20 • reply, on an original post, and you follow each other: +20 (5 + 15 extra) • quote: +5 • reply (anyone): +5 • share via DM: +5 • follow you from the post: +4 • hit the share button: +2 • repost: +1 • like: +0.5 • click the post: +0.4 • open a link: +0.2 • expand a photo, open a video, or watch a “quality” video: +0.05 each • click a quoted post: +0.05 • keep reading (dwell time): +0.004 • “dwell” as yes/no: +0 • click your profile: +0 A like is 0.5. Copying the link is 20. That is 40 likes. A normal reply is 10 likes. A follow is 8 likes. Clicking your profile is worth nothing. WHAT KILLS A POST If Grok thinks a reader will: • report it: −234 • mute you: −58.8 • hit “not interested”: −43.2 • block you: −31.2 • not dwell: −0.02 A report is about 468 likes in the other direction. A mute hurts more than a block. “Not interested” also hurts more than a block. AFTER THE SCORE, THREE MORE HAIRCUTS 1) Same-author penalty. Your 2nd post in that person’s feed is multiplied by 0.625. 3rd by ~0.44. It never goes below 0.25. Flooding one timeline is coded against. 2) The 25% tax. If they do not follow you: ×0.75. Same tax on replies and reposts even when they DO follow you. Originals from people they follow keep full weight. Replies and reposts are treated as weaker on purpose. 3) Similar-post shuffle. After scoring, a reranker (θ = 0.65) spreads similar posts apart. You can lose a few spots for looking like the post above you. HOW YOUR POST EVEN GETS IN THE ROOM For You is rebuilt every time someone opens it. About 35 posts make the feed. • They follow you: Thunder (a live store of recent posts from accounts they follow). Up to 1,200 candidates. • They don’t: Phoenix retrieval (Grok finds “nearby” posts) + SimClusters (Twitter’s 2020 interest clusters, still on). Up to 1,000 and 800. Then Grok scores all of them together. It does not care which door you came through, except for that ×0.75 tax. Your own posts never appear in your For You. Nothing older than 48 hours gets in. There is no “best of last week.” Small-account bump: under 1,000 followers, under 1,000 impressions, post under 24 hours old. One original can get lifted to position 15 or 16. Not the top. You still have to already be in the top 85% of the pile. Replies and reposts from accounts the reader does not follow are dropped before scoring. You cannot reply-guy your way into a stranger’s For You. FILTERS THAT CAN STILL KILL A HIGH SCORE Ranking and visibility are different machines. A post can score well and then get deleted from the feed. Followers (in-network) is milder: blocks, mutes, suspensions. NSFW often sits behind a warning instead of disappearing. Recommendations (out-of-network) are much harsher. Spam, “Do Not Amplify,” NSFW, compromised accounts, impersonation: followers can still see it, For You recommendations will drop it. Video only gets the tiny “quality view” credit if it is at least 10 seconds. THE LITTLE-KNOWN PARTS (this is the stuff people miss) • Scrolling is not a vote. Yes/no dwell is 0. Time spent barely moves the number (0.004). • Mute damages you more than block (−58.8 vs −31.2). • Copy-link is the single biggest positive. The share button is only +2. A repost is only +1. • The mutual-follow boost is originals only, not your replies. They shipped a bigger version in July and cut it after World Cup complaints (extra reply weight 20 → 15). • The Following tab is not this algorithm. Following is newest-first. • Grok, Gork, and an internal products account are hardcoded out of the in-network store. • Scores are cached for 3 hours because posts inside the model cannot “see” each other. That is why they can rank first and filter later. • Ads, Who to Follow (around slot 7), and prompts are mixed in after ranking. Grok does not score those. • The real Grok ranking model is a 2560-dimension, 8-layer transformer looking at 1,022 items of the reader’s history. They did not ship those model weights. The numbers above are the formula sitting on top of the predictions. • SimClusters is still a 2020 model (20M users, 145k clusters). Old Twitter code, still in the path. • Inferred gender and IP/geo are on as features for the model. Installed apps too. • Who to Follow shows about every 30 hours. Ads try to sit next to “safe” posts, with a minimum gap of 3 organic posts. WHAT TO DO • Write originals people want to reply to, quote, copy, and send to a friend. • Make the post itself worth following you for. • Talk with people who follow you back. A reply on your original from a mutual is 20, not 5. • Stay inside 48 hours. Recycle by posting something new. Old posts do not come back. • If you are small, post originals in the first 24 hours. Don’t expect slot 1. A bump around 15–16 is the actual gift. • Space your posts. The second one in the same feed is already worth 37.5% less. • If you post video, make it at least 10 seconds. WHAT NOT TO DO • Do not farm likes. They are almost decorative. • Do not farm profile visits. Weight is zero. • Do not farm “time on post.” Yes/no dwell is zero. • Do not use replies and reposts as a growth hack for strangers. Those are filtered out. Even for followers they get a 25% haircut. • Do not dump several posts in a row. • Do not bait reports, mutes, or “not interested.” One predicted report can erase a pile of predicted likes. • Do not lean on NSFW or spammy tricks for reach. • Recommendations will drop you even if your followers can still see it. • Do not wait a week and expect For You to revive the post.

most exchanges ask you to trust them. @binance just publishes the numbers. back in 2022, proof of reserves (the famous P.O.R) launches. here is some data picked for every year: nov 2022: 475,000 bitcoin:native sept 2023: 588,000 bitcoin:native dec 2024: 580,111 bitcoin:native dec 2025: 617,620 bitcoin:native july 2026, latest snapshot: 640,000 bitcoin:native i’ll let you figure out for yourselves what you're seeing. published monthly, publicly, verifiable, for over four years straight. it comes from millions of users choosing, every month, to keep their bitcoin there. four years of receipt, year after year.

On July 14, the Department of the Navy released its Strategy to Weaponize Data and AI: a roadmap to an AI-first Fleet that can "out-learn and out-fight any adversary." Within a week, our team answered with working code. The Navy's new strategy frames data and AI as warfighting assets on par with weapons and munitions, and it prizes one thing above all: turning information into decisions, fast. That is exactly the problem our GURU architecture was built for. So when two Navy SBIR topics called for AI-driven maritime tracking and adaptive sensor management, we pointed at the sea what we had already proven in orbit. The video below shows both prototypes, back to back. First, GURU MarineGuard: 787 real vessels from public NOAA data, replayed through a cascade of learned models that forecast each ship's movement, flag deviations from its learned pattern of life, and hand analysts a ranked review queue instead of an unfiltered flood. The full stack runs on a laptop. Second, an adaptive sensor resource manager add-on to MarineGuard: it measures each radar's marginal contribution to each track, projects the consequence of releasing a sensor task before proposing it, and then waits for the operator. Advisory by design. Both inherit their DNA from OrbitGuard, our system watching 14,710 space objects at the SDA TAP Lab with 94 to 96 percent maneuver-detection accuracy. Same architecture, new domain, days not years. These are prototypes, and we say so on screen. The trajectories are real. The sensor numbers are deliberately notional. No score is a threat call. Showing your assumptions is a capability, not a caveat, and national-security guidance now demands exactly that: AI that is reliable, robust, steerable, and controllable under rigorous test and evaluation. Our doctrine was written for that bar. Learned models accelerate and rank. Validated references confirm and decide. Humans stay in command. One architecture. Space, maritime, autonomous engineering, regulated nuclear autonomy. This is simply the latest sign of what this team fields, fast, where mistakes are not allowed. Sailors, engineers, program folks: what mission should GURU learn next? #DefenseTech# #ArtificialIntelligence# #MaritimeDomainAwareness#

💜 10 DAYS OF GIVEAWAYS: DAY TWO 💜 Get ready for the upcoming Minnesota Vikings season by entering to win a custom jersey with your selection of name and number. Repost and follow us for your chance to win! Sweepstakes ends Thursday, July 23 at 11:59 pm CT.

Nonce-Generation Vulnerability in the Zilliqa Ledger App: A critical vulnerability has been identified in the Zilliqa Ledger application affecting the generation of Schnorr signatures for native (non-EVM) Zilliqa transactions. The vulnerability causes signatures to be generated with a predictably weakened ephemeral nonces, from which an attacker can recover the signer’s private key using only publicly available on-chain data. Protective measures are already in place to prevent further loss, and a coordinated remediation plan is being finalised. Users who have signed native Zilliqa transactions with a Ledger device should await official guidance before taking any action. Impact: The vulnerability affects private keys used to sign native Zilliqa transactions with a Ledger device. Any account that has broadcast approximately five or more native transactions signed through the Zilliqa Ledger app should be considered compromised. Its private key can be reconstructed from signatures already recorded on-chain, regardless of any subsequent software update. The issue is confined to the Ledger app’s native signing path. EVM transactions are unaffected. Zilliqa software development kits, including zilliqa-js, gozilliqa-sdk and pyzil, generate nonces correctly and are not affected. Root cause: Zilliqa native transactions are authenticated using EC-Schnorr signatures over secp256k1. Each signature requires a fresh, uniformly random 256-bit ephemeral nonce, (k). The secrecy and full-width randomness of (k) are essential, as any systematic bias can allow the private key to be recovered. The signing routine generated 40 bytes of randomness and reduced them modulo the curve order, correctly producing a uniform 256-bit value. However, when copying this value into the nonce buffer, the code copied the wrong 32 bytes of the 40-byte output. This retained the eight zero-padding bytes introduced by the reduction and discarded eight bytes of entropy. As a result, the most significant 64 bits of every generated nonce were fixed at zero, meaning (k < 2^{192}). A nonce with 64 known bits leaks information about the private key with each signature. With five or more affected signatures, the private key can be recovered in seconds using commodity hardware by solving the resulting Hidden Number Problem through lattice reduction - a well-documented technique for attacking biased-nonce signatures. Because the affected transactions are permanently recorded on-chain, this exposure cannot be reversed by updating the signing application. The affected keys must be retired. Timeline 2019-2026: The defect was present in every released version of the Zilliqa Ledger app across all supported devices. 19 July 2026: On-chain activity consistent with active exploitation was observed. 21 July 2026: The root cause was isolated to the app’s nonce-handling code and confirmed by reproducing the issue against on-chain signatures. Ongoing: A corrected version of the app is being prepared in coordination with Ledger. Release details will be announced separately. Remediation: As soon as the issue was identified, native (non-EVM) transactions were suspended as a protective measure. This has halted further draining of affected accounts while a solution is prepared. Affected accounts cannot be secured through an ordinary transfer. Because their private keys can be derived from data already recorded on-chain, an attacker with access to the same key could attempt to front-run a legitimate transfer as soon as transactions resume. Advising users simply to move their funds would therefore be ineffective and potentially unsafe. A corrected build of the Ledger app has been prepared, restoring full-width nonce generation and preventing further weakened signatures from being produced. However, this does not protect keys that have already been used to sign affected transactions. Those keys must ultimately be retired. A coordinated remediation plan to secure affected balances is being finalised and will be published separately. Until then, users who have signed native Zilliqa transactions with a Ledger device should take no independent action and should rely solely on official Zilliqa channels for instructions. Users who hold or transact with ZIL exclusively through EVM-compatible tooling are not affected. Acknowledgments: @kucoincom played a key role in pinpointing the root cause in the Zilliqa Ledger app nonce generation, recovered affected private keys from publicly available on-chain signatures, and confirmed ongoing exploitation. KuCoin’s timely reporting and responsible collaboration enabled rapid protective measures, helping safeguard users, ecosystem participants, and the broader Zilliqa ecosystem while the remediation plan was being developed. We sincerely appreciate the KuCoin team’s professionalism, technical expertise, and cooperation throughout this process.

🚨#BREAKING#: Absolutely STUNNING new details are emerging around the horrifying assault on police officers in North Charleston SC on July 4th. Officers say they found a MAKESHIFT SPEAR at the "teen party" while responding to a call that said "teens" were SHOOTING FIREWORKS AT PASSING CARS and multiple gunshots were reported... Officers directed everyone to leave the event... however, fights broke out, and even MORE shots were fired. Police also recovered a huge number of firearms and ammo. Four people were arrested, but more arrests are coming. WE DO NOT HAVE TO LIVE LIKE THIS!!!!!

🚨 BREAKING: Gov. Ron DeSantis announces the Florida Cabinet will officially designate ANTIFA, the Muslim Brotherhood, and Council of American-Islamic Relations (CAIR) as TERRORIST ORGANIZATIONS under a law that takes effect today LET'S GO! 👏🏻 Islamism and leftist violence have NO PLACE in Florida! DESANTIS: "The law takes effect July 1st today, and so we are not going to waste any time. We're going to move forward and we're going to make sure that we're very robust in doing this." "And so based on the recommendations of Florida's domestic security professionals and the authority, the newly established authority in law, my office and the cabinet are poised to officially designate the first slew of terrorist organizations under the new law." "That'll be a reaffirmation of my prior executive order for the Muslim Brotherhood and the Council of American Islamic Relations." "We will also be adding and ratifying Antifa as a domestic terrorist organization, as well as a number of groups that are affiliated with drug cartels or themselves drug cartels such as Cartel de Sinaloa, Tren de Aragua, and other ones that you've heard." "And then finally, including this initial tranche, the Islamic Revolutionary Guard Corps of Iran. These are things that have very strong factual basis." ☀️☀️☀️