Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Paying for AI compute stopped being the hard problem on July 14, when Visa, Mastercard, and the Linux Foundation put their names on x402. We're partnering with 0G Labs (Home of Infinite AI) because the harder problem, proving the compute you paid for actually ran, still needed solving. 0G...

82,376 Aufrufe • vor 26 Tagen •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

The machine economy does not begin when robots get smarter. It begins when a machine can be paid to do something, and every party involved can prove what happened. Made with Fabric Foundation. Two systems meet in the middle of it: Agent Passport issues the agent a verifiable identity and a spending authority its owner defines, and RoboPay actuates a robot after the payment behind the request checks out. What happens before the robot moves: ▷ Authority is granted once, and it is bounded. The human signs a spending session with a passkey: a total budget, a per-transaction ceiling, the assets allowed, and an expiry. The agent holds no card number and no wallet key. It holds a delegation it cannot exceed. ▷ Two payments, because these are two different obligations. One settles with the merchant for the goods. A separate x402 payment pays the robot for the work of moving them. Buying a thing and hiring a machine to carry it are not the same transaction, and the receipt keeps them apart. ▷ Verification comes before motion. The request arrives with an x402 payment header. The facilitator checks the network, the price, the payee wallet, and the signed payload. Only then are the transaction details sealed onto the robot action event and the command published. Until that clears, the robot sits still. ▷ Every step leaves a receipt. Identity, scope, approval, both payments, verification, dispatch. When you need to know why a machine did something, the answer is a record rather than a guess. (This run was executed in a demo environment.) Agents have been paying for software for a while now. Paying for physical work is a harder problem, because a delivery cannot be rolled back. The guarantee has to sit in front of the action instead of behind it. Authorization before payment, payment before motion: that ordering is what makes it safe to let autonomous systems spend in the world we live in. It is also the layer the machine economy has to get right before anything else in it can work. Scoped by Kite. Verified by RoboPay. Delivered in the real world. 🪁

KITE AI

35,068 Aufrufe • vor 1 Monat

Someone ran Claude Code on a beach where any device overheats and that spot suddenly turned out to be the best home for the most powerful AI in the world. This is the reMarkable Paper Pro. A paper tablet for notes with no browser and no social media and not a single app. He sat down right on the sand in the open sun and brought up Claude Code on Opus 4.6 over the Claude API on the paper screen and opened his project ~/repos/webs while the waves broke a few steps away. For years every device had the same trouble outside. In direct sun the screen glares and washes out and heats up and instead of your work you see your own reflection. But e-ink does not blast its own light into your face. It reflects the sunlight like the page of a book. And here is what came out of it. The very thing that kills any normal screen outside turned into fuel for this one. The brighter the sun the sharper the picture because it has nothing to glare with and nothing to wash out. And then comes the thing no laptop on a beach will give you. Your eyes do not get tired. You can watch Opus think on max effort for an hour and it reads like a book in the sun and not a backlight you squint into. The picture only comes alive. In bright light it does not fade but turns sharper and higher in contrast than it ever was in a room. The charge lasts for days. E-ink barely touches the battery so there is no outlet anywhere on the sand and the tablet does not care. It weighs as much as a notebook. The whole setup folds into a beach bag like a pad with a pen on top. Everything on the screen is for real. Claude Code v2.1.110 and Opus 4.6 on the Claude API and the project ~/repos/webs open right on the e-ink in the middle of the sand. In my opinion this is the most unexpected home for an AI this year. Not an office with the blinds drawn and not a monitor cranked to full brightness but a quiet sheet of paper on the sand that open sun only makes better and on it the most powerful Claude writes code right on the page like a pen.

Blaze

89,575 Aufrufe • vor 2 Monaten

