Загрузка видео...

Не удалось загрузить видео

На главную

Kaspa's Toccata upgrade is seeing real use seven weeks after activation Seven weeks after Kaspa's Toccata hard fork, the upgrade's new machinery is in visible use. Kaspalytics counts 1,196 covenant-creating transactions in the past 24 hours, with over 2,700 covenant outputs created, programmable spending rules now running natively on...

17,989 просмотров • 5 дней назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

ZK Stack is a modular framework for building sovereign ZK-powered hyperchains, based on zkSync Era’s open source code. ➡️ Visit the new ZK Stack resource page: ZK Stack gives builders full sovereignty, ranging from the choice of the data availability mode to using your project's own token to decentralize the sequencer. ✅ Mature and battle-tested ZK Stack is the most battle-tested framework, ensuring all transactions are fully verified by Ethereum with the power of ZK proofs. ZK enables validity proofs to ensure the hyperchains' ecosystem state can't be corrupted and invalid transactions can't exist. ZK Stack has been further strengthened by $5M+ invested in audits, $~30M transactions-per-month and ~250k daily active users. ✅ Tailored to your needs ZK Stack grants you full autonomy to tailor your blockchain to cater to your product or protocol use case. A modular stack of ZK-powered components. ✅ Ready for mainstream adoption No matter how much adoption grows, ZK Stack brings the power of horizontal scalability to Ethereum. Just like adding more servers to address specific needs on the Internet, a boundless amount of hyperchains can be created with minimal costs. ZK tech, combined with our state diffs and data-compression approaches, unlocks: 📌 Flat fees regardless of gas price 📌 Privacy by default 📌 Cheap oracles (or any high-frequency protocol) 📌 Ultra low cost Validium accounts 📌 UX magic with native account abstraction ✅ Seamless access to users and liquidity Hyperchains are seamlessly interconnected with hyperbridges — the native and trustless communication protocol of the ZK Stack. It enables any chain to natively exchange messages and transfer value with any other chain, thus tapping into the users and liquidity of the entire hyperchain ecosystem. Unlike classic, centralized, bridges, hyperbridges rely solely on cryptography for security. ✅ Built today, to last forever ZK Stack is rooted in the long-term vision of Ethereum, aiming for subtraction and decentralization. Abiding by the ZK Credo principles, an alliance of developers and maintainers will guarantee the resources enabling this fully open source framework to evolve to onboard the needs of the next billion users.

ZKsync

317,602 просмотров • 2 лет назад

Dagknight technical progress As would be mentioned in a still unshared post by Michael Sutton, the dagknight effort is split into v0 devnet, v1 testnet and v2 mainnet candidate. I’ve been testing the current v0-based implementation in a small devnet with the help of some testers who run nodes and miners with me. The DK work can be thought of as split into two parts: (1) implementing the actual protocol and (2) wiring it up and using it. The testing and development over the last month has been focused on (2). Obviously, DK is a consensus change for selecting parents. What’s not so obvious is that such a change affects DAA, coinbase, IBD, pruning and a lot more. Each of these areas is very sensitive and requires proper understanding to wire correctly. An important consideration and difference from GD is that DK does not focus on maximizing a property like blue work. So to maintain topological properties of blue work, an independent (free) GD implementation is kept running specifically for maintaining blue work. This allows us to keep using the property for topology. Coloring and blue score use the megachain induced by DK. The wiring around DK as of this posting is in a working state, but still needs to be reviewed. Next efforts will be focused on protocol specific components, particularly Tie-Breaking and incremental UMC. Attached are some captures from the internal devnet. The dense DAG image is what happens when things related to DAA or other similar consensus parameter causes a node to insist on their POV. The video is a recent snippet of the KGI running on the devnet showing (perhaps not obviously) DK at work. The current “dagknight” branch is now posted on the main repo. A topic in the Public R&D has been opened for Dagknight development.

coderofstuff

52,857 просмотров • 5 месяцев назад

Say hello to Boojum 👋: zkSync Era’s new high-performance proof system for radical decentralization. Boojum is an upgrade that will transition zkSync Era to a STARK-powered proof system, providing world-class performance on consumer-grade hardware. 💡 Learn more: TL;DR 👇 Boojum is the name of our Rust-based cryptographic library, which we use to implement the upgraded version of the ZK circuits for zkSync Era and the ZK Stack. The name Boojum was inspired by Lewis Carroll's poem "The Hunting of the Snark," where the Boojum represents the most fearsome kind of Snark. We intentionally designed zkSync Era in a way that cryptographic upgrades can be made without a regenesis, meaning that the Boojum upgrade won’t cause any user disruptions. Why Boojum❓ From day one, zkSync’s mission is to advance personal freedom for all — making digital self-ownership universally accessible by building a blockchain network that is trustless, secure, permissionless, affordable, easy to use, resilient and limitlessly scalable. Boojum plays an important role in advancing this mission by delivering: 1. World-class performance zkSync Era’s current SNARK-based proof system is effective today, but it won’t scale to the volume that we envision for hyperchains. zkSync Era’s sequencer can already process over 100 TPS; Boojum orders of magnitude improvements to performance complements this well. 2. Reduced hardware requirements for decentralization Our long-term goal is to enable user-powered, decentralized proof generation. Boojum represents a breakthrough in this direction — with the prover running on consumer-grade GPUs requiring only 16 GB GPU RAM. Boojum’s Journey to Mainnet 🚴🏽‍♀️ Boojum is now live on Mainnet, generating and verifying ‘shadow proofs’ today with real production data so that we can carefully test the system ahead of fully migrating. Today, we’re also open-sourcing the repo; if you’d like to take a look, you can find it here 👇 This is the first of a series of posts on Boojum. We will provide updates on our progress, including more details on implementation, security, and performance. Watch here for more, anon ∎

