Veilid Framework v0.5.7 is out!
This is a SECURITY release, please update your servers to mitigate denial-of-service attacks.
✅ Debian packages updated ✅ RPM packages updated ✅ Pypi updated ✅ Rust Crates updated
Remote
VeilidNetwork
@VeilidNetwork@masto.hackers.town
mastodon 4.7.3Pronounced: “Vay-lid”.
An official CULT OF THE DEAD COW projekt.
Social Media shouldn’t be monetized.
Users are not a commodity.
Privacy Matters.
0 Followers
0 Following
18 Posts
Joined June 29, 2025
Rise and Reverberate!
Veilid 0.5.4 is released!
Too many fixes to mention, performance is way up, AND …drumroll please….
API is fully documented!
Come and get that sweet, sweet privacy respecting protocol!
https://docs.rs/veilid-core/latest/veilid_core/struct.VeilidAPI.html
Replying to
- Release 1.0.0: General Availability
- API stability
- Production app development readiness
We reserve the right to change the order of these even further. We're racing to get to 1.0.0, and sometimes when we discover that tasks can speculatively slot-in to the schedule earlier, we'll take that opportunity.
Veilid Framework 1.0.0 is still scheduled for March 2027. Let's fuckin' go.
Come check out Veilid and join the revolution at BsidesLV!
Veilid bringing the PLUR this year!
Privacy
Liberty
United
Revolution
Come get Veilid rave candy and hang out!
Replying to
Enter WebTransport. WebTransport is a brand-new protocol (only recently achieving a full
production release for Safari in the last month), but is supported by all major browser
families now, and it lets us operate in HTTPS Secure Context, using self-signed TLS
certificates via pre-exchanged fingerprints!
This plays well with Veilid's node-to-node model and gets us all the benefits of 'QUIC'
UDP-based networking as well, since WebTransport is QUIC internally.
Veilid Framework v0.5.6 is out!
This is primarily an optimization release, reducing build system requirements, and improving our CI release process to support application builds, including VeilidChat's next iterations.
- Optimizations:
- veilid-wasm and veilid-flutter WASM blob size greatly reduced (-47%)
- veilid-server 50% smaller, same great taste
- Duplicated crates consolidated
- Compile times improved
- Improved CI build supportReplying to
We've got a test network running -right now- with WebTransport support and it's both
performant/fast AND operational in the secure context.
To that end, we're going to rearrange our milestones to accommodate fast tracking
WebTransport support as *Veilid 0.6.0*!
### Revised Milestones
Here's the revised list of milestones. Dates for delivery are not guaranteed because
we work on 'Open-Source Time'. But rest assured we want these things as much as you do!
Replying to
So! One of the major long-standing shortcomings of Veilid has been that our browser WASM support only supported HTTP WebSockets, not HTTPS. While Veilid has its own cryptography regardless, the browsers have requirements in order to enable a 'secure context', which opens up a world of features our apps want:
- Camera/Mic access for video chats (for apps like VeilidChat!)
- Geolocation (for apps like Reunicorn!)
- Storage, WebGL, Service Workers, Credential Management, Clipboard access...
Replying to
- Release 0.11.0: Blockstore
- Large data transfer and CDN-style caching on the Veilid network
- Efficient cryptographic validation, chunking and distribution of app-level content
- Release 0.12.0: Unified Bindings Generation
- No more handwritten language bindings, more consistent API everywhere
- Support for more languages
- Release 0.13.0: Private Routing 2.0
- Address all known issues with Private Routing 1.0
- Improved forward secrecy and routing speed
To celebrate the release of 0.5, our friend Lodri has organized a neat fundraiser for Veilid foundation!
$25 gets you a holo cDc sticker, and an updated "cast" sticker for the book by @JosephMenn@infosec.exchange , $50 gets you all of the above plus a sweet patch!
Deets:
https://docs.google.com/forms/d/e/1FAIpQLSf8GptCfc0lNo_W3ZUrsgC2qIu4d60-4FmkbjBKVOY9vIBwAg/viewform
Replying to
The other option for P2P apps is and always has been WebRTC, but that spec is both very
complicated, and not really designed to be privately routed, and has a bunch of legacy
requirements about how to perform 'Internet Connectivity Establishment', that Veilid
already solves a different way. A lot of care will have to be taken to support WebRTC
the 'Veilid way', with the privacy everyone deserves. We'll do it, just not 'next'.
### But in the meantime, how do we proceed?
Replying to
All these things require 'HTTPS' and that little 'lock icon' on the location bar.
The original plan was to have avery different app model for WASM apps that could use
HTTPS contexts via 'Secure WebSockets', but that plan didn't work out, because there
was no good way around needing -centralized SSL certificates-, which in a P2P framework
is truly unworkable.
Replying to
A new VeilidChat beta will follow shortly, taking advantage of the upgrades to the framework.
✅ Debian packages updated
✅ RPM packages updated
✅ Pypi updated
✅ Rust Crates updated
Replying to
As routing tables in abandoned nodes begin to flush due to lack of successful connections, the network as a whole will being to solidify as a group of updated nodes who support all the features in the correct ways.
Replying to
- Release 0.9.0: ENV1 Envelope Format + HPKE Crypto Interface
- Prerequisites for post-quantum cryptography support
- Support larger RPC and the HPKE public key cryptography standard
- Release 0.10.0: VLD1 + Address-bound NodeIDs
- HPKE implementation with post-quantum cryptography algorithms
- Raising the bar on Sybil attacks on the Veilid DHT
Replying to
- Release 0.6.0: WebTransport
- HTTPS support for Veilid
- Faster more reliable UDP option that still support hole-punching
- Release 0.7.0: DHT Route Autopublish
- Management of private routes handled by Veilid
- DHT records used to exchange route blobs
- Release 0.8.0: Virtual Network Simulation
- Testing distributed algorithms at scale
- Ability to simulate the whole Veilid protocol, not just