Issue on docs
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 74/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- javascript
调研方向
从 /apps/builder-codes/builder-codes 开始,并获取 https://docs.base.org/llms.txt,以定位相关的文档结构和相邻页面。添加提供的“Accept B20 payments”指南,包括其中的 JavaScript 示例和相关链接,然后验证页面能够正确渲染,并且其链接和代码示例保持完整。
由索引模型根据 Issue 内容生成。
描述
Path: /apps/builder-codes/builder-codes> ## Documentation Index
Fetch the complete documentation index at: https://docs.base.org/llms.txt
Use this file to discover all available pages before exploring further.
Accept B20 payments
Accept B20 token payments in your app and match each transaction to an order with onchain memos.
B20 is an ERC-20 superset. Standard transfer, transferFrom, approve, balanceOf, and ERC-2612 permit all work, so an app that accepts ERC-20 tokens accepts B20 with no code changes.
B20's new features include transfer policies, pausing, supply caps, and memos. This guide uses the memo: transferWithMemo works like transfer, but also attaches a bytes32 reference such as an order ID and emits a Memo event immediately after the standard Transfer event. Your app can read that Memo event to tie each payment to an order.
Tag a payment with a memo
This example reads the token's decimals, sends a payment tagged with an order ID, then reads the memo back from the receipt. It uses your configured viem walletClient and publicClient:
import { parseUnits, stringToHex, hexToString, parseEventLogs } from 'viem';
const TOKEN = '0xB200...'; // the B20 token you accept
const MERCHANT = '0x...'; // where payments land
const ABI = [
{ type: 'function', name: 'decimals', stateMutability: 'view', inputs: [], outputs: [{ type: 'uint8' }] },
{ type: 'function', name: 'transferWithMemo', stateMutability: 'nonpayable',
inputs: [{ name: 'to', type: 'address' }, { name: 'amount', type: 'uint256' }, { name: 'memo', type: 'bytes32' }],
outputs: [{ type: 'bool' }] },
{ type: 'event', name: 'Memo', inputs: [
{ name: 'caller', type: 'address', indexed: true },
{ name: 'memo', type: 'bytes32', indexed: true },
] },
];
// Read decimals because B20 tokens range from 6 to 18.
const decimals = await publicClient.readContract({ address: TOKEN, abi: ABI, functionName: 'decimals' });
// Pay 10 tokens, tagging the transfer with an order ID.
const hash = await walletClient.writeContract({
address: TOKEN, abi: ABI, functionName: 'transferWithMemo',
args: [MERCHANT, parseUnits('10', decimals), stringToHex('order-42', { size: 32 })],
});
// The Memo event carries the order ID back. Read it from the receipt.
const receipt = await publicClient.waitForTransactionReceipt({ hash });
const [memo] = parseEventLogs({ abi: ABI, logs: receipt.logs, eventName: 'Memo' });
console.log(hexToString(memo.args.memo, { size: 32 }).replace(/\0+$/, '')); // "order-42"
To collect with an allowance instead of a direct transfer, use transferFromWithMemo. It emits the same Memo event.
Handle B20-specific reverts
A B20 transfer can revert where a standard ERC-20 would not. Surface these so a failed payment is visible, not silent:
PolicyForbids: the sender or recipient is not authorized by the token's transfer policy. Most tokens are open by default, but a regulated issuer can gate transfers with an allowlist or blocklist.- A paused transfer: the issuer paused the token's
TRANSFERfeature.
Call publicClient.simulateContract with the same arguments before sending. It raises these as typed errors before the user signs, so you can show the reason instead of a failed transaction.
Related pages
- B20 token standard: the full interface, including memos, policies, pausing, and roles.
- Query B20 events: index
TransferandMemoevents with the CDP SQL API to reconcile payments against orders at scale. - Launch a B20 Token: create your own B20 token.
- 主要语言
- JavaScript
- 星标
- 342
- 派生
- 823
- 平均合并
- 1 天 5 小时
- 30 天内合并 PR
- 59
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
base/docs 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
Issue on docs未关闭
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 92/100
维护者通常 1 天内回复
-
Broken redirect: /wallet-app/:slug* catch-all leads to 404可能已有人在做 @forumevi 于 22 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 92/100
维护者通常 1 天内回复
-
docs(builder-codes): base.dev links use HTTP instead of HTTPS可能已有人在做 @xam-dev-ux 于 42 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 95/100
维护者通常 1 天内回复
相似的 Issue
-
Access-request approve silently discards the decider's note (decision_note written only on deny)未关闭bug
难度 2/5 1-3 小时 新手友好度 72/100
Uuriko/project-room#3378 ·
维护者通常 1 天内回复
-
Notifications pagination accepts NaN and negative LIMIT/OFFSET可能已有人在做 @Senthil455 今天认领。 未关闭BUGS MEDIUM
难度 2/5 1-3 小时 新手友好度 62/100
elixpo/blogs.elixpo#419 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 65/100
immich-app/immich#32426 ·
维护者通常 1 天内回复