Canister's must-implement interfaces

What other interfaces should I implement apart from cycles management (to keep it alive) and ingress message inspection (to mitigate some attacks)? I ask because there might be something that missed.

https://wiki.internetcomputer.org/wiki/Best_practices_for_a_high_traffic_dapp_launch

^
when was this written? if it’s too old then we might need a new one

1 Like

The wiki article looks (still) reasonable. I can also recommend this page: Canister development security best practices | Internet Computer, but to make better recommendations you’d have to share a few more bits of information. What are your requirements? Should the canister be DAO-controlled? blackholed? Should it be self-sufficient? What are your security assumptions?

1 Like