Americano used centralization as an experiment, not a destination
On November 28, 2022, Espresso Systems released Americano to test HotShot, its responsive Byzantine-fault-tolerant consensus design for rollups. The team called the network internal and non-persistent. It used centralized broadcast infrastructure so engineers could establish a performance baseline, locate bottlenecks and then add a gossip fallback and data availability in later releases. The first public code therefore exposed the order of work: make fast agreement measurable before attempting open participation.
That choice followed a problem created by the rollup boom. A rollup could keep its own execution and still send users through a single sequencer; bridges and neighboring applications then had to wait for slower layer-one finality or trust that sequencer’s view. Espresso proposed a separate shared record for transaction order and available data. It was a confirmation layer, not another virtual machine, and the rollup would remain responsible for executing its own state transition.
