The partnership will allow Flare dApp developers to benefit from Elliptic's real-time transaction screening and crypto wallet checks.

Flare Integrates Elliptic’s Crypto Risk Management Solutions to Fortify DApps against Financial Crimes

DappRadar, the biggest Web3 dapp distribution platform, has unveiled its DappRadar's Blockchain Gaming for Q3 2023 report on the gaming segment growth within the Web3 ecosystem. Their findings highlight a 12% increase in Web3 gaming activity from the prior quarter,

Fasttoken Set to Be Utilized by Over 100 Game Developers in Web3 Games

This new feature makes MetaMask the first self-custody web3 wallet to integrate native security alerts, proactively preventing malicious transactions, protecting users from scams, phishing, and hacks,

MetaMask Adds Privacy-Preserving Security Alerts That Aims to Prevent Billions from Being Stolen

Leading Korean game developer Wemade has announced a strategic collaboration with Fingerlabs, a subsidiary of KOSDAQ-listed FSN, to foster the blockchain ecosystem.Seoul, South Korea, Nov. 01, 2023 (GLOBE NEWSWIRE) -- Leading Korean game developer Wemade has announced a strategic collaboration with Fingerlabs,

Wemade and Fingerlabs announce strategic collaboration to drive WEMIX3.0 blockchain ecosystem growth

The AWS Blockchain Node Runners has so far integrated Ethereum (ETH) and Solana (SOL), thus making it a major step for the latter.

Solana Blockchain Nodes Now Available to DeFi and Dapp Developers on AWS Repository

Disclaimer: The opinions expressed by our writers are their own and do not represent the views of U.Today. The financial and market information provided on

Shiba Inu (SHIB) Innovates with Addition of Privacy Feature – U.Today

These efforts often follow a framework of "dynamic adaptation policy pathways" (DAPP). This means the planning process has to remain flexible to keep adjusting as new information comes to hand. However, a recent symposium on the ten-year stocktake of this ...

Solving the climate adaptations that can make problems worse

MetaMask, one of the world’s leading self-custody web3 platform developed by Consensys, and Blockaid, a leading web3 security provider, have announced the launch of privacy-preserving security alerts in the MetaMask extension.

MetaMask Partners Blockaid On Security Alerts To Avert Billions In Crypto Assets Theft

MetaMask, a world-leading self-custody web3 platform developed by Consensys, and Blockaid, a leading web3 security provider, Tuesday, announced the launch of privacy-preserving security alerts in the MetaMask extension.

MetaMask launches privacy-preserving security alerts to prevent online assets theft

CryptoStrikers is ready to reshape the world of burned tokens through its state-of-the-art DeFi platform. By harnessing sophisticated technologies and championing community involvement, CryptoStrikers aims to revive burned tokens,

Introducing CryptoStrikers: A revolution where burned tokens gain new life & Proof Of Sacrifice

Get the most recent info and news about Dapp on HackerNoon, where 10k+ technologists publish stories for 4M+ monthly readers.

Ayudamos a integrar a los jugadores del ecosistema de pagos digitales como bancos, wallets y comercios en una sola carretera.

Dapp

You may be wondering what DOCKERIZE is. It means using Docker to containerize your dApp project. Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. Applications include web apps, APIs, mobile apps, and backend services. It includes the code you write, the libraries you use, and the configurations needed for it to run. Infrastructure like operating system(OS), Network setting, web servers, database, and other services your application interacts with. It also involves the hardware or virtual machines where your application runs. Docker allows you to package and run your application as a single entity in a loosely isolated environment called a CONTAINER. Container Containers are lightweight and contain everything needed to run the application, so you don't need to rely on what's installed on the host. You can share containers while you work, and be sure that everyone you share with gets the same container that works in the same way. For example, you and your colleagues are working on a dApp project that uses Node.js and Hardhat. Initially, you set up the project on your local machine, knowing that before your colleagues can run the application locally, they would need to install Node.js and Hardhat on their systems. Now, let’s imagine one of your colleagues is using a machine that isn't compatible with Node.js and Hardhat. How would you solve this problem? With Docker, you can package your application, along with all its dependencies, into a single container that can run on any operating system. This solves the issue of installing software or dependencies separately on different machines. Images After you’ve containerized your application, how do you get it to run? As a frontend developer, when starting a new React app, you usually run npx create-react-app or npm init vite@latest. For an existing project, you'd typically run git pull followed by npm install to get it running locally. Similarly, to run a container, you need something called a container image. A container image is a standardized package that includes all the files, binaries, libraries, and configurations needed to run your application inside a container. It’s like having everything bundled together so it can run consistently across any environment. See below for a container image: Practicals In this section, you will learn how to containerize and share your app. Prerequisites You have installed the latest version of Docker Desktop.
You have installed a Git client.
You have an IDE or a text editor to edit files. Docker recommends using Visual Studio Code. Containerize Your Application In your root directory, initialize docker using this command prompt: docker init Provide answers to the prompts. ? What application platform does your project use? Node  
? What version of Node do you want to use? 20.16.0  
? Which package manager do you want to use? npm  
? Do you want to run "npm run build" before starting your server? No  
? What command do you want to use to start the app? ["npm", "run", "dev"]  
? What port does your server listen on? 5173 You will see three additional files in your directory, namely .dockerignore, compose.yaml and DockerFile. Dockerfile: A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image.
compose.yaml: The Compose file, or compose.yaml file follows the rules provided by the Compose Specification in how to define multi-container applications.
.dockerignore: This file excludes files and directories from the build context. Inside Dockerfile, clear out the file and add the following: # syntax=docker/dockerfile:1  
ARG NODE_VERSION=20.16.0  
FROM node:${NODE_VERSION}-alpine  
# Use development node environment by default.  
ENV NODE_ENV development  
WORKDIR /app  
# Copy package.json and package-lock.json to the working directory  
COPY package.json package-lock.json ./  
# Install dependencies  
RUN npm install  
# Copy the rest of the source files into the image  
COPY . .  
# Change ownership of the /app directory to the node user  
RUN chown -R node:node /app  
# Switch to the node user  
USER node  
# Ensure node_modules/.bin is in the PATH  
ENV PATH /app/node_modules/.bin:$PATH  
# Expose the port that the application listens on  
EXPOSE 5173  
# Run the application  
CMD ["npm", "run", "dev"] Build your container image using this: docker build -t <your-image-name> . To see your container image, go to your docker desktop, click on Images, as shown below  or you can use this command prompt, docker images to see your container image in your terminal.  6. Run the image: docker run -p 5173:5173 <your-image-name> You should see an output like this: > vite-project@0.0.0 dev
> vite

  VITE v5.4.2  ready in 222 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: http://172.17.0.2:5173/ Sharing the Application Sign up or Sign in to Docker Hub.
