Beyond the cold wallet
then text. Heading: "Ud over cold wallet" or "Ud over den kolde wallet"? Better: "Ud over cold wallet" as term is known. Or "Ud over kold opbevaring"? Keep "cold wallet" in English often. But Danish crypto community uses "cold wallet". I'll use "cold wallet". Text: "Most people know Foundation for its Passport hardware wallet, a device designed to keep bitcoin keys offline. That’s still the core business. But the company sees a bigger opportunity in using the same secure hardware to authenticate a person’s identity or authorize an AI agent to act on their behalf. The new funding will go toward building that platform." Translation: "De fleste kender Foundation for deres Passport hardware-wallet, en enhed designet til at holde bitcoin-nøgler offline. Det er stadig kerneforretningen. Men virksomheden ser en større mulighed i at bruge den samme sikre hardware til at autentificere en persons identitet eller autorisere en AI-agent til at handle på deres vegne. Den nye finansiering vil gå til at opbygge den platform." Third paragraph:Authorizing AI agents in real time
"Here’s the hook: as AI agents get more capable — trading, signing, managing accounts — someone needs to approve what they do. Foundation wants to be the physical trust anchor. Think of a hardware token that an AI agent pings before it moves funds or changes a setting. The device says yes or no. That’s a different use case from just holding your bitcoin, but it relies on the same security architecture." Translation: "Her er grebet: efterhånden som AI-agenter bliver mere dygtige – handler, signerer, administrerer konti – skal nogen godkende, hvad de gør. Foundation ønsker at være det fysiske tillidsanker. Tænk på en hardware-token, som en AI-agent pinger, før den flytter midler eller ændrer en indstilling. Enheden siger ja eller nej. Det er en anden brugssituation end blot at holde dine bitcoin, men den bygger på den samme sikkerhedsarkitektur." "the hook" -> "grebet" (the catch). "ping" -> "pinger" (acceptable tech term). "use case" -> "brugssituation" or "anvendelsesområde". "security architecture" -> "sikkerhedsarkitektur". Fourth paragraph:The investors
"Fulgur Ventures led the round. It’s a firm that focuses on bitcoin-adjacent infrastructure, so the fit makes sense. Arche Capital, another crypto-native investor, joined in. Neither firm disclosed their exact stake. Foundation hasn't said when the new features will ship, but the company is known for taking its time on hardware releases — the Passport went through multiple revisions before launching." Translation: "Fulgur Ventures ledte runden. Det er et firma, der fokuserer på bitcoin-relateret infrastruktur, så pasformen giver mening. Arche Capital, en anden krypto-native investor, deltog. Ingen af firmaerne oplyste deres præcise andel. Foundation har ikke sagt, hvornår de nye funktioner vil blive lanceret, men virksomheden er kendt for at tage sig tid med hardwareudgivelser – Passport gennemgik flere revisioner, før den blev lanceret." "fit makes sense" -> "pasformen giver mening". "ship" -> "lanceret" or "udsendt". Fifth paragraph: "The timing isn't accidental. AI agents are proliferating fast, and most rely on software-based permissions that can be phished or exploited. A dedicated hardware layer is a harder target. Whether users will want to plug a wallet into their AI stack is an open question. Foundation is betting the answer is yes." Translation: "Timingen er ikke tilfældig. AI-agenter spreder sig hurtigt, og de fleste er afhængige af softwarebaserede tilladelser, der kan phishing-angribes eller udnyttes. Et dedikeret hardwarelag er et sværere mål. Om brugerne vil have lyst til at tilslutte en wallet til deres AI-stak er et åbent spørgsmål. Foundation satser på, at svaret er ja." "phished" -> "phishing-angribes" or "fiskes efter". "exploited" -> "udnyttes". "hardware layer" -> "hardwarelag". "AI stack" -> "AI-stak". Now meta description: "Foundation, a Boston bitcoin hardware wallet maker, raised $6.4M led by Fulgur Ventures to expand into identity, MFA, and real-time AI agent authorization." Translation: "Foundation, en Boston-baseret bitcoin hardware-wallet-producent, rejste 6,4 millioner dollars ledet af Fulgur Ventures for at udvide til identitet, MFA og realtidsautorisering af AI-agenter." Note: "MFA" can stay as acronym, but expand? In Danish "MFA" is used. "real-time AI agent authorization" -> "realtidsautorisering af AI-agenter". Also keep "Foundation" as proper noun. Now assemble JSON. Ensure proper escaping for HTML inside JSON string. Use double quotes. The content will be a string with HTML tags. I'll write it as a single line for JSON, but for readability I'll keep newlines in the thinking but in final JSON it should be a string. I'll produce the JSON with escaped newlines? Actually JSON allows newlines in string but it's ugly. Better to keep as one line or with . I'll write with actual newlines for clarity in the response, but the user expects valid JSON. I'll ensure it's valid by using double quotes and escaping any internal double quotes. The HTML has no double quotes, only single quotes? Actually it has double quotes in tags like etc. No, HTML tags use angle brackets, no double quotes inside except for attributes? But there are no attributes in this HTML. So no need to escape. Also the text has no double quotes. So it's safe.
I'll produce the JSON with indentation for readability, which is valid JSON. The user said "RESPOND IN JSON:" so I'll output only the JSON.
Final JSON:
{
"title": "Foundation rejser 6,4 millioner dollars til at omdanne hardware-wallets til AI-agent-gatekeepere",
"content": "Foundation, et Boston-baseret bitcoin hardware-wallet-selskab, har afsluttet en finansieringsrunde på 6,4 millioner dollars ledet af Fulgur Ventures. Arche Capital bidrog også. Pengene vil skubbe virksomheden langt ud over opbevaring af krypto – ind i identitet, multifaktorautentificering og et nyt s
Foundation, et Boston-baseret bitcoin hardware-wallet-selskab, har afsluttet en finansieringsrunde på 6,4 millioner dollars ledet af Fulgur Ventures. Arche Capital bidrog også. Pengene vil skubbe virksomheden langt ud over opbevaring af krypto – ind i identitet, multifaktorautentificering og et nyt s
