Ventirum is a decentralized binary prediction market engine. Users bet YES or NO on the outcome of real-world events — from crypto prices to elections to sports — with settlement on-chain.
Binary Markets
Every question resolves to YES or NO. Simple for users, powerful at scale. Tradable tickets create a liquid secondary market.
EVM-Native & Chain-Agnostic
Deployed on any EVM-compatible chain. Currently live on Avalanche. Designed to extend to Solana and beyond.
Fully Decentralized
Non-custodial smart contracts handle market creation, order matching, and settlement. No central point of failure.
Operator-Ready
The engine is designed to be run by third-party operators under white-label or SaaS agreements, enabling rapid market expansion.
02 / 09Cooperation Framework
Joint Venture Structure
We propose forming a new legal entity that will serve as the sole owner of all Ventirum intellectual property — including source code, documentation, and domain expertise. All future development, commercialisation, and licensing will operate through this entity.
Dev TeamContributes all existing IP: code, docs, know-how
→→
New EntityHolds all rights, drives development
→
LicenseeExternal or internal platform operators
InvestorCapital, business operations & growth
IP Transfer: On incorporation, Ventirum's complete codebase, technical documentation, operational know-how, and all associated intellectual property rights will be irrevocably assigned to the new company. This ensures clear ownership and protects all parties.
03 / 09Ownership
Equity Split — Two Options
Option A — With Signing Bonus
Investor pays each developer a one-time fee upon signing in exchange for a larger equity stake.
Shares
Investor — 70 %
Adam Grodzki — 15 %
Andreas Oehlke — 15 %
One-Time Fee59,000 USDC (≈ €50,000) per developer
Total Upfront118,000 USDC
Option B — No Upfront Payment
No signing bonus is paid. Developers receive a larger equity share to compensate.
Shares
Investor — 50 %
Adam Grodzki — 25 %
Andreas Oehlke — 25 %
One-Time FeeNone
Total Upfront0 USDC
04 / 09Business Model
Two Revenue Channels
Channel A — SaaS / B2B Licensing
Deliver Ventirum as a white-label prediction market engine to external companies. They operate their own front-end and markets; we provide the technology stack and ongoing updates.
Revenue Share10 – 20 %
ModelRecurring license + rev share
TargetWeb3 platforms, fintech operators
Channel B — Own Operator Instances
Run prediction market platforms ourselves under our own or partner brands. All generated revenue, after covering direct operating expenses, flows back to the parent entity.
Revenue Share100 % to entity
ModelDirect operation
TargetRegional market operators
05 / 09Developer Compensation
Monthly Engagement — Two Tiers
Tier 1 — Core Development
10,000 USDC / month / dev
20,000 USDC / month combined
Time Commitment≥ 50 % of working time (min. 75 h/month)
DeliverablesMinimum 2 new features or improvements per month
ScopePlatform development, quality assurance, maintenance, and operational resilience
Additional ScopeEvaluated individually per request, based on time consumption and task complexity
Tier 2 — Extended Engagement
17,600 USDC / month / dev
35,200 USDC / month combined (≈ €15,000 / dev)
Time Commitment≥ 70 % of working time
DeliverablesEverything in Tier 1, plus:
Additional ScopeTechnical analysis, code reviews, and advisory support across all investor-affiliated projects and teams
Expertise AreasWeb3, security, AI, and general technical consulting
Monthly combined cost comparison
Tier 1
20,000 USDC
Tier 2
35,200 USDC
06 / 09Revenue & Governance
Profit Distribution & Decision-Making
Revenue Waterfall
1
Gross Revenue All income generated by the platform
2
Operating Expenses Marketing, infrastructure, hardware, software, business travel, events
3
Net Profit Distributed proportionally according to equity ownership on a monthly basis
!
No Net Revenue? Investor covers all running costs after approving them
Governance
Business DecisionsDev team is consulted, but the investor holds final authority on company representation and product strategy
ObjectiveAll decisions serve the growth and benefit of the company
Expense ApprovalRunning costs require investor acceptance when the company operates at a loss
Joint ConsensusMarketing campaigns, conference attendance, and public representation costs require agreement from both parties
Principle: Revenue is reinvested in the business first. Profit sharing only occurs once all operational costs are sustainably covered. This ensures long-term viability before payouts begin.
07 / 09Exit Terms
Developer Exit Conditions
This venture requires full commitment from all parties. The exit framework is structured to protect the company and remaining stakeholders in every scenario.
Scenario A — Company has no net revenue
If the company is not generating net profit at the time of a developer's departure:
✕ All ongoing revenue rights are forfeited
✕ Monthly salary ceases immediately
✕ Equity shares are forfeited to the investor
Scenario B — Company is profitable
If the company is generating positive net revenue at the time of departure:
→ Company undergoes a fair valuation based on operational revenue
→ Investor purchases the departing developer's shares at the evaluated price
✕ Shares cannot be retained — the exiting developer must sell
Non-Negotiable: On exit, developers cannot retain their equity. The project demands active involvement from all shareholders. Passive ownership is not permitted.
08 / 09Initial Commitments
Roadmap of Priorities
Upon signing, the following items form the initial development roadmap, prioritised and executed collaboratively:
1
Solana Support Build an alternative platform implementation that supports Solana in addition to EVM chains, broadening the addressable market to the second-largest DeFi ecosystem.
2
Guardis Integration Connect the binary market solution with Guardis accounts and wallet infrastructure. Any revenue-share arrangement arising from this integration will benefit the joint venture entity.
3
SPOT Trading for YES/NO Tickets Enable users to trade YES and NO outcome tickets on the SPOT market, adding liquidity and a secondary trading layer to the prediction market.
4
Long-Term Feature Roadmap Develop a comprehensive multi-quarter feature plan and align priorities collaboratively with the investor, ensuring a shared vision for product evolution.
5
Back-Office Requirements & Implementation Plan Discuss operational and administrative tooling requirements with the investor. Design and agree on an implementation timeline for back-office infrastructure.
09 / 09Deep Dive
Market Analysis
Industry research covering market sizing, competitive landscape, fee benchmarks, investment track records, and the Avalanche opportunity gap.