diff --git a/blog/2024-09-03-building-tomorrow-juno-build-dao-for-the-future/index.mdx b/blog/2024-09-03-building-tomorrow-juno-build-dao-for-the-future/index.mdx index 3b5af961..0305bd67 100644 --- a/blog/2024-09-03-building-tomorrow-juno-build-dao-for-the-future/index.mdx +++ b/blog/2024-09-03-building-tomorrow-juno-build-dao-for-the-future/index.mdx @@ -38,6 +38,12 @@ import NewsletterForm from "@site/src/components/NewsletterForm"; ## 2. Get Informed +:::note + +The white paper has been updated to continue presenting the vision; however, the tokenomics aspect has been notably removed, as it is no longer relevant following the failure of the SNS DAO. + +::: + I’ve put together a [white paper](/docs/white-paper/intro) that outlines the reasoning and vision I have for a Juno Build DAO. I highly recommend giving it a read to fully understand what I’m aiming to achieve. If you have any questions, feel free to reach out on [Discord](https://discord.gg/wHZ57Z2RAG), [Twitter/X](https://x.com/junobuild), [OpenChat](https://oc.app/community/vxgpi-nqaaa-aaaar-ar4lq-cai/?ref=xanzv-uaaaa-aaaaf-aneba-cai) or also the [DFINITY forum](https://forum.dfinity.org/t/upcoming-juno-build-sns-decentralization-swap/34719) (as requested per their guidelines). diff --git a/docs/img/token-distribution.webp b/docs/img/token-distribution.webp deleted file mode 100644 index 171dd9fa..00000000 Binary files a/docs/img/token-distribution.webp and /dev/null differ diff --git a/docs/img/voting-power.webp b/docs/img/voting-power.webp deleted file mode 100644 index 05f82df8..00000000 Binary files a/docs/img/voting-power.webp and /dev/null differ diff --git a/docs/white-paper/conclusion.md b/docs/white-paper/conclusion.md index 76e3c70e..e37d413d 100644 --- a/docs/white-paper/conclusion.md +++ b/docs/white-paper/conclusion.md @@ -2,7 +2,7 @@ While I may be biased, I genuinely believe that Juno represents a significant step forward in the realm of decentralized development. I'm well aware that it does not yet cover all the features provided by Web2 services or the capabilities of standard Web3 solutions, but Juno's features and unique selling proposition are undeniably promising. Despite not having reached a significant market share yet, and with future scalability uncertain, Juno's potential is evident to me. -As for establishing a DAO, this step is crucial for continuing the journey. It would be paradoxical to promote full control for developers while keeping ownership of the ecosystem centralized. The DAO will ensure that Juno's growth, security, and transparency are maintained through community-driven governance. +Establishing a DAO is an essential step that Juno should consider taking someday. Promoting full control for developers while retaining centralized ownership would be paradoxical. When the time comes, a DAO will ensure that Juno’s growth, security, and transparency are upheld through community-driven governance. I hope you enjoyed the read! diff --git a/docs/white-paper/contributors.md b/docs/white-paper/contributors.md deleted file mode 100644 index 8406e809..00000000 --- a/docs/white-paper/contributors.md +++ /dev/null @@ -1,25 +0,0 @@ -# Contributors - -I developed and bootstrapped Juno. A few tasks, such as the design of the UI and logo, were outsourced to freelancers within my network. - -I have been a freelance web developer since 2018. I hold an engineering degree in Computer Science and an Executive Master of Business Administration (EMBA). In addition to development, I have also served as a project manager and business analyst . Notably, I was previously the Vice Director at the leading company providing ERP solutions for the Swiss company registry. - -In the future, I am committed to remaining the principal contributor to Juno, ensuring its continuous development and improvement. - -In addition, as the DAO grows, the team will expand to include additional developers to achieve the ambitious goals outlined in the roadmap, as well as a developer evangelist to foster further growth and engagement. - -That said, I am going to commit to the project only if the DAO succeeds. If it doesn't, Juno will enter maintenance mode, where I will stop developing new features and ultimately deprecate it. - -I've been developing Juno as a side project for some time now and I feel like I've reached a crossroads where it either becomes a true initiative developed by a group of contributors, or I just find a new hobby. In addition, unlike building with Juno, developing Web3 without it requires significant energy. Therefore, sunsetting it would likely also mean that I might take a break from developing any personal projects for some time. - -In short, to me, it's either Juno DAO or no Juno. - -:::info[Links] - -https://daviddalbusco.com - -https://x.com/daviddalbusco - -https://github.com/peterpeterparker - -::: diff --git a/docs/white-paper/intro.mdx b/docs/white-paper/intro.mdx index 2cf3c757..38ad190d 100644 --- a/docs/white-paper/intro.mdx +++ b/docs/white-paper/intro.mdx @@ -1,20 +1,12 @@ # Introduction -The Juno White Paper offers an in-depth exploration of the vision, architecture, and technological foundation that powers the platform. Designed for developers, architects, and decision-makers, this document outlines the key principles driving its innovation and presents a comprehensive proposal for transforming the Juno ecosystem into a decentralized autonomous organization (DAO). Additionally, the white paper covers the business model and tokenomics that will support this transition. +The Juno White Paper offers an in-depth exploration of the vision, architecture, and technological foundation that powers the platform. Designed for developers, architects, and decision-makers, this document outlines the key principles driving its innovation and presents a comprehensive proposal for eventually transforming the Juno ecosystem into a decentralized autonomous organization (DAO) Have fun reading. -:::warning - -The ICO on the Internet Computer failed on Saturday, October 12, 2024. The white paper has not yet been updated to reflect this failure. - -::: - :::note -For your convenience, the white paper is also available for download as a PDF. - -Version: 1.2.1 /// Last update: October, 2024 +Version: 1.3.0 /// Last update: October, 2024 ::: diff --git a/docs/white-paper/legal-umbrella.md b/docs/white-paper/legal-umbrella.md deleted file mode 100644 index 45592946..00000000 --- a/docs/white-paper/legal-umbrella.md +++ /dev/null @@ -1,13 +0,0 @@ -# Legal Umbrella - -To ensure Juno Build operates within a legally sound framework, I am considering two potential jurisdictions for incorporation, which would need to be discussed if the creation of the DAO succeeds. - -As a Swiss citizen, I recognize certain advantages in incorporating in Switzerland. Despite occasional concerns with the outcomes of certain votes, unfortunately influenced sometimes by far right-wing parties, I generally have faith in our direct political system. Additionally, the government and economy are generally stable. The implementation of new laws is also often relatively slow, providing time to anticipate regulatory changes. However, integrating in Switzerland may prove complex, costly, and could present certain challenges. - -For this reason, I am also considering the Marshall Islands as an alternative. This jurisdiction offers an advanced legal environment specifically tailored to the needs of DAOs. Incorporating in the Marshall Islands would also allow Juno Build to obtain corporate personhood, enabling the execution of business operations, signing of contracts, and other off-chain activities. - -This incorporation model would be strategically chosen to mitigate liability risks for projects and their investors. Under this structure, Juno Build DAO would be recognized as a DAO LLC, providing a legal buffer that protects against personal liability. Importantly, this setup would support operational flexibility, recognizing blockchain operations and smart contract governance as legitimate under its laws. - -Additionally, the Marshall Islands' legal framework would permit members holding less than a 25% share to maintain anonymity, eliminating the need for KYC procedures for these participants. - -In either case, Juno Build will require the necessary legal infrastructure to support its innovative approach to product development while maintaining legal compliance and operational efficiency. diff --git a/docs/white-paper/roadmap.mdx b/docs/white-paper/roadmap.mdx index eb5a2076..33d7ecb8 100644 --- a/docs/white-paper/roadmap.mdx +++ b/docs/white-paper/roadmap.mdx @@ -84,4 +84,4 @@ To date, and as a side note, these are the key features that have been successfu - Project Scaffolding Templates (Apr. 2024) -- Regions / Subnets Selection (Oct. 2024) \ No newline at end of file +- Regions / Subnets Selection (Oct. 2024) diff --git a/docs/white-paper/tokenomics/_category.json b/docs/white-paper/tokenomics/_category.json deleted file mode 100644 index 841c7a1b..00000000 --- a/docs/white-paper/tokenomics/_category.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "label": "Tokenomics", - "position": 16, - "link": { - "type": "generated-index", - "description": "Juno will launch a standard ICRC token, known as Juno Build token (JUNOBUILD), at the creation of the DAO through a Service Nervous System (SNS)." - } -} diff --git a/docs/white-paper/tokenomics/initial-sns-configuration.md b/docs/white-paper/tokenomics/initial-sns-configuration.md deleted file mode 100644 index f6a23b0c..00000000 --- a/docs/white-paper/tokenomics/initial-sns-configuration.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -sidebar_position: 6 ---- - -# Initial SNS Configuration - -The SNS will initially be configured with the values shown in the tables below which can all subsequently be changed by proposal. - -| Description | Value | -| ---------------------------------------------------------------------- | -------- | -| Transaction fee in JUNOBUILD tokens paid for ledger transfers | 0.01 | -| Number of JUNOBUILD tokens that rejected proposals cost the proposer | 10 | -| Minimum number of JUNOBUILD tokens that can be staked in a neuron | 100 | -| Initial voting period for a proposal | 3 days | -| Minimum neuron dissolve delay to vote | 6 months | -| Maximum neuron dissolve delay | 3 years | -| Maximum dissolve delay bonus | 75% | -| Maximum age for age bonus | 3 years | -| Maximum age bonus | 25% | -| Percentage of total supply that will be generated annually for rewards | 1.5% | diff --git a/docs/white-paper/tokenomics/outgoings.md b/docs/white-paper/tokenomics/outgoings.md deleted file mode 100644 index 11114d1d..00000000 --- a/docs/white-paper/tokenomics/outgoings.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -sidebar_position: 2 ---- - -# Outgoings - -The DAO will have various financial outflows for covering Juno's smart contract costs (such as running cycles and onboarding new developers), potential third-party services usage, audit, core team and operational expenses through grant programs. Additionally, JUNOBUILD token may be employed to reward contributions through bounties. - -We can expect those outgoings to be allocated as following: - -**1. Developers** (60%): This portion will be dedicated to compensating the core developers and the developer evangelist ensuring achieving the goal of the roadmap while fostering growth as well. - -**2. Marketing and Design** (15%): It will be allocated to engage consultants for various roles and tasks regarding marketing and design. - -**3. Marketing and Community Building** (5%): A modest portion of costs will support ongoing marketing efforts. This includes events aimed at attracting more developers and users to the platform. The relatively low allocation reflects a preference for genuine engagement over traditional advertising. - -**4. Operational Costs** (20%): This allocation will cover essential operational expenses, such as legal, accounting, and administrative costs. - -While it is challenging to predict when the DAO will incur more incomings than outgoings, we ideally aim to achieve a break-even point within three years. Initially, the DAO will incur more outgoings than incomings. diff --git a/docs/white-paper/tokenomics/purpose.md b/docs/white-paper/tokenomics/purpose.md deleted file mode 100644 index fcc4a883..00000000 --- a/docs/white-paper/tokenomics/purpose.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -sidebar_position: 1 -title: Purpose ---- - -# Purpose of the Token - -The Juno Build token will serve three purposes: governance, utility, and rewards. - -## Governance - -The governance token empowers developers and stakeholders to gain voting power by staking Juno Build tokens, which is a pivotal and central aspect of this project. As Juno operates as a blockchainless provider, it grants developers full control over their projects. This means that shipping new releases and providing services requires not only absolute trust but also complete transparency, the essence of Web3. Therefore, it is essential, in my opinion, that Juno becomes a DAO to ensure that what is built and delivered is validated by the community, developers and stakeholders, which is crucial for maintaining the trust, ensuring security, and quality. - -## Utility Token - -The Juno Build token will have multiple utilities within the ecosystem. These utilities will benefit both Juno and the developers: - -For Juno: - -1. **Transactions and Subscriptions:** The token can be used for payment of transactions and subscriptions for features provided by Juno, benefiting from a better price compared to transactions executed with other tokens. - -2. **Swapping for Computation Power:** The token can be swapped to acquire computation power, effectively converting it to cycles or other infrastructure fees. - -For Developers: - -3. **Integrated Payments:** Developers will be able to integrate payment features into their projects and dApps, linked with their wallets on Juno (Mission Control). This allows developers to manage a single wallet that earns revenue. - -4. **Clients Transactions:** Similar to payments, developers will also be able to earn for commissioned work or maintenance. For example, if a developer builds a dApp for a client, they can earn payments directly to their wallet on Juno. - -5. **Marketplace Transactions:** The future marketplace for developers will enable them to offer features and services to others. These transactions will be conducted using the Juno Build token. - -## Rewards - -The Juno Build token will act as a reward mechanism. Those who hold staked tokens will be eligible to receive tokens as rewards on a regular basis. diff --git a/docs/white-paper/tokenomics/sns-swap-configuration.mdx b/docs/white-paper/tokenomics/sns-swap-configuration.mdx deleted file mode 100644 index 48f2ab7e..00000000 --- a/docs/white-paper/tokenomics/sns-swap-configuration.mdx +++ /dev/null @@ -1,18 +0,0 @@ ---- -sidebar_position: 7 ---- - -# SNS Swap Configuration - -The SNS swap will be configured with the values shown below. - -| Description | Value | -| --------------------------------------------------------------------------- | ----------------------------- | -| Total number of JUNOBUILD tokens to be sold in the SNS Swap | 30,000,000 | -| Minimum ICP to be raised (otherwise sale fails and ICP returned) | 200,000 | -| Maximum ICP to be raised | 350,000 | -| Estimated ICP to come from the Neuron Fund at a 5.80 XDR conversion rate | Min: 127,526
Max: 129,310 | -| End date of sale (unless maximum ICP raised sooner) | Oct 12, 2024
3:00 PM | -| Minimum number of sale participants (otherwise sale fails and ICP returned) | 100 | -| Minimum ICP per buyer | 1 | -| Maximum ICP per buyer | 200,000 | diff --git a/docs/white-paper/tokenomics/token-distribution.md b/docs/white-paper/tokenomics/token-distribution.md deleted file mode 100644 index 135b41a1..00000000 --- a/docs/white-paper/tokenomics/token-distribution.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -sidebar_position: 4 ---- - -# Token Distribution - -The JUNOBUILD tokens will be allocated at Genesis as following: - -![A pie chart of the JUNOBUILD tokens allocation at Genesis](../../img/token-distribution.webp) - -:::note - -The percentages presented in chapter were calculated using the [SNS Tokenomics Analyzer](https://dashboard.internetcomputer.org/sns/tokenomics) on August 29, 2024. - -::: - -## SNS Swap - -To promote decentralized governance and secure funding for the SNS, 30% of the total JUNOBUILD supply will be allocated for a swap. Participants in this SNS Swap, including the Neuron Fund, will receive their tokens as part of a diversified portfolio. This portfolio comprises five equal-value neurons, each with staggered dissolve delays of 0, 6, 12, 18, and 24 months, respectively. This structured approach ensures a balanced distribution and fosters long-term commitment among participants. - -## Treasury - -Following the successful completion of the SNS swap, the Juno Build SNS-DAO treasury will hold an estimated 50 million JUNOBUILD tokens alongside the ICP accumulated during the swap. - -The deployment of any funds in the treasury will be strictly governed by DAO-approved proposals. - -Subsequent to the SNS swap, the Juno contributors core team plans to propose the allocation of approximately 2% of the JUNOBUILD tokens and corresponding ICP tokens from the treasury to the DEXs, initiating the trading of the JUNOBUILD token. - -## Team - -I will receive tokens in the form of a basket of five equal-value neurons. These neurons will have different dissolve delays and vesting periods of one year or more. - -Neurons with a “vesting period” remain untouchable until the designated period concludes, and no alteration can be made to the dissolve delay. - -| Index | Stake | Dissolve Delay | Vesting Period | -| ----- | --------- | -------------- | -------------- | -| 0 | 4,000,000 | 6 months | 1 year | -| 1 | 4,000,000 | 9 months | 1.5 years | -| 2 | 4,000,000 | 1 year | 2 years | -| 3 | 4,000,000 | 1.5 years | 3 years | -| 4 | 4,000,000 | 2 years | 5 years | diff --git a/docs/white-paper/tokenomics/total-supply.md b/docs/white-paper/tokenomics/total-supply.md deleted file mode 100644 index 6636b3b7..00000000 --- a/docs/white-paper/tokenomics/total-supply.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -sidebar_position: 3 ---- - -# Total Supply - -The total supply of JUNOBUILD tokens at genesis is 100 million. Over time, the supply will increase if more tokens are minted and decrease if tokens are burned. - -The SNS is designed to generate 1.5% of the total supply annually to distribute voting rewards to participating neurons. - -The SNS can burn tokens through proposals, by applying transaction fees, and potentially by adding a small percentage to the price of computer power purchases. diff --git a/docs/white-paper/tokenomics/voting-power.md b/docs/white-paper/tokenomics/voting-power.md deleted file mode 100644 index 65b32419..00000000 --- a/docs/white-paper/tokenomics/voting-power.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -sidebar_position: 5 ---- - -# Voting Power - -To participate in the governance of the Juno Build DAO, a neuron will have to possess a minimum dissolve delay of 6 months to be eligible to vote. This duration aligns with the roadmap shared in this white paper and could be reviewed in the future. - -The SNS voting power distribution at genesis will have the following proportions for direct participants, the Neurons' Fund, and developer neurons: - -![A pie chart representing the voting power](../../img/voting-power.webp) - -:::note - -The percentages presented in chapter were calculated using the [SNS Tokenomics Analyzer](https://dashboard.internetcomputer.org/sns/tokenomics) on August 29, 2024. - -::: diff --git a/juno.config.ts b/juno.config.ts index f6f54bb7..fd6a6649 100644 --- a/juno.config.ts +++ b/juno.config.ts @@ -88,6 +88,22 @@ const redirects: StorageConfigRedirect[] = [ "/assets/files/juno-white-paper-47063bc5d28d71fe7534bfa249ce3f14.pdf", location: "/files/juno-white-paper.pdf", code: 301 + }, + // Pages redirected after SNS DAO failure. + { + source: "/files/juno-white-paper.pdf", + location: "/docs/white-paper/intro", + code: 301 + }, + { + source: "/docs/white-paper/tokenomics/**/*", + location: "/docs/white-paper/intro", + code: 301 + }, + { + source: "/docs/white-paper/legal-umbrella", + location: "/docs/white-paper/intro", + code: 301 } ]; diff --git a/sidebars.ts b/sidebars.ts index 4ee0290d..27aa85d2 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -81,23 +81,6 @@ const sidebars: SidebarsConfig = { "white-paper/validation", "white-paper/target-audience", "white-paper/market-size", - "white-paper/contributors", - { - type: "category", - label: "Tokenomics", - link: { - type: "generated-index", - description: - "Juno will launch a standard ICRC token, known as Juno Build token (JUNOBUILD), at the creation of the DAO through a Service Nervous System (SNS)." - }, - items: [ - { - type: "autogenerated", - dirName: "white-paper/tokenomics" - } - ] - }, - "white-paper/legal-umbrella", "white-paper/conclusion" ] }; diff --git a/static/files/juno-white-paper.pdf b/static/files/juno-white-paper.pdf deleted file mode 100644 index 74c4b875..00000000 Binary files a/static/files/juno-white-paper.pdf and /dev/null differ