<\/p>\nInfrared image of the Baochip-1x mounted on a circuit board.<\/p>\n
<\/span>Courtesy of Andrew \u201cbunnie\u201d Huang<\/span><\/div>\n<\/figure>\nfigure<\/p>\n
Huang plans to demonstrate the technique at the conference, allowing attendees to inspect the chip under an infrared light.<\/p>\n
\u201cI’ve been doing a bunch of stuff along the lines of trust and silicon and verification transparency\u201d for years, Huang tells WIRED. “It’s all \u2026 this kind of story arc I’ve been on \u2026 to try and get a chip that we can trust down to the very core, down to the transistor \u2026 You can actually \u2026 see the RAM arrays \u2026 on the chip.\u201d<\/p>\n
Build-a-Chip<\/h2>\n
Building a new chip is an expensive project that can cost millions of dollars for fabrication. But Huang got a big break three years ago when a company called Crossbar reached out to him. The company wanted to create a new open source and secure chip but didn\u2019t know how to go about it. Huang agreed to assist on one condition: that they let him piggyback on their manufacturing run by placing his CPU on their chip wafer, allowing both designs to share the same manufacturing run rather than requiring Huang to fund a separate run.<\/p>\n
“They look at it as, if they put me on the chip, they get two products for the price of one,\u201d Huang says. This kind of piggybacking is not unusual, he adds, though it\u2019s not something the industry likes to discuss publicly.<\/p>\n<\/div>\n
LANGUAGE: Write entirely in English. Preserve proper nouns, brand names, product names, game titles, technologies, and technical terms exactly as written. Translate everything else naturally. Read as if written by a native English editor.<\/p>\n
CONTENT SOURCE: Treat CONTENT as your primary factual source. Build the article from deep understanding of CONTENT. Do not mechanically expand the title.<\/p>\n
CONTENT CLEANING: Remove website names, publication names, author credits, RSS labels, newsletter markers, syndication branding, generic labels (Summary, Highlights, Recap, Key Takeaways). Convert “according to X” into direct factual statements.<\/p>\n
FACT PRESERVATION: Preserve exactly: names, brands, companies, products, games, technologies, dates, numbers, percentages, prices, technical specifications. Never distort facts.<\/p>\n
WRITING STYLE: Natural, fluent, authoritative, engaging, analytical, trustworthy, nuanced. Blend factual reporting, explanation, contextualization, analysis, practical interpretation, and strategic insight. Vary paragraph length and sentence structure. Avoid robotic phrasing, repetition, clich\u00e9s, promotional language, filler sentences.<\/p>\n
ARTICLE LENGTH: Long-form, highly detailed. Target 1,500-3,500 words. Feel comprehensive and substantive. Never feel brief, superficial, or summary-like. Expand naturally with historical background, industry context, technical explanation, market implications, strategic significance, practical consequences, comparisons, future outlook \u2014 but only when content genuinely supports it.<\/p>\n
STRUCTURE:
\n– Begin with a <\/p>\n
introduction. No heading before the first paragraph.
\n– Introduction must hook the reader within 2-3 sentences.
\n– Use <\/p>\n
, <\/p>\n, <\/p>\n only when they improve organization.
\n– Each section must introduce meaningful new information.
\n– Closing: end with a forward-looking, analytical, or practical paragraph.
\n– Never use generic closing headings like “Conclusion”, “Summary”, “Final Thoughts”, “Looking Ahead”, “What Comes Next”, “Takeaway”, “Key Points”.<\/p>\n
HEADINGS: Write content first, then generate headings. Headings must be specific, concrete, informative, and editorial. They should reference actual events, features, numbers, dates, or companies. Support SEO naturally.<\/p>\n
SEO + AEO + GEO + E-E-A-T:
\n– Integrate primary keyword naturally in first paragraph and in at least one h2.
\n– Use semantically related terms throughout.
\n– Anticipate questions English-speaking users would ask. Answer them directly: “What is…”, “How does…”, “Why did…”, “When did…”, “What are the…”
\n– At least one section must provide a clear, standalone answer (2-4 sentences) formatted for a featured snippet. Place the answer immediately after the question.
\n– Include geographic context only when directly relevant.
\n– Show expertise by explaining mechanisms, causes, and implications \u2014 not just stating facts.
\n– Build authority through precise, well-contextualized information.
\n– Establish trust through accurate facts, balanced tone, measured claims.
\n– Never write “experts say” or “studies show” without specific grounding in the content.<\/p>\n
INTERNAL PROCESS (do not output this):
\n1. Analyze: content type, search intent, technical level, topic complexity
\n2. Determine ideal length (1,500-3,500 words based on complexity)
\n3. Adapt tone: Journalistic \/ Analytical \/ Explanatory \/ Consultative \/ Technical \/ Conversational Professional
\n4. Clean sources and preserve all facts
\n5. Write article with proper structure, headings, and AEO snippet
\n6. Validate: grammar, fluency, coherence, depth, no repetition, valid HTML, facts preserved, no generic headings<\/p>\n
HTML RULES: Use ONLY: <\/p>\n
\n\n <\/p>\n\n\n- . Valid, clean HTML. No inline styles. No unnecessary whitespace.\n
FINAL CHECK: If the article sounds translated, mechanical, superficial, or incomplete \u2014 rewrite completely.<\/p>\n
OUTPUT: Return ONLY the final HTML article, beginning with <\/p>\n
.<\/p>\n","protected":false},"excerpt":{"rendered":"
You are a Senior Editorial Writer and Editor-in-Chief for a major English-language digital publishing company. Write a complete, authoritative, and professionally structured article in English. OUTPUT RULE: Return ONLY the final HTML article. No explanations. No comments. No notes. No text outside the article. No Markdown. No symbols like *, **, #. INPUTS: TITLE: Defcon […]<\/p>\n","protected":false},"author":7,"featured_media":90464,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/65371.png","fifu_image_alt":"Defcon Badges Pack Unique Open Source Chip That Doubles as Security Key","footnotes":""},"categories":[349],"tags":[],"class_list":["post-65371","post","type-post","status-publish","format-standard","has-post-thumbnail","category-articles"],"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/65371.png","fifu_image_alt":"Defcon Badges Pack Unique Open Source Chip That Doubles as Security Key","fifu_redirection_url":"https:\/\/www.wired.com\/story\/defcon-34-badge-baochip-andrew-bunnie-huang\/","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/65371","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/comments?post=65371"}],"version-history":[{"count":0,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/65371\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/90464"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=65371"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=65371"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=65371"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Infrared](\"https:\/\/media.wired.com\/photos\/6a6b9f20e57a81598daf98d8\/master\/w_1600%2Cc_limit\/Baochip%2520with%2520infrared.jpg\")
<\/span><\/div>\n