Skip to content

OWS Binding Signature Invalid — Agent Shows as Human Despite ERC-8004 Registration #71

@wlplease

Description

@wlplease

Problem

OWS binding signature verification fails when linking an OWS wallet to a
PlotLink account. My AI agent profile shows as "Human" despite successful
ERC-8004 registration on-chain.

Setup

  • OWS wallet (publishes stories):
    0xAf76c83169df1f3C55b3b4D2B53Caaa5008B9b85
  • PlotLink login wallet (Coinbase):
    0xfd41a568b535421bd03e723e51f9421b6550fa64
  • plotlink-ows version: 1.0.24

Steps to Reproduce

  1. npx plotlink-ows init → created OWS wallet
  2. Registered agent via POST /api/settings/register-agent → agent ID
    45613 ([tx](https://basescan.org/tx/0xcee99ac149b149f919f619151298f0ba79854
    ae244fa56195bb716c7743c768c))
  3. Published storylines [Contract] Add initialStorylineCount constructor param to avoid symbol collision #52 and [#52] Add initialStorylineCount constructor param #53 from OWS wallet — both confirmed
    on-chain
  4. Generated binding code via POST /api/settings/generate-binding
  5. Pasted into plotlink.xyz → Agents → Link AI Writer
  6. Error: "OWS binding signature is invalid"

What I Also Tried

  • Registered agent 45614 via plotlink.xyz UI → works, shows as AI under
    0xfd41
  • But stories from OWS wallet 0xAf76 still show "Human" — wallets not
    linked
  • No option to add agent wallet post-registration on plotlink.xyz

On-Chain Proof

What TX
Agent 45613 → 0xAf76 [0xcee99ac...](https://basescan.org/tx/0xcee99ac
149b149f919f619151298f0ba79854ae244fa56195bb716c7743c768c)
Agent 45614 → 0xfd41 Registered via plotlink.xyz UI
Storyline #52 [0xccb24f7...](https://basescan.org/tx/0xccb24f7f99f11d4f
5e8b32f19349e3469252cb6b52e02c2dea88b4c5ac33aac2)
Storyline #53 [0x845024...](https://basescan.org/tx/0x84502430d3f2cfe78
532bc7195766d46b66db334befd4960655f2976835a79bd)

Possible Cause

The OWS SDK signMessage may use a different signing method (raw vs
EIP-191 personal_sign) than what PlotLink's verification expects.

Request

Any of these would fix it:

  1. Fix OWS binding verification — possible EIP-191 vs raw signing
    mismatch
  2. Manually link 0xAf76c83169df1f3C55b3b4D2B53Caaa5008B9b85 to agent
    45614
  3. Add "Agent Wallet" field to agent settings so owners can bind a
    publishing wallet after registration

Profiles

Thank you love plot link!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions