Add ERC: Smart Creative Commons Zero License (SCC0) #906
Conversation
SCC0 (Smart Creative Commons Zero) is the first public goods license tailored for decentralized public applications (Smart Commons), including dApps, dAIpps(AIs). This standard introduces a structured way for smart contracts to declare SCC0 compliance, enabling automated on-chain verification and governance integration.
eip-review-bot
changed the title
|
You are editing the template file in this pull request. You need to copy the template to the |
OK, thank you very much! |
ERC: Smart Creative Commons Zero (SCC0) License for public dAIpps and dApps
eip-review-bot
changed the title
|
The commit cef44f1 (as a parent of 4e1cbc7) contains errors. |
ERC: Smart Creative Commons Zero (SCC0) License for public dAIpps and dApps SCC0 (Smart Creative Commons Zero) is the first public domain license specifically designed for public decentralized applications—Smart Commons—applicable to both traditional dApps and decentralized AI applications (dAIpp).
Delete the file with wrong name format.
Fixed some content.
Fixed a syntax error.
eip-review-bot
changed the title
zhous
changed the title
eip-review-bot
changed the title
A tiny but important modification.
| SCC0 (Smart Creative Commons Zero) is the first public domain license specifically designed for public decentralized applications—Smart Commons—applicable to both traditional dApps and decentralized AI applications (dAIpp). As a universal standard for decentralized ecosystems, SCC0 implements automated on-chain compliance verification and governance through smart contracts, ensuring the following core principles: | ||
|
|
||
| - **Open Source and Free**: All Smart Commons must publicly release their source code, complete both on-chain and off-chain consistency verification, undergo thorough auditing, and be permanently free to use (only requiring payment for blockchain gas fees). | ||
|
|
||
| - **AI-led Governance:** Rules are enforced via smart contracts (such as rejecting interactions with non-compliant applications and prohibiting private token distributions), with AI gradually taking over the governance process. | ||
| - **Scalability:** The community can extend the license's functionalities by deploying new versions while maintaining backward compatibility. | ||
| - **Public Fund Support:** The Satoshi UTO Fund covers development costs and allocates rewards to anonymous contributors. | ||
| - **Launch Timing of SCC0 License Undetermined**: Prior to the formal activation of the SCC0 License, Smart Commons are not subject to any constraints in practice. For details, please refer to the "Compliance Enforcement in Smart Commons" section. | ||
|
|
||
| The SCC0 License is multi-versioned, and multiple versions can be valid simultaneously. This means that the interpretation of the SCC0 License itself may evolve as new versions are introduced. For instance, the current interpretation is based on the shared core requirements of Version 1 (V1) and Version 2 (V2). | ||
|
|
||
| The development of these versions follows a decentralized collaborative model, meaning that any individual or AI is free to create and publish a new version. | ||
|
|
||
| This proposal introduces a standardized on-chain framework for the SCC0 license, enabling smart commons to mutually verify compliance and integrate decentralized autonomous mechanisms—laying the technical foundation for an AI-driven public goods ecosystem. |
There was a problem hiding this comment.
Your abstract does a good job of laying out what the proposal is proposing, but doesn't have enough detail to give the reader a high-level technical overview of how the proposal accomplishes its goals. How does this proposal ensure that source code is actually released, or how auditing is known to be thorough?
|
|
||
| - **AI-led Governance:** Rules are enforced via smart contracts (such as rejecting interactions with non-compliant applications and prohibiting private token distributions), with AI gradually taking over the governance process. | ||
| - **Scalability:** The community can extend the license's functionalities by deploying new versions while maintaining backward compatibility. | ||
| - **Public Fund Support:** The Satoshi UTO Fund covers development costs and allocates rewards to anonymous contributors. |
There was a problem hiding this comment.
If the proposal relies on a particular funding source, it might not be the best fit for the ERC process.
|
|
||
| SCC0 v1 has been deployed by DAism, and any dApp/dAIpp adhering to it must: | ||
|
|
||
| - Interact with DAism's smart contract `0xdFBF69B7E5366FB3001C9a214dd85c5FE3f90bAe`. Or go to DAism to mint a smart common. |
There was a problem hiding this comment.
Similarly, if a proposal requires a particular product to implement, it likely isn't a good fit for the ERC process. We handle technical standards, not project documentation.
You should be describing the externally visible behaviours of compliant contracts, not writing a user manual for how to mint tokens.
| To ensure that dApps and dAIpps fully adhere to the principles of public interest and transparent governance, the SCC0 license introduces rules, a set of standardized on-chain verification and automated governance mechanisms. The core motivations include: | ||
|
|
||
| - **A License expressed through smart contract code:** To realize the vision of Code is Law, we must encode legal rules into code. | ||
| - **AI Verification:** Utilizing artificial intelligence to perform checks before interactions, ensuring that all parties meet the requirements of the SCC0 license and achieving trustless, automated compliance verification. | ||
| - **Inter-contract Mutual Verification:** Enforcing mandatory compliance checks before Smart Commons interact, thereby preventing non-public or non-compliant applications from infiltrating the ecosystem. | ||
| - **Incentive and Reward Mechanism:** Providing cost support for development and operations through a public governance fund while distributing anonymous rewards to contributors to foster healthy ecosystem growth. | ||
| - **Promoting AI-led and Transparent Governance:** Leveraging the strengths of artificial intelligence and blockchain to build a decentralized, autonomous governance framework led by dAIpps, thereby offering a novel pathway for the innovation of Smart Commons. | ||
|
|
||
| Overall, SCC0 is committed to establishing a self-managed, transparent, and rigorously compliant Smart Commons ecosystem, ensuring them consistently uphold the principles of public interest, openness, and autonomy—thereby providing strong support for the future popularization and development of Smart Commons. |
There was a problem hiding this comment.
This content is mostly talking about the goals of the proposal. The Motivation section should also convince the reader why this particular proposal is necessary (lay out the problem; why do we need SSC0?) and why the reader should choose this particular solution over other—potentially hypothetical—solutions.
| return IDaism(daismAddress).dappToSC(_dApp)>0; | ||
| } | ||
| ``` | ||
|
|
There was a problem hiding this comment.
So far this looks like it's documenting a particular deployed contract, and not a standard that requires multiple parties to coordinate. If you expect everyone to interact with this contract, then you should probably go write some developer documentation. You don't need an ERC.
ERCs are only really useful when multiple parties need to interoperate without having to communicate. ERC-20 tokens are a great example of a good standard. Every wallet wants to display every ERC-20 token, while every ERC-20 token wants to work with every wallet. If these parties had to write bespoke code for every integration, the whole ecosystem wouldn't have gone anywhere. That's where ERCs shine. Here, it looks like you have a single contract. If that's true, you should just publish some docs somewhere.
| mapping(uint => File) public logoStorages; // Storage for smart common logos | ||
| ``` | ||
|
|
||
| The reason why neither SSC0 V1 nor SSC0 V2 has introduced "detailed reward rules from Satoshi UTO Fund for smart commons" is that we can neither implement such measures through any centralized review panel approach, nor determine reward amounts through community voting using wallet addresses. The latter approach is even worse - it constitutes a pseudo-decentralized method that would only be employed by self-deceivers or even scammers. We expect some dAIpp take this work in the future, from valuation to prize management. |
There was a problem hiding this comment.
The reason why [...]
Content explaining choices made within the document itself belongs in the Rationale section.
| Below is the complete implementation of the SCC0 License Management contract (contract account: 0xebBd6AB9655F6fC4064a4D1000dB2654C72243fD): | ||
|
|
||
| ```solidity | ||
| // SPDX-License-Identifier: scc0 |
There was a problem hiding this comment.
We only allow CC0 code within the document itself. You can place other permissively licensed code (generally MIT/Apache) in your assets directory. As scc0 is not a valid SPDX identifier, I'm not sure what we can do with it.
| - **Deprecated Version Query**: Retrieve the full list of deprecated versions, or check the details of an SCC0 license by version number or license contract address to verify whether the protocol version has been deprecated. | ||
| - **Valid Version Query**: Retrieve the complete list of valid(active) versions, or check the details of an SCC0 license by version number or license contract address to verify whether the license version is still valid(active). | ||
|
|
||
| Below is the complete implementation of the SCC0 License Management contract (contract account: 0xebBd6AB9655F6fC4064a4D1000dB2654C72243fD): |
There was a problem hiding this comment.
Implementations generally go in the Reference Implementation section.
|
|
||
| ## Copyright | ||
|
|
||
| Copyright and related rights waived via CC0. |
There was a problem hiding this comment.
Please use the exact waiver (including hyperlink) from the template.
SCC0 (Smart Creative Commons Zero) is the first public goods license tailored for decentralized public applications (Smart Commons), including dApps, dAIpps(AIs). This standard introduces a structured way for smart contracts to declare SCC0 compliance, enabling automated on-chain verification and governance integration.