• © Goverland Inc. 2026
  • v1.0.1
  • Privacy Policy
  • Terms of Use
Aventus DAOAventus DAOby0xC30BB22003431D4D2CcA23458282D25F1A2EC9D40xC30B…C9D4

Proposal for the Extension of Business Development Initiative

Voting ended 6 months agoSucceeded

Proposal Overview

This proposal seeks the continued approval of the Aventus Network treasury to fund Matt Nowakowski and his work with the Aventus Community Business Development (ACBD) team on a quarterly basis, following the conclusion of the initial 6-month pilot. The valuable learnings from the first six months have created a powerful path to Aventus 2.0 adoption, prompting a readjustment of our approach and, consequently, our key performance indicators (KPIs).

This proposal outlines our refined strategy and the metrics by which the ACBD team's success will be measured, ensuring we are perfectly aligned with the most effective way to drive Aventus forward!

Motivation: Fueling Growth with a Proven Strategy

The initial 6-month pilot has been a period of aggressive discovery, providing insights into the most impactful avenues for Aventus adoption, as detailed in the accompanying "Six-Month Pilot Summary and Key Learnings Report" document prepared by ACBD.

Our deep dives into both Web2 and Web3 markets have unveiled a nuanced landscape, where we've learned that directly convincing enterprises to incur significant upfront costs for appchain spin-ups, even for compelling solutions, can be a challenging and lengthy process. Similarly, while engaging with the Web3 landscape, we found that its grant-chasing focus often misaligns with our collaborative, solution-driven approach.

But here's the exciting part: this pilot period has been invaluable in validating a more potent approach, one we like to call the "bridge team" strategy.

By fostering specialized teams with combined Web3 and industry expertise (like Atmos and Opalite AI now), who are fiercely incentivized to build and drive adoption for specific use cases, we can dramatically lower the barrier to entry for enterprises and deliver tangible utility faster than we can alone.

This renewal proposal is ultimately about how we take that model and use it to help us hit the previously agreed goals. See more detail in the Six-Month Pilot Summary and Key Learnings Report: https://drive.google.com/file/d/1JoAz3s7qsmYitIYkPcXzU2gWbXTtkJNW/view?usp=drive_link

Pilot Deliverables Summary: Building Momentum and Learning for the Future

Over the past six months we've diligently executed on our initial mandate, adapted swiftly to market realities, and laid a robust foundation for the phase ahead. Here's a look at what we've delivered:

Strategic Foundation & Outreach

  • BD Strategy Development: We developed and finalized a detailed BD strategy, aligned with the Aventus ecosystem’s goals and technical edge. This iterative process was guided by insights from Aventus Network Services and culminated in our "BD Strategy" presentation. For our initial strategy AMA see: https://youtu.be/swQb_ZOVx30 For current approach see Six-Month Pilot Summary and Key Learnings Report: https://drive.google.com/file/d/1JoAz3s7qsmYitIYkPcXzU2gWbXTtkJNW/view?usp=drive_link
  • Targeted Outreach Campaigns: We established comprehensive outreach pipelines, launching several outbound campaigns via platforms like Apollo.io and meticulously building target audience sheets. Our efforts engaged over 450 outbound leads, complemented by 10+ inbound leads and 6 channel partners, significantly expanding our network. For a summary of those see: https://x.com/i/broadcasts/1yoJMoaeMvwKQ

Engagement & Pipeline Development

  • Active Project Engagement: The ACBD team actively engaged with numerous projects, leading to 8 proposals shared across our diverse pipeline.
  • Those led to the formation of Atmos and Opalite AI, as well as their initial clients / pilots, while the rest mature into potential future commitments (including recently mentioned Fund Tokenization Project)
  • Community Communication: We've maintained consistent and transparent communication with the community, sharing our strategy and updates via AMAs [see links above]
  • Upon community feedback requesting more granular updates we’ve switched to weekly videos on Telegram on top of the AMAs.