ZKsync

827,349 просмотров • 3 лет назад

A robot just pulled two American pilots out of the sea near the Strait of Hormuz. It was the first time an autonomous sea drone has rescued people in a combat zone, and the war it happened in escalated within hours. The confirmed part is genuinely remarkable. After a US Army Apache went down off Oman, the two crew spent about two hours in the water until a 24-foot Saronic Corsair, an unmanned vessel run by the Navy’s Task Force 59, found them and carried them to a helicopter hoist. No human rescue crew exposed, no second aircraft risked. Both pilots are safe. It is a real leap in how the US fights. Then events moved faster than the evidence. Trump announced that Iran shot the helicopter down and that the US must respond. By 5 p.m. ET, CENTCOM was striking Iranian targets and calling it a proportional answer to unjustified Iranian aggression. Iran fired back overnight. No deaths have been reported on either side. But the cause of the crash is not yet established. Washington says Iran shot it down. Tehran denies it, has claimed no responsibility, and points to an accident or a collision in a crowded, contested waterway. The evidence has not been released. That gap is everything, because a deal was nearly done. A 60-day ceasefire extension and the reopening of the strait were days from signing. One disputed incident has now pulled American and Iranian forces back to trading fire over the same water. This is how fragile truces die. Not on a clear decision, but on a murky incident that hardens into certainty before the facts are in.

Shanaka Anslem Perera ⚡

185,542 просмотров • 2 месяцев назад

🚨 ANNOUNCEMENT: STABLECOINS ARE LIVE ON Meow. SEND AND RECEIVE USDC, FOR FREE, ALL FROM YOUR EXISTING CASH BALANCE! Now on Meow, you can send and receive USDC for free. All from your existing cash balance. That's right: the days of needing to pre-fund, maintain, and log in to a crypto exchange just to send and receive USDC are over, permanently. The SAME balance that you use for ALL your business finances, payroll, and corporate cards — is the one you can now use to send and receive USDC. This has huge ramifications for: — Crypto companies: that transact in USDC — Crypto VCs: who fund investments in USDC — Businesses: that receive vendor payments in USDC, and pay contractors internationally And the best part? These USDC transactions integrate natively with your accounting software, like QuickBooks, NetSuite, Puzzle, and more. And if that’s not enough? You can set up: — Custom spend controls, per dollar amount — Multi-user permissions And 2FA is enforced on every transaction This is one of our MOST REQUESTED FEATURES and we believe Meow is the first major business banking fintech in the U.S. (over $1 billion in assets on the platform) to support free sending and receiving USDC. Business finance is business finance, whether it's cash or stablecoins. The "bridge between Web2 and Web3" is finally here, for real. No more maintaining separate accounts at crypto exchanges for businesses. Crypto companies and crypto funds, apply today: Meow is a financial technology company, not a bank. Bridge is a licensed Money Services Business operating out of the United States.

Brandon Arvanaghi

126,571 просмотров • 1 год назад

This Chinese developer launched Llama 70B locally on a MacBook on a plane and for a full 11 hours without internet ran client projects. He was sitting by the window on a transatlantic flight with a MacBook Pro M4 with 64 GB of memory. WiFi on board cost $25 for the flight. He declined. No cloud API, no connection to Anthropic or OpenAI servers, no internet at all. Just a local Llama 3.3 70B on bf16 and his own orchestrator script. The model runs through llama.cpp. Generation speed, 71 tokens per second. Context around 60,000 tokens. Memory usage, 48.6 GiB out of 64. Battery at takeoff, 3 hours 21 minutes. And he gave the orchestrator this system prompt before takeoff: "You are an offline orchestrator running on a single MacBook. There is no network. The only resources you have are local files in /Users/dev/work, the Llama 70B inference server at localhost:8080, and a battery budget of 3 hours 21 minutes. Process the queue at /Users/dev/work/queue.jsonl (one client task per line). For each task: draft → run local evals → save artefact to /Users/dev/work/done/. Save context checkpoints every 12 tasks so you can resume after a battery swap. Stop only on empty queue or when battery drops below 5%." So the system knows exactly what resources it is running on. It knows it has no connection to the outside world for the next 11 hours. It knows it has finite memory and a finite battery. It knows the human will not intervene until the plane lands. The system runs in 1 loop. Takes a task from the queue, runs it through inference, saves the artifact, writes a checkpoint. Task after task, just like that. And only when the battery drops below 5% does the orchestrator automatically pause, waits for the laptop to switch to the backup power bank, and continues from the last checkpoint. Here is what the system actually writes in his log during the flight: "saved context checkpoint 8 of 12 (pos_min = 488, pos_max = 50118, size = 62.813 MiB)" "restored context checkpoint (pos_min = 488, pos_max = 50118)" "prompt processing progress: n_tokens = 50 / 60 818" "task 37016 done | tps = 71 s tokens text → /Users/dev/work/done/proposal_westside.md" Outside the window, clouds, blue sky, and no WiFi. On the tray, 1 MacBook, an open terminal on 2 screens, and an inference server on localhost. From what I have observed, this is the cleanest offline AI workflow I have seen in the past year: 11 hours of flight, $0 for WiFi, and the entire client queue closed before landing.

Blaze

1,841,161 просмотров • 3 месяцев назад

Category Labs is proud to introduce Cadence, our multiple-concurrent-proposers (MCP) consensus protocol that matches the optimal good-case latency of single-leader consensus while supporting arbitrarily short block intervals. When combined with BTX, our design for encrypted mempools, this represents a significant step towards solving the problem of MEV at the protocol level. In nearly every blockchain today, a single party ends up in control of each block: it decides which transactions get in, and can reorder them at will. MCP is the natural fix, but most recent designs pay for it with a separate aggregation phase, adding two extra communication rounds per block. Cadence makes the proposers part of consensus itself. Its fast path finalizes in an optimal three communication rounds, even when proposers are offline. Cadence also offers speculative finality, similar to MonadBFT, after just two rounds, revertible only if a proposer provably equivocated. In a simulation using estimated network delays between Monad mainnet's 200 globally distributed validators, finalization takes 219 ms on average, speculative finality 167 ms. Cadence pushes pipelining to the extreme: each block is proposed and finalized in its own independent consensus instance, without waiting on preceding blocks. The block interval then becomes a protocol parameter that can be arbitrarily small. At our initial target of 100 ms, a transaction waits on average just 50 ms to enter a proposal, and oracle prices, liquidations, and auctions can update every 100 ms. Cadence dynamically throttles the opening of new instances to bound the number of outstanding slots even during periods of network instability. When the network is healthy (under synchrony), a transaction included by an honest proposer can be neither dropped nor deferred (short-term censorship resistance), and no proposer can see the others' proposals in time to react (hiding). We prove both, together with safety and liveness under partial synchrony at the optimal 3f+1 fault bound. The Cadence protocol is modular: each module is simple on its own, and any of them can be swapped out without touching the rest. Cadence also builds on components already being deployed: proposals are disseminated as erasure-coded chunks over Deterministic RaptorCast, now rolling out on Monad, and validators vote on proposal digests, so voting does not wait for the full data to arrive. Start with the interactive tutorial: Full paper: Joint work by Kushal Babel, Fatima Elsheimy, Lioba Heimbach, Mohammad Mussadiq Jalalzai, Tobias Klenze, Jovan Komatovic, Jason Milionis, Mike Setrin, and Victor Shoup.

Category Labs

251,169 просмотров • 1 месяц назад

This guy built a visual scanner that reads 468 points on his face and 42 points on his hands from a regular webcam and turns them into a cloud of thousands of particles right between his palms. Inside, MediaPipe and TouchDesigner are linked: the first captures hands and face from the webcam with high accuracy, the second turns those coordinates into a live plane and feeds it into a POP system that instantly generates a swarm of particles in the shape of a head. No studio, no render farmer, no VR headset. Just a laptop, a webcam, and 1 TouchDesigner session. And traditional VJ studios keep teams of 5 people on a setup with lighting, custom hardware, and commercial plugins, while his expenses are only a TouchDesigner subscription and a regular USB camera. One laptop runs MediaPipe and TouchDesigner simultaneously, holds the camera stream at 60 FPS without drops, and in parallel processes 468 face points + 21 points on each hand. The camera captures frame after frame, MediaPipe in real time sends TouchDesigner the finger coordinates and face geometry, and the POP operator inside the engine translates those numbers into thousands of particle points with colors from bright pink to gold. This setup immediately defines the role of the tool and the limits of its autonomy. It knows where the fingertips are at every moment of the frame. It knows how to read the face geometry at any angle to the camera. It knows how to draw a swarm of particles between them with the right color and contour. → MediaPipe pulls 468 points from the face and 21 points from each hand, 60 times per second → TouchDesigner receives those coordinates, builds a virtual rectangle between the fingertips, and feeds it into the POP system → POP generates thousands of particle points in the shape of a head, coloring them in a gradient from bright pink to gold → The HUD layer adds green corners and a blue neon frame, styling the image like an AR interface → All layers assemble into 1 real-time frame that projects back onto the video in the camera window → The final image is recorded to a file or broadcast to a projector for a live installation And only when the guy spreads his hands wider does the plane between the palms stretch; brings them together, it narrows. Otherwise the system runs on its own. And when he moves from his home room to a concert hall, the same laptop with the same webcam launches the same TouchDesigner session in just 5 minutes, without reconfiguration, without a new team, and without a single line of new code. In his work setup there is no studio of his own and no team for assembly. On the desk sits a laptop with a webcam, on top run MediaPipe and TouchDesigner with POP operators, and the same setup through a USB camera moves to any concert without a new configuration. Out of everything I have seen this year, this is the cleanest Creative Coding setup on 1 laptop: 0 render farms, 0 studio lighting, and between them 3 libraries, thousands of particle points, and 1 webcam.

Blaze

38,242 просмотров • 3 месяцев назад

