Gitcoin

Suggestions for Smart Common Development

Details
Written by: Derek.DAism Zhou

Preparation

Dear developers,

This article is not a Solidity programming tutorial, but rather a suggestion aimed at maximizing the opportunities for Smart Common (public dApp) developers to earn awards.

Before reading this suggestion, be sure to understand DAism thoroughly to fully grasp this guide. Oh yeah, every developer of dApps and every author of EIPs had better read this article.

Minimum Requirements:

🧑‍🏫 What is Proof of Value?

📖 ​​DAism Whitepaper

🤖 Remember: You don't need to team up with others; your best partner is called AI!

Good Luck!

Review: What is a Smart Common?

The PoV (Proof of Value) requires developers to accept DAism's SC0 license and mint their dApp as Smart Commons. 

In other words, a Smart Common refers to a dApp or collection of dApps that adhere to the SC0 license - it is "smart" as it is written in smart contract language and self-executing, and it is designated as a public dApp or collection of public dApps through the SC0 license, making it a "common."

SC0 v0.1

Minting a Smart Common with a dApp under this license signifies that the dApp accepts this agreement as its exclusive license and acknowledges the anonymity of its owners or developers or managers. Due to this anonymity, no one can prove ownership of any rights, nor can anyone prove the assumption of any responsibilities.

  1. Any dApp of this Smart Common is under the governance of DAism.
  2. No Copyright
    Anonymity implies that the developed dApp entirely contributes to the public domain, becoming part of Smart Commons. Apart from being able to enjoy rewards brought by Proof of Value, it completely relinquishes all other rights, including all associated and adjacent rights.
  3. No Liability
    Anonymity means that no one in this world makes any warranties about a dApp and its exclusive valuation token, no one assumes any joint liability. When using or calling the dApp, or investing in the smart common's exclusive valuation token, no one may imply endorsement by the smart common or anyone related to the smart common.

The purpose of this license is to enable all developers to collectively develop public dApps.

Benefits of Proo of Value

For Developers

DAism's Proof of Value brings developers just a minute away from financial freedom through minting.

DAism's Proof of Value is also the only solution allowing "components" and "middleware" level dApp developers to earn awards. This allows the entire industry to spend years calmly innovating the foundational components（dApps and even EIPs）, and then fully leverage the composability of smart contracts to bring about innovative products in a building block manner.