Appchain Commitments & On-Chain Activity

  • Key Appchain Commitments: We successfully secured 2 out of 3 targeted appchain commitments, bringing two high-potential projects into the Aventus ecosystem, via the new “bridge team” approach: Atmos: Eliminating human error in cargo, see the website here: https://atmos.supply Opalite AI: Replacing human tasks with autonomous drone agents, see the website here: https://www.opalite.cc/
  • Driving On-Chain Activity: We expect a total of 130,000 transactions to hit the Aventus Mainnet over the next 12 months, driven by early client work, including: Atmos’ Airline Clients (Converted MOUs with Kuwait and Oman Airlines, UK Top10 airline coming): Anticipating 100,000 transactions. Opalite AI's Clients (Nuur MX contracted warehouses): Expecting 30,000 transactions. Initial transactions are already flowing, with 10k anticipated in August (depending on exact stock and start times), and a projected 20k in September from both Opalite AI and Atmos (assuming current contracting timelines). See existing live transactions from above here: https://explorer.mainnet.aventus.io/address/0xac79eeaab859c14d4b18d150105b229571a5b9e9cb876066bb8b1257144a0356/ 30k transactions expected on a quarter-by-quarter basis via a mix of Opalite AI and Atmos transactions (posted to Mainnet or their dedicated appchains later)
  • Scalable BD Operations: We've successfully established a scalable framework for our BD operations, as detailed in our Month 5 update linked above, including repeatable outbound campaigns and an efficient inbound channel setup.

Meeting Extension Criteria with Excitement

The initial 6-month pilot had an 'either/or' goal for extension: either securing 3 appchain commitments or driving 100,000 transactions. Our initial benchmark of securing three contracted appchain proposals by the pilot's end was set before we fully understood the sales cycle for the powerful Aventus stack (see Six-Month Pilot Summary and Key Learnings Report" for details). We quickly realized the complexities of achieving this using our initial approach, which led us to pivot our strategy towards forming "bridge teams."

While we didn't directly hit our target of three contracted appchains, this strategic shift has already yielded 2 committed teams (Atmos and Opalite) moving forward both across Aventus Mainnet and appchain deployment. This demonstrates a strong positive signal and indicates we're heading in the right direction.

To ensure a demonstration of progress and provide an onboarding pathway for Atmos and Opalite AI, we also focused on initiating transaction flow. Transactions are already flowing onto Mainnet and will continue to ramp up (see above for live transaction link associated with the committed projects). This powerful combination of strategic commitments and smaller, yet tangible, on-chain activity ensures we're providing compelling evidence of Aventus's growing utility and our work!

Refinement of the KPIs for Ongoing Extension

Our core ambition remains strong – we're still committed to achieving our key targets for appchain launches and treasury contributions as originally outlined, but now have a clearer, more effective pathway to get there, thanks to our "bridge team" strategy.

Our Core Commitments Remain:

  • Appchain Launches and Initial Contributions: We are maintaining our commitment to 3 appchains going live and making their first contributions to the Aventus treasury within this 12-month extension period. We are confident that this will be achieved through the success of Atmos and Opalite AI, along with potential new bridge teams / start ups!
  • Ambitious Treasury Contributions: We are still optimistic about our initially set $2.5 million USD in total appchain treasury contributions goal by end of month 12. Our "bridge team" approach, focusing on quality and incentivized adoption, provides a strong foundation for reaching this ambitious goal.

Adjustments for More Focused Success

While our above core ambitions stand firm, the pilot revealed that fostering new, specialized "bridge teams" is a more deliberate process than traditional "deal" closures. Although the number of teams / appchains spun up and maintained that way may have its capacity limitations, it allows for a bigger number of enterprises onboarded onto Aventus as their clients.

Therefore, to ensure we set ourselves up for continued success and sustained momentum, we propose a slight adjustment to one specific target: Revised Bridge Team Agreements: Instead of the original "6 new appchains agree to launch on Aventus," we propose a more focused target for agreements with new "bridge teams."

This adjustment acknowledges the deeper integration and specialized nature of these partnerships, ensuring each new team is poised for maximum impact.

