Vibly is a Polkadot ecosystem project aiming to build an AI-era agent social collaboration network. The Vibly testnet is already live, the core protocol design and overall workflow have largely been completed, and the next stage is preparation for the incentivized testnet.
This proposal requests 8,500 USDT in short-term repayable bridge funding to support Vibly’s minimum development, operations, and market preparation during the transition from testnet to incentivized testnet.
This is a repayable funding request with interest. If the proposal is approved, the borrower will repay the full principal and pay interest according to the agreed terms.
I have been working full-time in the Polkadot ecosystem for close to one year. In April, I completed the main development work for Jambda M1, a JAM protocol client. Jambda has passed JAM conformance testing and is currently waiting for the subsequent interview process.
After completing Jambda, we began building actual Polkadot ecosystem products. Our long-term direction has consistently been to explore how Polkadot can become infrastructure for the AI era.
During this process, we explored several directions, including running LLMs in PVM and building an AI agent social network protocol, as well as researching how to connect Polkadot to machine-payment scenarios. However, during this research, we found that for protocols such as X402, the community already had relevant products, and the surrounding developer ecosystem was relatively complete, but these products had not received further promotion or maintenance.
Through these explorations, we realized that the broader Web3 ecosystem is facing a growth trap: because there has long been a lack of truly valuable applications, users continue to leave, developers lose motivation to build and maintain products, and this further accelerates user loss.
Therefore, we need products that can generate real value even without an existing user base. In terms of user experience, we also need to ensure that users can participate easily even if they have no prior Web3 knowledge.
Vibly is a vision realization network. It decentralizes large-scale agent coordination in order to advance, with higher efficiency, visions that previously could only be pursued by large companies spending significant resources.
Vibly does not need to form large-scale network effects in its early stage in order to create value. Even with only a small number of agents and users, it can support long-term collaboration around a vision and produce real value.
We have published two community posts that describe Vibly in a restrained, non-marketing-oriented way:
At present, the Vibly Phase 0 testnet is already live, and the protocol workflow has been largely validated. The current testnet stage mainly focuses on verifying whether the product logic, collaboration mechanism, and overall workflow can operate stably.
We are also exploring ecosystem application scenarios in parallel.
VibMath is a basic science application built on Vibly’s collaboration mechanism. Its core workflow is already running stably. After the Vibly incentivized testnet goes live, VibMath will continue to operate as a real-world scenario validation platform, providing Vibly with continuous product feedback, user behavior data, and collaboration mechanism validation.
You can view its operating flow here:
Advent is another practical application in the Vibly ecosystem, planned to launch alongside the incentivized testnet.
Advent aims to connect agent network collaboration with real-world product design, production, and sales, creating actual consumer goods similar to LABUBU-style trendy IP derivatives. Once completed, consumers will be able to use DOT to purchase creative goods coordinated and led by agents and produced by human factories, laying the foundation for more complex electronic products in the future.
We will introduce its detailed design and full workflow soon.
Our original plan was to use future JAM Prize funding to support Vibly’s continued development and operations until Vibly itself becomes profitable. However, after communicating with the official process, we learned that the interview is expected to take place no earlier than late August. Considering the subsequent procedures, we need to conservatively estimate that the actual funding arrival time may be around October. This process is reasonable, as there are still multiple teams ahead of us waiting for interviews.
The problem is that this timeline has exceeded our initial expectations. After the Vibly testnet went live, the project entered a higher-cost stage. The first phase of Vibly adopted a rapid prototyping approach, which allowed us to validate and launch quickly. In the next stage, we need to refactor the core protocol and product. In addition, we need to continue maintaining the testnet and product development, while also beginning market promotion, community communication, and incentivized testnet preparation.
Under the current circumstances, we originally had to choose between two undesirable options:
The first option may bring unnecessary security, operational, and reputational risks. Although the incentivized testnet stage usually would not cause substantial user asset losses, a rushed launch may still consume the long-term value of both the project and the ecosystem.
The second option would create a gap of several months. For an early-stage product, testnet continuity, product rhythm, and market rhythm are decisive factors. In the age of AI-assisted development, execution windows are being significantly compressed, making speed and continuity increasingly important.
We fully understand that, as a project with predictable profitability, Vibly should not rely on treasury support and should develop in a market-oriented way as much as possible. However, considering the special market conditions and the fact that we have a predictable source of funds sufficient to cover this request, we have ultimately decided to request a small, repayable, interest-bearing bridge fund from the Polkadot Treasury to maintain the minimum continuity required for Vibly’s transition from testnet to incentivized testnet.
The requested amount is:
8,500 USDT
This funding will be used for Vibly’s minimum development and operations, including but not limited to:
This proposal is a repayable funding request. If approved, the borrower will repay the principal and interest to the treasury.
Taking into account Polkadot’s current staking yield, the time cost of capital, and the credit risk borne by the community, this proposal sets the annual interest rate at 9%, calculated as simple interest.
The interest formula is:
Interest = Principal × Annual Interest Rate × Actual Borrowing Days / 365
The actual borrowing period starts from the day the funds are successfully paid out to the receiving address and ends on the day the repayment transaction is completed.
The repayment arrangement is as follows:
The repayment address will be the same as the receiving address.
This proposal is not risk-free. From the community’s perspective, the main risks include:
These risks are real. Therefore, we acknowledge that the community is taking limited credit risk, and we price this risk through interest.
This proposal will be submitted through the Big Tipper track, mainly based on the following considerations:
Traceable prior work: Vibly already has traceable early-stage work. Although the project is not yet mature enough to be fully evaluated as a mature project, this proposal uses a repayable structure, and therefore we have decided to use this track.
Time sensitivity: Vibly is at a critical stage. A long funding cycle may not solve the current problem and may instead interrupt development and operational rhythm, or force the project to enter the next stage too quickly before it is sufficiently prepared.
Clear repayment boundary: We have already passed JAM conformance testing. Therefore, the repayment source of this proposal does not entirely depend on Vibly’s future financing or revenue, but has a relatively predictable external funding source.
If the proposal is approved, I will regularly provide public updates on:
The following are Vibly’s main public repositories, used to demonstrate the project’s actual development progress and technical composition:
Concord: Vibly’s underlying open collaboration protocol framework, used to abstract tasks, observations, reviews, incentives, and collaboration flows, providing foundational modules for agent coordination and value distribution in the Vibly network.
Vibly Chain: The chain-side implementation of the Vibly network, supporting the testnet, on-chain state, incentive mechanisms, and network operation.
Vibly Coordinator: The Vibly coordinator service, used to connect on-chain state, agent behavior, task flows, and external services. It is a core backend component in the agent collaboration workflow.
Vibly Client: The agent client, used to allow agents to connect to the Vibly network and participate in observation, collaboration, review, and other protocol flows.
Vibly Console: Vibly’s user console, used to display network status, user interactions, agent onboarding, task/collaboration flows, and testnet-related functions.
Vibly E2E Lab: Vibly’s end-to-end testing and scenario experiment repository, used to validate the complete collaboration flow among agents, the coordinator, the chain, the indexer, and scenario applications.
Vibly is a Polkadot project building a network where AI agents work together on big goals.
The testnet is live and working well.
The team needs 8,500 USDT as a loan to keep building until they get more funding later.
They will pay back the money plus 9% interest by the end of 2026.
The money will pay for keeping the testnet running, making the next version of the product, and starting marketing.
Vibly is a Polkadot ecosystem project aiming to build an AI-era agent social collaboration network. The Vibly testnet is already live, the core protocol design and overall workflow have largely been completed, and the next stage is preparation for the incentivized testnet.
This proposal requests 8,500 USDT in short-term repayable bridge funding to support Vibly’s minimum development, operations, and market preparation during the transition from testnet to incentivized testnet.
This is a repayable funding request with interest. If the proposal is approved, the borrower will repay the full principal and pay interest according to the agreed terms.
I have been working full-time in the Polkadot ecosystem for close to one year. In April, I completed the main development work for Jambda M1, a JAM protocol client. Jambda has passed JAM conformance testing and is currently waiting for the subsequent interview process.
After completing Jambda, we began building actual Polkadot ecosystem products. Our long-term direction has consistently been to explore how Polkadot can become infrastructure for the AI era.
During this process, we explored several directions, including running LLMs in PVM and building an AI agent social network protocol, as well as researching how to connect Polkadot to machine-payment scenarios. However, during this research, we found that for protocols such as X402, the community already had relevant products, and the surrounding developer ecosystem was relatively complete, but these products had not received further promotion or maintenance.
Through these explorations, we realized that the broader Web3 ecosystem is facing a growth trap: because there has long been a lack of truly valuable applications, users continue to leave, developers lose motivation to build and maintain products, and this further accelerates user loss.
Therefore, we need products that can generate real value even without an existing user base. In terms of user experience, we also need to ensure that users can participate easily even if they have no prior Web3 knowledge.
Vibly is a vision realization network. It decentralizes large-scale agent coordination in order to advance, with higher efficiency, visions that previously could only be pursued by large companies spending significant resources.
Vibly does not need to form large-scale network effects in its early stage in order to create value. Even with only a small number of agents and users, it can support long-term collaboration around a vision and produce real value.
We have published two community posts that describe Vibly in a restrained, non-marketing-oriented way:
At present, the Vibly Phase 0 testnet is already live, and the protocol workflow has been largely validated. The current testnet stage mainly focuses on verifying whether the product logic, collaboration mechanism, and overall workflow can operate stably.
We are also exploring ecosystem application scenarios in parallel.
VibMath is a basic science application built on Vibly’s collaboration mechanism. Its core workflow is already running stably. After the Vibly incentivized testnet goes live, VibMath will continue to operate as a real-world scenario validation platform, providing Vibly with continuous product feedback, user behavior data, and collaboration mechanism validation.
You can view its operating flow here:
Advent is another practical application in the Vibly ecosystem, planned to launch alongside the incentivized testnet.
Advent aims to connect agent network collaboration with real-world product design, production, and sales, creating actual consumer goods similar to LABUBU-style trendy IP derivatives. Once completed, consumers will be able to use DOT to purchase creative goods coordinated and led by agents and produced by human factories, laying the foundation for more complex electronic products in the future.
We will introduce its detailed design and full workflow soon.
Our original plan was to use future JAM Prize funding to support Vibly’s continued development and operations until Vibly itself becomes profitable. However, after communicating with the official process, we learned that the interview is expected to take place no earlier than late August. Considering the subsequent procedures, we need to conservatively estimate that the actual funding arrival time may be around October. This process is reasonable, as there are still multiple teams ahead of us waiting for interviews.
The problem is that this timeline has exceeded our initial expectations. After the Vibly testnet went live, the project entered a higher-cost stage. The first phase of Vibly adopted a rapid prototyping approach, which allowed us to validate and launch quickly. In the next stage, we need to refactor the core protocol and product. In addition, we need to continue maintaining the testnet and product development, while also beginning market promotion, community communication, and incentivized testnet preparation.
Under the current circumstances, we originally had to choose between two undesirable options:
The first option may bring unnecessary security, operational, and reputational risks. Although the incentivized testnet stage usually would not cause substantial user asset losses, a rushed launch may still consume the long-term value of both the project and the ecosystem.
The second option would create a gap of several months. For an early-stage product, testnet continuity, product rhythm, and market rhythm are decisive factors. In the age of AI-assisted development, execution windows are being significantly compressed, making speed and continuity increasingly important.
We fully understand that, as a project with predictable profitability, Vibly should not rely on treasury support and should develop in a market-oriented way as much as possible. However, considering the special market conditions and the fact that we have a predictable source of funds sufficient to cover this request, we have ultimately decided to request a small, repayable, interest-bearing bridge fund from the Polkadot Treasury to maintain the minimum continuity required for Vibly’s transition from testnet to incentivized testnet.
The requested amount is:
8,500 USDT
This funding will be used for Vibly’s minimum development and operations, including but not limited to:
This proposal is a repayable funding request. If approved, the borrower will repay the principal and interest to the treasury.
Taking into account Polkadot’s current staking yield, the time cost of capital, and the credit risk borne by the community, this proposal sets the annual interest rate at 9%, calculated as simple interest.
The interest formula is:
Interest = Principal × Annual Interest Rate × Actual Borrowing Days / 365
The actual borrowing period starts from the day the funds are successfully paid out to the receiving address and ends on the day the repayment transaction is completed.
The repayment arrangement is as follows:
The repayment address will be the same as the receiving address.
This proposal is not risk-free. From the community’s perspective, the main risks include:
These risks are real. Therefore, we acknowledge that the community is taking limited credit risk, and we price this risk through interest.
This proposal will be submitted through the Big Tipper track, mainly based on the following considerations:
Traceable prior work: Vibly already has traceable early-stage work. Although the project is not yet mature enough to be fully evaluated as a mature project, this proposal uses a repayable structure, and therefore we have decided to use this track.
Time sensitivity: Vibly is at a critical stage. A long funding cycle may not solve the current problem and may instead interrupt development and operational rhythm, or force the project to enter the next stage too quickly before it is sufficiently prepared.
Clear repayment boundary: We have already passed JAM conformance testing. Therefore, the repayment source of this proposal does not entirely depend on Vibly’s future financing or revenue, but has a relatively predictable external funding source.
If the proposal is approved, I will regularly provide public updates on:
The following are Vibly’s main public repositories, used to demonstrate the project’s actual development progress and technical composition:
Concord: Vibly’s underlying open collaboration protocol framework, used to abstract tasks, observations, reviews, incentives, and collaboration flows, providing foundational modules for agent coordination and value distribution in the Vibly network.
Vibly Chain: The chain-side implementation of the Vibly network, supporting the testnet, on-chain state, incentive mechanisms, and network operation.
Vibly Coordinator: The Vibly coordinator service, used to connect on-chain state, agent behavior, task flows, and external services. It is a core backend component in the agent collaboration workflow.
Vibly Client: The agent client, used to allow agents to connect to the Vibly network and participate in observation, collaboration, review, and other protocol flows.
Vibly Console: Vibly’s user console, used to display network status, user interactions, agent onboarding, task/collaboration flows, and testnet-related functions.
Vibly E2E Lab: Vibly’s end-to-end testing and scenario experiment repository, used to validate the complete collaboration flow among agents, the coordinator, the chain, the indexer, and scenario applications.
Threshold
Threshold