> But, imagine a DDOS attack on the nodes serving the blockchain. Okay. > I don’t see why “pay once read forever” works financially. A separate issue thats n

> But, imagine a DDOS attack on the nodes serving the blockchain. Okay. > I don’t see why “pay once read forever” works financially. A separate issue thats not really your problem. Its the node operators problem. When your use case expands to that being a viable problem for you, then you'll need to become a node operator or at least keep a copy of the state yourself. You can design applications around that. Or maybe you can't. Just rule those out or keep using AWS or some other company for those applications?