Outlier Ventures：如何用Arweave去中心化托管网站前端

Although bitcoin trading network involves no license and verifiability, there are still too many projects with managed fully centralized front ends. These platforms have become the most popular tools for developers because of their excellent developer experience and reasonable cost. The deployment of fully decentralized applications is not simple and the tools are not mature. In this paper, we describe how to easily deploy and host fully decentralized front ends, and we can buy about assets in products by paying US dollars at one time. And the engineering team, we spent a lot of time discussing and thinking about new technologies that will help shape our decentralized future. You can check out our technology radar. In addition to taking the time to help our portfolio companies make the right technology choices, we also build our own applications, such as the decentralized financing platform project recently built on the Internet. We decided to build more content on the stack and write many different design choices in the process and record our own in a series of blog posts. It is found that in this paper, we will pay special attention to the theme of decentralized storage. Various decentralized physical infrastructure networks allow developers to use similar services provided by Google Cloud, but participants with idle computing ability in a truly decentralized way will be encouraged to contribute their resources to an effective cloud computing platform, which has no intermediaries and no overall central control point or fault. This article explains the challenges of decentralized storage and how we can solve the hosting challenges. Introduction to the basic knowledge of the technology choices we have made. This is a challenge to decentralize storage directly from the deployment of decentralized front-end libraries. If the front-end is centralized, it will not be truly decentralized. If the front-end of the website can't log in or contains loopholes or worse, if the third party destroys the website users' confidence in them, what is the advantage of having a license-free contract? When the back-end and the front-end are completely transparent, people will often repeat it, which will make it more meaningful to decide on the evaluation of the hosting solution. Some acceptance criteria to keep in mind when hosting should ensure that it is tamper-proof and accessible, and allow tracking of deployed files on public infrastructure. Version control should be unstoppable, easy to deploy, easy to publish new content, and as cheap as possible with the integration cost. Encrypted payment is a service that we can pay with tokens without being forced to return to the legal tender channel. After defining these requirements, we have determined some available options to use our hosted nodes and use third-party providers. Our purpose: We decided to minimize our dependence on or any other third-party solutions. Although they bring many advantages in terms of easy deployment, they need keys. We regard them as a single point of failure and control risk. As long as there is a key, there is no guarantee of tamper resistance and accessibility. Inevitably, there is a trade-off between them. We often use them to host static content. We even discussed hosting our own nodes, which will provide end users with the ability to verify whether a specific deployment is consistent with the deployed code. And we can use and and to allow variable pointers to update website content and enable domain name resolution. However, because it is not an incentive network, it will be fixed to our own nodes, which may cause a single point of failure. This is what we strictly try to avoid. We have studied the fixed solution, for example, it provides an excellent developer experience, but in the end it is a centralized solution because it is based on the keys they hold and allows them to withdraw at any time. This is a useful service, but in this case, we decided that it would not provide us with the completely decentralized experience we were pursuing. For the same reason, another solution was ruled out. Next, we considered that it provided a layer on top of it and encouraged the provider to provide storage space by fixing the content to the node to pay the fee to the provider, and because both and were developed by, it was a smooth and coherent experience if it was not their business model. Depending on the transaction, we may choose to be a developer. We don't need to keep thinking about who to pay and how much to pay. Therefore, for our specific use case, we also ruled out our third choice, which provided us with a technical trade-off, but in the end, it was the solution we chose. Although the cost of each upload was very low, about US dollars each time, and the network had existed for five years, the tools and resources were less than those in the ecosystem, so we had to solve some interesting challenges, including developing me. Our own library is used directly from our binding and uploading tools. You can follow our steps here to get familiar with how to upload content to another name. First of all, we are familiar with the basic knowledge. After we decided to build a simple application, our first stop was there. We found a lot of useful resources for uploading data, including the prerequisites for deploying applications. You need to install and you also need an exchange account where you can buy some for us to deploy. Use the main network instead of the test network because it is cheap enough to carry out experiments. The first step is to create a wallet and use some funds to fund it. The interesting and simplest way is to create your wallet by checking whether the funds have reached your address. Now you have a wallet that contains your private key and public key. By running to find the address, you need to provide a small amount of funds. The interesting and simplest way is to start writing a few lines of code by checking whether the funds have reached your address. Deploy some content, first create a simple network application. Today, the simplest thing is to choose the default value that suits you best, and then look at it. You can find a lot of useful resources for uploading data packages, including deployment applications, or continue to browse blog articles to get a good way to create a file named and paste the following content to run it. You just deployed the first content here, which is good but not useful enough. The next step is to upload an actual file. Instead of a string, you need to deal with the tag gateway. For this reason, you need to know what kind of data it is providing, such as images uploading multiple files. Things are beginning to become interesting, but before traversing the directory and publishing all the files to it, there is one last concept to understand. When uploading files to it, each file will be assigned its own unique transaction. By default, these are not grouped or organized in any particular way, so the list contains all the files in a group, and it also contains an index attribute, which points to aliases pointing to any transaction. Trading is cheap, but it is far from creating so many transactions. 比特币今日价格行情网_okx交易所app_永续合约_比特币怎么买卖交易_虚拟币交易所平台

注册有任何问题请添加 微信：MVIP619 拉你进入群

文章转载注明 网址：https://netpsp.com/?id=62347