<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by rootMUD on Medium]]></title>
        <description><![CDATA[Stories by rootMUD on Medium]]></description>
        <link>https://medium.com/@root_mud?source=rss-ee35a88e63af------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*GPJB_nuSs0A33slA.jpg</url>
            <title>Stories by rootMUD on Medium</title>
            <link>https://medium.com/@root_mud?source=rss-ee35a88e63af------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:34:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@root_mud/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Scaffold-Move: uidl Movement dApp Quickly]]></title>
            <link>https://medium.com/@root_mud/scaffold-move-uidl-movement-dapp-quickly-69d2a69a3465?source=rss-ee35a88e63af------2</link>
            <guid isPermaLink="false">https://medium.com/p/69d2a69a3465</guid>
            <category><![CDATA[movement]]></category>
            <category><![CDATA[aptos]]></category>
            <category><![CDATA[move]]></category>
            <dc:creator><![CDATA[rootMUD]]></dc:creator>
            <pubDate>Mon, 27 Jan 2025 21:53:05 GMT</pubDate>
            <atom:updated>2025-01-27T22:07:46.295Z</atom:updated>
            <content:encoded><![CDATA[<h3>Scaffold-Move: to Buidl Movement dApp Quickly</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/311/1*ezfJlPNqYtBd8DlZ-xobYg.png" /><figcaption>movement</figcaption></figure><blockquote><em>Demo Video: </em><a href="https://www.youtube.com/watch?v=Erja2sIpR6U&amp;feature=youtu.be"><em>https://www.youtube.com/watch?v=Erja2sIpR6U&amp;feature=youtu.be</em></a></blockquote><blockquote><em>Online: </em><a href="https://scaffold.rootmud.xyz/"><em>https://scaffold.rootmud.xyz</em></a></blockquote><blockquote><em>Github: </em><a href="https://github.com/NonceGeek/scaffold-move"><em>https://github.com/NonceGeek/scaffold-move</em></a></blockquote><blockquote><em>Homepage: </em><a href="https://home.scaffold.rootmud.xyz/"><em>https://home.scaffold.rootmud.xyz</em></a></blockquote><h3>0x01 What is dApp Scaffolding?</h3><blockquote><em>💡</em><strong><em>What is Scaffold-Move？</em></strong></blockquote><blockquote><em>A modern, clean version of Scaffold-Move with NextJS, Supabase &amp; Deno, strong-AI-powered in the future.</em></blockquote><blockquote><em>A modern, clean version of Scaffold-Move based on NextJS, Supabase and Deno technology stack, which will be driven by strong artificial intelligence in the future.</em></blockquote><p>Inspired by Scaffold-ETH, it is a &quot;classic public goods project&quot; in the Ethereum ecosystem. Learn more about Scaffold-ETH at the homepage:</p><blockquote><a href="https://scaffoldeth.io/"><em>https://scaffoldeth.io/</em></a></blockquote><p>Scaffold projects are essential foundational tools for any ecosystem, reducing the workload of dApp developers by over <strong>90%</strong> . **However, Scaffold projects in the Move ecosystem are still in a very early stage.</p><p>In addition, the existing Scaffold project has the following room for improvement:</p><ul><li>The existing Scaffold has not yet been strongly combined with AI to give full play to the capabilities of AI in Development</li><li>The current Scaffold ecosystem has not yet established a comprehensive incentive mechanism and still follows the open-source model of Web2.</li></ul><p>NonceGeekDAO is committed to developing various types of scaffolds to provide Buidlers with a very fast ⚡ way to build dApps:</p><pre>+-------------------+<br>| Scaffold-Move 🪜 |<br>+-------------------+<br>+-------------------+<br>|Scaffold-GPT-Bot 🏗️|<br>+-------------------+<br>+-------------------+<br>| Scaffold-AO 🔨 |<br>+-------------------+<br>+-------------------+<br>| Scaffold-ETH 🛠️ |<br>+-------------------+</pre><h3>0x02 Scaffold-Move Quick Start</h3><h3>2.1 Contract Deployment</h3><p>We interact with the Movement network through the Aptos CLI.</p><blockquote><em>💡For more usage of </em><em>Aptos CLI, see the article:</em></blockquote><blockquote><a href="https://mp.weixin.qq.com/s/2_0wL1KIAdoxYqya-thi6Q"><em>Aptos CLI Usage Guide and REPL Design Suggestions | Move dApp Quick Start (Six)</em></a></blockquote><h4>2.1.1 Install Aptos CLI</h4><p>Install Aptos CLI.</p><p>See:</p><blockquote><a href="https://aptos.dev/cli-tools/aptos-cli-tool/install-aptos-cli"><em>https://aptos.dev/cli-tools/aptos-cli-tool/install-aptos-cli</em></a></blockquote><p>In general, it is recommended to use the precompiled binary directly, which will save the errors that may be encountered during compilation.</p><h4>2.1.2 Account initialization</h4><p>Initialize an account on the porto testnet as follows:</p><pre>$ aptos init --network custom --rest-url https://aptos.testnet.porto.movementlabs.xyz/v1 --profile movement_acct_1</pre><p>When the mainnet is launched, just replace --rest-url with the mainnet node URL.</p><pre>Configuring for profile movement_acct_1 <br>Configuring for network Custom <br>Using command line argument for rest URL https://aptos.testnet.porto.movementlabs.xyz/v1 <br>Enter your faucet endpoint [Current: None | No input: Skip (or keep the existing one if present) | &#39;skip&#39; to not use a faucet] <br>​<br>No faucet url given, skipping faucet... <br>Enter your private key as a hex literal (0x...) [Current: None | No input: Generate new key (or keep one if present)] <br>​<br>No key given, generating key... Account 0x6e7c05076c385337c5ea2dc522c7f147bb6ad7f60c16d68f6777bde658d12126 has been initialized locally, but you must transfer coins to it to create the account onchain<br>​<br>---<br>Aptos CLI is now set up for account 0x6e7c05076c385337c5ea2dc522c7f147bb6ad7f60c16d68f6777bde658d12126 as profile movement_acct_1! Run `aptos --help` for more information about commands<br>{<br>&quot;Result&quot;: &quot;Success&quot;<br>}</pre><p>During initialization, we will be asked to enter the faucet endpoint address to receive test coins. We can fill in the blanks. Then claim the test coins through the following page:</p><blockquote><a href="https://faucet.movementnetwork.xyz/?network=testnet"><em>https://faucet.movementnetwork.xyz/?network=testnet</em></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/0*A5vM-rL7lXDgGkWn.png" /></figure><h4>2.1.3 Download Scaffold-Move</h4><pre>$ # Download the source code and enter the directory<br>$ git clone https://github.com/NonceGeek/scaffold-move.git<br>$ cd scaffold-move</pre><h4>2.1.4 Contract compilation and deployment</h4><p>Compile the contract to generate binary code, which can be deployed after compilation.</p><pre>$ aptos move compile --package-dir ./contracts/hero --named-addresses hero=movement_acct_1</pre><pre>$aptos move compile --package-dir ./contracts/hero --named-addresses hero=movement_acct_1 <br>... <br>{ &quot;Result&quot;: [ &quot;6e7c05076c385337c5ea2dc522c7f147bb6ad7f60c16d68f6777bde658d12126::hero&quot; ] }</pre><p>Deployment:</p><pre>$ aptos move publish --package-dir ./contracts/hero --named-addresses hero=movement_acct_1 --profile movement_acct_1 ``` <br>​<br>```bash $ aptos move publish --package-dir ./contracts/hero --named-addresses hero=movement_acct_1 --profile movement_acct_1 Compiling, may take a little while to download git dependencies…<br> ... <br>package size 7437 bytes Do you want to submit a transaction for a range of [545200 - 817800] Octas at a gas unit price of 100 Octas? [yes/no] &gt;<br> yes<br> {<br> &quot;Result&quot;: { <br>&quot;transaction_hash&quot;: &quot;0x41b176ca7f823bfc57a842202135f458dfa19a0f74f14f9d3852c86d9fcc4c7f&quot;, &quot;gas_used&quot;: 5452, &quot;gas_unit_price&quot;: 100, &quot;sender&quot;: &quot;6e7c05076c385337c5ea2dc522c7f147bb6ad7f60c16d68f6777bde658d12126&quot;,<br>&quot;sequence_number&quot;: 0,<br>&quot;success&quot;: true,<br>&quot;timestamp_us&quot;: 1735302126711277,<br>&quot;version&quot;: 204080358,<br>&quot;vm_status&quot;: &quot;Executed successfully&quot;<br>}<br>}</pre><p>After deployment, you can view the results on the browser:</p><blockquote><a href="https://explorer.movementlabs.xyz/account/0x6e7c05076c385337c5ea2dc522c7f147bb6ad7f60c16d68f6777bde658d12126/modules/code/hero?network=testnet"><em>https://explorer.movementlabs.xyz/account/0x6e7c05076c385337c5ea2dc522c7f147bb6ad7f60c16d68f6777bde658d12126/modules/code/hero?network=testnet</em></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rL79UVCw1LaFmrRJ.png" /></figure><h3>2.2 dApp configuration and deployment</h3><pre># install<br>$ yarn<br># modify the configuration<br>$ vim .env.local<br># start with dev mode<br>$ yarn dev<br># buidl<br>$ yarn build</pre><p>Modify NEXT_PUBLIC_DAPP_ADDRESS in .env.local to the address of the contract you deployed.</p><h3>0x03 dApp Function Introduction</h3><h3>3.1 Wallet Connection</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/0*gTi7vg02556omEfL.png" /></figure><p>Currently supports three mainstream wallets: Nightly, Petra and OKX.</p><h3>3.2 Wallet, Account and Network Information Display</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XEU6hnXWts-9YWw5.png" /></figure><h3>3.3 Signature and Signature Verification</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3N1JvVu2CptPvaLT.png" /></figure><p>Signature success prompt:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/0*9wafTTRNbnA-sNg9.png" /></figure><p>Signature + signature verification success prompt:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/0*BQmkqZbVkLnvOPeJ.png" /></figure><h3>3.4 View Resources</h3><p>Take view balance as an example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J9kPRJXrVsQYDtJZ.jpg" /></figure><p>Source code:</p><pre>const getBalance = useCallback(async () =&gt; {<br>if (!adapter || !aptos) return; <br>const account = await adapter.account(); <br>const balance = await doGetBalance(aptos, account.address.toString()); <br>toast({ <br>title: &quot;balance&quot;, <br>description: balance!.toString(), <br>}); <br>}, [aptos, account]); <br>​<br>async function doGetBalance(aptos: Aptos, accountAddress: string) {<br> const [balance] = await aptos.view({ <br>payload: { <br>function: &quot;0x1::coin::balance&quot;, <br>typeArguments: [&quot;0x1::aptos_coin::AptosCoin&quot;], <br>functionArguments: [accountAddress], <br>}, <br>}); return balance; <br>} <br>... <br>&lt;button <br>onClick={getBalance}<br>className=&quot;px-4 py-2 bg-blue-500 text-white rounded-md hover:bg-blue-600 transition-colors&quot; <br>// disabled={!connected || !adapter || !aptos}<br>&gt;<br>View Example: Get Balance<br>&lt;/button&gt;</pre><h3>3.5 Function call</h3><p>Take the call of transfer function as an example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z_J2TuytsoXNVEdy.png" /></figure><p>Source code:</p><pre>const handleTransaction = useCallback(async () =&gt; {<br>// Docs: https://docs.nightly.app/docs/aptos/solana/connect<br>// console.log(&quot;info&quot;, account, adapter, aptos);<br>if (!account?.address) return;<br>const network = await adapter?.network();<br>if (network?.chainId !== 177) {<br>try {<br>await adapter?.changeNetwork({ name: Network.TESTNET, chainId: 177 }); <br>} catch (error) { <br>console.error(&quot;Failed to change network:&quot;, error); <br>} <br>} <br>const aptosConfig = new AptosConfig({ <br>network: network?.name || Network.TESTNET, <br>}); const aptosClient = new Aptos(aptosConfig); <br>const transaction: InputGenerateTransactionPayloadData = { <br>function: &quot;0x1::coin::transfer&quot;, <br>typeArguments: [&quot;0x1::aptos_coin::AptosCoin&quot;],<br>functionArguments: [ &quot;0x960dbc655b847cad38b6dd056913086e5e0475abc27152b81570fd302cb10c38&quot;,<br> 100,<br> ], <br>}; <br>​<br>const userResponse = await signAndSubmitTransaction({ <br>payload: transaction, <br>}); <br>​<br>if (userResponse.status !== UserResponseStatus.APPROVED) { <br>throw new Error(userResponse.status); <br>} <br>// Confirm withdraw in backend <br>const hash = (userResponse as unknown as { args: { hash: string } }).args <br>.hash; <br>try { <br>await aptosClient.waitForTransaction({ transactionHash: hash }); <br>} catch (error) { <br>console.error(error); <br>} <br>​<br>toast({ <br>title: userResponse.status, <br>description: &quot;This transaction has been &quot; + userResponse.status, <br>}); }, [account]); <br>​<br>... <br>&lt;button <br>onClick={handleTransaction} <br>className=&quot;px-4 py-2 bg-blue-500 text-white rounded-md hover:bg-blue-600 transition-colors&quot; <br>// disabled={!connected || !adapter || !aptos}<br>&gt;<br>Send Transaction Example: Transfer<br>&lt;/button&gt;</pre><h3>0x04 What is the ideal dApp scaffold?</h3><h3>4.1 Fully implementing the Web3 incentive mechanism that serves DeveloperGC</h3><p>Through the on-chain protocol, the intelligent settlement and intelligent allocation of <strong>developer contributions</strong> are carried out, and the Scaffold case is encouraged to be improved through open source collaboration, which is essentially equivalent to the implementation of Scaffold-Move-DAO.</p><h3>4.2 AI Friendly</h3><p>Through the autonomous vector database, the database can be self-expanded from multiple channels of the Internet and developer community. On this basis, LLM support is added to further reduce the mental burden and time cost of developers.</p><pre>+--------------------+              +---- From Internet<br>|      VectorDB      |  Data Growth |<br>|       about        |&lt;-------------+---- From Dev Community<br>| Contract/dApp Code |              |<br>+--------------------+              +---- ...<br>          ↓ Feed<br>+--------------------+      +----------------+<br>|        LLM         |-----&gt;| Scaffold-Move  |---+--- Generate Contract Code<br>+--------------------+      +----------------+   |<br>                                                 +--- Generate dApp Code</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69d2a69a3465" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Embedding Search: The Underrated Search Algorithm]]></title>
            <link>https://medium.com/@root_mud/embedding-search-the-underrated-search-algorithm-0dd0eacc4abd?source=rss-ee35a88e63af------2</link>
            <guid isPermaLink="false">https://medium.com/p/0dd0eacc4abd</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[embedding]]></category>
            <dc:creator><![CDATA[rootMUD]]></dc:creator>
            <pubDate>Tue, 07 Jan 2025 21:27:54 GMT</pubDate>
            <atom:updated>2025-01-07T21:27:54.152Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*4i0jHb-xbXYYyr8_UvBDWg.png" /></figure><h3>0x01 What is Embedding?</h3><h3>1.1 Embedding as a data representation</h3><p>Embeddings are a data representation that allows us to easily find the “correlation” between two or more data points. They are powerful because they allow you to store unstructured data (that is, data that does not fit neatly into the JSON format) and create searchable systems based on this data.</p><p>Embedding example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SwkArhyjIsSrXJLbf6VWoQ.png" /></figure><p>From an abstract perspective, the data structure design based on Embedding will include three parts: data (Data), metadata (MetaData) in JSON format, and vector data (Embedding). Among them, data is responsible for content storage, Embedding is the coordinate of the content in the vector space, and MetaData is responsible for data labeling📌.</p><p>There are two points to note:</p><p>1/ If necessary, the data in MetaData can be flattened to facilitate retrieval and other data operations.</p><p>2/ The ID can either be a traditional incremental ID or a unique ID like a UUID.</p><h3>1.2 Embedding as a Data Correlation Algorithm</h3><blockquote><em>💡The following content is from </em><a href="https://platform.openai.com/docs/guides/embeddings"><em>OpenAI Documentation</em></a></blockquote><p>Embeddings is a type of algorithm used by OpenAI to measure the correlation between content.</p><blockquote><em>💡ANN (Approximate Nearest Neighbor Algorithm) and KNN (Nearest Neighbor Algorithm) can both be classified under the category of Embedding algorithms.</em></blockquote><p>Common application scenarios of Embeddings include:</p><ol><li>Search (ranking results based on the relevance of the query content)</li><li>Clustering (grouping similar content)</li><li>Recommendation (recommending items with related content)</li><li>Anomaly detection (identifying outliers with low relevance)</li><li>Diversity measurement (analyzing similarity distribution)</li><li>Classification (classifying content based on the most similar tags)</li></ol><p>Embedding is essentially a list of floating point numbers (vector). The distance between two vectors is used to measure their relevance:</p><ul><li>Small distance means high correlation</li><li>Large distance means low correlation</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*W9xLtdX8qWYuoCvAq3BDFA.png" /></figure><h3>0x02 Why choose Embedding algorithm?</h3><h3>2.1 General advantages</h3><p>If you search for 🔍 related literature, you will find two advantages of Embedding algorithm:</p><ul><li><strong>Multimodal support:</strong> Different types of content can be Embedded, so Embedding algorithm can be used as a solution for various types of search. If it is a traditional retrieval solution, different algorithms need to be selected for different data types.</li><li><strong>Simplicity and efficiency:</strong> Simplicity and efficiency are the characteristics of the Embedding algorithm. The most intuitive proof is that we can use the PostgresSQL 🐘 function with less than 30 lines of code to implement retrieval:</li></ul><pre>-- this search algorithm is impled under 30 line!<br>create or replace function embedding_search_bodhi_text_assets_k_v_space_145 (<br>query_embedding vector(3072),<br>match_threshold float,<br>match_count int<br>)<br>returns table (<br>id int,<br>data text,<br>metadata json,<br>creator text,<br>id_on_chain int,<br>similarity float<br>)<br>language sql stable<br>as $$<br>select<br>bodhi_text_assets_k_v_space_145.id,<br>bodhi_text_assets_k_v_space_145.data,<br>bodhi_text_assets_k_v_space_145.metadata, bodhi_text_assets_k_v_space_145.creator, bodhi_text_assets_k_v_space_145.id_on_chain, 1 - (bodhi_text_assets_k_v_space_145.embedding_3072 &lt;=&gt; query_embedding) as similarity from bodhi_text_assets_k_v_space_145 where bodhi_text_assets_k_v_space_145.embedding_3072 &lt;=&gt; query_embedding &lt; 1 - match_threshold order by bodhi_text_assets_k_v_space_145.embedding_3072 &lt;=&gt; query_embedding limit match_count; <br>$$;</pre><h3>2.2 Ignored “cost upfront”</h3><p>However, these two advantages are purely an evaluation of the Embedding algorithm from the perspective of computer science. Therefore, the Embedding algorithm is often questioned — <strong>These advantages can only be regarded as “vitamins 💊”, not “painkillers 🩹”. It is good to use it, but it is not impossible to use traditional solutions 🤔.</strong></p><p>I think this is because the biggest feature of the Embedding algorithm has been overlooked by people, that is:</p><blockquote><em>The Embedding algorithm imposes </em><strong><em>“cost upfront”.</em></strong></blockquote><p>Data entry costSearch cost<strong>Traditional search algorithm</strong>NoneBackend server cost<strong>Embedding algorithm</strong>Vectorization costRetrieval content vectorization cost</p><p>The Embedding algorithm transfers the backend server cost required by the traditional search algorithm to the vectorization cost of the content, including the vectorization of the retrieved content and the vectorization of the retrieved content.</p><p>This seemingly small change opens up a world of possibilities 🏈.</p><p>For example, combined with our newly designed “backend-free” AI SaaS framework, anyone can build their own search engine at a very low cost🔍!</p><pre>User<br>               ↓ Request<br>+-----------------------------------------------------------------+<br>|                           Stack                                 |<br>+-----------------------------------------------------------------+<br>| User | Task | Solution | Resolver | Fee | Rate | Human/AI/Both  |<br>+-----------------------------------------------------------------+<br>                ↑ Handle                     ↑ Handle<br>             AI Services                    Human Services</pre><p><strong>Under the new architecture, the cost of the backend server is replaced by the cost of a local idle computer, Awesome!</strong></p><blockquote><em>📄 </em><strong><em>Supplementary information:</em></strong></blockquote><blockquote><em>In fact, this method is very classic… In 1999, we could provide computing power for “looking for aliens 👽” through computer screensavers…</em></blockquote><blockquote><a href="https://setiathome.berkeley.edu/"><em>https://setiathome.berkeley.edu/</em></a></blockquote><h3>2.3 Web3-based &amp; AI-Friendly &amp; Low-Cost Search Engine</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bQA_PD6psVRfOkE6Lj6ieg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0dd0eacc4abd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a “Mass Maintenance” BuidlerBoard | BeWater.xyz]]></title>
            <link>https://medium.com/@root_mud/designing-a-crowdsourced-buidlerboard-bewater-xyz-1e5d2f3d2ed3?source=rss-ee35a88e63af------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e5d2f3d2ed3</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[bewater]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[rootMUD]]></dc:creator>
            <pubDate>Sun, 05 Jan 2025 13:07:05 GMT</pubDate>
            <atom:updated>2025-01-05T13:15:43.655Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/251/1*-b9FlSg6iaEjUawKXxaMJg.png" /></figure><blockquote><a href="https://buidlerboard.bewater.xyz/"><em>https://buidlerboard.bewater.xyz</em></a></blockquote><h3>0x01 Talk is Cheap, Show me the Code</h3><p>In the Web3 world, there’s a well-known saying:</p><blockquote><strong><em>Talk is Cheap, Show me the Code.</em></strong></blockquote><p>Sometimes this saying is questioned; other times, it’s validated.</p><p>However, just like students studying economics believe that <strong>“in the long run, prices will fluctuate around value”</strong>, as Buidlers, many of us also believe that:</p><blockquote><em>In the long run, </em><strong><em>the value of the project fluctuates around the value of the code</em></strong><em>.</em></blockquote><p>The biggest advantage of adopting this as a “principle” is that it offers an excellent balance between “mental load” and “effectiveness”.</p><p>We can naturally increase our mental load and design a more complex “project evaluation standard”, thereby increasing our <strong>“evaluation effect”</strong> of the project. But for buidlers, <strong>mind is the most valuable resource</strong>. So, do we really want to do this? Are we sure that “optimization” is not picking up sesame seeds and throwing away watermelons 😂?</p><blockquote><em>Reference: “Independent Hacker Startup Operating System”</em></blockquote><p>After trying various approaches, many Buidlers, including myself, end up returning to this simple principle. The easiest way to decide whether to participate in a project is to open its GitHub Org, browse through the repositories, and within 30 seconds, we often reach a conclusion.</p><p>In reality, BuidlerBoard — a subjective leaderboard that exists in the minds of all Buidlers — has already been around for a long time. As Buidlers, the projects we contribute to through Pull Requests reflect the Repos and Developers listed on our mental BuidlerBoard.</p><h3>0x02 A “Crowdsourced” BuidlerBoard</h3><p>BeWater’s current initiative is to take this subjective BuidlerBoard and “upgrade” it into a “crowdsourced” BuidlerBoard.</p><p>Many interesting innovations come from this “publicization” attempt.</p><ul><li><strong>Bitcoin: </strong>Originally, centralized institutions maintained their own ledgers. Upgrading to “collective maintenance by many nodes” led to Bitcoin.</li><li><strong>WeChat Read: </strong>Initially, people made personal reading notes, but upgrading to “collective reader-maintained notes” evolved the experience.</li><li>…</li></ul><p>So, the BuidlerBoard project is essentially exploring the following questions:</p><ul><li>How would a “crowdsourced” BuidlerBoard evolve if launched?</li><li>What new possibilities arise if this BuidlerBoard becomes infrastructure?</li></ul><h3>0x03 How will BuidlerBoard evolve?</h3><p>The first version of BuidlerBoard has been released, including Developer-based BuidlerBoard:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*38JxAczrjPS-xCeT.png" /></figure><p>and BuidlerBoard based on Repo code repository:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YrxLOrjFhgbSTJH1.png" /></figure><p>In addition to some conventional fixes such as mobile phone adaptation, there are some “evolutionary space” as follows:</p><ul><li><strong>Project submission portal</strong></li></ul><p>Developers can submit a link🔗 to add a Repo to the data source. This feature is key to enabling “crowdsourced maintenance.”</p><ul><li><strong>Two versions are divided into Github BuidlerBoard and BeWater Projects BuidlerBoard</strong></li></ul><p>The initial release covers all open-source GitHub projects. In the future, to encourage participation in the BeWater Hackathon Platform, a dedicated BeWater Projects BuidlerBoard may be introduced for registered Projects and Buidlers.</p><ul><li><strong>On-chain Integration</strong></li></ul><p>Store BuidlerBoard data on the blockchain.</p><p>Here are some suggestions from <strong>Jolestar</strong>:</p><blockquote><em>Put the builder and repo info on chain, and sync the git root to chain periodically. And I suggest training an AI to give a score to the builder.</em></blockquote><blockquote><em>Use Cases:</em></blockquote><p>1/ Provide commit proof or contribute proof via the git root.</p><p>2/ Projects can airdrop to the builder via the info on-chain or proof.</p><p>3/ The AI agent on-chain can evaluate the builder and give a grant.</p><blockquote><em>— — </em><a href="https://github.com/orgs/BeWaterXYZ/discussions/575"><em>https://github.com/orgs/BeWaterXYZ/discussions/575</em></a></blockquote><blockquote><em>💡Since 24 years, BeWater has started the practice of Web3 and Open-Source in project governance, hoping to transform from “traditional software engineering model” to “no-access, 🌏globalized, self-evolving Web3 software engineering model” (ᕦʕ •ᴥ•ʔᕤ):</em></blockquote><blockquote><a href="https://github.com/orgs/BeWaterXYZ/"><em>https://github.com/orgs/BeWaterXYZ/</em></a></blockquote><ul><li><strong>Algorithm update</strong></li></ul><p>From the perspective of traditional software engineering, software is considered an inorganic substance, while from the perspective of “Web3 software engineering”, we consider software as <strong>“living organisms”</strong>, which is also the key point and difficulty in understanding the new model of “Web3 software engineering”.</p><p>If we consider software as an inorganic substance, then the design principles of “no mistakes” and “no flaws” should be taken as the design principles at the very beginning, just like a skilled craftsman carving a work;</p><p>However, if we consider software as a “living organism”, then the design principles become “simple” and “self-evolvable”. Think about the origin of life under natural occurrence! The extremely simple initial principles combined with the deduction of time eventually evolved into complex and robust living organisms.</p><p>Similarly, we need to start with “simple principles” and give them space and time to evolve.</p><p>Take BuidlerBoard as an example, using a simple algorithm as the initial design — —</p><blockquote><strong><em>Use the number of stars as the basis for sorting Developers and Repos.</em></strong></blockquote><p>After that, we let the evolution of this algorithm be driven by the community — — Is there a more reasonable sorting algorithm? Come to Github Discussion to make your suggestions:</p><blockquote><em>ε(´｡•᎑•`)っ ~ </em><a href="https://github.com/orgs/BeWaterXYZ/discussions"><em>https://github.com/orgs/BeWaterXYZ/discussions</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e5d2f3d2ed3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RootMUD DAO: 7e8 年度总结]]></title>
            <link>https://medium.com/@root_mud/rootmud-dao-7e8-%E5%B9%B4%E5%BA%A6%E6%80%BB%E7%BB%93-88f60ec3cfa2?source=rss-ee35a88e63af------2</link>
            <guid isPermaLink="false">https://medium.com/p/88f60ec3cfa2</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[dao]]></category>
            <dc:creator><![CDATA[rootMUD]]></dc:creator>
            <pubDate>Tue, 31 Dec 2024 13:51:41 GMT</pubDate>
            <atom:updated>2024-12-31T13:51:41.398Z</atom:updated>
            <content:encoded><![CDATA[<p>作者：社区经理 Olab, Founder LeeDuckGo</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*px7UBMGTdEYtgEPr.jpg" /></figure><p>rootMUD DAO 是一个由人工智能驱动基于 Move 生态的虚拟 Web3 社区。</p><p>通过将 AI 技术融入 Web3 生态系统，我们正在构建新一代用户社区。</p><p>回顾过去的一年，我们完成了许多目标。虽然我们遇到了项目发展过程中常见的挑战，但我们将其视为学习、适应和加强系统的机会。</p><h3>已实现的里程碑</h3><ul><li><strong>AO 自主宠物 v1.0：</strong>在 AO 生态系统上推出了我们的第一款游戏，获得了用户的广泛好评和采用</li><li><strong>人生重开模拟器 Relive：</strong>基于 AI Agent 的游戏构建的实验，同时也是构建多链游戏的实验，目前设计包含如下版本：Web2 版本、AO 版本、EVM 版本（测试版）、Move 版本（开发中）…</li></ul><blockquote><a href="https://relive.noncegeek.com/">https://relive.noncegeek.com</a></blockquote><blockquote><a href="https://relife.rootmud.xyz/">https://relife.rootmud.xyz/</a></blockquote><ul><li><strong>Scaffold Aptos：</strong>一个AI Friendly 的脚手架的项目，让开发者能在降低 80% 心智成本与时间成本的情况下构建 Move 应用！</li></ul><blockquote>https://scaffold.rootmud.xyz</blockquote><ul><li><strong>MoveDID：</strong>构建基于 Move 的数字身份协议</li><li><strong>AptosCraft ：</strong>基于 Move 构建的游戏协议 —— 去中心化的 NFT 合成台，是未来构建 Move 游戏生态的基础工作</li><li><strong>BeWater 平台建设：</strong>持续参与 BeWater Hackathon Platform 的平台建设工作。</li></ul><blockquote>https://bewater.xyz</blockquote><h3>社区与参与</h3><ul><li><strong>社交媒体增长：</strong>Twitter 和 Telegram Group 完成了初步发展。</li><li><strong>黑客马拉松和赏金计划：</strong>参与了多个生态的 Hackathon 和 Grant 活动，和多个生态与项目方建立了良好的合作关系。</li></ul><p><strong>代币经济学与治理</strong> 作为社区驱动的 DAO，我们通过社区投票将代币从 Mapo 网络转移到 Rooch 网络。今年没有发生重大代币销毁事件。</p><h3>挑战与解决方案</h3><h4>技术挑战</h4><p><strong>开发人员短缺</strong>：我们需要更多的 Contributors!</p><p><strong>解决方案</strong>：我们启动了内部黑客马拉松和赏金计划来吸引有才华的开发人员，并寻求与信誉良好的开发人员社区建立合作伙伴关系。</p><h4>市场挑战</h4><p><strong>代币酝酿阶段</strong>：我们的代币全年处于发展和准备阶段，由于战略定位，市场曝光度有限。</p><p><strong>解决方案</strong>：为了提高<strong>可玩性</strong>，我们启动了将我们的代币从 Mapo 网络迁移到新的 Move-based 网络。</p><p>未来展望 展望未来，RootMUD DAO 将继续致力于推动创新、扩大我们的生态系统并培育全球开发者社区。</p><h3>感谢 ❤️</h3><p>当我们结束这一章并展望美好的未来时，我们要向今年参与 RootMUD DAO 旅程的每个人表示最深切的感谢。</p><p>对于我们的社区成员、开发者、合作伙伴和支持者来说，你们对我们使命的信任和持续的参与一直是我们成长和成功的驱动力。你们的反馈、参与和合作塑造了我们迄今为止所取得的成就，并将继续激励我们未来的发展。</p><p>感谢我们的开发团队和贡献者们的辛勤工作、创造力和奉献精神。你们对创造人工智能和 Web3 双驱的社区的热情成就了 RootMUD DAO 的今天。</p><p>对于我们的合作伙伴和合作者，我们珍视你们对我们的信任，并期待在来年加强我们的关系。</p><p>感谢您参与这次旅程。我们迫不及待地想看看明年我们能一起取得什么成就。</p><p><strong>怀着感激之心，</strong> <strong>RootMUD DAO 团队</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88f60ec3cfa2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Movement 白皮书中文版]]></title>
            <link>https://medium.com/@root_mud/movement-%E7%99%BD%E7%9A%AE%E4%B9%A6%E4%B8%AD%E6%96%87%E7%89%88-6906858895c9?source=rss-ee35a88e63af------2</link>
            <guid isPermaLink="false">https://medium.com/p/6906858895c9</guid>
            <category><![CDATA[movement]]></category>
            <category><![CDATA[move]]></category>
            <dc:creator><![CDATA[rootMUD]]></dc:creator>
            <pubDate>Thu, 12 Dec 2024 11:59:15 GMT</pubDate>
            <atom:updated>2024-12-19T08:56:15.775Z</atom:updated>
            <content:encoded><![CDATA[<h3>摘要</h3><p>我们推出了 Move Stack Chains，这是一个由以太坊保护的基于 Move 的安全可扩展性 rollup 网络，旨在满足更安全执行环境的需求。其核心是 Move Stack，这是一个用于创建高度可定制 Move Rollup 的模块化框架。</p><p>Movement Network 作为我们的旗舰通用型 L2 Move Rollup，展示了 Move Stack 的主要功能：</p><ol><li><strong>Move 执行器：</strong>具备 MoveVM 的高吞吐量执行层，支持并行执行和 EVM 兼容性，可与现有应用程序无缝集成。</li><li>创新的快速最终确定结算机制，通过验证者网络的经济安全性实现秒级确认时间，同时保持以太坊的安全性。</li><li><strong>模块化：</strong>Move Stack 可以集成多个数据可用性（DA）服务和排序器。开发者还可以选择「有效」或「乐观」 rollup 配置，以达成传统的以太坊安全保证。</li></ol><p>我们还推出了 Move Arena，这是一个复杂的基础设施，将 Move Stack Chains 与我们的内部服务集成，并支持下一代可互操作 rollup 生态系统。作为 Move Arena 的一部分，rollup 可以受益于我们的去中心化共享排序器网络（DSS），该网络实现了无缝的跨 rollup 互操作性，增强了抗审查能力，并消除了单点故障。</p><p>DSS 通过我们的多重质押机制来确保安全性，该机制在 Move Stack Chains 及其他链上汇集经济安全性，最大限度地减少基础设施要求，并最大化每个 Move Rollup 的主权性。</p><h3>目录</h3><p>1 目标与动机</p><p>2 Movement 网络</p><p>2.1 原始组件</p><p>2.2 原始框架</p><p>3 Move Rollup 框架和 MoveVM</p><p>3.1 Move Rollup 架构</p><p>3.2 Move 执行器</p><p>3.3 Move Stack</p><p>4 快速最终确定结算</p><p>4.1 以太坊结算和安全性</p><p>4.2 有效性和乐观 rollup 的安全性</p><p>4.3 快速最终确定结算的安全性</p><p>4.4 后确认</p><p>4.5 双重最终确定性</p><p>5 Move Arena</p><p>5.1 Move Stack Chains：应用特定链网络</p><p>5.2 DSS：去中心化共享排序器</p><p>5.3 多资产质押</p><h3>词汇表</h3><p>Move — 用于 MoveVM 的编程语言和运行时环境。</p><p>Movement Network — 通用型基于 Move 的 rollup。</p><p>Move Rollup — 基于 Move 的 rollup 蓝图。</p><p>Move Stack Chains — 基于 Move 的 rollup 网络。</p><p>Move Executor — 支持执行 MoveVM 和 EVM 字节码的模块。</p><p>Move Stack — 用于构建和部署自定义 Move Rollup 所需的工具、组件和适配器堆栈。</p><p>DSS （Decentralized Shared Sequencer） — Move Stack 的去中心化共享排序器。</p><p>Move Arena — 使 Move Rollup 能够访问 DSS 和质押结算机制的框架。</p><h3>1 目标与动机</h3><p>区块链技术提供了一个去中心化账本，参与者无需依赖中央机构就能进行交易。以太坊网络首次提出了一个多功能的世界计算机概念，具有可编程交易（称为智能合约）的功能，能够实现超越比特币网络简单货币或资产转移的任意业务逻辑。</p><p>以太坊基础技术的广泛采用仍然受到几个限制因素的阻碍，如交易最终确定性的高延迟、低吞吐量（以每秒交易数TPS表示），以及去中心化应用程序（dApps）中普遍存在的安全漏洞。</p><p>以太坊主网凭借其无与伦比的总锁定价值（TVL）水平，提供了最高级别的加密经济安全性，这创造了一个利用其一流安全保障的无可比拟的激励机制。</p><p>为解决以太坊网络上述限制，已提出了多种解决方案。其中最流行的是rollup，这是一种第2层（L2）解决方案，可将多个L2交易打包成单个第1层（L1）交易。注意，在本文中我们将L1和以太坊互换使用，但这也适用于其他L1和L2。Rollup在以太坊主网上结算交易，从而继承其高级别安全性。Rollup成功解决了以太坊的一些可扩展性限制，但尚未能完全解决dApp的安全漏洞和延迟问题。</p><p>以太坊的一些原始设计选择（被以太坊rollup继承）使其成为一个非常复杂的基础设施，难以解决当前的限制。例如，EVM的设计并不能防止安全漏洞、意外的资产重复或重入攻击。EVM本身的全局存储模型使交易执行难以并行化，这严重限制了网络的可扩展性。然而，以太坊网络的设计选择和限制为我们提供了一个很好的机会来反思当前技术并思考如何改进。</p><p>最近，执行层出现了新的范式，提供了新的执行环境和编程语言。后者的一个例子是Move，最初由Facebook（Diem/Libra项目）开发，这是一个新一代高度安全和高效的Web3开发平台，为安全漏洞和可扩展性提供了原则性解决方案。它为Web3开发者提供现代工具，以应对部署可靠、经济高效的dApp的挑战。Move和MoveVM被用于L1链中，如Aptos、Sui和0L，并在安全性、低延迟（亚秒级最终确定性）和吞吐量方面展示了非常有前景的结果（持续报告的吞吐量为30k TPS，理论值160k TPS，相比之下以太坊通常为20 TPS）。</p><blockquote><em>Move语言提出了Web3开发的新方法，旨在解决当前区块链技术的限制。Move引入了一种称为 </em><strong><em>资源导向编程</em></strong><em> 的新编程范式，实现了MoveVM中交易的并行执行，同时通过形式验证提供强大的安全保证。</em></blockquote><p>Move社区面临的主要挑战之一是建立一个加密经济安全的生态系统，但目前，<strong>L1链Aptos、Sui和0L尚未达到以太坊的TVL、流动性和开发者活跃度水平。</strong>这为我们的Move社区提供了一个引人注目的机会，将高度加密经济安全的以太坊平台与最先进的Web3开发平台Move/MoveVM结合起来。</p><blockquote><em>我们的提议是建立一个可互操作的链网络，以弥合Move和以太坊这两个生态系统之间的差距，在这里，</em><strong><em>最先进的Web3技术与最具加密经济安全性的L1链相遇。</em></strong></blockquote><p>我们的贡献：在第2节中，我们介绍了Movement Network，这是一个通用的基于Move的rollup。Movement Network架构源自第3节描述的更通用的Move Rollup蓝图框架，这是我们网络中所有基于Move的rollup共享的。第4节描述了我们新颖的快速最终确定结算机制。在第5节中，我们介绍了Move Arena（基于Move的链网络），以及实现跨链互操作性的共享排序器DSS。</p><h3>2 Movement 网络</h3><p>Movement Network是Movement Labs的通用型rollup（图1）。它是第一个集成了Celestia数据可用性、去中心化共享排序、具有通过快速最终确定结算实现双重最终确定性选项的乐观rollup，以及提供无与伦比交易吞吐量的Move虚拟机（MoveVM）执行环境的以太坊L2。这种集成将使开发者能够以最少的资源消耗创建高性能、面向消费者的应用程序。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PODRUvOhHUFBfHn5.png" /></figure><h3>2.1 原始组件</h3><p>我们开发了三个原始组件，并在Movement Network中加以利用。</p><ol><li><strong>Move执行器</strong>（第3.2节），同时支持MoveVM和EVM交易，使Web3开发者能够在单一网络上部署Move和EVM字节码的智能合约。</li><li><strong>快速最终确定结算模块</strong>（第4节），连接验证者网络，与乐观和有效性结算机制相比，可实现更快的结算最终确定性。</li><li><strong>去中心化共享排序器模块DSS</strong>（第5节），确保可定制的交易排序，具有一系列方法模板，如用于缓解抢先交易攻击和增强抗审查能力的公平交易排序。</li></ol><p>首先，Movement Network同时支持MoveVM和EVM交易。这是我们架构的独特特征，因为大多数rollup只支持一种类型的交易。这个特性对于让Web3开发者快速加入Movement Network至关重要。对于Move Arena（第5节）来说，这也是一个重要优势，<strong>因为它允许开发者利用现有的EVM dApp，并通过Move平台的高级特性对其进行扩展。</strong>例如，像ERC-20这样的标准EVM合约可以部署在Movement Network上，新的安全Move dApp可以开发并与之互操作。</p><blockquote><em>Move执行器支持MoveVM和EVM交易，允许Web3开发者在同一网络上部署Move和EVM字节码的智能合约。它提供了一个独特的基础设施，Web3开发者可以通过更安全和高效的Move框架迁移或扩展其现有的EVM dApp。</em></blockquote><p>其次，我们引入了快速结算机制（第4节），这是有效性和乐观rollup的替代结算机制。快速最终确定结算依赖于一组质押原生代币的验证者。验证者必须通过形成多数（例如，总质押量的2/3）来确认新L2状态的正确性。</p><blockquote><em>快速结算机制提供快速最终确定性，同时也有助于提高Movement Network原生代币的实用性。</em></blockquote><p>第三，通过使用DSS排序器，Movement Network建立在排序市场（如Espresso、Astria或基于L1的排序）的替代方案之上。这是一个深思熟虑的选择，以确保Movement Network（以及更广泛的Move Rollup网络）的主权性，并提供快速、可定制和可验证的交易排序。</p><p>另一个考虑因素是（去中心化）共享排序市场的复杂性，特别是在分配奖励和惩罚方面，这些是目前缺乏良好解决方案的难题。主权排序器模块提供了一个解决方案，其中费用可以由L2而不是外部组件（市场）收取，从而积极影响L2原生代币的实用性。共享排序旨在提供不同rollup之间的某种程度的互操作性，这在第5.2节中讨论。</p><blockquote><em>DSS排序器提供主权的、快速的、可定制的和抗审查的交易排序，实现互操作性并提高Movement Network原生代币的实用性。</em></blockquote><h3>2.2 原始框架</h3><p>我们开发了两个原始框架，并在Movement Network中加以利用。</p><ol><li>Move Stack（第3.3节），以Move执行器为核心，支持创建可定制的rollup。</li><li>Move Arena（第5节），提供部署和加入Move rollup网络的框架。Move Rollup可以配置为连接到Move Arena的各种组件，如快速结算或DSS。这使其能够利用Move Arena的优势，包括与其他Move Rollup的互操作性、快速最终确定性等。</li></ol><h3>3 Move Rollup Framework 与 MoveVM</h3><p>我们介绍 Move Rollup（图2），这是我们基于 Move 的以太坊安全 rollup 的通用架构。Move Rollup 是一个模块化架构，其组件可以根据客户需求进行配置，以提供最合适、最具成本效益和性能的组件。</p><p>在 Move Rollup 中，我们提供欺诈证明、ZK 证明，以及一种新的快速最终性机制（第4节）。在该机制中，由质押了原生代币的验证者网络来验证新的 L2 状态的正确性和数据的可用性，并提供具有高经济安全性的超快速可靠最终性。</p><p>我们在图5中展示了 Move Rollup 配置的分类，并在表1中提供了示例。</p><h3>3.1 Move Rollup 的架构</h3><p>Move Rollup 是一个用于创建基于 Move 的 rollup 的通用架构，这些 rollup 使用 Move 执行器（第3.2节，图2，第8页）。</p><p>Move Rollup 通用架构具有一组核心组件，</p><ul><li>执行器用于处理交易并生成新的 L2 区块</li><li>L1上的桥接合约，用于在 L1 和 rollup 之间进行资产存取</li><li>连接到排序器以对交易进行排序</li><li>连接到数据可用性（DA）服务，确保交易数据对结算机制可访问</li><li>连接到结算机制，验证交易执行的正确性</li></ul><p>Move Rollup 可用于创建基于 Move 的 rollup，例如 Movement Network（第2节）就是这种通用架构的一个实例。</p><p>Move Rollup 中交易的生命周期如下，</p><p>交易 tx 被提交到内存池（客户端，图2顶部）</p><p>排序器从内存池中提取包含 tx 的交易批次 b，并对其进行排序。排序器将 b 的交易数据发布到 DA 服务（L1或替代 DA）</p><p>执行器处理这些交易。这会产生新的 L2 状态（以及其简短的承诺，称为状态根 s），该状态也会发布到 L1 的桥接合约中</p><p><em>图2. 带有 Move 执行器的通用 Move Rollup 架构。黄色部分为架构中的固定组件，而白色部分为可定制组件</em></p><p>交易 tx 的结算发生在 L1 验证桥接合约验证或批准新状态时。这可以通过以下方式完成，使用 ZK 证明、在乐观 rollup 中成功通过挑战期，或在快速最终性结算中验证法定人数证书时。</p><h3>3.2 Move 执行器</h3><p>所有 Move Rollup（如 Movement Network）的执行层都是 MoveVM。Move 技术栈提供了一个执行模块 Move Executor，它可以执行 MoveVM 字节码和 EVM 字节码。该模块是我们架构的核心，且不可配置。</p><p><em>图3. Move 执行器</em></p><blockquote><em>Move Executor 模块支持在同一条链上执行 MoveVM 和 EVM 字节码。</em></blockquote><p>图3展示了 Move Executor 模块的高层视图。根据交易类型（Move 或 EVM），从内存池中对交易进行分类。相应的虚拟机（MoveVM 或 Geth）执行交易。在 MoveVM 中，这会产生一个变更集，随后应用到全局存储中。在 Geth 中，交易可以被执行并修改全局存储，也可以被追踪以生成可应用于全局存储的变更集。这提供了一种方式，使 Move 和以太坊交易都能以通用格式更新全局存储。另一个很好的特性是，读/写集也可以通过 Geth 提取，并可以无缝地在 MoveVM 内置的并行执行引擎 BlockSTM 中使用。</p><blockquote><em>Move Executor 复用现有的 EVM 解释器，并与 MoveVM 无缝集成以利用其并行执行引擎，从而提供并行 EVM。此外，在底层使用现有的 EVM 解释器确保了 Move Rollup 与 EVM 等效，且执行的 EVM 字节码与 L1 上的行为相同。</em></blockquote><p><em>图4. Move 技术栈提供了一组组件（黄色框）和适配器（白色框）。要从 Move Rollup 蓝图创建 rollup 实例，需要从可用选项中选择（即配置）组件</em></p><h3>3.3 Move Stack</h3><p>Move 技术栈提供支持来创建和部署 Move Rollup。开发者可以通过从 Move 技术栈提供的选项中选择合适的组件，快速在网络中启动新的 Move Rollup，如图4所示。</p><p>Move 技术栈的（可配置）组件包括：</p><ul><li><strong>排序器</strong>：rollup 可以选择使用默认的 DSS（去中心化共享排序服务），但也提供了默认的自主排序机制。</li><li><strong>数据可用性</strong>：我们计划支持以太坊 EIP-4844 blob，以及主要的 DA 解决方案（例如 0G、Avail、Celestia、EigenDA、Near）。</li><li><strong>结算机制</strong>：乐观（欺诈证明）、ZK（有效性证明）、快速最终性（认证）。</li></ul><p><em>表1. Move Rollup 配置的例子</em></p><p>表1展示了 Move Arena(第5节)中各种不同类型的 Move Rollup,展示了基于特定需求的广泛定制可能性。此外,使用 Move 技术栈部署 Move Rollup 促进了关键基础设施组件的标准化,包括钱包软件、开发者 API 和区块浏览器。这种标准化增强了互操作性,显著改善了整个 Move Arena 生态系统中开发者和用户的体验。</p><h3>4 快速最终确定结算</h3><p>Move Rollup框架的模块化特性使得链可以通过一种新颖的质押机制来确保安全。这种质押机制提供了具有高加密经济安全性的快速最终性。</p><blockquote><em>💡注：在区块链领域，”finality”（最终性）是一个重要的技术概念，表示交易达到一个确定且不可更改状态的时间点。</em></blockquote><p>由于我们的快速最终性结算方法在安全性方面与以太坊的工作方式类似，我们将回顾与此背景相关的基本概念，特别是以太坊的安全模型（第4.1节）和ZK与乐观rollup的安全性（第4.2节）。然后，我们引入后确认（Postconfirmations）的概念，这是实现快速最终性结算的一种简单机制（第4.3节）。我们将快速最终性结算提供的安全级别与乐观和有效性rollup进行比较，详见图5。最后，我们提出将传统rollup结算与快速最终性结算相结合的双重最终性方案，以同时提供以太坊安全性和经济保护的快速最终性保证（第4.5节）。</p><p><em>图5 Rollup的分类。Move Rollup是可配置的，可以采用上述任何形式。Movement Network是一个采用乐观方法和快速最终性结算的双重最终性rollup</em></p><blockquote><em>💡注：这里的”dual-finality”（双重最终性）是指该网络同时具备两种确认机制，既有乐观rollup的特性，又有快速最终性结算的特点。</em></blockquote><h3>4.1 以太坊结算和安全性</h3><p>以太坊的共识是一个权益证明（PoS）协议，验证者必须质押一定数量的资产（32 ETH）以激励他们诚实地验证状态转换。如果验证者表现出拜占庭（恶意）行为，就要承担被削减质押的风险。在以太坊主网（L1）上，一旦状态转换（新区块的创建）获得了足够多验证者的认证，就被视为最终确定。”足够的质押”通常被理解为所有验证者总质押量的2/3 — 即超级多数。因此，在假设少于1/3的验证者是恶意的情况下，如果超过2/3的验证者已经认证了一个状态转换，那么这个状态转换必定是正确的，因为在这2/3的验证者中至少有一个是诚实的（非拜占庭）。</p><p>PoS机制提供的安全性有两个方面：</p><ul><li>活性：为了阻止超级多数对正确的状态转换进行认证，攻击者需要控制超过1/3的验证者。当系统中的总质押量很大时，这被认为是不可行的（发生这种情况的概率可以忽略不计）。</li><li>安全性：为了强制执行不正确的状态转换（例如，双重支付），攻击者需要控制2/3的验证者。与前一点类似，在有足够大的质押量的情况下，这也被认为是不可行的。</li></ul><blockquote><em>以太坊安全性：安全级别，即以太坊网络的活性和安全性（状态转换的正确性），会随着系统中的总质押量增加而提高。总质押量越高，网络就越安全。以太坊网络提供的安全级别通常被称为”以太坊安全性”。</em></blockquote><h3>4.2 有效性和乐观rollup的安全性</h3><p>rollup主要有两种类型：有效性（ZK）rollup和乐观rollup。两者都在第一层（如以太坊主网）上进行结算，但使用不同的结算机制。</p><p>在ZK-rollup中，当状态转换的ZK证明被接受时就完成了结算。这是通过向L1验证者合约提交验证交易来实现的。由于验证者是作为L1上的合约实现的，验证阶段的安全级别就是以太坊的安全性。在假设ZK证明系统（证明生成和验证者合约）是正确的前提下，ZK证明当且仅当状态转换正确时才会被接受。</p><blockquote><strong><em>ZK-rollup安全性：</em></strong><em>ZK-rollup的安全级别与以太坊的安全性相同：ZK-rollup继承了以太坊的安全性。</em></blockquote><p>在乐观rollup中，交易的最终性 — 在向第一层提交数据和状态承诺后 — 是在一个称为挑战期的时间窗口结束时达成的。因此，安全性是有条件的：如果在挑战期结束时（通常是7天）没有成功的争议，则结算完成。争议是对状态转换提出质疑的一种方式。如果验证者认为状态转换计算错误，可以对其提出争议。可信的争议解决机制会解决这个挑战：如果挑战成功，提交错误状态转换的人会被削减质押。否则，发起挑战的验证者会被削减质押。假设至少有一个诚实的验证者（如瞭望塔）重新执行每个L2状态转换，L2提交错误的新状态在实践中是不可行的。安全级别取决于争议在哪里解决。如果是通过合约在以太坊主网上解决（例如在[14]中），且解决争议的合约是可信的（没有漏洞），那么争议解决的安全性就是以太坊的安全性。</p><blockquote><strong><em>乐观rollup安全性：</em></strong><em>乐观rollup的争议解决机制可以继承以太坊的安全性。但如果在挑战期结束之前没有验证者检查状态转换，那么安全级别就是零。</em></blockquote><p>以太坊主网上状态转换（即交易）的最终性大约需要12分钟。生成ZK证明平均需要10–15分钟，因此ZK-rollup上的交易最终性预计需要20–25分钟。对于乐观rollup，标准挑战期是1周。在这两种情况下，交易最终确认所需的时间对某些（如果不是许多）应用来说可能过长。</p><h3>4.3 快速最终性结算的安全性</h3><p>如前几节所述，有效性（零知识证明，ZKP）和乐观（欺诈证明，FP）rollup可以分别在大约30分钟和1周内以太坊安全级别完成交易最终确认。然而，在交易最终确认之前，对其有效性和结果（成功或失败）的保证是有限的。这可能会成为许多DeFi应用的限制因素。通过快速最终性结算，可以提供一个中间级别的经济安全性，但具有快速最终性保证。</p><p>快速最终性结算通过权益证明（PoS）协议提供安全性。在PoS协议中，验证者质押一些资产（例如，以L2原生代币形式）以激励他们诚实地验证L2状态转换的状态。如果他们不诚实（接受错误的状态转换或拒绝正确的状态转换），他们的质押可能会被削减。如果他们是诚实的验证者，他们会因其活动而获得奖励。验证者网络可以为正确执行的区块提供快速且具有经济支持的确认。更准确地说，验证者的角色是确认状态转换的执行是正确的。</p><p>在仅使用快速最终性结算的Move Rollup上，当有足够多的验证者确认了状态转换的正确性时，该状态转换（对应于一组交易的执行）就达到了L2最终性（不可逆）。为简单起见，我们假设所有验证者质押相同的金额，”足够多”意味着超过2/3的验证者。全部质押价值称为L2-Stake。图6说明了快速最终性结算的过程，以及交易达到（L1/L2）最终性所需的时间。</p><p>总的来说，用户现在可以快速获得关于其交易结果的保证，并可以决定这是否足以假定交易不可逆，或是否要等待L1最终性（通过ZKP或FP）以获得以太坊级别的安全性。</p><p><em>图6. 安全级别和最终确认时间。最终确认时间不包括L1（以太坊）的平均最终确认时间（13分钟）。显示的时间仅供参考，可能会有所变化</em></p><p><strong>与乐观和ZK-rollup的比较：</strong></p><p>乐观rollup在有诚实验证者对每个错误的状态转换提出争议的条件下，继承了以太坊的安全性。然而，目前乐观rollup限制了挑战者的名单，以减少延迟攻击的风险（在这种攻击中，攻击者可以发起尽可能多的争议，只要他们愿意放弃保证金）。以上所有这些都对用户施加了重要的信任假设。此外，与验证者网络中的总质押保护相比，削减惩罚在经济上可能并不够大。</p><p>与ZK-rollup相比，仅采用快速最终性结算的Move Rollup不需要昂贵的证明生成设备。然而，快速最终性结算带来的最显著改进是与乐观和ZK-rollup相比大大减少了延迟。由于认证可以在几秒钟内完成，我们可以提供快速最终性保证并大幅改善用户体验。这与ZK-rollup设置中需要数分钟和乐观设置中需要数天形成对比。</p><p>快速最终性结算对于互操作性和原子跨rollup交易（需要快速结算时间）来说至关重要。乐观和ZK-rollup在这方面都存在不足。希望在不久的将来，允许使用专用硬件进行实时证明的ZK证明技术能够广泛使用，但目前尚不清楚这一点何时能够实现。</p><p>关于乐观rollup，它们本质上需要较长的挑战期（最多一周）来应对社会工程和攻击向量。相比之下，快速最终性rollup可以在几秒钟内提供最终性保证。</p><blockquote><em>参考资料：</em><a href="https://docs.arbitrum.io/how-arbitrum-works/bold/gentle-introduction"><em>https://docs.arbitrum.io/how-arbitrum-works/bold/gentle-introduction</em></a></blockquote><blockquote><em>快速最终性Move Rollup可以比乐观rollup更安全，并且比ZK-rollup具有更快的最终性。如果验证者网络的总质押量大于或等于以太坊验证者的总质押量，那么快速最终性Move Rollup甚至可以达到以太坊的经济安全级别。快速最终性结算方法的整体安全性取决于验证者的总质押量。质押、奖励和验证步骤继承了以太坊的安全性。</em></blockquote><p>我们在第5.3节讨论质押机制的一般化形式：多资产质押。</p><p><em>图7 交易的确认阶段。预确认（Preconfirmation）是承诺交易将被包含（甚至执行）在下一个区块中。相比之下，后确认（Postconfirmation）提供由验证者的L2质押经济支持的保证，确保执行者处理交易后的新状态是正确的</em></p><h3>4.4 后确认</h3><p>后确认是快速最终性结算的一种实现。</p><p>首先，我们提供了L1上确认的定义，它与L1最终确认不同。（我们认为将L1确认定义为与L1最终性相同并不实用）。当状态在L1区块中有承诺时，我们说交易在L1上得到确认。需要注意的是，如果包含该交易的区块成为孤块，已确认的交易仍可能被回滚。</p><p>后确认与预确认不同。它们提供的是新区块正确性的保证，而不仅仅是交易将被包含（或执行）的保证。它也不是复杂执行票据机制的替代品，因为它不提供影响区块创建的方式，而是报告区块中交易执行的正确性。图7描述了交易的确认阶段。</p><p>后确认之所以快速，是因为它们在执行交易区块后、新区块提交时立即发送，见图7。后确认本身可能与状态确认一起被确认（即包含在L1区块中）。</p><p>机制如下：</p><ul><li>一组验证者在可信的L1合约StakingK中质押一些资产。</li><li>对于Move Rollup的给定状态转换，验证者广播他们签名的认证（批准或拒绝），同时收集其他验证者的签名认证。</li><li>当验证者收集到代表超过总质押量2/3的认证时，他们将其提交给StakingK合约。</li><li>StakingK合约验证认证签名是否有效、唯一，并且占总质押量的2/3以上。状态转换成为最终确认。</li></ul><p>由于加密保护的签名，拜占庭验证者无法伪造/篡改签名认证。假设少于1/3的验证者是拜占庭式的，并且由于需要2/3多数，就不可能有恶意行为者能够提交足够的认证来支持错误的状态转换。此外，在同步期间保持活性，因为2/3的质押量也足以完成认证过程。</p><p>验证2/3验证者已确认状态转换的过程由StakingK合约执行。因此，验证步骤继承了以太坊的安全性。质押/削减/奖励功能也在L1上以相同的安全级别执行。</p><p>聚合认证：为了使认证过程更有效率，我们可以要求验证者运行L1轻客户端。他们可以访问StakingK的状态并自行确定有多少验证者处于活跃状态。活跃验证者是指未被削减质押的验证者。</p><p>验证者可以向整个验证者网络广播他们对新区块的投票。验证者可以记录和聚合签名认证。当其中一个验证者确定达到2/3超级多数时，他们可以将聚合的（签名）认证发送给StakingK合约。这减少了记录认证所需的L1交易数量。</p><p>我们还应注意，验证者记录正面和负面的认证，并将两种类型的认证都发送给StakingK。一旦达到2/3超级多数，StakingK合约可以削减那些进行负面认证的验证者的质押，因为他们是不诚实的（假设最多1/3的验证者是拜占庭式的）。</p><h3>4.5 双重最终性</h3><p>虽然快速最终性结算提供了一种快速且经济上稳健的交易最终性形式，但通过将其与乐观和ZK-rollup的已验证安全保证相结合，可以进一步加强。通过分层这些方法，我们可以提供双层安全模型（即双重最终性），利用两个系统的优势。</p><p>在这种组合方法中，快速最终性结算提供由验证者质押的经济安全性支持的最终性级别，确保交易快速确认。系统还可以调用乐观或ZK-rollup的传统最终性机制，这些机制提供源自以太坊主网的额外安全优势，尽管会带来这些方法典型的延迟。</p><p>这种双层最终性模型的运作方式如下：</p><ul><li><strong>快速最终性层</strong>：快速最终性结算框架中的验证者快速确认状态转换的正确性，提供经济上安全且迅速的初始最终性层，通过减少等待时间来改善用户体验。</li><li><strong>乐观/ZK最终性层</strong>：在建立快速最终性后，交易数据还通过第二个最终性机制（乐观或ZK-rollup）在以太坊主网上处理。这确保即使快速最终性机制被破坏（例如，由于验证者的重大但不太可能的串通），交易仍然受益于以太坊的强大安全保证。</li></ul><p>通过组合这些机制，系统提供了高度安全和高效的交易最终性过程：</p><ul><li><strong>改善用户体验</strong>：用户受益于快速最终性结算提供的快速且经济安全的最终性，同时不牺牲以太坊结算层提供的长期安全性。</li><li><strong>灵活性和弹性</strong>：这种方法允许系统适应各种安全需求，根据不同应用的具体要求在速度和安全性之间提供平衡的权衡。</li><li><strong>增强安全性</strong>：两个独立最终性机制的整合显著降低了成功攻击的概率，因为攻击者需要同时破坏验证者网络和二级最终性过程。</li></ul><p>总之，这种双层最终性方法提供了两全其美的优势：<strong>快速最终性结算的快速且经济支持的保证，结合乐观或ZK-rollup的成熟安全性。这种混合模型对于需要即时交易确认和最高安全标准的应用特别有利。</strong></p><h3>5 The Move Arena</h3><p>Move Arena 是一个先进的区块链基础设施，旨在与我们的内部服务套件无缝集成，并支持可互操作的 rollup 网络。该基础设施促进了一个动态生态系统的创建，使各种 rollup 能够高效运行并相互交互。它的设计旨在满足现代区块链应用程序的多样化需求，提供增强的互操作性、安全性和资源效率。</p><p>Move Arena 建立在几个核心组件之上，这些组件增强了其功能性和互操作性，如图 8 所示：</p><ul><li><strong>Move Stack Chains</strong>：用于部署和管理应用程序特定 rollup 的框架。</li><li><strong>DSS（去中心化共享排序器网络）</strong>：确保跨 rollup 互操作性的无缝衔接，并增强网络安全性。</li><li><strong>验证者网络</strong>：基于权益证明（PoS）的认证系统，为快速最终性结算提供保障，确保强大的经济安全性（参见第 4 节）。</li><li><strong>多资产质押</strong>：允许质押者使用多种资产进行质押，提高灵活性和经济安全性。</li></ul><p>在接下来的章节中，我们将深入探讨 Move Stack Chains、DSS 和验证者网络的概念。</p><h3>5.1 Move Stack Chains：应用程序特定链的网络</h3><p>应用程序特定链正在成为区块链世界的标准。这主要是因为 DeFi、游戏或供应链应用程序对延迟和吞吐量有不同的要求。隐私或专有要求可能还需要将某个链及其 dApp 与其他链隔离。因此，应用程序特定链正在 Avalanche、Cosmos 和 Polkadot 等 L1 网络中大量涌现。</p><p>我们可以利用我们架构的模块化特性（第 3 节）来满足特定需求，同时提供跨链互操作性和共享流动性。这是通过创建一个称为 Move Stack Chains 的 Move Rollups 网络，并将该网络集成到我们新型平台 Move Arena 中实现的（图 8）。通过共享相同的模块化架构，Move Stack Chains 中的链具有更强的互操作性，可以共享相同的桥接和数据可用性层，并且可以从 Move Arena 提供的快速结算中受益。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/0*ryDhJVKpWP73bCE5.jpg" /></figure><p><em>图8. Move Arena：为 Move Stack Chains 提供服务的独特区块链基础设施 — 一个可互操作的 Move Rollups 网络</em></p><p>这种设计选择与其他 L2 生态系统保持一致，包括 Optimism Superchain、Arbitrum Orbit、Polygon Supernets、zkSync Elastic Chain 或 Starknet appchains（第 3 层）。</p><blockquote><em>Move Arena 提供了一种经济高效且安全的方式来部署新的应用程序特定 Move Rollups。此外，作为 Move Stack Chains（rollup 网络）的一部分，这些链配备了跨链互操作性，以及它们之间的共享流动性。</em></blockquote><p>在接下来的部分中，我们将概述 Move Arena 的关键特性。我们将讨论 DSS（第 5.2 节）这一创新的共享排序器解决方案，以及多重质押概念（第 5.3 节），这些都增强了我们网络的安全性和经济效率。</p><h3>5.2 DSS：去中心化共享排序器</h3><p>DSS 作为 Move Arena 的去中心化共享排序器，与大多数 rollups 中常用的中心化排序器有所不同。这种去中心化设计通过消除单点故障来增强网络健壮性，促进交易排序的公平性和抗审查能力，并允许无许可参与[9]。</p><p>为了在交易排序上达成共识，我们采用了高度可扩展、高性能的拜占庭容错（BFT）协议。</p><p>由于中心化的特性，中心化排序器可能比去中心化排序器提供更快的预确认。然而，DSS 通过构建高度可扩展的 BFT 共识机制和高效的内存池机制，可以提供仅略微增加时间的快速预确认，并且具有基于经济保障而非信任的额外优势。在吞吐量方面，中心化排序器可能具有更少的吞吐量限制，但现代 BFT 协议已经取得了重大进展，能够实现远超需求的吞吐量水平。最后，用户可能更看重互操作性特性而非延迟问题。</p><p>DSS 的一个显著特征是其跨所有 Move Rollups 的共享架构。这种共享排序器方法对于实现 Move Arena 生态系统内的无缝互操作性至关重要。通过使用共同的排序层，DSS 促进了 Move Rollups 之间的跨链原子交换和流动性池化，显著提高了网络的整体安全性、功能性和效率。</p><p>排序器负责将交易数据发布到每个 rollup 选择的 DA 服务。为了减轻数据隐藏攻击，我们对不合规的排序器实施惩罚机制。虽然 DSS 管理交易排序共识，但由 MoveVM 驱动的 Move 执行器负责处理交易执行。这种关注点分离优化了网络效率和安全性，为未来的创新（如隐私增强或选择性审查功能）奠定了基础。</p><p>与其他共享排序器解决方案不同，我们对 DSS 和 Move Rollup 框架的管理允许更深层次的集成和优化。</p><blockquote><em>我们的共享基础设施方法不仅减轻了单个 rollup 的基础设施负担，还创建了一个统一的生态系统，使资产和流动性能够在 Move Rollups 之间自由流动，提升了整体用户体验和网络效用。最终结果是一个高度可互操作和可扩展的 L2 解决方案，结合了 MoveVM 的优势。</em></blockquote><h3>5.3 多资产质押</h3><p>我们的 DSS 去中心化共享排序器使用权益证明（PoS）机制。快速最终性结算也使用 PoS 来激励验证者在验证新区块时保持诚实。PoS 在以太坊等生态系统中已经证明其有效性，要求候选人质押原生代币，以展示承诺并增强抵御攻击的能力。单一资产质押要求质押者使用固定的加密货币进行质押，这意味着如果他们没有持有质押协议中使用的代币，可能需要在质押前进行资产交换。这对质押者来说可能是一个障碍。这就是为什么我们将启用多资产质押，这是一种允许质押者使用多种资产进行质押并获得奖励的 PoS 机制（图 9，图片来自 Freepik 的 myriammir）。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/0*prFS5-QTfD40JGxA.jpg" /></figure><p><em>图 9. 多资产质押</em></p><blockquote><em>这就是为什么我们将启用多资产质押，它是一种允许质押者使用多种资产进行质押并获得奖励的 PoS。</em></blockquote><p>多资产质押对质押者来说很方便，但对网络运营者来说也带来一些挑战：</p><ul><li>质押池由多种资产组成，这些资产的价格可能会波动</li><li>PoS 协议通常依赖于总质押量的 2/3 超级多数来完成决策（在排序器中的排序，通过快速最终性结算确认新区块）</li><li>由于前两点，一些质押者可能获得不合理的权力，少数质押者可能控制 2/3 的超级多数，这会对加密安全性产生负面影响</li></ul><p>解决这个问题的一个方案是使用（质押）池代币。质押者质押任意资产并获得池代币。当新的质押者质押（或解除质押）一些资产时，可以铸造（或销毁）池代币，并且需要应用一些再平衡策略[6]和流动性曲线选择来管理质押池。</p><p>实施保护我们质押者的安全策略（例如防止无常损失）是一个活跃的研究课题。</p><p>我们多重质押方法中的一个关键特性是无需运行节点就能进行质押的能力。这种称为委托的机制最大化了质押价值的数量，因此大大提升了经济安全性。</p><h3>参考资料</h3><ol><li>0L: 0l network. <a href="https://0l.network/">https://0l.network/</a>, accessed: 2024–01–12</li><li>Aptos: <a href="https://aptosfoundation.org/">https://aptosfoundation.org/</a>, accessed: 2024–01–12</li><li>Blackshear, S., Cheng, E., Dill, D.L., Gao, V., Maurer, B., Nowacki, T., Pott, A., Qadeer, S., Rain, D.R., Sezer, S., et al.: Move: A language with programmable resources. Libra Assoc p. 1 (2019)</li><li>Blackshear, S., Chursin, A., Danezis, G., Kichidis, A., Kokoris-Kogias, L., Li, X., Logan, M., Menon, A., Nowacki, T., Sonnino, A., Williams, B., Zhang, L.: Sui lutris: A blockchain combining broadcast and consensus (2023)</li><li>Buterin, V., et al.: A next-generation smart contract and decentralized application platform. white paper 3(37), 2–1 (2014)</li><li>Forgy, E., Lau, L.: A family of multi-asset automated market makers (2022), <a href="https://arxiv.org/abs/2111.08115">https://arxiv.org/abs/2111.08115</a></li><li>Ivanov, N., Li, C., Sun, Z., Cao, Z., Luo, X., Yan, Q.: Security threat mitigation for smart contracts: A survey. arXiv preprint arXiv:2302.07347 (2023)</li><li>Liu, C., Liu, H., Cao, Z., Chen, Z., Chen, B., Roscoe, B.: Reguard: finding reentrancy bugs in smart contracts. In: Proceedings of the 40th International Conference on Software Engineering: Companion Proceeedings. pp. 65–68 (2018)</li><li>Motepalli, S., Freitas, L., Livshits, B.: Sok: Decentralized sequencers for rollups. arXiv preprint arXiv:2310.03616 (2023)</li><li>Motepalli, S., Jacobsen, H.A.: Decentralizing permissioned blockchain with delay towers. arXiv preprint arXiv:2203.09714 (2022)</li><li>Nakamoto, S.: Bitcoin: A peer-to-peer electronic cash system. Cryptography Mailing List (2008)</li><li>Ogundeji, O.: Vitalik buterin sets milestones on ethereum’s route to be the ‘world computer’. <a href="https://cointelegraph.com/news/vitalik-buterin-sets-milestones-on-ethereums-route-to-be-the-world-computer">https://cointelegraph.com/news/vitalik-buterin-sets-milestones-on-ethereums-route-to-be-the-world-computer</a> (2016), accessed: 2024–01–11</li><li>Sui: <a href="https://sui.io/">https://sui.io/</a>, accessed: 2024–01–12</li><li>Ye, Z., Misra, U., Song, D.: Specular: Towards Trust-minimized Blockchain Execution Scalability with EVM-native Fraud Proofs. CoRR abs/2212.05219 (2022), <a href="https://doi.org/10.48550/arXiv.2212.05219">https://doi.org/10.48550/arXiv.2212.05219</a></li></ol><h3>译者：为什么 Movement？</h3><ul><li><strong>MoveVM 成为 L2 是必然趋势</strong></li></ul><p>MoveVM 在 Programming Language 层面具备优越性，但TVL（总锁定价值）不足是 Move L1 的难点与卡点。因此，Move as L2 的方案是未来的必然趋势。</p><ul><li><strong>降低开发者的心智成本</strong></li></ul><p>对于新链来说，到底要新发明一种语言/框架，还是使用已有的成熟语言/框架，这是一个问题。使用已有的被开发者熟悉的语言与框架，对于开发者更加友好。Movement 选择与 Aptos 完全兼容是明智的。</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6906858895c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dimension Life — 归集所有链上的碎片信息]]></title>
            <link>https://medium.com/@root_mud/dimension-life-%E5%BD%92%E9%9B%86%E6%89%80%E6%9C%89%E9%93%BE%E4%B8%8A%E7%9A%84%E7%A2%8E%E7%89%87%E4%BF%A1%E6%81%AF-930aa03be1b7?source=rss-ee35a88e63af------2</link>
            <guid isPermaLink="false">https://medium.com/p/930aa03be1b7</guid>
            <category><![CDATA[arweave]]></category>
            <category><![CDATA[arweave-ao]]></category>
            <dc:creator><![CDATA[rootMUD]]></dc:creator>
            <pubDate>Fri, 11 Oct 2024 02:50:40 GMT</pubDate>
            <atom:updated>2024-10-11T02:54:20.315Z</atom:updated>
            <content:encoded><![CDATA[<h3>Dimension Life — 归集所有链上的碎片信息</h3><p><a href="https://dimensionlife.rootmud.xyz/">https://dimensionlife.rootmud.xyz</a></p><pre>+------------------------+    +---------+<br>| Activites on BTC Chain | -&gt; | Process | ----+<br>+------------------------+    +---------+     |<br>                                              |        +-----------------------+<br>+------------------------+    +---------+     |        | dimensionLife Process |--+<br>| Activites on EVM Chain | -&gt; | Process | ----+        +-----------------------+  |-- Full Chain Behavior <br>+------------------------+    +---------+     |        +-----------------------+  |<br>                                              |--------| Achievements Process  |--+<br>+-------------------------+   +---------+     |        +-----------------------+<br>| Activites on Move Chain |-&gt; | Process | ----+<br>+-------------------------+   +---------+     |<br>                                              |<br>+------------------------+                    |<br>| Activites on AO Native |--------------------+<br>+------------------------+</pre><p>DimensionLife 的愿景是归集用户所有的链上信息。</p><p>Web3 世界长期处于「春秋战国时代」。各种具备差异性的链在各自发展，包括 EVM-based Chains、BTC-based Chains、Move-based Chains、AO 以及其他等等。</p><p>然而，从用户角度来说，一个「多链玩家」在与 dApp 交互的过程中势必产生很多<strong>「链上碎片信息」</strong>。</p><p>dimension Life 意图成为基于 Arweave 和 AO 的「Web3 存档器」，目前从「链上游戏」作为开端，在未来将会扩大到 Web2/Web3 在内的更多领域。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/0*ptnUKAz46w_CwHtk.png" /></figure><pre>+--------+    +---------+   Data  +----------------+<br>| A Game | -&gt; | Process | -------&gt;| Dimension Life |<br>+--------+    +---------+         +----------------+</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=930aa03be1b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Follow Verification]]></title>
            <link>https://medium.com/@root_mud/follow-verification-c34acb8f64c1?source=rss-ee35a88e63af------2</link>
            <guid isPermaLink="false">https://medium.com/p/c34acb8f64c1</guid>
            <category><![CDATA[rss3]]></category>
            <category><![CDATA[rss-feeds]]></category>
            <category><![CDATA[rss]]></category>
            <dc:creator><![CDATA[rootMUD]]></dc:creator>
            <pubDate>Sun, 15 Sep 2024 14:36:34 GMT</pubDate>
            <atom:updated>2024-09-15T14:36:34.190Z</atom:updated>
            <content:encoded><![CDATA[<p>This message is used to verify that this feed (feedId:58151136709735424) belongs to me (userId:55822446012235776). Join me in enjoying the next generation information browser <a href="https://follow.is/">https://follow.is</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c34acb8f64c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[重建 RSS]]></title>
            <link>https://medium.com/@root_mud/%E9%87%8D%E5%BB%BA-rss-169bc8ba8326?source=rss-ee35a88e63af------2</link>
            <guid isPermaLink="false">https://medium.com/p/169bc8ba8326</guid>
            <category><![CDATA[rss]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[rootMUD]]></dc:creator>
            <pubDate>Sun, 15 Sep 2024 14:28:47 GMT</pubDate>
            <atom:updated>2024-09-15T14:28:47.142Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>💡在 Web3 中可以 Rebuidl 的 4 Stuff：Blog、RSS、MUD 与 BBS</em></blockquote><blockquote><em>RSS 是一种网络提要[3]，它允许用户和应用程序以「标准化的计算机可读格式」访问网站更新。订阅 RSS 提要可以让用户在单个新闻聚合器中跟踪许多不同的网站，该聚合器会不断监视网站的新内容，而无需用户手动检查它们。RSS 阅读器可以内置在浏览器中、安装在台式计算机上或安装在移动设备上。</em></blockquote><blockquote><em>— — Wikipedia 机翻</em></blockquote><p>RSS 起源于互联网时代的早期，那时候还没有如现在这样的 App 巨鲸（Facebook、Twitter、Google、腾讯、抖音……），大家使用 RSS 「抓取」自己喜欢的源。</p><p>随着互联网的发展，各种 App 巨鲸崛起，我们只要注册一个账号，App 巨鲸就会喂给我们资讯。我们无需再去自己订制源。App 巨鲸会基于我们的浏览喜好进行「持续推送」…… 所以，RSS 渐渐的被历史淘汰了。</p><p>这无疑是一个必然的过程。</p><p>然而，有些有趣的问题值得我们去思考。这个必然的过程是「对」的吗？RSS 还有可能复兴吗？如果复兴，那么新一代的 RSS 会是怎样的？</p><h3>0x01 「顺应人性」的和「对的」</h3><p>很多时候，我们会相信「物竞天择，适者生存」，因此，活下来的就天然正确。</p><p>然而，这个粗暴的判断是有问题的，很多时候，活下来的是「顺应了人性」，而不是「对的」。</p><p>例如，如果我们认为「健康的食物=对，不健康的食物=错」。美式快餐在世界上活得非常好的原因不是因为它对，而是因为它顺应了人性。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*vsRtZYq7C-M0JyId.jpg" /></figure><p>同理，为什么是「基于推荐算法的 App」活得很好，然而 RSS 却没落了呢？</p><p>我认为是因为 — —</p><p>基于推荐算法的 App 顺应了人性，但这并不说明其正确。</p><p>老话说「忠言逆耳」，说好听的话是顺应人性的，会得到人们天然的喜爱。</p><p>同样，根据你现在已有的喜好去推荐内容是顺应人性的，也会得到人们天然的喜爱。</p><p>然而，就如同沉迷于美式快餐会让我们的身体越来越不健康一样，陷入推荐算法也会影响到我们的「精神健康」。</p><p>我们可以绘制一个简单的模型去描述它。</p><p>假设初始状态下我在 App（如抖音）中表现出了「喜好 A」和「喜好 B」，之后 App会不断给我推荐「喜好 A」和「喜好 B」的内容，从而加强我对「喜好 A」和「喜好 B」的偏爱，然后不断循环……</p><p>用户陷入其已有喜好之中，自然是符合 App 利益的 — — 因为用户有了黏性。</p><p><strong>但这真的符合用户的利益吗？</strong></p><p>我有一段时间沉迷于「肥皂剧」，所以我的 Timeline 上是肥皂剧。然后突然有一天我「断舍离」了。我想跟肥皂剧一刀两断，但是 App 依然会根据我的喜好来推送肥皂剧。</p><p>这是推荐算法的本质 — — <strong>「不断加强你的已有喜好，创造你对已有喜好的黏性，进而成为对 App 的黏性」</strong>。</p><p>我们可以看到，这种本质在精神层面是封闭的，不开放的。在「推荐算法」的系统下经历漫长的时间，我们最终会走向一个状态 — — 我们不再增减喜好，而是已有的喜好不断增强。</p><p><strong>「即使链接互联网，我们依然会成为一个又一个封闭的系统」。</strong></p><p>反之是 RSS。RSS绝对是反人性的，需要自己去搞一个个的订阅源，然后还要自行手动管理 — — 就跟我们在家去做复杂的中餐似的。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/0*3W-Hb-UpFQ_GDNSj.jpg" /></figure><p>然而，这种牺牲换来的是一个开放的、令人舒适的信息系统！</p><p>如上图所示，基于 RSS 的系统中，我们有喜好 A 和喜好 B，我们可以自由地去控制各种喜好的「流量」，比方说「喜好 A」相关信息每天推送 100 条，「喜好 B」每天推送 50条。也可以自由地「断舍离」 — — 我原来喜欢「钓鱼」，订阅了很多「钓鱼」相关的源，现在我不喜欢了，Ok，把所有的相关「源」Cut 掉！</p><p>TimeLine 瞬间清净。</p><p>因此，这个系统是<strong>「开放的」</strong>，使用这个系统的人也必将具备<strong>「高度的开放」</strong>。</p><p>开放才是互联网的本质精神。</p><h3>0x02 RSS 有可能复兴吗？</h3><p>RSS 复兴的道路可能是曲折的，但是长期来看 RSS 会重新获得更大的市场。</p><p>但是这需要一个关键因素，那就是有「激励因素」能冲抵使用 RSS 带来的「麻烦成本」，这个激励因素要看具体的设计了。我们可以将激励因素划分为「经济激励」与「非经济激励」。</p><ul><li><strong>经济激励</strong></li></ul><p>提供优秀 RSS 源能获得经济激励，这个 RSS 源可能是由提供者创作的，也可以是由提供者整合的。</p><ul><li><strong>非经济激励</strong></li></ul><p>例如 Crypto 世界中的声望等。</p><h3>0x03 Base on Blockchain/Web3 的 RSS 是怎样的？</h3><p>以下纯属个人YY。</p><h3>3.1 重新定义博客</h3><p>个人博客指的是不依赖任何博客平台的，自己搭建的拥有自己域名的博客。</p><p>虽然个人博客在国内已然式微（仅有部分大佬还正常运维着博客），但是从全球的角度来说，依然存在不少的个人博主。</p><p>在 Crypto 世界，我们可以重新定义博客，而博客理应是 RSS 重要的信息来源。因此，在 RSS 复兴之前，我们似乎应该先讨论「博客复兴」？但是这又是另一个主题了。</p><p>在这里就简单地列举 Crypto 博客可能的玩法：</p><ul><li>可以看到博主的 Crypto 身份</li><li>可以聚合博主的 NFTs &amp; Credentials</li><li>可以聚合博主的多个 Web3 dApp 内容，如Bodhi</li><li>如果是技术博主，可以显示博主参与的 Web3 项目</li><li>最后当然是博主可以提供 RSS 订阅源啦</li></ul><h3>3.2 可穿透的收益与可追溯的再创作</h3><p>这个是和 Web2 的 RSS 系统不一样的地方。因为基于 Blockchain，所以新一代 RSS 从技术上可以做到「收益可穿透」与「再次创作可追溯」。</p><p>也就是通过智能合约的方式让 RSS 源的创造者与传播者、让原创作品和再次创作作品均能获得收益，从而让新一代 RSS 真的承载住「有形价值」，从而可以抵消使用 RSS 带来的「麻烦成本」。</p><blockquote><em>不过区块链赋能创作者这个命题提了好多年了，</em><strong><em>现在也没看到一个特别成功的产品出来。</em></strong><em>这是否是因为之前的产品不是从「RSS 复兴」这个角度来设计的呢？这个就需要进一步的思考与探讨了。</em></blockquote><blockquote><em>— — 2021 年本文第一版</em></blockquote><blockquote><em>— — </em><a href="https://mp.weixin.qq.com/s/Md7PT4sPecPd-HCIXIV2_A"><em>https://mp.weixin.qq.com/s/Md7PT4sPecPd-HCIXIV2_A</em></a></blockquote><p>值得高兴的是，和 2021 年第一版发表时相比，我们似乎看到了一些希望 — —</p><ul><li>Bodhi 协议 实现了内容代币化</li><li>Follow正在打造 The Next Gen of RSS</li><li>AI 让我们能更方便的制作自己的 RSS Feed 了</li><li>……</li></ul><p>接下来会怎么样呢？需要继续跟踪👀。</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=169bc8ba8326" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Productize handbook in 24 hours | Indiehacker Case 0x01]]></title>
            <link>https://medium.com/@root_mud/productize-handbook-in-24-hours-indiehacker-case-0x01-e5211e7245ee?source=rss-ee35a88e63af------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5211e7245ee</guid>
            <category><![CDATA[indiehackers]]></category>
            <dc:creator><![CDATA[rootMUD]]></dc:creator>
            <pubDate>Sat, 07 Sep 2024 13:26:13 GMT</pubDate>
            <atom:updated>2024-09-07T13:27:21.675Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*WSo1K77EXQOJEypd.png" /></figure><p>View online:</p><blockquote><a href="https://indiehacker.rootmud.xyz/"><em>https://indiehacker.rootmud.xyz/</em></a></blockquote><p>Source code address: Your own project and time</p><blockquote><a href="https://github.com/NonceGeek/indiehacker-handbook"><em>https://github.com/NonceGeek/indiehacker-handbook</em></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/989/1*YPpz3hoMMBkS6aBvUxOEDQ.png" /></figure><h3>1 Core Thinking</h3><h4>1.1 Have your own long-selling book</h4><p>The underlying basis of this project and core values comes from “doing things that are effective in the long run”, which is a judgment made by using “metacognitive ability” in the manual.</p><p>In terms of specific matters, writing needs to write “long-selling books”, so that it is possible to capture unlimited “lifetime user value” as explained in 1.3.2 Your own project and time.</p><p>From this perspective, it is not cost-effective to write books on technical topics because of the effective timeliness. In contrast, the topics of “independent hackers” or “super individuals” will have long-term vitality.</p><h4>1.2 Productize a book?</h4><p>💡 Is it possible for us to productize a book?</p><p>This is an interesting proposition. In other words, what if a product revolves around a book?</p><pre>Components<br>+---------------+ +-- Reader DAO<br>| Book📚        |--+-- Notes<br>| Self          | |-- AI Agent<br>+---------------+ |-- Offline Activities<br>                  |-- Shop<br>                  |-- ...</pre><p>We regard this book as the core of a software. Traditional books are equivalent to non-extensible software. What if we upgrade it to a software that can install plug-ins?</p><p>Mind storm, you will find many possibilities: reader DAO, co-creation notes, AI Agent matching books, offline activities, online shopping malls…</p><p>Therefore, this attempt is equivalent to the prototype of “book productization”. In the future, perhaps more books or content can be tried to be productized?</p><h3>2 Time limit</h3><p>I set a time limit for this project, that is, the MVP version (minimum viable product) should be launched within 24h from the start of construction.</p><p>Why is there a time limit?</p><h4>2.1 Force to simplify functions</h4><p>The first reason is to force thinking about the simplification of functions by limiting the time.</p><ul><li>Which functions are necessary in the MVP version?</li><li>Which functions are not currently implemented?</li><li>Which functions can be used with the help of on-site products?</li></ul><p>Final thinking results:</p><ul><li>The overall framework uses Scaffold-ETH-2, which integrates a series of functions such as wallet login:</li></ul><blockquote><a href="https://scaffoldeth.io/"><em>https://scaffoldeth.io/</em></a></blockquote><ul><li>Reuse the code of bodhi-bbs tried before</li><li>Deno + Supabase are used in the backend, and only one table is used to store all notes📒</li><li>For the case section, Github Discussion is used directly, and no development is done by yourself</li><li>For early Shares, Bodhi is used directly</li><li>The core is to realize the display of Notes</li></ul><h4>2.2 Forced to optimize production costs</h4><p>The final production cost of Indiehacker is its own time, so the output time is controlled to 24h, that is, to see if the production cost can be controlled to the production cost corresponding to 24h.</p><p>2.2.1 AI</p><p>In the use of AI, compared with the previous combination of ChatGPT + Copilot, Cursor is added. The advantage is that it is more convenient and can be done directly in VSCode; the disadvantage is that the effect is not satisfactory. When modifying the function point, other places that do not need to be modified will be changed, and repeated debugging is required.</p><p>2.2.2 Trade-offs</p><p>During the productization process, two problems were encountered that could not be solved within 10–20 minutes, so they were converted into Issues:</p><blockquote><a href="https://github.com/NonceGeek/indiehacker-handbook/issues/"><em>https://github.com/NonceGeek/indiehacker-handbook/issues/</em></a></blockquote><p>Then seek help from DAO friends.</p><p><strong>Organization</strong> is an important software in the independent hacker startup operating system. Mastering this software will help us break through the productivity bottleneck faced by individuals.</p><h4>2.3 Foreshadows more possibilities</h4><p>The change in the product output time parameter foreshadows more possibilities.</p><p>For example, it proves that with the help of AI, it is more feasible for office workers to maintain Side Project on a daily basis. As long as there are weekends off, they can start their own Side Project entrepreneurial journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5211e7245ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Indiehacker Startup Operating System]]></title>
            <link>https://medium.com/@root_mud/indiehacker-startup-operating-system-b904447d359a?source=rss-ee35a88e63af------2</link>
            <guid isPermaLink="false">https://medium.com/p/b904447d359a</guid>
            <category><![CDATA[indiehackers]]></category>
            <dc:creator><![CDATA[rootMUD]]></dc:creator>
            <pubDate>Sun, 01 Sep 2024 13:47:50 GMT</pubDate>
            <atom:updated>2024-09-06T01:44:54.517Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*Q-umdznyo2dublp6.png" /></figure><blockquote>The app version of this book:</blockquote><p><strong>https://indiehacker.rootmud.xyz</strong></p><blockquote><em>NonceGeekDAO has more plans for the growth of indie hackers.</em></blockquote><blockquote><em>If you are interested in becoming an indie hacker, you can dm me on Twitter: </em><a href="https://x.com/0xleeduckgo"><em>https://x.com/0xleeduckgo</em></a><em>.</em></blockquote><h3>0x00 What is the indie hacker?</h3><p>“Indie Hacker” literally means “independent hacker”.</p><p>But in practical terms, it refers to a type of people who are independent, self-operated and develop their own online business to earn income. They “create products” and sell them to make profits.</p><p>They are both developers and entrepreneurs. They do not rely on large companies, but develop their own products through their own technical capabilities and business concepts to achieve an independent and free way of working.</p><blockquote><a href="https://indiehacker.one/#%E4%BB%80%E4%B9%88%E6%98%AF%E7%8B%AC%E7%AB%8B%E5%BC%80%E5%8F%91%E8%80%85"><em>https://indiehacker.one/#%E4%BB%80%E4%B9%88%E6%98%AF%E7%8B%AC%E7%AB%8B%E5%BC%80%E5%8F%91%E8%80%85</em></a></blockquote><pre>+-------+  +----------+  +-----------+  +--------+  +--------------------+<br>| Owner |  | Designer |  | Organizer |  | Seller |  | People Be Organized|<br>+-------+  +----------+  +-----------+  +--------+  +--------------------+<br>    |          |          |                  |          | <br>    +----------+----------+------------------+----------+<br>                          |<br>              +---------------------+  +------------------------+<br>              | Effective Producers |  | Ineffective Producers |<br>              +---------------------+  +------------------------+<br>                          |             |<br>                          +-------------+<br>                                  |<br>                           +-----------+  +---------------+<br>                           | Producers |  | Non-producers |<br>                           +-----------+  +---------------+<br>                                  |          |<br>                                  +----------+<br>                                        |<br>                                      +-------+<br>                                      | Crowd |<br>                                      +-------+</pre><blockquote><em>Production does not necessarily make money. Because the goods or services produced must be sellable, that is, they can meet social needs in order to make money. Otherwise, all the time and energy spent will be wasted. Therefore, production must be effective production.</em></blockquote><blockquote><em>— — The root cause of the hardship of life · The truth of wealth by Li Xiaolai</em></blockquote><p>Based on this picture to analyze indie hackers, then ideally indie hackers should be the owners, designers, organizers, sellers and organizers of effective production. Considering that making mistakes is inevitable in the real world, sometimes they will become ineffective producers.</p><blockquote><em>💡 Why is work, that is, the business model where a piece of time can only be sold once, so inefficient, but most people still work?</em></blockquote><blockquote><em>Because the biggest advantage of working is that workers can get benefits regardless of whether they are engaged in effective production. But its side effect is that it is difficult for workers to exercise the ability to “judge whether their production is effective”.</em></blockquote><h3>0x01 Why start a business from an indie hacker?</h3><p>In the past, when we talked about starting a business, we often thought of a startup team composed of experts in different roles, including CTO, CEO, etc., and then wrote a beautiful PPT to explain their ideas to investors to change the world, successfully raised funds and then reached the peak of life…</p><p>However, I think that for the current environment, starting from an indie hacker is a more feasible way to start a business. What is the reason?</p><h3>1.1 The fundamental premise of Startups: survival</h3><blockquote><em>A common mistake made by many Chinese entrepreneurs is that they rely too much on venture capital. There is nothing wrong with leveraging venture capital, but it is a misunderstanding to mistakenly believe that Startups must rely on investment and that investors have the obligation to raise their own companies to adulthood.</em></blockquote><blockquote><em>When entrepreneurs regard maintaining the survival of the company as someone else’s business, they lose their survival instinct. At one point, I didn’t take it seriously, but later I found that the consequences were disastrous — it’s like hoping that someone without a cerebellum will become an Olympic champion.</em></blockquote><blockquote><em>I believe some people will ask: How can an Internet company make a profit from the first day? But “not making money in the short term” and “completely ignoring the issue of making money” are completely different. If a company cannot make money and spend money according to its own will for a long time, it cannot control its own destiny. The vast majority of startups fail because they run out of money when the entrepreneurs are not prepared enough.</em></blockquote><blockquote><em>For entrepreneurs, it is not vulgar to talk about money at any time. On the contrary, the attitude towards money is one of the basic values ​​of an entrepreneur: Is the attitude towards spending investors’ money consistent with spending your own money? When it is not profitable, does the company spend lavishly? When the company has no money, can the entrepreneur lead the team through the difficult stage? Another question: Can an entrepreneur who is not good at managing funds in the early stage of Startups really build a big company? Can an entrepreneur who can’t make money really create massive wealth? — — As the “10,000 hours” theory of Wanyong Wanling shows, making money is a skill, and building a company with high returns and barriers is an advanced skill that requires long-term training. Buffett read through the investment-related books in the library when he was ten years old, which is a good example.</em></blockquote><blockquote><em>Although the business models are different, there are only two ways for startups to survive: they have the ability to make money, or their business grows fast enough for investors to continue to bet on it. The indicators for selecting the latter are quite clear: Is the number of users growing rapidly? Is the user retention rate high enough? Are the user acquisition costs and maintenance costs very low? Is the barrier established over time? If these points cannot be met, you need to find a way to be self-sufficient as soon as possible. Of course, there is also a special case where the founder has a strong financing ability. But don’t forget that there are very few entrepreneurs in the world who can repeatedly raise funds with loss-making businesses, so don’t take the initiative to classify yourself as one of them.</em></blockquote><blockquote><em>— — </em><a href="https://zhuanlan.zhihu.com/p/20047712"><em>https://zhuanlan.zhihu.com/p/20047712</em></a></blockquote><blockquote><em>— — </em><a href="https://zhuanlan.zhihu.com/p/19878922"><em>https://zhuanlan.zhihu.com/p/19878922</em></a></blockquote><blockquote><em>— — </em><a href="https://zhuanlan.zhihu.com/p/19973765"><em>https://zhuanlan.zhihu.com/p/19973765</em></a></blockquote><blockquote><em>— — by Zhang Liang</em></blockquote><p>The biggest reason is that the first prerequisite for starting a business is to survive. In entrepreneurial guidance, everyone always says that you need to find a market that meets “high frequency, rigid demand, and wide audience” and then start your entrepreneurial journey.</p><p>However, reality is not always as expected. Before finding a market that meets the conditions, or waiting for your market to meet the conditions, we always have to start when the conditions are not sufficient.</p><p>For example, we may face the reality that the number of users cannot achieve high-speed growth for a long period of time.</p><p>In this case, satisfying <strong>the ability to make money</strong> seems to be the only way to start a business.</p><h3>1.2 Analyze costs and benefits</h3><p>Okay, we have determined the fundamental premise of Startups that is universal for most people — <strong>survive when you are able to make money.</strong></p><p>Then let’s look at the costs and benefits of Startups. It’s very simple. If the benefits are greater than the costs, then you can survive; otherwise, not.</p><blockquote><em>💡The costs here include “money costs”, “time costs” and “mental costs”.</em></blockquote><blockquote><em>Wealth Index = One’s own production income/one’s own consumption expenditure</em></blockquote><blockquote><em>If a person’s wealth index = 1, then this person is neither poor nor rich; if the wealth index &lt; 1, then he is poor, and the smaller the wealth index, the poorer he is; if the wealth index &gt; 1, then he is rich, and the larger the wealth index, the richer he is. Very simple, very direct, and very clear.</em></blockquote><blockquote><em>— — Factors that react on production · The truth of wealth by Li Xiaolai</em></blockquote><p>There are only four situations for the costs and benefits of starting a business:</p><ul><li>Low cost, low benefits</li><li>Low cost, high benefits</li><li>High cost, low benefits</li><li>High cost, high benefits</li></ul><h4>1.2.1 High cost, low benefits</h4><p>This is the quadrant we must avoid falling into when starting a business. In this case, our wealth index will be far below 1.</p><h4>1.2.2 High cost, high benefits</h4><p>This model is much better than the previous one. In fact, the entrepreneurial goal of most startups is to achieve this model. However, the implicit risk of this model is that the factors affecting the benefits are very complex and may change suddenly; however, the cost flexibility is poor, and the cost control measures often cannot keep up with the changes in benefits, so it is easy to slide into the first model.</p><h4>1.2.3 Low cost, high benefits</h4><p>This model is a very ideal situation! But it is very difficult to achieve such a goal at the beginning, because a skill is always very clumsy at the beginning. However, we can try to make this one the “goal” of our Startups.</p><blockquote><em>💡Writing a long-term bestseller is a typical low-cost, high-return thing.</em></blockquote><h4>1.2.4 Low cost, low return</h4><p>This is not a “sexy” start, and it is very different from the blockbuster entrepreneurial story.</p><p>However, starting with clumsiness is often inevitable, and Startups is no exception.</p><blockquote><em>It’s almost always the same process: once you start </em><strong><em>trying</em></strong><em>, you will definitely encounter </em><strong><em>impossibility</em></strong><em> first, and you will encounter </em><strong><em>possibility</em></strong><em> only after </em><strong><em>repeated attempts</em></strong><em>, and you may encounter </em><strong><em>clumsiness</em></strong><em> immediately after that, and you may become </em><strong><em>proficient</em></strong><em> after a while, and then there may be a long </em><strong><em>stagnation</em></strong><em>, and you may only become </em><strong><em>proficient</em></strong><em> after a lot of deliberate practice…</em></blockquote><blockquote><em>Impossible ···&gt; Possible — → Clumsiness ···&gt; Proficiency — → Stagnation ···&gt; Proficiency</em></blockquote><blockquote><em>The most important and difficult part of this is, of course, the leap from </em><strong><em>impossibility</em></strong><em> to </em><strong><em>possibility</em></strong><em>, which is a breakthrough from 0 to 1.</em></blockquote><blockquote><em>— — </em><a href="https://1000h.org/self-training/03-trials-and-errors.html"><em>https://1000h.org/self-training/03-trials-and-errors.html</em></a><em> by Li Xiaolai</em></blockquote><p>Start with the “low cost, low benefit” model, then optimize our model in the process of “learning, practicing, using, and creating”, and finally transition to the “low cost, high benefit” model. This is a very feasible practical path.</p><blockquote><em>💡 What is “learning, practicing, using, and creating”?</em></blockquote><blockquote><em>The process of self-study actually needs to be broken down into the following four stages, although there are often some overlaps between them:</em></blockquote><ul><li>Learning</li><li>Practice</li><li>Use</li><li>Creating</li></ul><blockquote><em>As long as you can read, you can’t help reading; as long as you feel that there is something “worth learning”, you can’t help learning — in fact, everyone is learning all the time, but the choice of learning goals and the way and efficiency of learning are different.</em></blockquote><blockquote><em>Most people have never distinguished these stages, nor have they studied how to treat these stages respectively. This explains why so many people can’t help reading and learning, but never really master decent skills in their entire lives… Because they make mistakes in the first stage, give up in the second stage, skip the third stage directly, and always “make do”, as for the fourth stage, they never think about it…</em></blockquote><blockquote><em>— — </em><a href="https://github.com/selfteaching/the-craft-of-selfteaching/blob/master/markdown/Part.2.A.clumsy-and-patience.md#%E7%AC%A8%E6%8B%99%E4%B8%8E%E8%80%90%E5%BF%83"><em>https://github.com/selfteaching/the-craft-of-selfteaching/blob/master/markdown/Part.2.A.clumsy-and-patience.md#%E7%AC%A8%E6%8B%99%E4%B8%8E%E8%80%90%E5%BF%83</em></a></blockquote><blockquote><em>— — Clumsy and Patience · Self-study is a Craft</em></blockquote><h4>1.2.5 indie hackers are always in low-cost mode</h4><p>So, back to the topic — from the perspective of cost and benefit, why is it a highly recommended solution to start a business from an indie hacker?</p><p>The answer is: starting as an indie hacker can ensure that the cost is low, that is, to ensure that we are in the third or fourth mode.</p><p>In terms of time cost, it is enough to continuously build and maintain a Side Project on weekends — this is very friendly to indie hackers who still have a main job but want to start a business.</p><p>In terms of money cost, at least in the early stage, indie hackers take on all the roles in the project (see 0x00 section), as long as they cover the money they have invested in this matter, we call it the indie hacker Startups 1.0 stage.</p><p>Further, if the income can cover their living expenses, then they can start a business full-time — that is, they have entered the indie hacker Startups 2.0 stage.</p><h3>1.3 The key factor that cannot be ignored — time</h3><p>In Startups, “time” is very interesting because it can be called the <strong>least respected key factor</strong>. Many people believe that since capital can directly buy time, if I invest 10 times the amount of money, I can speed up my entrepreneurial progress 10 times.</p><p>However, I think that capital cannot directly buy time in at least two aspects.</p><h4>1.3.1 Ability polishing and time</h4><p>First is the polishing of entrepreneurial skills.</p><blockquote><em>Most people have the same problem. They are willing to spend money, and some are willing to spend time, but none of them are willing to pay attention — to be honest, they don’t know where to pay attention, regardless of whether they have enough attention.</em></blockquote><blockquote><em>Learning, </em><strong><em>learning</em></strong><em> and </em><strong><em>learning</em></strong><em>, </em><strong><em>studying</em></strong><em> and </em><strong><em>practicing</em></strong><em>, obviously </em><strong><em>practicing</em></strong><em> is more important. There is a very long distance between </em><strong><em>knowing</em></strong><em> and </em><strong><em>doing</em></strong><em> — the distance in time.</em></blockquote><blockquote><em>Learning a foreign language is a good example. I can write and tell you the pronunciation and key points of each English phoneme clearly, in detail and systematically, and I can repeat it to you… Then you can indeed say that you know it, but can you really do it? Can you do it well right away? It’s not that it’s not necessarily, but it’s definitely not possible at the beginning.</em></blockquote><blockquote><em>Learning without practice is useless. Practice will inevitably take up a lot of time.</em></blockquote><blockquote><em>And, you can only practice by yourself. When learning together, it may be more effective, but when practicing together, everyone will often be dragged down by the worst one. Moreover, everyone is different, everyone has different difficulties, everyone has different previous accumulation, and everyone practices in different ways… Therefore, in most cases, useful </em><strong><em>practice can only be personalized</em></strong><em>, and the more critical the point, the more so.</em></blockquote><blockquote><em>— — </em><a href="https://1000h.org/self-training/02-last-resort.html"><em>https://1000h.org/self-training/02-last-resort.html</em></a><em> by Li Xiaolai</em></blockquote><p>It is useless for all skills such as programming and cooking. Startups as a skill, from impossible to possible, from clumsy to skilled, from stagnant to proficient (see 1.2.4), all require <strong>inevitable time cost</strong>, and further speaking — — cost to carry out effective deliberate practice.</p><p>This is the <strong>commonality</strong> of entrepreneurial skills compared with other skills.</p><p>The characteristic of entrepreneurial skills is that Startups is a skill that <strong>combines multiple dimensions</strong>. Because we have to play multiple roles at the same time (see the 0x00 section), we have to be a CEO, a programmer, a salesperson, a product manager, etc. This was almost impossible before the intelligent era, but the revolutionary breakthrough of artificial intelligence has made us see the possibility — <strong>With the help of artificial intelligence, the cost of self-study has been greatly reduced. </strong>Therefore, it is no longer out of reach for a person to “quickly get started” with multiple different ability stacks.</p><p>However, this is still quite difficult. Therefore, Startups must start as early as possible, and through a long enough period of “learning, practicing, using, and making”, we can finally achieve “getting started” in becoming an indie hacker.</p><h4>1.3.2 Your own projects and time</h4><p>If we take time as a key factor in our own projects, how should we “screen” suitable projects? In other words, what projects are worth doing?</p><p>The answer is — <strong>Do projects that last as long as possible</strong>.</p><p>This simple standard is actually strict, and we can look at its opposite.</p><ul><li><strong>Chasing hot spots</strong></li></ul><p>Hot spots can generate profits for a period of time, but the project is likely to die directly after it is outdated. The lifetime value of a customer is very limited.</p><ul><li><strong>One-time projects</strong></li></ul><p>Commonly seen in projects done by Hackathon hunters and Bounty hunters. Similarly, such projects are also difficult to generate customer lifetime value.</p><p>Therefore, it is a good entrepreneurial habit to decide to do a project that lasts as long as possible from the beginning. We can continue to ask ourselves many questions on this basis:</p><ul><li>Will this project still make sense in 10 years?</li><li>Will I still want to continue this project in 10 years?</li><li>How to ensure that this project can survive for 10 years?</li><li>…</li></ul><p>Now looking back, <strong>Why do we use “longevity” as a key indicator to measure our own projects?</strong></p><p>There are two main reasons:</p><p><strong>1/ Short-lived projects have very limited customer lifetime value</strong></p><blockquote><em>Customer lifetime value refers to the profit you can make from a customer who purchases your products or services in his lifetime.</em></blockquote><blockquote><em>— — Business skills not taught in school · The truth of wealth by Li Xiaolai</em></blockquote><pre>↑User lifetime value<br>|-------------------------------+<br>|                               |<br>|                               |<br>|                               |<br>|                               | Number of users<br>+--------------------------------------- →</pre><p>The final profit is the area of ​​the above matrix diagram.</p><p>A long-lived project may achieve a continuous increase in the matrix area; but the matrix area of ​​a short-lived project is very limited.</p><p>The secret hidden here is that the growth of the number of users and the lifetime value of users is not always a linear relationship. A long-lived project has the opportunity to continuously optimize its “growth curve” and thus optimize the “growth area” of the matrix.</p><p><strong>2/ Only long-lived projects can cross the singularity of the “compound interest curve”</strong></p><blockquote><em>What is time? Time is not only a means of production. It also has another equally important definition:</em></blockquote><blockquote><em>Time is the only path to development.</em></blockquote><blockquote><em>So, just this one difference leads traders to play completely different games in the same arena. What speculators actually participate in is what I think is the worst type of finite game, called “zero-sum game”: the money earned is actually the money lost by others. Investors are different. If they succeed, they earn “the result of development”. What they participate in is actually an “infinite game”.</em></blockquote><blockquote><em>— — The fundamental difference between investment and speculation · The truth of wealth by Li Xiaolai</em></blockquote><p>The compound interest curve is the optimal form of the growth curve, which can be expressed in the formula:</p><blockquote><em>y = a(1+x)^t</em></blockquote><ul><li>y: final result</li><li>a: initial value</li><li>x: growth rate</li><li>t: time</li></ul><p>Expressed in a curve chart, it is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HghpOhPdeEn5kzTo.jpg" /></figure><p>Our expectation is that under continuous optimization, key indicators can follow the compound interest curve, such as total revenue and number of users.</p><blockquote><em>The confusing thing about the compound interest curve is that it is lower than linear growth for a considerable period of time.</em></blockquote><blockquote><em>— — Compound interest is a reasonable phenomenon · The truth of wealth</em></blockquote><p>Therefore, only long-lived projects can be proven to follow the compound interest curve.</p><p>One thing to note is that the characteristic of “longevity” is a necessary but not sufficient condition for the continuous growth of “customer lifetime value”, and it is also a necessary but not sufficient condition for growth to follow the “compound interest curve”. In other words, without this condition, the goal cannot be achieved, but with this condition, the goal may not be achieved.</p><h4>1.3.3 Outsourcing projects and time</h4><p>When becoming an indie hacker, you must be <strong>very cautious</strong> about outsourcing. Outsourcing for open source projects — you can consider it; outsourcing for closed source projects — try your best not to do it.</p><p>The reason is that when practicing independent hacking, we will hope to get rid of the business model of selling a piece of time only once and achieve a business model of selling a piece of time many times.</p><p>Therefore, it is natural to suffer from closed source outsourcing where the results are difficult to reuse.</p><h3>0x02 The most important ability</h3><blockquote><em>💡 What is the most important?</em></blockquote><blockquote><em>No matter what you learn, you should ask yourself this question repeatedly, yes, keep asking:</em></blockquote><blockquote><strong><em>What is the most important concept in this field?</em></strong></blockquote><blockquote><em>The most important concept in the field of “learning” is “</em><a href="http://mp.weixin.qq.com/s?__biz=MzAxNzI4MTMwMw==&amp;mid=401569526&amp;idx=1&amp;sn=54213794b520e0b35b49ae6a64399361&amp;scene=21#wechat_redirect"><em>self-study</em></a><em>”; the most important concept in the field of driving is “safety”; the most important concept in the subject of probability is “independence”; the most important concept in the subject of statistics is “sample validity”; the most important concept in the field of learning a foreign language is “use” ; The most important concept in the field of programming is “object”; the most important concept in the field of personal pursuit of financial freedom is “</em><a href="http://mp.weixin.qq.com/s?__biz=MzAxNzI4MTMwMw==&amp;mid=401199907&amp;idx=1&amp;sn=0d5395ca0f0737afefc72a48c7ecd278&amp;scene=21#wechat_redirect"><em>compound interest</em></a><em>”; in the field of life, whether it is making friends or falling in love, the most important concept is “sincerity”; the most important concept in the field of work is “initiative”…</em></blockquote><blockquote><em>When you first enter a field, there is always a period of time when you are in a state of “confusion”, which is normal; the methodology to get out of this state is to repeatedly ask yourself this question: “What is the most important concept?” — This is almost the most important learning methodology.</em></blockquote><blockquote><em>After finding the </em><strong><em>most important concept</em></strong><em>, you must do everything possible to build a sufficiently systematic </em><strong><em>methodology</em></strong><em> for this </em><strong><em>concept</em></strong><em>. — — </em><a href="http://xiaolai.co/books/xiaolai-xuexi/b70c02a57b8e6ad4fec72947e4f4c808.html"><em>http://xiaolai.co/books/xiaolai-xuexi/b70c02a57b8e6ad4fec72947e4f4c808.html</em></a></blockquote><p>As mentioned above, indie hacker Startups is a comprehensive skill that requires multi-dimensional abilities. Therefore, when getting started with this skill, the question of <strong>what is the most important</strong> becomes particularly important. The answer to this question determines whether we can start smoothly.</p><blockquote><em>What is the most important thing in getting started with the skill of indie hacker Startups?</em></blockquote><p>My answer is: metacognitive ability and meta-learning ability.</p><h3>2.1 Metacognitive ability</h3><p>Metacognition, that is, cognition about cognition.</p><blockquote><em>This is a very important concept because it almost determines whether a person has the opportunity to grow. The so-called metacognition refers to “cognition of cognition.” In other words, you can recognize your cognition, although it is a bit awkward, but it is not that difficult to understand. When you are thinking, you can realize that you are thinking, and further realize what you are thinking, and further judge whether your thinking method and thinking results are correct, and further correct your wrong thinking method or results. This is metacognitive ability.</em></blockquote><blockquote><em>— — </em><a href="http://xiaolai.co/books/3c76228cf822d6d30b14795b74b1481a/chapter2.html"><em>http://xiaolai.co/books/3c76228cf822d6d30b14795b74b1481a/chapter2.html</em></a></blockquote><p>In Startups, only with metacognitive ability can we realize what bugs there are in our thinking, and then optimize our “brain operating system”.</p><p>From the perspective of practical experience, this is very important. Because of multi-dimensional operation, we will be in a state of insufficient “mental resources” for a long time in Startups.</p><p>In fact, in the early stage of Startups, all resources are insufficient, but mental resources are particularly special.</p><p>I divide resources into two categories:</p><ul><li>Resources that can be replaced by other resources, such as labor resources, which we can buy with money.</li><li>Resources that cannot be replaced by other resources, the most typical one is mental resources. I can save mental resources by optimizing the way I consume my mental resources, but I cannot buy mental resources from others.</li></ul><p>It is easier to understand with a game analogy:</p><ul><li>The first resource is like a prop in the game, which can be exchanged for money or other props.</li><li>The second resource is like an energy bar, but there is no energy supplement in the game, and the most we can do is to optimize the way we consume energy.</li></ul><p>Therefore, continuously optimizing our brain operating system is equivalent to optimizing the “memory resources” occupied by each program at the bottom level, so that we have more “available resources”.</p><h3>2.2 Meta-learning ability</h3><p>If metacognitive ability is to optimize the programs that are already running in the brain, then “meta-learning ability” is aimed at the “loader” and “upgrade program” of each program.</p><p>Brain program startup steps:</p><pre>+--------------+      +-------------+      +----------------+<br>---&gt;| Load program | ---&gt; | Run program | ---&gt; | Upgrade program |<br>    +--------------+      +-------------+      +----------------+<br>    |     Quick    |      |   Practice  |          |<br>    |     start    |      |   process   |          |  Iterative upgrade<br>    +--------------+      +-------------+          |<br>                                   ↑---------------+</pre><p>In fact, the boundary between learning and practice in the real world is very vague. We often practice and learn at the same time, but in order to understand more clearly, it is helpful to split it into three “subroutines”.</p><p>Mastering meta-learning ability, that is, learning to quickly get started with any skill in the right way, is to save the cost of getting started with any skill and increase the probability of success.</p><h3>2.3 Quick start guide for meta-learning ability</h3><p>In this section, we will explain the most critical points of meta-learning ability in the most concise way.</p><blockquote><em>💡As mentioned above, when indie hackers are getting started with entrepreneurial skills, it is inevitable that they will not have enough mental resources, which means they will always appear “clumsy”. However, it is the need for mental resources that forces indie hackers to learn the ability to manage their mental resources in a meticulous manner. This ability is reflected in the writing of tutorials, that is, indie hackers will habitually write “the simplest and fastest introductory tutorials” — because redundancy is a waste of mental energy.</em></blockquote><h4>2.3.1 Minimum necessary knowledge</h4><blockquote><em>For any skill, there are some small but necessary knowledge points. As long as you learn them, you can start using that skill. Only by using it can you “accumulate mileage”, only by using it can you hone your skills, and only by using it can you change your life through </em><a href="http://mp.weixin.qq.com/s?__biz=MzAxNzI4MTMwMw==&amp;mid=401310327&amp;idx=1&amp;sn=a90987fcf7289d82666a2afa27f5df94&amp;scene=21#wechat_redirect"><em>practice</em></a><em>.</em></blockquote><blockquote><em>To learn any skill, you must find the </em><strong><em>“minimum necessary knowledge”</em></strong><em>.</em></blockquote><blockquote><em>— — </em><a href="http://xiaolai.co/books/xiaolai-xuexi/3b15b0238df8c521e4904914af7826e9.html"><em>http://xiaolai.co/books/xiaolai-xuexi/3b15b0238df8c521e4904914af7826e9.html</em></a></blockquote><p>The first key point of the minimum necessary knowledge is to think about what is the minimum necessary knowledge of the skill you want to learn? Start practicing immediately after mastering the minimum necessary knowledge.</p><h4>2.3.2 Learn to design teaching with gamification</h4><p>Teaching design is the most important part of skill learning. However, in the traditional model, we are used to entrusting the most important part to others — it is no different from entrusting our lives to others.</p><p>Design your own teaching!</p><ul><li>Learn how to design steps one by one to make the height of each step reasonable</li><li>Learn to design the reward mechanism in the process to ensure that the brain gets positive feedback</li><li>Learn how to “repeat correctly” to break through the threshold to “mastery” without being bored</li><li>Learn how to arrange the position of knowledge points so that too much “pre-knowledge” will not impact our confidence</li><li>Learn how to arrange learning and practice to avoid “practice too early” or “learning without practice”</li><li>Learn how to look at the overall situation to avoid missing “key points”</li><li>……</li></ul><p>In fact, after summarizing the above key points, it is the minimum necessary knowledge about “teaching” — that is, <strong>“gamification”</strong>.</p><p>A good thinking tool is:</p><blockquote><strong><em>Does my teaching design conform to the game design rules?</em></strong></blockquote><ul><li>Immediately attack the BOSS after killing a few monsters — not in line with</li><li>The interval between rewards is too long — not in line with</li><li>Only skill learning, no practical operation — not in line with</li><li>……</li></ul><h3>0x03 Sales</h3><p>In the second article, we emphasized that “metacognitive ability” and “meta-learning ability” are the top priorities for indie hacker entrepreneurial skills. If our brain is an operating system, then “metacognitive ability” is equivalent to the system’s built-in “supervisory program” and “upgrade program”, and “meta-learning ability” is equivalent to the “loader” and “upgrade program” when we install any software.</p><p>Then, what we are going to explain next is the program that our brain should load when learning the skill of indie hacker Startups.</p><p>At this time, we have to ask ourselves the classic question again:</p><blockquote><em>What is the most important?</em></blockquote><p>Although we will eventually install all the programs, the order of software installation is very important, because as explained in the first article, the fundamental premise of Startups is survival. The installed software must provide enough revenue to cover the cost to meet the need of “survival”, and then there will be cost to install the next software.</p><pre>+------------------------------+ Get the minimum necessary knowledge<br>| indie hacker Startups skills | ------------ Metacognition &amp; Meta-learning<br>+------------------------------+<br>           ↓ Time and money costs<br>Install the first software ---------------+<br>↑     Upgrade the first software          | Benefit &gt;= Existing cost + Installation cost of <br>--------←---------------------------------+  the next software<br>↓<br>Install the second software ---------------+<br>↑     Upgrade the second software          | Benefit &gt;= Existing cost + Installation cost of <br>...                                             the next software<br>↓<br>Quick start goal achieved, with indie hacker Startups skills system 1.0</pre><h3>3.1 The first software to be installed is sales</h3><p>Many indie hackers with technical backgrounds, because of inertial thinking, will think that “production” is the first software to be installed, and start to develop it, which is the reason why many programmers start their own businesses repeatedly “from entry to giving up”.</p><p><strong>Sales is the first software to be installed.</strong></p><h4>3.1.1 Avoid the trap of “ineffective production”</h4><p>Let’s review the picture mentioned in the first article:</p><pre>+-------+  +----------+  +-----------+  +--------+  +--------------------+<br>| Owner |  | Designer |  | Organizer |  | Seller |  | People Be Organized|<br>+-------+  +----------+  +-----------+  +--------+  +--------------------+<br>    |          |          |                  |          | <br>    +----------+----------+------------------+----------+<br>                          |<br>              +---------------------+  +------------------------+<br>              | Effective Producers |  | Ineffective Producers |<br>              +---------------------+  +------------------------+<br>                          |             |<br>                          +-------------+<br>                                  |<br>                           +-----------+  +---------------+<br>                           | Producers |  | Non-producers |<br>                           +-----------+  +---------------+<br>                                  |          |<br>                                  +----------+<br>                                        |<br>                                      +-------+<br>                                      | Crowd |<br>                                      +-------+</pre><blockquote><em>— — The root cause of hardship in life · The truth of wealth by Li Xiaolai</em></blockquote><p>The trap of starting from “designer” + “organizer”, that is, “producer” is that it is easy to fall into the range of “ineffective production” because the skill of “judging whether production is effective” has not been mastered.</p><p>On the contrary, as a seller, it is much easier to select “effectively produced” products for sale.</p><h4>3.1.2 Understanding “real needs” from sales</h4><blockquote><em>The benefits of being a salesperson <br>| — — — — Close enough to production<br>| — — — — Understand the real needs<br>| — — — — Understand the real competition<br>| — — — — Unlimited income<br>| — — — — No requirements for academic qualifications<br>| — — — — No pressure of bankruptcy</em></blockquote><blockquote><em>The benefit of being close to the needs is that compared with people in other jobs, you have more opportunities to see more needs and have more in-depth learning opportunities for a certain need. These are all knowledge, and they may become your own means of production in the future.</em></blockquote><blockquote><em>— — The truth about wealth in jobs that people don’t like to do by Li Xiaolai</em></blockquote><p>The second benefit is that starting from sales helps us understand the “real needs”, and understanding the real needs is a necessary but not sufficient condition for “effective production” — that is, effective production must be based on understanding the real needs; but understanding the real needs is only one of the many factors of “effective production”.</p><p>But, in any case, understanding the real needs is a good starting point for “effective production”.</p><h3>3.2 What is sales?</h3><p>Why do we ask this question?</p><p>Because in the general context, the sales we are talking about are sales in a narrow sense — that is, selling products to users explicitly as a main job or part-time job. If we understand it this way, we will feel that doing sales is always a matter of startup costs, and this idea will hinder us from upgrading our sales capabilities.</p><p>Let’s expand the definition of sales — explicitly or implicitly selling products to users as a main job or part-time job. In this way, we will find that sales are everywhere.</p><ul><li><strong>Finding a job:</strong> Treat yourself as a product to be sold, and sell it to employers in the human resources market;</li><li><strong>Sell articles:</strong> Treat articles as products to be sold, and sell them to the organizations to which they are submitted;</li><li><strong>Participating in hackathons:</strong> Treat coding and presentation behaviors as products to be sold, and sell them to sponsors</li><li>……</li></ul><p>Generalized sales helps <strong>“actively and deliberately practice”</strong> sales skills.</p><ul><li><strong>Proactive</strong></li></ul><p>Realizing that “implicit” sales are also sales, we will be more proactive in sales practice.</p><ul><li><strong>Deliberate</strong></li></ul><p>Realizing that “implicit” sales are also sales, we will deliberately incorporate them into the “sales” thinking framework when performing these actions.</p><blockquote><em>💡When sales is defined only in a narrow sense, “job hunting” and “sales” are two unrelated procedures. When we define sales in a broad sense, “job hunting”, “participating in hackathons” and other procedures are included in the ascending order of “sales”, and they can share the “underlying module” of the sales procedure.</em></blockquote><blockquote><em>Sales Process<br>+ — — — — — — — — — — — -+ + — — — — — — -+ + — — — — — — — — — — — — — — -+<br>| Selling General Goods | | Job Hunting | | Participating in Hackathons | …<br>+ — — — — — — — — — — — -+ + — — — — — — -+ + — — — — — — — — — — — — — — -+<br>+ — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — -+<br>| Bottom-Level Modules |<br>| Minimum Required Knowledge | Key Concepts | Key Information | … |<br>+ — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — -+</em></blockquote><h3>3.3 Quick Start Guide to Sales Ability</h3><h4>3.3.1 Minimum Required Knowledge</h4><p>What is the minimum required knowledge for sales ability?</p><p><strong>Pursue.</strong></p><p>Under the pursuit mindset, the core issue of sales is — How do we <strong>actively</strong> pursue users and close deals?</p><p>Under the pursuit mindset, the core issue of sales has changed — How do we let users <strong>actively</strong> pursue us and close deals?</p><p>The core question leads to corresponding sub-questions:</p><ul><li>How to “choose” a product that is good enough to make users “pursue” it?</li></ul><blockquote><em>💡This is another example of the result forcing action. If we just sell it without the restriction of pursuit/pursue, we don’t need the product to be good enough…</em></blockquote><ul><li>How to achieve user “pursue” at the “emotional” level?</li><li>How to achieve user “pursue” at the “rational” level?</li><li>……</li></ul><h4>3.3.2 Advanced</h4><blockquote><em>Make a good product, </em><a href="http://xiaolai.co/books/8327ac77840b8e66d8245eef28052099/make-a-product-that-has-a-soul.html"><em>make the product the best, most needed, and most loved</em></a><em>, is the most essential and powerful sales.</em></blockquote><blockquote><a href="http://xiaolai.co/books/8327ac77840b8e66d8245eef28052099/becoming-the-expert-of-your-own-users.html"><em>Becoming the expert of your own users</em></a><em> is the most powerful sales tool. I agree with these basic methodologies from the bottom of my heart.</em></blockquote><blockquote><a href="http://xiaolai.co/books/8327ac77840b8e66d8245eef28052099/the-founder-sells-everything.html"><em>http://xiaolai.co/books/8327ac77840b8e66d8245eef28052099/the-founder-sells-everything.html</em></a></blockquote><h3>3.4 References</h3><ul><li><a href="https://blog.daozhuixuetang.com/articles/career-daozhui-book.html">Job seekers, let employers chase you</a>:</li></ul><blockquote><a href="https://blog.daozhuixuetang.com/articles/career-daozhui-book.html"><em>https://blog.daozhuixuetang.com/articles/career-daozhui-book.html</em></a></blockquote><ul><li><a href="https://blog.daozhuixuetang.com/articles/sales-daozhui-ebook.html">Salesperson, let customers chase you</a>:</li></ul><blockquote><a href="https://blog.daozhuixuetang.com/articles/sales-daozhui-ebook.html"><em>https://blog.daozhuixuetang.com/articles/sales-daozhui-ebook.html</em></a></blockquote><ul><li><a href="https://blog.daozhuixuetang.com/articles/daozhui-love-book.html">Single women, let the male god chase you</a>:</li></ul><blockquote><a href="https://blog.daozhuixuetang.com/articles/daozhui-love-book.html"><em>https://blog.daozhuixuetang.com/articles/daozhui-love-book.html</em></a></blockquote><ul><li><a href="http://d4.daozhuixuetang.com/">Enterprise 4.0: Let customers chase you</a>:</li></ul><blockquote><a href="http://d4.daozhuixuetang.com/"><em>http://d4.daozhuixuetang.com/</em></a></blockquote><ul><li>My sales concept and methodology:</li></ul><blockquote><a href="http://xiaolai.co/books/xiaolai-xuexi/0206f8cfc50f13b8eb959e675b40c3ab.html"><em>http://xiaolai.co/books/xiaolai-xuexi/0206f8cfc50f13b8eb959e675b40c3ab.html</em></a></blockquote><ul><li>Sales must be done in person:</li></ul><blockquote><a href="http://xiaolai.co/books/8327ac77840b8e66d8245eef28052099/the-founder-sells-everything.html"><em>http://xiaolai.co/books/8327ac77840b8e66d8245eef28052099/the-founder-sells-everything.html</em></a></blockquote><h3>0x04 Production</h3><h3>4.1 Ensure the probability of effective production</h3><p>In the section “Learn to design teaching”, we mentioned that we should design a reasonable “positive feedback mechanism” for ourselves. When we are producing, we need to take this into consideration. Ineffective production is inevitable, and ineffective production brings inevitable “negative feedback” to players, and even discourages them from playing — think about how you would feel if you worked hard to pass a level in the game, but found an empty box!</p><p>Therefore, the first point when mentioning production is: <strong>How ​​can we ensure the probability of effective production, so that its value is enough for us to continue?</strong></p><blockquote>“Pick a small market and dominate it” — Peter Thiel</blockquote><blockquote><em>I have been thinking about the problem of matching products and user groups recently.</em></blockquote><blockquote><em>This is first due to Peter Thiel’s enlightening teaching: the core of the Internet is monopoly rather than competition, and startups should first find a niche market and monopolize it, and then gradually expand.</em></blockquote><blockquote><em>Secondly, if I think of Minecraft, a game that was developed by almost one person but has tens of millions of active users and sold $2.5 billion, if I have gained anything, it should be that the developer met the needs of a group of people to play Lego on the computer. Discovering and meeting this unmet need is 10,000 times more important than making exquisite products and promoting them crazily.</em></blockquote><blockquote><em>— — </em><a href="https://zhuanlan.zhihu.com/p/19878922"><em>https://zhuanlan.zhihu.com/p/19878922</em></a></blockquote><p>Here are two key points:</p><p><strong>1/ </strong>Persistently exercise <strong>“yourself”</strong> ability to judge effective production</p><p>We can divide all abilities into two categories: “abilities that do not need to be mastered personally” and “abilities that must be mastered personally”.</p><p>The former ability is like programming and cooking. You don’t necessarily need to learn programming to start a technology business, and you don’t necessarily need to learn how to cook to open a restaurant. You can hire the right people with money to complete it, or directly buy the fruits of others’ labor.</p><p>The latter, such as investment and sales, must be mastered by self-study, and you must spend enough time and effort on it to achieve proficiency.</p><p>The ability to “judge effective production” belongs to the latter. It and investment can both be classified under the category of “judgment and decision-making ability”. Therefore, like investment, “judgment of effective production” does not have the scale effect of human resources. The judgment made by a large team is not necessarily more accurate than that of a single individual.</p><p>Thank you for this! It is the existence of this type of ability that has given indie hackers a living space.</p><p>2/ Make small products that meet <strong>“single demand”</strong></p><p>Only meeting a single demand, this limiting condition allows us to better consider whether this demand is established.</p><ul><li>Satisfy the needs of community residents for eating skewers — a single demand, we can easily verify whether this demand is established;</li><li>Satisfy users’ needs for the metaverse — complex needs, difficult to verify whether it is established;</li><li>Satisfy users’ needs for their own chain releases — complex needs, difficult to verify whether it is established;</li><li>……</li></ul><p>Then, follow the design that each product only meets a single demand, treat each product as a mutually isolated life form, and make the overall ecology formed by the product group clearer:</p><ul><li>Each product has its own user group, and multiple user groups with different needs are not mixed together</li><li>Each product has its own life frequency, Let it crash</li><li>Each product has its community developers, and developers can be more focused</li><li>……</li></ul><p>In short, the ultimate goal of all designs is <strong>better insight into needs</strong>.</p><blockquote><em>Fall in love with your users.</em></blockquote><blockquote><em>— — Kevin Hale</em></blockquote><blockquote><em>— — </em><a href="https://leilux.github.io/lou/startup/YC%20startup%20CS183B/lesson7/readme.html"><em>https://leilux.github.io/lou/startup/YC%20startup%20CS183B/lesson7/readme.html</em></a></blockquote><h3>4.2 Controlling production costs</h3><p>To control production costs, the most important thing is naturally the “probability of ensuring effective production” mentioned in the previous section. Ineffective production is the abyss of cost consumption — the harder you work, the more serious the loss.</p><p>Costs can be specifically divided into “time cost”, “money cost” and “mental cost”. Sort by importance:</p><blockquote><em>Mental cost &gt; Time cost &gt; Money cost</em></blockquote><p>In other words, using money to replace time, using money to replace mental effort, and using time to replace mental effort are all cost-effective transactions.</p><p>I control production costs through the following factors: system design, AI, and organizational governance.</p><h4>4.2.1 System design</h4><p>Reasonable system design can optimize the production costs of all projects at a fundamental level, which is often overlooked by producers.</p><p>For example, as mentioned in the previous section, each single requirement corresponds to an independent product, which belongs to system design. Designing a complex Mono App will increase production costs, which is contrary to the refined operation of indie hackers.</p><p>In addition, there are some other tricks at the system design level:</p><ul><li><strong>Rationally choose programming language and technology stack</strong></li></ul><p>As programmers often say, programming language is not important when it comes to whether the product can be realized. However, programming language is an important and long-term factor affecting development costs. For example, if we choose Java as the development language of Web3 programs or choose Vue as the front-end development framework of Web3, we will continue to pay costs.</p><p>Therefore, indie hackers should carefully choose programming languages ​​and technology stacks. A good question is:</p><blockquote><em>Will this programming language or technology stack still be valuable in 10 years? (Maybe this programming language or technology stack itself will die, but if it has long-term value, then it will at least become the predecessor of a new star).</em></blockquote><ul><li><strong>Use more scaffolding</strong></li></ul><blockquote><em>Gentlemen are not born different, but </em>good at borrowing things<em>.</em></blockquote><blockquote><em>— — Encouragement to Study · Xunzi</em></blockquote><p>The second and third points actually talk about the same thing — learn to “borrow power” and save costs by borrowing power.</p><p>Using scaffolding allows developers to divert their energy from basic work and focus on core business code. In fact, when we intervene in an ecosystem, we will first check the scaffolding of this ecosystem. If there is no scaffolding, we will make one ourselves. From a long-term perspective, a continuously maintained scaffolding will reduce the cost of all related products.</p><blockquote><em>💡 A big secret when starting a business is that before reaching a certain stage, UI design is not important. The value of the product depends on how much you meet the needs of users rather than whether your design is unique. Therefore, using a universal UI with scaffolding is sufficient in the early stage.</em></blockquote><ul><li><strong>Cooperate with existing products</strong></li></ul><p>On the basis of consistency with your product logic, cooperating with existing products is a good choice. Not only does it reduce production costs, but it can also reduce sales costs by converting users of existing products.</p><p>When choosing cooperating products, the most important thing I value is whether the values ​​are consistent. If the values ​​cannot be agreed upon, temporary cooperation can be achieved at this stage, but in the long run, the two will take different “evolutionary paths”.</p><p>In addition, the ability of products to cooperate with each other is also a new feature brought to the computer field by the development of Web3. In the era of Web2, the life cycle of a product depends entirely on its creator. Therefore, there is a risk of the death of the cooperative product. But in Web3, once the contract is deployed, it cannot be changed, and there is no need to worry about various accidents.</p><pre>+--------+ +--------+<br>| dApp α | | dApp β | ...<br>+--------+ +--------+<br>+----------------------------------------------+<br>| Protocol based on Smart Contract - long live |<br>+----------------------------------------------+</pre><h4>4.2.2 AI</h4><p>The breakthrough progress of general artificial intelligence has greatly reduced two costs: “learning cost” and “production cost”. Therefore, any individual and organization should prepare their own “AI toolbox”.</p><h4>4.2.3 Organizational governance</h4><p>Organizational governance is an effective means of controlling production costs. However, from the perspective of indie hackers and traditional organizations, organizational governance is a completely different set of ideas. This is explained in the first edition of the NonceGeekDAO white paper in 2022:</p><blockquote><a href="https://www.noncegeek.com/#/whitepaper"><em>https://www.noncegeek.com/#/whitepaper</em></a></blockquote><p>This topic will be discussed in more detail in the next article “Organization”.</p><h3>4.3 Towards a better target</h3><p>In the first article. We mentioned that “high frequency, rigid demand, and wide audience” is an ideal entrepreneurial market, which is enough for suitable startups to grow rapidly.</p><p>But it is difficult to find such an ideal target in the initial stage of Startups. Therefore, the target we are in at the beginning always has some conditions that cannot be met, but the difference between benefits and costs allows us to survive.</p><p>It’s like playing a game — everyone knows that in a strategy game, you have to occupy the best resource territory, but the birthplace is often not a choice, and you can only survive with the existing resources of the birthplace.</p><p>Fortunately, we have the ability to migrate or expand. As long as we survive and keep evolving, we can always reach a better target.</p><p><strong>So, we first know what the ideal target of the product is — “high frequency, rigid demand, and wide audience”. Then continue to evolve, develop new products or upgrade old products, and eventually reach the ideal target, sooner or later.</strong></p><h3>4.4 The minimum necessary knowledge about production</h3><p>I think the minimum necessary knowledge about production is <strong>“insight into the user’s state”</strong> (demand is the result of the state).</p><p>In an intimate relationship, if you can “insight into the other person’s state” and achieve 100% in perception, then you don’t even need skills in other parts — all skills are to make up for the lack of perception.</p><p>Similarly, if you can “insight into the user’s state” and achieve 100% in perception, then even if the product implementation is rough, you can succeed. On the contrary, it will only be “finely crafted ineffective production”, making beautiful but unused products.</p><h3>0x05 Organization</h3><h3>5.1 Organization from the perspective of indie hackers</h3><p>In the “Production” article, we mentioned: “Effort cost &gt; Time cost &gt; Money cost”. Therefore, using money to buy time or effort is always a good deal. For indie hackers, <strong>organization is a group where members trade time with each other</strong>.</p><p>One-to-one time trading in an organization:</p><pre>+----------------------+    Resources     +---------------------+<br>| Organization members | -------------&gt;   | Organization members |<br>+----------------------+                  +----------------------+<br>|    Need time    | &lt;-------------        | Need money or        |<br>+-----------------+           Time        |other resources       | <br>| Result: Own time|                       +----------------------+         <br>+---------------------------------+<br>| Add your own time               |<br>| Means of production → Commodity |<br>+----------------------------------+<br>                      +---------&gt; Sell time at a higher value and in a better way (for example, one time is sold multiple times)</pre><p>One-to-many time trading in an organization:</p><pre>+-----------------+<br>| Organization    |<br>|      members    |<br>+-----------------+<br>| Need money or   |<br>| other resources |<br>+-----------------+<br>Resources ↑ ↓ Time<br>+-----------------+    Resources   +--------------------+<br>| Organization    |                |   Organization     |<br>| members         | -------------&gt; |     members        |<br>+-----------------+                +--------------------+<br>| Need  time      | &lt;------------- | Need money or other|                                                                     |                 | &lt;--------------|    resources       |       <br>+--------------------+             +--------------------+<br>| Add your own time  |<br>+---------------------------------+<br>| Means of production → Commodity |<br>+---------------------------------+<br>        +----&gt; Sell the integrated time at a higher value and in a better way (higher value after integration)</pre><h3>5.2 indie hackers’ needs for organizations</h3><p>From the perspective of demand, indie hackers always need time in batches, not the complete time of all time owners. Because the traditional employment system is not compatible with the needs of indie hackers, indie hackers should naturally use the Bounty system (that is, one-time purchase) to meet their needs for time and energy.</p><p>If indie hackers form relevant communities, the Bounty system will replace the traditional employment system as the basic time trading system, which is exactly what NonceGeekDAO has been practicing.</p><pre>match<br>Traditional company &lt;-------&gt; Employment system as the main system, Bounty system as the auxiliary system<br>            match<br>Community &lt;-------&gt; Bounty-based system as the main system, employment system as the auxiliary system<br>​</pre><p><strong>The biggest advantage of the bounty-based system is that the time of the buidlers is atomized.</strong></p><p>Under the traditional employment system, the buidlers’ time is sold in bulk, and the organization can only buy it on a monthly basis. From the perspective of the organization, the organization has purchased redundant time that it does not need; from the perspective of the buidlers, mixing “slacking time” and “effective time” and selling them together is actually wasting their own time. “Slacking time” could have been used to do more meaningful things in an open and aboveboard manner, which is a lose-lose situation.</p><p>Under the bounty system, buidlers atomize and distribute their time and the organization buys the output of atomic time. From the perspective of the buidlers, they have more atomic time to sell to more organizations in a diversified way; from the perspective of the organization, it can more flexibly combine the production results of the buidlers. For example, with the same cost of 20,000 yuan, an organization can only hire one mid-level front-end engineer under the traditional employment system; but using the Bounty system, it can issue 20 Bounties of 1,000 yuan, covering multiple aspects such as front-end, back-end, design, product and marketing.</p><h3>5.3 Organizational paradigm shift under Bounty Protocol</h3><p>As we explained in the “Top Priority Capabilities” section, continuing the analogy with computer systems, “the way to sell time” is equivalent to the underlying protocol of the “organizational operating system”. Companies and communities use two very different underlying protocols, and on top of this underlying protocol, we build very different “organizational operating systems”.</p><h4>5.3.1 Gamification — The minimum necessary knowledge about organizations</h4><p>We still use the concept of “minimum necessary knowledge” mentioned in the second article to think about this problem:</p><blockquote><strong><em>If an organization based on Bounty Protocol has a minimum necessary knowledge, what is it?</em></strong></blockquote><p>My answer is: <strong>“Gamification”</strong>.</p><p>This is consistent with the “Learning to Gamify Instructional Design” in the Meta-learning Quick Start Guide in the second article, because self-study and teaching are originally part of organizational governance.</p><p>We can use the same thinking tools to ask key questions:</p><blockquote><strong><em>Does the organizational system I designed conform to the rules of game design?</em></strong></blockquote><p>Compared to self-study, a “single-player game”, the organization is more like a “Table RPG”. If you are not familiar with this form, the next best metaphor is MMORPG (Massive Multiplayer Online Role-Playing Game). Therefore, it has greater complexity and means more diverse gameplay.</p><p>The following are some extended questions based on the key questions:</p><ul><li>How to design a minimalist guide for players so that new players can start as soon as possible? (Super Mario series is a model in this regard)</li><li>How to design the main quest?</li><li>How to design a dungeon?</li><li>How to design a reasonable team-building mechanism so that players can smoothly team up to play dungeons?</li><li>How to design a minimalist guide for DM (Dungeon Master) so that a group of high-quality DMs will appear in the organization?</li><li>How to attract willing incentive providers?</li><li>How to ensure the “online number” of the game while allowing people to come and go freely?</li><li>…</li></ul><p>Here are some articles related to NonceGeekDAO’s past organizational construction:</p><ul><li><a href="http://mp.weixin.qq.com/s?__biz=MzI0NTM0MzE5Mw==&amp;mid=2247486882&amp;idx=1&amp;sn=fcc51bb37ba087ffdb1b2d421b9cd5e3&amp;chksm=e94ebb14de393202cde7bb7964f31ea821006da183351c57964a002dbc4ed31d35a6fdcb20f1&amp;scene=21#wechat_redirect">DM Practice Manual (Part 1) | Let’s Talk About DAO 0x09</a></li><li><a href="http://mp.weixin.qq.com/s?__biz=MzI0NTM0MzE5Mw==&amp;mid=2247487611&amp;idx=1&amp;sn=2621572b7611e1cdc06853be73f556cf&amp;chksm=e94ea6cdde392fdb9f904faa3603a20dbef371ba67ac3b1434340888f583b5cf860fb3972454&amp;scene=21#wechat_redirect">DM Practice Manual (Part 2) | Let’s Talk About DAO 0x0D</a></li><li><a href="http://mp.weixin.qq.com/s?__biz=MzI0NTM0MzE5Mw==&amp;mid=2247484656&amp;idx=1&amp;sn=04087972d3b670a892e8a177740dfb87&amp;chksm=e94eb246de393b50b1d932059947eb7513c54dc3612d0f002346b799514b2f62d5eb5783baac&amp;scene=21#wechat_redirect">The essence of managers is game designers | Notes on the Training of New Developers (VI)</a></li></ul><h4>5.3.2 Permissionless</h4><p>GIt and Github are <strong>developed for decades and have been proven to be effective global asynchronous collaboration systems</strong>. Developer DAOs should be built on Git. system. Therefore, permissionless should be a necessary feature of the developer DAO and the key source of its vitality. Anyone can submit an issue to any open source project, and anyone can solve the issue and submit a PR (Pull Request). The Reviewer should merge it after verifying that the submission is valid. <strong>The entire process should be decoupled from the identity of the submitter.</strong></p><p>In fact, how to add an incentive layer to the existing Git/Github system and upgrade it to the Web3.0 version so that open source participants can get their due benefits is an important proposition that has not yet been solved, but it will be realized in the next 5-10 years.</p><h4>5.3.3 Globalization</h4><p>Traditional organizations are limited by geographical space, and they always employ workers in a limited geographical space. This approach has two disadvantages:</p><ul><li><strong>Regional risks:</strong> Both organizations and organizational members are affected by regional risks, including regional policy risks and regional economic risks. If we use computer terms, it is <strong>“single point failure risk”</strong>.</li><li><strong>Homogeneity risk:</strong> People in the same geographical space will have the same characteristics, leading to the “homogeneity risk” of the organization, limiting the possibilities of the organization. There are similar examples in computer systems: in blockchain design, we often use different programming languages ​​​​to implement nodes in order to prevent <strong>homogeneity risk</strong>.</li></ul><p>Therefore, DAO should go a step further on the basis of “no access” and consciously increase the globalization of its participants, that is, the degree of diversity.</p><h3>0x06 Continuously optimize the operating system — production factors and counter-production factors</h3><blockquote><em>Bayes’ theorem:</em></blockquote><blockquote><em>$$<br>P(A|B) = \frac{P(B|A) \cdot P(A)}{P(B)}<br>$$</em></blockquote><blockquote><em>To describe it as simply as possible in “</em><strong><em>natural language</em></strong><em>”, it is:</em></blockquote><blockquote><em>Bayesian reasoning is “the process of continuously using new evidence to adjust the parameters of the prediction model to improve the accuracy of the prediction”.</em></blockquote><blockquote><em>— — </em><a href="https://1000h.org/self-training/10-going-back.html"><em>https://1000h.org/self-training/10-going-back.html</em></a></blockquote><blockquote><em>— — Back to Basics · 1000 Hours</em></blockquote><p>Start as quickly as possible and build an “indie hacker startup operating system”. We can give it a version number v1.0.</p><p>The next thing to do is to continuously optimize the operating system and keep it upgraded while maintaining the normal operation of the 1.0 system functions.</p><p>In this process, the most basic principle is “Bayes’ theorem”. Through practice, we continue to optimize the key parameters of the operating system itself and its software, such as: the cost of acquiring new skills, the probability of successful sales, production quality…</p><p><strong>What are the key parameters?</strong></p><p>Here are my views — —</p><ul><li>Key parameters of meta-learning software: the cost of acquiring new skills</li><li>Key parameters of meta-cognitive software: the degree of self-awareness</li><li>Key parameters of sales software: the probability of successful sales</li><li>Key parameters of production software: effective production quality (effective production probability x effective production quality)</li><li>Key parameters of organizational software: effective production quality (effective production probability x effective production quality)</li></ul><p><strong>What is the most critical parameter?</strong></p><p>Further questioning, what is the most critical parameter of this operating system?</p><p>My answer is — — <strong>Effective production quality (effective production probability x effective production quality)</strong>.</p><p>After formulating the key parameters, we can further explore “production factors” and “counter-production factors”.</p><p>What are production factors? Production factors are factors that help improve key parameters.</p><p>What are counter-production factors? Counterproductive factors are factors that may cause key parameters to decline.</p><pre>↓ Add the monitor ↓<br>Sales | Production | Organization --- Key parameters --- Productive factors and counterproductive factors<br>+-------------------------+<br>| Metacognitive ability | Meta-learning ability | --- Key parameters --- Productive factors and counterproductive factors<br>+-------------------------+<br>| indie hacker startup operating system | --- Key parameters --- Productive factors and counterproductive factors<br>+-------------------------+</pre><p>Focusing on key indicators, production factors and counterproductive factors is equivalent to installing a monitor on our operating system, and this monitor itself is part of “metacognitive ability”.</p><p><strong>What are the key production factors?</strong></p><p>Here are my views — —</p><ul><li><strong>Key production factors of meta-learning software</strong></li><li>Effective concentration time</li><li>Autonomous learning ability</li><li>Historical success times</li><li><strong>Key production factors of meta-cognitive software</strong></li><li>Basic logic ability</li><li>Ability to apply first principles</li><li>Key production factors of sales software</li><li>Perception ability</li><li>Branching ability</li><li>Expression ability</li><li>Historical success times</li><li><strong>Key production factors of production software</strong></li><li>Demand judgment ability</li><li>Product realization ability</li><li>Historical success times</li><li><strong>Key production factors of organizational software</strong></li><li>Member growth curve</li><li>Organizational governance ability</li></ul><p>We can see that “historical success times” is a key production factor in multiple software, which is the mystery of “Bayes’ theorem”. Based on success and thinking about success, we have the opportunity to continuously upgrade our operating system and software.</p><p><strong>What is the most critical production factor?</strong></p><p>I think the most critical production factor is “autonomous learning ability”, which is the basis for obtaining and optimizing other production factors.</p><p><strong>What is the most critical counter-production factor?</strong></p><blockquote><em>Of course, the most anti-productive factor is the misunderstanding of money or wealth itself.</em></blockquote><blockquote><em>— — Factors that counteract production · The truth about wealth by Li Xiaolai</em></blockquote><h3>0x07 Summary and follow-up</h3><p>I became an indie hacker in 2019 and simultaneously established NonceGeekDAO, a developer DAO for indie hackers.</p><p>The first version of this manual was completed in September 2024. It is based on the thinking and summary of the experience of learning, practicing, using and creating the skill of “indie hacker Startups” for 5 years. Before the end of 2019, the main explorations were “metacognitive ability”, “meta-learning ability” and “production ability”. After the establishment of DAO in 2019, we began to gradually explore the ability of “organizational governance for indie hackers” and “sales ability”.</p><p>This manual attempts to explore the first principles of “indie hacker” Startups.</p><blockquote><em>💡 What is the first principle?</em></blockquote><blockquote><em>The first principle refers to returning to the most basic conditions of things, breaking them down into various elements for deconstruction analysis, and thus finding the best way to achieve the goal.</em></blockquote><p>The result is the “indie hacker Startup Operating System” described in 0x00-0x07. On this basis, we will update it based on actual cases, that is, continue to understand and upgrade this operating system through actual cases.</p><p>These cases will clearly state how we use one or more “software” in this operating system.</p><pre>+--→ Sales | Production | Organization<br>| +-------------------------------------+<br>| | Metacognitive |   Meta-learning     |<br>| |    ability    |      ability        |<br>| +-------------------------------------+      Practical case 0x01...<br>| |indiehacker startup operating system | =&gt; Practical case 0x02...<br>| +-------------------------------------+   Practical case 0x03...<br>| |        BIOS: First principles       |         ↑<br>| +-------------------------------------+         |<br>+----------------↑ ↑------------------------------+<br>Power supply Case-based system upgrade</pre><p>In addition, regarding “metacognitive ability”, “meta-learning ability” and “production ability”, I recommend the book that is still being written:</p><blockquote><a href="https://github.com/leeduckgo/the-craft-of-selfteaching/tree/feature/javascript"><em>Self-learning is a craft Javascript version</em></a></blockquote><p>On the one hand, the original Python version is the best book on self-study on the market;</p><p>On the other hand, from Javascript Getting started with programming will help indie hackers start “effective production” as quickly as possible.</p><p>NonceGeekDAO has more plans for the growth of indie hackers.</p><p>If you are interested in becoming an indie hacker, you can dm me on Twitter: <a href="https://x.com/0xleeduckgo">https://x.com/0xleeduckgo</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b904447d359a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>