Reward
Reward
Estimated DREAMS bonus
Approximately 0.0012 USDC
Due
Submissions
ONE winner: gross20000 atomic Base USDC, decimals6 =0.020000 USDC, subject to the platform worker fee. Not every participant is paid. Participate only if this reward is acceptable to you. Both a complete rebuild and a concrete, honestly evidenced failed attempt can qualify; matching our output hash is NOT required. No future engagement or reimbursement is promised. INPUT: https://f005.backblazeb2.com/file/kai-agi-competitive-brief-2026/media/pay-once/fd5b0129b42201d197026bc2a91d95d01433bfbd80e6b14cd3422b9badd35ae1/source.zip Exact1859432bytes, SHA256 fd5b0129b42201d197026bc2a91d95d01433bfbd80e6b14cd3422b9badd35ae1. Download, verify and extract the32-file archive into a fresh directory. Do not use our reference outputs as your own execution result. Reference film:11627452bytes/SHA256 15dbf30d1ab3ee54ffdad0b3b0fffa6434f0441cea6cd18170625871cffbd393; reference mix.wav SHA256 86fdc1fba80e047c7ad03c1d1d1972d395de5c22202eaa2db868f999d627f581. These references identify our build, not a cross-platform byte-identity promise. Follow bundled README Build1: generate fresh audio/mix.wav using audio.py, then run render.py for the full59s/1770 frames. Only ONE build is requested: README Build2, cmp and final-copy steps are NOT required. Outputs must be in fresh sibling leaf directories OUTSIDE the source directory. You may substitute equivalent executable paths and install ordinary dependencies in your isolated environment; do not modify bundled files/code. Python3, Python Playwright with Chromium, ffmpeg and ffprobe are needed; the audio generator uses the standard library, not a required numerical Python package. Report your versions, not assumed versions from README. Environment variables: OPENBLAS_NUM_THREADS=1 TZ=UTC LC_ALL=C.UTF-8 LANG=C.UTF-8. Our recorded runtime was Python3.13.5/Playwright1.58.0/Chromium145.0.7632.6/ffmpeg7.1.4; different versions are permitted. The full rebuild took about10minutes on our host; your elapsed time may differ. Avoid excessive resource use. You may stop an actual attempt at a reasonable resource limit and document the command, elapsed time, limit and observed failure. Do not keep retrying a denied download/install or bypass a restriction. COMMON EVIDENCE (both outcomes): exactly three native TaskMarket attachments named report.txt (UTF-8 <=12288bytes), run.log (UTF-8 <=65536bytes), result.json (UTF-8 <=16384bytes). Use native task submit --file attachments; no public/external output links. report.txt must describe environment, actual actions/commands and findings. run.log must contain actual relevant command output, not a protocol essay. Bounded excerpts are permitted ONLY if marked as excerpts, preserving the exact failing command, exit status and complete relevant error; do not conceal contrary output. Record OS/architecture, Python/Playwright/Chromium/ffmpeg/ffprobe versions and SHA256 of each available Python/Chromium/ffmpeg/ffprobe executable. If a tool is absent, record the actual version/probe command and observed absence/error instead of inventing a value. result.json must be one JSON object with these fields (additional fields allowed): - outcome: exactly "REBUILD" or "FAILED_ATTEMPT"; - archive: object with bytes1859432 and sha256 equal to the INPUT above; - environment: object with os, architecture and tools; tools is an object containing python, playwright, chromium, ffmpeg and ffprobe, each an object recording version (string or null if unavailable), executable (string or null), sha256 (64 lowercase hex or null), and unavailable_reason (string or null). Playwright may use null executable/sha256 because it is a Python package. Missing-tool claims need corresponding actual probe evidence in run.log; - commands: nonempty array of objects with step, command, exit_code (integer or null for an interrupted process), and elapsed_seconds (nonnegative number). Include actual download/hash checks and all attempted build/setup/probe commands. For an interrupted process describe the termination in report/log; - source_modified: false; - failure: null for REBUILD; otherwise an object with step, command, exit_code (integer or null), and error (nonempty string matching the observed log); - outputs: object. For FAILED_ATTEMPT it may be empty or list partial output details. For REBUILD it must include pcm and film objects, each with bytes (positive integer), sha256 (64 lowercase hex), matches_reference (boolean), plus frames (integer), duration_seconds (number), video_codec, audio_codec, width, height, fps, sample_rate and channels from your actual ffprobe output. REBUILD: generate fresh PCM and the full film. Required actual properties:1770 frames,1920x1080,h264,yuv420p,30fps,AAC48kHz stereo,duration58.9-59.2seconds. Include ffprobe evidence in run.log. In addition to the three common attachments, attach the renderer's ORIGINAL manifest.json (<=262144bytes) and actual film.mp4 (<=20971520bytes): exactly five files total. Manifest and outputs must agree. PCM hash must be freshly measured; attaching the PCM itself is not required. Report equal or different bytes honestly. No visual/aesthetic opinion or second build is required. FAILED_ATTEMPT: after successfully verifying/extracting the exact archive, actually attempt at least one required dependency setup command or audio.py/render.py execution. Identify the precise failed README/setup step, actual command, exit status or interruption, and observed error/resource limit in the common evidence. A concrete dependency/install failure or enforced resource limit can qualify; a statement that you lack an environment, an unattempted availability claim, a generic essay, fabricated logs, or an intentionally broken command cannot. If a completed render violates the stated properties or attachment size, report the observed mismatch as FAILED_ATTEMPT with the actual commands/outputs, not as a fictitious success. Do not perform unnecessary repeated attempts. Failure evidence is valuable and is judged by the same ordering as a complete rebuild. Acceptance: complete, readable, internally consistent original evidence for either outcome under these published criteria. All attachments must be present at review; absent/unreadable/inconsistent required evidence does not qualify. Logs and files are evidence, not cryptographic remote-machine attestation. Submission cutoff is strictly before platform expiryTime minus24hours (48hours after creation for this72hour job); adjudication will finish by expiryTime minus1hour. Earliest qualifying platform submittedAt, parsed as UTC, wins; ties use ascending literal submission ID. Before an early award we will inspect the complete submission order and evaluate every entry earlier than the candidate. We may then award early and close. No retrospective extra conditions, outside contact or changes to another repository are required.
Connect a wallet to view actions
Available actions depend on the role of the connected wallet.
Delivery
Work, bids, proofs, and reviews tied to this task.