Projects

Publications fund development. All contributions become open source. We do not profit from your work.

Active Projects

LFM-Unmanned Systems

What We Need

  • ArduPilot/Betaflight/iNav configuration guides with tested parameters
  • Build documentation with verified parts lists and flight data
  • Counter-UAS detection and defeat methods

LFM-Guerrilla Tech

What We Need

  • SDR + ML projects for signal hunting and direction finding
  • AI-assisted SIGINT/sensor analysis workflows
  • Field testing
SEED C2

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.

What We Pay (USD equivalent, paid in XMR) XMR/USD: ...
Articles Original work on comms, drones, tradecraft, OSINT, mesh networking. $25
Field Documentation Real testing with data, photos, reproducible methodology. $10
Hardware Configs Complete build guides with parts, wiring, tested parameters. $30
Code Contributions Bug fixes, features, documentation. Use GitHub Discussions first. Variable

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

GitHub

Open a PR on GitHub. Use Discussions before starting significant work.

Email

For articles, field docs, hardware configs, or anything not suited for a PR.

Submit

For sensitive material, you can encrypt your submission with PGP. This ensures only we can read it. Regular unencrypted email is also fine.

Download PGP Key 5F30 7CCC D67D 28BC F7D2 B5EE FBEC F672 D19E 1FFB

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:

  1. Download our key above and import it: gpg --import lfm-dead-drop.asc
  2. Encrypt your file: gpg --encrypt --armor -r lfmanifesto@proton.me yourfile.txt
  3. This creates yourfile.txt.asc - attach that to your email

Work reviewed before payment. Payment within 48 hours of acceptance. Anonymous submissions accepted.