The creator of High Bandwidth Memory (HBM) put a number on the AI build that should stop every infra investor cold. A cluster of a million GPUs runs at roughly 10-20% utilization (Save this). Kim Jung-ho spent thirty years building what feeds the GPU, and his claim is that the GPU is barely working. Here is what is actually happening. Every time a model generates output, the data has to be read out of memory, computed, and written back. The read and the write swallow almost the entire cycle. While that data moves, the GPU does nothing. It sits there, fully powered, fully paid for, waiting. By Kim's estimate the memory is doing only about 30 percent of the work it needs to do. The processor idles the rest. So a million installed GPUs run at 10 to 20 percent. You are not compute constrained. You are memory constrained, and the expensive part is standing around. Adding more GPUs does not fix this. It gives you more processors starving for the same data. Here is the part that decides the next decade. Memory can grow. When a cell cannot shrink any further, you stack it into a high-rise, layer on layer. A GPU cannot be stacked. It runs too hot and needs a cooler bolted to its back, so the one move that rescues memory is closed to the processor. The thing that can keep stacking compounds. The thing that cannot plateaus. The marginal dollar in an AI build now buys more by fixing the memory path than by bolting on another idle GPU. Which is why the companies that control memory bandwidth and supply are not suppliers to the AI trade. They are the AI trade.

Fireside Alpha

38,370 Aufrufe • vor 2 Monaten

your agent reviewing its own work is not a check. it is a second opinion from the same source. this is the most common gap in agent systems and it hides in plain sight, because the step exists. there is a review. it just cannot do the thing you think it does. here is the mechanism. the model produced an output from a context. you then ask the same model, holding the same context, whether that output is correct. it answers fluently, because that is what it does. and the answer is drawn from the same distribution that produced the thing being judged. same weights, same window, same blind spots. if the reason the output is wrong is something the model does not know, the review does not know it either. if the reason is something the context does not contain, the review has the same context. the failure mode and the detector share a cause. > why it feels like it works because most of the time the output is fine, and the review says fine. agreement is not evidence of detection. a reviewer that says pass on everything agrees with reality most of the time too. what you actually want to measure is what happens on the cases that are wrong. that is the only place a check earns its name, and it is exactly the place where a self-review is weakest. there is research on this. Huang and colleagues at DeepMind showed at ICLR 2024 that intrinsic self-correction, revising without external grounding, does not reliably help and often makes things worse. > what to actually do move the check outside the model. a test that runs, a schema that validates, a file that exists or does not, an exit code from something you did not write. these are not smarter than the model. they are just not correlated with it, and that is the entire value. when the judgement genuinely needs a model, at minimum use a different family. same family means shared blind spots, and frontier judges measurably inflate scores for outputs that look like their own. and split the work by kind. anything objectively checkable goes to code. only the genuinely semantic calls go to a judge, and those get a rubric written as one line. a review inside the loop tells you the model is confident. a check outside it tells you whether the work is done. save this - then read the eval setup below

Hanako

14,325 Aufrufe • vor 28 Tagen

America is about to lose the AI race, and it will not happen at the frontier. It will happen at the floor. Everyone is watching who ships the smartest model. The actual war is over the 80% of tokens nobody posts about: the routine inference that quietly runs the world. On current trajectory, that fight is already lost. Watch what people do, not what they say. Coinbase just defaulted its own engineers off frontier models onto open weights and cut AI spend nearly in half while usage kept climbing. Even NVIDIA runs a closed frontier model as an orchestrator and pushes the volume to its own open weights. The frontier is becoming a router. The volume goes open. That part is settled. Here is the part that should terrify Washington: the only credible open tier today is Chinese. GLM. Kimi. And the US answer is to tighten export controls and freeze its own labs in place, as if you can embargo a file that is already downloaded, or price-match free. So China hands the Global South Huawei hardware and free open models, and a generation in Africa and Southeast Asia learns to reason through a model that will not tell them what happened at Tiananmen Square. That is not a cost story. That is influence through inference. You do not have to win hearts and minds when you supply the mind. Open source is not a nice-to-have for America. It is the whole ballgame for the 80%, and right now the US is barely on the field. We need American open weights. Not eventually. Now.

Ben Pouladian

71,722 Aufrufe • vor 2 Monaten