A network is not the same thing as a chain. These two words get used interchangeably in blockchain. They shouldn't be. A chain is a single linear sequence of blocks. One history. One state. One set of validators. Everything that happens on it competes for space in that same sequence. A network is a set of independent things that cooperate. The internet is a network. The banking system is a network. They're not faster versions of a single thing; they're a fundamentally different model. When people talk about scaling blockchain, they almost always mean scaling the chain. Making the sequence faster. Adding capacity. Reducing congestion. It's the same problem, approached the same way, over and over. Amaroo starts somewhere else. Not "how do we make the chain faster?" but "could the network model, the one that actually worked for the internet, produce something the chain model can't?" One chain getting faster has a ceiling. A network of cooperating chains might not have the same one. → amaroo.com

Early internet hit a wall. Things slowed down, and the instinct was obvious: upgrade the machine. More RAM. Faster CPU. Bigger pipe. It worked, until it didn't. The actual breakthrough wasn't a better machine. It was realising you didn't need one. TCP/IP wasn't a faster protocol. It was a different way of thinking entirely: distribute the work, let ordinary machines cooperate, let the network carry the load. Blockchain is hitting the same wall right now. And most scaling projects are responding the same way: bigger blocks, faster finality, more throughput on a single chain. Better machines. Amaroo starts from a different question. Not "how do we make the chain faster?" But, "what does it look like to actually scale the network?"