A “bridge team” is defined as a separate legal entity, designed to take on the risk and development of dedicated solutions for a particular sector of customers / leads driven by the ACBD team in the form of Aventus-first products. The teams are a mix of individuals picked and assembled to address the particular sector in mind (e.g. aviation, AI verticals etc), with ACBD team bootstrapping the GTM role, and external individuals picked for either their Web3 or industry expertise. All individuals involved get equity upside to motivate them in driving the success of the business, while delivering value to Aventus via their clients. The formation of new “bridge teams” does not come at additional cost to the treasury - the individuals involved are driven by potential equity upside and future salaries (if any) stemming from revenue generated by the clients.

Our Quarterly KPIs, Built for Impact

These revised KPIs are designed to capture the value creation of our "bridge team" strategy, focusing on building and scaling crucial intermediary entities and showcasing real-world utility, now framed with quarterly summaries for the first year. We'll set new targets for Year 2 at the end of Q4. If met we automatically roll to the next quarter, if not we explain why to the community and have a vote to continue.

Q1 Targets: Foundation & Launch

Key Focus: Laying the groundwork for appchain launches, initiating treasury contributions, and maintaining initial network activity. Appchain Launch: Launch 1 appchain in production (across Atmos and Opalite). Treasury Contribution: Contribute 5% of token supply to the treasury as a one-off contribution. Mainnet Activity: Achieve 30,000 transactions on Aventus Mainnet from non-appchain activity.

Q2 Targets: Expansion & First Scaling

Key Focus: Launching a second appchain, continuing treasury contributions, introducing appchain scaling, and boosting treasury value from business development. Appchain Launch: Launch 2nd appchain in production (across Atmos and Opalite). Treasury Contribution: Contribute 5% of token supply to the treasury as a one-off contribution. Mainnet Activity: Achieve 30,000 transactions on Aventus Mainnet from non-appchain activity. Appchain Scaling: Achieve at least 50,000 transactions on the 1st appchain for the quarter. Treasury Value (ACBD): Accumulate $250,000 value of tokens in the Aventus treasury from ACBD efforts (across the first two appchain tokens, USD values taken at end of quarter price or liquidated price).

Q3 Targets: Diversification & Accelerated Scaling

Key Focus: Launching a third, new appchain, maintaining treasury contributions, significantly scaling existing appchains, and rapidly increasing treasury value from existing tokens. Appchain Launch: Launch 3rd appchain in production (from a new team). Treasury Contribution: Contribute 5% of token supply to the treasury as a one-off contribution. Mainnet Activity: Achieve 30,000 transactions on Aventus Mainnet from non-appchain activity. Appchain Scaling: Achieve at least 100,000 transactions across the first two appchains for the quarter. Treasury Value (ACBD): Accumulate $1,000,000 value of tokens in the Aventus treasury from ACBD efforts (across all three appchain tokens, USD values taken at the end of the quarter or liquidated price).

Q4 Targets: Full Scaling & Treasury Growth

Key Focus: Maximizing transaction volume across all launched appchains and achieving substantial treasury value through sustained business development. Appchain Scaling: Achieve at least 150,000 transactions across all three appchains for the quarter. Treasury Value (ACBD): Accumulate $2,500,000 value of tokens in the Aventus treasury from ACBD efforts (across all three appchain tokens, USD values taken at token price at the end of quarter or liquidated price) Mainnet Activity: Achieve 30,000 transactions on Aventus Mainnet from non-appchain activity.

Ongoing Long-term KPIs (not part of Quarterly Targets, but tracked quarterly as additional contributions):

These KPIs will be reported on a quarterly basis but are long term in nature, reflecting continuous effort and progress throughout the year.

Bridge Team Development & Traction (Quantitative & Qualitative)

  • Establishment & Growth of Bridge Teams: KPI: Secure and formally integrate a 3rd high-potential "bridge team" (beyond Atmos and Opalite AI) actively developing and deploying solutions on Aventus or with clear plans for an Aventus appchain integration. This includes evaluating or participating in their team structure, industry focus, and go-to-market strategy to ensure a perfect fit with our vision. Measurement: Formal agreement with ANS or passed community proposal, public team announcements, and documented go-to-market plans.

  • Bridge Team Capital Acquisition: KPI: Support and enable at least 1 "bridge team" to secure external funding (e.g., grants, angel investment, seed rounds etc. of at least $200k across sources) to supercharge their development and go-to-market efforts. Measurement: Public announcements of funding rounds or investment/grant.

