> For the complete documentation index, see [llms.txt](https://gimi.gitbook.io/gimi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gimi.gitbook.io/gimi/case-studies/web-3/polyprize-2-making-web3-easy-one-new-account-at-a-time.md).

# PolyPrize 2: “Making Web3 Easy — One New Account at a Time”

#### <mark style="color:$success;">**Overview**</mark>

MyUnicornAccount and Polygon are on a mission to make Web3 onboarding instant, effortless, and fun. The goal was simple: show the world that joining Web3 is no longer a technical hurdle — it’s as easy as creating an email login.

To prove it, Polygon partnered with GIMI to launch **PolyPrize Round 2**, a creator-driven activation built entirely around *new accounts, new wallets, and real on-chain actions*.\
No crypto experience required.\
No gas.\
No friction.

The objective wasn’t just awareness — it was **mass conversion**: get people to create fresh Polygon Accounts, claim an NFT, and showcase how fast and simple Web3 can be in 2025.

#### <mark style="color:$success;">**The Campaign**</mark>

The PolyPrize 2 campaign invited creators to demonstrate the “before & after” of joining Polygon using MyUnicornAccount. All content revolved around **starting fresh** — a brand-new account, a new NFT, and a real on-chain action completed in seconds.

This campaign turned Web3 onboarding into social content — and the results spoke for themselves.

### **Key Results**

* **Total Spend:** **$600**
* **Total Contributions:** **400**
* **Total Engagements:** **30,000**
* **Total Views:** **400,000**

Of the 400 total submissions:

#### **250 users successfully created a new Polygon Account&#x20;*****and*****&#x20;completed the on-chain NFT claim.**

This represents:

#### **🔥 62.5% Full-Funnel Conversion**

(content creator → new account → NFT claim → on-chain action)

This is an exceptionally high rate for Web3, where typical conversion across similar funnels ranges from **8% to 20%**.

**Why this matters:**\
This campaign required **three meaningful actions**, all completed by real people:

✔ Creating a fresh Web3 account\
✔ Claiming an NFT\
✔ Executing an on-chain transaction\
✔ Posting content explaining the process

This proves Polygon’s onboarding flow is simple enough for mainstream users — not just crypto natives.

#### <mark style="color:$success;">**Impact**</mark>

PolyPrize 2 delivered something rarely seen in Web3:\
**hundreds of new, verifiable on-chain users created organically through social content.**

Creators didn’t just talk about Polygon — they *demonstrated* Polygon.\
They showed their audiences what it looks like to join Web3 in under 30 seconds. Skits, memes, screen-recordings, and POVs flooded social media, transforming onboarding into culture.

#### <mark style="color:$success;">**Takeaway**</mark>

Web3 onboarding is no longer a challenge — it’s a content moment.

PolyPrize 2 proved that when you make blockchain simple, fun, and rewarding:\
**people don’t just sign up… they go on-chain.**

[VIEW CAMPAIGN](https://app.gimi.co/en/p/org/unicorn-eth)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gimi.gitbook.io/gimi/case-studies/web-3/polyprize-2-making-web3-easy-one-new-account-at-a-time.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.