{ "projectName": "Immutable Mobile Terminal", "nodes": [ { "id": "application_processor_soc", "name": "Main Application Processor", "productName": "NXP i.MX 8M Plus (MIMX8ML8DVNLZAB)", "category": "electrical", "type": "mcu", "pins": [ "VDD_ARM", "VDD_SOC", "DRAM_DATA", "PCIE_TX", "PCIE_RX", "MIPI_DSI_TX", "MIPI_CSI_RX", "USB1_DN", "USB1_DP", "I2C1_SCL", "I2C1_SDA", "SPI1_MOSI", "SPI1_MISO", "SPI1_SCLK", "SPI1_SS0", "UART1_TX", "UART1_RX", "GPIO_1" ], "dimensions": "15x15x1.2mm", "quantity": 1, "estimatedCost": 42.5, "purchaseUrl": "https://www.digikey.com/en/products/result?keywords=MIMX8ML8DVNLZAB", "partId": "fec2bb89-4b51-4dd1-a6e4-618ae95ddeaf", "aliexpressUrl": "https://s.click.aliexpress.com/e/_c2vuJvYN", "research": { "sourcing": [ { "vendor": "Amazon", "url": "" }, { "vendor": "AliExpress", "url": "https://www.aliexpress.com/w/wholesale-nxp-i-mx-8m-plus-8mpevk.html" } ] }, "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=NXP+i.MX+8M+Plus+%28MIMX8ML8DVNLZAB%29&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1", "imageUrl": "https://imgs.search.brave.com/gguIvOdhg-H6L11_Jxar81aurittFH1bdZ-NpeV5ClE/rs:fit:500:0:1:0/g:ce/aHR0cHM6Ly93d3cu/ZW1iZWRkZWRhcnRp/c3RzLmNvbS93cC1j/b250ZW50L3VwbG9h/ZHMvMjAxOC8wNC9p/bXg3ZF9jb21fZnJv/bnRfNTQweDMzMy01/NDB4MzMzLnBuZw" }, { "id": "discrete_hsm", "name": "Hardware Security Module", "productName": "Microchip ATECC608B-TFLXTLS", "category": "electrical", "type": "module", "pins": [ "SDA", "SCL", "GND", "VCC" ], "dimensions": "3x2x0.6mm", "quantity": 1, "estimatedCost": 1.2, "purchaseUrl": "https://www.digikey.com/en/products/result?keywords=ATECC608B-TFLXTLS", "partId": "57a59ce2-9e56-4896-8a5c-03d24040ca78", "imageUrl": "https://m.media-amazon.com/images/I/31sZRq-JD9L._SL500_.jpg", "aliexpressUrl": "https://s.click.aliexpress.com/e/_c2yOOlWN", "research": { "sourcing": [ { "vendor": "AliExpress", "url": "https://www.aliexpress.com/w/wholesale-microchip-atecc608b-tflxtls.html" }, { "vendor": "Amazon", "url": "" }, { "vendor": "Amazon", "url": "https://www.amazon.com/dp/B0FNB49H6D?tag=blueprintam-20&linkCode=osi&th=1&psc=1", "price": "$47.67" } ] }, "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=Microchip+ATECC608B-TFLXTLS&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "nfc_transceiver", "name": "NFC Secure Reader", "productName": "STMicroelectronics ST25R3916B-AQFT", "category": "electrical", "type": "module", "pins": [ "RFI1", "RFI2", "RFO1", "RFO2", "SPI_MISO", "SPI_MOSI", "SPI_SCLK", "SPI_SS", "IRQ", "VDD", "VSS" ], "dimensions": "5x5x0.85mm", "quantity": 1, "estimatedCost": 3.8, "purchaseUrl": "https://www.digikey.com/en/products/result?keywords=ST25R3916B-AQFT", "partId": "3eb114ee-0802-45ea-ace0-db8089e3f9e7", "imageUrl": "https://m.media-amazon.com/images/I/41A1pQMwYrL._SL500_.jpg", "aliexpressUrl": "https://s.click.aliexpress.com/e/_c4kopEfX", "research": { "sourcing": [ { "vendor": "Amazon", "url": "https://www.amazon.com/dp/B0748MNSYK?tag=blueprintam-20&linkCode=osi&th=1&psc=1", "price": "$69.95" }, { "vendor": "AliExpress", "url": "https://www.aliexpress.com/w/wholesale-st25r3911b-stmicroelectronics.html" } ] }, "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=STMicroelectronics+ST25R3916B-AQFT&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "fingerprint_sensor", "name": "Biometric Fingerprint Sensor", "productName": "Synaptics FS4600", "category": "electrical", "type": "sensor", "pins": [ "VDD", "GND", "SPI_MOSI", "SPI_MISO", "SPI_CLK", "SPI_CS", "INT", "RESET" ], "dimensions": "10x10x1.5mm", "quantity": 1, "estimatedCost": 12.5, "purchaseUrl": "https://www.digikey.com/en/products/result?keywords=Synaptics+Fingerprint+Sensor", "partId": "59f285d4-a274-4c55-a218-4821b422e915", "imageUrl": "https://imgs.search.brave.com/ixYbz39ddL1P0T7HipP2AixmYxsvHyUJPA2c6LFLZcU/rs:fit:500:0:1:0/g:ce/aHR0cHM6Ly93d3cu/YW5kcm9pZGF1dGhv/cml0eS5jb20vd3At/Y29udGVudC91cGxv/YWRzLzIwMTgvMDEv/U3luYXB0aWNzLUNs/ZWFyLUlELUZTOTUw/MC1maW5nZXJwcmlu/dC1zZW5zb3ItVml2/by1BQS0zLmpwZw", "aliexpressUrl": "https://s.click.aliexpress.com/e/_c2uD9aSt", "research": { "sourcing": [ { "vendor": "AliExpress", "url": "https://www.aliexpress.com/w/wholesale-synaptics-fs9500.html" }, { "vendor": "Amazon", "url": "" } ] }, "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=Synaptics+FS4600&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "touchscreen_display", "name": "High-Res Touchscreen Display", "productName": "Adafruit 5.0 inch TFT Display with Capacitive Touch (ST7701S / GT911)", "category": "electrical", "type": "display", "pins": [ "MIPI_D0_P", "MIPI_D0_N", "MIPI_CLK_P", "MIPI_CLK_N", "VDD", "GND", "SDA", "SCL", "INT", "RESET" ], "dimensions": "121x76x4.2mm", "quantity": 1, "estimatedCost": 39.95, "purchaseUrl": "https://www.adafruit.com/product/4421", "partId": "38640c42-c254-4bba-8a72-c491ea2815a2", "imageUrl": "https://m.media-amazon.com/images/I/312wHnB1XHL._SL500_.jpg", "aliexpressUrl": "https://s.click.aliexpress.com/e/_c3Vf7BY9", "research": { "sourcing": [ { "vendor": "AliExpress", "url": "https://www.aliexpress.com/w/wholesale-5-0-inch-ips-tft-lcd-with-capacitive-touch-st7701s-driver-gt911-touch.html" }, { "vendor": "Amazon", "url": "https://www.amazon.com/dp/B0FB48G5V9?tag=blueprintam-20&linkCode=osi&th=1&psc=1", "price": "$24.24" }, { "vendor": "Amazon", "url": "https://www.amazon.com/dp/B0DNNC3WQ1?tag=blueprintam-20&linkCode=osi&th=1&psc=1", "price": "$21.11" } ] }, "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=Adafruit+5.0+inch+TFT+Display+with+Capacitive+Touch+%28ST7701S+%2F+GT911%29&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "wireless_module", "name": "Wi-Fi and Bluetooth Module", "productName": "Murata LBEE5XV1YM-539", "category": "electrical", "type": "module", "pins": [ "SDIO_CLK", "SDIO_CMD", "SDIO_DATA0", "SDIO_DATA1", "SDIO_DATA2", "SDIO_DATA3", "UART_TXD", "UART_RXD", "UART_RTS", "UART_CTS", "VIN", "GND" ], "dimensions": "11.4x7.9x1.4mm", "quantity": 1, "estimatedCost": 14.2, "purchaseUrl": "https://www.digikey.com/en/products/result?keywords=LBEE5XV1YM", "partId": "5ded1c70-a1e2-4b37-b050-af344c058e62", "imageUrl": "https://imgs.search.brave.com/ykV9InfV4UhoCMBwvMq0Z7_pKtQqPtiNTXU-E0PMOBo/rs:fit:500:0:1:0/g:ce/aHR0cHM6Ly9tbS5k/aWdpa2V5LmNvbS9W/b2x1bWUwL29wYXNk/YXRhL2QyMjAwMDEv/bWVkaWFzL2ltYWdl/cy83MTMxL01GR19M/QkVFMFpaMktMLTAw/MS5qcGc", "aliexpressUrl": "https://s.click.aliexpress.com/e/_c2w2ucwH", "research": { "sourcing": [ { "vendor": "Amazon", "url": "" }, { "vendor": "AliExpress", "url": "https://www.aliexpress.com/w/wholesale-murata-type-1zm-lbee5zz1zm-923.html" } ] }, "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=Murata+LBEE5XV1YM-539&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "pmic", "name": "Power Management IC", "productName": "NXP PCA9450CHN", "category": "electrical", "type": "power", "pins": [ "VIN", "BUCK1_OUT", "BUCK2_OUT", "LDO1_OUT", "LDO2_OUT", "I2C_SDA", "I2C_SCL", "ON_OFF", "RESET_B", "GND" ], "dimensions": "7x7x0.85mm", "quantity": 1, "estimatedCost": 3.4, "purchaseUrl": "https://www.digikey.com/en/products/result?keywords=PCA9450CHN", "partId": "7ba3784a-7364-4787-ba68-ecf629fd0003", "description": "Dedicated PMIC for i.MX 8M Mini, providing various regulated voltage rails.", "imageUrl": "https://imgs.search.brave.com/Md6rYYKKPDvxEM4w_CK9MiPIu5QVMrqksWI27ZbLDJQ/rs:fit:0:180:1:0/g:ce/aHR0cHM6Ly93d3cu/YWxsZGF0YXNoZWV0/Lm5ldC9odG1sZGF0/YXNoZWV0LzEyNDUx/MjYvTlhQL1BDQTk0/NTBDSE4vMTU3NC84/L1BDQTk0NTBDSE4u/Z2lm.jpeg", "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=NXP+PCA9450CHN&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "usb_c_pd_controller", "name": "USB-C Power Delivery Controller", "productName": "STMicroelectronics STUSB4500QTR", "category": "electrical", "type": "power", "pins": [ "VCONN", "CC1", "CC2", "VBUS", "I2C_SDA", "I2C_SCL", "RESET", "GND" ], "dimensions": "4x4x1mm", "quantity": 1, "estimatedCost": 1.85, "purchaseUrl": "https://www.digikey.com/en/products/result?keywords=STUSB4500QTR", "partId": "4bebd35a-4878-4d0e-a629-65083d83a6e1", "description": "Controller for USB-C Power Delivery negotiation, allowing flexible power input.", "imageUrl": "https://imgs.search.brave.com/6RgIWEDUrpMJPVmnnz9dWGloD2rZrHnsVOOXP80N4zY/rs:fit:500:0:1:0/g:ce/aHR0cHM6Ly9zdGF0/aWMuZGF0YXNoZWV0/cy5jb20vaW1hZ2Uv/OTg1NDE0My1zdG1p/Y3JvZWxlY3Ryb25p/Y3Mtc3R1c2I0NTAw/cXRyLWltYWdlLnBu/Zw", "aliexpressUrl": "https://s.click.aliexpress.com/e/_c42Sn1iv", "research": { "sourcing": [ { "vendor": "Amazon", "url": "" }, { "vendor": "AliExpress", "url": "https://www.aliexpress.com/w/wholesale-stmicroelectronics-stusb4500qtr.html" } ] }, "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=STMicroelectronics+STUSB4500QTR&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "active_discharge_switch", "name": "Fast Zeroization Power Switch", "productName": "Texas Instruments TPS22918DBVR", "category": "electrical", "type": "power", "pins": [ "VIN", "VOUT", "ON", "CT", "QOD", "GND" ], "dimensions": "2.9x1.6x1.1mm", "quantity": 1, "estimatedCost": 0.45, "purchaseUrl": "https://www.digikey.com/en/products/result?keywords=TPS22918DBVR", "partId": "b498dee1-03d4-4b0a-b149-1a0d93c61868", "imageUrl": "https://imgs.search.brave.com/ntqCcJhykNy4Zzhx0_mhhhTR-sGD_2h8FP00sHUzXcE/rs:fit:500:0:1:0/g:ce/aHR0cHM6Ly9hc3Nl/dHMubGNzYy5jb20v/aW1hZ2VzL2xjc2Mv/OTAweDkwMC8yMDIy/MTIzMV9UZXhhcy1J/bnN0cnVtZW50cy1M/UDI5ODUtNTBEQlZS/X0M3NDUxMV9iYWNr/LmpwZw", "aliexpressUrl": "https://s.click.aliexpress.com/e/_c4OqQmY9", "research": { "sourcing": [ { "vendor": "AliExpress", "url": "https://www.aliexpress.com/w/wholesale-texas-instruments-lp2985-18dbvr.html" }, { "vendor": "Amazon", "url": "" } ] }, "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=Texas+Instruments+TPS22918DBVR&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "optical_tamper_sensor", "name": "Optical Light Tamper Detector", "productName": "Broadcom APDS-9005-020", "category": "electrical", "type": "sensor", "pins": [ "OUT", "VCC", "GND" ], "dimensions": "2x2x0.6mm", "quantity": 2, "estimatedCost": 0.95, "purchaseUrl": "https://www.digikey.com/en/products/result?keywords=APDS-9005-020", "partId": "4f0b18b7-ded1-4369-b357-2bb6b0c5464f", "imageUrl": "https://imgs.search.brave.com/FKAVopu57Tpd4HugMhLSkcWp5zkqQikxU-UHa4hsglc/rs:fit:500:0:1:0/g:ce/aHR0cHM6Ly93d3cu/ZXRlaS5jb20vZmls/ZXMvdXBsb2Fkcy9w/cm9kdWN0L2ltZy8y/MDI0LzEyLzIyL3Mv/M2I5NTgxOTAzMmM1/NDgyYWE0MzM5NDEw/YWUyZjk5N2Yud2Vi/cA", "aliexpressUrl": "https://s.click.aliexpress.com/e/_c4NYl3pp", "research": { "sourcing": [ { "vendor": "AliExpress", "url": "https://www.aliexpress.com/w/wholesale-broadcom-apds-9301-001.html" }, { "vendor": "Amazon", "url": "" } ] }, "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=Broadcom+APDS-9005-020&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "main_chassis_midframe", "name": "CNC Aluminum Midframe", "productName": "Custom CNC 6061-T6 Aluminum Midframe", "category": "mechanical", "type": "structural", "description": "Precision CNC-milled aluminum midframe acting as the structural backbone, thermal heatsink, and internal shielding divider between RF and secure processing zones.", "dimensions": "155x75x6.5mm", "material": "6061-T6 Aluminum", "quantity": 1, "estimatedCost": 45, "purchaseUrl": "https://www.amazon.com/s?k=6061-T6+aluminum+sheet+plate", "partId": "17e51b8c-30f3-4309-8c7f-47e9cb391958", "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=Custom+CNC+6061-T6+Aluminum+Midframe&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "front_bezel_housing", "name": "Front Bezel Enclosure", "productName": "Polycarbonate Front Bezel", "category": "mechanical", "type": "enclosure", "description": "High-impact polycarbonate front bezel that secures the touchscreen display assembly and seals against dust and moisture ingress.", "dimensions": "158x78x4mm", "material": "Polycarbonate", "quantity": 1, "estimatedCost": 8.5, "purchaseUrl": "https://www.amazon.com/s?k=polycarbonate+sheet+1/8", "partId": "b533e1c0-944e-4cf8-8821-068845d07181", "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=Polycarbonate+Front+Bezel&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1", "research": { "specs": [ { "label": "Material", "value": "High-impact Polycarbonate (PC, UL 94 V-0 flame-retardant)" }, { "label": "External Dimensions", "value": "165.5 mm x 83.0 mm x 8.8 mm" }, { "label": "Internal Dimensions", "value": "158.5 mm x 76.2 mm x 6.5 mm" }, { "label": "Nominal Wall Thickness", "value": "2.2 mm" }, { "label": "Weight", "value": "31.5 grams" }, { "label": "Mounting Options", "value": "M2.5 brass heat-set inserts (6 points) and snap-fit alignment ribs" }, { "label": "Panel Cutout Locations", "value": "Primary display window (142 mm x 71 mm), lower-center fingerprint sensor aperture (12 mm x 12 mm)" }, { "label": "Sealing Method", "value": "Integrated perimeter groove for co-molded silicone elastomer gasket (IP67 compliant)" } ], "summary": "This Polycarbonate Front Bezel is a highly durable mechanical enclosure component designed to house and protect the touchscreen assembly of the mobile terminal. It features integrated mounting structures for secure attachment to the aluminum midframe and precise cutouts for the fingerprint sensor. Engineered with a dedicated gasket channel, it ensures reliable protection against dust and water ingress to achieve an IP67 rating.", "sourcing": [] } }, { "id": "display_mount_bracket", "name": "Display Mounting Bracket", "category": "mechanical", "type": "3d_printed", "description": "3D-printed internal support frame for precisely positioning the high-resolution touchscreen and routing its fragile ribbon cables.", "dimensions": "140x70x2mm", "material": "PETG", "printSettings": "100% infill, 0.15mm layer height, carbon-fiber composite recommended", "mountsFor": "touchscreen_display", "quantity": 1, "estimatedCost": 3, "purchaseUrl": "https://www.amazon.com/s?k=carbon+fiber+petg+filament+1.75mm" }, { "id": "rear_cover_shell", "name": "Rear Cover with Tamper Mesh Channels", "category": "mechanical", "type": "3d_printed", "description": "3D-printed impact-resistant rear outer shell featuring micro-channels on the inner surface for routing the active copper-wire tamper detection mesh.", "dimensions": "158x78x6mm", "material": "ABS", "printSettings": "40% infill, 0.2mm layer height, vapor-smoothed for weather resistance", "quantity": 1, "estimatedCost": 6.5, "purchaseUrl": "https://www.amazon.com/s?k=abs+filament+1.75mm+black" }, { "id": "optical_tamper_light_pipe", "name": "Optical Tamper Light Guide", "category": "mechanical", "type": "3d_printed", "description": "Bespoke optical guide printed in transparent PMMA-like material to direct internal light-path signals specifically across the seam line to the optical detector.", "dimensions": "12x8x6mm", "material": "PETG", "printSettings": "100% infill, 0.1mm layer height, clear/transparent filament", "mountsFor": "optical_tamper_sensor", "quantity": 1, "estimatedCost": 1.5, "purchaseUrl": "https://www.amazon.com/s?k=transparent+clear+petg+filament" }, { "id": "fingerprint_sensor_holder", "name": "Biometric Sensor Secure Holder", "category": "mechanical", "type": "3d_printed", "description": "Specialized internal structural holder that isolates and rigidly clamps the fingerprint sensor against the outer frame aperture.", "dimensions": "16x16x4mm", "material": "PETG", "printSettings": "100% infill, 0.1mm layer height", "mountsFor": "fingerprint_sensor", "quantity": 1, "estimatedCost": 1.2, "purchaseUrl": "https://www.amazon.com/s?k=petg+filament+1.75mm" }, { "id": "nfc_antenna_spacer", "name": "NFC Antenna Ferrite Spacer", "category": "mechanical", "type": "3d_printed", "description": "Non-conductive, RF-transparent spacer block that isolates the NFC reader and antenna from the aluminum midframe to prevent signal attenuation.", "dimensions": "42x35x2.5mm", "material": "PLA", "printSettings": "20% infill, 0.2mm layer height", "mountsFor": "nfc_transceiver", "quantity": 1, "estimatedCost": 1, "purchaseUrl": "https://www.amazon.com/s?k=pla+filament+1.75mm" }, { "id": "wireless_antenna_isolator", "name": "RF Antenna Isolation Frame", "category": "mechanical", "type": "3d_printed", "description": "Isolating sub-frame designed to hold the Wi-Fi/Bluetooth antenna modules at a fixed clearance distance from ground planes.", "dimensions": "32x15x5mm", "material": "PLA", "printSettings": "30% infill, 0.15mm layer height", "mountsFor": "wireless_module", "quantity": 1, "estimatedCost": 1.1, "purchaseUrl": "https://www.amazon.com/s?k=pla+filament+1.75mm" }, { "id": "hsm_shield_can", "name": "HSM Physical Shielding Can", "productName": "Laird Technologies PCB Shielding Can", "category": "mechanical", "type": "structural", "description": "Tin-plated steel RF/EMI shield cover that solders directly to the PCB over the secure element to block electromagnetic side-channel attacks and physical probing.", "dimensions": "25x25x4.5mm", "material": "Tin-Plated Steel", "mountsFor": "discrete_hsm", "quantity": 1, "estimatedCost": 2.4, "purchaseUrl": "https://www.amazon.com/s?k=pcb+shield+can", "partId": "cc74a8d8-060f-43fc-8134-498c2c9c617b", "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=Laird+Technologies+PCB+Shielding+Can&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "assembly_screws", "name": "Enclosure Assembly Screws", "productName": "M1.6 Torx T5 Machine Screws", "category": "mechanical", "type": "misc", "description": "High-tensile security micro-screws used to fasten the outer polycarbonate bezel and rear shell securely to the aluminum midframe.", "dimensions": "M1.6x6mm", "material": "304 Stainless Steel", "quantity": 12, "estimatedCost": 0.15, "purchaseUrl": "https://www.amazon.com/s?k=M1.6+torx+screws+stainless+steel", "partId": "9a86243e-e179-458a-a00b-f836c3e2d974", "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=M1.6+Torx+T5+Machine+Screws&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "internal_thread_inserts", "name": "Brass Threaded Heat-Set Inserts", "productName": "M1.6 Brass Threaded Inserts", "category": "mechanical", "type": "misc", "description": "Heat-set brass inserts installed into the polycarbonate parts to provide rugged, reusable threads for security screws.", "dimensions": "M1.6x2.5mm", "material": "Brass", "quantity": 12, "estimatedCost": 0.18, "purchaseUrl": "https://www.amazon.com/dp/B0DTTMBS9K?tag=blueprintam-20&linkCode=osi&th=1&psc=1", "partId": "322e9631-b1af-4ce7-8eaf-af0229f03471", "imageUrl": "https://m.media-amazon.com/images/I/41AGID00IsL._SL500_.jpg", "aliexpressUrl": "https://s.click.aliexpress.com/e/_c3R5kxop", "research": { "sourcing": [ { "vendor": "AliExpress", "url": "https://www.aliexpress.com/w/wholesale-m1-6-brass-threaded-inserts.html" }, { "vendor": "Amazon", "url": "" }, { "vendor": "Amazon", "url": "https://www.amazon.com/dp/B0DTTMBS9K?tag=blueprintam-20&linkCode=osi&th=1&psc=1", "price": "$8.49" } ] }, "ebayUrl": "https://www.ebay.com/sch/i.html?_nkw=M1.6+Brass+Threaded+Inserts&_sacat=0&_from=R40&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339153059&customid=blueprint&toolid=10001&mkevt=1" }, { "id": "application_processor_soc_mount", "name": "Main Application Processor Mount", "category": "mechanical", "type": "3d_printed", "mountsFor": "application_processor_soc", "description": "Standoff bracket sized to the Main Application Processor's mounting hole pattern. M2.5 holes for board fasteners; vented underside for airflow.", "material": "PETG", "printSettings": "30% infill, 0.2mm layer, 4 perimeters", "quantity": 1, "estimatedCost": 2, "purchaseUrl": "", "dimensions": "60x40x12mm" } ], "electricalConnections": [ { "source": "pmic", "target": "application_processor_soc", "type": "power", "voltage": "1.2V", "current": "2.5A", "label": "VDD_ARM Core Power" }, { "source": "pmic", "target": "application_processor_soc", "type": "power", "voltage": "1.8V", "current": "1.5A", "label": "VDD_SOC I/O Power" }, { "source": "pmic", "target": "active_discharge_switch", "type": "power", "voltage": "3.3V", "current": "500mA", "label": "Secured Peripherals Switch Supply" }, { "source": "active_discharge_switch", "target": "discrete_hsm", "type": "power", "voltage": "3.3V", "current": "100mA", "label": "Zeroizable HSM VCC" }, { "source": "active_discharge_switch", "target": "fingerprint_sensor", "type": "power", "voltage": "3.3V", "current": "50mA", "label": "Zeroizable Biometric Power" }, { "source": "pmic", "target": "nfc_transceiver", "type": "power", "voltage": "3.3V", "current": "150mA", "label": "NFC Transceiver VDD" }, { "source": "pmic", "target": "touchscreen_display", "type": "power", "voltage": "3.3V", "current": "500mA", "label": "Display VDD" }, { "source": "pmic", "target": "wireless_module", "type": "power", "voltage": "3.3V", "current": "800mA", "label": "Wireless Module Power" }, { "source": "pmic", "target": "optical_tamper_sensor", "type": "power", "voltage": "3.3V", "current": "10mA", "label": "Tamper Sensor VCC" }, { "source": "usb_c_pd_controller", "target": "pmic", "type": "power", "voltage": "5V", "current": "3A", "label": "System Input VBUS" }, { "source": "application_processor_soc", "target": "discrete_hsm", "type": "data", "protocol": "i2c", "sourcePin": "I2C1_SCL", "targetPin": "SCL", "label": "HSM I2C Clock" }, { "source": "application_processor_soc", "target": "discrete_hsm", "type": "data", "protocol": "i2c", "sourcePin": "I2C1_SDA", "targetPin": "SDA", "label": "HSM I2C Data" }, { "source": "application_processor_soc", "target": "nfc_transceiver", "type": "data", "protocol": "spi", "sourcePin": "SPI1_MOSI", "targetPin": "SPI_MOSI", "label": "NFC SPI MOSI" }, { "source": "application_processor_soc", "target": "nfc_transceiver", "type": "data", "protocol": "spi", "sourcePin": "SPI1_MISO", "targetPin": "SPI_MISO", "label": "NFC SPI MISO" }, { "source": "application_processor_soc", "target": "nfc_transceiver", "type": "data", "protocol": "spi", "sourcePin": "SPI1_SCLK", "targetPin": "SPI_SCLK", "label": "NFC SPI Clock" }, { "source": "application_processor_soc", "target": "nfc_transceiver", "type": "data", "protocol": "spi", "sourcePin": "SPI1_SS0", "targetPin": "SPI_SS", "label": "NFC SPI Chip Select" }, { "source": "application_processor_soc", "target": "fingerprint_sensor", "type": "data", "protocol": "spi", "sourcePin": "SPI1_MOSI", "targetPin": "SPI_MOSI", "label": "Fingerprint SPI MOSI" }, { "source": "application_processor_soc", "target": "fingerprint_sensor", "type": "data", "protocol": "spi", "sourcePin": "SPI1_MISO", "targetPin": "SPI_MISO", "label": "Fingerprint SPI MISO" }, { "source": "application_processor_soc", "target": "fingerprint_sensor", "type": "data", "protocol": "spi", "sourcePin": "SPI1_SCLK", "targetPin": "SPI_CLK", "label": "Fingerprint SPI Clock" }, { "source": "application_processor_soc", "target": "fingerprint_sensor", "type": "data", "protocol": "gpio", "sourcePin": "GPIO_1", "targetPin": "SPI_CS", "label": "Fingerprint SPI Chip Select" }, { "source": "application_processor_soc", "target": "touchscreen_display", "type": "data", "protocol": "dsi", "sourcePin": "MIPI_DSI_TX", "targetPin": "MIPI_D0_P", "label": "Display DSI Lane" }, { "source": "application_processor_soc", "target": "touchscreen_display", "type": "data", "protocol": "i2c", "sourcePin": "I2C1_SCL", "targetPin": "SCL", "label": "Touchscreen I2C Clock" }, { "source": "application_processor_soc", "target": "touchscreen_display", "type": "data", "protocol": "i2c", "sourcePin": "I2C1_SDA", "targetPin": "SDA", "label": "Touchscreen I2C Data" }, { "source": "application_processor_soc", "target": "wireless_module", "type": "data", "protocol": "uart", "sourcePin": "UART1_TX", "targetPin": "UART_RXD", "label": "WLAN/BT UART TX" }, { "source": "application_processor_soc", "target": "wireless_module", "type": "data", "protocol": "uart", "sourcePin": "UART1_RX", "targetPin": "UART_TXD", "label": "WLAN/BT UART RX" }, { "source": "optical_tamper_sensor", "target": "active_discharge_switch", "type": "data", "protocol": "gpio", "sourcePin": "OUT", "targetPin": "ON", "label": "Tamper Event Trigger to Cut Power" }, { "source": "application_processor_soc", "target": "pmic", "type": "data", "protocol": "i2c", "sourcePin": "I2C1_SCL", "targetPin": "I2C_SCL", "label": "PMIC Control Bus SCL" }, { "source": "application_processor_soc", "target": "pmic", "type": "data", "protocol": "i2c", "sourcePin": "I2C1_SDA", "targetPin": "I2C_SDA", "label": "PMIC Control Bus SDA" }, { "source": "application_processor_soc", "target": "usb_c_pd_controller", "type": "data", "protocol": "i2c", "sourcePin": "I2C1_SCL", "targetPin": "I2C_SCL", "label": "USB-PD Control SCL" }, { "source": "application_processor_soc", "target": "usb_c_pd_controller", "type": "data", "protocol": "i2c", "sourcePin": "I2C1_SDA", "targetPin": "I2C_SDA", "label": "USB-PD Control SDA" }, { "source": "pmic", "target": "usb_c_pd_controller", "type": "power", "voltage": "1.2V", "sourcePin": "VIN", "targetPin": "VBUS" }, { "source": "pmic", "target": "active_discharge_switch", "type": "power", "sourcePin": "GND", "targetPin": "GND" }, { "source": "active_discharge_switch", "target": "discrete_hsm", "type": "power", "sourcePin": "GND", "targetPin": "GND" }, { "source": "active_discharge_switch", "target": "fingerprint_sensor", "type": "power", "sourcePin": "GND", "targetPin": "GND" }, { "source": "pmic", "target": "nfc_transceiver", "type": "power", "sourcePin": "GND", "targetPin": "VSS" }, { "source": "pmic", "target": "touchscreen_display", "type": "power", "sourcePin": "GND", "targetPin": "GND" }, { "source": "pmic", "target": "wireless_module", "type": "power", "sourcePin": "GND", "targetPin": "GND" }, { "source": "pmic", "target": "optical_tamper_sensor", "type": "power", "sourcePin": "GND", "targetPin": "GND" }, { "source": "usb_c_pd_controller", "target": "pmic", "type": "power", "sourcePin": "GND", "targetPin": "GND" } ], "mechanicalConnections": [ { "source": "front_bezel_housing", "target": "main_chassis_midframe", "label": "M1.6 screws", "delta": { "x": 0, "y": -5.2, "z": 1.5 } }, { "source": "display_mount_bracket", "target": "main_chassis_midframe", "label": "M1.4 screws", "delta": { "x": 0, "y": 2.3, "z": 0.5 } }, { "source": "rear_cover_shell", "target": "main_chassis_midframe", "label": "assembly_screws into internal_thread_inserts", "delta": { "x": 0, "y": -0.2, "z": -1.5 } }, { "source": "internal_thread_inserts", "target": "main_chassis_midframe", "label": "heat-set press fit", "delta": { "x": 0, "y": 0, "z": 0 }, "rotation": { "x": 90, "y": 0, "z": 0 } }, { "source": "optical_tamper_light_pipe", "target": "rear_cover_shell", "label": "snap-fit retention clips", "delta": { "x": 0, "y": 0, "z": 0 } }, { "source": "fingerprint_sensor_holder", "target": "front_bezel_housing", "label": "M1.4 screws", "delta": { "x": 0, "y": 4, "z": 0 } }, { "source": "nfc_antenna_spacer", "target": "rear_cover_shell", "label": "pressure-sensitive adhesive tape", "delta": { "x": 0, "y": 4.3, "z": 0 } }, { "source": "wireless_antenna_isolator", "target": "main_chassis_midframe", "label": "snap-fit", "delta": { "x": 0, "y": 5.8, "z": 0 } }, { "source": "hsm_shield_can", "target": "main_chassis_midframe", "label": "M2 bolts", "delta": { "x": 0, "y": 5.5, "z": 0 } }, { "source": "application_processor_soc_mount", "target": "main_chassis_midframe", "label": "M2 screws", "delta": { "x": 0, "y": 9.3, "z": 0 } }, { "source": "assembly_screws", "target": "rear_cover_shell", "label": "through-hole insertion", "delta": { "x": 0, "y": 0, "z": 0 } }, { "source": "display_mount_bracket", "target": "touchscreen_display", "label": "mount", "delta": { "x": 0, "y": 3.1, "z": 0 } }, { "source": "optical_tamper_light_pipe", "target": "optical_tamper_sensor", "label": "mount", "delta": { "x": 0, "y": -3.3, "z": 0 } }, { "source": "fingerprint_sensor_holder", "target": "fingerprint_sensor", "label": "mount", "delta": { "x": 0, "y": -1.2, "z": 0 } }, { "source": "nfc_antenna_spacer", "target": "nfc_transceiver", "label": "mount", "delta": { "x": 0, "y": -1.7, "z": 0 } }, { "source": "wireless_antenna_isolator", "target": "wireless_module", "label": "mount", "delta": { "x": 0, "y": 1.8, "z": 0 } }, { "source": "hsm_shield_can", "target": "discrete_hsm", "label": "mount", "delta": { "x": 0, "y": -1.9, "z": 0 } }, { "source": "application_processor_soc_mount", "target": "application_processor_soc", "label": "mount", "delta": { "x": 0, "y": 5.4, "z": 0 } }, { "source": "front_bezel_housing", "target": "active_discharge_switch", "label": "attached", "delta": { "x": 0, "y": 0, "z": 2.6 } }, { "source": "front_bezel_housing", "target": "pmic", "label": "attached", "delta": { "x": 0, "y": 0, "z": 2.4 } }, { "source": "front_bezel_housing", "target": "usb_c_pd_controller", "label": "attached", "delta": { "x": 0, "y": -1.5, "z": 0 } } ], "projectDescription": "An interchangeable, zero-trust mobile terminal that secures decentralized identity without storing persistent user data. It utilizes an ARM-based application processor, a discrete hardware security module with physical tamper-detection mesh channels, an NFC wallet reader, biometric authentication, and an active zeroization circuit to wipe ephemeral session keys instantly.", "imagePromptSnapshot": { "description": "Project idea: ## Overview\n\nThis document defines a system architecture for a \"stateless\" or \"immutable\" smartphone in which persistent user data never resides on any single device. Instead, data is sharded, encrypted, and distributed across a compute/storage network, and user identity and data access are bound to a cryptographic wallet rather than to any physical handset. The device becomes an ephemeral, interchangeable rendering and I/O terminal — a \"thin hardware client\" for a decentralized backend. The architecture is organized into four layers: hardware root of trust, wallet-based identity and authentication, sharded storage and compute, and the application marketplace runtime.\n\n## Design Goals and Threat Model\n\nThe core design goal is that compromising, stealing, or physically destroying any single device should not expose or destroy user data, and any compliant device on the network should be able to \"become\" the user's phone the moment a wallet is authenticated. This inverts the conventional mobile threat model: instead of protecting data at rest on a single device, the priority shifts to (1) protecting the wallet keys/credentials that authorize access, (2) protecting data in transit and at rest across many untrusted third-party nodes, and (3) ensuring the local device itself is not a persistent target because it holds nothing of lasting value once a session ends. Attackers to defend against include device theft/forensic extraction, malicious or compromised storage/compute nodes in the network, man-in-the-middle session hijacking, side-channel and fault-injection attacks against the local secure hardware, and supply-chain tampering during manufacturing.\n\n## Layer 1: Hardware Root of Trust and Secure Enclave\n\nEvery device needs an immutable, chip-fabricated hardware root of trust that anchors a verified boot chain, since software alone cannot be trusted to bootstrap trust in itself. Following the pattern used in Apple's Secure Enclave and Qualcomm/ARM designs, the Boot ROM is burned in silicon at fabrication and holds the manufacturer's root public key; it verifies the first-stage bootloader's signature before executing it, and each subsequent stage verifies the next, forming an unbroken chain of trust up to the OS kernel. A dedicated, physically isolated secure coprocessor — analogous to Apple's Secure Enclave or an ARM TrustZone-based Trusted Execution Environment (TEE) — should run independently of the main application processor, with its own boot ROM, RAM, and hardware AES engine, so that even a fully compromised main OS cannot directly access enclave secrets.[1][2][3][4][5][6]\n\nBecause this device is explicitly \"immutable\" in the sense of holding no persistent user data, the secure enclave's job is narrower than in conventional phones: it does not need to protect a large local data vault, but it must protect three things that are highly sensitive even if ephemeral: the session's derived key-share material, biometric templates used for local wallet unlock, and the device's unique hardware identity keys used to attest to the network that this is a genuine, unmodified device. TrustZone's split into \"Secure World\" and \"Normal World\" execution environments, enforced by hardware bus-level access controls rather than software permissions, is well suited to isolating this key material from the Android/Linux-style normal-world OS running the marketplace app runtime.[2][7][1]\n\n### Physical Tamper and Side-Channel Resistance\n\nBecause devices in this network are commodity, interchangeable, and potentially used by many different wallet-holders over their lifetime (e.g., loaner devices, kiosks, secondhand units), physical tamper resistance matters more than in a single-owner phone. Recommended hardware countermeasures include:\n\n- Physically Unclonable Functions (PUFs) to derive a device-unique fingerprint from manufacturing-level silicon variations, giving each unit an unforgeable identity that cannot be cloned even by the manufacturer.[8][9]\n- Active mesh tamper-detection shielding and voltage/clock-glitch and power side-channel countermeasures (constant-time crypto operations, power-analysis-resistant AES cores) around the secure enclave, since power side-channel attacks remain a practical threat against embedded secure elements.[10]\n- Automatic zeroization of enclave key material on detection of tamper events, voltage anomalies, or unexpected temperature/clock conditions.\n- A \"Boot Progress Register\" style mechanism (as used in iOS) that permanently restricts access to sensitive operations once the device enters recovery/DFU-like states, preventing downgrade or debug-mode key extraction.[6]\n- Post-quantum-ready root-of-trust primitives, since manufacturers such as Samsung's Exynos line are already anchoring PQC algorithms at the hardware root given the multi-year lifespan of silicon designs.[11]\n\n## Layer 2: Wallet-Based Identity and Session Authentication\n\nSince \"connecting your wallet\" replaces logging into a specific device, the wallet must function as a portable, self-sovereign root identity rather than a login credential tied to one phone. A Decentralized Identifier (DID) model, aligned with W3C DID/Verifiable Credential standards and already implemented in production wallets such as Identfy, lets the user's identity be verified cryptographically without any central identity server, and lets the user selectively disclose only the attributes a given app needs. Under this model, the phone hardware never stores the identity — it only stores a temporary, revocable session capability derived from a successful wallet handshake.[12]\n\n### Key Management via Threshold MPC, Not Local Seed Storage\n\nA single private key held on one device recreates the exact fragility the immutable-phone concept is trying to eliminate: lose or crack the device, lose the identity. Instead, key management should use Multi-Party Computation (MPC) with threshold signatures, following the pattern used by MetaMask Embedded Wallets and similar TSS-based custody systems, where the private key is never fully reconstructed on any device. A practical 2-of-3 (or higher threshold) share design maps well onto this architecture:[13][14]\n\n| Key share | Where it lives | Purpose |\n|---|---|---|\n| Authentication share | Wallet network / distributed signer nodes | Released only after biometric or PIN challenge succeeds[14] |\n| Device attestation share | Local secure enclave (ephemeral, session-only) | Proves the current terminal is a genuine, uncompromised device[14][13] |\n| Recovery share | User-controlled backup (separate hardware token, or split across trusted contacts via Shamir's Secret Sharing) | Enables identity recovery without any single device[14] |\n\nEach of the k-of-n approaches — Shamir's Secret Sharing (reconstructs the key transiently in memory to sign) versus Threshold Signature Schemes (never reconstructs the key at all, only combines partial signatures) — trades off differently; TSS is preferable here because it means no full private key ever exists in memory on any device, including the enclave, minimizing the value of physically compromising a single terminal.[15][14]\n\n### \"Tap and Become My Phone\" Session Flow\n\n1. User approaches any network-compliant terminal and initiates wallet connection (NFC tap, QR, or Bluetooth proximity).\n2. The terminal's secure enclave generates an ephemeral session keypair and sends a device-attestation proof (signed by its hardware-rooted identity key) to the wallet network.\n3. The wallet network verifies the device attestation, challenges the user for a biometric/PIN factor to release the authentication key-share, and the threshold signature ceremony authorizes a scoped, time-limited session token.\n4. The terminal receives only a capability token — never raw keys or a full data set — that lets it request specific shards from the storage/compute network for the current session.\n5. On session end (timeout, explicit logout, or device tamper detection), the enclave wipes all session key material, returning the device to a \"blank\" state.\n\n## Layer 3: Sharded Storage and Compute Network\n\nUser data must be split, encrypted, and distributed such that no single storage node — and no single device — ever holds a complete, usable copy. Erasure coding (e.g., Reed-Solomon), as used in IPFS/Filecoin-style decentralized storage, splits each file into k data shards plus r parity shards; the original can be reconstructed from any k of the n total shards, so losing or compromising any individual node up to the redundancy threshold neither destroys data availability nor exposes a usable file to that node alone. This differs from simple replication by giving similar fault tolerance at a fraction of the storage overhead — a (6,3) scheme, for example, tolerates the loss of any 3 of 9 shards at roughly 1.5x storage overhead versus multiple full copies.[16][17]\n\nExtending sharding \"down to compute,\" as the concept requires, means the same principle applies to processing, not just storage: rather than one device running a full application binary and holding all working data in one place, computation on sensitive data should be split across multiple nodes such that no single node sees plaintext data plus the full logic simultaneously. This can draw on two complementary decentralized-compute patterns already proven at scale:\n\n- Decentralized compute marketplaces (Akash, Golem-style architectures) that match application workloads to a distributed pool of provider nodes, paying for compute via token incentives and avoiding centralized cloud dependency.[18]\n- Data-availability sampling techniques from modular blockchains (e.g., Celestia's two-dimensional Reed-Solomon expansion), where light clients verify that data is fully available across the network by sampling small random chunks rather than downloading everything — a useful model for lightweight phone terminals verifying shard integrity without pulling full datasets.[17]\n\nFor workloads that require processing on genuinely sensitive plaintext (not just encrypted-at-rest data), the compute nodes themselves should run inside TEEs (ARM TrustZone-class or server-grade confidential computing enclaves such as ARM's CCA), so that even the node operator hosting the compute cannot inspect the data or logic being processed, extending the \"immutable, zero-trust\" principle from the phone all the way into the network.[19]\n\n### Storage/Compute Node Trust Model\n\n| Component | Assumption | Mitigation |\n|---|---|---|\n| Individual storage node | Untrusted; may be malicious or compromised | Erasure coding (k-of-n reconstruction); shards individually encrypted client-side before distribution[17][20] |\n| Individual compute node | Untrusted; may attempt to read data or tamper with results | Confidential computing / TEE-based execution; result attestation and cross-node result verification[19] |\n| Network as a whole | Assumed to have sufficient honest-node redundancy geographically | Geographic/operator diversity requirements for shard placement to avoid correlated failure or seizure[20][21] |\n| Local terminal device | Untrusted after session ends; disposable | No persistent data; ephemeral session keys wiped on logout/tamper[6] |\n\n## Layer 4: Application Marketplace Runtime\n\nApplications in this model should be delivered and executed the way workloads run on a decentralized compute network rather than as installed local binaries: an app's code and state live as content-addressed, shardable artifacts (similar to how IPFS uses content hashing instead of location-based addressing so an app's identity is its hash, not its install path). This lets the same application session move fluidly between physical devices, since \"installing an app\" becomes \"requesting the network render this content-addressed application against my wallet-scoped data\" rather than a device-local install process. Selective disclosure via verifiable credentials lets each app request only the minimum data scope needed for the session, rather than the wallet exposing an entire data graph to every application, echoing the \"share only what's required\" model already used in DID wallets.[20][12]\n\n## Key Trade-offs and Open Risks\n\nThe architecture solves for device-level compromise and data permanence at the cost of introducing new dependency on network availability, latency, and the security of the storage/compute mesh itself; a phone that holds nothing locally is only as usable as its connection to the network, so offline resilience (e.g., a minimal encrypted local cache with its own short-lived, sacrificial keys) needs separate design treatment. Threshold-signature wallet recovery also shifts risk from \"lost device\" to \"lost or colluding key-share custodians,\" so the recovery-share distribution policy (how many parties, geographic/organizational diversity) is a first-order security decision, not an implementation detail. Finally, hardware attestation is only as strong as the chip fabrication supply chain; PUF-based device identity mitigates cloning but does not eliminate the risk of a compromised fabrication process embedding a backdoor at the root-of-trust level.[9][8]\n\nDesign notes: immutable smartphone, decentralized identity, physical tamper resistance, ephemeral session keys, hardware root of trust\n\nElectrical components (current): Main Application Processor (mcu, 15x15x1.2mm); 3x module: Hardware Security Module, NFC Secure Reader, Wi-Fi and Bluetooth Module; 2x sensor: Biometric Fingerprint Sensor, Optical Light Tamper Detector; High-Res Touchscreen Display (display, 121x76x4.2mm); 3x power: Power Management IC, USB-C Power Delivery Controller, Fast Zeroization Power Switch\n\nMechanical/structural parts (current): 2x structural: CNC Aluminum Midframe, HSM Physical Shielding Can; Front Bezel Enclosure (enclosure, 158x78x4mm); 7x 3d_printed: Display Mounting Bracket, Rear Cover with Tamper Mesh Channels, Optical Tamper Light Guide, Biometric Sensor Secure Holder +3 more; 2x misc: Enclosure Assembly Screws, Brass Threaded Heat-Set Inserts", "tags": [ "immutable smartphone", "decentralized identity", "physical tamper resistance", "ephemeral session keys", "hardware root of trust" ] }, "originalPrompt": "## Overview\n\nThis document defines a system architecture for a \"stateless\" or \"immutable\" smartphone in which persistent user data never resides on any single device. Instead, data is sharded, encrypted, and distributed across a compute/storage network, and user identity and data access are bound to a cryptographic wallet rather than to any physical handset. The device becomes an ephemeral, interchangeable rendering and I/O terminal — a \"thin hardware client\" for a decentralized backend. The architecture is organized into four layers: hardware root of trust, wallet-based identity and authentication, sharded storage and compute, and the application marketplace runtime.\n\n## Design Goals and Threat Model\n\nThe core design goal is that compromising, stealing, or physically destroying any single device should not expose or destroy user data, and any compliant device on the network should be able to \"become\" the user's phone the moment a wallet is authenticated. This inverts the conventional mobile threat model: instead of protecting data at rest on a single device, the priority shifts to (1) protecting the wallet keys/credentials that authorize access, (2) protecting data in transit and at rest across many untrusted third-party nodes, and (3) ensuring the local device itself is not a persistent target because it holds nothing of lasting value once a session ends. Attackers to defend against include device theft/forensic extraction, malicious or compromised storage/compute nodes in the network, man-in-the-middle session hijacking, side-channel and fault-injection attacks against the local secure hardware, and supply-chain tampering during manufacturing.\n\n## Layer 1: Hardware Root of Trust and Secure Enclave\n\nEvery device needs an immutable, chip-fabricated hardware root of trust that anchors a verified boot chain, since software alone cannot be trusted to bootstrap trust in itself. Following the pattern used in Apple's Secure Enclave and Qualcomm/ARM designs, the Boot ROM is burned in silicon at fabrication and holds the manufacturer's root public key; it verifies the first-stage bootloader's signature before executing it, and each subsequent stage verifies the next, forming an unbroken chain of trust up to the OS kernel. A dedicated, physically isolated secure coprocessor — analogous to Apple's Secure Enclave or an ARM TrustZone-based Trusted Execution Environment (TEE) — should run independently of the main application processor, with its own boot ROM, RAM, and hardware AES engine, so that even a fully compromised main OS cannot directly access enclave secrets.[1][2][3][4][5][6]\n\nBecause this device is explicitly \"immutable\" in the sense of holding no persistent user data, the secure enclave's job is narrower than in conventional phones: it does not need to protect a large local data vault, but it must protect three things that are highly sensitive even if ephemeral: the session's derived key-share material, biometric templates used for local wallet unlock, and the device's unique hardware identity keys used to attest to the network that this is a genuine, unmodified device. TrustZone's split into \"Secure World\" and \"Normal World\" execution environments, enforced by hardware bus-level access controls rather than software permissions, is well suited to isolating this key material from the Android/Linux-style normal-world OS running the marketplace app runtime.[2][7][1]\n\n### Physical Tamper and Side-Channel Resistance\n\nBecause devices in this network are commodity, interchangeable, and potentially used by many different wallet-holders over their lifetime (e.g., loaner devices, kiosks, secondhand units), physical tamper resistance matters more than in a single-owner phone. Recommended hardware countermeasures include:\n\n- Physically Unclonable Functions (PUFs) to derive a device-unique fingerprint from manufacturing-level silicon variations, giving each unit an unforgeable identity that cannot be cloned even by the manufacturer.[8][9]\n- Active mesh tamper-detection shielding and voltage/clock-glitch and power side-channel countermeasures (constant-time crypto operations, power-analysis-resistant AES cores) around the secure enclave, since power side-channel attacks remain a practical threat against embedded secure elements.[10]\n- Automatic zeroization of enclave key material on detection of tamper events, voltage anomalies, or unexpected temperature/clock conditions.\n- A \"Boot Progress Register\" style mechanism (as used in iOS) that permanently restricts access to sensitive operations once the device enters recovery/DFU-like states, preventing downgrade or debug-mode key extraction.[6]\n- Post-quantum-ready root-of-trust primitives, since manufacturers such as Samsung's Exynos line are already anchoring PQC algorithms at the hardware root given the multi-year lifespan of silicon designs.[11]\n\n## Layer 2: Wallet-Based Identity and Session Authentication\n\nSince \"connecting your wallet\" replaces logging into a specific device, the wallet must function as a portable, self-sovereign root identity rather than a login credential tied to one phone. A Decentralized Identifier (DID) model, aligned with W3C DID/Verifiable Credential standards and already implemented in production wallets such as Identfy, lets the user's identity be verified cryptographically without any central identity server, and lets the user selectively disclose only the attributes a given app needs. Under this model, the phone hardware never stores the identity — it only stores a temporary, revocable session capability derived from a successful wallet handshake.[12]\n\n### Key Management via Threshold MPC, Not Local Seed Storage\n\nA single private key held on one device recreates the exact fragility the immutable-phone concept is trying to eliminate: lose or crack the device, lose the identity. Instead, key management should use Multi-Party Computation (MPC) with threshold signatures, following the pattern used by MetaMask Embedded Wallets and similar TSS-based custody systems, where the private key is never fully reconstructed on any device. A practical 2-of-3 (or higher threshold) share design maps well onto this architecture:[13][14]\n\n| Key share | Where it lives | Purpose |\n|---|---|---|\n| Authentication share | Wallet network / distributed signer nodes | Released only after biometric or PIN challenge succeeds[14] |\n| Device attestation share | Local secure enclave (ephemeral, session-only) | Proves the current terminal is a genuine, uncompromised device[14][13] |\n| Recovery share | User-controlled backup (separate hardware token, or split across trusted contacts via Shamir's Secret Sharing) | Enables identity recovery without any single device[14] |\n\nEach of the k-of-n approaches — Shamir's Secret Sharing (reconstructs the key transiently in memory to sign) versus Threshold Signature Schemes (never reconstructs the key at all, only combines partial signatures) — trades off differently; TSS is preferable here because it means no full private key ever exists in memory on any device, including the enclave, minimizing the value of physically compromising a single terminal.[15][14]\n\n### \"Tap and Become My Phone\" Session Flow\n\n1. User approaches any network-compliant terminal and initiates wallet connection (NFC tap, QR, or Bluetooth proximity).\n2. The terminal's secure enclave generates an ephemeral session keypair and sends a device-attestation proof (signed by its hardware-rooted identity key) to the wallet network.\n3. The wallet network verifies the device attestation, challenges the user for a biometric/PIN factor to release the authentication key-share, and the threshold signature ceremony authorizes a scoped, time-limited session token.\n4. The terminal receives only a capability token — never raw keys or a full data set — that lets it request specific shards from the storage/compute network for the current session.\n5. On session end (timeout, explicit logout, or device tamper detection), the enclave wipes all session key material, returning the device to a \"blank\" state.\n\n## Layer 3: Sharded Storage and Compute Network\n\nUser data must be split, encrypted, and distributed such that no single storage node — and no single device — ever holds a complete, usable copy. Erasure coding (e.g., Reed-Solomon), as used in IPFS/Filecoin-style decentralized storage, splits each file into k data shards plus r parity shards; the original can be reconstructed from any k of the n total shards, so losing or compromising any individual node up to the redundancy threshold neither destroys data availability nor exposes a usable file to that node alone. This differs from simple replication by giving similar fault tolerance at a fraction of the storage overhead — a (6,3) scheme, for example, tolerates the loss of any 3 of 9 shards at roughly 1.5x storage overhead versus multiple full copies.[16][17]\n\nExtending sharding \"down to compute,\" as the concept requires, means the same principle applies to processing, not just storage: rather than one device running a full application binary and holding all working data in one place, computation on sensitive data should be split across multiple nodes such that no single node sees plaintext data plus the full logic simultaneously. This can draw on two complementary decentralized-compute patterns already proven at scale:\n\n- Decentralized compute marketplaces (Akash, Golem-style architectures) that match application workloads to a distributed pool of provider nodes, paying for compute via token incentives and avoiding centralized cloud dependency.[18]\n- Data-availability sampling techniques from modular blockchains (e.g., Celestia's two-dimensional Reed-Solomon expansion), where light clients verify that data is fully available across the network by sampling small random chunks rather than downloading everything — a useful model for lightweight phone terminals verifying shard integrity without pulling full datasets.[17]\n\nFor workloads that require processing on genuinely sensitive plaintext (not just encrypted-at-rest data), the compute nodes themselves should run inside TEEs (ARM TrustZone-class or server-grade confidential computing enclaves such as ARM's CCA), so that even the node operator hosting the compute cannot inspect the data or logic being processed, extending the \"immutable, zero-trust\" principle from the phone all the way into the network.[19]\n\n### Storage/Compute Node Trust Model\n\n| Component | Assumption | Mitigation |\n|---|---|---|\n| Individual storage node | Untrusted; may be malicious or compromised | Erasure coding (k-of-n reconstruction); shards individually encrypted client-side before distribution[17][20] |\n| Individual compute node | Untrusted; may attempt to read data or tamper with results | Confidential computing / TEE-based execution; result attestation and cross-node result verification[19] |\n| Network as a whole | Assumed to have sufficient honest-node redundancy geographically | Geographic/operator diversity requirements for shard placement to avoid correlated failure or seizure[20][21] |\n| Local terminal device | Untrusted after session ends; disposable | No persistent data; ephemeral session keys wiped on logout/tamper[6] |\n\n## Layer 4: Application Marketplace Runtime\n\nApplications in this model should be delivered and executed the way workloads run on a decentralized compute network rather than as installed local binaries: an app's code and state live as content-addressed, shardable artifacts (similar to how IPFS uses content hashing instead of location-based addressing so an app's identity is its hash, not its install path). This lets the same application session move fluidly between physical devices, since \"installing an app\" becomes \"requesting the network render this content-addressed application against my wallet-scoped data\" rather than a device-local install process. Selective disclosure via verifiable credentials lets each app request only the minimum data scope needed for the session, rather than the wallet exposing an entire data graph to every application, echoing the \"share only what's required\" model already used in DID wallets.[20][12]\n\n## Key Trade-offs and Open Risks\n\nThe architecture solves for device-level compromise and data permanence at the cost of introducing new dependency on network availability, latency, and the security of the storage/compute mesh itself; a phone that holds nothing locally is only as usable as its connection to the network, so offline resilience (e.g., a minimal encrypted local cache with its own short-lived, sacrificial keys) needs separate design treatment. Threshold-signature wallet recovery also shifts risk from \"lost device\" to \"lost or colluding key-share custodians,\" so the recovery-share distribution policy (how many parties, geographic/organizational diversity) is a first-order security decision, not an implementation detail. Finally, hardware attestation is only as strong as the chip fabrication supply chain; PUF-based device identity mitigates cloning but does not eliminate the risk of a compromised fabrication process embedding a backdoor at the root-of-trust level.[9][8]", "plan": "- Ephemeral Client Processor: High-performance System-on-Chip (SoC) with hardware-enforced virtualization, ARM TrustZone/TEE support, and a secure coprocessor element.\n- Cryptographic Hardware: Discrete secure element (such as an ATECC608B or similar) or dedicated hardware security module (HSM) with Physically Unclonable Function (PUF) capability and active tamper-detection mesh inputs.\n- Peripherals and Display: High-resolution touchscreen display, biometric sensor (fingerprint/camera module), NFC transceiver for wallet tapping, and Bluetooth/Wi-Fi/cellular radio modules for network connectivity.\n- Power Management: Rechargable Li-ion battery, USB-C controller with USB Power Delivery, and low-dropout (LDO) regulators supporting fast power-rail shutoff/discharge circuits for key zeroization.\n- Structural Enclosure: CNC-milled aluminum or impact-resistant polycarbonate chassis designed to accommodate active shielding wires, secure mounting screws, and alignment brackets for the display and main board.\n- Custom 3D-Printed Parts: Custom-designed internal structural sub-frames, brackets for holding antennas in optimal configurations, and physical light-pipe guides for optical tamper-detection sensors.", "notes": [ "immutable smartphone", "decentralized identity", "physical tamper resistance", "ephemeral session keys", "hardware root of trust" ], "projectId": "3722a504-6690-48f5-9a8c-fe048ba24e97", "instructionPreamble": { "tools": [ "Soldering station with micro-fine tip", "Hot air rework station", "M1.4, M1.6, and M2 precision screwdrivers", "3D printer capable of ABS/PETG printing", "Soldering iron with heat-set insert tip", "Digital multimeter", "ESD-safe tweezers", "Kapton tape" ], "assumptions": [ "Access to an ESD-safe workbench environment", "Experience with high-density surface-mount soldering (SMD)", "Ready-to-print 3D CAD files for the enclosures and brackets", "Active logic analyzer or oscilloscope for bus verification" ] }, "instructionSteps": [ { "id": "fabricate", "subSteps": [ { "id": "fabricate_1", "title": "Print mechanical brackets and enclosures", "partIds": [ "display_mount_bracket", "rear_cover_shell", "optical_tamper_light_pipe", "fingerprint_sensor_holder", "nfc_antenna_spacer", "wireless_antenna_isolator", "application_processor_soc_mount" ] }, { "id": "fabricate_2", "title": "Install brass threaded inserts into the midframe", "partIds": [ "internal_thread_inserts", "main_chassis_midframe" ] }, { "id": "fabricate_3", "title": "Vapor-smooth ABS rear cover and polish optical light guide", "partIds": [ "rear_cover_shell", "optical_tamper_light_pipe" ] }, { "id": "fabricate_4", "title": "Test fit PCB assemblies and metal shielding can", "partIds": [ "hsm_shield_can", "main_chassis_midframe" ] } ] }, { "id": "wire", "subSteps": [ { "id": "wire_1", "title": "Wire PMIC rails to Application Processor and active discharge switch", "partIds": [ "pmic", "application_processor_soc", "active_discharge_switch" ] }, { "id": "wire_2", "title": "Solder secondary power distribution networks for sensors and display", "partIds": [ "active_discharge_switch", "discrete_hsm", "fingerprint_sensor", "nfc_transceiver", "touchscreen_display", "wireless_module", "optical_tamper_sensor" ] }, { "id": "wire_3", "title": "Route USB-C PD controller connections to the PMIC", "partIds": [ "usb_c_pd_controller", "pmic" ] }, { "id": "wire_4", "title": "Solder SPI and I2C buses between processor, HSM, and sensors", "partIds": [ "application_processor_soc", "discrete_hsm", "nfc_transceiver", "fingerprint_sensor" ] }, { "id": "wire_5", "title": "Connect MIPI DSI, I2C, and GPIO control lines to Touchscreen and Wireless Module", "partIds": [ "application_processor_soc", "touchscreen_display", "wireless_module" ] }, { "id": "wire_6", "title": "Wire active zeroization loop from optical sensor to active discharge switch", "partIds": [ "optical_tamper_sensor", "active_discharge_switch" ] } ] }, { "id": "bringup", "subSteps": [ { "id": "bringup_1", "title": "Verify PMIC power supply outputs and current draw", "partIds": [ "pmic", "usb_c_pd_controller" ] }, { "id": "bringup_2", "title": "Validate core active discharge switch functionally via physical testing", "partIds": [ "active_discharge_switch", "optical_tamper_sensor" ] }, { "id": "bringup_3", "title": "Establish serial bootloader connection with processor", "partIds": [ "application_processor_soc" ] }, { "id": "bringup_4", "title": "Scan I2C and SPI buses for active security modules", "partIds": [ "application_processor_soc", "discrete_hsm", "nfc_transceiver", "fingerprint_sensor" ] }, { "id": "bringup_5", "title": "Initialize display output and test touchscreen digitizer functionality", "partIds": [ "application_processor_soc", "touchscreen_display" ] } ] }, { "id": "assemble", "subSteps": [ { "id": "assemble_1", "title": "Mount Application Processor and secure discrete HSM shield", "partIds": [ "application_processor_soc_mount", "application_processor_soc", "hsm_shield_can", "discrete_hsm" ] }, { "id": "assemble_2", "title": "Fit display, fingerprint sensor, and optical guide into brackets", "partIds": [ "touchscreen_display", "display_mount_bracket", "fingerprint_sensor", "fingerprint_sensor_holder", "optical_tamper_light_pipe" ] }, { "id": "assemble_3", "title": "Secure NFC antenna and wireless isolators to midframe and rear shell", "partIds": [ "nfc_antenna_spacer", "nfc_transceiver", "wireless_antenna_isolator", "wireless_module", "rear_cover_shell" ] }, { "id": "assemble_4", "title": "Perform final integration of structural frames and screw closure", "partIds": [ "front_bezel_housing", "main_chassis_midframe", "rear_cover_shell", "assembly_screws" ] } ] } ], "wiringCleanedHash": "3722a504-6690-48f5-9a8c-fe048ba24e97::active_discharge_switch:VIN|VOUT|ON|CT|QOD|GND,application_processor_soc:VDD_ARM|VDD_SOC|DRAM_DATA|PCIE_TX|PCIE_RX|MIPI_DSI_TX|MIPI_CSI_RX|USB1_DN|USB1_DP|I2C1_SCL|I2C1_SDA|SPI1_MOSI|SPI1_MISO|SPI1_SCLK|SPI1_SS0|UART1_TX|UART1_RX|GPIO_1,discrete_hsm:SDA|SCL|GND|VCC,fingerprint_sensor:VDD|GND|SPI_MOSI|SPI_MISO|SPI_CLK|SPI_CS|INT|RESET,nfc_transceiver:RFI1|RFI2|RFO1|RFO2|SPI_MISO|SPI_MOSI|SPI_SCLK|SPI_SS|IRQ|VDD|VSS,optical_tamper_sensor:OUT|VCC|GND,pmic:VIN|BUCK1_OUT|BUCK2_OUT|LDO1_OUT|LDO2_OUT|I2C_SDA|I2C_SCL|ON_OFF|RESET_B|GND,touchscreen_display:MIPI_D0_P|MIPI_D0_N|MIPI_CLK_P|MIPI_CLK_N|VDD|GND|SDA|SCL|INT|RESET,usb_c_pd_controller:VCONN|CC1|CC2|VBUS|I2C_SDA|I2C_SCL|RESET|GND,wireless_module:SDIO_CLK|SDIO_CMD|SDIO_DATA0|SDIO_DATA1|SDIO_DATA2|SDIO_DATA3|UART_TXD|UART_RXD|UART_RTS|UART_CTS|VIN|GND::data|application_processor_soc|GPIO_1|fingerprint_sensor|SPI_CS|gpio|;data|application_processor_soc|I2C1_SCL|discrete_hsm|SCL|i2c|;data|application_processor_soc|I2C1_SCL|pmic|I2C_SCL|i2c|;data|application_processor_soc|I2C1_SCL|touchscreen_display|SCL|i2c|;data|application_processor_soc|I2C1_SCL|usb_c_pd_controller|I2C_SCL|i2c|;data|application_processor_soc|I2C1_SDA|discrete_hsm|SDA|i2c|;data|application_processor_soc|I2C1_SDA|pmic|I2C_SDA|i2c|;data|application_processor_soc|I2C1_SDA|touchscreen_display|SDA|i2c|;data|application_processor_soc|I2C1_SDA|usb_c_pd_controller|I2C_SDA|i2c|;data|application_processor_soc|MIPI_DSI_TX|touchscreen_display|MIPI_D0_P|dsi|;data|application_processor_soc|SPI1_MISO|fingerprint_sensor|SPI_MISO|spi|;data|application_processor_soc|SPI1_MISO|nfc_transceiver|SPI_MISO|spi|;data|application_processor_soc|SPI1_MOSI|fingerprint_sensor|SPI_MOSI|spi|;data|application_processor_soc|SPI1_MOSI|nfc_transceiver|SPI_MOSI|spi|;data|application_processor_soc|SPI1_SCLK|fingerprint_sensor|SPI_CLK|spi|;data|application_processor_soc|SPI1_SCLK|nfc_transceiver|SPI_SCLK|spi|;data|application_processor_soc|SPI1_SS0|nfc_transceiver|SPI_SS|spi|;data|application_processor_soc|UART1_RX|wireless_module|UART_TXD|uart|;data|application_processor_soc|UART1_TX|wireless_module|UART_RXD|uart|;data|optical_tamper_sensor|OUT|active_discharge_switch|ON|gpio|;power|active_discharge_switch|GND|discrete_hsm|GND||;power|active_discharge_switch|GND|fingerprint_sensor|GND||;power|active_discharge_switch||discrete_hsm|||3.3V;power|active_discharge_switch||fingerprint_sensor|||3.3V;power|pmic|GND|active_discharge_switch|GND||;power|pmic|GND|nfc_transceiver|VSS||;power|pmic|GND|optical_tamper_sensor|GND||;power|pmic|GND|touchscreen_display|GND||;power|pmic|GND|wireless_module|GND||;power|pmic|VIN|usb_c_pd_controller|VBUS||1.2V;power|pmic||active_discharge_switch|||3.3V;power|pmic||application_processor_soc|||1.2V;power|pmic||application_processor_soc|||1.8V;power|pmic||nfc_transceiver|||3.3V;power|pmic||optical_tamper_sensor|||3.3V;power|pmic||touchscreen_display|||3.3V;power|pmic||wireless_module|||3.3V;power|usb_c_pd_controller|GND|pmic|GND||;power|usb_c_pd_controller||pmic|||5V" }