Community Engagement & Visibility (Enhanced & Empowering)

  • Regular Community Contact: KPI: Establish and maintain more regular and direct contact with the community via platforms like Telegram, beyond just monthly AMAs, building on successful engagement efforts to ensure the community is always up-to-date with progress. Measurement: Weekly TG-based updates as established in July, in between monthly AMAs and quarterly reports.

  • Transparency & Communication: KPI: Continue our monthly progress AMAs, detailing the traction and learnings from the "bridge team" strategy, showcasing transaction volume, and outlining our exciting future pipeline. Measurement: Consistency and depth of reports and AMAs, positive community feedback, and soaring engagement levels.

The Ask from the Community

The ask from the community remains unchanged – to support the activity of the BD team in this new format, we would like to request continued funding with the same structure as in the original pilot proposal.

  • Monthly Retainer: $10,000 USD paid in AVT in monthly instalments, renewed quarterly based on above KPIs, for the time dedicated to BD efforts and leadership of the ACBD team, as well as support to the bridge teams. The amount of AVT will be calculated using the spot rate on CoinGecko at time of transfer, plus 5% for any slippage/fees incurred.
  • BD Team Event Budget: A maximum $2,000 USD in AVT per quarter for travel and attendance expenses to attend key events (requested on a per-need-basis).
  • Team Performance Bonus (excluding Atmos and Opalite AI launches, applicable only on future fully external bridge teams that receive no bootstrapping GTM support from ACBD, if any): A total of 4,000 AVT per passed appchain proposal: 50% payable upon the appchain’s proposal successful governance vote; 50% payable upon appchain’s first deposit into Aventus treasury.

Beyond the appchain’s first deposit into the Aventus treasury, 5% of the total appchain token contributions for the first year are paid out quarterly as bonus to the BD team.

Justification for Our Refined Approach

These goals we’d like to be held against for the coming months are a direct reflection of our validated, high-impact "bridge team" strategy.

They prioritize the critical early stages of establishing these entities, driving initial activity, and ultimately bringing them to full appchain maturity. By focusing on measurable user adoption and external validation (like funding) for these bridge teams, we're forging a more realistic and impactful pathway to Aventus's long-term success. The early emphasis on Mainnet transactions provides immediate feedback and highly visible utility for the community while the more complex appchain spin-ups mature over time.

We are super thrilled about this refined approach! We believe that by focusing on these new metrics, we can more effectively guide our BD efforts, deliver truly transformative results, and clearly demonstrate the utility and adoption of the Aventus Network to our community. The accompanying "Six-Month Pilot Summary and Key Learnings Report" provides the comprehensive rationale and context for this strategic recalibration.

How to Vote

You can either vote on the Ethereum-compatible governance platform or the Aventus-compatible governance platform. The platform you vote on depends on where your AVT is at the start of this vote.

To vote on the Aventus Network governance Dapp: Go to https://voting.mainnet.aventus.io Ensure you have the PolkadotJS browser extension installed on your browser Click on “Connect Your Polkadot Wallet” Once your wallet is connected, click on the proposal you want to vote on Choose the option you want to vote for Sign the voting message

Vote weight: 1 vote per AVT

To vote on Ethereum via Snapshot: Go to https://gov.aventus.io Click on the "Connect wallet" button in the top right corner. You can vote using any of the five compatible wallets supported by the platform. Connect with the wallet provider that you used to stake your AVT or where you hold your AVT Click on this proposal to vote on it Choose the option you want to vote for Sign the message via your wallet

Vote weight: 1 vote per AVT

Off-Chain Vote

For
65.33K AVT100%
Against
0 AVT0%
Quorum:6532935%
Download mobile app to vote

Timeline

Aug 04, 2025Proposal created
Aug 04, 2025Proposal vote started
Aug 11, 2025Proposal vote ended
Aug 11, 2025Proposal updated