moneycanbuy.fun: draft board tasks and dares (TaskVault v6)

These are draft tasks, ready to post. Nothing in them has been funded. Every rule cited below comes from the repository at commit 8603831, and only from three files: docs/MECHANICS.md (shortened to MECH), docs/TOKEN-UTILITY.md (TU) and contracts/README.md (CR). Each rule names the section it came from. Statements marked (inference) are my own reading of those rules and do not appear in the source text.

Entry 0: index of task titles

Section 1: Shill moneycanbuy.fun

1. Quote-post a live task and explain its 24 h dispute window in one post
2. Five-post X thread: the life of one task from Open to Completed
3. 60-second screen recording walking through one live task page
4. Hand-drawn diagram of a submission's states, posted on X
5. Reply-guy rescue: answer a stranger asking how bounties stay honest
6. Explain 'no author cancel' in exactly three sentences on X
7. Post a real-world flyer of moneycanbuy.fun on your own noticeboard or fridge
8. Livestream clip: read one live task aloud and say whether you'd do it
9. Write a 300-to-600-word blog post on how a doer's bond works
10. Meme template: 'Me after nobody disputed within 24 h'
11. Record a 30-second voice-over of the four reward currencies

Section 2: Shill IMD, the IMD swarm and IMD culture

1. X thread: what a 7-agent swarm panel with quorum 5 means
2. Video: act out the IMD swarm answering yes/no as seven people (or seven hats)
3. Draw the DOER CODE format IMD-- as a poster
4. Explain 'silence is not an answer' in one X post
5. On-chain shout-out: a self-transaction whose input data reads IMD SWARM 7 OF 5
6. Ninety-second explainer: why only identity.md NFT holders vote on disputes
7. Thread: the three ways a question reaches the IMD swarm
8. Write an IMD swarm haiku trilogy
9. Blog post: 'One NFT, one vote', how an identity.md dispute vote works
10. Thirty-second video: show the order an appeal goes in, with sticky notes
11. Quote-post: the IMD swarm's answer is final, explained like a sports referee

Section 3: Viral and unhinged, but safe and legal

1. Give your houseplant a formal job interview for 'Dispute Juror'
2. Sea shanty about the doer's bond, 45 to 90 seconds, sung by you
3. Nature-documentary narration of your pet (or a toy) doing nothing for 60 s
4. Bake a cake iced with 'OPEN → COMPLETED'
5. Shakespearean monologue: 'To dispute, or not to dispute'
6. Register your pet rock on chain with a self-transaction
7. Recreate a famous painting using only kitchen utensils
8. Cardboard-box TaskVault: build the vault and lock a cookie inside it for 24 h
9. Dramatic slow-motion reading of the creation-fee rule
10. Sock-puppet courtroom: puppets act out a dispute vote
11. Wear a paper crown reading 'MONEY CAN BUY' for one full video call

Section 4: Impossible tasks, kept for hype

1. Photograph the surface of the Sun from the surface of the Sun
2. Submit a mainnet transaction whose hash is all zeros, sent from your address
3. Count aloud to infinity, finished, in one unedited video
4. An X post containing this task's DOER CODE, dated before the year 2006
5. Draw a square circle and have it verified as both
6. Publish the largest prime number
7. Hand-write every digit of pi, all of them
8. Be in two cities at once, in one continuous shot
9. Fold one sheet of paper in half 104 times on camera
10. A transaction of yours included in Ethereum's genesis block

---

Rules every task below relies on (facts, with source)

• R-SUBMIT. A doer submits exactly one proof link whose form matches the task's proof type. x_post is https://[www.|mobile.|m.](x.com|twitter.com)/<handle>/status/<id>. video is a YouTube, youtu.be, Kick or Twitch link, or an X post. onchain_tx is 0x plus 64 hex characters. link is any https:// link. Two pieces of evidence are optional: a screenshot (the digest of an IPFS block) and a note of at most 200 bytes. A submission cannot be withdrawn (MECH, "Submission lifecycle → Submit"; CR, "Task and submission fields on chain").
• R-CODE. The contract itself builds the DOER CODE IMD-<taskId>-<doer address, 0x + 40 lowercase hex> and puts it in every swarm question. The default prompt tells the panel that the post, video description or page must contain the whole DOER CODE, and that for onchain_tx the transaction must be sent from the doer's address (CR, "Task and submission fields on chain"; MECH, "The swarm → Question"). The site shows each doer their own code (CR, same section). Every originality check below builds on this code, because nobody can include it in a proof before they know both the task id and their own address.
• R-TEXT. A task condition is 1 to 256 bytes of valid UTF-8 and may not contain ", \ or control characters. A title is 1 to 80 bytes (MECH, "Limits"). The swarm sees only the condition, the proof and the proof type (CR, "Task and submission fields on chain"). The author should paste each task's acceptance criteria, shortened, into the 256-byte condition. The longer text below is meant for the task page and for voters.
• R-DISPUTE. Anyone except the doer, the author included, can dispute within the 24 h dispute window by posting a dispute bond. TU §4 gives it as 0.5 IMD plus 1% of the reward. The first dispute opens a 24 h vote of identity.md NFT holders, one NFT per vote. A decision can be appealed to the IMD swarm, and anyone can call the swarm when the vote does not decide. The swarm's valid answer is final. The losing side's bonds pay the winners, the NFT voters who voted correctly and the treasury (MECH, "Disputes", "NFT voting", "The swarm", "Money and fees"; TU §4).
• R-ACCEPT. If nobody disputes within 24 h, the submission is Accepted and the doer receives the reward minus 10%. If the vote ends without a decision and nobody calls the swarm within 24 h, the submission is also Accepted, under the tie rule (MECH, "Overview" and the state diagram; CR, "Rules at a glance"). (inference) So a false proof is rejected only if somebody disputes it. Each author should watch their task's dispute window.
• R-MIN / R-LARGE. The minimum reward is $5 by oracle, or 0.5 IMD (MECH, "Task lifecycle → Create"). TU §1 gives flat minimums instead: 5 USDC, 0.002 ETH, 1 IMD or 1,000 YOLO. A reward of $300 or more (or 40 IMD or more) makes the swarm check mandatory, and the doer prepays its fee (MECH, "Submission lifecycle → Mandatory swarm check"). A $YOLO task with no reliable YOLO price counts as large whatever its size (MECH, "Rules worth knowing" #9). For that reason, every suggested reward in sections 1 to 3 stays under $300, and $YOLO is recommended only where that cost is acceptable.
• R-DEADLINE / R-REFUND. The deadline closes submit and topUp only. A submission that is active or queued is still judged to its end. A task becomes Expired only when its deadline has passed and no submission is active. After that, every contributor withdraws their own share. There is no author cancel. The creation fee (at least 0.0005 ETH) goes to the treasury and is never refunded (MECH, "Task lifecycle → Withdraw / Deadline"; MECH, "Money and fees"). A $YOLO add-on returns to whoever added it under the same rule (TU §2; CR, "Sweeten with $YOLO").

Conflicts between the three source files (uncertainty, not settled here)

• C1, bond sizes. MECH ("Money and fees") and CR ("Rules at a glance") put the dispute bond at max(1 IMD, 0.5 IMD + 1% R_imd), paid in IMD, plus an ETH fee of 0.0003 to 0.01 ETH. They put the doer bond at max(1 IMD, 0.5 IMD + 3% R_imd), doubling ×2 per rejection or submission ahead. TU §3 and §4 instead give 0.5 IMD plus 3% or 1% in the reward's currency, with no doubling and no ETH fee. MECH and CR both say that TU applies where they differ on $YOLO rules. Whether that also covers bonds on ETH, USDC or IMD tasks is not stated. These drafts quote no bond amounts, and none of them depends on the answer.
• C2, dispute and vote details. TU §4 says one dispute per submission, an early decision at a 20-vote margin, and no doer reply. MECH ("Disputes", "NFT voting") and CR ("Risks") say any number of disputers, no early decision (audit C-02), and a 12 h doer reply. The drafts rely only on what the files agree on: the 24 h window, the NFT vote, the swarm on appeal or call, and the loser's bond paying the winners.
• C3, minimum reward. R-MIN above gives both versions. Every suggested reward below clears both.
• Open questions. None of the three files says how the real swarm panel treats screenshots or free text (MECH, "Rules worth knowing", last paragraph; CR, "Risks"). Every "anti-fake" check below therefore relies on things anyone can verify in public: post timestamps, the DOER CODE, and on-chain data. It never relies on the screenshot alone.

---

SECTION 1: Shill moneycanbuy.fun

1.1 Quote-post a live task and explain its 24 h dispute window in one post

1. TITLE: Quote-post a live task and explain its 24 h dispute window in one post
2. DESCRIPTION: From your own X account, publish one original post (not a reply) that names "moneycanbuy.fun", names one task currently Open on the board by its task number, and explains in your own words that a proof is paid only if nobody disputes it within 24 hours. The post must contain your DOER CODE for this task. No paid promotion, no bought engagement, and the post stays up until the task settles.
3. REWARD: $10–$25 in USDC. The value is stable for a small social task, the minimum clears both C3 versions, and it stays far below the $300 mandatory-check threshold.
4. DEADLINE: 7 days from posting. One post takes minutes, and a week gives time zones and weekends room without leaving the task hanging.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • It is one X post on the doer's own account, published after this task was created.
   • The text contains the exact string moneycanbuy.fun.
   • The text contains "task #N", where N is a task other than this one that showed status Open when the post was made.
   • The text states that the window is 24 hours and that no dispute means payment, in any wording.
   • The text contains the doer's full DOER CODE.
   • The post is still live when the dispute window closes.
7. PROOF FORMAT: The link is https://x.com/<handle>/status/<id>. The optional screenshot shows the post with its date visible. The note says task #N was Open at <UTC time>; code in post.
8. ORIGINALITY CHECK: The post contains the DOER CODE IMD-<this taskId>-<doer address>, and the post's timestamp falls after this task's creation.
9. ANTI-FAKE / ANTI-AI CHECK: A voter opens the live post and checks three things. The post exists, its date on X is later than task creation, and the DOER CODE matches the submitting address byte for byte. An edited screenshot cannot pass, because the link itself is what gets judged.
10. HOW A FALSE SUBMISSION IS REJECTED: Mechanism R-DISPUTE: a dispute within 24 h with the dispute bond (TU §4), then the NFT vote, then the swarm on appeal. The loser's bond pays the winners, the correct voters and the treasury (MECH, "Disputes", "Money and fees"). The proof loses if the post is deleted, predates the task, lacks the code or the 24 h statement, or the cited task was not Open.

1.2 Five-post X thread: the life of one task from Open to Completed

1. TITLE: Five-post X thread: the life of one task from Open to Completed
2. DESCRIPTION: Publish an X thread of at least five posts on your own account explaining a task's path. Cover: an author locks a reward, a doer submits one link, the 24 h dispute window, the NFT vote, the swarm on appeal, and payment with a 10% fee. The first post names moneycanbuy.fun and carries your DOER CODE. Submit the link to the first post.
3. REWARD: $25–$60 in USDC. Writing a thread is more work than a single post, and stable value suits a writing job.
4. DEADLINE: 7 days from posting. A few hours of writing, with a week of slack.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • The first post contains moneycanbuy.fun and the DOER CODE.
   • The thread has at least five posts, all by the same account and chained as replies to the first.
   • Each of these six terms appears somewhere in the thread: "reward", "proof", "24 h" or "24 hours", "dispute", "NFT", "swarm".
   • The thread states that the accepted doer receives 90%, or that the fee is 10% (MECH, "Money and fees").
   • Every post is dated after task creation.
7. PROOF FORMAT: The link goes to the first post. The screenshot shows the full thread. The note says 5+ posts; terms: reward proof 24h dispute NFT swarm 10%.
8. ORIGINALITY CHECK: The DOER CODE is in post 1, and every post's timestamp is after task creation.
9. ANTI-FAKE / ANTI-AI CHECK: A voter counts the live replies under post 1 and checks that they all come from the same handle. A thread copied from someone else lacks this doer's code. Text written by an AI is not grounds to reject. A missing term or a missing code is.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE, with a 24 h dispute (TU §4), an NFT vote and the swarm on appeal (MECH, "Disputes"). The proof loses if there are fewer than five posts, a listed term is missing, the 10%/90% claim is missing, or the code is absent.

1.3 60-second screen recording walking through one live task page

1. TITLE: 60-second screen recording walking through one live task page
2. DESCRIPTION: Record one continuous screen capture of 45 to 120 seconds of the moneycanbuy.fun site showing any Open task's page. Narrate aloud, or use on-screen text, to cover its reward, currency, deadline and proof type. At the start, show a text editor or note on the same screen with your DOER CODE typed in it. Upload the recording to YouTube or X.
3. REWARD: $20–$50 in USDC.
4. DEADLINE: 10 days from posting. Recording and uploading are quick, and the extra days allow for editing tools and upload problems.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • The video runs 45 to 120 seconds and is uploaded after task creation.
   • The DOER CODE is visible in the first 10 seconds.
   • One Open task page is visible, and its reward, currency, deadline and proof type are each said aloud or shown as text.
   • The video description contains the DOER CODE and moneycanbuy.fun.
   • The capture has no cuts. One continuous recording means a cursor that never jumps between frames.
7. PROOF FORMAT: The link is a YouTube or X video URL. The screenshot shows the frame with the DOER CODE. The note says task #N shown; 0:00-0:10 code; no cuts.
8. ORIGINALITY CHECK: The DOER CODE appears both on screen and in the description, and the task shown was Open after this task was created.
9. ANTI-FAKE / ANTI-AI CHECK: A voter scrubs the video for a jump cut and checks that the on-screen task number and values match that task's on-chain TaskCreated data. A generated video would have to reproduce live values exactly.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE: a dispute within 24 h (TU §4), an NFT vote and the swarm on appeal (MECH, "Disputes"). The proof loses on a cut, a missing code, or task values that do not match the chain.

1.4 Hand-drawn diagram of a submission's states, posted on X

1. TITLE: Hand-drawn diagram of a submission's states, posted on X
2. DESCRIPTION: Draw on paper, by hand, the submission states Queued, Review, Voting, Decided, NoDecision, Asked, Final and Void, with arrows (MECH, "Submission lifecycle" diagram). Write your DOER CODE on the same sheet. Photograph the sheet and post the photo on X with moneycanbuy.fun in the text.
3. REWARD: $15–$40 in USDC.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • The photo is of paper, not a digital drawing.
   • All eight state names appear, written by hand.
   • At least seven arrows connect the states.
   • The DOER CODE is written by hand on the same sheet.
   • The post text contains moneycanbuy.fun.
   • The post is dated after task creation.
7. PROOF FORMAT: The link is to the X post. The screenshot is a full-resolution photo. The note says 8 states, hand-drawn, code on sheet.
8. ORIGINALITY CHECK: The handwritten DOER CODE sits on the sheet. Because the code is specific to this task, an older diagram cannot contain it.
9. ANTI-FAKE / ANTI-AI CHECK: Voters zoom in to check that the code is handwritten in the same ink as the diagram, with no pasted overlay or uniform font. An AI image rarely writes a 52-character code correctly, so the code must match exactly.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if a state name is missing, the code is wrong or typed, or the drawing is digital.

1.5 Reply-guy rescue: answer a stranger asking how bounties stay honest

1. TITLE: Reply-guy rescue: answer a stranger asking how bounties stay honest
2. DESCRIPTION: Find an existing X post by someone else that asks how online bounties, dares or freelance escrow stay honest. Reply to it with an explanation of moneycanbuy.fun's bond, dispute and vote mechanism. Your reply must contain your DOER CODE. Do not reply to posts that ask for no promotion, and do not tag accounts that are not part of the conversation.
3. REWARD: $10–$25 in USDC.
4. DEADLINE: 14 days from posting. Finding a fitting question takes searching, and two weeks is plenty.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • The proof is a reply, visible as a reply, to a post by a different account.
   • The parent post asks about honesty, trust or scams in bounties, dares or escrow.
   • The reply names moneycanbuy.fun and mentions both "bond" and "dispute".
   • The reply contains the DOER CODE and is dated after task creation.
7. PROOF FORMAT: The link goes to the reply's status. The screenshot shows the parent post and the reply together. The note quotes the parent's question in 200 bytes or fewer.
8. ORIGINALITY CHECK: The DOER CODE is in the reply.
9. ANTI-FAKE / ANTI-AI CHECK: Voters open the link and confirm that X shows it as a reply to a different handle, and that the parent post predates the reply. A parent post planted from a sock-puppet account created after the task was posted counts as a fake parent, and the proof fails.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the parent account is the doer's own or was created after the task, if the reply is off-topic, or if the code is missing.

1.6 Explain 'no author cancel' in exactly three sentences on X

1. TITLE: Explain 'no author cancel' in exactly three sentences on X
2. DESCRIPTION: Post on X, in exactly three sentences, why an author on moneycanbuy.fun cannot pull a reward away from a doer mid-review. Cover these three points: there is no author cancel, a withdrawal needs a public notice an hour ahead, and a submission sent during that hour locks the share until its result (MECH, "Task lifecycle → Withdraw"). Include your DOER CODE after the third sentence.
3. REWARD: $10–$20 in USDC.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • There are exactly three sentences, plus the code, plus moneycanbuy.fun.
   • The three facts above are each present.
   • The post makes no claim that contradicts MECH, "Withdraw".
   • The post is dated after task creation.
7. PROOF FORMAT: The link is to the X post. The note says 3 sentences: no cancel / 1h notice / locked by submission.
8. ORIGINALITY CHECK: The DOER CODE is in the post.
9. ANTI-FAKE / ANTI-AI CHECK: Voters count the sentences and check each one against MECH, "Withdraw". Correctness is objective, so it does not matter whether the text was AI-assisted.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the sentence count is not three, a fact is missing or wrong, or the code is missing.

1.7 Post a real-world flyer of moneycanbuy.fun on your own noticeboard or fridge

1. TITLE: Post a real-world flyer of moneycanbuy.fun on your own noticeboard or fridge
2. DESCRIPTION: Make a paper flyer, printed or handwritten, that says moneycanbuy.fun and gives one rule of the board in one line. Pin it to a surface you own or are explicitly allowed to use, such as your fridge or your own noticeboard. Do not use public walls, poles or other people's property. Film a continuous clip of at least 10 seconds that shows the flyer, then today's date on a phone lock screen, then your handwritten DOER CODE on a card next to the flyer, and post the clip on X.
3. REWARD: $10–$30 in USDC.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • The clip is one continuous shot of at least 10 seconds, posted on X or YouTube.
   • The flyer shows moneycanbuy.fun and one rule.
   • The phone lock screen shows a date after task creation.
   • The DOER CODE card is visible in the same shot as the flyer.
   • The post text states that the surface is the doer's own or used with permission.
7. PROOF FORMAT: The link is a video or X post. The screenshot shows the frame with the flyer and code together. The note says own fridge; date shown at 0:0X.
8. ORIGINALITY CHECK: The handwritten DOER CODE and the dated lock screen appear in one take.
9. ANTI-FAKE / ANTI-AI CHECK: Voters check that the camera moves without a cut from the flyer to the phone to the code. A generated or composited clip shows warping or a cut.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses on a cut, a missing date or code, or a flyer on public or someone else's property.

1.8 Livestream clip: read one live task aloud and say whether you'd do it

1. TITLE: Livestream clip: read one live task aloud and say whether you'd do it
2. DESCRIPTION: During a live stream on Twitch, Kick or YouTube, read aloud the title and condition of one Open moneycanbuy.fun task, then say "I would" or "I would not" do it and why, in at least one sentence. Show your DOER CODE on screen while you read. Submit a clip or VOD link to that moment.
3. REWARD: $20–$50 in USDC.
4. DEADLINE: 14 days from posting. Streamers stream on a schedule, and two weeks covers at least one stream for most of them.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • The link is a Twitch, Kick or YouTube VOD or clip of a live broadcast dated after task creation.
   • The task title and condition are read aloud and match the chain.
   • A verdict and a reason are spoken.
   • The DOER CODE is on screen during the reading.
7. PROOF FORMAT: The link is a clip or VOD, with a timestamp if possible. The note says task #N read at mm:ss; code overlay.
8. ORIGINALITY CHECK: The DOER CODE overlay and the live-broadcast date both appear.
9. ANTI-FAKE / ANTI-AI CHECK: The platform marks the VOD as a past broadcast with its date. Voters compare the spoken condition with the task's on-chain condition.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the video was not a live broadcast, the condition was misread, or the code is absent.

1.9 Write a 300-to-600-word blog post on how a doer's bond works

1. TITLE: Write a 300-to-600-word blog post on how a doer's bond works
2. DESCRIPTION: Publish a public article of 300 to 600 words on any blog platform explaining the doer's bond on moneycanbuy.fun. Cover these points: it is posted at submit, it is returned on acceptance, and it is lost if the proof is rejected. Cite the source file by name (docs/MECHANICS.md or docs/TOKEN-UTILITY.md). Put your DOER CODE in the first paragraph.
3. REWARD: $30–$80 in USDC.
4. DEADLINE: 10 days from posting.
5. PROOF TYPE: link
6. ACCEPTANCE CRITERIA:
   • The page is public and loads without a login.
   • The body is 300 to 600 words.
   • All three bond facts are stated.
   • A source file is named.
   • The DOER CODE is in the first paragraph.
   • A publish date after task creation is shown on the page.
   • The post does not state a specific bond amount as settled fact (see C1).
7. PROOF FORMAT: The link is the https:// article URL. The screenshot shows the top of the article with its date. The note gives the word count and the source cited.
8. ORIGINALITY CHECK: The DOER CODE is in paragraph 1.
9. ANTI-FAKE / ANTI-AI CHECK: Voters load the page and check the date and word count. Writing quality is not judged. The checks are factual accuracy against the named file and the code.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the word count is out of range, a fact is wrong or missing, the page sits behind a login, or the code is missing.

1.10 Meme template: 'Me after nobody disputed within 24 h'

1. TITLE: Meme template: 'Me after nobody disputed within 24 h'
2. DESCRIPTION: Make an original image meme that you drew or photographed yourself, with no copyrighted template, captioned "Me after nobody disputed within 24 h". Post it on X with moneycanbuy.fun and your DOER CODE in the post text.
3. REWARD: $10–$25 in $YOLO. It is a meme, and the project's meme token fits. Caveat R-LARGE: while YOLO has no reliable price, the submission counts as large. If the board shows no YOLO price, fund it in USDC instead.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • The image contains the exact caption.
   • The image is the doer's own drawing or photo.
   • The post text contains moneycanbuy.fun and the DOER CODE.
   • The post is dated after task creation.
7. PROOF FORMAT: The link is to the X post. The note says own photo/drawing, caption exact.
8. ORIGINALITY CHECK: The DOER CODE is in the post text.
9. ANTI-FAKE / ANTI-AI CHECK: A reverse-image search by the disputer finding an earlier identical image proves it is not the doer's own.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the caption differs, the image is found posted earlier by someone else, or the code is missing.

1.11 Record a 30-second voice-over of the four reward currencies

1. TITLE: Record a 30-second voice-over of the four reward currencies
2. DESCRIPTION: Record a video of 20 to 45 seconds in which your own voice names the board's four reward currencies, ETH, USDC, IMD and $YOLO, and says that a top-up must use the same currency as the task (MECH, "Task lifecycle → Top up"). Your handwritten DOER CODE must be on screen throughout.
3. REWARD: $15–$30 in IMD. It promotes IMD alongside the board. An IMD reward clears both the 0.5 IMD and the 1 IMD minimums at that size.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • The video is 20 to 45 seconds.
   • All four currencies are spoken.
   • The same-currency top-up rule is spoken.
   • The code is visible in all frames.
   • The video is uploaded after task creation.
7. PROOF FORMAT: The link is a YouTube or X video. The note says 4 currencies + same-currency rule; code on card.
8. ORIGINALITY CHECK: The handwritten DOER CODE is on screen the whole time.
9. ANTI-FAKE / ANTI-AI CHECK: Voters check that the card stays in frame for the full continuous take. A cut-away to a pasted overlay shows up as a frame jump.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if a currency or the rule is missing, or the code is not visible throughout.

SECTION 2: Shill IMD, the IMD swarm and IMD culture

2.1 X thread: what a 7-agent swarm panel with quorum 5 means

1. TITLE: X thread: what a 7-agent swarm panel with quorum 5 means
2. DESCRIPTION: Publish an X thread of at least three posts explaining the following. The IMD swarm answers a dispute question yes or no with a panel of at least 7 agents and a quorum of at least 5. An answer outside those limits counts as silence (MECH, "The swarm → Answer binding"; CR, "Task and submission fields on chain"). Post 1 names "IMD swarm" and carries your DOER CODE.
3. REWARD: $20–$50 in IMD. The task is about IMD, and paying in IMD makes that point.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • The thread has three or more posts on one account.
   • The numbers 7 and 5 are both stated with their roles: panel and quorum.
   • It states that the answer is yes/no.
   • It states that an invalid or late answer counts as silence.
   • The DOER CODE is in post 1.
   • Every post is dated after task creation.
7. PROOF FORMAT: The link goes to post 1. The note says panel 7 / quorum 5 / yes-no / silence.
8. ORIGINALITY CHECK: The DOER CODE is in post 1.
9. ANTI-FAKE / ANTI-AI CHECK: Voters check each number against the cited MECH section. A wrong number fails, whatever wrote it.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses on a wrong panel or quorum number, a missing silence rule, or a missing code.

2.2 Video: act out the IMD swarm answering yes/no as seven people (or seven hats)

1. TITLE: Video: act out the IMD swarm answering yes/no as seven people (or seven hats)
2. DESCRIPTION: Film a sketch of 30 to 120 seconds in which seven "agents" each vote yes or no on a made-up dare, and at least five agree. The agents can be seven willing adults or seven hats on one person. Say the outcome aloud. A sign with your DOER CODE must be in shot at the start. Anyone else who appears must be an adult who has agreed to appear.
3. REWARD: $25–$60 in IMD.
4. DEADLINE: 10 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • Seven distinct agents vote on screen.
   • At least five votes match, and the result spoken matches the majority.
   • The DOER CODE sign is visible in the first 10 seconds.
   • The video is uploaded after task creation, and its description contains "IMD swarm".
7. PROOF FORMAT: The link is a YouTube or X video. The note says 7 agents, N agree, result X; code at 0:0X.
8. ORIGINALITY CHECK: The DOER CODE sign is in the video.
9. ANTI-FAKE / ANTI-AI CHECK: Voters count the agents and votes frame by frame. A generated clip tends to fail at a consistent count of seven, and a miscount fails objectively.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if fewer than seven agents appear, fewer than five agree, or the code is missing.

2.3 Draw the DOER CODE format IMD-- as a poster

1. TITLE: Draw the DOER CODE format IMD-- as a poster
2. DESCRIPTION: Make a hand-drawn poster explaining why a moneycanbuy.fun proof carries the code IMD- plus the task id plus the full doer address. The reason is that a shorter part could be ground out by a vanity tool, letting a thief submit an honest doer's post first (CR, "Task and submission fields on chain"). Write your own real DOER CODE on the poster as the example. Post a photo on X.
3. REWARD: $15–$40 in IMD.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • The poster is hand-drawn on paper.
   • It shows the three parts of the code labelled.
   • It states the "full address, not a short part" reason.
   • The example is the doer's real DOER CODE.
   • The post is dated after task creation.
7. PROOF FORMAT: The link is to the X post. The screenshot is the full photo. The note says 3 parts labelled + vanity reason.
8. ORIGINALITY CHECK: The doer's real DOER CODE is the example on the poster.
9. ANTI-FAKE / ANTI-AI CHECK: Voters compare the 40 hex characters on the poster with the submitting address. Image generators garble long hex strings.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the code does not match the submitter byte for byte, or the reason is missing.

2.4 Explain 'silence is not an answer' in one X post

1. TITLE: Explain 'silence is not an answer' in one X post
2. DESCRIPTION: In one X post, explain what happens when the IMD swarm stays silent on an appeal. The caller's fee is lost, their bond comes back, the case returns to its previous state, and a new 24 h window starts (MECH, "The swarm → Silence on a call / appeal"). Include your DOER CODE.
3. REWARD: $10–$25 in IMD.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • It is a single post.
   • All four consequences are stated.
   • "IMD swarm" is named.
   • The DOER CODE is present.
   • The post is dated after task creation.
7. PROOF FORMAT: The link is to the X post. The note says fee lost / bond back / state restored / new 24h.
8. ORIGINALITY CHECK: The DOER CODE is in the post.
9. ANTI-FAKE / ANTI-AI CHECK: Voters check the four points against MECH, "Silence on a call / appeal".
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if any consequence is wrong or missing, or the code is absent.

2.5 On-chain shout-out: a self-transaction whose input data reads IMD SWARM 7 OF 5

1. TITLE: On-chain shout-out: a self-transaction whose input data reads IMD SWARM 7 OF 5
2. DESCRIPTION: From the address you submit with, send an Ethereum mainnet transaction of 0 ETH to that same address. Its input data must be the UTF-8 hex encoding of the text IMD SWARM 7 OF 5 IMD-<taskId>, using this task's id. You pay only your own gas. Submit the transaction hash.
3. REWARD: $10–$30 in ETH. The doer spends ETH on gas, so the reward replaces it in kind.
4. DEADLINE: 5 days from posting. It is a single transaction, and five days covers waiting for low gas.
5. PROOF TYPE: onchain_tx
6. ACCEPTANCE CRITERIA:
   • The transaction is on Ethereum mainnet and succeeded.
   • from equals the submitting doer address, and to equals the same address.
   • The value is 0.
   • The input data decodes exactly to IMD SWARM 7 OF 5 IMD-<this taskId>.
   • The block time is after task creation.
7. PROOF FORMAT: The proof is 0x plus 64 hex. The note says self-tx, data = IMD SWARM 7 OF 5 IMD-<id>.
8. ORIGINALITY CHECK: The task id is in the input data. The code rule for onchain_tx is that the transaction is sent from the doer (CR, "Task and submission fields on chain").
9. ANTI-FAKE / ANTI-AI CHECK: Anyone looks the hash up on chain and decodes the input. Nothing can be edited, because the data is the block's own.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the sender is wrong, the data differs, the transaction failed, or it predates the task.

2.6 Ninety-second explainer: why only identity.md NFT holders vote on disputes

1. TITLE: Ninety-second explainer: why only identity.md NFT holders vote on disputes
2. DESCRIPTION: Record a video of 45 to 90 seconds explaining four facts. Dispute votes on moneycanbuy.fun are cast by identity.md NFT holders, one NFT per vote. Holding $YOLO gives no vote (TU §9). A vote that matches the final outcome earns a share of the loser's bond (TU §4). Show your DOER CODE on a card.
3. REWARD: $20–$50 in IMD.
4. DEADLINE: 10 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • The video is 45 to 90 seconds.
   • All four facts are spoken.
   • The DOER CODE card is visible.
   • The video is uploaded after task creation.
7. PROOF FORMAT: The link is a YouTube or X video. The note says 1 NFT=1 vote / YOLO no vote / correct vote paid.
8. ORIGINALITY CHECK: The DOER CODE card is in the video.
9. ANTI-FAKE / ANTI-AI CHECK: Voters check each fact against TU §4 and §9, and look for a continuous shot with the card.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses on a wrong fact (for example "YOLO holders vote"), a missing card, or the wrong length.

2.7 Thread: the three ways a question reaches the IMD swarm

1. TITLE: Thread: the three ways a question reaches the IMD swarm

2. DESCRIPTION: Write an X thread of at least three posts that names the three routes by which the IMD swarm is asked about a moneycanbuy.fun proof (MECH, "The swarm → When asked"):

   • the mandatory check for large rewards;
   • callSwarm when the vote did not decide;
   • an appeal of an NFT decision.

   Put your DOER CODE in post 1.

3. REWARD: $20–$45 in IMD.

4. DEADLINE: 7 days from posting.

5. PROOF TYPE: x_post

6. ACCEPTANCE CRITERIA:

   • The thread has three or more posts.
   • All three routes are named, with the $300 / 40 IMD threshold for the first.
   • The DOER CODE is in post 1.
   • The thread is dated after task creation.

7. PROOF FORMAT: The link goes to post 1. The note says check >= $300 / callSwarm / appeal.

8. ORIGINALITY CHECK: The DOER CODE is in post 1.

9. ANTI-FAKE / ANTI-AI CHECK: Voters check the three routes and the threshold against MECH.

10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if a route or the threshold is missing or wrong, or the code is missing.

2.8 Write an IMD swarm haiku trilogy

1. TITLE: Write an IMD swarm haiku trilogy
2. DESCRIPTION: Post three original haiku (5-7-5 syllables in English) in a single X post. One is about the IMD swarm, one about an identity.md NFT vote, and one about a bond. The post also carries your DOER CODE.
3. REWARD: $10–$25 in IMD.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • There are three haiku, each with lines of 5, 7 and 5 syllables.
   • The topics are swarm, NFT vote and bond, one per haiku, with the topic word appearing in each.
   • The DOER CODE is present.
   • The post is dated after task creation.
7. PROOF FORMAT: The link is to the X post. The note gives the syllable counts, for example 5-7-5 x3.
8. ORIGINALITY CHECK: The DOER CODE is in the post.
9. ANTI-FAKE / ANTI-AI CHECK: A search of the exact first line finding an earlier post by another account proves the haiku was copied. Syllables are counted objectively.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses on a syllable miscount, a missing topic word, earlier text by someone else, or a missing code.

2.9 Blog post: 'One NFT, one vote', how an identity.md dispute vote works

1. TITLE: Blog post: 'One NFT, one vote', how an identity.md dispute vote works
2. DESCRIPTION: Publish a public article of 300 to 600 words on the identity.md NFT dispute vote. Cover the 24 h vote, one NFT per vote, the margin of 10 needed for a decision at vote end, and the fact that a vote with no decision can go to the swarm (MECH, "NFT voting"). Name the source files. The DOER CODE goes in paragraph 1. If you also mention TU §4's 20-vote early decision, flag it as a conflict between the files (C2).
3. REWARD: $30–$80 in IMD.
4. DEADLINE: 10 days from posting.
5. PROOF TYPE: link
6. ACCEPTANCE CRITERIA:
   • The page is public, with no login.
   • It is 300 to 600 words.
   • All four facts are stated.
   • A source file is named.
   • The code is in paragraph 1.
   • The page is dated after task creation.
7. PROOF FORMAT: The link is the https:// article. The note gives the word count and the four facts listed.
8. ORIGINALITY CHECK: The DOER CODE is in paragraph 1.
9. ANTI-FAKE / ANTI-AI CHECK: Voters check the facts against MECH, "NFT voting" and the date on the page.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if a fact is missing or wrong, the word count is out of range, or the code is missing.

2.10 Thirty-second video: show the order an appeal goes in, with sticky notes

1. TITLE: Thirty-second video: show the order an appeal goes in, with sticky notes
2. DESCRIPTION: In one continuous shot of 20 to 60 seconds, stick notes on a surface in this order: "Dispute", "NFT vote 24h", "Decided", "Appeal", "Reply 12h", "IMD swarm", "Final". Narrate each one as you place it (MECH, state diagram). The last note carries your DOER CODE.
3. REWARD: $15–$35 in IMD.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • The video is 20 to 60 seconds, in one shot.
   • The seven notes are placed in the stated order.
   • The last note shows the DOER CODE.
   • The video is uploaded after task creation.
7. PROOF FORMAT: The link is a YouTube or X video. The note says 7 notes in order; code on last.
8. ORIGINALITY CHECK: The DOER CODE is on the final note.
9. ANTI-FAKE / ANTI-AI CHECK: Hands place the notes live in a continuous shot. Voters check the order and look for cuts.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the order is wrong, there is a cut, or the code is missing.

2.11 Quote-post: the IMD swarm's answer is final, explained like a sports referee

1. TITLE: Quote-post: the IMD swarm's answer is final, explained like a sports referee
2. DESCRIPTION: Write one X post that explains, through a referee or umpire analogy, that a valid IMD swarm answer ends a moneycanbuy.fun case: yes means Accepted and no means Rejected (MECH, "The swarm → Final"). It must also state that the NFT vote comes before the swarm. Include your DOER CODE.
3. REWARD: $10–$20 in IMD.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • The post uses a referee or umpire analogy.
   • It states yes = Accepted and no = Rejected, and that the answer is final.
   • It states that the NFT vote comes first.
   • The code is present, and the post is dated after task creation.
7. PROOF FORMAT: The link is to the X post. The note says referee analogy; yes=accept no=reject; NFT first.
8. ORIGINALITY CHECK: The DOER CODE is in the post.
9. ANTI-FAKE / ANTI-AI CHECK: Voters check the three facts against MECH.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if a fact is missing or reversed, or the code is missing.

SECTION 3: Viral and unhinged, but safe and legal

General safety rule for this section, to put in each condition: nothing dangerous, nobody filmed without consent, no minors on camera, no public property or other people's property used, and no animal stressed.

3.1 Give your houseplant a formal job interview for 'Dispute Juror'

1. TITLE: Give your houseplant a formal job interview for 'Dispute Juror'
2. DESCRIPTION: Film a mock job interview of 45 to 120 seconds with a houseplant you own, for the position "Dispute Juror". Ask it at least three questions and "hear" its answers. Wear something formal on your top half. Your DOER CODE must be on a name card in front of the plant.
3. REWARD: $15–$40 in USDC.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • The video is 45 to 120 seconds and shows one plant.
   • Three or more questions are asked aloud, and the phrase "Dispute Juror" is said.
   • The name card with the DOER CODE is visible.
   • Nobody but the doer appears.
   • The video is uploaded after task creation.
7. PROOF FORMAT: The link is a YouTube or X video. The note says 3 questions; card w/ code.
8. ORIGINALITY CHECK: The DOER CODE name card is in the video.
9. ANTI-FAKE / ANTI-AI CHECK: It must be one continuous shot with a real plant and the card in frame. Voters check that the card stays legible and steady with no compositing seams.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if there are fewer than three questions, the phrase is missing, the code is missing, or another person appears without stated consent.

3.2 Sea shanty about the doer's bond, 45 to 90 seconds, sung by you

1. TITLE: Sea shanty about the doer's bond, 45 to 90 seconds, sung by you
2. DESCRIPTION: Sing an original sea shanty of 45 to 90 seconds about posting a bond, waiting out the 24 h window and getting paid. The singing must be in your own voice, on camera, with no AI voice. The chorus must include the line "twenty-four hours and no dispute". The DOER CODE is shown on paper.
3. REWARD: $20–$50 in $YOLO. Comedy content suits the meme token. Caveat R-LARGE applies; use USDC if no YOLO price is shown.
4. DEADLINE: 10 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • The video is 45 to 90 seconds.
   • The doer's face is visible while singing.
   • The chorus line is sung at least twice.
   • The code paper is visible.
   • The video is uploaded after task creation.
7. PROOF FORMAT: The link is a YouTube or X video. The note gives the chorus timestamps.
8. ORIGINALITY CHECK: The DOER CODE paper is visible, and the chorus line is new to this task.
9. ANTI-FAKE / ANTI-AI CHECK: Voters check lip-sync against the audio across a continuous shot. A dubbed AI voice drifts off the mouth movements.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the face is not visible, the chorus is missing, the lip-sync is clearly mismatched, or the code is missing.

3.3 Nature-documentary narration of your pet (or a toy) doing nothing for 60 s

1. TITLE: Nature-documentary narration of your pet (or a toy) doing nothing for 60 s
2. DESCRIPTION: Film 60 to 120 seconds of your own resting pet, or a stuffed toy, behaving as it normally would, and narrate it in a nature-documentary voice. Do not wake, move or stress the animal. Say the word "escrow" at least once. The DOER CODE is on a card in frame.
3. REWARD: $15–$35 in USDC.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • The video is 60 to 120 seconds, with narration throughout.
   • "Escrow" is spoken.
   • The animal is not handled or disturbed on camera.
   • The card is visible.
   • The video is uploaded after task creation.
7. PROOF FORMAT: The link is a YouTube or X video. The note says "escrow" at mm:ss; card in frame.
8. ORIGINALITY CHECK: The DOER CODE card is in frame.
9. ANTI-FAKE / ANTI-AI CHECK: Continuous footage with the card in the same physical scene. Voters look for an overlaid card.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the animal is disturbed, the word is missing, or the card is missing.

3.4 Bake a cake iced with 'OPEN → COMPLETED'

1. TITLE: Bake a cake iced with 'OPEN → COMPLETED'
2. DESCRIPTION: Bake or decorate a cake, cupcake or tray bake with "OPEN → COMPLETED" written in icing, and put a paper flag with your DOER CODE on it. Post a photo and one bite-reaction sentence on X.
3. REWARD: $15–$40 in USDC.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • The photo shows a real baked item with "OPEN" and "COMPLETED" in icing and an arrow between them.
   • The DOER CODE flag is visible in the same photo.
   • The post text contains one sentence describing the taste.
   • The post is dated after task creation.
7. PROOF FORMAT: The link is to the X post. The note says icing text + flag.
8. ORIGINALITY CHECK: The DOER CODE flag is in the photo.
9. ANTI-FAKE / ANTI-AI CHECK: AI images garble long codes. The code on the flag must match the submitter exactly, and a garbled or overlaid code fails.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the icing text is wrong, the flag code does not match, or the item is not a baked good.

3.5 Shakespearean monologue: 'To dispute, or not to dispute'

1. TITLE: Shakespearean monologue: 'To dispute, or not to dispute'
2. DESCRIPTION: Perform on camera an original monologue of 45 to 120 seconds that opens with "To dispute, or not to dispute" and mentions the bond and the 24-hour window. A prop skull is optional; a stuffed toy works as one. The DOER CODE appears on a scroll or paper you hold up.
3. REWARD: $20–$45 in $YOLO (caveat R-LARGE), or USDC.
4. DEADLINE: 10 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • The video is 45 to 120 seconds.
   • It opens with the exact line.
   • "bond" and "twenty-four hours" are spoken.
   • The DOER CODE is held up on camera.
   • The doer performs, with their face visible, and the video is uploaded after task creation.
7. PROOF FORMAT: The link is a YouTube or X video. The note says opening line 0:00; code shown at mm:ss.
8. ORIGINALITY CHECK: The DOER CODE scroll is visible.
9. ANTI-FAKE / ANTI-AI CHECK: It is one continuous take. Voters check lip-sync and that the paper is physically held.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the opening line or the required words are missing, the code is missing, or the voice is dubbed.

3.6 Register your pet rock on chain with a self-transaction

1. TITLE: Register your pet rock on chain with a self-transaction
2. DESCRIPTION: Name a rock you own. From your submitting address, send a 0-ETH Ethereum mainnet transaction to yourself whose input data is the UTF-8 hex of PET ROCK <name> IMD-<taskId>. Submit the transaction hash. Optionally attach a screenshot of the rock next to the name written on paper.
3. REWARD: $10–$25 in ETH, which covers gas in kind.
4. DEADLINE: 5 days from posting.
5. PROOF TYPE: onchain_tx
6. ACCEPTANCE CRITERIA:
   • The transaction is on mainnet and succeeded.
   • from and to are both the submitting address.
   • The value is 0.
   • The input decodes to PET ROCK followed by a name of 1 to 20 letters, a space, and IMD-<this taskId>.
   • The block time is after task creation.
7. PROOF FORMAT: The proof is 0x plus 64 hex. The note gives the decoded text.
8. ORIGINALITY CHECK: The task id is in the calldata, and the sender is the doer.
9. ANTI-FAKE / ANTI-AI CHECK: Anyone decodes the input from the chain. The screenshot is optional and is not judged.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the sender, recipient or data is wrong, the transaction failed, or it predates the task.

3.7 Recreate a famous painting using only kitchen utensils

1. TITLE: Recreate a famous painting using only kitchen utensils
2. DESCRIPTION: Arrange only kitchen utensils (spoons, forks, whisks, pans and the like) on a flat surface to recreate a public-domain painting painted before 1900. Name the painting in your post. Photograph the arrangement with your DOER CODE written on a paper towel inside the frame.
3. REWARD: $15–$40 in USDC.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • The arrangement uses kitchen utensils only, with no paint or printouts.
   • The painting is named and dates from before 1900.
   • The code is on a paper towel in the frame.
   • The post is dated after task creation.
7. PROOF FORMAT: The link is to the X post. The note gives the painting's name and year.
8. ORIGINALITY CHECK: The DOER CODE paper towel is in the photo.
9. ANTI-FAKE / ANTI-AI CHECK: Voters check that the code matches exactly. Generated images fail on long hex strings and show impossible utensil shapes.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if non-utensil materials are used, the painting is not named or dates from 1900 or later, or the code is wrong.

3.8 Cardboard-box TaskVault: build the vault and lock a cookie inside it for 24 h

1. TITLE: Cardboard-box TaskVault: build the vault and lock a cookie inside it for 24 h
2. DESCRIPTION: Label a cardboard box "TASKVAULT" and put a cookie inside, sealed with tape on which you sign your name and today's date. Film the sealing next to a phone showing the date and time. Twenty-four hours or more later, film yourself opening the box (the same tape, now cut) next to the phone, then eat the cookie or hand it to a consenting adult. Post both clips in one X thread with the DOER CODE in post 1.
3. REWARD: $15–$35 in USDC.
4. DEADLINE: 7 days from posting. The job needs a 24 h wait, and a week leaves room for it.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • There are two clips in one thread, each one continuous.
   • The phone time in clip 2 is at least 24 h after the phone time in clip 1.
   • The signed tape is visible in both clips.
   • The DOER CODE is in post 1.
   • Both posts are dated after task creation.
7. PROOF FORMAT: The link goes to post 1, which contains a video. The note gives both phone times.
8. ORIGINALITY CHECK: The DOER CODE is in post 1, and the two X post timestamps are at least 24 h apart.
9. ANTI-FAKE / ANTI-AI CHECK: X's own post times must also be at least 24 h apart, which a doer cannot edit. Voters also compare the signature on the tape across both clips.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the post times are less than 24 h apart, the tape differs, or the code is missing.

3.9 Dramatic slow-motion reading of the creation-fee rule

1. TITLE: Dramatic slow-motion reading of the creation-fee rule
2. DESCRIPTION: Read the sentence "Creation fee: at least 0.0005 ETH, to the treasury, never refunded" (MECH, "Money and fees") in the most dramatic way you can, filmed in slow motion. Use a fan or wind effect, but no fire or anything hazardous. The DOER CODE appears on a card at the end.
3. REWARD: $10–$30 in ETH. The joke is about an ETH fee.
4. DEADLINE: 7 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • The video is 15 to 90 seconds.
   • The sentence is read word for word, with "0.0005 ETH" and "never refunded" audible.
   • Slow motion is used.
   • The code card is visible at the end.
   • No hazardous props are used.
   • The video is uploaded after task creation.
7. PROOF FORMAT: The link is a YouTube or X video. The note says sentence verbatim; card at end.
8. ORIGINALITY CHECK: The DOER CODE card is in the video.
9. ANTI-FAKE / ANTI-AI CHECK: Voters check that the spoken words match the source sentence and that the card is physical.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the wording is wrong, there is no slow motion, the code is missing, or a hazardous prop is used.

3.10 Sock-puppet courtroom: puppets act out a dispute vote

1. TITLE: Sock-puppet courtroom: puppets act out a dispute vote
2. DESCRIPTION: Using at least three sock puppets (a doer, a disputer and a voter), act out a dispute in 60 to 180 seconds. The doer submits a proof link, the disputer posts a bond, and the voter decides. Make sure the line "only the doer can't dispute" is said, which reflects MECH, "Participants". A puppet holds up the DOER CODE.
3. REWARD: $20–$50 in $YOLO (caveat R-LARGE), or USDC.
4. DEADLINE: 10 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • Three or more puppets appear, and the video is 60 to 180 seconds.
   • The three roles are named aloud.
   • The exact line is spoken.
   • The code is shown by a puppet.
   • The video is uploaded after task creation.
7. PROOF FORMAT: The link is a YouTube or X video. The note says 3 roles; line at mm:ss; code at mm:ss.
8. ORIGINALITY CHECK: The DOER CODE is held by a puppet.
9. ANTI-FAKE / ANTI-AI CHECK: It is a continuous physical puppet scene. Voters check that the code card is a real object in the scene.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if a role or the line is missing, or the code is missing.

3.11 Wear a paper crown reading 'MONEY CAN BUY' for one full video call

1. TITLE: Wear a paper crown reading 'MONEY CAN BUY' for one full video call
2. DESCRIPTION: Make a paper crown reading "MONEY CAN BUY" and wear it for a whole video call of at least 15 minutes with consenting adults, who are told about it in advance. Do not record the call. Afterwards, film yourself still wearing it next to a phone that shows the call log entry, with its date and length visible and other participants' names covered. Hold up your DOER CODE in the same clip.
3. REWARD: $10–$30 in USDC.
4. DEADLINE: 10 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • It is one continuous clip.
   • The crown text is legible.
   • The call log shows a duration of 15 minutes or more and a date after task creation.
   • Participant names are covered.
   • The code is shown.
   • The call itself is not recorded.
7. PROOF FORMAT: The link is a YouTube or X video. The note gives the call's date and duration.
8. ORIGINALITY CHECK: The DOER CODE and the dated call log appear in one shot.
9. ANTI-FAKE / ANTI-AI CHECK: Voters check for a continuous shot from the crown to the phone to the code, and that the log date is after task creation.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). The proof loses if the duration is under 15 minutes, names are exposed, the date is wrong, or the code is missing.

