Summary: Let's say "computational contracts" instead of "smart contracts".
I've been studying and working with [smart contracts](https://en.wikipedia.org/wiki/Smart_contract) for a long time. I remember learning about them for the first time through [a talk by Mike Hearn](https://www.youtube.com/watch?v=mD4L7xDNCmA) (former bitcoin developer) which completely blew my brains out. I'm such a fan of the concept that the name of the company which later became [OpenZeppelin](https://openzeppelin.com/) was originally... [Smart Contract Solutions](https://www.crunchbase.com/organization/smart-contract-solutions). I've always believed smart contracts would change the world (which kinda already happened), but heck... I also always hated the name "smart contract". With all due respect to [Nick](https://en.wikipedia.org/wiki/Nick_Szabo), who coined the term, it sucks. I couldn't ever come up with a convincing alternative, so I [just](https://maraoz.medium.com/smart-contracts-and-bitcoin-a5d61011d9b1) [used](https://blog.openzeppelin.com/the-hitchhikers-guide-to-smart-contracts-in-ethereum-848f08001f05/) "smart contracts" and swallowed my tears.
HOWEVER, I recently came across an alternative which I really, really liked:
✨computational contracts✨.
It’s more precise, unambiguous, complete, and it sounds a lot less like a buzzword. A computational contract is a contract that is defined, enforced, and/or executed computationally. That’s it! Clear and simple. Almost self-explanatory.
I know it’s probably too late to change how everyone calls smart contracts computational contracts, but I had to try. If you agree, please start using “computational contracts”. If you don’t, ignore this post and have a nice day :)
maraoz.com