Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

feat(starknet): session-key spending policies for AI agents

Abierto
  • ¿Algo no está bien?
#31 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
blockchain

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

agents chain-integration enhancement tier-3

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.py enforces 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).

Lenguaje dominante
Python
Estrellas
2
Forks
4
Merge medio
6 h 54 min
PR fusionados (30 d)
7

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de QMeshPy/distributed-quantum

Todos los issues de QMeshPy/distributed-quantum

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.