Select the Create Repository button.  
Name your repository with the same container image name. Make sure the Visibility is Public.
Select Create. Sign in to Docker Hub using the command line docker login -u <YOUR USERNAME> Enter your Password Your Password won’t be visible while typing Use the docker tag command to give the getting-started image a new name. Replace YOUR-USER-NAME with your Docker ID: You may encounter this denied: requested access to the resource is denied while pushing.
To fix this,

relogin using docker login, press enter.
After that, you will be navigated to your browser,
copy your OTP the terminal and input it,
press CONFIRM
repush the image

You will see an output like: This shows your image has been built and pushed into a registry. Your team can now pull this image and run the application on their local machine. You can check by searching for your container image on the search bar on your docker desktop or docker hub. Troubleshooting Port Conflict:

Error: if the port 8000 was already in use.
Solution: Identified the process using port 8000 and terminated it using the following commands: # Find the process using port 8000  
lsof -i :8000  
# Kill the process (replace <PID> with the actual process ID found from the previous command)  
kill -9 <PID> Alternatively, you could run the Docker container on a different port: docker run -p 8001:8000 my-vite-app Update an Application Anything you update your app. e.g., you change a syntax or function,

Stop your docker desktop, click on Containers
Stop the port, and click on delete.  
Rebuild the Application using the docker build command. docker build -t <your-image-name> . Rerun the app. docker run -p 5173:5173 <your-image-name> Conclusion By following this guide, you can easily package your application and its dependencies into a container, share it with your team, and run it easily on any machine. This not only enhances collaboration but also mitigates issues related to environment setup and compatibility. You may be wondering what DOCKERIZE is. It means using Docker to containerize your dApp project. DOCKERIZE DOCKERIZE Docker Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. applications infrastructure Applications include web apps, APIs, mobile apps, and backend services. It includes the code you write, the libraries you use, and the configurations needed for it to run. Applications include web apps, APIs, mobile apps, and backend services. It includes the code you write, the libraries you use, and the configurations needed for it to run. Applications Infrastructure like operating system(OS), Network setting, web servers, database, and other services your application interacts with. It also involves the hardware or virtual machines where your application runs. Infrastructure like operating system(OS), Network setting, web servers, database, and other services your application interacts with. It also involves the hardware or virtual machines where your application runs. Infrastructure Docker allows you to package and run your application as a single entity in a loosely isolated environment called a CONTAINER. CONTAINER. Container Containers are lightweight and contain everything needed to run the application, so you don't need to rely on what's installed on the host. You can share containers while you work, and be sure that everyone you share with gets the same container that works in the same way. For example, you and your colleagues are working on a dApp project that uses Node.js and Hardhat. Initially, you set up the project on your local machine, knowing that before your colleagues can run the application locally, they would need to install Node.js and Hardhat on their systems. Now, let’s imagine one of your colleagues is using a machine that isn't compatible with Node.js and Hardhat. How would you solve this problem? With Docker, you can package your application, along with all its dependencies, into a single container that can run on any operating system. This solves the issue of installing software or dependencies separately on different machines. Images After you’ve containerized your application, how do you get it to run? As a frontend developer, when starting a new React app, you usually run npx create-react-app or npm init vite@latest . For an existing project, you'd typically run git pull followed by npm install to get it running locally. Similarly, to run a container, you need something called a container image . npx create-react-app npm init vite@latest git pull npm install container image A container image is a standardized package that includes all the files, binaries, libraries, and configurations needed to run your application inside a container. It’s like having everything bundled together so it can run consistently across any environment. See below for a container image: Practicals In this section, you will learn how to containerize and share your app. Prerequisites You have installed the latest version of Docker Desktop. You have installed a Git client. You have an IDE or a text editor to edit files. Docker recommends using Visual Studio Code. You have installed the latest version of Docker Desktop . Docker Desktop You have installed a Git client . Git client You have an IDE or a text editor to edit files. Docker recommends using Visual Studio C ode. Visual Studio C ode. Containerize Your Application In your root directory, initialize docker using this command prompt: In your root directory, initialize docker using this command prompt: docker init docker init Provide answers to the prompts. Provide answers to the prompts. ? What application platform does your project use? Node  
? What version of Node do you want to use? 20.16.0  
? Which package manager do you want to use? npm  
? Do you want to run "npm run build" before starting your server? No  
? What command do you want to use to start the app? ["npm", "run", "dev"]  
? What port does your server listen on? 5173 ? What application platform does your project use? Node  
? What version of Node do you want to use? 20.16.0  
? Which package manager do you want to use? npm  
? Do you want to run "npm run build" before starting your server? No  
? What command do you want to use to start the app? ["npm", "run", "dev"]  
? What port does your server listen on? 5173 You will see three additional files in your directory, namely .dockerignore, compose.yaml and DockerFile. You will see three additional files in your directory, namely .dockerignore , compose.yaml and DockerFile. .dockerignore compose.yaml DockerFile. Dockerfile: A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image. compose.yaml: The Compose file, or compose.yaml file follows the rules provided by the Compose Specification in how to define multi-container applications. .dockerignore: This file excludes files and directories from the build context. Dockerfile : A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image. Dockerfile compose.yaml : The Compose file, or compose.yaml file follows the rules provided by the Compose Specification in how to define mul ti-container applications. compose.yaml compose.yaml Compose Specification in how to define mul .dockerignore : This file excludes files and directories from the build context. .dockerignore Inside Dockerfile, clear out the file and add the following: Inside Dockerfile , clear out the file and add the following: Dockerfile # syntax=docker/dockerfile:1  
ARG NODE_VERSION=20.16.0  
FROM node:${NODE_VERSION}-alpine  
# Use development node environment by default.  
ENV NODE_ENV development  
WORKDIR /app  
# Copy package.json and package-lock.json to the working directory  
COPY package.json package-lock.json ./  
# Install dependencies  
RUN npm install  
# Copy the rest of the source files into the image  
COPY . .  
# Change ownership of the /app directory to the node user  
RUN chown -R node:node /app  
# Switch to the node user  
USER node  
# Ensure node_modules/.bin is in the PATH  
ENV PATH /app/node_modules/.bin:$PATH  
# Expose the port that the application listens on  
EXPOSE 5173  
# Run the application  
CMD ["npm", "run", "dev"] # syntax=docker/dockerfile:1  
ARG NODE_VERSION=20.16.0  
FROM node:${NODE_VERSION}-alpine  
# Use development node environment by default.  
ENV NODE_ENV development  
WORKDIR /app  
# Copy package.json and package-lock.json to the working directory  
COPY package.json package-lock.json ./  
# Install dependencies  
RUN npm install  
# Copy the rest of the source files into the image  
COPY . .  
# Change ownership of the /app directory to the node user  
RUN chown -R node:node /app  
# Switch to the node user  
USER node  
# Ensure node_modules/.bin is in the PATH  
ENV PATH /app/node_modules/.bin:$PATH  
# Expose the port that the application listens on  
EXPOSE 5173  
# Run the application  
CMD ["npm", "run", "dev"] Build your container image using this: Build your container image using this: docker build -t <your-image-name> . docker build -t <your-image-name> . To see your container image, go to your docker desktop, click on Images , as shown below or you can use this command prompt, Images docker images docker images to see your container image in your terminal. 6. Run the image: docker run -p 5173:5173 <your-image-name> docker run -p 5173:5173 <your-image-name> You should see an output like this: > vite-project@0.0.0 dev
> vite

  VITE v5.4.2  ready in 222 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: http://172.17.0.2:5173/ > vite-project@0.0.0 dev
> vite

  VITE v5.4.2  ready in 222 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: http://172.17.0.2:5173/ Sharing the Application Sign up or Sign in to Docker Hub. Select the Create Repository button. Name your repository with the same container image name. Make sure the Visibility is Public. Select Create. Sign up or Sign in to Docker Hub. Sign up Docker Hub. Select the Create Repository button. Create Repository Name your repository with the same container image name. Make sure the Visibility is Public . Visibility Public Select Create . Create Sign in to Docker Hub using the command line Sign in to Docker Hub using the command line docker login -u <YOUR USERNAME> docker login -u <YOUR USERNAME> Enter your Password Enter your Password Your Password won’t be visible while typing Your Password won’t be visible while typing Use the docker tag command to give the getting-started image a new name. Replace YOUR-USER-NAME with your Docker ID: Use the docker tag command to give the getting-started image a new name. Replace YOUR-USER-NAME with your Docker ID: docker tag getting-started YOUR-USER-NAME You may encounter this denied: requested access to the resource is denied while pushing. To fix this, relogin using docker login, press enter.
After that, you will be navigated to your browser,
copy your OTP the terminal and input it,
press CONFIRM
repush the image You will see an output like: You may encounter this denied: requested access to the resource is denied while pushing. denied: requested access to the resource is denied To fix this, relogin using docker login, press enter. After that, you will be navigated to your browser, copy your OTP the terminal and input it, press CONFIRM repush the image relogin using docker login , press enter. docker login After that, you will be navigated to your browser, copy your OTP the terminal and input it, OTP press CONFIRM CONFIRM repush the image You will see an output like: This shows your image has been built and pushed into a registry. Your team can now pull this image and run the application on their local machine. You can check by searching for your container image on the search bar on your docker desktop or docker hub . docker hub Troubleshooting Port Conflict:

Error: if the port 8000 was already in use.
Solution: Identified the process using port 8000 and terminated it using the following commands: Port Conflict : Error: if the port 8000 was already in use.
Solution: Identified the process using port 8000 and terminated it using the following commands: Port Conflict Error: if the port 8000 was already in use. Solution: Identified the process using port 8000 and terminated it using the following commands: Error : if the port 8000 was already in use. Error 8000 Solution : Identified the process using port 8000 and terminated it using the following commands: Solution 8000 # Find the process using port 8000  
lsof -i :8000  
# Kill the process (replace <PID> with the actual process ID found from the previous command)  
kill -9 <PID> # Find the process using port 8000  
lsof -i :8000  
# Kill the process (replace <PID> with the actual process ID found from the previous command)  
kill -9 <PID> Alternatively, you could run the Docker container on a different port: Alternatively, you could run the Docker container on a different port: docker run -p 8001:8000 my-vite-app docker run -p 8001:8000 my-vite-app Update an Application Anything you update your app. e.g., you change a syntax or function,

Stop your docker desktop, click on Containers
Stop the port, and click on delete.  
Rebuild the Application using the docker build command. Update an Application Anything you update your app. e.g., you change a syntax or function, Stop your docker desktop, click on Containers
Stop the port, and click on delete.  
Rebuild the Application using the docker build command. Update an Application Anything you update your app. e.g., you change a syntax or function, Update an Application Stop your docker desktop, click on Containers Stop the port, and click on delete. Rebuild the Application using the docker build command. Stop your docker desktop, click on Containers Containers Stop the port, and click on delete. Rebuild the Application using the docker build command. docker build docker build -t <your-image-name> . docker build -t <your-image-name> . Rerun the app. Rerun the app. docker run -p 5173:5173 <your-image-name> docker run -p 5173:5173 <your-image-name> Conclusion By following this guide, you can easily package your application and its dependencies into a container, share it with your team, and run it easily on any machine. This not only enhances collaboration but also mitigates issues related to environment setup and compatibility.

A Beginner's Guide to Dockerizing a Vite dApp Project

የ Vite dApp ፕሮጀክትን ለመቆጠብ የጀማሪ መመሪያ

Guía para principiantes sobre cómo dockerizar un proyecto de dApp de Vite

Unha guía para principiantes para dockerizar un proxecto Vite dApp

Vite dApp プロジェクトを Docker 化する初心者向けガイド

დამწყებთათვის გზამკვლევი Vite dApp პროექტის დოკერიზაციისთვის

Panduan Pemula untuk Melabuhkan Projek Vite dApp

Vite dApp परियोजना डकराइज गर्नको लागि एक शुरुआती गाइड

Huk qallariqpa yanapakuynin huk Vite dApp Proyecto Dockerizing kaqpaq

Mwongozo wa Waanzilishi wa Kuweka Mradi wa Vite dApp

ንጀመርቲ መምርሒ ንዶከርይዝድ ፕሮጀክት ቫይት ዲኣፕ

“Vite dApp” taslamasyny dokerlemek üçin başlangyç gollanma

Hướng dẫn cho người mới bắt đầu về Dockerizing một dự án dApp Vite

A Newbie Developer's Guide to Bringing AI Into Blockchain dApps

ব্লকচেইন dApps-এ AI আনার জন্য একজন নবাগত বিকাশকারীর গাইড

Ein Leitfaden für Entwicklerneulinge zum Integrieren von KI in Blockchain-dApps

Una guía para desarrolladores novatos para incorporar la IA a las dApps de Blockchain

Guide du développeur débutant pour intégrer l'IA dans les dApps Blockchain

ब्लॉकचेन dApps में AI लाने के लिए एक नौसिखिया डेवलपर की मार्गदर्शिका

ブロックチェーン dApps に AI を導入するための初心者開発者向けガイド

