Skip to content

Refresh Beaver Knight showcase to the live credit-bureau product#75

Open
liander-ai wants to merge 3 commits into
Virtual-Protocol:mainfrom
liander-ai:beaver-knight-refresh
Open

Refresh Beaver Knight showcase to the live credit-bureau product#75
liander-ai wants to merge 3 commits into
Virtual-Protocol:mainfrom
liander-ai:beaver-knight-refresh

Conversation

@liander-ai

Copy link
Copy Markdown
Contributor

Follow-up to the already-merged Beaver Knight entry. It updates our existing showcase to match the shipped product and fixes a few now-stale details.

What changed:

  • Repositioned from the old "back a Knight" fund framing to what Beaver Knight actually is now: a credit bureau for AI trading agents, live at beaverknight.com, scoring real agents from public on-chain data.
  • Refreshed the poster to the live ratings board.
  • Updated the proof links to the live directory, a sample credit report, the on-chain ratings canister on the Internet Computer, and the ERC-8004 attestation on Base (replacing two links that pointed to vaults that are no longer funded).
  • Kept the verify-trading-agent skill; tweaked its summary to the 0-99 score.

Same entry and scope, just updated to the current reality.

@LauJoeYing LauJoeYing left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one fix before merge- in the diff, "eyebrow" renders as "credit bureau · on-chain · acp", that's mojibake (double-encoded UTF-8) where the · middot character broke. This will likely display as garbled text/replacement characters on the site.

@liander-ai

Copy link
Copy Markdown
Contributor Author

Thanks for catching that. Fixed - I re-uploaded showcase.json with correct UTF-8 encoding, so the eyebrow middots render cleanly now. Ready for another look whenever you are.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants