Bitcoin Rail Integrity (BRI)15%
Measures whether the platform is BTC / Lightning / ecash only at the platform layer, avoids altcoins and stablecoins, and minimizes fiat dependence baked into the system.
This page converts the full audited framework into a single linked artifact. Every platform section includes direct links to the relevant official site, repository, documentation, or reference point inside the body of the analysis rather than collapsing all sources into a detached appendix.
All scores are 0–100 per axis. Composite score equals the weighted sum. The model privileges Bitcoin rail integrity, real forkability, identity minimization, custody discipline, governance resistance, telos yield, and practical liquidity. Two qualitative tags are also carried throughout: platform type (aggregator/indexer vs executor/escrow market) and reputation portability (how much work history can survive platform failure).
Measures whether the platform is BTC / Lightning / ecash only at the platform layer, avoids altcoins and stablecoins, and minimizes fiat dependence baked into the system.
Measures clear OSI licensing, frontend and backend openness where applicable, and the realistic ability to self-host or fork a fully working instance rather than a symbolic open shell over a closed core.
Measures the main identity anchor—such as Nostr, Lightning, PGP, email, or OAuth—and scores pseudonymity viability, KYC exposure, and correlation or dox risk.
Measures who actually holds the sats, for how long, and under what trust model: direct flow, partial escrow, balance wallet, or fully custodial settlement.
Measures jurisdiction, corporate or VC exposure, single-admin chokepoints, and the distance from the current state to a KYC, altcoin, or “compliance partnership” pivot.
Measures the approximate share of activity that builds Bitcoin, FOSS, privacy, and sovereignty-oriented infrastructure rather than synthetic-stack labor such as AI training data, behavioral prediction, compliance systems, or surveillance rails.
Measures practical volume and reliability of work flow and sats flow. Ideological alignment is handled mostly in Telos Yield, while this axis focuses on usable throughput and market depth.
Type distinguishes aggregators or indexers from executors or escrow platforms. Reputation portability tracks whether proofs of work, contribution history, or reputation can survive platform collapse through Git history, Nostr events, exported data, or project-native records.
Final ranking is grouped into three tiers: structurally strongest, strong but partially compromised, and mixed or captured. The table below reproduces the complete final scoring model with the final weighted composite score for each platform.
| Rank | Platform | BRI (15) | FF (20) | IRP (15) | CPS (10) | GCS (10) | TY (20) | AL (10) | Composite |
|---|---|---|---|---|---|---|---|---|---|
| 01 | SatShoot | 100 | 95 | 95 | 85 | 95 | 95 | 60 | 91.3 |
| 02 | Bitcoin Bounties | 100 | 85 | 90 | 95 | 85 | 95 | 70 | 89.5 |
| 03 | Stacker News jobs & bounties | 90 | 95 | 85 | 70 | 85 | 90 | 75 | 86.3 |
| 04 | fossjobs.net | 40 | 95 | 65 | 95 | 90 | 75 | 80 | 76.3 |
| 05 | Lightning Bounties | 95 | 50 | 50 | 75 | 65 | 85 | 70 | 69.8 |
| 06 | ZapWork | 95 | 25 | 80 | 75 | 70 | 85 | 65 | 69.3 |
| 07 | Microlancer | 95 | 30 | 70 | 75 | 70 | 55 | 80 | 64.3 |
| 08 | Bitcoiner Jobs | 80 | 20 | 55 | 95 | 70 | 55 | 90 | 60.8 |
| 09 | Stakwork | 95 | 30 | 80 | 70 | 50 | 20 | 95 | 57.8 |
Each entry preserves the full final scoring logic and adds direct links to the relevant official page, repository, or documentation source inside the analysis itself.
SatShoot presents itself as a Nostr-native freelancing marketplace that supports paying in sats, with direct linkage to a live instance at satshoot.com. No altcoin or stablecoin layer is surfaced in the core framing.
The Pleb5/satshoot repository is explicitly MIT-licensed and is structured as a real codebase rather than a thin marketing wrapper. Forking and self-hosting are plausible.
Identity is rooted in Nostr keys rather than corporate OAuth or mandatory email. That gives SatShoot one of the strongest pseudonymous identity postures in this set.
Lightning and Cashu-based flows allow a more sovereign payment architecture, though practical custody quality depends on chosen mints and relay practices. The score assumes deliberate use rather than naive default behavior.
Open code plus decentralized protocols radically reduce capture surface. Even if the main site fails, the stack can be replicated from the repo and the social graph is not owned by a single corporate identity provider.
The platform’s core architecture—Nostr identity, sats-denominated work, and portable reputation—directly supports a sovereign labor graph rather than routing work into conventional HR or AI-labor pipelines.
Liquidity remains early-stage. Structural quality is exceptional, but the volume profile is still smaller than older or more generalized marketplaces.
bitcoinbounties.org is explicitly a collection of Bitcoin project bounties, and the coinkite/bitcoinbounties-pub repo is labelled as the data source for the site.
The open data layer is strong: the public repo allows adding or editing bounty records via pull requests. The current front-end is simple enough to recreate, but the score stays below SatShoot because open data is clearer than a fully licensed front-end stack.
The directory itself holds minimal identity surface. Participation at the listing layer is Git-based, and payout identity questions are displaced to the underlying sponsor or project.
Bitcoin Bounties does not hold funds; it points to opportunities. That keeps custody risk low and sharply distinguishes it from escrow-driven marketplaces.
There is still a single operator nexus via Coinkite, but the simple architecture and open data significantly reduce dependence on any one front-end instance.
The site’s object is overwhelmingly Bitcoin infrastructure work. In telos terms, very little energy appears to be routed toward synthetic-stack labor or generic corporate throughput.
Volume is meaningful but specialized. This is a focused bounty vault, not a mass labor market.
Stacker News runs a sats-native social economy, and the jobs section shows sats-posting logic. Some job relationships still settle off-platform in fiat, so the score is high rather than absolute.
The stackernews/stacker.news repository is MIT-licensed, self-hostable, and explicitly describes itself as “100% FOSS.”
Pseudonymous participation is natural and identity exposure is lower than classic job boards. The score remains below SatShoot because this is still a conventional web application with normal hosting and telemetry surfaces.
Internal bounties and tips involve custodial Lightning balances. Other jobs simply use Stacker News for discovery and settle elsewhere. That mixed model places it between pure indexers and full escrow markets.
The site has a clear operating center, but open code and cloneability lower long-term capture risk. Governance cannot fully enclose the graph because the software is portable.
The jobs and bounties cluster is culturally and economically biased toward Bitcoin, Lightning, FOSS, and sats-native builders.
There is a consistent stream of opportunities, though jobs are only one slice of the larger Stacker News ecosystem.
fossjobs.net is not a Bitcoin-native platform. It functions as a FOSS-only job board and generally routes applicants into conventional compensation rails.
The fossjobs/fossjobs repository is MIT-licensed, and the about page states that the site is based on the open-source software Jobberbase. Structurally, this is one of the cleanest codebases in the set.
The board itself collects little, but applicants are commonly pushed into normal HR funnels that require resumes, real names, and institutional identity traces.
No funds move through the board. It acts strictly as a discovery layer.
The platform is a non-commercial hobby project with low apparent capture pressure. Open code and simple architecture reinforce its resilience.
The site explicitly states that it only lists jobs directly improving FOSS or open hardware. That gives it strong telos yield through open infrastructure, even though it is not specifically Bitcoin-native.
The board has sustained listing flow and a clear niche. It outperforms several Bitcoin-native but structurally weaker or more captured platforms on practical discovery value.
Lightning Bounties is explicitly a Bitcoin-powered bug bounty platform using the Lightning Network for rewards.
The lb-next frontend and public docs are MIT-licensed, but the core backend is private. That creates a partially open shell over a closed operational center.
The project’s own documentation states that it uses GitHub OAuth to verify identity. That is a major correlation and deplatforming surface because contributor identity is bound to Microsoft’s GitHub graph.
The platform holds bounty funds in Lightning escrow until claims resolve. That is normal for bug bounties, but it still creates a non-trivial custodial trust point.
Closed backend plus GitHub dependence plus startup-like product structure widen the route to future compliance or policy capture.
Despite the architectural weaknesses, the underlying activity is still mostly FOSS and Bitcoin-adjacent bounty work. The work itself remains directionally strong.
It has usable dev-focused liquidity, especially for GitHub-native workflows, but not enough scale to offset the structural penalties.
ZapWork markets itself as a Nostr-powered freelancer platform where work is monetized directly with Bitcoin. The jobs layer openly references Bitcoin categories and decentralized workforce framing.
ZapWork is built on open protocols, but no clearly licensed public repository was identified in the final audit. Some ecosystem chatter claims the code is open, but without an explicit OSI license and visible repo, forkability remains unproven.
The login flow supports Nostr Connect, which is a major structural advantage over conventional OAuth-centric platforms. Standard web access and email pathways still exist, so it does not reach SatShoot’s level.
Job funds appear to be held in a backing wallet during execution, implying platform-managed escrow for at least part of the payment flow.
ZapWork’s ethos is strong, but unless the implementation layer is clearly open and reproducible, the product still centers a company-operated domain and operational stack.
The conceptual direction is solid: censorship resistance, Nostr social graph, and Bitcoin-denominated work. The score stays high because the platform is pushing toward sovereign labor rails even if the implementation remains partly opaque.
There is visible marketplace activity and a growing network effect, but the actual liquidity profile still looks early and uneven.
The Microlancer repo describes the platform as “a Bitcoin Lightning network powered freelancing platform” with “No KYC, no PayPal, no credit cards!” Rail integrity is therefore strong.
The main application repository is public but lacks a license file, which means the code is not legally FOSS. Only the auxiliary lightning-php helper repo is clearly MIT-licensed. This sharply limits the forkability score.
No mandatory KYC is a real advantage, but the platform still uses a conventional web account model. Privacy is better than mainstream freelancing portals, but not protocol-native.
Microlancer appears to support both platform escrow and direct peer-to-peer variants depending on the task setup. That mixed custody pattern prevents both a very low score and a top-tier score.
Microlancer remains a centralized SaaS with a normal company-operated front-end and infrastructure stack. It is less visibly captured than some corporate peers, but still structurally enclosed.
Task mix is broad and frequently generic rather than concentrated on sovereign infrastructure. That keeps liquidity useful while pulling down telos intensity.
Microlancer has been around long enough to build a meaningful work flow. It outperforms several architecturally cleaner entrants on raw practical usage.
Bitcoiner Jobs is explicitly a career site for Bitcoin companies, but most hiring relationships remain conventional employment flows rather than sats-native contracts mediated by the platform.
No clearly licensed public repo surfaced in the final audit. The platform is treated as proprietary until proven otherwise.
The job seeker path is classic HR infrastructure: account creation, profile, resume handling, and strong incentives toward real-world identity disclosure. That is a major privacy downgrade compared with Nostr-native or Git-history-native systems.
The platform is a pure indexer; it does not intermediate or hold compensation flows.
Mission alignment is Bitcoin-specific, but the operational structure is still a centralized commercial job board and therefore relatively easy to steer into standard compliance practices.
Not all Bitcoin companies are sovereignty-positive in the same way. A large share of the ecosystem includes custodians, exchanges, and other regulated operators. That dilutes the telos score.
This is one of the most active discovery hubs for Bitcoin company roles. Liquidity is strong even though the structure is conventional.
Stakwork is widely described as a Lightning-based platform paying workers in Bitcoin. On the payment rail axis alone, it scores well.
The core platform is not meaningfully open. Some adjacent ecosystem components exist elsewhere, but Stakwork itself operates as a closed service.
Workers can often participate without a bank account, which is real. But privacy remains bounded by normal web telemetry and a company-controlled operational layer.
Balances are held on-platform until withdrawal, creating an ordinary custodial bottleneck.
The CB Insights profile frames Stakwork as a business process automation company that combines AI and human workers. That is a high-capture institutional posture.
The decisive issue is task composition. The Bitcoin Products AI category describes Stakwork as a global microtask platform paying workers in Bitcoin for AI training data and business process automation. Under this model, that is synthetic-stack labor with sats as the wrapper.
Stakwork has very strong throughput. Its rank is low not because it lacks volume, but because its volume is directed into AI and automation pipelines rather than sovereign infrastructure.
The final ordering stabilizes around a simple rule: platforms rise when they combine Bitcoin-native rails with real forkability, identity minimization, low custody exposure, and labor flow into open sovereign infrastructure. They fall when they route labor into synthetic-stack systems, trap users in proprietary backends, or force reputation through corporate identity graphs.
This page is a direct HTML/CSS transformation of the final audited writeup. Links are placed inside the relevant argument rather than isolated at the bottom. The strongest evidence anchors used in this version include the official repositories and project pages for SatShoot, Bitcoin Bounties, Stacker News, fossjobs.net, the Lightning Bounties frontend and GitHub OAuth documentation, the live ZapWork site, the Microlancer repository, the live Bitcoiner Jobs site, and the Stakwork company profile plus AI-category reference used to ground the final telos penalty.