m3taversal
0c93e4a8a4
Co-authored-by: m3taversal <m3taversal@gmail.com> Co-committed-by: m3taversal <m3taversal@gmail.com>
45 lines
2.7 KiB
Markdown
45 lines
2.7 KiB
Markdown
---
|
||
type: source
|
||
title: "Futardio: Diverg fundraise goes live"
|
||
author: "futard.io"
|
||
url: "https://www.futard.io/launch/5mbLJavVEu9hRgEd9Sg2GCQSNMjRWc9t6ZzjamndU64q"
|
||
date: 2026-04-14
|
||
domain: internet-finance
|
||
format: data
|
||
status: unprocessed
|
||
tags: [futardio, metadao, futarchy, solana]
|
||
event_type: launch
|
||
---
|
||
|
||
## Launch Details
|
||
- Project: Diverg
|
||
- Description: Automated security scans + on-chain investigations, with clear and actionable results.
|
||
- Funding target: $25,000.00
|
||
- Total committed: N/A
|
||
- Status: Live
|
||
- Launch date: 2026-04-14
|
||
- URL: https://www.futard.io/launch/5mbLJavVEu9hRgEd9Sg2GCQSNMjRWc9t6ZzjamndU64q
|
||
|
||
## Team / Description
|
||
|
||
Use of funds
|
||
Most of this round goes to hiring. We need more hands on engineering and security-minded product work so we’re not always trading speed against quality. A meaningful slice goes to marketing, not a giant splash campaign, but steady stuff that actually moves the needle: content, events, partnerships, and getting the product in front of teams who should be using it. The rest keeps the lights on: infra, tools, legal, and the boring ops you need so customers don’t get burned by downtime or surprise costs. We’re not trying to fund ten experiments at once; we’re trying to grow the team and get louder in the right rooms while staying solvent.
|
||
|
||
Roadmap and milestones
|
||
Next month is mostly cleanup and reliability: auth, credits, rate limits, the paths people hit every day, plus tests on the security-sensitive pieces so regressions don’t slip through. Over the following couple months we want sharper outputs from what we already built: reports people can share, investigations that don’t oversell what’s heuristic, and strict mode that still means something when it fires red. By roughly ninety days we’d like a small set of teams using us in a repeatable way, with a clearer story we can tell from real usage, not a roadmap full of fantasy features.
|
||
|
||
Market and differentiation
|
||
We’re talking to teams that ship fast, especially in crypto, where “run a scan” isn’t the hard part; figuring out what to trust is. We sit in that gap: automated coverage plus enough depth that an operator can make a call without drowning in noise. We’re not claiming we’ve solved security; we’re building a product that’s honest about blind spots and gets better every ship cycle. Distribution for now is direct: us in the conversation, the product doing the demo, and marketing that points to what actually shipped.
|
||
|
||
## Links
|
||
|
||
- Website: https://divergsec.com
|
||
- Twitter: https://x.com/divergsec
|
||
- Telegram: https://t.me/divergcommunity
|
||
|
||
## Raw Data
|
||
|
||
- Launch address: `5mbLJavVEu9hRgEd9Sg2GCQSNMjRWc9t6ZzjamndU64q`
|
||
- Token: Diverg (DIVERG)
|
||
- Token mint: `DAEusuieHjV3gTaWpr2HcCbPiA1ktbBU7gk6LHjCmeta`
|
||
- Version: v0.7
|