Skip to content

Latest commit

 

History

History
42 lines (27 loc) · 1.37 KB

File metadata and controls

42 lines (27 loc) · 1.37 KB

HashPay x ARC Names Send Page

Small pitch prototype for creating HashPay payment requests with .arc names instead of raw hex addresses.

This version does not use mock recipient records. It resolves names through real ARC Name Service infrastructure, then generates a HashPay checkout URL using HashPay's existing URL parameter surface.

Demo Flow

  1. Open index.html in a browser.
  2. Start the ANS API from the repo root if you want the REST path:
npm run dev:api

The page also attempts a direct Arc Testnet eth_call fallback against the ANS registry if the REST API is unavailable.

  1. Enter a registered .arc recipient. bob256.arc is registered in the current Arc Testnet deployment and resolves to the repo treasury wallet.
  2. Enter an amount and optional memo.
  3. Generate the request link.

The lookup uses:

GET /resolve/:name

or direct Arc RPC:

eth_call -> ARCNameRegistry.resolve(string)

The generated HashPay URL uses the parameter names observed in the HashPay bundle:

https://hashpaylink.com/pay?n=arc&e=<resolved-wallet>&a=<amount>&m=<memo>&arcName=<name>&source=arc-names

Pitch Point

HashPay keeps its payment-link, QR, checkout, and dashboard strengths. ARC Names adds a human-readable trust layer so merchants and agents can request payment by name first, with the resolved wallet shown before checkout.