Subscribe to Base Korea 대한베이스
<100 subscribers
Subscribe to Base Korea 대한베이스
<100 subscribers
interviewer : Team Infra402 - Sanghyeok, Yeongmin
The ‘Meet Base Builders’ article series interviews teams in Korea building products on Base Chain to share their firsthand experiences and insights.
These stories aim to serve as a practical roadmap for new builders looking to enter the Base ecosystem, as well as for those seeking to challenge themselves with the various opportunities Base offers, such as hackathons and developer events.
On November 29, the "Qwen SKYST Hackerthon on Base" Demo Day, co-hosted by Base, Alibaba Cloud, and Flock.io, took place with great success.
The hackathon centered on two key tracks—developing Base Mini Apps and building on the x402 Platform—leveraging AI applications integrated with Flock.io’s API. Ten finalist teams engaged in intense pitching battles for a total prize pool of $17,000, with Developer Ambassador logen joining the panel to serve as a distinguished judge.
In this edition of 'Meet Base Builders,' we sat down with team "infra402," who emerged victorious from the fierce competition, to cover the story of their passionate hackathon journey.
Daehan Base offers a wide range of information and events for new Base Builders! Connect with Daehan Base through the official channels below.
Daehan Base X: https://x.com/daehan_base
Daehan Base TG: https://t.me/daehanbase
Base Korea Developer Group TG: https://t.me/daehan_base_devs
Q. It’s a pleasure to meet you, Base Builders! Could you please introduce yourselves?
Sanghyeok: Hello, I’m Sanghyeok. I spent a long time active as a "Degen" in the crypto market, but I eventually became captivated by blockchain technology itself, which led me to enter the field of computer science. Currently, I am a junior developer building diverse experiences within the Web3 ecosystem.
Yeongmin: I was originally a student studying computer science, with a focus on Large Language Models (LLMs). Since the middle of this year, I joined forces with Sanghyeok, and we are now active members of the blockchain community ‘PDAO,’ diving into Web3 development together.
Q. Congratulations again on winning the hackathon! Did either of you have prior experience with the Base ecosystem or other Web3 development?
Sanghyeok: I have traded on Coinbase before, but this was my first time directly utilizing the Base chain ecosystem for development. As for Web3 development experience, I have been challenging myself in various hackathons since the middle of this year, exploring different chains like Solana and Monad rather than limiting myself to just one. Along the way, I also achieved success by placing in a recent Monad Ideathon.
Yeongmin: I also entered the Base ecosystem for the first time through this hackathon. Since the middle of this year, I have been building my Web3 development experience by teaming up with Sanghyeok to compete in various hackathons.
Q. You experienced the Base ecosystem firsthand through this hackathon. Was there anything you felt was particularly different compared to other chains?
Yeongmin: It might be specific to this event, but I really appreciated having a clear theme and tools like the ‘x402 protocol.’ It made concreting the PoC (Proof of Concept) much smoother. Usually, other hackathons have such broad tracks that we spend a lot of time on ideation, but this Base hackathon clearly presented utilization components like the Base Mini App and x402, making it very efficient to set our development goals.
Sanghyeok: I was impressed by the convenience from a development perspective. Early-stage products often have insufficient documentation, but the official docs for Base-related technologies were organized very concisely and clearly. Thanks to this, the development process was very smooth, even though we were working with new technology.
Q. Please briefly explain the Infra402 project.
Sanghyeok: Infra402 is a project focused on resolving the complex payment procedures and difficult UI issues found in existing cloud services to maximize user experience (UX). The key lies in simplifying processes using the x402 protocol. Users can utilize cloud hosting as easily as working in a local environment simply by conversing with a chatbot, without the need for complex configurations.
Q. What idea inspired you to start this project?
Yeongmin: During college, I studied cloud architecture deeply and even obtained an AWS certification. However, whenever I used existing cloud services like AWS or GCP, I felt the barrier to entry was high due to complex credit card registration procedures and unintuitive UIs. In particular, the PAYG (Pay As You Go) model had a fatal flaw: it was difficult for users to estimate expected costs.
Sanghyeok: That's correct. Especially with the recent rapid growth of the AI Agent market, the demand for cloud services among individual developers is exploding. However, it is still very difficult for beginners to handle existing services immediately.
Yeongmin: As someone who enjoys "Homelabbing," I wanted to simplify the complex processes involved in setting up a server. So, I planned a product where "if the user states the desired specifications, an AI agent automatically builds it." Technically speaking, it’s a structure where AI controls Proxmox, a Linux-based virtual machine management platform, combined with the x402 protocol. We built a new business model by allowing the costs for AI-managed cloud resources to be processed via x402 through high-frequency micropayments.
Sanghyeok: To summarize, we implemented "external hosting that is as easy as local hosting" by simplifying payment and settlement processes through x402 and innovating the UX with a chatbot interface. We wanted to verify the hypothesis that if the user experience (UX) becomes drastically more convenient, users will be willing to pay for it.
Q. Recently, 'x402' has been a hot topic in the industry. How do you two evaluate x402?
Sanghyeok: I would define x402 not just as next-generation payment infrastructure, but as the "Industrial Revolution of Finance." Most current internet revenue models rely on ad exposure. However, as the AI era arrives in 2025, direct traffic to original websites is decreasing, and AI summarizing information is becoming common. This implies the collapse of the existing ad revenue model. At this juncture, x402 transforms the calls and interactions between AI agents themselves into a means of value creation. I believe the next-generation financial revenue paradigm, going beyond advertisements, lies right here.
Yeongmin: As a developer, I have used various LLM tooling, but I thought the issue of "payments between agents" was too complex to dare solve. However, as soon as I encountered the x402 protocol, I was convinced, thinking, "This is it!" In a future where all processes are automated by AI agents and workflows, I believe x402 will become the most critical element of the payment system.
Q. Why did you decide to build this project at the Base Hackathon and on the Base chain?
Yeongmin: Since the x402 protocol is a technology led by Coinbase, we determined that support would be most reliable on the Base chain, which serves as its foundation. In reality, the quality of documentation we encountered during the process was incomparably organized relative to other chains, allowing us to focus solely on development.
Sanghyeok: The support for development tools was also a decisive factor. Coinbase provides its own x402 Facilitator, which allowed us to implement complex logic with great ease. Thanks to such tooling lowering the initial entry barrier, the process of building an x402-based project was highly efficient.
Q. What does the actual user experience look like?
Sanghyeok: It offers a highly intuitive experience through a FlockAI-based chatbot interface. Everything is ready simply by connecting a wallet, with no need for a separate sign-up process.
When a user enters their desired resources (e.g., 1 Core, 1GB RAM, 10GB Disk, 2-minute rental) into the chat window, Proxmox on the backend actually creates a Linux container. The AI Agent then provides the user with the Lease ID and password for the created container. Users can visually confirm via a VNC screen that the container is running properly. Payment processing and DB storage are handled automatically, and users can easily check the status or extend the usage period just by asking the agent.
Q. Could you share the process of how you built the project during the short hackathon period?
Yeongmin: For efficiency, we established a clear sequence before starting. We proceeded in the order of [Topic Selection → Overall Architecture Design → Core Feature Implementation (x402 authentication & Proxmox API-based wallet integration) → Chatbot Frontend Implementation]. The entire development took about one week. As this was done part-time alongside our academic studies, we could have shortened the timeline significantly had we focused on it full-time.
Sanghyeok: We adopted a Top-down approach. We started by diagramming the entire system structure using draw.io and verifying the data interaction methods of the x402 protocol. The most significant technical challenge during development was determining "how to organically connect containers with wallets." We dedicated a lot of effort to designing this connection.
Q. How did you utilize Agents and other tools during the development process?
Yeongmin: We used Codex 5 Max as our main tool. We processed the Proxmox API documentation into JSON format to train the agent first, and then had it write the necessary code. In particular, we had it output directly as Pydantic data models to apply immediately to the FastAPI backend, which allowed us to secure both development speed and system stability at the same time.
Q. You mentioned this was your first time developing on Base. Where did you mainly get the necessary technical information?
Yeongmin: We relied entirely on the official Base Docs. The documentation was systematically organized, which was a huge help. From a technical perspective, x402 operates as middleware for FastAPI. Thanks to this, applying it to existing code was much smoother than expected. As for the rest of the infrastructure setup, it is similar to the general Web2 technology stack, so you can sufficiently resolve issues by referring to existing web development materials or references.
Related Base Docs: https://docs.base.org/base-app/agents/x402-agents
Q. Could you share the tech stack used in the project?
Sanghyeok: We built the frontend using TypeScript and the backend primarily with Python. In fact, we relied heavily on AI agents for this project. Since the agents provided significant assistance in generating code and implementing logic, the selection of the tech stack itself was not a hurdle in development nor a factor that required deep consideration.
Q. How did you configure the project's system architecture?
Sanghyeok: Our architecture is a hybrid model combining Web2 cloud infrastructure with a Web3 payment system. Since we need to provide cloud services, a Web2-based server architecture forms the foundation, while the user-facing interface utilizes Base Wallet and the x402 Facilitator to integrate with the blockchain.
The major components are as follows:
Proxmox: The core Hypervisor responsible for container provisioning.
LXC: Linux containers created by Proxmox that are actually rented out or held.
Provider Backend: Acts as a type of Paywall. It provisions the container once payment is confirmed.
User-end Backend: Acts as the "brain," handling LLM orchestration and payment execution.
Frontend: The chat interface where the user communicates with the agent.
Yeongmin: Let me explain the step-by-step workflow of how data flows on top of this architecture.
Request: The user requests "resource rental" via the frontend chatbot.
Structuring: The LLM Backend interacts with Flock.io to structure the user's natural language request into a format the system can understand and requests verification from the Provider Backend.
Verification: The Provider Backend queries the x402 Facilitator and the DB to check "payment feasibility" and "resource availability."
Provisioning: Once payment is complete, it activates the LXC (container) in Proxmox VE and records the [Wallet ↔️ Resource] mapping information in the DB.
Response: The LLM Backend receives the access token and endpoint information and delivers it to the chatbot. When usage ends, automatic reclamation and log recording are performed.
Ultimately, it is a structure where [Proxmox Infrastructure → x402 Payment/Verification → Flock.io Chatbot UX] connects smoothly as a single pipeline.
Q. You mentioned that the connection between the x402 Facilitator and Base Wallet is key. I’m curious about the specific operating principles.
Yeongmin: Role of x402: To put it simply, we placed an 'x402 Paywall' on top of an existing infrastructure provider (Proxmox in this case) and built a client to control it. It works by having an LLM agent (or an automation tool like n8n) trained on x402 payment tooling handle the payment process swiftly on the user's behalf to provide the necessary computing resources.
Base Wallet Connection: Honestly speaking, in the initial planning stage, we intended to implement a seamless wallet connection via the Base App. However, given the limited time of a hackathon, it was difficult to find the optimal solution, so for this prototype, we adopted a method where the user inputs their Private Key directly. (Laughs) While this isn't suitable for actual production deployment, it functions without issues for personal services or at the PoC (Proof of Concept) stage.
Q. Do you have any tips for those preparing to build on Base, or for those looking to start Web3 development?
Yeongmin: The most important tip is to 'thoroughly utilize the official documentation.' There is a slang term among developers called RTFM (Read The Manual), meaning that reading manuals carefully is the absolute basic of basics. Especially in the Web3 ecosystem where information is often fragmented, official documentation is almost the only reliable compass that keeps you from getting lost.
To give you a pro tip, Base's official documentation is so concise and well-structured that it has an optimized size for training AI agents entirely. I also started with almost no knowledge of Web3. If you have a fun idea, I recommend you just try building it with excitement rather than fear of the technology.
Q. Many new builders enter Web3 development through hackathons. As hackathon winners, what tips would you give to future participants?
Sanghyeok: 'Selection and focus' are the most important. Don't make the PoC (Proof of Concept) stage too sprawling. The shortcut to winning is to focus on clearly designing one core feature that you most want to show—something that is definitely implementable within the limited time—and focusing on 'finishing' it.
Yeongmin: Believe in the power of 'empathy.' Fellow participants and judges are all developers in the end. Rather than looking for something grand, if you create a service that solves an 'inconvenience I experienced while developing,' it will be a powerful product that elicits empathy from every builder in the room.
Q. Finally, a word for the Base Builders reading this!
Sanghyeok, Yeongmin: "Don't hesitate, Just Build." We also started without knowing anything about Web3, but we challenged ourselves believing in just one fun idea. If you have an idea in your head, don't be afraid to put it into action. And Base is the perfect stage to take that first step.
You could be the star of the next Base development event! Connect with Daehan Base and Base builders through the official channels below to stay informed.
Daehan Base X: https://x.com/daehan_base
Daehan Base TG: https://t.me/daehanbase
Base Korea Developer Group TG: https://t.me/daehan_base_devs
interviewer : Team Infra402 - Sanghyeok, Yeongmin
The ‘Meet Base Builders’ article series interviews teams in Korea building products on Base Chain to share their firsthand experiences and insights.
These stories aim to serve as a practical roadmap for new builders looking to enter the Base ecosystem, as well as for those seeking to challenge themselves with the various opportunities Base offers, such as hackathons and developer events.
On November 29, the "Qwen SKYST Hackerthon on Base" Demo Day, co-hosted by Base, Alibaba Cloud, and Flock.io, took place with great success.
The hackathon centered on two key tracks—developing Base Mini Apps and building on the x402 Platform—leveraging AI applications integrated with Flock.io’s API. Ten finalist teams engaged in intense pitching battles for a total prize pool of $17,000, with Developer Ambassador logen joining the panel to serve as a distinguished judge.
In this edition of 'Meet Base Builders,' we sat down with team "infra402," who emerged victorious from the fierce competition, to cover the story of their passionate hackathon journey.
Daehan Base offers a wide range of information and events for new Base Builders! Connect with Daehan Base through the official channels below.
Daehan Base X: https://x.com/daehan_base
Daehan Base TG: https://t.me/daehanbase
Base Korea Developer Group TG: https://t.me/daehan_base_devs
Q. It’s a pleasure to meet you, Base Builders! Could you please introduce yourselves?
Sanghyeok: Hello, I’m Sanghyeok. I spent a long time active as a "Degen" in the crypto market, but I eventually became captivated by blockchain technology itself, which led me to enter the field of computer science. Currently, I am a junior developer building diverse experiences within the Web3 ecosystem.
Yeongmin: I was originally a student studying computer science, with a focus on Large Language Models (LLMs). Since the middle of this year, I joined forces with Sanghyeok, and we are now active members of the blockchain community ‘PDAO,’ diving into Web3 development together.
Q. Congratulations again on winning the hackathon! Did either of you have prior experience with the Base ecosystem or other Web3 development?
Sanghyeok: I have traded on Coinbase before, but this was my first time directly utilizing the Base chain ecosystem for development. As for Web3 development experience, I have been challenging myself in various hackathons since the middle of this year, exploring different chains like Solana and Monad rather than limiting myself to just one. Along the way, I also achieved success by placing in a recent Monad Ideathon.
Yeongmin: I also entered the Base ecosystem for the first time through this hackathon. Since the middle of this year, I have been building my Web3 development experience by teaming up with Sanghyeok to compete in various hackathons.
Q. You experienced the Base ecosystem firsthand through this hackathon. Was there anything you felt was particularly different compared to other chains?
Yeongmin: It might be specific to this event, but I really appreciated having a clear theme and tools like the ‘x402 protocol.’ It made concreting the PoC (Proof of Concept) much smoother. Usually, other hackathons have such broad tracks that we spend a lot of time on ideation, but this Base hackathon clearly presented utilization components like the Base Mini App and x402, making it very efficient to set our development goals.
Sanghyeok: I was impressed by the convenience from a development perspective. Early-stage products often have insufficient documentation, but the official docs for Base-related technologies were organized very concisely and clearly. Thanks to this, the development process was very smooth, even though we were working with new technology.
Q. Please briefly explain the Infra402 project.
Sanghyeok: Infra402 is a project focused on resolving the complex payment procedures and difficult UI issues found in existing cloud services to maximize user experience (UX). The key lies in simplifying processes using the x402 protocol. Users can utilize cloud hosting as easily as working in a local environment simply by conversing with a chatbot, without the need for complex configurations.
Q. What idea inspired you to start this project?
Yeongmin: During college, I studied cloud architecture deeply and even obtained an AWS certification. However, whenever I used existing cloud services like AWS or GCP, I felt the barrier to entry was high due to complex credit card registration procedures and unintuitive UIs. In particular, the PAYG (Pay As You Go) model had a fatal flaw: it was difficult for users to estimate expected costs.
Sanghyeok: That's correct. Especially with the recent rapid growth of the AI Agent market, the demand for cloud services among individual developers is exploding. However, it is still very difficult for beginners to handle existing services immediately.
Yeongmin: As someone who enjoys "Homelabbing," I wanted to simplify the complex processes involved in setting up a server. So, I planned a product where "if the user states the desired specifications, an AI agent automatically builds it." Technically speaking, it’s a structure where AI controls Proxmox, a Linux-based virtual machine management platform, combined with the x402 protocol. We built a new business model by allowing the costs for AI-managed cloud resources to be processed via x402 through high-frequency micropayments.
Sanghyeok: To summarize, we implemented "external hosting that is as easy as local hosting" by simplifying payment and settlement processes through x402 and innovating the UX with a chatbot interface. We wanted to verify the hypothesis that if the user experience (UX) becomes drastically more convenient, users will be willing to pay for it.
Q. Recently, 'x402' has been a hot topic in the industry. How do you two evaluate x402?
Sanghyeok: I would define x402 not just as next-generation payment infrastructure, but as the "Industrial Revolution of Finance." Most current internet revenue models rely on ad exposure. However, as the AI era arrives in 2025, direct traffic to original websites is decreasing, and AI summarizing information is becoming common. This implies the collapse of the existing ad revenue model. At this juncture, x402 transforms the calls and interactions between AI agents themselves into a means of value creation. I believe the next-generation financial revenue paradigm, going beyond advertisements, lies right here.
Yeongmin: As a developer, I have used various LLM tooling, but I thought the issue of "payments between agents" was too complex to dare solve. However, as soon as I encountered the x402 protocol, I was convinced, thinking, "This is it!" In a future where all processes are automated by AI agents and workflows, I believe x402 will become the most critical element of the payment system.
Q. Why did you decide to build this project at the Base Hackathon and on the Base chain?
Yeongmin: Since the x402 protocol is a technology led by Coinbase, we determined that support would be most reliable on the Base chain, which serves as its foundation. In reality, the quality of documentation we encountered during the process was incomparably organized relative to other chains, allowing us to focus solely on development.
Sanghyeok: The support for development tools was also a decisive factor. Coinbase provides its own x402 Facilitator, which allowed us to implement complex logic with great ease. Thanks to such tooling lowering the initial entry barrier, the process of building an x402-based project was highly efficient.
Q. What does the actual user experience look like?
Sanghyeok: It offers a highly intuitive experience through a FlockAI-based chatbot interface. Everything is ready simply by connecting a wallet, with no need for a separate sign-up process.
When a user enters their desired resources (e.g., 1 Core, 1GB RAM, 10GB Disk, 2-minute rental) into the chat window, Proxmox on the backend actually creates a Linux container. The AI Agent then provides the user with the Lease ID and password for the created container. Users can visually confirm via a VNC screen that the container is running properly. Payment processing and DB storage are handled automatically, and users can easily check the status or extend the usage period just by asking the agent.
Q. Could you share the process of how you built the project during the short hackathon period?
Yeongmin: For efficiency, we established a clear sequence before starting. We proceeded in the order of [Topic Selection → Overall Architecture Design → Core Feature Implementation (x402 authentication & Proxmox API-based wallet integration) → Chatbot Frontend Implementation]. The entire development took about one week. As this was done part-time alongside our academic studies, we could have shortened the timeline significantly had we focused on it full-time.
Sanghyeok: We adopted a Top-down approach. We started by diagramming the entire system structure using draw.io and verifying the data interaction methods of the x402 protocol. The most significant technical challenge during development was determining "how to organically connect containers with wallets." We dedicated a lot of effort to designing this connection.
Q. How did you utilize Agents and other tools during the development process?
Yeongmin: We used Codex 5 Max as our main tool. We processed the Proxmox API documentation into JSON format to train the agent first, and then had it write the necessary code. In particular, we had it output directly as Pydantic data models to apply immediately to the FastAPI backend, which allowed us to secure both development speed and system stability at the same time.
Q. You mentioned this was your first time developing on Base. Where did you mainly get the necessary technical information?
Yeongmin: We relied entirely on the official Base Docs. The documentation was systematically organized, which was a huge help. From a technical perspective, x402 operates as middleware for FastAPI. Thanks to this, applying it to existing code was much smoother than expected. As for the rest of the infrastructure setup, it is similar to the general Web2 technology stack, so you can sufficiently resolve issues by referring to existing web development materials or references.
Related Base Docs: https://docs.base.org/base-app/agents/x402-agents
Q. Could you share the tech stack used in the project?
Sanghyeok: We built the frontend using TypeScript and the backend primarily with Python. In fact, we relied heavily on AI agents for this project. Since the agents provided significant assistance in generating code and implementing logic, the selection of the tech stack itself was not a hurdle in development nor a factor that required deep consideration.
Q. How did you configure the project's system architecture?
Sanghyeok: Our architecture is a hybrid model combining Web2 cloud infrastructure with a Web3 payment system. Since we need to provide cloud services, a Web2-based server architecture forms the foundation, while the user-facing interface utilizes Base Wallet and the x402 Facilitator to integrate with the blockchain.
The major components are as follows:
Proxmox: The core Hypervisor responsible for container provisioning.
LXC: Linux containers created by Proxmox that are actually rented out or held.
Provider Backend: Acts as a type of Paywall. It provisions the container once payment is confirmed.
User-end Backend: Acts as the "brain," handling LLM orchestration and payment execution.
Frontend: The chat interface where the user communicates with the agent.
Yeongmin: Let me explain the step-by-step workflow of how data flows on top of this architecture.
Request: The user requests "resource rental" via the frontend chatbot.
Structuring: The LLM Backend interacts with Flock.io to structure the user's natural language request into a format the system can understand and requests verification from the Provider Backend.
Verification: The Provider Backend queries the x402 Facilitator and the DB to check "payment feasibility" and "resource availability."
Provisioning: Once payment is complete, it activates the LXC (container) in Proxmox VE and records the [Wallet ↔️ Resource] mapping information in the DB.
Response: The LLM Backend receives the access token and endpoint information and delivers it to the chatbot. When usage ends, automatic reclamation and log recording are performed.
Ultimately, it is a structure where [Proxmox Infrastructure → x402 Payment/Verification → Flock.io Chatbot UX] connects smoothly as a single pipeline.
Q. You mentioned that the connection between the x402 Facilitator and Base Wallet is key. I’m curious about the specific operating principles.
Yeongmin: Role of x402: To put it simply, we placed an 'x402 Paywall' on top of an existing infrastructure provider (Proxmox in this case) and built a client to control it. It works by having an LLM agent (or an automation tool like n8n) trained on x402 payment tooling handle the payment process swiftly on the user's behalf to provide the necessary computing resources.
Base Wallet Connection: Honestly speaking, in the initial planning stage, we intended to implement a seamless wallet connection via the Base App. However, given the limited time of a hackathon, it was difficult to find the optimal solution, so for this prototype, we adopted a method where the user inputs their Private Key directly. (Laughs) While this isn't suitable for actual production deployment, it functions without issues for personal services or at the PoC (Proof of Concept) stage.
Q. Do you have any tips for those preparing to build on Base, or for those looking to start Web3 development?
Yeongmin: The most important tip is to 'thoroughly utilize the official documentation.' There is a slang term among developers called RTFM (Read The Manual), meaning that reading manuals carefully is the absolute basic of basics. Especially in the Web3 ecosystem where information is often fragmented, official documentation is almost the only reliable compass that keeps you from getting lost.
To give you a pro tip, Base's official documentation is so concise and well-structured that it has an optimized size for training AI agents entirely. I also started with almost no knowledge of Web3. If you have a fun idea, I recommend you just try building it with excitement rather than fear of the technology.
Q. Many new builders enter Web3 development through hackathons. As hackathon winners, what tips would you give to future participants?
Sanghyeok: 'Selection and focus' are the most important. Don't make the PoC (Proof of Concept) stage too sprawling. The shortcut to winning is to focus on clearly designing one core feature that you most want to show—something that is definitely implementable within the limited time—and focusing on 'finishing' it.
Yeongmin: Believe in the power of 'empathy.' Fellow participants and judges are all developers in the end. Rather than looking for something grand, if you create a service that solves an 'inconvenience I experienced while developing,' it will be a powerful product that elicits empathy from every builder in the room.
Q. Finally, a word for the Base Builders reading this!
Sanghyeok, Yeongmin: "Don't hesitate, Just Build." We also started without knowing anything about Web3, but we challenged ourselves believing in just one fun idea. If you have an idea in your head, don't be afraid to put it into action. And Base is the perfect stage to take that first step.
You could be the star of the next Base development event! Connect with Daehan Base and Base builders through the official channels below to stay informed.
Daehan Base X: https://x.com/daehan_base
Daehan Base TG: https://t.me/daehanbase
Base Korea Developer Group TG: https://t.me/daehan_base_devs
Share Dialog
Share Dialog
No comments yet