Share article

Nansen is trying to turn its on-chain data stack into something developers actually ship with, and it is dangling a Mac Mini M4 to make the point. Earlier today, the firm behind the Nansen analytics platform posted that Week 2 of its #NansenCLI Challenge is now mid-flight, with submissions closing on March 29 at 11:59 PM SGT.
Crypto News Summary March 24

The post was a quote tweet of Nansen's own Week 2 announcement. In the original message, Nansen set the window as March 23 to March 29 (SGT) and laid out judging criteria that are unusually specific for a crypto "build" campaign: creativity, real-world usefulness, technical depth, and presentation clarity. It also flagged an operational detail that matters for anyone expecting to be paid: winners will be contacted by DM for verification before prizes are sent.

Nansen's new commentary adds two bits of signal. First, it claims "40+ submissions" arrived in Week 1, which suggests the challenge is attracting more than the usual low-effort hackathon churn. Second, it explicitly nudges entrants towards demos, noting that video or demo submissions "tend to stand out". That is effectively an optimisation hint: judging is not purely code-review driven, it is also about communicating what you built and why it works.
The incentives for Week 2 are unchanged: first prize is one Mac Mini M4 (16GB RAM, 256GB SSD), second gets 50,000 Nansen API credits, and third gets 10,000 credits. For builders already paying for data access, the credits can be the more meaningful reward than the hardware. For everyone else, it is a way of pulling developers deeper into Nansen's API surface area and CLI tooling, which in turn can increase stickiness for teams that automate wallet labels, token flows, and alerting.
Nansen Smart Alerts Adds Custom Webhooks for All

One community reply pointed to Nansen's eligibility requirements via an external link, a reminder that these promos often come with restrictions (jurisdiction, age, verification, and similar). Anyone building with the expectation of collecting prizes should check that page before sinking time into a proper submission.

Why this matters: CLI tooling is where a lot of serious on-chain work happens, especially for quants and ops teams that need repeatable pipelines. If Nansen can get developers to standardise workflows around its CLI and API credits, it strengthens its position as infrastructure, not just a dashboard.

Risk check: the fastest way for this to fizzle is if winners feel the verification process is opaque, or if the "40+ submissions" number does not translate into genuinely useful open-source outputs. The real tell will be whether Week 2 produces tools people keep using after the prizes are gone.

Companies Referenced

Nansen logo

Nansen

Tags

#On-chain analytics#Nansen#Nansen CLI#Developer challenge#Crypto devtools#API credits#Hackathon#Mac Mini M4#Builder incentives#Developer outreach

Original tweet