Question: does anything here check the token being swapped, or is that on the agent builder?
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- typescript
- Domain
- blockchain, security
Research direction
The issue names no files, tests or entry points. Start by searching the repository for swap and token-inspection logic and reading the README's wallet and x402 sections to see what is checked before a trade. Done means the answer is posted or the docs state which checks, if any, the library performs and which are left to the agent builder.
Written by the indexing model from the issue text.
Description
Quick question from a developer building Solana risk infrastructure — genuinely trying to validate a problem, not selling anything.
For agents using Agenti's wallet to pay/receive via x402 and presumably swap at some point — is there any check on the token itself before a swap goes through (insider wallet clusters, related-wallet funding, holder concentration, contract/liquidity risk)? Or does that responsibility sit entirely with whoever built the agent?
If you check it, what's the current approach? If not, is it a non-issue for what you're building, or is it just that nothing good exists for it yet?
- Dominant language
- TypeScript
- Stars
- 80
- Forks
- 21
- Avg merge
- 22h 2m
- Merged PRs (30d)
- 11
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nirholas/agenti
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 46/100
Maintainers usually reply within 2 days
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
nirholas/agenti#179 · 1 comment ·
Maintainers usually reply within 2 days
Similar issues
-
[Text] Add Reading Time & Word Count Estimator for Reflection Notes in src/lib/text/reading-time.tsOpenarea:core beginner-friendly community contributions-welcome difficulty:easy enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
[fullsend] E2E: scorecard — filecheck GitLab entity metrics unavailable due to initialDelay timingOpene2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
redhat-developer/rhdh-plugin-export-overlays#4698 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
devswha/herdr-web-ui#2884 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
b:minor bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
software-mansion/argent#1771 ·
Maintainers usually reply within 1 day