SECTION 4: Impossible tasks, kept for hype

Read before posting any of these. Under R-ACCEPT, a proof that nobody disputes within 24 h is paid. These tasks are impossible to complete, but they are safe from payout only while someone disputes every fake. (inference) The author, or a watcher, should check the board while any submission on these tasks is in Review. Keep the reward under $300 so a doer cannot hope to pass on a silent mandatory check (MECH, "Mandatory swarm check": silence opens a normal window). A low reward also limits what is locked until the deadline.

4.1 Photograph the surface of the Sun from the surface of the Sun

1. TITLE: Photograph the surface of the Sun from the surface of the Sun
2. DESCRIPTION: Post on X a photo taken by you while standing on the Sun's surface, with your handwritten DOER CODE in the frame. Telescope, satellite and agency images do not count. The camera and the doer must both be physically on the Sun.
3. REWARD: $20–$100 in $YOLO. It is a hype piece. With no YOLO price, any submission counts as large (MECH, "Rules worth knowing" #9), which makes fake attempts dearer.
4. DEADLINE: 30 days from posting. That is long enough to keep the joke trending, and short enough that the funds come back within a month.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • The photo was taken on the Sun's surface.
   • The doer and the code card are physically present there.
   • The post is dated after task creation.
7. PROOF FORMAT: The link is to the X post. The note gives the location.
8. ORIGINALITY CHECK: A handwritten DOER CODE card in the frame.
9. ANTI-FAKE / ANTI-AI CHECK: Paper burns long before it reaches the Sun, and no human can survive there. Any image of a legible card "on the Sun" is therefore edited or generated by definition.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE: a dispute within 24 h with the dispute bond (TU §4), an NFT vote, and the swarm on appeal (MECH, "Disputes"). No submission can pass a vote, because the claim is physically impossible, so any image is fabricated.
11. REFUND PATH: There is no author cancel (MECH, "Task lifecycle → Withdraw"). When the 30-day deadline passes with no active submission, the task becomes Expired. Every contributor, the author included, then withdraws their own share, and any $YOLO add-on returns to whoever added it (TU §2). The creation fee of at least 0.0005 ETH is never refunded (MECH, "Money and fees"). A submission still being judged at the deadline delays Expired until it ends.

4.2 Submit a mainnet transaction whose hash is all zeros, sent from your address

1. TITLE: Submit a mainnet transaction whose hash is all zeros, sent from your address
2. DESCRIPTION: Submit an Ethereum mainnet transaction, sent from your submitting address, whose transaction hash is 0x followed by 64 zeros.
3. REWARD: $20–$100 in ETH. It's a crypto-native joke for a crypto-native currency.
4. DEADLINE: 30 days from posting.
5. PROOF TYPE: onchain_tx
6. ACCEPTANCE CRITERIA:
   • The proof equals 0x followed by 64 zeros.
   • A transaction with that hash exists on mainnet.
   • Its from is the submitting doer.
7. PROOF FORMAT: The proof is that hash. The note is optional.
8. ORIGINALITY CHECK: The transaction must be sent from the doer's address (CR, "Task and submission fields on chain").
9. ANTI-FAKE / ANTI-AI CHECK: Anyone looks the hash up on chain. No mined transaction has it, so the lookup fails.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). No submission can pass, because finding such a hash means inverting Keccak-256, which is computationally infeasible. Any hash submitted either is not all zeros or does not exist on chain, which anyone can check.
11. REFUND PATH: There is no author cancel (MECH, "Withdraw"). When the 30-day deadline passes with no active submission, the task becomes Expired and every contributor withdraws their own share. The creation fee of at least 0.0005 ETH is not refunded (MECH, "Money and fees").

4.3 Count aloud to infinity, finished, in one unedited video

1. TITLE: Count aloud to infinity, finished, in one unedited video
2. DESCRIPTION: Upload one unedited video of yourself counting aloud through every positive whole number and finishing, with your DOER CODE visible at the end.
3. REWARD: $20–$80 in $YOLO (hype; see the 4.1 note).
4. DEADLINE: 14 days from posting. A short window makes the joke sharper and gets the funds back sooner.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • It is one continuous video.
   • Every positive integer is spoken.
   • The count ends.
   • The code appears at the end.
7. PROOF FORMAT: The link is a YouTube or X video. The note gives the last number said.
8. ORIGINALITY CHECK: The DOER CODE is visible at the end.
9. ANTI-FAKE / ANTI-AI CHECK: Any video has finite length, and any last number has a successor that was not said.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). No submission can pass, because a finished count of an infinite set is logically impossible. A disputer just names the last number plus one.
11. REFUND PATH: There is no author cancel (MECH, "Withdraw"). When the 14-day deadline passes with no active submission, the task becomes Expired. Each contributor withdraws their own share, and $YOLO add-ons return to whoever added them (TU §2). The creation fee is not refunded (MECH, "Money and fees").

4.4 An X post containing this task's DOER CODE, dated before the year 2006

1. TITLE: An X post containing this task's DOER CODE, dated before the year 2006
2. DESCRIPTION: Submit an X (Twitter) post from your account that contains your DOER CODE for this task and whose platform-shown date is before 1 January 2006.
3. REWARD: $20–$80 in USDC.
4. DEADLINE: 21 days from posting.
5. PROOF TYPE: x_post
6. ACCEPTANCE CRITERIA:
   • The post contains the full DOER CODE.
   • X shows the post's date as before 2006-01-01.
7. PROOF FORMAT: The link is to the X post. The note gives the post's date.
8. ORIGINALITY CHECK: The DOER CODE contains this task's id, which did not exist before the task was created.
9. ANTI-FAKE / ANTI-AI CHECK: Voters open the link and read the date X itself shows. Screenshots are not accepted as the date source.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). No submission can pass, because the code includes a task id created years after 2006. A post cannot carry it at an earlier date, and the date X shows is not under the doer's control.
11. REFUND PATH: There is no author cancel (MECH, "Withdraw"). When the 21-day deadline passes with no active submission, the task becomes Expired and each contributor withdraws their own share. The creation fee is not refunded (MECH, "Money and fees").

4.5 Draw a square circle and have it verified as both

1. TITLE: Draw a square circle and have it verified as both
2. DESCRIPTION: Publish one drawn figure, on a public page, that is simultaneously a Euclidean square (four equal straight sides, four right angles) and a Euclidean circle (every point the same distance from a centre). Put your DOER CODE on the page.
3. REWARD: $20–$80 in IMD. Logic jokes for the swarm crowd.
4. DEADLINE: 21 days from posting.
5. PROOF TYPE: link
6. ACCEPTANCE CRITERIA:
   • One figure meets both definitions in the Euclidean plane.
   • The code is on the page.
   • The page is dated after task creation.
