# Bitcoin Projects at AI Tinkerers

> Canonical HTML: https://aitinkerers.org/technologies/bitcoin
> Markdown URL: https://aitinkerers.org/technologies/bitcoin.md
> Technology record last updated: 2026-02-23T20:58:03Z
> Generated: 2026-09-21T06:41:56Z

Bitcoin is the first decentralized digital currency (BTC): a peer-to-peer electronic cash system operating without a central bank or single administrator.

Bitcoin is a revolutionary digital asset, launched in 2009 by the pseudonymous Satoshi Nakamoto, designed to solve the 'double-spending' problem for online payments. It operates on a public, distributed ledger called the blockchain, which is secured by a Proof-of-Work (PoW) consensus mechanism. This technology allows for direct, trustless transactions between two parties globally, bypassing traditional financial institutions. A key feature is its programmed scarcity: the total supply is hard-capped at 21 million coins, preventing inflation via arbitrary minting. It functions as a store of value and a medium of exchange, tracked on a transparent, immutable record.

- Official technology site: https://bitcoin.org
- Public AI Tinkerers demos and talks: 1
- Result page: 1 of 1

## Recent Public Talks and Demos

### [Design → Agentic UI Parity: Verifiable Figma/XD → MCP App UIs using constraint manifests + template registries](https://nyc.aitinkerers.org/talks/rsvp_ISg04Sc9n2Q)

We’ll demo a verifiable pipeline that translates Figma/Adobe XD designs into constraints + tokens + responsive rules, generates interactive MCP App UIs, and produces a design parity report (auditable) that proves the shipped UI honors design intent across breakpoints. What we’re building (technical, grounded) A design-to-agentic-UI system with four primitives: Design ingestion (Figma/XD) Extract design tokens (color, type scale, spacing), component semantics (buttons, cards, nav), and layout intent (grid, alignment, density). Convert to a normalized Design Intent Spec (DIS). Template registry (universal UI templates) A library of parametric templates (layout archetypes + interaction patterns). Templates accept tokens + constraints and output UI code. Constraint manifest (the verification core) A machine-readable manifest that encodes: Layout constraints (grid columns, min/max widths, padding rules, alignment invariants) Responsive rules (breakpoints, reflow behavior, truncation rules, priority ordering) Component contracts (required states, accessibility expectations, interaction affordances) This manifest is the “source of truth” the generator must satisfy. MCP App UI runtime The UI is delivered as an MCP App (interactive UI inside the client) with explicit tool bindings (UI actions → tool calls). The same manifest drives both generation and verification. The verification mechanism (non-brittle parity checks) We’ll show two complementary verification layers that go beyond “apply tokens”: A) Structural / rule-based verification (fast, deterministic) Compile DIS → constraint assertions per breakpoint: e.g., “card grid is 1-col under 640px, 2-col under 1024px, 3-col above” “primary CTA remains above the fold on mobile” “nav collapses into drawer with N max items visible” Verify the generated UI against these assertions by analyzing: template parameters used layout tree structure computed layout properties for each breakpoint (from the rendered DOM snapshot) B) Visual / perceptual verification (tolerant, non-brittle) Render both: design reference (from Figma/XD export frames) generated UI (MCP App UI at the same viewport sizes) Compute similarity using: a perceptual diff (SSIM/LPIPS-style) and bounding-box alignment checks for key components (header, CTA, cards) Output a parity score per breakpoint + annotated diffs. The auditable output (what we’ll “pop the hood” on) A concrete engineering artifact called a Design Parity Report, containing: tokens applied (hashes + versions) template IDs and parameters used constraint manifest version parity scores per breakpoint annotated diffs for any violations remediation hints (“use Template X instead of Y”, “tighten padding constraint at md breakpoint”) This report is logged as an append-only, auditable event alongside the UI artifact, so teams can prove what changed, why it changed, and whether parity improved or regressed over time. What we’ll demo live (5 minutes) Start with a Figma/XD screen (desktop + mobile frames). Ingest → generate interactive MCP App UI. Run the parity checker across 3 breakpoints. Show the Design Parity Report + one intentional failure (e.g., CTA drops below fold on mobile). Fix by changing a constraint or swapping template → re-run → parity passes.

- Event context: Feb Demo Day: How are you turning design into code? (with Baz) — 2026-02-04 — New York City
- Public talk page: https://nyc.aitinkerers.org/talks/rsvp_ISg04Sc9n2Q

## Related Technologies

- [Adobe XD](https://aitinkerers.org/technologies/adobe-xd) ([Markdown](https://aitinkerers.org/technologies/adobe-xd.md)) — 2 public demos
- [CSS](https://aitinkerers.org/technologies/css) ([Markdown](https://aitinkerers.org/technologies/css.md)) — 6 public demos
- [ERC-8004](https://aitinkerers.org/technologies/erc-8004) ([Markdown](https://aitinkerers.org/technologies/erc-8004.md)) — 2 public demos
- [Figma](https://aitinkerers.org/technologies/figma) ([Markdown](https://aitinkerers.org/technologies/figma.md)) — 6 public demos
- [Liquid UI](https://aitinkerers.org/technologies/liquid-ui) ([Markdown](https://aitinkerers.org/technologies/liquid-ui.md)) — 1 public demo
- [MCP](https://aitinkerers.org/technologies/mcp) ([Markdown](https://aitinkerers.org/technologies/mcp.md)) — 129 public demos
- [MCP server](https://aitinkerers.org/technologies/mcp-server) ([Markdown](https://aitinkerers.org/technologies/mcp-server.md)) — 3 public demos
- [Prompts](https://aitinkerers.org/technologies/prompts) ([Markdown](https://aitinkerers.org/technologies/prompts.md)) — 6 public demos
- [Runtime](https://aitinkerers.org/technologies/runtime) ([Markdown](https://aitinkerers.org/technologies/runtime.md)) — 10 public demos
- [Server](https://aitinkerers.org/technologies/server) ([Markdown](https://aitinkerers.org/technologies/server.md)) — 6 public demos
- [Tokens](https://aitinkerers.org/technologies/tokens) ([Markdown](https://aitinkerers.org/technologies/tokens.md)) — 3 public demos