Lastly, DAism's Proof of Value builds a new world where what a dApp or its copy does or supports outside of it, good or bad, has nothing to do with PoV's governance. DAism's Proof of Value governance only means that as long as someone contributes a valuable dApp to the world built by DAism, the developer of that dApp can receive perpetual awards. We know that the smart contract part of a dApp, along with related technical standards, are mostly under free software's licenses (such as EIP's CC0 license), meaning that cloning is inherently encouraged by blockchain. Do you think a dApp's developer would just watch their achievements be taken away?

Therefore, we believe no dApp developer will miss out on DAism! All dApps will enter DAism!

For Investors

In the technical stack of Proof of Value, the DAism development team has also built a more revolutionary DEX for investment, the IADD Network. It surpasses existing market mechanisms with its investment-friendly features. For example, the first investor of a Valuation Token can never suffer a loss, significantly reducing the investment risks for value investors. Additionally, investor behavior is also a decentralized valuation of the dApp’s value... We won't discuss more details now due to the theme, but just let you know that investors will prefer the investment market within Proof of Value.

Basic Features of Smart Common

Public is the core attribute of a Smart Common. In detail, Smart Common has the following basic features:

  1. No Copyright
    Developers do not retain copyright, meaning anyone can freely adapt it.
  2. No Liability
    Developers (anyone) have nothing to do with any issue/disaster of any smart commons.
  3. Free
    As a public good, it naturally cannot embed any commercial model. This doesn't need to be emphasized in the license because the freedom to adapt ensures this.

Key Points for Smart Common Development

If you are an author of EIP, please read this article first: Applying PoV Value Proof to EIPs, AI Fields or anything else.

  1. Do Not Undermine Its Public Nature:
    Do not embed any commercial model, or once someone freely adapts it to be free, your intellectual achievement becomes someone else's financial freedom!
  2. Remember You Can't Keep Anything Except Bonuses:
    Bonuses brought by Proof of Value are assured. But besides that, you cannot keep anything through any means. So please note:
    1. Keep your development secret before minting it as a Smart Common.
      The SC0 license states that you cannot prove smart contract innovation as your original and others plagiarized from you.
      While we encourage more technical discussion and sharing to promote smart common development, balance open technical discussions and your awards/achievements.
    2. Act Quickly.
      Especially in technical discussions, once you have an idea, quickly develop the smart contract and mint your Smart Common. The calculus battle between Newton and Leibniz, as well as blockchain anonymity, remind you not to delay!
  3. Don’t Be Sad, You Can Copy:
    Copy requires attention to surpass the original! Complete clone will only tarnish your wallet address without any other gain!
  4. Smaller dApps Have Higher Success Rates:
    Compare to a smartphone: It took almost a century and a half to evolve from the invention of the carbon composition resistor to today's indispensable smartphones. This is because repeating resistors alone can't make a smartphone. You also need inductors, capacitors, diodes, transistors, Hall sensors, etc. If you want to design a smartphone, you need hundreds of electronic components in your mind. With components, the next step is solving the complexity of chips (integrated circuits). A chip integrates necessary resistors, capacitors, inductors, diodes, etc., on a small piece of semiconductor or dielectric substrate, then packaged into a microstructure with the required circuit functions. A Redmi Note10 Pro requires 114 chips! With these chips and components, plus some special parts, the smartphone emerges.
    Comparing to blockchain applications, how many available now?
    The components are far from enough, right?
    A more detailed description can be found in this article. 
    Let's continue:
    1. Once you understand the urgent task is developing component-level Smart Commons (we can call these Smart Components), you will understand that the smaller your Smart Component, the less likely it will have design errors or redundancies, useless features, naturally leading to higher success rates. Remember anyone can optimize your dApp and become a true success!
    2. DAism essentially governs the entire industry into a unified open collaboration organization. The smaller the dApp, the more likely it is to be directly called by more third parties.
    3. Take the seemingly simplest part, the screw, for example. Can you imagine how many types there are? If curious, see how many are introduced here. While dApps may not have such extreme cases, similar situations will definitely occur. So, keep it minimal.
    4. Another strategy to higher success rates: If your idea is complex or you want to create a large product, it's best to split it into multiple small ones. If all the dApps succeed, third parties can call any dApp they want, and due to the smart contracts composability, they can call several dApps together as well. If the final product you aimed for is completed, this development model gives you multiple extra awards, excellent! If most of your developed dApps fail (most likely your product fails too), but even if one succeeds, you can still get a perpetual award without wasting all your efforts!
      Sometimes integrating all at once may be more efficient or significantly lower gas fees. In such cases, providing a "full version" might be a good strategy as well.
  5. Smart Components Should Not Be Upgradable:
    We know most dApps today are designed to be upgradable via standards like the diamond (ERC-2535).
    But, if you use many Smart Components developed by others and assemble them into a product like playing Lego, and these Smart Components could be upgradable by their developers at any time, would anyone dare to use your product?
    What if a developer goes mad and ruins their Smart Component; or if an upgraded version contains severe security bugs or functional bugs; or if a developer gets jealous of your higher bonuses and tries to sabotage you...
    Obviously, it's better to hardcode Smart Components to be non-upgradable.
    For chip-level dApps, it’s also better to develop in a non-upgradable way. If not possible, have a strategy to eventually switch to non-upgradable.
    However, for very few products, such as DAism itself, being a large platform and not a Smart Component or chip-level dApp, not retaining upgradability is extremely dangerous.
    Notably, DAism has thoughtfully considered developers' interests. It provides an smart upgrade strategy for Smart Commons:
    1. If your non-upgradable dApp has bugs, quickly revise the smart contract code.
    2. Deploy the revised contract as another dApp.
    3. Use the new dApp to mint a new version of the Smart Common on DAism.
    4. Third parties using your dApp can freely choose which dApp to call based on their technical evaluation. If they deem the new dApp necessary, they call the new one. If there's no big deal with the old one(works fine and no security bug), they may do nothing. Regardless of their choice, you continue to get awards.
    5. If unsure, deploying both an upgradable and a non-upgradable version for a Smart Component or middleware is a good strategy.
  6. When Deploying dApps, Ensure to Verify and Publish Your Smart Contract Source Code:
    Verifying and publishing your smart contract source code ensures everyone can see the source code matches the compiled code.
    Pay special attention to achieving Full Verification.
    Official documentation: VERIFYING SMART CONTRACTS
    For relevant operational details, refer to this video.
  7. EIPs(Ethereum Improvement Protocols) is a Treasure Trove:
    Many EIPs are application standards.
    All EIPs follow the CC0 license. Simply put, CC0 ensures all EIPs relinquish copyright.
    Thus, you can freely turn any EIP into a dApp and mint your Smart Common.
    You can also clone existing open-source dApps... Act quickly!
  8. DAism’s Proof of Value is a massive innovation in human (or maybe AI included) collaboration:
    1. Smart Contracts Composability, coupled with the public nature of Smart Commons, means everyone is within the same collaborative system. Essentially, you are participating in a global open collaboration community!
    2. There may be many different variations of the same Smart Component (like SCREW just mentioned), greatly increasing your chances.
    3. Like constantly building with numerous Lego blocks, you have a lifetime opportunity to continuously create your Smart Commons.
    4. As long as your dApp has value, you can continuously receive awards. These rewards could last a decade (until surpassed by a similar dApp created by others), your entire lifetime, or even extend to benefit your descendants, making you a great-grandfather or great-grandmother forever remembered by future generations.
  9. In case DAism fails...
    Even if DAism fails, it will not affect the application of your dApp. DAism simply adds an additional reward mechanism for you, without embedding anything else into your dApp except a few lines of code to call the mint interface. Therefore, as long as your dApp is valuable, you can still rely on it to generate income in new avenues or just anywhere.

Risk Warning

  1. Please ensure that your wallet address's private key (mnemonic phrase) is not lost or leaked!
  2. If you are changing the administrator of your smart commoner, be sure to carefully verify the wallet address of the new administrator. If the address(account) of the new administrator is incorrect and the proposal to change the administrator of the smart commoner is approved, it may render your smart commoner unmanageable, potentially leading to catastrophic consequences.

Food for Thought

  1. When testing your dApp or smart commoner on a test network (like Sepolia), what should you pay attention to?
  2. If you are a dApp developer who has raised funds for the project and issued tokens, does DAism still have relevance to you?

Helpful EIPs

ERC-6372: Contract clock

DAism Beta Version (Sepolia Testnet)

daism.io (Would be DAism.io/test after DAism publised on Ethereum Mainnet)

The frontend is currently under refinement.

DAism plans to officially launch in July. Developers, keep up the good work!

More Development Tips

Yes, there are more development tips waiting for you!

We will share them with everyone in the "Mastering Proof of Value Battle with GPT"!

The era of Blockchain 3.0 Smart Commoners is officially underway

Join the "Mastering Proof of Value Battle with GPT" and get lifelong awards in just 1 minute!