Darkbloom verification pending: MDM, App Attest and trust on macOS 27
Updated
A Mac can be online, with a model loaded, and still get no paid requests because Darkbloom has not verified it. Verification was the most common provider problem in September 2026, especially while Macs moved from Darkbloom’s MDM profile to Apple’s App Attest on macOS 27. Everything below comes from Darkbloom’s own provider docs (links at the end).
Check where your Mac stands
- Run darkbloom status and read the Trust line. hardware / online means verified: the coordinator can route public work to your Mac.
- self_signed / online with “awaiting MDM verification”, or App Attest shown as pending, means connected but not yet verified. The Mac gets no public paid work, though it can still earn base rewards.
- Any level followed by / untrusted and a reason means the coordinator stopped routing to your Mac.
- Run darkbloom doctor for the local side. Its APP ATTEST section shows whether a key is stored and enrolled, any key cooldown, and whether the provider runs in the logged-in session.
macOS 27: App Attest instead of the MDM profile
- Since Darkbloom 0.9.7, Macs on macOS 27 or later can be verified with Apple’s App Attest, without installing Darkbloom’s MDM profile. New setups on macOS 27 skip the profile.
- Darkbloom says its MDM will be switched off, so it recommends upgrading to macOS 27.
- Already enrolled with MDM? Upgrading macOS does not remove the profile. Update the provider, restart it and check darkbloom status. Keep the profile until Darkbloom reports that removal is ready.
- Then remove it only with darkbloom unenroll, choosing the App Attest option, in an interactive Terminal window. Removing the profile yourself first is a common way providers lost verification in September.
- Company-managed Macs keep their employer profile; they don’t need Darkbloom MDM for App Attest.
What verification needs
- System Integrity Protection on, and Secure Boot at Full Security (both changed only in Recovery).
- A user logged in at the Mac’s screen, not just over SSH. Turn on automatic login, turn off log out when idle, and keep the Mac from sleeping, so it can verify again after a reboot.
- A current provider version that Darkbloom has approved. The provider updates itself, so check verification again after an update or a macOS upgrade.
- A release version of macOS. Darkbloom staff have said App Attest doesn’t work on macOS betas.
Common triggers
- A reboot or power cut with nobody logged in at the screen.
- An overnight provider update or a macOS upgrade.
- Sleep and wake: every reconnect has to pass verification again.
- Removing the MDM profile before Darkbloom confirmed App Attest.
How to get verified again
- Log in at the Mac’s screen and run darkbloom doctor. Fix anything it flags in the attestation checks.
- Keep the provider running. When Apple’s check fails for a moment, Darkbloom retries on its own after one minute, then five, then every ten minutes. It can take a while, and waiting is often all that’s needed.
- Restart the provider (darkbloom restart) so it re-registers, then check darkbloom status again.
- Make sure the provider is up to date. Several September releases (0.9.8 to 0.9.10) fixed App Attest getting stuck.
- On macOS 27, don’t install the MDM profile or delete saved credentials to get around a pending App Attest check. Darkbloom’s docs say to diagnose with darkbloom doctor instead.
- Still stuck after a day? Check GitHub issue #1161 and the Darkbloom Slack; others may be hitting the same thing.
Sources
- Darkbloom provider attestation guide: github.com/Layr-Labs/d-inference/blob/master/docs/provider/attestation.md
- Darkbloom troubleshooting: github.com/Layr-Labs/d-inference/blob/master/docs/provider/troubleshooting.md
- Release notes (0.9.7 App Attest without MDM; 0.9.8–0.9.10 fixes): github.com/Layr-Labs/d-inference/releases
- App Attest pending on macOS 27: github.com/Layr-Labs/d-inference/issues/1161
How BloomGauge helps
BloomGauge shows live whether paid work is reaching your Mac and what it earns each hour, so a Mac that is online but no longer verified shows up as paid work stopping, not as a silent gap in next week’s payout.
Questions
What does self_signed mean in Darkbloom?
Your Mac is connected but Darkbloom has not finished verifying it, so it is not sent public paid requests. On macOS 27 verification uses App Attest; on older macOS it uses Darkbloom’s MDM profile. Check darkbloom status and darkbloom doctor.
Do I still need the Darkbloom MDM profile on macOS 27?
Not for new setups: since Darkbloom 0.9.7, macOS 27 Macs can be verified with App Attest. If your Mac already has the profile, keep it until Darkbloom reports removal is ready, then remove it with darkbloom unenroll and the App Attest option.
Why is Darkbloom App Attest verification pending for hours?
Common causes are nobody logged in at the Mac’s screen, an outdated provider, a macOS beta, or a recent reboot or update. Log in, run darkbloom doctor, update the provider and restart it. Darkbloom retries on its own, so a working setup may just need time.
Does Darkbloom verification work over SSH or on a headless Mac?
No. App Attest needs a user logged in at the Mac’s screen. Turn on automatic login and turn off auto-logout, so the Mac can verify again after a reboot.
Related
- Why is my Mac online but not getting Darkbloom jobs?
- Darkbloom provider on a Mac: setup checklist
- How Darkbloom pays Mac providers: token earnings and base rewards
- Is Darkbloom safe? What access it gets to your Mac
- darkbloom unenroll errors: moving from MDM to App Attest, step by step
- Running Darkbloom on a headless Mac: no monitor, SSH and automatic login
Updated 2026-09-29. Still stuck? Ask in #bloomgauge on the Darkbloom Slack or contact us. BloomGauge is independent and not affiliated with Darkbloom.