Batch Normalization by hand ✍️ ~ 7 steps walkthrough below Batch normalization is common practice for improving training and achieving faster convergence. It sounds simple. But it is often misunderstood. 🤔 Does batch normalization involve trainable parameters, tunable hyper-parameters, or both? 🤔 Is batch normalization applied to inputs, features, weights, biases, or outputs? 🤔 How is batch normalization different from layer normalization? So I drew and calculated one entirely by hand. Goal: normalize a mini-batch of 4 examples to mean 0 and variance 1, then let the network scale it back. = 1. Given = A mini-batch of 4 training examples, each with 3 features. = 2. Linear layer = Let us multiply by the weights and add the biases. Batch norm sits after this, which answers the second question: what gets normalized is features, not inputs, weights or biases. = 3. ReLU = We apply the activation, and -2 becomes 0. Negative values are suppressed before any statistic is taken. = 4. Batch statistics = Let us compute the sum, mean, variance and standard deviation, one row at a time. A row is a feature and the four columns are the four examples, so every number here measures one feature against the rest of the batch. That is the "batch" in batch normalization, and it is exactly what layer normalization does not do. The statistics are rounded to whole numbers, which is what keeps the rest of the page doable in pen. = 5. Shift to mean 0 = We subtract the mean, in green. The four values in each feature now average to zero. = 6. Scale to variance 1 = Let us divide by the standard deviation, in orange. Each feature now has variance one, whatever scale it arrived at. = 7. Scale and shift = We multiply by a linear transformation and pass the result on. The diagonal and the last column are trainable, so having just forced every feature to mean 0 and variance 1, we hand the network the means to undo it. The outputs: Mean of each feature = [2, 1, 2] Std dev of each feature = [1, 1, 2] To the next layer = [2, -2, 2, 0], [-3, 3, 6, -3], [2, 0, 1, 2] The answers: 🤔 Both. The scale and shift are trainable, the statistics are not. Epsilon and the momentum on the running statistics are the hyper-parameters, and one mini-batch by hand needs neither. 🤔 Features, after the linear layer, not inputs, weights or biases. 🤔 Batch norm measures across the batch, one feature at a time. Layer norm measures across the features, one example at a time. 💾 Save this post!

Tom Yeh

20,638 просмотров • 1 месяц назад

Ethereum in 2026 → What you need to know. Today ETH price is $2,104 which is almost 57% down from its all time high of $4,954 in August 2025. Fear and Greed index stands at 28. The Relative Strength Index (RSI) is approaching oversold conditions and retail interest is absent. However every on chain metric is hitting an all time high. - There are almost 35.5 million ETH staked. - Stablecoins on Ethereum have surpassed $158 billion. Tbh ETH exchange reserves are at their lowest since 2016. Spot ETH ETFs have attracted $11.6 billion in total net inflows. The network is more used, more secure and more embedded in institutions than ever yet the price remains in the fear zone. That disparity outlines the whole Ethereum narrative in 2026. - Pectra launched in May 2025 increasing the validator cap from 32 to 2,048 ETH. - Fusaka followed in December. - Glamsterdam is set for the first half of 2026 aiming for 10,000 transactions per second and over 78% reduction in gas fees through full account abstraction. - Hegota arrives in the second half with Verkle Trees pushing towards a stateless Ethereum. This upgrade pace is not slowing down. And the good thing is institutional side looks promising too. Ethereum Foundation staked 70,000 ETH in April 2026. This shift from selling ETH to fund operations to earning staking yield is significant. Yet there is an uncomfortable truth that many ignore → Layer 2 solutions like Base keep most fee revenue instead of returning it to ETH holders. Standard Chartered estimated that Base alone took $50 billion from ETH market cap. Increased Layer 2 activity does not directly translate to higher ETH value. So far this issue is unresolved concern underlying every optimistic outlook. The bullish scenario here is hinges on Glamsterdam delivering results, ETF inflows returning and the Federal Reserve lowering rates. and the bearish scenario suggests that Layer 2 value capture issue remains unresolved. Its crazy that the divergence between fundamentals and price is not a temporary dislocation but a structural issue. Right now the critical level to watch is $2,080. If it drops below that the bearish case becomes serious. Honestly fundamentals keep getting stronger while the price continues lagging behind. Next six months will determine which perspective will prevail.

evans

17,498 просмотров • 3 месяцев назад

One of the oldest cities in Spain is split in two by a 120 meter gorge. In the 18th century, a bridge was built across it. Hidden inside that bridge is a prison cell whose window opens onto the drop... The city is called Ronda, in the mountains of Andalusia, and it has been continuously inhabited since prehistoric times. The Romans called it Arunda. The Moors held it for seven centuries. In 1966, the Spanish state declared its historic centre a national heritage site. The gorge that cuts it in two is called El Tajo. On one side stands the old Moorish quarter, La Ciudad, with roots in the 8th century. On the other stands the newer town, El Mercadillo, built outside the medieval walls when Ronda outgrew them. For most of the city's history, the only way between them was a long descent to the river below, and a long climb back up. In 1735, King Philip V of Spain ordered a bridge to span the chasm. The first attempt collapsed in 1741, killing about fifty people. A second project began in 1759 under the Spanish architect José Martín de Aldehuela. It took thirty-four years. The bridge was finally inaugurated in 1793. It is 98 meters tall, made of solid stone, and it has never moved. Above the central arch, the architects built a chamber of about sixty square metres. For most of the bridge's history, this chamber served as a prison. The prisoners could see the river through a small barred window in the floor of their world. Ernest Hemingway visited Ronda repeatedly in the years before and after the Spanish Civil War, and the most harrowing chapter of For Whom the Bell Tolls — the village massacre Pilar describes, with men beaten by their neighbors and pushed off a cliff — was likely set in this town... -- -- -- If you enjoyed this, I write a weekly newsletter read by over 50,000 people who love rediscovering the beauty of the past. You can join us here: If you'd like to support my work, a paid subscription is what makes it possible.