블록체인 dApp에 AI를 도입하기 위한 초보자 개발자 가이드

Guia do desenvolvedor novato para trazer IA para dApps Blockchain

Руководство для новичков по внедрению искусственного интеллекта в децентрализованные приложения на блокчейне

Yapay Zekayı Blockchain dApp'lerine Getirmeye Yönelik Yeni Başlayan Geliştirici Kılavuzu

Hướng dẫn dành cho nhà phát triển mới về việc đưa AI vào các dApps trên Blockchain

将人工智能引入区块链 dApp 的新手开发者指南

How to Build DApp on Rootstock with Next.js, Typescript, and Solidity

Tracks, the innovative Web3 music streaming dApp created by LABEL Foundation and built on the BNB Chain, is now available on LG Smart TVs running webOS 22 and webOs 23 globally. This pioneering launch introduces the first-ever Web3 music app on an LG smart TV platform, transforming how users engage with music streaming. The app delivers an engaging experience by offering high-quality music coupled with stylish artwork, strongly resonating with millennials and seamlessly integrating into their daily lives. Since its debut in July, the mobile dApp TRACKS, running on the BNB Chain, has rapidly gained momentum, acquiring over 150,000 users and 10,000 daily active users, predominantly among millennials. This surge in popularity followed investments from top-tier funds in 2022. Tracks' success stems from its user-centric approach, distinguishing it from conventional content provider-focused music services. Along with a sustainable revenue model, Tracks aligns with the growing trend of Free Ad-Supported TV, aiming to further amplify its revenue strategy in this area. Through its collaboration with LG, Tracks extends its reach into the lives of users across various devices, aiming to surpass the limitations of paid streaming and globalize music access. Tracks is well on its way to becoming a premier platform in both and Web2 music services. Web3 The app is now accessible on the latest LG Smart TV models at no cost, offering an immersive and accessible music experience.

LABEL Foundation’s Tracks Launches Web3 Music dApp on LG Smart TVs

LABEL ফাউন্ডেশনের ট্র্যাক LG স্মার্ট টিভিতে Web3 Music dApp লঞ্চ করেছে

Tracks der LABEL Foundation führt Web3 Music dApp auf LG Smart TVs ein

Tracks de LABEL Foundation lanza Web3 Music dApp en televisores inteligentes LG

Tracks de la Fondation LABEL lance Web3 Music dApp sur les téléviseurs intelligents LG

लेबल फाउंडेशन के ट्रैक्स ने एलजी स्मार्ट टीवी पर वेब3 म्यूजिक डीएपी लॉन्च किया

LABEL Foundation の Tracks が LG スマート TV で Web3 Music dApp を開始

LABEL Foundation의 Tracks, LG 스마트 TV에 Web3 Music dApp 출시

LABEL Foundation’s Tracks lança Web3 Music dApp em Smart TVs LG

Компания Tracks Фонда LABEL запускает dApp Web3 Music на телевизорах LG Smart TV

LABEL Foundation's Tracks, LG Akıllı TV'lerde Web3 Music dApp'i Başlatıyor

Các bài hát của LABEL Foundation ra mắt dApp âm nhạc Web3 trên TV thông minh LG

LABEL 基金会的 Tracks 在 LG 智能电视上推出 Web3 音乐 dApp

Content Overview What is dApp? What client-side technologies should be used for a dApp? Which type of domain should you choose? Authentication: MetaMask's Dark Side Blockchain Selection: Which Chains Are Best for dApps? Funding Your Idea Through Grants What is dApp? The commonly accepted definition of a is, in short, an application that can operate autonomously using a distributed ledger system. At first glance, it seems straightforward. But, when you begin to question and list examples of dApps, it appears most dApps wouldn't qualify. It may even seem as if true dApps don't exist. dApp If one developer tried to explain to another what a dApp is in 2023, they'd probably say, "Well, it's like a website that calls various APIs working with blockchain." Just like that, the magic of the term 'dApp' would vanish. The other developer would think, "What's the big deal? Why so much fuss about it?" The reason is that the genuine concept of dApps has long been sacrificed for user convenience. Originally, the term implied that every instance of the application runs on the user's device. You'd fetch wallet balances from your node, and you'd send transactions from it as well. The application itself should be stored on a distributed storage system resistant to censorship, outages, and attacks. All user-generated data should also be stored in such storage or directly in a blockchain smart contract. It's a captivating concept, but it clashes with reality. Blockchain data can weigh gigabytes or even terabytes. Decentralized storage requires specific software and space for distributed data, isn't as fast as AWS, and often needs specialized browsers. Interacting with smart contracts costs money in cryptocurrency, and purchasing it isn't straightforward for first-timers. Then, factor in the complexity of setup, the need for specialized knowledge, ample free time, and the myriad of blockchains out there. So, dApp developers started offloading the most complex parts for users to separate services, interfacing with them solely via APIs. Now, almost every blockchain has its API. This means dApps have to store settings for each network to cater to more users. While APIs for distributed storage exist, hosting the dApp on them isn't efficient. Most solutions can't compete with web2 in speed and convenience. Hence, such storage systems are only used for tasks where response time isn't a priority. Even on Hackernoon, Arweave is used only for backing up articles. What client-side technologies should be used for a dApp? Well, if we aim to reach the maximum number of people in 2023 and 2024, then client-side web technologies are the way to go for . True, backend technologies like PHP and Python won't cut it, but any framework based on JavaScript/Typescript will do the trick. You can pick from the top 3 frameworks: React, Angular, or Vue.js. However, in my experience, Web3 components for Angular are rarer. My personal choice is React with Typescript. Of course, nobody's stopping you from using plain JavaScript, but why would you? creating a dApp Further, to interact with smart contracts, you'll need some kind of library. The most popular ones are Web3.js and ethers.js. In my opinion, both aren't the most elegant. Their APIs frequently change, and code examples older than a year might not work straight away. My personal pick is ethers.js. Its structure feels more intuitive to me, and compared to Web3.js, the solutions tend to be more concise. In the documentation of various projects, examples are usually provided for at least these two libraries. First and foremost, create an empty project (React + Typescript). npx create-react-app project-name --template typescript Navigate to the project directory. cd project-name Install ethers. This will ensure you have the most up-to-date version. Keep in mind that older examples from the internet might not work without adjustments. npm i ethers Which type of domain should you choose? No, I'm not talking about top-level domains like .com, .org, and the like. I'm discussing whether one should opt for decentralized domains instead of traditional ones. Yes, domains can be decentralized, too. Instead of the usual top-level domains, you might come across ones like .eth, .nft, .wallet, .crypto, and .go. Unfortunately, using them in popular browsers (like Chrome and Safari) without additional extensions won't work. Various companies have been trying for years to establish a domain zone that functions both in web2 and web3. So far, agreements have only been reached with less popular browsers like Opera and Brave. In these browsers, Web3 domains work. So, if your target audience primarily uses the most popular browsers, the choice is clear: you need a Web2 domain. However, if your application becomes popular, domain squatters might purchase a domain with your project's name. When the Web3 revolution takes place and domains become accessible in all browsers, these squatters will likely demand a hefty price for that domain. From this, it emerges that Web3 domains might be worth purchasing as a safeguard against squatters or for a hardcore audience using specific browsers. Furthermore, such domains can serve as an alternative to unreadable wallet addresses. Instead of a complex address like 0x5301b241879e66EC45fD284D3D97A5C51472D6f3, you could use a domain like “mydapp.crypto” to send and receive funds. Authentication: MetaMask's Dark Side Currently, MetaMask stands as the most popular browser extension for storing people's wallet private keys. The private key is the most crucial element - "Not Your Keys, Not Your Crypto.” Entrusting such a vital component to anyone is a no-go, making it preferable to store it on one's device. MetaMask, in this context, allows users to keep their private key locally and doesn't share it with anyone, not even dApps, no matter how nicely they ask. Despite its millions of users, getting started with MetaMask isn't straightforward. One has to go through a myriad of not-so-simple steps to set up an initial empty wallet. And then an equal number of steps are required to fund that wallet. I can confidently say that the next billion users will opt for a different solution. But as of now, it's the industry standard, and . every dApp should support MetaMask But what if I told you there are over a hundred other wallets out there? It would be ideal to support those as well. But don't pull your hair out just yet! Solutions already exist that support all popular wallets. Typically, apart from browser extensions, these solutions also cater to mobile apps, significantly broadening the potential user base. Examples of services you can use are Web3Auth and WalletConnect. Blockchain Selection: Which Chains Are Best for dApps? If you delve into the website of nearly any blockchain project, you're often met with bold claims: their blockchain is the fastest, most user-friendly, cheapest, and boasts millions of users now or will very soon. So, with this vast array of blockchains and ecosystems, how do you pick the right one? In my view, the answer is clear-cut: if the blockchain is EVM-compatible, you're already halfway there. EVM, or Ethereum Virtual Machine, backed by the Ethereum Foundation, is a standard that any blockchain project can adopt. Critically, all tools for testing, debugging, deployment, linting, explorers, etc., will seamlessly integrate with this new chain. This means that if you create a dApp for one EVM-compatible project, it can, with minimal configuration, work across nearly all others. Sounds like magic, right? Regarding non-EVM compatible projects, for them, you must have a clear rationale. Recognize that targeting these chains may limit your user base, offer fewer tools, and present more unprecedented bugs. The smart contract languages also differ, sometimes drastically. Here are the languages used for smart contract development in the top 20 capitalization projects: Solidity, Plutus, and FunC. Each of these languages is tailored specifically for individual blockchains. Grasping each requires considerable time, as their operational principles vary substantially. when developing dApps Of course, you can architect your dApp to operate across a majority of these diverse chains. However, that's an advanced move and quite time-consuming. Straddling two worlds isn't always straightforward. Let's dive right back into building our dApp with the newfound knowledge at our disposal. For this walkthrough, I'll be using the Gnosis Chain as our EVM-compatible blockchain. It's an L2 network that boasts cost-efficient transactions. For several years now, I've deployed a public notes smart contract on it, allowing users to create textual notes under their usernames. You can find it at this address: `0xf6b270136Da7F8a2113B93a3b9Eeaf5160C45bA0`. To read data from this contract, you first need to instantiate a provider. A provider essentially acts as an RPC API to a specific blockchain node. The server delivering the data is already in sync with the blockchain network and provides the most up-to-date state. const provider = new JsonRpcProvider('https://rpc.gnosischain.com/'); To fetch data from our contract, we'll create an instance of `Contract` from `ethers`. const contract = new Contract('0xf6b270136Da7F8a2113B93a3b9Eeaf5160C45bA0', notesAbi, provider); If I had linked my contract address with a .eth domain, then you could access the contract like this. const contract = new Contract('myapp.eth', notesAbi, provider) In this instance, we're passing in my smart contract's address, the provider, and the ABI (Application Binary Interface). The ABI ensures that the node can interpret state data from binary correctly. The ABI content is quite detailed for this article, so I've moved it to a separate URL. Next, we need to prepare the username in the required format to use it for data retrieval: const usernameHash = keccak256(toUtf8Bytes('igor')); Then, you can fetch all the records I've saved in the smart contract like this: const items = await contract.getNotes(usernameHash); You can check out the entire code for `App.tsx` . here Also, a quick heads-up: In the example, I'm using a free provider. If you're scaling a dApp with a significant user base, it might not be suitable. In such cases, you'd either want to set up your node or opt for paid providers from services like Alchemy or Infura. Funding Your Idea Through Grants In the fast-paced world of dApps, innovative ideas can often operate at a loss for extended periods. It's great if you've got a plan to turn a profit swiftly and a few thousand dollars to sustain yourself in the meantime. But if you don't, fret not. Ideas with sound financial potential always catch the eye of venture angels and investors. But in the Web3 universe, innovation is additionally fostered through grants provided by major foundations such as Ethereum, Binance, and Optimism. These grants are often disbursed without any strings attached, either in phases or as a lump sum. Unlike venture capital, grants don't come with the business obligations typical of angel investors. Projects awarded grants from a specific foundation should, in the long run, positively impact that specific ecosystem. The conditions and allocated amounts vary from one foundation to another, with grant amounts ranging from hundreds to hundreds of thousands of dollars. These are often disbursed in the project's native tokens. To gauge if your project idea aligns with a particular grant program, study previously awarded grants and benchmark against your own. Do you think you can deliver something similar or even better? You're likely grant material. But bear in mind that securing a grant can be a long process. Despite being a fantastic avenue to bring your project to life, be prepared for stage to take weeks or even months. The stages you'll navigate are: each Application Preparation. Many grant applications are straightforward. You'll be detailing your idea and showcasing your team's expertise. Put forward a compelling pitch about both the project and the team. Lack of experience in Web3 might reduce your chances of securing a grant. Project Evaluation. After submitting your application, anticipate a long evaluation phase. The higher the grant amount requested, the longer the evaluation. Typically, you'll receive an approval or rejection email. However, some projects might ghost your application. A month post-submission, don't hesitate to follow up on the application status. And feel free to apply to multiple foundations. Some projects might even qualify for grants from various foundations. Just be wary of potential conflicts of interest and clarify the feasibility of securing multiple grants upfront. Contract Signing. Post-grant approval, you'll engage in a phase of document preparation and signing by all committee members. While you can often start working before the contract signing, there's no guarantee that the contract will get finalized. The hold-up isn't always on the foundation's end; sometimes, sanctions might prevent a grant's disbursement based on your citizenship or residency. Project Acceptance. Acceptance of your grant can be slow-paced. Every committee member will thoroughly vet your solution. Prep a top-tier demo of your project since some members might have less technical knowledge and will evaluate based solely on your demo resources: demo sites and video presentations. Grant Payout. Post a successful grant review, the approval decision goes to accounting. Here, too, payments can get held up, especially if multiple people's confirmations are required. Often, these individuals are engaged across various projects, not just grants. To obtain a list of nearly all projects offering grants, search for "List Web3 Grants" online. As you can see, if you have experience in web2 development, not all concepts in web3 will be clear at first. Many things might raise questions. Nevertheless, this article calls for a part 2, where we could build a full-fledged application using different networks, with the capability to store data in a decentralized manner, as well as interact with smart contracts either at the user's expense or the developer's. See you in the next part!

