diff --git a/docs/archive/announcements/news/carpe-beta-launched.md b/blog/carpe-beta-launched.md similarity index 78% rename from docs/archive/announcements/news/carpe-beta-launched.md rename to blog/carpe-beta-launched.md index ae021c15..394843d9 100644 --- a/docs/archive/announcements/news/carpe-beta-launched.md +++ b/blog/carpe-beta-launched.md @@ -1,22 +1,15 @@ - -10 Feb 2022 -- With the launch of the beta version of the Carpe Desktop App, the 0L Network has taken the next step towards making it possible for anyone to run a miner and earn crypto rewards. - - - +--- +title: "Carpe Beta Launched" +date: 2022-02-10 +tags: [carpe, wallet, software] +--- + +With the launch of the beta version of the Carpe Desktop App, the 0L Network has taken the next step towards making it possible for anyone to run a miner and earn crypto rewards. Carpe is a desktop wallet and miner that runs on the new 0L Network blockchain. The app is lightweight and designed to help you establish your digital identity in the 0L Network, while paying you coins to do so. Carpe is a standalone desktop application that will run on any contemporary Windows or Mac machine. The app is gentle on your resources, meaning that you can continue to use your computer normally while the app runs in the background. Simply install it, turn it on, and start earning tokens. - - - Today's release is the Beta of Carpe. The new version includes an improved interface and user experience and, under the hood, auto-update and automatic network connections. With this release, the community would also like to thank the over 3,000 (!!) alpha testers who have helped us bring Carpe to where it is today. - - - -**To get started, [follow this link](https://github.com/0LNetworkCommunity/carpe)**. We've also created a set of easy to follow instructions, including [a video tutorial](https://youtu.be/FcPiiZNS8sA). Additionally, [you can also find a welcoming community of people that would be happy to help you on our Discord Server. Join us!](https://discord.gg/Ry2cf4NrbS) - - - +**To get started, [follow this link](https://github.com/0LNetworkCommunity/carpe)**. We've also created a set of easy to follow instructions, including [a video tutorial](https://youtu.be/FcPiiZNS8sA). Additionally, [you can also find a welcoming community of people that would be happy to help you on our Discord Server. Join us!](https://discord.gg/0LNetwork) Carpe Diem diff --git a/docs/archive/announcements/news/carpe-goes-multilingual.md b/blog/carpe-goes-multilingual.md similarity index 90% rename from docs/archive/announcements/news/carpe-goes-multilingual.md rename to blog/carpe-goes-multilingual.md index 6ca10068..d26dc87f 100644 --- a/docs/archive/announcements/news/carpe-goes-multilingual.md +++ b/blog/carpe-goes-multilingual.md @@ -1,14 +1,12 @@ +--- +title: "Carpe Goes Multilingual" +date: 2022-03-25 +tags: [carpe, wallet, software] +--- + We've released, today, a new version of the 0L Network's Carpe Wallet \& Desktop Miner. This release (v.0\.3\.0\) is our latest release in the Carpe Beta series and includes significant new functionality, including multilingual support and a new tab "Events", which displays a list of events associated with your account (i.e., when coins move in and out of the wallet). This latest version ships with Chinese, Portuguese, and French language support. It is our plan to add additional languages in the near future. - - - To upgrade to the latest version, simply shut down and then restart your Carpe instance. You should be prompted to install the new version. Thanks to all on the Dev Team for making this happen! For those of you who are new to Carpe, [follow this link to grab the installer](https://github.com/0LNetworkCommunity/carpe) for Mac or WIN - - - To learn more about Carpe, visit the dedicated page on this site: [http://openlibra.blog/technology/carpe\-desktop\-app/](http://openlibra.blog/technology/carpe-desktop-app/) - - diff --git a/docs/archive/canonical/technical/delay-towers-pt-0.md b/blog/delay-towers-pt-0.md similarity index 97% rename from docs/archive/canonical/technical/delay-towers-pt-0.md rename to blog/delay-towers-pt-0.md index 20c4b4b2..f3e211a6 100644 --- a/docs/archive/canonical/technical/delay-towers-pt-0.md +++ b/blog/delay-towers-pt-0.md @@ -1,3 +1,10 @@ +--- +title: "Part 0 - A high-throughput chain with a fair launch" +date: 2021-11-01 +tags: [Delay Towers, canonical] +--- + + ## A high\-throughput chain with a fair launch diff --git a/docs/archive/canonical/technical/delay-towers-pt-1.md b/blog/delay-towers-pt-1.md similarity index 98% rename from docs/archive/canonical/technical/delay-towers-pt-1.md rename to blog/delay-towers-pt-1.md index 19136dc4..75ef5c1d 100644 --- a/docs/archive/canonical/technical/delay-towers-pt-1.md +++ b/blog/delay-towers-pt-1.md @@ -1,3 +1,10 @@ +--- +title: "Part 1 - Puzzle Towers for BFT" +date: 2021-11-05 +tags: [Delay Towers, canonical] +--- + + ## Puzzle Towers for BFT diff --git a/docs/archive/canonical/technical/delay-towers-pt-2.md b/blog/delay-towers-pt-2.md similarity index 98% rename from docs/archive/canonical/technical/delay-towers-pt-2.md rename to blog/delay-towers-pt-2.md index 275bb200..6c5a4d95 100644 --- a/docs/archive/canonical/technical/delay-towers-pt-2.md +++ b/blog/delay-towers-pt-2.md @@ -1,3 +1,10 @@ +--- +title: "Part 2 - From Puzzle Towers and VDFs to Delay Towers" +date: 2021-11-08 +tags: [Delay Towers, canonical] +--- + + ## From Puzzle Towers and VDFs to Delay Towers diff --git a/docs/archive/canonical/technical/delay-towers-pt-3-implementation-on-bft.md b/blog/delay-towers-pt-3-implementation-on-bft.md similarity index 99% rename from docs/archive/canonical/technical/delay-towers-pt-3-implementation-on-bft.md rename to blog/delay-towers-pt-3-implementation-on-bft.md index 52bcb6d7..7c98e841 100644 --- a/docs/archive/canonical/technical/delay-towers-pt-3-implementation-on-bft.md +++ b/blog/delay-towers-pt-3-implementation-on-bft.md @@ -1,3 +1,10 @@ +--- +title: "Part 3 - A Delay Towers Implementation on BFT" +date: 2021-11-12 +tags: [Delay Towers, canonical] +--- + + ## TL;DR diff --git a/docs/archive/canonical/future-proofing-the-economics-of-blockchains-pt-3.md b/blog/future-proofing-the-economics-of-blockchains-pt-3.md similarity index 99% rename from docs/archive/canonical/future-proofing-the-economics-of-blockchains-pt-3.md rename to blog/future-proofing-the-economics-of-blockchains-pt-3.md index 029fbdd2..7672d7de 100644 --- a/docs/archive/canonical/future-proofing-the-economics-of-blockchains-pt-3.md +++ b/blog/future-proofing-the-economics-of-blockchains-pt-3.md @@ -1,3 +1,10 @@ +--- +title: "Future-Proofing the Economics of Blockchains - Part III" +date: 2021-11-17 +tags: [canonical] +--- + + ## TL;DR diff --git a/docs/archive/canonical/future-proofing-the-economics-of-blockchains-pts-1--2.md b/blog/future-proofing-the-economics-of-blockchains-pts-1--2.md similarity index 99% rename from docs/archive/canonical/future-proofing-the-economics-of-blockchains-pts-1--2.md rename to blog/future-proofing-the-economics-of-blockchains-pts-1--2.md index 2cfeb4b3..c8b30b95 100644 --- a/docs/archive/canonical/future-proofing-the-economics-of-blockchains-pts-1--2.md +++ b/blog/future-proofing-the-economics-of-blockchains-pts-1--2.md @@ -1,3 +1,10 @@ +--- +title: "Future-Proofing the Economics of Blockchains - Part I and II" +date: 2021-11-17 +tags: [canonical] +--- + + ## TL;DR diff --git a/docs/archive/canonical/libra-liberated.md b/blog/libra-liberated.md similarity index 99% rename from docs/archive/canonical/libra-liberated.md rename to blog/libra-liberated.md index 238d49ab..af2fd076 100644 --- a/docs/archive/canonical/libra-liberated.md +++ b/blog/libra-liberated.md @@ -1,3 +1,10 @@ +--- +title: "Libra Liberated" +date: 2021-11-15 +tags: [canonical] +--- + + There once was a community that wanted a blockchain. diff --git a/docs/archive/announcements/news/new-milestones-for-carpe.md b/blog/new-milestones-for-carpe.md similarity index 95% rename from docs/archive/announcements/news/new-milestones-for-carpe.md rename to blog/new-milestones-for-carpe.md index 76ae9891..82f87841 100644 --- a/docs/archive/announcements/news/new-milestones-for-carpe.md +++ b/blog/new-milestones-for-carpe.md @@ -1,50 +1,32 @@ +--- +title: "New Milestones for Carpe" +date: 2022-08-11 +tags: [carpe, wallet, software] +--- + The 0L Network today reached a new record in terms of activity on the network: The daily number of active Carpe miners topped 2,000 for the first time today, with 2,080 installations running and earning tokens today. The number of active Carpe miners has been increasing steadily across the last 30 days, as new users have joined the community and discovered how easy it is to run Carpe and earn rewards. - - - Also on this date we have released a newly updated version of Carpe \- version 0\.5\.0\. Here's what's new: - - - * Wallet\-to\-wallet coin transfers * Better reliability connecting to the chain * Dynamic VDF proofs (improving network and miner performance!) * Over\-the\-air upgrades * Support for localization in multiple new languages - - - For the next few days, you will need to manually download and install Carpe. The automatic updater will be enabled after we’ve given our more experienced users a chance to install the new version manually and report back on their experience. - - - Here are the links for the packages you need for a manual update: - - - * Windows users: [https://github.com/0LNetworkCommunity/carpe/releases/download/v0\.5\.0/carpe\_0\.5\.0\_x64\.msi](https://github.com/0LNetworkCommunity/carpe/releases/download/v0.5.0/carpe_0.5.0_x64.msi) * MacOS users (11\+ only): [https://github.com/0LNetworkCommunity/carpe/releases/download/v0\.5\.0/carpe\-macos\-11\.dmg](https://github.com/0LNetworkCommunity/carpe/releases/download/v0.5.0/carpe-macos-11.dmg) * Debian users: [https://github.com/0LNetworkCommunity/carpe/releases/download/v0\.5\.0/carpe\_0\.5\.0\_amd64\.deb](https://github.com/0LNetworkCommunity/carpe/releases/download/v0.5.0/carpe_0.5.0_amd64.deb) - - - For those of you unfamiliar with Carpe, it is a wallet and light miner application that can run on most consumer computers. The app only requires 1 thread of your CPU, meaning not only can most machines run it, but you can run it in the background while you do other things with your machine. Download Carpe, learn about 0L and start receiving rewards \- it’s very easy to get started. - - - Kudos to all of the Carpe contributors and the top\-tier 0L community for pressing on during this crypto winter. It’s time for builders to build! We welcome all builders into the community and encourage you to explore this site to learn more and [drop by our Discord and say hi](https://discord.gg/Nw7MpczV4X). - - - Carpe diem! diff --git a/blog/openlibra-nodejs-release.md b/blog/openlibra-nodejs-release.md index f2edbbb5..2aa42d16 100644 --- a/blog/openlibra-nodejs-release.md +++ b/blog/openlibra-nodejs-release.md @@ -1,7 +1,5 @@ --- title: "The Open Libra NodeJS Library Has Been Published on npm 🔥" -author: "Codilion" -author_title: "Contributor" date: 2025-02-06 tags: [open-libra-sdk, npm] --- @@ -9,7 +7,7 @@ tags: [open-libra-sdk, npm] Congratulations to the Open Libra contributors! ### **Open Libra NodeJS library** `open-libra-sdk` has been published on the npm repository! - + This SDK brings you an easy way to integrate Open Libra blockchain functionality into your NodeJS applications. Whether you’re building new decentralized apps or exploring blockchain integrations, this library provides the essential tools to get started. For complete installation details, usage instructions, and further information, please visit the npm repository page: diff --git a/blog/press-mysten.md b/blog/press-mysten.md new file mode 100644 index 00000000..014e963e --- /dev/null +++ b/blog/press-mysten.md @@ -0,0 +1,11 @@ +--- +title: "Mysten Labs Partners With 0L Network to Expand Move For Secure Smart Contracts" +date: 2022-02-01 +tags: [press, partners] +--- + + +Mysten Labs, a Web 3\.0 infrastructure company, announced a partnership with 0L Network, an open and permissionless version of the Diem blockchain. Together, Mysten Labs and 0L will build tools and resources for the Move smart contract programming language. Move, released as part of the Diem technology stack, is uniquely effective for secure smart contract development. In line with the partnership, the projects plan to roll out joint Move hackathons and mentorship programs starting in March 2022\. + +[Read Full Article](https://www.globenewswire.com/news-release/2022/02/01/2377039/0/en/Mysten-Labs-Partners-With-0L-Network-to-Expand-Move-For-Secure-Smart-Contracts.html) + diff --git a/docs/archive/canonical/technical/proof-of-fee-part-1.md b/blog/proof-of-fee-part-1.md similarity index 99% rename from docs/archive/canonical/technical/proof-of-fee-part-1.md rename to blog/proof-of-fee-part-1.md index cabdf21f..5e3097a6 100644 --- a/docs/archive/canonical/technical/proof-of-fee-part-1.md +++ b/blog/proof-of-fee-part-1.md @@ -1,19 +1,14 @@ +--- +title: "Proof of Fee - Part 1" +date: 2022-10-15 +tags: [PoF, Proof of Fee, canonical] +--- + ## The Cost of Consensus - -  - - - - -  - - - - ### TL;DR diff --git a/docs/archive/canonical/technical/proof-of-fee-part-2.md b/blog/proof-of-fee-part-2.md similarity index 99% rename from docs/archive/canonical/technical/proof-of-fee-part-2.md rename to blog/proof-of-fee-part-2.md index e2580e59..bec223ad 100644 --- a/docs/archive/canonical/technical/proof-of-fee-part-2.md +++ b/blog/proof-of-fee-part-2.md @@ -1,4 +1,9 @@ - +--- +title: "Proof of Fee - Part 2" +date: 2022-10-20 +tags: [PoF, Proof of Fee, canonical] +--- + ``` In [Part 1 of this paper](http://openlibra.blog/2022/10/15/proof-of-fee-part-1/) we laid the foundations for Proof of Fee. Some of the ideas expressed there may be different from what you have seen elsewhere, and we do urge you to read that before you begin here. In Part 2 of this paper, below, we get into the mechanics and implementation details of Proof-of-Fee (PoF). diff --git a/docs/archive/proposals/october-2022-governance-recap.md b/blog/proposals/october-2022-governance-recap.md similarity index 99% rename from docs/archive/proposals/october-2022-governance-recap.md rename to blog/proposals/october-2022-governance-recap.md index 049894e5..a47ffae2 100644 --- a/docs/archive/proposals/october-2022-governance-recap.md +++ b/blog/proposals/october-2022-governance-recap.md @@ -1,3 +1,10 @@ +--- +title: "2022 Governance Recap" +date: 2022-11-08 +tags: [governance, proposal] +--- + + # October 2022 Governance Recap The 0L Community recently concluded its first round of collaborative, decentralized strategic planning. Starting first with rounds of guided discussion on the [RadicalxChange Voice](https://voice.radicalxchange.org/) platform, the process culminated with a set of eight proposals for community vote. In this blog post, we’re going to take a brief look at the contents of those proposals and reflect on the outcomes of the vote.  diff --git a/docs/archive/proposals/proposal-2210-1-final-supply.md b/blog/proposals/proposal-2210-1-final-supply.md similarity index 97% rename from docs/archive/proposals/proposal-2210-1-final-supply.md rename to blog/proposals/proposal-2210-1-final-supply.md index 781275af..ca5cf00c 100644 --- a/docs/archive/proposals/proposal-2210-1-final-supply.md +++ b/blog/proposals/proposal-2210-1-final-supply.md @@ -1,3 +1,9 @@ +--- +title: "Proposal 2210-1 - Final Supply" +date: 2022-10-11 +tags: [governance, proposal] +--- + ###### Proposal Type: **Signalling** diff --git a/docs/archive/proposals/proposal-2210-2-proof-of-fee.md b/blog/proposals/proposal-2210-2-proof-of-fee.md similarity index 98% rename from docs/archive/proposals/proposal-2210-2-proof-of-fee.md rename to blog/proposals/proposal-2210-2-proof-of-fee.md index ea1d25a1..9051e185 100644 --- a/docs/archive/proposals/proposal-2210-2-proof-of-fee.md +++ b/blog/proposals/proposal-2210-2-proof-of-fee.md @@ -1,3 +1,9 @@ +--- +title: "Proposal 2210-2 - Proof of Fee" +date: 2022-10-13 +tags: [governance, proposal] +--- + ###### Proposal Type: Signalling diff --git a/docs/archive/proposals/proposal-2210-3-musical-chairs.md b/blog/proposals/proposal-2210-3-musical-chairs.md similarity index 98% rename from docs/archive/proposals/proposal-2210-3-musical-chairs.md rename to blog/proposals/proposal-2210-3-musical-chairs.md index 71c77bb9..138f7806 100644 --- a/docs/archive/proposals/proposal-2210-3-musical-chairs.md +++ b/blog/proposals/proposal-2210-3-musical-chairs.md @@ -1,3 +1,9 @@ +--- +title: "Proposal 2210-3 - Musical Chairs" +date: 2022-10-10 +tags: [governance, proposal] +--- + ###### Proposal Type: Signalling diff --git a/docs/archive/proposals/proposal-2210-4-repurpose-carpe.md b/blog/proposals/proposal-2210-4-repurpose-carpe.md similarity index 96% rename from docs/archive/proposals/proposal-2210-4-repurpose-carpe.md rename to blog/proposals/proposal-2210-4-repurpose-carpe.md index 4fd23ef8..decda1ce 100644 --- a/docs/archive/proposals/proposal-2210-4-repurpose-carpe.md +++ b/blog/proposals/proposal-2210-4-repurpose-carpe.md @@ -1,3 +1,9 @@ +--- +title: "Proposal 2210-4 - Repurpose Carpe" +date: 2022-10-11 +tags: [governance, proposal] +--- + ###### Proposal Type: Signalling diff --git a/docs/archive/proposals/proposal-2210-5-revenue-binding-primitives.md b/blog/proposals/proposal-2210-5-revenue-binding-primitives.md similarity index 94% rename from docs/archive/proposals/proposal-2210-5-revenue-binding-primitives.md rename to blog/proposals/proposal-2210-5-revenue-binding-primitives.md index 58374e41..a3e0881e 100644 --- a/docs/archive/proposals/proposal-2210-5-revenue-binding-primitives.md +++ b/blog/proposals/proposal-2210-5-revenue-binding-primitives.md @@ -1,3 +1,9 @@ +--- +title: "Proposal 2210-5 - Revenue Binding Primitives" +date: 2022-10-11 +tags: [governance, proposal] +--- + ###### Proposal Type: Signalling diff --git a/docs/archive/proposals/proposal-2210-6-faucets-for-workers.md b/blog/proposals/proposal-2210-6-faucets-for-workers.md similarity index 95% rename from docs/archive/proposals/proposal-2210-6-faucets-for-workers.md rename to blog/proposals/proposal-2210-6-faucets-for-workers.md index d8068f9c..99c0bf49 100644 --- a/docs/archive/proposals/proposal-2210-6-faucets-for-workers.md +++ b/blog/proposals/proposal-2210-6-faucets-for-workers.md @@ -1,4 +1,9 @@ - +--- +title: "Proposal 2210-6 - Faucets for Workers" +date: 2022-10-11 +tags: [governance, proposal] +--- + ###### Proposal Type: Signalling diff --git a/docs/archive/proposals/proposal-2210-7-donor-directed-community-wallets.md b/blog/proposals/proposal-2210-7-donor-directed-community-wallets.md similarity index 97% rename from docs/archive/proposals/proposal-2210-7-donor-directed-community-wallets.md rename to blog/proposals/proposal-2210-7-donor-directed-community-wallets.md index 636efb90..56379c84 100644 --- a/docs/archive/proposals/proposal-2210-7-donor-directed-community-wallets.md +++ b/blog/proposals/proposal-2210-7-donor-directed-community-wallets.md @@ -1,3 +1,9 @@ +--- +title: "Proposal 2210-7 - Donor Directed Community Wallets" +date: 2022-10-12 +tags: [governance, proposal] +--- + ###### Proposal Type: Signalling diff --git a/docs/archive/proposals/proposal-2210-8-infrastructure-escrow-funding.md b/blog/proposals/proposal-2210-8-infrastructure-escrow-funding.md similarity index 96% rename from docs/archive/proposals/proposal-2210-8-infrastructure-escrow-funding.md rename to blog/proposals/proposal-2210-8-infrastructure-escrow-funding.md index 4604b936..cba7e6dc 100644 --- a/docs/archive/proposals/proposal-2210-8-infrastructure-escrow-funding.md +++ b/blog/proposals/proposal-2210-8-infrastructure-escrow-funding.md @@ -1,3 +1,9 @@ +--- +title: "Proposal 2210-8 - Infrastructure Escrow Funding" +date: 2022-10-12 +tags: [governance, proposal] +--- + ###### Proposal Type: Signalling diff --git a/docs/archive/proposals/scorpions-claw-proposal.md b/blog/proposals/scorpions-claw-proposal.md similarity index 96% rename from docs/archive/proposals/scorpions-claw-proposal.md rename to blog/proposals/scorpions-claw-proposal.md index 5ab4a8f4..3ecbd5fb 100644 --- a/docs/archive/proposals/scorpions-claw-proposal.md +++ b/blog/proposals/scorpions-claw-proposal.md @@ -1,4 +1,9 @@ -# Scorpion's Claw Recommendation +--- +title: "Scorpion's Claw Recommendation" +date: 2024-04-09 +tags: [fork, proposal] +--- + ## Community Wallet Analytics and V7 Hard Fork Parameters [DRAFT] @@ -18,9 +23,9 @@ The result is a list of 436 accounts. If validators decide, they can now run a v There was a handful of abuse cases. However, the vast majority of the exploit was conducted by a long-term community member who has publicly declared ownership of the accounts originating the exploit. -- 6DA2B828F3018637379203940C639A95 -- 27E9577869ADFD677DBA9C940DEECE0A -- 988B8C3B7E55B6E5126884E02C8F166E +- `6DA2B828F3018637379203940C639A95` +- `27E9577869ADFD677DBA9C940DEECE0A` +- `988B8C3B7E55B6E5126884E02C8F166E` A hard fork is recommended, and should happen with a validator ceremony open to the public and using a clean database using the version 7.0.0 software release. @@ -176,9 +181,9 @@ If the relationships of these few nodes are expanded, the flow of funds goes thr The community wallets involved in this case are: -- 7B61439A88060096213AC4F5853B598E -- 5E68026887147DE0EA9CA90962C25A41 -- 97DCBC6BFAA7EDF00F9002DAAED49C46 +- `7B61439A88060096213AC4F5853B598E` +- `5E68026887147DE0EA9CA90962C25A41` +- `97DCBC6BFAA7EDF00F9002DAAED49C46` There is no information publicly available about these "community" programs. Different from other credible and well regarded programs in the community. Their principal source of funding was from "validators" nodes which the individual publicly associated themselves with. Due to the nature of Match Index (described above), many other validators became unwitting contributors to these accounts (the "harvesting" exploit). @@ -188,15 +193,15 @@ Community wallets could not reasonably accumulate much capital unless they solic In this case, the exploiter had ownership of the following validator addresses: -- 6DA2B828F3018637379203940C639A95 -- 15B291FFCA97895D726E8AA9A5BE6A2A -- 5DC8C3878E99E9FD12EBDEFA1803D332 -- C5162C65FDE8C9D9CA9B564E41A54003 -- 988B8C3B7E55B6E5126884E02C8F166E -- 7D299BF3D624E937C23302D8B5E3A1B2 -- 99E4EE712E2A57F694344D288A0FC27A -- 9F1D8C66883768F167A097FF4C58DE88 -- C0FFEE1A3393516D27B72B28464EAA5F +- `6DA2B828F3018637379203940C639A95` +- `15B291FFCA97895D726E8AA9A5BE6A2A` +- `5DC8C3878E99E9FD12EBDEFA1803D332` +- `C5162C65FDE8C9D9CA9B564E41A54003` +- `988B8C3B7E55B6E5126884E02C8F166E` +- `7D299BF3D624E937C23302D8B5E3A1B2` +- `99E4EE712E2A57F694344D288A0FC27A` +- `9F1D8C66883768F167A097FF4C58DE88` +- `C0FFEE1A3393516D27B72B28464EAA5F` # The Hard Fork Goals diff --git a/docs/archive/proposals/team-arctika-recommendation.md b/blog/proposals/team-arctika-recommendation.md similarity index 97% rename from docs/archive/proposals/team-arctika-recommendation.md rename to blog/proposals/team-arctika-recommendation.md index 9441d268..f7b0a733 100644 --- a/docs/archive/proposals/team-arctika-recommendation.md +++ b/blog/proposals/team-arctika-recommendation.md @@ -1,3 +1,10 @@ +--- +title: "Team Arctika Recommendation" +date: 2023-05-23 +tags: [econ, proposal] +--- + + **To survive, the 0L Network needs to solve two problems. We need**: 1. Abundant capital for security, and 2. Abundant capital for recruiting talent. @@ -14,14 +21,14 @@ The crypto headwinds are significant: Regulatory pressure, fraud, scammers and a We can estimate that, in order to attract validators, the network will have to pay each validator US$4-5k per month (this is consistent with what validators are paid in mature networks with smoothly operating software). In our interviews with professional validators, we arrived at $4,200 as our baseline. See the data in the table, below: -![](../../assets/validator-opportunity-cost.png) +![](../../docs/assets/validator-opportunity-cost.png) The Team agrees that we need to provision for another 7 years of network operations. We’re roughly three years into the network’s life cycle at this point in time (1 year in testnet, followed by almost 2 years since Genesis). Altogether, we should make it through at least the first 10 years of the network. Of course, translating a token with no market value into monthly USD amounts requires some assumptions about value. We must take a conservative approach on market cap, for "all weather conditions". Despite what we’ve seen with some of our peer networks, we can't reasonably say that the base case for networks is a valuation of $1B\+ over the next 7 years. Likewise a network worth less than $50M for many years likely leads to extinction. So, the calculations we made assumed a $100M market cap, from which a token value could be extrapolated; this seemed like a reasonable base-case (which could be substantiated further). At that intersection: 100 validators earning $4,200 per month over 7 years, with a network on average worth $100m, the result is approx 35% of network capital needs to be pre-diluted for sufficient safety. -![](../../assets/infrastructure-escrow-pledge-sensitivity.png) +![](../../docs/assets/infrastructure-escrow-pledge-sensitivity.png) ### Over-allocation @@ -78,7 +85,7 @@ We looked at many models of dilutions and fees. Asking validators to invest 80% * Reduce the gap between worker and validators to 1\.3X from 16X. -![](../../assets/summary-dilution-impacts.png) +![](../../docs/assets/summary-dilution-impacts.png) We think this allocation, with abundant amounts for future capital, which honors prior workers such that we can continue recruiting for future talent, and sets up all current participants for future success is **unique and exemplary in the industry, and fulfills our mission of creating "good capital" and gives us the best shot at surviving and thriving.** diff --git a/docs/archive/proposals/the-0l-network-constitution.md b/blog/proposals/the-0l-network-constitution.md similarity index 96% rename from docs/archive/proposals/the-0l-network-constitution.md rename to blog/proposals/the-0l-network-constitution.md index ecd27aa6..ee6c035d 100644 --- a/docs/archive/proposals/the-0l-network-constitution.md +++ b/blog/proposals/the-0l-network-constitution.md @@ -1,3 +1,9 @@ +--- +title: "0L Network Constitution" +date: 2022-05-03 +tags: [governance] +--- + Adopted by Community Polling on 3 May 2022 diff --git a/blog/research-report-decentralizing-permissioned-blockchain-with-delay-towers.md b/blog/research-report-decentralizing-permissioned-blockchain-with-delay-towers.md new file mode 100644 index 00000000..cc0341a1 --- /dev/null +++ b/blog/research-report-decentralizing-permissioned-blockchain-with-delay-towers.md @@ -0,0 +1,14 @@ +--- +title: "Research Report: Decentralizing Permissioned Blockchain with Delay Towers" +date: 2022-03-22 +tags: [research report] +--- + + +This report, published 18 March 2022, looks at the Delay Towers mechanism that was pioneered and deployed in the 0L Network. + +The article was co-authored by Shashank Motepalli and Hans-Arno Jocobsen of the University of Toronto. We quote the original synopsis below: + +> Growing excitement around permissionless blockchains is uncovering its latent scalability concerns. Permissioned blockchains offer high transactional throughput and low latencies while compromising decentralization. In the quest for a decentralized, scalable blockchain fabric, i.e., to offer the scalability of permissioned blockchain in a permissionless setting, we present L4L to encourage decentralization over the permissioned Libra network without compromising its sustainability. L4L employs delay towers, -- puzzle towers that leverage verifiable delay functions -- for establishing identity in a permissionless setting. Delay towers cannot be parallelized due to their sequential execution, making them an eco-friendly alternative. We also discuss methodologies to replace validators participating in consensus to promote compliant behavior. Our evaluations found that the cost of enabling decentralization over permissioned networks is almost negligible. Furthermore, delay towers offer an alternative to existing permissionless consensus mechanisms without requiring airdrops or pre-sale of tokens. + +\>\> [View the original article, with download link to full report](https://arxiv.org/abs/2203.09714) diff --git "a/docs/archive/proposals/spring-forward\302\240.md" "b/blog/spring-forward\302\240.md" similarity index 98% rename from "docs/archive/proposals/spring-forward\302\240.md" rename to "blog/spring-forward\302\240.md" index 8653bd82..1a971347 100644 --- "a/docs/archive/proposals/spring-forward\302\240.md" +++ "b/blog/spring-forward\302\240.md" @@ -1,155 +1,70 @@ +--- +title: "Spring Forward" +date: 2022-04-29 +tags: [news] +--- + -Growth requires challenge.  - - - +Growth requires challenge There was plenty of such fuel over the last several weeks, challenging our community to run a functional and fair network that is more poised for growth. This announcement will detail what has happened, how we addressed it and how, along the way, we solved a number of different problems and improved prospects going forward. - - - On 9 April 2022, the 0L Network halted. Multiple factors combined to create the incident; factors that started small and cascaded until the entire network ceased to produce blocks. While the detailed causes and the technical forensics have been discussed at length in our community meetings, the important point to raise here is that the halt was avoidable – or rather would have been avoidable – had a sufficient number within our validator community been more attentive to their machines and taken steps in a timely fashion. Better coordination is a key learning derived from this event. - - - With the network stopped, the community decided to take the time to make some major changes and bring back a network that was better and stronger and more aligned to the broader community’s interests. **As you read this, the network is back, with a new set of features and a richer set of options for developers, Carpe miners, and the community as a whole.** - - - Among the enhancements we’ve launched with this new version of the 0L Network: - - - ### **Carpe Enhancements** - - - Together with this network upgrade, we will shortly be releasing a new version of the Carpe wallet and desktop miner. With this release, Carpe will attain full wallet functionality, with the ability for users to send and receive coins using a standard wallet interface. The new release is in testing now and will be announced soon. The Internet of Value needs money in motion. - - - ### **Make Whole** - - - With this upgrade, we have set up a methodology for Carpe miners to claim coins that were under-paid to them in several past epochs due to a network bug. The Make Whole proposal has already been approved by the community, and we have set up a process that can be executed easily from inside Carpe to do so (you can learn more about this, and the new version of Carpe, once the release date is formalized). - - - ### **Slow Wallets** - - - Slow wallet holders, particularly the members of our Hustle Karma workforce, will be pleased to learn that we have also used this upgrade to ease limitations on slow wallets. As of today, you can use your Carpe slow wallets to move coins! Daily transaction limits remain in place for slow wallets, at the level of 1,000 Libra per day. (Note that the daily transaction limit parameter is subject to adjustment by the community at a future date.) The goal is to balance active labor participation and value accrual with fair vesting and spending. - - - ### **Recovery Tools** - - - A new set of recovery tools and workflows to make the network better able to recover from shocks in the future. There were a number of refactors to the writeset-tool, which enables a halted network to apply transactions at rest to upgrade the state machine code, update validator set, trigger new epochs, and enter recovery mode. Future halts could have very minimal downtime if the root cause is found quickly. - - - ## **Addressing the Larger Problem** - - - The tools and actions listed above are important and worth celebrating. However, we have a larger social issue that needs resolution – that is, the negative impact of passive validators.  - - - The recent outage shows the need to take action to better align validator incentives with the best interests of the broader 0L Network community. There is a very good argument that the recent network stoppage was less a technical problem than a problem of misalignment of incentives and expectations. We need to take steps to assure an engaged, professional validator set and we also need to change the competitive dynamics for validators in order to disincentivize passive validators.  - - - To tackle the first issue, we are implementing a new approach to validator set selection. At the launch of the network, validators were entitled to invite whomever they chose to join the validator set. The system had no checks in place, other than a rate limit on how frequently invitations could be issued. We initially counted on social pressure and common sense to guide our validators to select individuals or organizations who were able to manage their nodes to a professional level, and who would respect system requirements. Unfortunately, we now have experience showing that a more rigorous approach is needed. Indeed, the initial failures that began the cascade that led to the most recent network halt occurred first with the nodes that were under-provisioned and not in line with our published system requirements. Those failures were then complicated by many of those validators failing to be responsive to their machines and take remedial steps to recover from the failure. - - - Going forward, we are layering in a “vouching” system for validator set selection. At every epoch the system will check that each validator entering the set has endorsement by at least 4 existing validators of different "ancestry" . We mitigate the sybil issues by checking that the vouches come from  different “family trees” (i.e., who onboarded them). Every epoch, you can only join the validator set if you have at least 4 peers known to be good actors vouching for you. To facilitate this requirement, we have created an onchain permission tree that makes it easy to trace the lineage of individual validators.  - - - ### **Funding the Community via Proof of Burn** - - - The second issue – the competitive dynamics of the validator class – is somewhat more complex. The goal is to make the cost to exist as a validator higher, and thereby disincentivize passive validators (free riders). To accomplish this aim, we are making two changes. - - - First, we are putting in place a more expensive Proof of Burn mechanism. At launch, Proof of Burn was a fixed and insubstantial amount: Each validator was charged 1 coin per epoch to join the validator set. We also implemented a voluntary autopay function that encouraged validators to redirect a portion of their rewards to community wallets. The mechanism was 0L’s answer to how to capitalize the system’s growth and expansion in the absence of outside capital.  - - - By increasing the Proof of Burn we can also automate community wallet funding by making it simpler and more seamless for those who opt-in. We’re increasing the burn from 1 coin to 50% of validator rewards. Those funds will be distributed each epoch among the community wallets based on donations to those wallets. Validators also have the option to give more than 50% if they wish, and if they do not want to divert the funds to the community wallets, they can elect to have the coins burned. Note that this change simply streamlines the autopay functionality that has been tested since the Genesis of the network. - - - Second, we are closing a loophole in the system’s capitalization game by making the Proof of Burn apply to both active and inactive validators. This approach not only helps provide critical network funding, it also incentivizes validators to participate in consensus in order to earn rewards and avoid the clawback of their previously earned coins. We expect this change to be controversial with some people and we have suspended the implementation of the Proof of Burn on inactive validators for 10 epochs. During that time, people can learn more about it and discuss. If there are substantial objections, the issue will be debated and revisited.  - - - The changes to the validator onboarding and economics may not be guaranteed to reach the desired state, but directionally, they move us closer to the goal: Engaged validators who are stewards of the chain. Implementation of new types of economic incentives and games (for example, delegation) could build on these changes, make the economics more interesting for Carpe miners, and also help disincentivize inattentive validators.  - - - ## **Next Steps** - - - At present, the network is in Recovery Mode and Carpe miners are able to start the app and check balances and have minimal interactions, but not mine their Tower. Recovery Mode suspends all economic activity to allow for testing and network stabilization. (This also disincentivized actors from front-running or otherwise taking advantage of skewed economics from network halts.) To be clear, while the network is in Recovery Mode no rewards are being paid to anyone – not even validators. One Saturday, 30 April, the network will open again for Carpe miners and we invite everyone to come back in. - - - Also, as noted above, the Proof of Burn on inactive validators is being held in abeyance until Epoch 185\. During that time, if there are objections to this approach, they need to be discussed in the community to determine whether action should be taken.  - - - ## **In Conclusion** - - - Blockchain are infinite games. The game itself evolves and adapts. Passivity and paralysis are not an option. - - - **The 0L network is live and running, as is our global community working towards the mission of a transparent, participatory, liberating, open blockchain network for all. We have dealt with the challenges of the moment to create a stronger foundation for the future, and we will continue to evolve the technology, social contracts, and norms of the project to best accomplish such a mission. Your voice is heard. There are more rewards for Carpe miners, as well as a hard commitment for 50% of the funds to flow to community-building wallets that reward participants that build along with us.** - - - - -**Carpe diem. ✊☀️** +**Carpe diem ✊☀️** diff --git a/blog/the-road-less-traveled.md b/blog/the-road-less-traveled.md new file mode 100644 index 00000000..d40e624d --- /dev/null +++ b/blog/the-road-less-traveled.md @@ -0,0 +1,65 @@ +--- +title: "Open Libra: The Road Less Traveled" +date: 2025-02-12 +tags: [blog, news, canonical] +--- + +**A force of the public which has the capital necessary to make meaningful interventions, at the scale of the largest organizations in society. This requires independence, durability, and sense.** + + +### Independent, Perpetual, Sensible + +*OL looks different because it is different.* Open Libra does not have a foundation, has no labs entity, no VC funding, and no ICO. Why not? Because, unlike the First In - First Out pump and dump schemes that litter the Crypto landscape, Open Libra has a clean regulatory and moral profile to serve our focused mission — perpetual funding for impact in society, independent of corporations, governments, and traditional finance of the day. + +The unique feature of digital assets is their opportunity to be perpetual, a highly misunderstood and underrated property. OL measures its plans in centuries, on much longer scales than you are accustomed to if you are in tech. But if instead the product is defined as independent and good capital, then a 100-year time frame is plausible. The next generations should expect there to exist an institution (more like a force of the public) which has the capital necessary to make meaningful interventions, at the scale of the largest organizations in society. Open Libra is five years in, and still pre-launch. Deliberately being principled, vigilant, and evolutionary. + +### Forget Cryptocurrency, Think *Open Titles* + +The future lies in the thing that comes after currencies: durable capital which can accumulate entitlements, benefits, and rights over time. Digital titles that are both accessible and enforceable over generations, far beyond transient software versions and networks. Crypto makes a tacit promise: wealth while participating in what the future brings. We extend that further to create a product everyone would want to be a part of: to invite the 98% of the world who seek to participate in future themes of technology, social coordination, and build wealth through engagement with society. + +We ask difficult questions of the industry because, to us, the design space is clear, but the offers in the market are not. + +Learn more about our vision at [https://openlibra.io](https://openlibra.io). + +## 2024: A Year of Resilience and Progress + +2024 was a pivotal year for Open Libra. Reinforcing our commitment to the long game, the project undertook several strategic measures to solidify its foothold and secure the mission. + +We faced an exploit, a multi-step governance abuse which involved social engineering, deception, and transaction manipulation. + +**This was not a software failure, but a breach of trust.** + +This of course, is not a surprise, and neither an unexpected disappointment. OL goes slow in order to observe and correct the course. The abuse unfolded faster precisely because the exploiters began to take notice of the core founding team that was catching up to the evidence. + +The active community responded with an industry-leading forensic process that disabled 98% of exploited funds, demonstrating our commitment to fairness and justice in our community. The community has been clear from the beginning, that we do not invite or suffer that Open Libra is not for the 2% seeking quick wins at the expense of fellow community members. To address these challenges, a hard fork was executed and forensic tools were created, available at [GitHub](https://github.com/openlibra), facilitating interoperability and expanding the Open Libra ecosystem. + +It took months to develop Forensic Db, a missing piece of blockchains. The comprehensive forensic database ensures project accountability and transparency. Where necessary, proper authorities in The Netherlands were also engaged to ensure regulatory compliance and proper legal standing. + +## Learnings + +### Socialized Enforcement + +Unlike traditional blockchain projects with centralized governance structures, Open Libra enforces norms through four levels of socialized enforcement. When loose social consensus fails, you should expect to see several layers of enforcement: + +1. **Smart Contracts:** Improve the binding of key policies of your community norms. +2. **Social Slashing:** Start a new network that reinforces the norms, move the party elsewhere. +3. **Civil Legal Recourse:** Utilizing judicial systems is fair game when Smart contracts are multi-party agreements. +4. **Criminal Enforcement:** Ultimately, criminal enforcement is reasonable against fraud and misconduct when a sovereign's laws overlap with ours. + +### First In Last Out is Worth Fighting For + +One of OL's oldest founding beliefs is that First In First Out leads to abuse in markets (pump and dump). Many of our exemplary policies (Slow Wallets, Community Wallets) are explicitly designed with a goal of “First In, Last Out” principle. In 2024, we diverged from this norm, both intentionally by exploiters and unintentionally by distraction. Governance upgrades have been proposed and are in progress to ground us in this principle again. + +## Looking Forward to 2025 and Beyond + +As the project sets its sights on the future, Open Libra will introduce several key initiatives in 2025 designed to reinforce its mission and expand its impact: + +- **SlowWalletV2 Proposal:** Enhancing security and longevity for long-term holders. +- **Project Nest Egg:** An initiative that aims to transform Libra into a force for good by funding high-quality real-world businesses by effectively deploying capital through Community Wallets. By harnessing voluntary contributions, these wallets become a strategic asset, driving sustainable growth and innovation within the ecosystem. +- **Validator Bidding Optimization:** Streamlining the validator selection process for greater efficiency. +- **Exchange Listing Initiatives:** Community-driven efforts to expand accessibility and liquidity. + +## Join Us + +*The active community invite experts across disciplines who align with our mission and are committed to sustainable, long-term impact to JOIN US: [https://openlibra.io](https://openlibra.io).* + diff --git a/docs/archive/econ/the-rulebook-at-genesis.md b/blog/the-rulebook-at-genesis.md similarity index 98% rename from docs/archive/econ/the-rulebook-at-genesis.md rename to blog/the-rulebook-at-genesis.md index df744f07..ce8e86ca 100644 --- a/docs/archive/econ/the-rulebook-at-genesis.md +++ b/blog/the-rulebook-at-genesis.md @@ -1,3 +1,10 @@ +--- +title: "Future-Proofing the Economics of Blockchains - Appendix: The Rulebook at Genesis" +date: 2021-11-18 +tags: [canonical] +--- + + As you can see in our write ups mentioned above, we do things a little differently around here: We had no venture investors, there is no premine, no foundation with tokens, and anyone with a laptop can participate and earn coins. Here's a quick reference to the policies implemented at genesis: diff --git a/blog/thedefiant.md b/blog/thedefiant.md new file mode 100644 index 00000000..19e2bdbe --- /dev/null +++ b/blog/thedefiant.md @@ -0,0 +1,10 @@ +--- +title: "0L Aims To Revive Facebook’s Libra Cryptocurrency With Fair Launch" +date: 2021-11-16 +tags: [news] +--- + + +Every now and then folks adjacent to crypto Twitter like to tweet out some version of “Remember Libra?”. Libra was Facebook’s first effort to get in on the decentralized web, with a bold promise to “bank the unbanked” via blockchain that was revealed in mid-2019\. The world’s largest social network caved into regulatory pressure and gave up on its higher-end ambitions less than a year later. + +[Read Full Article](https://thedefiant.io/0l-libra-fork-fair-launch/) diff --git a/docs/archive/announcements/news/press-mysten.md b/docs/archive/announcements/news/press-mysten.md deleted file mode 100644 index c0a0349c..00000000 --- a/docs/archive/announcements/news/press-mysten.md +++ /dev/null @@ -1,59 +0,0 @@ - -  - - - - - -#### Press Release - 1 Feb 2022 - - - - - - -## Mysten Labs Partners With 0L Network to Expand Move For Secure Smart Contracts - - - - - - -Mysten Labs, a Web 3\.0 infrastructure company, announced a partnership with 0L Network, an open and permissionless version of the Diem blockchain. Together, Mysten Labs and 0L will build tools and resources for the Move smart contract programming language. Move, released as part of the Diem technology stack, is uniquely effective for secure smart contract development. In line with the partnership, the projects plan to roll out joint Move hackathons and mentorship programs starting in March 2022\. - - - - - -[Read Full Article](https://www.globenewswire.com/news-release/2022/02/01/2377039/0/en/Mysten-Labs-Partners-With-0L-Network-to-Expand-Move-For-Secure-Smart-Contracts.html) - - - - - - - -#### The Defiant - 16 Nov 2021 - - - - - - -## 0L Aims To Revive Facebook’s Libra Cryptocurrency With Fair Launch - - - - - - -Every now and then folks adjacent to crypto Twitter like to tweet out some version of “Remember Libra?”. Libra was Facebook’s first effort to get in on the decentralized web, with a bold promise to “bank the unbanked” via blockchain that was revealed in mid-2019\. The world’s largest social network caved in to regulatory pressure and gave up on its higher-end ambitions less than a year later. - - - - - - - - -[Read Full Article](https://thedefiant.io/0l-libra-fork-fair-launch/) diff --git a/docs/archive/canonical/technical/research-report-decentralizing-permissioned-blockchain-with-delay-towers.md b/docs/archive/canonical/technical/research-report-decentralizing-permissioned-blockchain-with-delay-towers.md deleted file mode 100644 index 59c95eab..00000000 --- a/docs/archive/canonical/technical/research-report-decentralizing-permissioned-blockchain-with-delay-towers.md +++ /dev/null @@ -1,17 +0,0 @@ - -This report, published 18 March 2022, looks at the Delay Towers mechanism that was pioneered and deployed in the 0L Network. - - - - -The article was co-authored by Shashank Motepalli and Hans-Arno Jocobsen of the University of Toronoto. We quote the original synopsis below: - - - - -Growing excitement around permissionless blockchains is uncovering its latent scalability concerns. Permissioned blockchains offer high transactional throughput and low latencies while compromising decentralization. In the quest for a decentralized, scalable blockchain fabric, i.e., to offer the scalability of permissioned blockchain in a permissionless setting, we present L4L to encourage decentralization over the permissioned Libra network without compromising its sustainability. L4L employs delay towers, -- puzzle towers that leverage verifiable delay functions -- for establishing identity in a permissionless setting. Delay towers cannot be parallelized due to their sequential execution, making them an eco-friendly alternative. We also discuss methodologies to replace validators participating in consensus to promote compliant behavior. Our evaluations found that the cost of enabling decentralization over permissioned networks is almost negligible. Furthermore, delay towers offer an alternative to existing permissionless consensus mechanisms without requiring airdrops or pre-sale of tokens. - - - - -\>\> [View the original article, with download link to full report](https://arxiv.org/abs/2203.09714) diff --git a/docs/archive/econ/a-brief-overview-of-system-policies.md b/docs/archive/econ/a-brief-overview-of-system-policies.md deleted file mode 100644 index b7770b15..00000000 --- a/docs/archive/econ/a-brief-overview-of-system-policies.md +++ /dev/null @@ -1,154 +0,0 @@ -As you can see in our write ups elsewhere, we do things a little differently around here: we had no venture investors, there is no premine, no foundation with tokens, and anyone with a laptop can participate and earn coins. - - -Here's a quick reference to the policies implemented at genesis, with further discussion below. - - -## Rewards - - -* Rewards are paid at the end of each "Epoch", daily at 16:00 UTC. -* The majority of the rewards will go to Validator Nodes, you'll need a cloud host to be successful at this (you can't do this with a laptop, and you need to be somewhat technical). Transaction fees are the principal source of rewards, but they can be augmented by Guaranteed Minimum subsidies. -* End Users (who are not Validator Nodes), can receive an Identity Subsidy for creating durable identities through Delay Towers. This is a system "mining pool". - - -## Requirements - - -* We do not do Proof of Stake, instead preventing Sybil accounts is done through Delay Towers, a sybil resistance technique we invented. -* It uses Proofs of elapsed time which are done by the `tower` app on cloud machines, or the `carpe` desktop all for end users -* Validators are required to build Delay Towers, they must produce 6 delay proofs per day in order to gain admission to the validator set, and also to remain. -* End Users can optionally build Delay Towers to establish a persistent identity (and perhaps later join as a validator), and there is a reward for that. - - -## Validator Rewards - - -* Securing the network is done by a maximum of 100 delegations of "Validator Nodes". This is very valuable work to the network. -* At the start of the network each Validator Node has typically 1 entity or person behind it (a delegation of 1\). -* To become a candidate for a Validator Node, all that is required is to run the configuration tool, and to have any existing Validator in a current validator set send an onboarding transaction. (it's not a vote by the validator set to include a new validator.) While it doesn't take group permission to onboard a new validator, existing validators are rate-limited from creating endless accounts. They can only onboard a new prospective validator every 14 days/epochs. -* The budget for Validator subsidies is "thermostatic", it goes up or down depending on the total number of Validator Nodes doing work successfully. - - - + If the network is about to fail, with only 4 nodes on the network, the budget the network has for security, exactly 8,400,000 coins (the maximum). The 4 nodes share the 8,400,000 coins, 2,100,000 each. - + On the other extreme, when the network is reaching its technical performance limit, there is no reason to subsidize Validators. At 100 Validator nodes, the total budget is 0, and the 100 validators will share the transaction fees the network produces. -* The validator subsidy only exists in the absence of sufficient transaction fees. It is a Guaranteed Minimum, which is net of transaction fees. So hypothetically if the network has 4 nodes, and hence the security budget is 8,400,000, however the total transaction fees are already above this number (e.g. 10,000,000\), there is no need to subsidize the guaranteed minimum, there are no new Coins minted. This prevents unnecessary inflation. - - -## End Users Mining - - -* Anyone with a laptop and with an ordinary account (End Users) can receive coins for creating a Delay Tower (proofs of elapsed time), as a basis for durable identity. We also call this mining. -* At genesis the protocol provides a subsidy for end users building up their identity. The reward pool for all miners is exactly the equivalent of one Validator Node's rewards in a given day. This can be thought of as a single system subsidized "mining pool". -* It is a smaller reward compared to Validator Nodes. So, end users are encouraged to run Validator Nodes or pool together to share rewards of validator nodes. Future mining pools are up to the community to design and create. -* While End User account receive relatively smaller amounts of coins for the Identity Subsidy, their accounts have no restrictions on transferability, - - -## Transferability - - -* There are no restrictions on ordinary 0L accounts (end user accounts). -* There are voluntary restrictions people can place on their account: Slow Wallet and Community Wallet tags. - - -### Slow Wallets - - -* Early participants of a network may receive generous subsidies, but they are prevented from dumping on less sophisticated users, these are Slow Wallets. All validator node accounts, where a majority of rewards flow to must be Slow Wallets. -* At genesis Slow Wallets currently cannot transfer Coins between accounts. At epoch 100, they get 10,000 coins unlocked per epoch (day). - - -### Community Wallets - - -* Community wallets are optional settings which allow greater transparency, and also allow owners of the account to help prevent fraud. This designation of wallet is useful for anyone wishing to set up a program for the community benefit. And it also appoints all addresses in the validator set to be observers of the wallet, and they can slow down transactions by vertoing. With sufficient Vetoes the transaction gets rejected. -* CommunityWallets can only make transfers to Slow Wallets. - - -## Autopay Sponsoring Programs in the Community - - -* Autopay aims to make it trivially easy for early coin holders to send to development programs within the community. At this stage of the network Autopay can only send to wallets tagged CommunityWallets, this is a benefit of being a community wallet. -* At time of writing, there are approx 12 programs that have elected to use CommunityWallets. -* Like most smart contract platforms, the 0L System requires spending of credits (GAS Coins) for running smart contract computations on the system. These resources are allocated according to specific rules encoded in the core logic of the system. - - -# Earning Credits - - -Anyone can earn credits for themselves by performing computational work on the system. No permission is required. - - -The OL network is a marketplace: of sellers of computation (Validators), and buyers of computation (End Users). The marketplace does not receive a fee. Instead the Validators receive the entirety of the Coins earned for the services performed. - - -Since the transaction fees may not be sufficient inducement for a seller of computation to join as a Validator, the network has Guaranteed Minimum Transaction Fee, which is subsidized in certain network conditions. - - -# Guaranteed Minimum Transaction Fee - - -At times when the network is insecure (with very few validators), the transaction fees flowing through the marketplace may not be attractive enough for a prospective seller of compute power to join. - - -The Guaranteed Minimum provides a baseline earnings which the Validator can rely on. A network Subsidy makes up the difference between what actual transactions fees were paid, and what is justifiable as a minimum payment. If the Guaranteed Minimum is 10 Coins given a network condition, but the transaction fees amounted to 3 coins, then the network creates new credits amounting to 7 Coins, and thus pays the total of 10 to the validator. Supposing the minimum guaranteed calculated by the algorithm is instead 1 Coin per validator, and the same 3 coins were due from transaction feed, then the network does not create any new Coins, and pays the 3 coins to the validator (in excess of the 1 Coin the network considered a justifiable minimum). - - -The network's operating software encodes a schedule of the minimal accepted earnings given certain network conditions. The formula is intentionally simple. - - -When there are four validators on the network (near failure) the guaranteed minimum is at its highest. When there are 100 validators on the network, (the transaction throughput is exponentially diminished beyond that amount in BFT networks) the network has excess compute power, and the minimum guaranteed is zero Coins. This means that at 100 validators the validators should expect to earn only the transaction fees flowing through the network. For easy comprehension by prospective validators the schedule is a straight line from 4 to 100 validators. - - -This Auction aims to ensure the network always pays for security when it needs it, but does not overpay when it is not necessary to do so. It will appear generous at times, and miserly at others, but it should attract the necessary users. - - -Note, these allocation rules make some assumptions about BFT, that there is a super majority of honest actors and that the most committed validators are included in the validator set (proof of weight from Delay Towers) - - -# Identity Subsidy - - -0L's identity subsidy sybil resistance mechanism relies on Validators creating Delay Towers which provide a persistent, and non-forgeable identity. - - -It is important for the network to have as many users as possible creating durable identities, i.e producing Delay Towers. It has a number of benefits: allowing users not yet set up as validators to create identities, allows fullnodes to receive some compensation for providing replication services, and allows the VDF delay mechanism to be tested in a wide variety of hardware configurations so that the difficulty can be periodically adjusted. - - -While these activities are useful and deserve a meaningful subsidy, they are also low effort and cannot compete with the earnings to Validators (which are critical). This work is also less useful as the network matures, and has higher security (from Validator participation). Also the identity subsidy is highly gameable, and can lead to exploits by sophisticated users. The economics are designed such that those sophisticated users will be incentivized instead to run Validator nodes. - - -To balance the needs of validators, and exploits possible, miners thus share the equivalent of 1 Validator's Guaranteed Minimum in every epoch. The identity subsidy is an example of a "mining pool", where the end users share the rewards of one validator node. At genesis the protocol is sponsoring this single mining pool. We expect future mining pools to be an emergent property of the network, as end users seek to receive more rewards, from naturally diminishing rewards to the single system mining pool. - - -# Transferring Credits - - -Transfers of credits are unlimited for End User accounts (plain accounts). If an End User is running a "miner" and creating a tower, those credits are freely transferable. - - -There two categories of accounts that have opt-in rules for transfers - - -## Community Wallets - - -These are wallets that have elected to have community oversight. If a person or entity would like to increase the credibility of that wallet (e.g to create a program), they may opt to have the transfers be slowed down or ultimately rejected. More details here: - - -Community wallets typically will receive funds from AutoPay, if anyone wishes to automatically donate a % of their credits. - - -Sending automatic payments is easy. It is also encouraged socially. On the current network Validator Nodes are voluntarily opting into donating on average more than 50% of their rewards. - - -## Slow Wallets - - -Since transferring credits by early users can cause undesirable effects (e.g. creating markets and dumping credits on lesser informed users), the earliest members, and the ones most likely to accumulate large amounts of credits are rate-limited in transferring funds. Transferability also interferes with the ability of the auction for security. - - -The exception is transferring credits to Community Wallets. Those transfers are unlimited. - - -There are accounts that have elected to have restricted transferability. Those are designated Slow Wallets. To join a Validator Set a prospective user must have a Slow Wallet. diff --git a/docusaurus.config.js b/docusaurus.config.js index 94f3b04d..1a7dcb01 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -51,6 +51,9 @@ const config = { 'https://github.com/0LNetworkCommunity/documentation/edit/main/', }, blog: { + blogSidebarTitle: 'All posts', + blogSidebarCount: 'ALL', + onInlineAuthors: 'ignore', showReadingTime: true, editUrl: 'https://github.com/0LNetworkCommunity/documentation/edit/main/blog/'}, theme: {