James Lucas

69,196 просмотров • 3 месяцев назад

i'm not fine after reading this a guy with a laptop got his own silicon chip manufactured with software Google gave away. the commercial version of that software rents for up to $1,000,000 a year. he never signed a vendor contract and never paid for a seat. he wrote the logic, pushed it to GitHub, and nine months later a wafer came out of a fab. getting silicon with your name in it used to take a company. now it takes nine months. his slot was 160 by 100 microns: about 1,000 logic gates, 8 inputs, 8 outputs, clocked past 50 MHz. more than 600 designs have already come back this way. this is the open silicon stack. Google and SkyWater published a complete 130nm manufacturing process, DARPA funded the software that turns code into a fab-ready file, and all of it sits in public repositories. turns out the whole flow fits in a git push: - write the logic in Verilog, or drag gates around in a browser if you have never done this - push to GitHub, an action runs synthesis, placement, routing and sign-off on the commit - OpenROAD finishes place-and-route with no human in the loop, code to fab file inside 24 hours - SKY130 carries the fab's real design rules, so passing the checks means it is manufacturable - a few hundred designs share one wafer, which is the only reason a person can afford the masks nobody puts this part in the thread: 130nm is roughly where the industry stood in 2001, and you wait six to nine months for silicon. this does not get you a GPU. it gets you a real object with your logic inside it. bookmark this. the video is one of those designs opened layer by layer, and every rectangle in it exists in the file that was sent to the fab.

Argona

150,347 просмотров • 25 дней назад

There is a marble quarry in the Italian Alps that has been working since 1387, but in 639 years it has had only one customer... The quarry is at Candoglia, at the mouth of the Ossola valley. On 24 October 1387, Gian Galeazzo Visconti decided that the cathedral going up in his city should be built of marble rather than brick, and handed the quarry over to the Veneranda Fabbrica del Duomo, the body established to build it. He also granted the stone free passage down the waterways to Milan. The blocks went by raft from the river Toce into Lake Maggiore, down the Ticino, along the Naviglio Grande, then through a system of locks into a small lake in the centre of the city, a few hundred metres from the site. The bargemen carried the letters AUF, for "ad usum fabricae", for the use of the works, which cleared the cargo through customs without charge. People in Lombardy still say "a ufo" for something got for nothing, and the phrase is traditionally traced back to those barges... Mark Twain came in 1867 and noticed something most visitors walk past: "We saw a new statue put in its niche yesterday alongside of one which had been standing these four hundred years." It has never stopped: around a thousand tonnes of Candoglia marble still comes out of the mountain every year, and all of it goes to the same building. In a workshop in the Certosa district, sculptors cut replacements for whatever the weather has eaten away, from the same stone, for the same institution, founded in 1387. The cathedral was declared finished in 1965 but the quarry never stopped, because a cathedral like this is not something you complete... it is inherited, kept, and handed on. As John Ruskin wrote in The Seven Lamps of Architecture: "When we build, let us think that we build forever. Let it not be for present delight, nor for present use alone; let it be such work as our descendants will thank us for; and let us think, as we lay stone on stone, that a time is to come when those stones will be held sacred because our hands have touched them, and that men will say, as they look upon the labour and wrought substance of them: ‘See! This our fathers did for us.’"

James Lucas

99,081 просмотров • 29 дней назад

