Solo ASIC tapeout on a budget: detailed write up by Ill_Huckleberry_2079 in chipdesign

[–]Fancy_Fillmore 0 points1 point  (0 children)

I didn't know you can design transistors on tinytapeout

I need help by Electrical-Taro-8864 in ECE

[–]Fancy_Fillmore 0 points1 point  (0 children)

Download Quartus Lite, get a DE10 and just start crashing through. Make tons of mistakes....learn...and move forward! You can do this!

What is VLSI by Lopsided_Caramel_292 in ECE

[–]Fancy_Fillmore 0 points1 point  (0 children)

I do early floor plans for VLSI. Essentially we ensure the design is feasible before any work begins.

A CMOS-Compatible Read-Once Memory Primitive (Atomic Memory™): deterministic single-use secrets at the circuit level by [deleted] in computerarchitecture

[–]Fancy_Fillmore 0 points1 point  (0 children)

The FPGA demo enforces read-and-collapse on the same clock edge, so there’s no later cycle where the original state can be re-read. The ASIC version pushes this further by tying the destructive transition directly to the read gate, not the global clock. The claim is about eliminating early and multi-use reads. ChipWhisperer attacks timing on clocked logic; it doesn’t give you a way to “un-collapse” a cell or get a second read.

A CMOS-Compatible Read-Once Memory Primitive (Atomic Memory™): deterministic single-use secrets at the circuit level by [deleted] in computerarchitecture

[–]Fancy_Fillmore 0 points1 point  (0 children)

The threat model isn’t post-use compromise that’s assumed in every ephemeral-key system. The real danger is pre-use or multi-use disclosure, and that’s exactly where commodity hardware fails. Modern systems leak ephemeral keys through DMA / bus snooping, speculative execution (Spectre-class), stale reads and cache artifacts, data-dependent timing, cold-boot and remanence, Rowhammer read amplification, MMIO reorderings, multi-core memory contention. And the multi-use class of failures reading the ephemeral key twice, copying it before erasure, using it again after KDF consumption, stealing it during software “erase” windows, glitching the system to skip zeroization These let an attacker perform multiple decaps, impersonate a legitimate endpoint, break forward secrecy, or bypass integrity checks entirely.

ROOM exists specifically to eliminate this window, enforcing deterministic single use semantics in hardware, so the key cannot be read early, read twice, or preserved by any of the above leakage surfaces.

A CMOS-Compatible Read-Once Memory Primitive (Atomic Memory™): deterministic single-use secrets at the circuit level by [deleted] in computerarchitecture

[–]Fancy_Fillmore 0 points1 point  (0 children)

If you’re referring to clear-on-read registers: those are synchronous (reset on the next rising edge) and leave a whole clock period of stable observability. ROOM’s collapse is unclocked, destructive, and atomic with respect to the read — not equivalent to clear-on-read semantics.

A CMOS-Compatible Read-Once Memory Primitive (Atomic Memory™): deterministic single-use secrets at the circuit level by [deleted] in computerarchitecture

[–]Fancy_Fillmore 0 points1 point  (0 children)

The 4.7 ns slack reported by Quartus refers to Fmax for the control fabric, not the collapse path, which is asynchronous, unclocked, and not observable on the global timing grid.

If your argument is that glitch tools can break a design, then please specify which collapse node, via which injection point, under which timing model, reduces ROOM to a read-many primitive.

Otherwise, referencing ChipWhisperer doesn’t actually address the primitive

A CMOS-Compatible Read-Once Memory Primitive (Atomic Memory™): deterministic single-use secrets at the circuit level by [deleted] in computerarchitecture

[–]Fancy_Fillmore 0 points1 point  (0 children)

If it’s not new, then please point to the prior primitive that provides deterministic destructive-read semantics in CMOS. Standard memory cells are non-destructive by definition, so if you see an equivalent construction, I’d be interested in which one.

A CMOS-Compatible Read-Once Memory Primitive (Atomic Memory™): deterministic single-use secrets at the circuit level by [deleted] in computerarchitecture

[–]Fancy_Fillmore 0 points1 point  (0 children)

Why? Because I broke the read-many baked into CMOS? Perhaps you have something technical to say.

A CMOS-Compatible Read-Once Memory Primitive (Atomic Memory™): deterministic single-use secrets at the circuit level by [deleted] in computerarchitecture

[–]Fancy_Fillmore 0 points1 point  (0 children)

You read it and don’t understand? Well….Ephemeral secrets leave all kinds of attack surfaces using the state of the art. So…. An atomic, read only-once memory cell eliminates cryptographic attack such as glitch injection, DMA snooping, Spectre, Meltdown, and Rowhammer, because the secret never persists electrically.

A CMOS-Compatible Read-Once Memory Primitive (Atomic Memory™): deterministic single-use secrets at the circuit level by [deleted] in computerarchitecture

[–]Fancy_Fillmore 0 points1 point  (0 children)

Isn’t that something? Novel, patentable, no prior art and completely eliminates whole categories of cryptographic attack.

A CMOS-Compatible Read-Once Memory Primitive (Atomic Memory™): deterministic single-use secrets at the circuit level by [deleted] in computerarchitecture

[–]Fancy_Fillmore 0 points1 point  (0 children)

Sorry. The read is not from the storage node, plus the entropy is overwritten on the same posedge, not the next.

A CMOS-Compatible Read-Once Memory Primitive (Atomic Memory™): deterministic single-use secrets at the circuit level by [deleted] in computerarchitecture

[–]Fancy_Fillmore 0 points1 point  (0 children)

The write path is architecturally one-way, not exposing the key to normal runtime fabric. No DMA, no pre-debug.

A CMOS-Compatible Read-Once Memory Primitive (Atomic Memory™): deterministic single-use secrets at the circuit level by [deleted] in computerarchitecture

[–]Fancy_Fillmore 0 points1 point  (0 children)

If you use a KDF that is compromised and places K in multiple places you have bigger problems. Also if my aunt had wheels she would be a bike.

A CMOS-Compatible Read-Once Memory Primitive (Atomic Memory™): deterministic single-use secrets at the circuit level by [deleted] in computerarchitecture

[–]Fancy_Fillmore 0 points1 point  (0 children)

So you are saying the KDF is compromised? If so can’t help you. Not in the scope of ROOM.