Dive Into dApps: Your Ultimate Guide to Start Crafting Them Today!

The Evolution of Discoverability: Navigating the Polygon Ecosystem In an age where technology evolves faster than our ability to adapt, the digital universe presents an expansive frontier. Within this vast expanse lies the Polygon ecosystem, a treasure trove of decentralized applications (dapps) promising to reshape the future. But, as with every digital horizon, the challenge remains: How do we traverse this landscape effortlessly? The rise of the Polygon network has been nothing short of meteoric. Lauded for its scalability and efficiency, it has become the choice platform for a multitude of dapps ranging from decentralized finance (DeFi) to gaming (GameFi), digital identities, and even the next generation of social networks. The sheer diversity is dazzling, but therein lies the problem — discoverability. Discovering the Undiscovered Imagine standing before a library with millions of books, but no catalog or system to locate the one you want. This is precisely the challenge users face within the Polygon ecosystem. While developers and tech enthusiasts might find their way through sheer experience or technical prowess, the average user — intrigued by the promises of web3 — finds themselves overwhelmed. This presents a paradox. On one hand, the Polygon ecosystem promises decentralization, autonomy, and unparalleled innovation. On the other, the sheer volume and complexity pose a formidable barrier to the very audience it hopes to serve. The Need for Intuitive Interfaces Enter the importance of intuitive platforms. Just as Google made the vast internet searchable and Apple’s App Store made thousands of apps accessible with a single touch, the Polygon ecosystem needs its navigator — a compass guiding users to the dapps most relevant to them. Moreover, in an age where user experience determines the adoption and success of a platform, it's paramount that this navigator isn't just functional but also user-friendly. This involves integrating sophisticated backend processes with front-end interfaces designed with the layman in mind. Kresus SuperApp: Unveiling a Revolutionary Marketplace for Polygon Dapps The line that distinguishes our digital present from the decentralized future blurs a little more today, as Web3 pioneer Kresus unveils a groundbreaking solution: the Kresus Marketplace. It's not just any marketplace; it's an intelligently curated space to explore the expansive world of dapps within the Polygon ecosystem. : Vested Interest Disclosure This author is an independent contributor publishing via our . Be it through direct compensation, media partnerships, or networking, the author has a vested interest in the company/ies mentioned in this story. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR brand-as-author program A Seamless Entry to Web3 Picture this: a universal portal where you can effortlessly navigate the myriad decentralized applications within the rapidly evolving Polygon network, without the usual learning curve. Kresus, with its SuperApp, has once again demonstrated that such a concept isn't confined to the realms of sci-fi. Building on the robust foundation of the Kresus SuperApp—a combined crypto wallet and gateway to Web3's marvels—the Kresus Marketplace is designed to redefine user experience. Collaboratively engineered with Polygon Labs and harnessed by the innovative Meroku’s Protocol, it integrates the functionalities of a dapp browser, streamlining it with a web3 interface that rivals even the slickest app stores of the web2 era. Polygon: The Nexus of Innovation Why Polygon? As a thriving hub for dapps across a gamut of sectors—from decentralized finance (DeFi) to GameFi, digital identity solutions, and the ever-emerging social networks—the answer seems clear. This integration aims to leverage Polygon's prolific ecosystem, allowing Kresus users to dive deep into a diverse array of decentralized applications. Ravikant Agrawal of Polygon Labs shares the enthusiasm, noting, “The collaboration with Kresus unlocks an unprecedented platform for projects in our ecosystem, paving the way for accelerated growth.” Such strategic alliances highlight the dynamic potential of Web3, signaling a future where the line between conventional web and blockchain becomes almost indistinct. Elevating User Experience Trevor Traina, the visionary CEO and Founder of KresusLabs, elaborated on this partnership's essence: "Our alignment with Polygon is a testament to the wave of innovation Web3 promises. Our objective with the Marketplace is clear—to familiarize users with this new digital frontier, ensuring that web3 becomes as indispensable as the internet itself." The integration is monumental, not just in its scope but in the user-centric approach it represents. By wrapping the intricacies of onchain applications within a user-friendly environment reminiscent of web2, Kresus Marketplace is bridging the chasm between these two digital worlds. A Comprehensive Ecosystem The release of Kresus Marketplace isn't an isolated endeavor. To enhance its commitment to providing an unparalleled access route to the Polygon ecosystem, Kresus will introduce tools like Kresus Connect. This SDK promises a seamless integration with handpicked Polygon projects, enhancing the scope and reach of both the SuperApp's users and the Polygon community. A Confluence of Tradition and Revolution From traversing virtual realms in metaverses to crafting unique digital identities, Kresus aims to make the digital transformation effortless. Users can now interact with the Polygon ecosystem without the complexity of exporting account specifics, seamlessly melding the familiar with the revolutionary. Concluding Thoughts The launch of Kresus Marketplace is emblematic of a broader industry trajectory. As blockchain and Web3 technologies gain traction, their integration into everyday applications will define the next digital age. With Kresus leading the charge, we stand on the cusp of a new era where the potential of the decentralized web will be within everyone's grasp. For those keen to immerse themselves in this confluence of technology and innovation, Kresus promises a front-row seat. Dive into the future, today: . Kresus

Unlocking the Polygon Universe: Kresus Unveils Revolutionary Dapp Marketplace

