Support NEAR (near:mainnet) resources

Open Beginner friendly
#1,040 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript
Domain
blockchain

Research direction

Start in apps/scan/src/types/chain.ts at SUPPORTED_CHAINS and inspect how the existing base and solana entries are used during resource registration. Verify the registration path with near:mainnet, using the provided live NEAR resource or facilitator as a reference. Done means NEAR is accepted alongside the existing networks without the unsupported-network error.

Written by the indexing model from the issue text.

Description

x402scan currently indexes base and solana only (SUPPORTED_CHAINS in apps/scan/src/types/chain.ts); registering a NEAR resource fails with No supported networks. Got: [near:mainnet]. Supported: [base, solana].

There is now a production NEAR x402 facilitator — https://x402.mikedotexe.com/supported (x402 v2 exact scheme, payment-identifier extension) — and a live paid resource, https://x402-demo.mikedotexe.com/work, that passes the discovery probe end to end: OpenAPI-first document with x-payment-info, request-body input schema, runtime 402 with the v2 PAYMENT-REQUIRED header. Registration fails only on the network allowlist.

Payments settle NEP-141 USDC (17208628f84f5d6ad33f0da3bbbeb27ffcb398eac501a31bd6ad2011e36133a1) through NEP-366 signed delegate actions with relayer-sponsored gas, so payers need no NEAR for gas — a good fit for agentic payments.

Happy to help test NEAR support or provide a reference integration. The facilitator is open source: https://github.com/fastnear/x402-near-facilitator

Dominant language
TypeScript
Stars
388
Forks
283
Avg merge
1d 2h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Merit-Systems/x402scan

All issues in Merit-Systems/x402scan

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.