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

research(near): NEAR Intents universal deposit and TEE-held agent keys

Abierto
  • ¿Algo no está bien?
#30 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, blockchain, security

Línea de trabajo

Start by reading the official NEAR Intents and agent-key documentation, then verify current docs, testnet availability, and any x402 relationship. The issue names no repository implementation files or tests; prototype a testnet deposit tied to dependency #3 and a TEE-held agent key, or document blockers. Done means a committed decision record under docs/ with security analysis and a reproducible prototype or documented blocker.

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

Descripción

chain-integration enhancement payments research-spike tier-3

Summary

Evaluate NEAR Intents as a universal deposit mechanism (pay with an asset on any supported chain, receive USDC credit) and NEAR's TEE-based agent key model as a replacement for platform-custodial agent wallets.

Motivation

Universal deposits reduce rails to maintain, and TEE-held keys address the stated custody weakness of platform-managed wallets.

Current state in this repo

  • Agent wallets are platform-managed (AgentKit), documented as a deliberate MVP trade-off in docs/superpowers/AGENTKIT_CONTEXT.md in the documentation repo.

Proposal

  • Read the official NEAR Intents and agent-key documentation and capture supported assets/chains.
  • Prototype a testnet deposit that credits the ledger (#3), and a prototype agent key held in a TEE.
  • Decision record on adopt/defer with security analysis.

Acceptance criteria

  • Decision record committed under docs/.
  • A reproducible prototype or a documented blocker.

Out of scope

  • Production use.

Dependencies

  • #3

Verify before implementing

  • Everything: current docs, testnet availability and any x402 relationship were not confirmed during initial research.

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 14 min
PR fusionados (30 d)
18

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.