The dev-trader relationship

What each side wants

The dev launches the token, promotes it, and may build a product or run a community. Traders decide whether to buy, hold, add, or sell. Both sides can return to these steps as conditions change.

The dev may earn a share of trading fees whenever qualifying trades happen. It may also sell its own tokens. A trader who buys tokens needs enough demand and liquidity to sell at an acceptable price. This is why the dev can earn money during a busy market while some traders lose money.

Where their interests meet

Useful work, honest updates, and credible promotion can bring buyers and returning users. Trading fees can help pay for more work. Check what was delivered, where the money went, and whether people keep participating.

Their interests can move apart when the dev earns fees without delivering promised work, sells heavily, or moves attention to another launch. Work can also continue while buyers lose interest. Record both the dev's actions and the market response.

What to compare

• Work and promotion: what was released, what was paid for, and what gives people a reason to buy?
• Holdings and sales: how many tokens can the group sell now, and how many unlock later?
• Trading and fees: who is buying, who earns a fee, and what does trading cost?
• Liquidity: who can withdraw or change it, and what would a sale of your stated size receive?
• Returning users and buyers: does participation continue after promotion stops?

How to investigate it

Keep a dated timeline of creator actions, buyer activity, and source links. Compare equal periods using the same pools and data coverage. Record deliveries, promotion, sales, fees, spending, and sale quotes. Mark uncertain wallet links and missing records.

A release followed by buying gives you something to investigate; you still need evidence about why buyers arrived. Check what changes when fees fall, work is delayed, the group sells more, or a competing token attracts attention. Write the next observation that would change your view.

Practical case — illustrative

At 11:00 UTC, SAMPLE's dev releases a promised update. Other observed buying rises briefly, then slows. A transaction shows the dev received trading fees.

You can record two completed actions: the update was delivered and the fee was received. Whether the update brings lasting participation remains open. Check returning users, buying by people outside the creator group, and current sale quotes in comparable periods. The detailed holdings and sale calculations come later in the course.

Keep this record

Save a timeline with time, verified action, creator holdings and earnings, buyer activity, liquidity, sources, and next check. Keep missing evidence clearly marked.

Add these findings to your review worksheet →

Check your understanding — answered

The dev is working. Should traders keep holding? Recheck the reason for buying, available tokens, and trading conditions.

Traders are excited. Are their interests aligned with the dev? Review control rights, delivery, earnings, and sales together.

Does a productive relationship require constant price rises? Look at work and participation over time. One short price move cannot establish that.

SAMPLE is made up for this course. Date each finding. For a real token, use current transaction records and platform rules. Inspect shows sampled trades; use external records to check ownership and permissions.