The past few months have been extremely exciting for web3 developers in the Ethereum ecosystem. While there have been several interesting developments around scalability and better user experience, arguably the biggest offering to come out this year has been Consensys’ zkEVM chain , which released to mainnet on July 11, 2023 and in the first few days has . Linea shows a lot of promise in solving the most pressing problems plaguing public blockchains: speed, scale, and cost. Linea already processed over half a million transactions Let’s try it out. We’ll build our very own crowdfunding dapp and deploy it to using Infura, Truffle, and MetaMask. Linea Linea: an EVM-compliant L2 Linea is an L2 scaling solution known as a (or zk-rollup, for short). These rollups enable developers to offload data and computations from the main chain while guaranteeing the security of the latter. It does so by employing a cryptographic method called zero-knowledge proofs which allows Linea to prove and verify transactions, but the Ethereum blockchain still provides the security. zero-knowledge rollup Effectively, this leads to the creation of a supplemental chain (an L2) where transactions are blazing fast and extremely cheap. Linea can handle more transactions per second than Ethereum while guaranteeing a faster time to finality and at a fraction of the costs. Linea is also Ethereum Virtual Machine (EVM) compliant (a zkEVM). In other words, all the tools, programming languages, and design patterns will work and behave in exactly the same way as they do on Ethereum. It’s all about high scalability and low cost all while being developer friendly. Building on Linea is best done through Infura, which is also built by Consensys. Because these two products are well integrated, you can begin building and deploying your dapps in a matter of minutes. The Linea testnet, which has been active for about three months, has seen over 5 million unique addresses created and over 40 million transactions. And now with the mainnet launch, projects and developer adoption should only accelerate. So let’s start building that dapp. Create a crowdfunding dapp on Linea Step 1: Sign up for an Infura account First we need an Infura account. We need this for two purposes: to get free lineaETH from Infura’s faucet, and to get access to an RPC endpoint through which we can deploy our smart contract and conduct transactions. If you haven’t done so already, . Next, navigate to the and create a new key from the top right. sign up for an Infura account dashboard For network, choose You can name your key/project anything you want. Web3 API. After creating your key, you’ll be redirected to your new project’s dashboard where you will be able to see a section called Endpoints. Here, you’ll find both the testnet and mainnet endpoints of Linea. Take note of both. In this project, we will be deploying to the testnet but we will also go through the instructions you need to follow in order to deploy a real dapp to the mainnet. Step 2: Install a web3 wallet like MetaMask To pay gas fees and sign transactions, we need a self-custodial crypto wallet. For this tutorial, we will use MetaMask, a free and proven wallet. At the time of writing, MetaMask is the most popular wallet in the world. . Download MetaMask as a browser extension here If this is your first time using MetaMask, you’ll be prompted to complete a series of steps that end with generating a wallet recovery phrase. . Not only will you need it later, but losing it means you will also lose access to your wallet. Store this carefully After setting up your wallet, navigate to the top left and click on the Network dropdown. Here, toggle You should see the network. Switch to this; we will be operating on this chain for the rest of the tutorial. Show Test Networks. Linea Goerli Step 3: Acquire lineaETH through the Infura faucet To pay for gas, we need lineaETH. Fortunately, since we’re working on a testnet, we can obtain free test ETH from . You might be required to sign in with your Infura account to obtain funds. Infura’s Linea faucet Once this is done, you should see a small balance of lineaETH in MetaMask. Step 4: Install node and npm using Truffle In order to create and configure a Truffle project (which is where we will write and deploy our smart contracts), we need node and npm on our local machine. . Get them here Once this is done, you can check that they’ve been installed correctly by checking their version numbers on the Terminal. $ node -v
$ npm -v Step 5: Create a Truffle project With node and npm installed, we’re ready to create our Truffle project. Open a terminal and run these commands: $ mkdir crowdfund && cd crowdfund
$ npm init -y
$ npm install –global truffle
$ truffle init
$ truffle test Next, we’ll install the dotenv and the HD Wallet Provider packages. The former will help keep our credentials secret and safe, whereas the latter will allow us to integrate MetaMask with our Truffle project. $ npm install @truffle/hdwallet-provider dotenv Step 6: Write the Crowdfunding smart contract Now let’s write our smart contract! We’ll keep it very simple to start, but you can add more advanced functionality to this contract as needed. The smart contract will set a value as the goal amount, and the public will be invited to pool funds for the project. The funding will be open for a set period of time. Once this period expires, if the amount pooled is greater than or equal to the goal, the owner of the contract will be able to withdraw the funds from the contract. Otherwise, funds will be released back to the origin wallets. Open the Truffle project created in the previous step in your code editor. Next, create a file called in the folder called , and add the following: Crowdfunding.sol contracts // SPDX-License-Identifier: MIT
pragma solidity ^0.8.4;

contract Crowdfunding {
    address public owner;
    uint public goal;
    string public description;
    uint public deadline;

    uint public totalFunds;
    bool public withdrawn;
    mapping(address => uint) public contributions;
    address[] public investors;

    constructor(uint _goal, string memory _description, uint _deadlineBlockCount) {
        // Define goal, project description, and deadline
        goal = _goal;
        description = _description;
        deadline = block.number + _deadlineBlockCount;

        // Set owner to deployer of the contract
        owner = msg.sender;
        withdrawn = false;
    }

    function contribute() public payable {
        require(block.number <= deadline, "Funding period has ended.");

        // Add amount to total funds
        totalFunds += msg.value;

        // Add wallet to investor list and amount to contributions dictionary
        contributions[msg.sender] += msg.value;
        investors.push(msg.sender);
    }

    function withdraw() public {
        require(block.number > deadline, "Cannot withdraw before the deadline.");
        require(!withdrawn, "Funds have been withdrawn.");

        withdrawn = true; // prevent re-entrancy attacks

        if(totalFunds >= goal) {
            // If goal was reached, transfer the funds to the owner
            payable(owner).transfer(totalFunds);
        } else {
            // If goal was not reached, refund investors
            for(uint i = 0; i < investors.length; i++) {
                address investor = investors[i];
                payable(investor).transfer(contributions[investor]);
            }
        }
    }

    function isGoalReached() public view returns (bool) {
        return totalFunds >= goal;
    }
} Make sure everything is working by compiling the contract using: $ truffle compile If all goes well, the output should look something like this: Compiling your contracts...
===========================
> Compiling ./contracts/CrowdFunding.sol
> Artifacts written to /Users/rounakbanik/paulie/crowdfund/build/contracts
> Compiled successfully using:
   - solc: 0.8.20+commit.a1b79de6.Emscripten.clang Step 7: Connect your project to Infura and MetaMask Let’s now configure our Truffle project to work with Infura and MetaMask. As a first step, create the file in the root directory and add the following code: .env MNEMONIC=”< Metamask Wallet Recovery Phrase >” Next, let’s configure Truffle to work with Infura. Add the following code to : truffle.config.js require('dotenv').config();
