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
npx plotlink-ows init → created OWS wallet
Registered agent via POST /api/settings/register-agent → agent ID
45613 ([tx](https://basescan.org/tx/0xcee99ac149b149f919f619151298f0ba79854
ae244fa56195bb716c7743c768c))
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
Generated binding code via POST /api/settings/generate-binding
Pasted into plotlink.xyz → Agents → Link AI Writer
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
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:
Fix OWS binding verification — possible EIP-191 vs raw signing
mismatch
Manually link 0xAf76c83169df1f3C55b3b4D2B53Caaa5008B9b85 to agent
45614
Add "Agent Wallet" field to agent settings so owners can bind a
publishing wallet after registration
Profiles
Thank you love plot link!
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
0xAf76c83169df1f3C55b3b4D2B53Caaa5008B9b850xfd41a568b535421bd03e723e51f9421b6550fa64Steps to Reproduce
npx plotlink-ows init→ created OWS walletPOST /api/settings/register-agent→ agent ID45613 ([tx](https://basescan.org/tx/0xcee99ac149b149f919f619151298f0ba79854
ae244fa56195bb716c7743c768c))
on-chain
POST /api/settings/generate-bindingWhat I Also Tried
0xfd410xAf76still show "Human" — wallets notlinked
On-Chain Proof
0xAf760xfd41Possible Cause
The OWS SDK
signMessagemay use a different signing method (raw vsEIP-191 personal_sign) than what PlotLink's verification expects.
Request
Any of these would fix it:
mismatch
0xAf76c83169df1f3C55b3b4D2B53Caaa5008B9b85to agent45614
publishing wallet after registration
Profiles
https://plotlink.xyz/profile/0xAf76c83169df1f3C55b3b4D2B53Caaa5008B9b85
https://plotlink.xyz/profile/0xfd41a568b535421bd03e723e51f9421b6550fa64
Thank you love plot link!