7. PROOF FORMAT: The link is an https:// page. The note gives the figure's description.
8. ORIGINALITY CHECK: The DOER CODE is on the page.
9. ANTI-FAKE / ANTI-AI CHECK: Voters check the two definitions: a figure with straight sides has corner points that sit farther from the centre than the midpoints of its sides.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). No submission can pass, because the two definitions contradict each other in Euclidean geometry. Non-Euclidean or "metric" redefinitions are excluded by the condition.
11. REFUND PATH: There is no author cancel (MECH, "Withdraw"). When the 21-day deadline passes with no active submission, the task becomes Expired and each contributor withdraws their own share. The creation fee is not refunded (MECH, "Money and fees").

4.6 Publish the largest prime number

1. TITLE: Publish the largest prime number
2. DESCRIPTION: Publish on a public page a prime number that is larger than every other prime number, with your DOER CODE. A "largest known" prime does not count. It must be the largest prime that exists.
3. REWARD: $20–$80 in IMD.
4. DEADLINE: 21 days from posting.
5. PROOF TYPE: link
6. ACCEPTANCE CRITERIA:
   • The number is prime.
   • No prime larger than it exists.
   • The code is on the page.
7. PROOF FORMAT: The link is an https:// page. The note gives the number's digit count.
8. ORIGINALITY CHECK: The DOER CODE is on the page.
9. ANTI-FAKE / ANTI-AI CHECK: Euclid's proof gives a larger prime for any finite list, so a disputer cites that proof.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). No submission can pass, because there are infinitely many primes, so no largest one exists.
11. REFUND PATH: There is no author cancel (MECH, "Withdraw"). When the 21-day deadline passes with no active submission, the task becomes Expired and each contributor withdraws their own share. The creation fee is not refunded (MECH, "Money and fees").

4.7 Hand-write every digit of pi, all of them

1. TITLE: Hand-write every digit of pi, all of them
2. DESCRIPTION: Film yourself hand-writing every decimal digit of pi, ending with the last one, in one continuous video, with your DOER CODE on the first page.
3. REWARD: $20–$80 in $YOLO (hype; see the 4.1 note).
4. DEADLINE: 14 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • It is one continuous video.
   • All digits are written.
   • A final digit is reached.
   • The code is on page 1.
7. PROOF FORMAT: The link is a YouTube or X video. The note gives the claimed last digit.
8. ORIGINALITY CHECK: The DOER CODE is on page 1.
9. ANTI-FAKE / ANTI-AI CHECK: Pi is irrational, so it has no last digit. Any "last digit" claim fails on its face.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). No submission can pass, because pi's decimal expansion is infinite and does not repeat.
11. REFUND PATH: There is no author cancel (MECH, "Withdraw"). When the 14-day deadline passes with no active submission, the task becomes Expired. Each contributor withdraws their own share, and $YOLO add-ons return to whoever added them (TU §2). The creation fee is not refunded (MECH, "Money and fees").

4.8 Be in two cities at once, in one continuous shot

1. TITLE: Be in two cities at once, in one continuous shot
2. DESCRIPTION: In one continuous, unedited video, appear physically in two cities at least 100 km apart at the same moment. Hold your DOER CODE in both places.
3. REWARD: $20–$80 in USDC.
4. DEADLINE: 21 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • The same single person is physically present in both cities simultaneously.
   • The video is one unedited shot.
   • The code is visible in both places.
