From a cursory look:

- looks dead simple

- no IP layer (there's a ttpip folder in that repo though)

- distributed congestion control (TCP has a "window" field + a bunch of tentative RFCs, this has a purposeful "congestion")

- 100% implementable in hardware (TCP can, but it's complex)

Not a general TCP replacement, but the README properly highlights a "many endpoints local link" use case:

> the protocol executed entirely in hardware and deployed to a very large multi-ExaFlops (fp16) supercomputer with over 10s of thousands of concurrent endpoints. This protocol does not need a CPU or OS to be involved in any way to link and execute.