Israel Has Hit Nearly Everything It Planned To. Now What?... 🚨 OPERATIONAL UPDATE: ISRAEL U.S. WAR WITH IRAN - Reporting Window: Last 24 Hours Israel has now largely completed its preplanned strategic strike package inside Iran, while Iran’s response continues to degrade in scale but not in intent. At the same time, the northern front is heating back up, and regional actors are positioning for what comes next rather than what comes now. ✈️ STRATEGIC AIR CAMPAIGN OVER IRAN Israel has effectively finished its target list. The IDF now confirms that nearly all “vital and strategic” targets have been struck. Over the past 24 hours, operations focused on depth and completeness rather than expansion. Strikes hit a wide geographic spread including Tehran, Shiraz, Kermanshah, and Ahvaz, with particular emphasis on military-industrial infrastructure. Key targets included: *⃣ Approximately 20 weapons production and R&D fa cilities in Tehran *⃣ Mehrabad Airport and adjacent regime-linked infrastructure *⃣ A chemical supply node tied to SPND, Iran’s weapons development apparatus At the same time, Israel continued its shift into economic warfare. The destruction of major components of Mobarakeh Steel, Iran’s largest industrial complex, is not tactical. It is strategic degradation of long-term national capacity. What changed here is straightforward. This is no longer a shaping campaign. This is a completion phase. Israel has moved from identifying targets to executing them, and now toward locking in the strategic outcome. 🚀 IRANIAN MISSILE ACTIVITY Iran is still responding, but the character of that response has changed. In the latest barrage, roughly 10 ballistic missiles were launched in the opening wave. That makes it one of the larger salvos in recent weeks, but still far below earlier peak volumes. Most were intercepted, and physical damage was limited, though civilian impact remains real, particularly through panic, injuries, and indirect casualties. The important distinction is this: Iran still has the stockpile, but not the operational tempo. Its retaliation doctrine remains intact. It continues to mirror categories of targets struck inside Iran, expanding at times to civilian and economic infrastructure in Israel and across the Gulf. But the scale is no longer overwhelming. It is calibrated. 🔥 NORTHERN FRONT: LEBANON ESCALATION While Iran slows, the northern front is doing the opposite. Hezbollah resumed intense rocket fire into northern Israel, including a direct hit in Kiryat Shmona that caused multiple injuries. In response, Israeli operations intensified significantly. In the last 24 hours: *⃣ Over 40 Hezbollah fighters were killed *⃣ A senior Hezbollah commander was eliminated in Beirut *⃣ The IDF began systematically destroying homes used for launch positions and surveillance This marks a clear doctrinal shift. Israel is no longer just responding to fire. It is shaping the battlefield, likely toward a buffer-zone model similar to early phases of Gaza operations. 🌍 REGIONAL AND GLOBAL DIPLOMATIC MOVEMENT Diplomatic activity is accelerating for one reason. The military phase is stabilizing. President Trump again stated that the war is nearing completion, though notably without offering a clear timeline or exit structure. That ambiguity is now a central feature of the conflict’s political layer. At the same time: *⃣ Pakistan has emerged as a potential mediator between the U.S. and Iran *⃣ Gulf and European states are pushing for de-escalation frameworks *⃣ Discussions are increasingly focused on maritime security and the Strait of Hormuz The UAE, in particular, has highlighted the scale of Iranian regional attacks, reporting hundreds of intercepted missiles and drones while framing Iran’s actions as violations of sovereignty and international law. This is no longer just about the battlefield. It is about shaping the post-war order. ⚠️ INTERNAL IRAN PRESSURE Inside Iran, pressure is building across multiple fronts. The economy is entering a wartime shock phase, with inflation rising sharply and essential goods becoming harder to access. At the same time, the regime continues internal crackdowns, including executions tied to earlier protests. There are also signs of instability at higher levels. The reported assassination attempt on former foreign minister Kamal Kharazi adds another layer of uncertainty, whether internal or externally driven. Public trust is eroding. Information control is weakening. The internal environment is becoming more volatile, not less. 🧭 THE BIG PICTURE What changed in the last 24 hours is not the scale of the war. It is the clarity of its trajectory. Israel has largely completed its strategic objectives inside Iran. Iran continues to respond, but at a reduced and more controlled pace. The center of gravity is shifting away from large-scale strikes and toward political positioning. At the same time, the Lebanon front is emerging as the most active and unpredictable theater. 🧠 MY ASSESSMENT This is the phase most observers misread. The war is not ending because Iran has collapsed or because stability has been achieved. It is moving toward an endpoint because the core objectives have been demonstrated. Israel and the United States have shown that they can penetrate Iran at will, dismantle critical infrastructure, and do so without being pulled into a prolonged ground conflict. That changes the strategic equation. Even if the regime remains in place, the message is now unmistakable. Military dominance does not require occupation. Deterrence no longer depends on long wars. And that lesson will not be lost on Iran, Hezbollah, the Houthis, or any actor watching how this conflict unfolded.

Inside_Israel_Intel

129,155 просмотров • 4 месяцев назад

