Dear developers and friends at HACKERHOUSE, hello!
During this HACKERHOUSE event, I have aligned the SCC0 text with its smart contracts. And this license is part of our project DAism.
SCC0 License has been released on GitHub and Ethereum: https://github.com/DAism2019/SCC0
1. The Revolution of Blockchain and Smart Contracts
We all know, a smart contract is essentially a piece of code running on the Ethereum blockchain. It consists of code and data (state) and is deployed at a specific address. Since smart contracts cannot be modified or deleted once deployed, and their source code can be verified, they truly embody the principle of "code is law." At the same time, all applications built on smart contracts share a distinct feature: anonymity. Each contract records an “owner” variable, but this "owner" is merely an address that cannot be directly tied to a real-world identity, which is both the charm and challenge of blockchain.
2. The Birth and Core Philosophy of SCC0 License
In this anonymous and untraceable environment, traditional legal concepts and legal guarantees become meaningless because we cannot truly verify who is behind a particular account. Based on this, our DAism team introduced the SCC0 License. Instead of providing traditional legal protection for applications, SCC0 adopts a completely immune preventive strategy—blocking harmful interactions and preventing malicious behaviors to ensure the healthy ecosystem of public decentralized applications.
This also means that all dApps will be permanently open and free to all users.
SCC0 License ensures that all dApps following this license become fully dedicated to the public domain, forming what we call “Smart Commons.” In other words, once an application declares compliance with SCC0, its development and all related components will entirely belong to the public domain. Developers, apart from receiving anonymous rewards from the public governance mechanism, will no longer have traditional ownership claims or bear any responsibilities.
3. Technical Implementation and On-Chain Verification
To give you a clearer understanding of SCC0's technical implementation, let’s see how it is declared in smart contracts. SCC0 License has two versions:
- SCC0 v1 requires the following declaration in the smart contract:address public constant LICENSE = 0xdFBF69B7E5366FB3001C9a214dd85c5FE3f90bAe; address public constant GOVERNANCE = 0xe40b05570d2760102c59bf4ffc9b47f921b67a1F;
- SCC0 v2 extends v1 by not only maintaining the license declaration but also recommending that developers declare the name and type of their Smart Common and set contract ownership to a multisig address to gradually transition control to intelligent applications (dAIpps).
address public constant LICENSE = 0xaCb910db73473944B2D23D37A0e46F57a43c6a49;
// Recommended declarations for better interaction:
address public owner; // Address for rewards
string public scName; // Smart Common name
string public scType; // Smart Common type
This on-chain declaration mechanism enables every application following SCC0 to be verified publicly on the blockchain, facilitating automated interaction checks. This not only enhances transparency but also provides a reliable mechanism to identify and reward developers genuinely contributing to the public domain.
4. Incentive Mechanism and Satoshi UTO Fund
While designing SCC0, we fully considered the importance of incentive mechanisms and operational costs.
All applications following the SCC0 License will participate in the reward system driven by the public governance fund, Satoshi UTO Fund. Simply put, as long as your application complies with SCC0 standards, you can receive anonymous rewards. This reward mechanism is entirely decentralized, eliminating traditional approval processes and avoiding any form of centralized operational risks.
Of course, this also means that the Satoshi UTO Fund will support all operational costs for running your dApp.
As we often say: "Fight magic with magic." We no longer rely on traditional laws and systems, which may be filled with unfair factors or even scams. Instead, we use technology and sound financial mechanisms to build a new, automated incentive system that fosters public governance and positive interactions.
5. The Wisdom of Immunity and the Vision of a New Civilization
Some may ask, in the absence of traditional legal protection, how do we ensure the interests of users and developers? The answer lies in the concept of immunity. SCC0 License does not attempt to provide post-event remedies for every possible risk. Instead, it prevents harmful behaviors from the outset through standard declarations, on-chain verification, AI audits, and preventive mechanisms. We believe that only by building defenses within the system beforehand can risks be mitigated before they even occur.
Furthermore, the SCC0 License aims to do more than just this. We hope to use this licensing mechanism to build a civilization that surpasses capitalist material civilization—one that is based on public governance and intelligent consensus. Here, technology is not just a tool but a form of magic that drives social progress. Through anonymous reward mechanisms, decentralized governance structures, and new forms of interaction, we are striving to achieve a historic transition from traditional economic models to a future public civilization.
6. Looking Forward: Building Smart Commons Together
Dear developers, our gathering at HACKERHOUSE today is not just to showcase technology but to witness a new transformation together. SCC0 License not only provides a green pathway for your application into the public domain but also opens a window for you to participate in future public governance.
Whether you are a dApp developer, a dAIpp builder, or an innovator exploring the blockchain ecosystem, as long as you choose to follow SCC0, your project will become part of Smart Commons. You will benefit from on-chain transparent verification mechanisms, participate in public governance fund rewards and cost coverage, and most importantly—your project will exist in an entirely new way. It will no longer be constrained by traditional ownership and responsibilities but will be founded on a pure public spirit, driving the joint progress of technology and civilization.
7. Conclusion
Before concluding today’s talk, I want to summarize with one sentence: In the future, code will continue to be law, but our law will no longer rely on traditional legal texts—it will be rooted in consensus (such as love), anonymity, and immunity mechanisms.
SCC0 License is precisely such a revolutionary attempt. It provides us with a new way of thinking and a practical path to achieving a fairer, more transparent, and decentralized public civilization.
Let us join hands and embrace this new era together. Thank you for listening, and I welcome all of you to engage further after this event to explore how technology and creativity can build a world beyond capitalist material civilization!
Love you all! Thank you!