diff --git a/docs/faq/lukso.md b/docs/faq/lukso.md deleted file mode 100644 index f0585aec54..0000000000 --- a/docs/faq/lukso.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: LUKSO -description: LUKSO Frequently Asked Questions -sidebar_position: 1 ---- - -# Frequently Asked Questions - -## What is LUKSO? - -[LUKSO](https://lukso.network/) is a Blockchain network dedicated to existing and coming digital lifestyle use cases. It will be running with a Casper consensus algorithm (PoS) combined with an [Ethereum Virtual Machine](https://medium.com/mycrypto/the-ethereum-virtual-machine-how-does-it-work-9abac2b7c9e) (EVM) execution engine. - -## What is LYXe and LYX? - -LYX is the native cryptocurrency of the LUKSO Blockchain and is required to secure this decentralized infrastructure. It is used to pay for transaction fees and needs to be locked (staking) to participate in the block production. - -"[LYXe](https://etherscan.io/token/0xA8b919680258d369114910511cc87595aec0be6D)" is LYX on the Ethereum Blockchain and is the token that the [Reversible ICO](https://rico.lukso.network) returned. - -Once the [LUKSO mainnet](../networks/mainnet/running-a-node.md) starts, there will be a migration of LYXe to LYX on the LUKSO Blockchain. Both LYXe and LYX represent the same asset but on different Blockchain networks. - -## Why a new network for LUKSO and why an L1 ? - -LUKSO is dedicated to constructing standards that significantly enhance the user experience of blockchain technology, thus facilitating its widespread adoption. To realize this vision, it's essential to establish a fresh network from the ground up. This approach allows early users to experience the ease of use and simplicity brought about by UniversalProfiles and the new standards introduced by LUKSO. - -Creating a new network also provides an environment to test and demonstrate the potential of these standards free from the constraints of older standards and tools used on existing networks. It offers a space to evolve and refine these new concepts without hindrance. - -As for why LUKSO is a Layer 1 (L1) network, this choice is rooted in the current state of Layer 2 (L2) technologies. While L2 solutions are promising for scaling blockchain systems, they are still heavily under development and their security largely depends on the underlying L1 they are built upon. L1 networks, on the other hand, offer greater security as they are not reliant on another layer. Therefore, to ensure a robust, secure foundation for its innovative standards and user-focused features, LUKSO has opted to build as a Layer 1 network. - -## Are transactions on lukso cheaper than other blockchains? - -Transactions are usually cheaper on new blockchain networks due to the reduced competition for block space. Essentially, every block on a blockchain has a finite capacity for transactions. If the demand for transactions surpasses this capacity, users must compete for the limited space. This competition often manifests as transaction fees - the higher the fee you're willing to pay, the more likely your transaction will make it into the next block. - -On established networks like Bitcoin or Ethereum, where the demand for block space is significant, transaction fees can be quite steep. However, on newer networks, fewer users equate to less competition, and hence, lower transaction fees. - -Nevertheless, over time, as a network attracts more users and demand for block space rises, transaction fees are likely to increase. It's here where solutions like relay services come into play, which can notably improve this situation. These services can abstract the gas fees from the user, potentially enabling limited free transactions based on their business model. - -Furthermore, these relay services can develop a mechanism that allows for the distribution of relay call executions, strategically waiting for times when gas fees are low. This way, relay services can optimize transaction costs while maintaining a smooth user experience. - -## Can people use Metamask and other wallets on LUKSO ? - -Yes, people can use Metamask and other Ethereum-compatible wallets with LUKSO. This is due to LUKSO being designed as an Ethereum 2.0-like chain, and it maintains compatibility with the Ethereum Virtual Machine (EVM). Metamask, along with many other wallets, were originally created for the Ethereum blockchain and are thus EVM-compatible. This allows them to interact with any blockchain that also supports EVM, which includes LUKSO. - -However, while using Metamask and other Ethereum wallets can allow basic interactions with the LUKSO network, it's suggested that for the best and most comprehensive experience on the LUKSO blockchain, you use the UniversalProfile's browser extension. This extension is specifically designed to allow full control of your unique digital identity or 'profile' on the LUKSO network, offering a more integrated and feature-rich experience. - -## How can an NFT be updatable on lukso - -On the LUKSO network, NFTs can be made updatable through the use of certain standards, specifically the LSP8 standard. While the underlying technology of the LUKSO network is similar to that of Ethereum, it differentiates itself through the use of advanced standards. - -The commonly used NFT standards on Ethereum, ERC721 and ERC1155, do not fully support updatable metadata for NFTs. This is a limitation that LUKSO's LSP8 standard seeks to address. - -The LSP8 standard introduces a standardized key-value store, which allows for metadata to be stored and updated across time. This makes NFTs on the LUKSO network dynamic, as their information can be altered after they are minted. For more detailed information on how this is achieved, please refer to the [LSP8](../standards/nft-2.0/LSP8-Identifiable-Digital-Asset.md) documentation. - -## How can I create a phygital on LUKSO? - -Creating a 'phygital' on LUKSO, a hybrid between a physical and a digital asset, involves the use of LUKSO's LSP7 and LSP8 token standards. These standards offer a flexible and updatable data key-value store, enabling a digital asset on the blockchain to carry and update relevant information related to its physical counterpart. - -In practice, a phygital asset would have a digital representation on the blockchain using the LSP7 or LSP8 standards. This allows it to link and dynamically update information on-chain that pertains to the physical aspect of the asset. - -## How to stay up to date about LUKSO? - -You can follow us on [Twitter](https://twitter.com/lukso_io), read our [Medium articles](https://medium.com/lukso) and follow the announcements on our [Discord](https://discord.gg/lukso) server. - -## Where can I download the Whitepaper? - -Here you can find the download link for the [LUKSO Whitepaper](https://uploads-ssl.webflow.com/629f44560745074760731ba4/62b200bfe0af12186845519a_LUKSO_Whitepaper_V1-1.pdf). - -## I am a developer. Where do I start? - -If you are a developer and want to use the future LUKSO Blockchain, you can already start building using our [Public Testnet](../networks/testnet/parameters.md) and read our [developer's guides](../guides/universal-profile/create-profile). - -Please join our [Discord](https://discord.gg/lukso) and get in touch if you have terrific ideas for the new digital lifestyle economy! - -## I found a bug. Where can I report it? - -You can create a GitHub issue in the related project's repository. If you can't do it, you can send us a message on our [Discord](https://discord.gg/lukso) server. diff --git a/docs/faq/lukso/_category_.yml b/docs/faq/lukso/_category_.yml new file mode 100644 index 0000000000..02b6ada9ce --- /dev/null +++ b/docs/faq/lukso/_category_.yml @@ -0,0 +1,3 @@ +label: '🆙 LUKSO' +collapsed: false +position: 1 diff --git a/docs/faq/lukso/feature-requests.md b/docs/faq/lukso/feature-requests.md new file mode 100644 index 0000000000..4e35ff5f2f --- /dev/null +++ b/docs/faq/lukso/feature-requests.md @@ -0,0 +1,42 @@ +--- +sidebar_label: 'Feature Requests' +sidebar_position: 3 +--- + +# Feature Requests + +### Will there be video guides about LSPs? + +Yes, LUKSO is planning to create videos for LSPs both on the theoretical and practical end. They will be released after the mainnet process, and the LSP development is finalized with audits and grant programs. + +### Will there be re-occurring developer events? + +Yes, developer meetings and events are planned to present our monthly tech progress and move into a more transparent development process. You can now find and discuss weekly tech updates within the official [LUKSO Discord](https://discord.gg/lukso) server. + +### Will there be another LUKSO Hackathon? + +Yes, we’re planning and preparing future hackathon projects. For official announcements, please follow our [LUKSO Twitter](https://twitter.com/lukso_io) account. You can already have a look into the developer channels on our [LUKSO Discord](https://discord.gg/lukso) in order to find teammates or project ideas. + +### Is there going to be a grants program? + +Yes, We're preparing to launch the grant program after the mainnet migration process is fully finalized. As you can see in the [LYX distribution](https://medium.com/lukso/the-lyxe-migration-process-374053e5ddf5), there are reserves and the foundation's treasury to support grants and drive the development of the network. + +### Will there be DappNode or Avado Support for LUKSO? + +We are collaborating with the [DappNode](https://dappnode.com/) team to provide official support for the LUKSO blockchain. The support will likely be available within the launch process. However, we do not have information about potential other node providers adding support. + +### Will there be a Ledger integration for LUKSO? + +You can use your [Ledger](https://www.ledger.com/de) to store LYXe and LYX already using the Ethereum application. Before the mainnet launch process is not fully completed, there are no active approaches to adding official integrations to hardware wallets. Please note that it is not within our sole control, as external wallet providers decide which blockchains to add. + +### Will LUKSO be listed on additional exchanges? + +Other exchanges than [KuCoin](https://www.kucoin.com/de) and [GateIO](https://www.gate.io/) may join and list LUKSO, but this is not under our sole control. While the network grows adoption by finalizing the mainnet launch process and enabling regular validators to join the network, there will be more interest in external services to support our blockchain. + +### Is it planned to have a video guide about setting up a node? + +Setting up a node exceeds the network configurations and LUKSO CLI. Complete node setups depend on many influences, such as the operating system, security measures, server location, network configurations, and hardware. Due to the various configurations, we cannot issue a standardized guide. However, you can check the [Community Guides](https://docs.luksoverse.io/) by Luksoverse or join the [ETHStaker](https://discord.com/invite/ucsTcA2wTq) Community Discord to get comprehensive knowledge about running a node for EVM networks. + +### Will there be a Mobile Application for Universal Profiles? + +Yes, LUKSO is actively developing a mobile addition to the browser extension, letting you interact with your Universal Profiles on the go. There is no strict release date planned, but we aligned the development of the Mobile and Browser Extension in order to be able to quickly implement features on both sides. diff --git a/docs/faq/lukso/general-information.md b/docs/faq/lukso/general-information.md new file mode 100644 index 0000000000..2638b7a2b5 --- /dev/null +++ b/docs/faq/lukso/general-information.md @@ -0,0 +1,42 @@ +--- +sidebar_label: 'General Information' +sidebar_position: 1 +--- + +# General Information + +### What is the LUKSO Network? + +LUKSO is a Layer-1 blockchain network dedicated to existing and coming digital lifestyles and creative use cases. It is built on the EVM framework and compatible with all other platforms or protocols built on Ethereum. + +### Will LUKSO be the main platform to integrate LSPs? + +The LUKSO blockchain will be the first mover for LUKSO Standard Proposals. In conjunction with the surrounding ecosystem, Universal Profiles greatly enhance the interaction and convenience of managing LSPs. This advantage stems from the **seamless integration of Universal Profiles**. With a dedicated network like LUKSO, we can implement well-thought-out, upgradable standards directly from the start. This clean-cut approach allows us to bypass the challenges of retrofitting standards into an existing system. + +### Who defined the LUKSO token supply? + +The genesis validators of LUKSO collectively determined the token distribution of 42M LYX by voting for it while depositing LYXe, after 3 different options were given by LUKSO. After the [Genesis Validator Contract](https://etherscan.io/address/0x42000421dd80D1e90E56E87e6eE18D7770b9F8cC#code) was closed, the network started with the related genesis files. + +### Why did LUKSO launch as Layer-1 Blockchain? + +LUKSO is an L1 blockchain designed to provide **distinct security, interoperability, and adaptability advantages**, creating a network effect that supports a newly independent economy without compromising its key aspects. + +LUKSO is dedicated to constructing standards that **significantly enhance the user experience of blockchain** technology. However, the full potential of Universal Profiles can't be realized if only a fraction of the network is onboarded through it. Interactions between profiles bring substantial value, and making Universal Profiles the initial accounts through which users are joining guarantees easy usability and upgradability for everyone. Creating a new network offers a space to **evolve and refine** these new concepts **without the hindrance of constraints** from current landscapes and without the obligation of being fully backward compatible. + +LUKSO also wants to ensure **smooth user onboarding** and subsidize early adopters using Universal Profiles. Creating a network effect of convenience through subsidization would not have been sufficient on existing Layer-1 blockchains due to high gas costs or Universal Profiles being a smaller subset of deployed accounts. + +Despite L2 solutions offering lower costs, they often suffer from interoperability issues, governance concerns, and the need for rolling back data to the main network, **risking the siloing of assets and profiles**. Depending on the rollup type, different sacrifices like calculation, smart contract execution, or finality time have to be made on top. + +Rollups, while providing scalability, present their challenges. They are only as secure as the speed at which assets can be exited to the main chain. Moreover, **not every protocol or activity** implemented on the rollup **can be exited**, as not everything is an asset. This limits their applicability and functionality for new account systems. + +While standalone applications might not see the necessity of having their own Layer-1 network, LUKSO provides a **distinct realm for a new** core blockchain **account ecosystem**, necessarily needing the robust and secure foundation to utilize its full potential. + +### What's the token distribution of LUKSO? + +Please look at our official [Network Migration](https://etherscan.io/address/0x42000421dd80D1e90E56E87e6eE18D7770b9F8cC#code) article to see the distribution amounts and listing of the final supply. Previous distributions have been outlaid in our [Genesis Validator](https://medium.com/lukso/its-happening-the-genesis-validators-are-coming-ce5e07935df6) announcement. + +### What's the difference between LYXt, LYXe, and LYX? + +- **LYXt** is the currency for developers used on our official LUKSO Testnet without monetary value. LYXt can be required for free using the [Testnet Faucet](https://faucet.testnet.lukso.network/). The Testnet is maintained by a set of whitepisted node operators to ensure stability. +- **LYXe** is the representation of LYX on the Ethereum Blockchain, used to start off the LUKSO Mainnet in a distributed way. It was created in 2020 during the [rICO](https://medium.com/lukso/re-launching-the-reversible-ico-5289989ce7ed) of LUKSO and started as main token before the mainnet was released. +- **LYX** is the official coin of the LUKSO Blockchain, similar to ETH on Ethereum. People that acquired LYXe before the mainnet launch can migrate their LYXe to LYX using the [LUKSO Migration Bridge](https://migrate.lukso.network/). diff --git a/docs/faq/lukso/project-differentiation.md b/docs/faq/lukso/project-differentiation.md new file mode 100644 index 0000000000..703f4e5faf --- /dev/null +++ b/docs/faq/lukso/project-differentiation.md @@ -0,0 +1,52 @@ +--- +sidebar_label: 'Project Differentiation' +sidebar_position: 2 +--- + +# Project Differentiation + +### How does Universal Profile differ from ENS? + +The [Ethereum Name Service](https://docs.ens.domains/) (ENS) and Universal Profiles serve different purposes but can complement each other in the blockchain ecosystem. While they might look similar from the outside, they **differ in their tech stack and target**. + +ENS is a **naming system** for accounts on the Ethereum blockchain. It functions similarly to the internet's domain name system (DNS), enabling users to replace long, complex blockchain addresses with verifiable human-friendly names. Name services make it easier for users to send transactions and interact with smart contracts without remembering their account addresses. Users can even add additional information, such as social media links, email addresses, keywords, or profile pictures. + +Universal Profiles, on the other hand, are **accounts acting as the center for your persona and blockchain interactions**. They can have extensive and upgradable data records directly on them while also being able to interact with on-chain applications, just as regular wallets. In comparison to ENS, the information is stored and maintained by a global registry service. + +While name services are convenient for transferring assets, they are **not as fitting to maintain an on-chain persona**. The domains can not be secured with multiple keys, have limited attachable information, and require payments to keep your domain names. If the subscription expires, all historical transactions no longer bear this name, meaning **users would lose their** verifiable information and **reputation** connected to the name. Anyone else could rebuy the domain and assume the identity associated with it. Universal Profiles can tackle such concerns, as they have convenience features such as **permission management and rotatable keys**. However, Universal Profiles are accounts and have regular blockchain addresses. + +In this regard, name services and Universal Profiles could work together to enable the ultimate convenience: having both extensive account features and a connected domain to them. + +### How do Universal Profiles differ from LENS Profiles? + +LENS is a **governed social media protocol** within which profiles are managed as NFTs. Where these NFTs can be used underneath many social applications, the asset-bound approach inherently ties them to the protocol, leveraging the functionality specific to the underlying EOA wallet. Basic blockchain accounts only have one static seed phrase and can’t store information, so the overall functionality is limited. + +Universal Profiles, conversely, are **generic smart contract accounts** not tied to any use case that can have public data natively. They can interact directly with on-chain applications such as regular wallets. Still, it features permission and asset management, updatable profile information, and lets you interact as one persona through different EOA keys. + +Here, the operational approach differs from LUKSO. If the idea of LENS is drawn further, many protocols or applications would have **separated profile data** like we currently have with Web 2.0 accounts. LUKSO approaches a **universal framework** where a profile is a standalone account to open up the capabilities of blockchains and move beyond the current limitations. + +### How do Universal Profiles differ from ERC4337? + +Account Abstraction, outlined in ERC4337, standardizes how the **body of future blockchain accounts** should be set up and what **transaction flow** they follow to improve security and scalability. With the standardization, not only is the account itself decoupled from the signing, making keys exchangeable, but an attempt is made to integrate these accounts natively into the EVM protocol, making EOAs obsolete. The standard features a new transaction type and pool, bundling of network interactions, key rotation, and the payment of transaction fees using tokens. However, it mainly defines **how the core account manages the execution of transaction calls**, not a fully-fledged-out account system! Beyond that frame, extended identity or persona schemes could be created on top. + +LUKSO is coming from the opposite, user-focused perspective. Universal Profiles already are **extensible accounts** that can be full of information, have a permission control system, can be notified on transfers to create consent, and even come with many features for assets and vaults. LUKSO achieves the functionality by having **state-of-the-art contract-based accounts**, using EOAs as controller keys on their back. + +While Account Abstraction might be a proper fundament for future EVM blockchain accounts, Universal Profiles **already define the full-on account ecosystem**. LUKSO ensured that Universal Profiles will be compatible with Account Abstraction under the hood. After the standard is finalized or integrated within the protocol, LUKSO **could adopt its functionality** into Universal Profiles for further optimization. Because of their modular and upgradable nature, these updates could even be done after the profiles were deployed. + +Both projects relieve each other by finding new standardizations on different ends. Nevertheless, they could go hand-in-hand. + +### How could Universal Profiles relate on DIDs and VCs? + +Decentralized Identifiers ([DIDs](https://www.w3.org/TR/did-core/#abstract)) and Verifiable Credentials ([VCs](https://www.w3.org/TR/vc-data-model/)) are game-changers for identity and account management in Web3 for managing claims about an entity or persona. DIDs and VCs offer flexibility in implementation. They can be applied in various ways, including Web2, private companies, and service providers. Blockchain is just one potential application of this tech stack. For it to work, claims only need some address with a corresponding encryption key. + +The DID and VC tech stack can be **connected to the storage** of a Universal Profile, with its **global addresses potentially serving as identifiers** of the certificate or role. What's different to using a regular wallet is that the Universal Profile can directly house the descriptions and metadata, not just the unique reference address. In addition, their controller keys can change using on-chain security without modifying the persona's address. + +The main goal of DIDs and VCs is to **enable more distributed, secure, and equal relationships** in the digital world. This potential is maximized when combined with open blockchain ledgers. The implementation details are up to individual projects, allowing diverse solutions tailored to specific use cases. Some are heading toward bundling claims and making them portable across different services, and some are further focusing on zero-knowledge-proofs to maintain proper privacy. + +Claims and UPs are not inherently linked, but combining the technologies could unlock their full potential for **creating decentralized, secure, and verifiable digital identities or profiles**. We are expecting projects to explore different ways of implementing identity claims, pushing the boundaries of what's possible regarding privacy, security, and interoperability. However, by default, Universal Profiles are about showing public account data. + +### How does LUKSO differ from DISCO? + +DISCO is building on DIDs and VCs, and the project is about keeping your identity claims together so you can take them across apps conveniently. + +LUKSO, on the other hand, is building the **next generation of accounts** called Universal Profiles, where **claims can be incorporated** or held with lots of extended functionality about its core management. diff --git a/docs/faq/lukso/project-origins.md b/docs/faq/lukso/project-origins.md new file mode 100644 index 0000000000..65d362f0a8 --- /dev/null +++ b/docs/faq/lukso/project-origins.md @@ -0,0 +1,52 @@ +--- +sidebar_label: 'Project Origins' +sidebar_position: 6 +--- + +# Project Origins + +### What was the LUKSO rICO? + +The public funding of the project took place in 2020 on the Ethereum blockchain using Ether. LYXe, the **token equivalent on the Ethereum blockchain**, was handed out to participants of the funding. + +The public sale was implemented as a **Reversible Initial Coin Offering** (rICO), allowing participants to purchase LYXe tokens at a specific price over **eight months** without a commitment to participate in the entire process length of the sale. Buyers could discontinue and have their remaining ETH returned at any time. It was also possible to join the sale in the latter stages without being drastically disadvantaged. In total, the project received nearly 10,000 Ether. + +The rICO, proposed by LUKSO founder Fabian Vogelsteller for the LUKSO public sale, is a **public standard that gradually unlocks tokens through an autonomous-acting contract instance** deployed on the Ethereum blockchain. LUKSO did this to provide a fairer token sale and more protection for the buyer. + +### Where can I find the LYXe token address? + +The official address of the LYXe token is `0xA8b919680258d369114910511cc87595aec0be6D`. The Code of the LYXe Contract on Ethereum can be found here. + +### Why was LYXe implemented as ERC777 token? + +[ERC777](https://ethereum.org/de/developers/docs/standards/tokens/erc-777/) is a token standard on the Ethereum blockchain aimed at improving token contracts' functionality and user experience compared to its predecessor, the ERC20 standard. The key features of the ERC777 standard include: + +- **Send and Receive Hooks**: This allows tokens to notify the recipient contract about incoming tokens, which can then choose to reject or accept them. Similarly, a contract can be notified before its tokens are moved and take action accordingly. This helps to prevent the common problem of tokens being stuck in contracts, which is prevalent in the [ERC20](https://ethereum.org/de/developers/docs/standards/tokens/erc-20/) standard. +- **Operator Access**: In the ERC777 standard, a user can designate an operator to manage their tokens. This can be used to allow a third-party smart contract to perform certain operations, which can enable more complex and powerful functionality. +- **Backward Compatibility**: Despite having improved features, ERC777 is backward compatible with ERC20, which means contracts expecting ERC20 tokens can handle ERC777 tokens without any issue. +- **More Detailed Transactions**: In ERC777, the 'send' function includes transaction data, not just the amount and recipient. This additional information can be helpful for dApps that need to process more than just simple transfers. +- **Minting and Burning Events**: ERC777 allows the tracking of token minting and burning events, which can be helpful for dApps that need to monitor the total supply of a token dynamically. + +### How did the Genesis Validators start the network? + +The [Genesis Deposit Contract](https://etherscan.io/address/0x42000421dd80D1e90E56E87e6eE18D7770b9F8cC#code) was open for about three weeks and was frozen on the 9th of May. The PoS consensus was started with all Genesis Validators that deposited up to block 17,227,300 on Ethereum. There was a 46,523 block delay after the LUKSO team triggered the freeze. The genesis deposit contract received 10.336 deposits from 223 unique addresses based on the [Dune Analytics Dashboard](https://dune.com/hmc/lukso-genesis-validators). Each validator had to deposit 32 LYXe. + +Based LUKSO mainnet was started on the [23rd of May of 2023](https://medium.com/lukso/genesis-validators-start-your-clients-fe01db8f3fba) using the genesis files created from the deposits on Ethereum. All future validator deposits will be made as regular validators. + +### Where can I find the LUKSO Genesis Deposit Contract? + +The official address of the Genesis Deposit Contract is `0x42000421dd80d1e90e56e87e6ee18d7770b9f8cc`. The Code of the contract can be found here. You can also see the list of all valid token transfers until the contract has been closed. We also have a Dune Dashboard for Genesis Validators showing created deposits. + +### Which features did the Genesis Deposit Contract have? + +The deposit contract called the external LYXe [ERC777](https://ethereum.org/de/developers/docs/standards/tokens/erc-777/) token contract to lock the deposit amounts. To prepare the genesis files of the mainnet launch featured a freeze. Therefore, the deposit contract featured checks if a public key has been registered, preventing duplicate deposits. Only static deposit amounts of 32 LYX were allowed. + +The freeze also came with a delay function to allow people to have time still after the LUKSO team triggered it. Each validator that went through the Genesis Launchpad stored not only the LYXe token but also a vote for the initial coin supply of the mainnet. The additional data was stored on-chain to have a publically verifiable source of the initial LYX supply and distribution. + +### How much gas did the Genesis Deposit Contract consume? + +The Genesis Validator Deposit Contract consumed around `300k` gas per validator key. The contract needed quite some gas for good reasons, as it can be seen as the portal into a new blockchain. Additional features were required to have a safe and verifiable way for LUKSO's genesis. + +### How was the token supply of LUKSO determined? + +Genesis validators were able to deposit LYXe to the deposit launchpad. Each deposit transaction voted **35M**, **42M**, or **100M** LYX to the smart contract. 84.2% of the Genesis Validators voted for 42M. After the deposit contract was frozen, Genesis Validators could choose between the three genesis files to start their nodes. The launch was sealed after most validators had selected the genesis files of 42M. diff --git a/docs/faq/lukso/project-timeline.md b/docs/faq/lukso/project-timeline.md new file mode 100644 index 0000000000..777c6e3433 --- /dev/null +++ b/docs/faq/lukso/project-timeline.md @@ -0,0 +1,34 @@ +--- +sidebar_label: 'Project Timeline' +sidebar_position: 4 +--- + +# Project Timeline + +### When did LUKSO launch its Testnet? + +The LUKSO Testnet was launched on [3 May 2023 at 4:20 PM UTC](https://medium.com/lukso/genesis-validators-deposit-smart-contract-freeze-and-testnet-launch-c5f7b568b1fc). It allowed developers to shift their dApps from L16 and test them before going live on the mainnet. The launch also served as a pre-test for mainnet, which went live only 20 days later. The testnet features the same architecture as the mainnet- however, depositing validators requires being whitelisted. + +### When did LUKSO launch its Mainnet? + +The LUKSO Mainnet was launched on [23 May 2023 at 4:20 PM UTC](https://medium.com/lukso/genesis-validators-start-your-clients-fe01db8f3fba). After starting with a participation rate of 68%, the network's consensus quickly gained momentum and was fully functioning with epochs within the first hour. The participation rate then increased to over 95% within the first week. The network was launched with about 185 nodes distributed globally. LUKSO itself operated none of them. + +### When was Shapella enabled on Mainnet? + +The Shapella update, which is responsible for enabling validator withdrawals, was enabled on the 30th of June 2023, 5 weeks after the initial launch of the LUKSO mainnet happened. A few days after the withdrawals were enabled, the LUKSO mainnet was opened to regular validators coming in due to the LYXe migration. + +### What was the L14 Testnet? + +The L14 was the initial testnet to showcase LUKSOs vision of Universal Profiles. It is maintained by LUKSO and used for the [Universal Profile Explorer](https://universalprofile.cloud/) and [The Dematerialised](https://thedematerialised.com/) Marketplace, which have already launched multiple digital asset sales. Regarding the tech, L14 still uses outdated ERC725 versions from 2020. Once the profiles and assets are migrated to the mainnet, those assets and profiles will be updated to the latest LSP standardizations. + +### What was the L15 Testnet? + +The L15 was the ephemeral testnet to showcase LUKSOs initial network architecture. The development was started in 2021 and featured the Vanguard and Pandora chains to integrate Proof of Stake into the EVM tech stack. Later, the architecture was aligned with the Ethereum architecture, as the ecosystem quickly shifted focus from sharding to Proof of Stake itself. There was no need for a custom implementation anymore. + +### What was the L16 Testnet? + +The L16 was LUKSOs latest testnet before the LUKSO launch phase. It started as a decentralized network in 2022 and featured the almost final network architecture without slasher functionality. People could add and run validators nodes and prepare for the mainnet setups. The LUKSO team also went on and did stress tests for transactions and analyzed network behaviors. The community also started developing the first applications and deployed contracts using funds from the faucet. + +### Since when has the L16 Testnet been deprecated? + +After the final and consistent LUKSO Testnet release, L16 has been officially deprecated since 15th June 2023. Developers had a transition time of 3 months. Community members and the team then shut down all nodes and services at the end of June 2023. diff --git a/docs/faq/lukso/wallet-support.md b/docs/faq/lukso/wallet-support.md new file mode 100644 index 0000000000..136375d2e6 --- /dev/null +++ b/docs/faq/lukso/wallet-support.md @@ -0,0 +1,22 @@ +--- +sidebar_label: 'Wallet Support' +sidebar_position: 5 +--- + +# Wallet Support + +### Whats the best way to use LUKSO? + +It's suggested to use the [Universal Profile Extension](https://docs.lukso.tech/guides/browser-extension/install-browser-extension) while interacting with apps and services on LUKSO. The extension offers you a much more user-friendly and feature-rich experience than you would get using regular wallets. + +### Can the Universal Profile Extension be considered a wallet? + +The Universal Profile Extension should not be classified as a wallet. While connected Universal Profiles can store assets, the extension serves as a comprehensive center for your blockchain interactions and reflects your on-chain persona with much more capabilities than just holding assets. + +### Which wallets can be used with the LUKSO network? + +LUKSO is an EVM-compatible network. Therefore, any Ethereum wallet that allows custom networks can be used on the LUKSO network. You can find all the parameters of the LUKSO mainnet within the [Network](https://docs.lukso.tech/networks/mainnet/parameters) section. + +### Can I use hardware wallets like Ledger to store LYX? + +Yes, you can use hardware wallets with Ethereum support, such as [Ledger](https://www.ledger.com/) or [Trezor](https://trezor.io/), to store LYX. Both can connect to browser-based wallets like [MetaMask](https://metamask.io/) and then be used to send or receive tokens. To see your LYX, you must add the LUKSO Mainnet as a custom network. The parameters can be found in the [Network](https://docs.lukso.tech/networks/mainnet/parameters) section. diff --git a/src/pages/index.js b/src/pages/index.js index 804d6abe0d..f5f19e600f 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -65,7 +65,7 @@ function Index() { />