const HDWalletProvider = require('@truffle/hdwallet-provider');
const { MNEMONIC } = process.env;

module.exports = {
  networks: {
    development: {
      host: "127.0.0.1",
      port: 8545,
      network_id: "*"
    },
    linea_goerli: {
      provider: () => new HDWalletProvider(MNEMONIC, `<INFURA LINEA TESTNET RPC>`),
      network_id: '59140',
    },
    linea_mainnet: {
      provider: () => new HDWalletProvider(MNEMONIC, `< INFURA LINEA MAINNET RPC>`),
      network_id: '59144',
    },
  }
}; Step 8: Deploy the smart contract to Linea via Infura RPC As a final step, let’s create a deployment script in the folder. Name it . Add the following: migrations 1_deploy_contract.js const Crowdfunding = artifacts.require("Crowdfunding");

module.exports = function(deployer) {
  // Arguments are: contract
  deployer.deploy(
    Crowdfunding,
    // _goal
    web3.utils.toWei("10", "ether"),
    // _description
    "Test Project",
    // _deadlineBlockCount
    10000
  );
}; Now deploy the contract: $ truffle migrate --network linea_goerli You’ll see something like: Compiling your contracts...
===========================
> Everything is up to date, there is nothing to compile.


Starting migrations...
======================
> Network name:    'linea_goerli'
> Network id:      59140
> Block gas limit: 30000000 (0x1c9c380)


1_deploy_contract.js
====================

   Deploying 'Crowdfunding'
   ----------------------
   > transaction hash:    0x3e2889c9b6f8b05d99c482a617893cf34eae4fea...
   > Blocks: 2            Seconds: 18
   > contract address:    0x64ccE52898F5d61380D2Ec8C02F2EF16F28436de
   > block number:        414030
   > block timestamp:     1680726601
   > account:             0xc361Fc33b99F88612257ac8cC2d852A5CEe0E217
   > balance:             0.185605297028804606
   > gas used:            1704607 (0x1a029f)
   > gas price:           2.500000007 gwei
   > value sent:          0 ETH
   > total cost:          0.004261517511932249 ETH

   > Saving artifacts
   -------------------------------------
   > Total cost:     0.004261517511932249 ETH

Summary
=======
> Total deployments:   1
> Final cost:          0.004261517511932249 ETH Congratulations! The smart contract is now live on Linea. Notice that we’ve done all this using tools and development environments built for the Ethereum network. Also, notice how we’ve made deployment possible at an extremely cheap transaction cost. That’s the combined beauty of Linea — EMV-compliant, fast, and cheap. Now that your crowdfunding contract is live and working on Linea testnet, it’s time to take it to mainnet! There your supporters will be able to invest in your project by paying a negligible amount of gas and still get the contract enforcement guaranteed by Ethereum. To deploy to mainnet, simply switch the RPC endpoint when you deploy the contract: $ truffle migrate --network linea_mainnet Conclusion Hopefully you’ve learned what Linea is all about, how it makes Ethereum better, and how you can deploy your own smart contract on the network. To learn more, and start building! check out the Linea site

Building Your Own Crowdfunding Dapp Using Infura and Linea

Blockchains allow for lots of novel use cases that leverage their open and decentralized tech, but the industry is still nascent, with lots of hurdles for user adoption. Let’s discuss how we can minimize these hurdles to bring blockchain tech to the masses, without them even knowing about it. The Need for Wallets Typically, using a blockchain requires using a piece of software called a “wallet” to store your private key. These wallets often take the form of extensions for popular web browsers (like Google Chrome). There are downsides to this, such as the fact that not all wallets support every blockchain, often resulting in users having to install multiple wallets. The main reason to use a wallet is to manage your private key, allowing you to repeatedly access the same account, which is important if you are storing valuable assets such as tokens or NFTs on that account. These tokens are needed to pay transaction fees on blockchains, allowing users to use the network. But what if you could use a blockchain without a wallet? A Wallet-Free Experience There are two methods of storing private keys locally (on a user’s computer), without using a wallet. The first is to use an Iframe app (like Login with Google), and the second is to simply store the private key in the local storage. By using one of these methods, a user no longer needs a wallet. Applications can sign transactions on behalf of users. Obviously, this can present security risks, but users can use this setup for things that are low stakes, such as liking a post on a social network. However, if this user needs tokens in order to interact with the network, they will likely still want to use a wallet, in order to better manage and secure their tokens. It is worth noting that not all blockchain users necessarily need tokens. , a Web3 social platform, uses a system called Energy to enable dapp developers to easily cover the transaction fees of users. This can be done with just a of code: Subsocial few lines const burnAmount = 1 // 1 SUB
const parsedBurnAmount = burnAmount * 10 ** 10 //SUB token uses 10 decimals
const target = '3osmnRNnrcScHsgkTJH1xyBF5kGjpbWHsGrqM31BJpy4vwn8'
const tx = api.tx.energy.generateEnergy(target, parsedBurnAmount.toString()) Test it live on the . Subsocial Playground As a result of this, if a dapp supports the energy system, users of that dapp don’t even need to think about tokens — they can just use the application. By combining these two points, users can sign into decentralized applications using their locally-stored private key, with their public key acting as their user ID, and they will not need tokens (thanks to Subsocial’s energy system). In this way, anyone can interact with a blockchain without installing and setting up a wallet. This is similar to the classic Web2 model where anyone can create an anonymous account on a forum and start using it right away to discuss any topic in the world. A great example of this in Web3 is , an anonymous and censorship-resistant chat application powered by Subsocial. Grill.chat However, unlike in Web2, users don’t even need to create an account to get started chatting on Grill.chat, they just need to send a message, and an account will be generated for them, along with some energy. Not all blockchain use cases require wallets and token ownership, and Subsocial’s is a great example of pioneering ways to onboard more users to Web3, without them even realizing it. We are moving towards a time where people will be using blockchain tech without knowing it, and solutions like this help move us toward that future. Grill.chat Resources Wallet-free On-Chain Chat Experience: https://grill.chat Subsocial Network: https://subsocial.network Try Energy System on Subsocial Playground: https://play.subsocial.network/energy/generate Subsocial Developer Chat: Join Now

DAPP

dapp.mx

51-200 employees

Since 2016

COMPANY RANKING

DAPP

EVERGREEN INDEX #4585

Representing this company? Click here to claim and customize this page!

Dapp WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

DAPP

dapp.mx

51-200 employees

Since 2016

COMPANY RANKING

DAPP

EVERGREEN INDEX #4585

RELATED COMPANIESRANK

STORIES ABOUT DAPP

Representing this company? Click here to claim and customize this page!

Dapp WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!