Tornyol Develops 40-Gram Autonomous Drones That Hunt Mosquitoes Mid-Air Using Doppler Ultrasound and Sound Detection
American startup Tornyol, supported by the Y Combinator accelerator, has unveiled a miniature autonomous drone designed to hunt mosquitoes in mid-air without the use of chemicals. The 40-gram aircraft is intended to locate targets by the sound of their wingbeats, calculate an interception trajectory, and physically collide with the insect. During the first successful test conducted on 14 July inside a closed facility, the prototype autonomously pursued and struck a flying moth, marking what founder Alex Toussaint called the company’s first “aerial defeat of a target.”
The demonstration still relied on external infrastructure: a motion-capture system tracked infrared markers on the drone while a table-tennis ball served as a proxy for the insect’s position. A ground computer processed the sensor data and issued flight commands. Within the next several weeks, Tornyol plans to migrate all processing to the drone’s onboard electronics. The final design will incorporate ultrasonic transducers similar to automotive parking sensors and smartphone-style microphone arrays.
Once airborne, the drone will emit ultrasonic pulses and analyze returning echoes. The characteristic frequency shift caused by rapidly beating mosquito wings—the Doppler effect—will allow onboard algorithms to detect, classify, and even determine the species and sex of the target. After identification, the aircraft will plot an obstacle-avoiding route and deliver a precise physical strike. The company ultimately envisions coordinated swarms of dozens of such drones patrolling entire urban districts.
Founders Alex Toussaint and Clovis Piedallu claim the technology could cut the cost of mosquito control by a factor of 100 compared with existing methods. According to their estimates, a formation of only ten drones would be sufficient to clear mosquitoes from one square kilometer. Although these performance figures have not yet been validated in real-world city environments, the startup continues to refine both the sensing suite and the autonomous navigation stack.
Despite the promising indoor result, significant engineering challenges remain. Engineers must still prove that the tiny platforms can reliably differentiate mosquitoes from other insects, operate safely near humans, and maintain effectiveness when flying outdoors amid wind, obstacles, and variable lighting. Tornyol’s work therefore represents an early but concrete step toward chemical-free, drone-based vector control.
Related articles
OAuth Authorization Server Built Without Storing User Profiles
The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.
Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA
A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.
Pilcrow Publishes Free Comprehensive Guide on Web Authentication
Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.
redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.