7. PROOF FORMAT: The link is a YouTube or X video. The note names the two cities.
8. ORIGINALITY CHECK: The DOER CODE appears in both locations.
9. ANTI-FAKE / ANTI-AI CHECK: Split screens, twins, mirrors, screens and video calls are excluded. Any of them shows a seam, a second person, or a display.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). No submission can pass, because one body cannot occupy two places at once. Every possible submission is therefore a composite or a second person, which a disputer names.
11. REFUND PATH: There is no author cancel (MECH, "Withdraw"). When the 21-day deadline passes with no active submission, the task becomes Expired and each contributor withdraws their own share. The creation fee is not refunded (MECH, "Money and fees").

4.9 Fold one sheet of paper in half 104 times on camera

1. TITLE: Fold one sheet of paper in half 104 times on camera
2. DESCRIPTION: In one unedited video, fold a single ordinary sheet of paper in half 104 times, counting each fold aloud. Your DOER CODE must be written on the sheet before folding starts.
3. REWARD: $20–$80 in $YOLO (hype; see the 4.1 note).
4. DEADLINE: 14 days from posting.
5. PROOF TYPE: video
6. ACCEPTANCE CRITERIA:
   • It is one sheet and one continuous video.
   • 104 folds are made, each a full half-fold, and counted aloud.
   • The code is shown on the sheet before fold 1.
7. PROOF FORMAT: The link is a YouTube or X video. The note says 104 folds; code at 0:0X.
8. ORIGINALITY CHECK: The DOER CODE is on the sheet.
9. ANTI-FAKE / ANTI-AI CHECK: At 0.1 mm thick, 2^104 layers would measure about 2×10^27 m, which is larger than the observable universe. Voters stop counting at the fold where it visibly fails.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). No submission can pass, because the final stack could not fit in the universe, let alone in a camera frame.
11. REFUND PATH: There is no author cancel (MECH, "Withdraw"). When the 14-day deadline passes with no active submission, the task becomes Expired. Each contributor withdraws their own share, and $YOLO add-ons return to whoever added them (TU §2). The creation fee is not refunded (MECH, "Money and fees").

4.10 A transaction of yours included in Ethereum's genesis block

1. TITLE: A transaction of yours included in Ethereum's genesis block
2. DESCRIPTION: Submit the hash of a mainnet transaction sent from your submitting address and included in Ethereum's block 0, the genesis block.
3. REWARD: $20–$100 in ETH.
4. DEADLINE: 30 days from posting.
5. PROOF TYPE: onchain_tx
6. ACCEPTANCE CRITERIA:
   • The hash resolves on mainnet.
   • Its block number is 0.
   • Its from is the submitting doer.
7. PROOF FORMAT: The proof is 0x plus 64 hex. The note says block 0.
8. ORIGINALITY CHECK: The transaction must be sent from the doer's address (CR, "Task and submission fields on chain").
9. ANTI-FAKE / ANTI-AI CHECK: Anyone looks the hash up and reads its block number. The genesis block contains no transactions.
10. HOW A FALSE SUBMISSION IS REJECTED: R-DISPUTE (TU §4; MECH, "Disputes"). No submission can pass, because block 0 has no transactions at all, so every submitted hash is either not found or sits in a later block.
11. REFUND PATH: There is no author cancel (MECH, "Withdraw"). When the 30-day deadline passes with no active submission, the task becomes Expired and each contributor withdraws their own share. The creation fee of at least 0.0005 ETH is not refunded (MECH, "Money and fees").