Projects
Publications fund development. All contributions become open source. We do not profit from your work.
Active Projects
LFM-Reticulum
Encrypted mesh communications over HF radio using Reticulum and FreeDV. Long-range, off-grid, no repeaters. Building Monero transaction capability over mesh.
What We Need
- HF propagation testing across all HF bands with documented results
- Hardware configuration guides for radios and sound card interfaces
- Link budget analysis from real deployments
- Python contributions to ReticulumHF transport layer
LFM-Unmanned Systems
FPV platforms and counter-UAS. Build documentation, flight controller configs, and operational techniques drawn from current conflict reporting.
What We Need
- ArduPilot/Betaflight/iNav configuration guides with tested parameters
- Build documentation with verified parts lists and flight data
- Antenna theory and practical builds for FPV applications
- Counter-UAS detection and defeat methods
LFM-Guerrilla Tech
AI-assisted field operations: medical diagnosis support, direction finding, telemedicine over mesh, and improvised tech solutions using dev boards and LLMs.
What We Need
- LLM prompts and workflows for field medical triage assistance
- SDR + ML projects for signal hunting and direction finding
- Raspberry Pi / Jetson field medical device builds
- AI-assisted SIGINT analysis workflows
Project channels are invite-only. Join #general first, introduce yourself and state which project you want to contribute to. Access granted after review.
Contributing
We pay for work that ships. Articles get published. Code gets merged. Field data becomes documentation. All payments in Monero. Need a wallet? See our Resources page.
Submission Guidelines
Articles
- Length: 1,200 - 3,000 words
- Format: .docx, .odt, or Markdown (.md)
- Font: 12pt, standard font (Times New Roman, Arial, Liberation Serif)
- Structure: Title, author name or handle, body with subheadings, sources at end
- File naming:
ARTICLE_Title_Author_Date.docx
Field Documentation
- Format: .docx, .odt, or Markdown (.md)
- Required: Date, location (general area), equipment used, methodology, results
- Structure: Objective, setup, procedure, data/observations, conclusions
- Photos: Include if applicable, labeled with description
- File naming:
FIELD_TestType_Author_Date.docx
Hardware Configs
- Format: .docx, .odt, or Markdown (.md)
- Required: Complete parts list with sources, wiring diagrams, config files, tested parameters
- Include: Build photos, cost breakdown, software/firmware versions
- File naming:
HW_DeviceType_Author_Date.docx
Code Contributions
- Process: Open a Discussion on the relevant repo before starting significant work
- Standards: Follow existing code style, include tests if applicable
- Documentation: Update README or docs for new features
How to Submit
Open a PR on GitHub. Use Discussions before starting significant work.
For articles, field docs, hardware configs, or anything not suited for a PR.
SubmitFor sensitive material, you can encrypt your submission with PGP. This ensures only we can read it. Regular unencrypted email is also fine.
What is PGP? PGP (Pretty Good Privacy) encrypts files so only the intended recipient can read them. You encrypt with our public key, and only our private key can decrypt it.
How to use:
- Download our key above and import it:
gpg --import lfm-dead-drop.asc - Encrypt your file:
gpg --encrypt --armor -r lfmanifesto@proton.me yourfile.txt - This creates
yourfile.txt.asc- attach that to your email
Work reviewed before payment. Payment within 48 hours of acceptance. Anonymous submissions accepted.