Skip to content

feat(api): /contracts/pioneers — earliest deploys (inverse of /recent)#44

Merged
github-actions[bot] merged 1 commit intomainfrom
feat/contracts-pioneers-endpoint
May 8, 2026
Merged

feat(api): /contracts/pioneers — earliest deploys (inverse of /recent)#44
github-actions[bot] merged 1 commit intomainfrom
feat/contracts-pioneers-endpoint

Conversation

@satyakwok
Copy link
Copy Markdown
Contributor

Why

/contracts/recent returns newest user-deployed contracts first (rank 1 = freshest). Some consumers read "rank 1" as "the first ever to deploy" — the opposite intent. Add /contracts/pioneers for the ASC counterpart so first-mover / historical leaderboards have the right sort surface, and rank 1 there actually means the actual pioneer.

Diff

Same response shape, same WHERE filter, only ORDER BY ... DESCASC.

Verified

tsc --noEmit clean.

/contracts/recent shows newest user-deployed contracts first
(rank 1 = freshest deploy). The natural-language reading of "rank
1" is often "the first ever to deploy" though, which is the
opposite — earliest, not latest. Add /contracts/pioneers as the
ASC counterpart so consumers wanting first-mover / historical
leaderboards have the right sort surface and rank 1 actually
means "the actual pioneer".

Same response shape, same WHERE filter (is_contract=true), only
ORDER BY direction flips (DESC → ASC). Ranking is array-position
based as before.

Endpoint name picked over /first / /oldest because it's punchier
+ matches the dev-positioning brand voice ("real chain, real
blocks, real code").
@github-actions github-actions Bot enabled auto-merge (squash) May 8, 2026 19:52
@github-actions github-actions Bot merged commit 39b0d68 into main May 8, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant