v2.0.0 — Full rewrite for npm publishing under @aigen-protocol scope#1
Open
Aigen-Protocol wants to merge 2 commits intomainfrom
Open
v2.0.0 — Full rewrite for npm publishing under @aigen-protocol scope#1Aigen-Protocol wants to merge 2 commits intomainfrom
Aigen-Protocol wants to merge 2 commits intomainfrom
Conversation
Renamed scope to @aigen-protocol/plugin-safeagent (we control this scope;
@elizaos/* is the upstream's). Built dist/ for npm publish.
Actions (4):
- SHIELD — pre-trade safety check via HTTP /scan + /honeypot
- WATCH_WALLET — register wallet for HMAC-signed webhook alerts
- SAFE_CHECK — view-only on-chain SafeRouter.checkBeforeBuy (Base)
- SAFE_SWAP_CALLDATA — build calldata for SafeRouter.safeSwap (custody-safe)
Build: tsc → dist/{index.js,index.d.ts,index.js.map,index.d.ts.map}
Verified end-to-end: SHIELD returned correct 100/100 SYSTEM TOKEN for USDC
on Base via fetch. Plugin loads cleanly, all 4 actions registered.
Per @lalalune (eliza issues #6706, #6707, #6708): plugin proposals must
be developed in own repo + published to npm. This is that publication.
To publish (requires npm account + login):
npm login
npm publish # access:public configured
Once published:
npm install @aigen-protocol/plugin-safeagent
Aigen-Protocol
pushed a commit
to Aigen-Protocol/aigen-protocol
that referenced
this pull request
May 7, 2026
- SafeRouter V2 deployed on Optimism (0x38be6AA1044e866FcDFE34d4B4273F703668B80E, block 151287236, tx 0x1df8010ade30a2d622af9f6e1248619dd8cfb6b5af9447986981b8639fce5f6c) wrapping Velodrome V2. Same code as Base V2, atomic safety guarantee, same custom-error revert path. Cost $0.005 from OP-ETH balance. - ElizaOS plugin install line: `npm install @aigen-protocol/plugin-safeagent` (PR Aigen-Protocol/plugin-safeagent#1, awaiting npm publish) - New ERC submitted to ethereum/ERCs#1729 (Token Safety Score, Standards Track, category ERC). Reference implementations are our deployed oracles + SafeRouter. Replaces our withdrawn 7913-update PR (we incorrectly targeted OZ Signature Verifiers; this is a new unassigned-number proposal). - Multi-chain table at top, on-chain proof tx hashes inline.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the plugin for npm publish. Per elizaOS maintainer @lalalune, plugins must be developed in own repo + published to npm — this is that publication-ready state.
Changes
@elizaos/plugin-safeagent(not ours) →@aigen-protocol/plugin-safeagent(ours)SHIELD,WATCH_WALLET,SAFE_CHECK,SAFE_SWAP_CALLDATAdist/artifacts via tsc)Verified
tscclean (no errors)require('./dist/index.js').default— plugin namesafeagent-aigen, 4 actions registeredPublish (requires owner npm login):
npm login npm publish # configured for access:public