feat(starknet): session-key spending policies for AI agents
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python
- 领域
- blockchain
调研方向
Start by reading issue #2 and the agent configuration and funding paths named here: ai_agent_service._execute_funding and agent/cost_guard.py. Verify the current session-key standard, maintained Python client API, and testnet paymaster availability before choosing an account implementation. Done means policy limits are enforced on-chain, session keys can be revoked and expire, and policy parameters map to existing agent config fields, with tests and documentation.
由索引模型根据 Issue 内容生成。
描述
Summary
Enforce AI agent spending limits in a Starknet smart account via session keys, so caps hold even if the backend is compromised, and offer gasless onboarding through a paymaster.
Motivation
Agent budgets (max_per_proposal, daily_budget) are enforced only in application code. On-chain policy is a stronger guarantee and a good showcase of account abstraction.
Current state in this repo
- Limits live in agent config documents and
ai_agent_service._execute_funding;agent/cost_guard.pyenforces a separate set of budgets for the workspace agent.
Proposal
- Register Starknet testnet in the registry (#2) with a minimal adapter.
- Select an account implementation supporting session keys and define a policy (allowed targets/tokens, per-call and per-day limits, expiry).
- Create the session key for an agent and use it for agent-initiated funding calls; revoke on demand from the UI.
- Optionally sponsor fees with a paymaster for new users.
- Document the toolchain (Cairo, Python client) and its cost for contributors.
Acceptance criteria
- An agent can transact within policy and is rejected on-chain beyond it.
- Session keys can be revoked and expire automatically.
- Policy parameters map to the existing agent config fields.
Out of scope
- Proving the quantum simulation with STARKs (research-grade).
- Mainnet.
Technical notes and risks
- Session-key standards are still a draft and wallet implementations are not mutually compatible. Pick one implementation and document the lock-in.
Dependencies
- #2
Verify before implementing
- Current session-key standard status and the maintained Python client API.
- Paymaster availability on testnet.
Part of ##1. Ground rules for all issues in this roadmap are listed there (testnet-first, no secrets in the repo, chain logic behind the registry, tests and docs with every PR).
- 主要语言
- Python
- 星标
- 2
- 派生
- 4
- 平均合并
- 6 小时 54 分钟
- 30 天内合并 PR
- 7
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
QMeshPy/distributed-quantum 的其他 Issue
-
enhancement good first issue helia storage tier-1
难度 2/5 1-3 小时 新手友好度 78/100
QMeshPy/distributed-quantum#53 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 4/5 3-5 天 新手友好度 55/100
QMeshPy/distributed-quantum#78 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 3/5 1-2 天 新手友好度 66/100
QMeshPy/distributed-quantum#77 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments tier-2
难度 5/5 一周以上 新手友好度 35/100
QMeshPy/distributed-quantum#76 ·
维护者通常 1 天内回复
-
documentation good first issue kubo storage tier-1
难度 2/5 1-3 小时 新手友好度 42/100
QMeshPy/distributed-quantum#75 ·
维护者通常 1 天内回复
查看 QMeshPy/distributed-quantum 的全部 Issue
相似的 Issue
-
Validate non-divisible effective batch sizes in the Unsloth LoRA backend可能已有人在做 @debesh-biswas 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
-
`rx.Model` event arguments emit `PydanticDeprecatedSince20` once per payload key可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100
reflex-dev/reflex#7634 · 1 条评论 ·
维护者通常 2 天内回复
-
documentation
难度 1/5 1-3 小时 新手友好度 82/100
topoteretes/cognee#6239 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
ranaroussi/yfinance#3009 ·
维护者通常 1 天内回复
-
Test discovery aborts on GPU builds without cuStateVec: check_cuStateVec expects a failed result but set_config() now raises RuntimeError可能已有人在做 @dmeliksetian 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 84/100
Qiskit/qiskit-aer#2495 ·
维护者通常 1 天内回复