I’m still at my desk, half-finished notes open, trying to make sense of what building on Midnight actually asks from a developer. And the more I look at Compact, the less it feels like “just another smart contract language.”
You know What stands out to me is the shift in mindset. On Midnight, the contract is not simply code you throw onchain and let everyone inspect. Compact is built for a different job: defining rules that can be proven without exposing the sensitive data behind them. Midnight’s own docs describe Compact as a TypeScript-based, domain-specific language for privacy-preserving smart contracts, where familiar code compiles into zero-knowledge circuits rather than forcing developers to work directly with cryptography.
I think that changes the feel of development. You are not only writing logic. You are deciding what must be public, what stays confidential, and what can be verified without being revealed. That is a more careful kind of programming.
The practical part matters too. Midnight’s guides frame Compact as the layer that helps developers build apps with selective disclosure, private state, and proof-based validation, while examples like the bulletin board show identity checks happening without exposing the user behind the action.
So when I read “building confidential smart contracts with Compact,” I do not hear a branding line. I hear a development diary from a different kind of blockchain.
What makes Compact on Midnight most interesting to you?