Agent registration management
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- go
- Domain
- backend-api-design, blockchain, cli, networking
Research direction
Start by locating the CLI and internal and external agent registration paths, then review how the current tunnel and 8004 metadata calls are represented. Clarify the required set-metadata behavior, tunnel-change trigger, and gas reporting before implementation. Done means registration matches the current tunnel and metadata updates are observable with gas estimates or usage.
Written by the indexing model from the issue text.
Description
Problem to be solved
Our trycloudflare links are still pretty impermanent, websites, skills, etc go out of date (often for relying on latest tags too, different issue).
Proposed solution
Have the cli (and internal and external agents) manage the updating of agent registration to match the current tunnel with a set metadata call. Log approximately how much gas will be consumed / was consumed in u.Dim(). trigger this clean up if we detect a tunnel change? service rich metadata on the domain?
Out of scope
(but worth discussing)
what if we do a --publish equivalent to our launchpad, and give them a more persistent place for discovery (and maybe tunnelling?). something like pet-name.agent.obol.tech (or .dev or something), and allow them to CRUD metadata there? (imo it depends on how good decentralised finding services through 8004 is, could we watch for registrations? would that restrict us to eth funders only? whereas if they call us directly they don't need to go on chain to display them.
- Dominant language
- Go
- Stars
- 11
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 ObolNetwork/obol-stack
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ObolNetwork/obol-stack#612 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
ObolNetwork/obol-stack#829 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 72/100
ObolNetwork/obol-stack#828 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
ObolNetwork/obol-stack#821 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
ObolNetwork/obol-stack#807 · 1 comment ·
All issues in ObolNetwork/obol-stack
Similar issues
-
bug github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1393 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
JakeChampion/lang#10213 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
oasisprotocol/oasis-sdk#2523 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100