🚨 OPERATIONAL UPDATE: ISRAEL U.S. WAR WITH THE ISLAMIC REPUBLIC - Reporting Window: LAST 24 HOURS • Iran widened its fire again with a broad evening missile barrage on central Israel and continued attacks across the Gulf, including a drone strike that hit a fuel tank at Kuwait International Airport • Israel intensified strikes across Iran, with reported hits in Tehran, Qazvin and Alborz industrial areas, plus continued pressure on missile infrastructure and launch cells • Hezbollah kept the northern front active, including a direct rocket hit on a building in Kiryat Shmona, while Israel deepened its Lebanon campaign and Katz publicly framed the objective as a security zone up to the Litani • The diplomatic track moved forward, but only in the strangest possible way: Trump says talks are progressing, Iran still publicly denies direct negotiations, and multiple reports now point to JD Vance as Tehran’s preferred American interlocutor • The big picture is unchanged: the war is still live on every major front, but the center of gravity is shifting toward a contest over how it ends, who gets to define victory, and whether the Gulf will stay adjacent to the war or be pulled fully into it The most important thing to understand about the last 24 hours is that this was not a quiet period masked by negotiations. It was the opposite. The battlefield remained active from Tehran to southern Lebanon to Kuwait, even as Washington and Tehran edged further into a murky negotiation channel. That is what gives the last day its character: not de escalation, but simultaneous escalation and diplomacy, both moving at once. Open source reporting reflects the same picture, with repeated indications of strikes in Tehran and Qazvin, attacks near Baghdad airport, a Kuwait airport fuel fire, and a large Iranian barrage toward central Israel late in the window. **Special thanks to Michael W for your continued contribution to the open-source intel picture behind these updates. ━━━━━━━━━━━━━━━━━━ 🚀 IRANIAN MISSILE FIRE ON ISRAEL Iran kept up the pressure on Israel in two different ways over this window. Earlier in the cycle, a cluster warhead strike wounded nine people in Bnei Brak, with additional damage in Petah Tikva, while Hezbollah fire from Lebanon killed a woman near Mahanayim Junction and wounded several more in Kiryat Shmona. Later, near the end of the reporting window, Iran launched another broad barrage toward central Israel, with warnings stretching across Gush Dan, Sharon, Wadi Ara, Samaria, Judea and the Dead Sea region. Open source reporting you provided tracked that second wave in real time, showing how broad the alert footprint was even though initial reports indicated no immediate casualties from that specific evening barrage. This is what stands out operationally: Iran’s missile campaign is not gone, but it looks increasingly built around selective disruption rather than the huge opening barrages of the war. The salvos are still dangerous, still capable of civilian casualties and still capable of producing visually dramatic and politically effective moments, but they are landing against a backdrop of steadily intensifying strikes on Iran’s launch network. That makes each successful hit feel more deliberate and more strategic. ━━━━━━━━━━━━━━━━━━ ✈️ THE AIR CAMPAIGN OVER IRAN KEPT MOVING Israel’s strike campaign inside Iran also remained broad and geographically layered. Reuters reported renewed Israeli strikes as talks were being floated through intermediaries. Open source intelligence adds texture to that by showing repeated reporting from open source channels of impacts in eastern and western Tehran, the Alborz industrial zone in Qazvin province, and additional blasts reported across Khuzestan and other regions. There were also repeated reports of targeted assassination attempts in east Tehran, which fits the broader pattern of not just degrading launchers and production nodes, but also hunting the people tied to them. The color here matters. This no longer looks like a campaign limited to air defenses and obvious military compounds. The picture from the last 24 hours is of a system being pressed from multiple angles at once: missile depots, industrial support zones, launch crews, command elements and regime infrastructure in and around Tehran. Open source reporting reinforces that sense of breadth, especially the repeated references to Qazvin and Alborz secondary explosions and to ongoing heavy activity over Tehran. ━━━━━━━━━━━━━━━━━━ ⚡ THE ENERGY WAR IS STILL HOT The clearest new regional energy development in this window was Kuwait. Reuters reported that a drone attack hit a fuel tank at Kuwait International Airport, causing a fire but no casualties. That matters not because the material damage was catastrophic, but because it again shows Iran or Iran aligned actors reaching directly for civilian and logistical energy infrastructure in Gulf states. This was not an abstract threat anymore. It was a live strike on a functioning international hub. Your outbox tracked the same event quickly and repeatedly, alongside additional open source reporting about nearby attacks and power disruptions in Kuwait. At the same time, the diplomatic and military discussion around the Strait of Hormuz kept shaping everything else. Markets moved on talk of a U.S. proposal and possible hosted talks in Pakistan or Turkey. Oil eased on negotiation optimism, but the underlying structure of the crisis remains the same: Iran still retains the ability to disrupt shipping and energy confidence without fully “closing” the Strait in a formal sense. That is why even modest signs of diplomacy can move oil sharply, and why even a localized drone strike in Kuwait still carries outsized weight. ━━━━━━━━━━━━━━━━━━ 🇱🇧 LEBANON IS NOT A SIDESHOW The northern front kept boiling. Reuters reported that Israel now intends to occupy a swathe of southern Lebanon up to the Litani River, with Defense Minister Israel Katz explicitly describing a “security zone” concept. That is not rhetoric you use if you still think this is a short punitive phase. At the tactical level, Hezbollah continued to demonstrate that it can still impose costs, including a direct rocket hit on a building in Kiryat Shmona and earlier casualties in the north. Meanwhile, open source reporting pointed to Israeli strikes in Nabatieh, Rashidiya, Bchamoun and broader southern Lebanese infrastructure, which matches the picture of sustained pressure rather than episodic retaliation. The broader meaning is straightforward. Israel is signaling that if the Iran war ends inconclusively on the Iranian front, it does not intend to leave Hezbollah’s northern threat structure intact and simply hope for the best. Lebanon is being shaped now as part of the endgame, not just the current fight. ━━━━━━━━━━━━━━━━━━ 🇮🇶 IRAQ STAYED ACTIVE TOO Iraq remained active in the background, but it should not be treated as background noise. Open source intel reporting includes repeated reporting on a targeted U.S. strike on a vehicle near Baghdad airport and continued militia related activity tied to U.S. positions and proxy structures. That comes after the prior cycle’s major strikes on PMF and militia command nodes. It fits the larger pattern we have now seen for weeks: Iraq is not the main theater, but it is still one of the places where the war keeps trying to widen horizontally. ━━━━━━━━━━━━━━━━━━ 🌍 THE NEGOTIATION TRACK GOT STRANGER, NOT CLEARER Trump is still publicly presenting the talks as real progress. Reuters reports that Pakistan conveyed a U.S. proposal, with Pakistan or Turkey possible venues, and that Washington has floated a broader framework dealing with nuclear capability, missiles and proxies. At the same time, Iran continues to publicly deny meaningful direct talks and has toughened its public stance, insisting on guarantees, compensation and no rollback of its missile deterrent. What makes the last 24 hours more interesting is the growing focus on who would even talk for the United States. Times of Israel and Jerusalem Post reporting both indicate that JD Vance is increasingly central to the diplomacy, with Tehran reportedly preferring him over Witkoff and Kushner. The diplomatic track here appears as both real and deeply unstable, with questions about who on the Iranian side actually holds authority and whether Washington is now seeking an end state short of outright regime collapse. That shift matters because it tells us something important: Washington increasingly seems to be searching for an off ramp that still looks like victory, while Israel and Gulf allies appear much less comfortable with ending this war before Iran’s military and proxy architecture are degraded further. That tension is now one of the defining features of the conflict. ━━━━━━━━━━━━━━━━━━ 📌 WHAT MATTERS MOST RIGHT NOW 1️⃣ The war is still fully active across multiple fronts Iran hit central Israel again, Kuwait airport was struck, Lebanon stayed hot and Israel kept pounding targets inside Iran. Negotiations did not replace combat. They were layered on top of it. 2️⃣ The pressure on Iran’s internal military system keeps deepening The accumulating pattern of strikes in Tehran, Qazvin, Alborz and other areas suggests a campaign that is still broadening the target set, not narrowing it. Open source reporting in your files strongly supports that picture. 3️⃣ The diplomatic track is real, but it is not clean Trump is selling progress. Iran is denying direct talks. Vance is becoming more central. And nobody looking at the battlefield would conclude that the war is genuinely close to stopping on its own. ━━━━━━━━━━━━━━━━━━ BOTTOM LINE The last 24 hours painted a clearer picture than some of the recent reporting windows. This is no longer just a war of salvos and counterstrikes. It is now a war over end states. Iran is still trying to prove it can widen the cost map, not just hit Israel but keep the Gulf under pressure too. Israel is still trying to prove that sustained, system level degradation inside Iran can continue even while diplomacy swirls overhead. And Washington is trying to find a formula that can stop the war without looking like it backed down. That is why the reporting feels different now. The battlefield is still violent, but the arguments over how this ends are becoming just as important as the strikes themselves.

Inside_Israel_Intel

23,818 просмотров • 5 месяцев назад

We are launching A first attempt at building a digital theme park for the Zama Protocol. Our thesis is simple: to accelerate the adoption of FHE, we need cool apps designed for real people. Users don't adopt protocols, they adopt experiences. In most ecosystems, there are very few places that turn participation into status and fun. Usage is transactional, not emotional. Adoption stalls. zashapon is always open, accessible, social by default, and adding infinite attractions over time. It's a playful layer that makes the ecosystem feel like… an ecosystem. The mechanics are simple: - You make FHE transactions by using confidential apps - You get tickets - You can spend them in Zashapon Participation → access → rewards. Zashapon is creating a flywheel: More FHEVM usage → more tickets → more play → more rewards → more users → more builders → more FHEVM usage. Why “gashapon” machines? Because "chance + collection + ritual" is one of the oldest, most reliable engagement loops in games and theme parks. It creates stories users want to repeat. Zashapon uses FHERand to make sure all draws are programmatically fair and confidential. Fun without trust tradeoffs. What you get today: NFTs. What you get tomorrow: anything that can be digitally rewarded — access, perks, whitelists, lore items, partner drops, even real-world benefits. Zashapon is the entertainment / loyalty / identity layer for confidential applications building on top of the Zama Protocol. In physical theme parks: you ride → you collect → you show → you come back with friends. In Zashapon: you use confidential apps → you earn tickets → you draw → you flex / trade / build → you return. We're launching with one Gashapon machine, rewarding the users of Soon there will be many more — one for every new app, partner, and experience built on the Zama Protocol. Digital parks win by expanding attractions continuously. Zashapon is live on Zama testnet right now. Go try it now!

Soliton

84,817 просмотров • 8 месяцев назад

Stateless History Node is almost like a regular Ethereum node, but it doesn't store state and it doesn't have EVM execution. It's used only for syncing events and thus - is faster and gives you FREE INDEXING. You don't have to pay 6 figures for RPC anymore! Just spin up a Stateless History Node, plug rindexer or Ponder there, and enjoy free (AND FAST!!) indexing! This node is syncing >1000 blocks per second at my local pc (less than 6hrs for the whole Ethereum), and it should use less than 200GB - which means you can host it on a MacMini, Hetzner or whatever. You can futhermore filter that by using block ranges or bloom filters, etc - I haven't developed this yet. What you see is a proof of concept. It works via native devp2p 'eth' protocol, but with EIP4444 and The Prune we would have to also support era1 archives and Portal Network. But so far it works - there are plenty of peers serving historical receipts, and they serve them FAST! If you run Stateless History Node you can also serve the blocks and receipts - so that could help to preserve archival data too. For now there is no data validation yet (and even no data storage - that's a very early PoC), but we can verify validity of chain by simultaneously running a lightweight CL node (or not lightweight if you're extremely paranoid). And then support verifying the hashes of receipts and blocks with their parents, maintaining full integrity and zero trust. It's also written in rust, btw. So, I guess, at least for Ethereum Mainnet the era of RPC's pumping moneybags is over - there's finally a local, trustless and free indexing alternative available. Too sad this won't work for Optimism / Base , cause despite introducing P2P after Bedrock - they haven't enabled receipts transfer in the protocol (or at least I couldn't find one). Arbitrum is even sadder - I don't believe there is a P2P layer at all - you just have to run your own node, hold state and execute blocks to get events. There is hope - Paradigm recently released Ress - stateless execution, but it requires nodes to support Witness preparation & exchange - but this could work for L2s - cause the main blocker for local RPCs rn is huge state (VPS with TB storage cost a lot), and the second blocker is EVM forks makes it hard to hold a node - it needs to be maintained, upgraded, etc. Ress at least solves the state part. But anyways, I will try to continue working on this and release some MVP version with RPC endpoint and data storage soon - follow the updates!

Convergence Boy

29,799 просмотров • 7 месяцев назад