lastmjs
commented
4 years ago - [x] No canister access to other internet protocols (no http requests, no web sockets)
- [ ] No private computation (can't perform computations on private data within a canister, can't store private data that the canister can see in plain text)
- [ ] I believe this is actually being addressed before Mercury launch
- [ ] Can't natively consume state from other blockchains (can't easily port an ERC20 for use with ICP)
- [ ] Not as decentralized as Ethereum
- [ ] This actually may not be true once we have many independent data centers...watch this
- [ ] Since the nodes aren't designed to be run by anyone, there may be fewer individuals involved
- [ ] No blocks
- [ ] How will we trust the state of the system without being able to verify all state changes up to the current state? Will this be okay? If the code is open source, and we trust its executation, will that be enough?
- [ ] 4gb limit per canister requires special data structures for scale-out
- [ ] BigMap and BigSearch will help abstract this away. I feel like it should be abstracted away at the canister level already. Also, improvements in Wasm may help this in the coming years
- [ ] Can BigMap scale down?
- [ ] Can a canister that is just serving queries handle any type of load on it as long as the load of a single query is less than the 4gb memory limit?
- [ ] We have to think about the different types of subnets to deploy canisters to