Paid Task (Sats): Run DamageBDD macOS Builds + Report Errors

1. Overview

DamageBDD is a multi-app Erlang/OTP monorepo (apps/*) built with rebar3 + relx. We need a clean macOS build sanity-check and structured error report.

Your job: run the mac build locally, capture logs, reproduce failures, and report clearly so we can patch fast.

2. Repository Details

2.1. Project

Name: DamageBDD
Language: Erlang/OTP (monorepo with apps/*)
Build Tool: rebar3
Release Tool: relx (include_erts = true)

2.2. Repository

GitHub: https://github.com/DamageBDD/damagebdd
Default branch: main
Uses git submodules: no (standard deps via rebar)

2.3. Architecture Notes

Multiple OTP apps: damage, erm, ecai, nosternity, vanillae, bop
Includes Cowboy (HTTP), IPFS client, cryptographic deps, telemetry
Linux-only NIF builds currently exist (ecai)
GTK-related C build hook may be Linux-specific

We need to verify:

Can macOS build a production release?
Do OS-specific hooks break the build?
Does the release binary run?

3. Target Environments

macOS Sonoma / Ventura
Apple Silicon (arm64) preferred
Intel (x86₆₄) also valuable
Bonus if both tested

4. Prerequisites (baseline)

Xcode Command Line Tools
Homebrew
Erlang/OTP 26+ (brew install erlang)
rebar3 (brew install rebar3)
git
make

Optional:

gmp
openssl
libsodium (if needed by crypto deps)

5. Required Build Steps

git clone https://github.com/DamageBDD/damagebdd.git
cd damagebdd

rebar3 clean
rebar3 compile
rebar3 as prod release

If release succeeds:

cd _build/prod/rel/damage
bin/damage foreground

Or:

bin/damage console

6. Deliverables

Environment Report
- macOS version
- CPU arch (arm64 or x86₆₄)
- Erlang/OTP version
- rebar3 version
- brew list (top-level summary)
Full Build Logs
- compile output
- release output
- first failing error (if any)
Repro Notes
- exact commands run
- environment variables used
Diagnosis
- likely cause of failure
- suggestion for fix (even approximate)

If build succeeds:

confirm release path
confirm binary executes
confirm any runtime warnings

7. Known Likely Failure Points

Linux-specific make hook: apps/erm/c_src gtknode4
Linux-only NIF port_specs (ecai)
Hardcoded include paths in NIF build
System library linkage differences (mac vs linux)

Your report should specifically call out which of these break (if any).

8. Payment (in sats)

Assumed BTC price: USD 68,000 1 USD ≈ 1,470 sats

8.1. Tier A – Single architecture build + structured report

250,000 – 400,000 sats
(~USD 170 – 272)

8.2. Tier B – Single arch + deeper root cause analysis

450,000 – 650,000 sats
(~USD 306 – 442)

8.3. Tier C – Both arm64 + x86₆₄ tested + consolidated report

700,000 – 1,200,000 sats
(~USD 476 – 816)

8.4. Suggested default offer

500,000 sats (~USD 340) for a solid single-arch build + actionable report.

Bonus: additional sats for PRs or working mac profile patch.

9. Acceptance Criteria

Reproducible environment description
Complete logs
Clear first failure (or success confirmation)
Actionable diagnosis

10. Payment Method

Lightning invoice preferred
On-chain possible if needed
Payment released on report delivery

11. How to Apply

Reply with:

macOS version
CPU architecture
Whether you can test both architectures
Desired payout tier
Relevant Erlang / OTP / NIF experience

You will receive confirmation and any additional internal build notes if needed.

DamageBDD