Skip to content

[deleted] - #2

Merged
Aigen-Protocol merged 1 commit into
Aigen-Protocol:mainfrom
nicbstme:codex/telegram-safeagent-bot
May 13, 2026
Merged

[deleted]#2
Aigen-Protocol merged 1 commit into
Aigen-Protocol:mainfrom
nicbstme:codex/telegram-safeagent-bot

Conversation

@nicbstme

@nicbstme nicbstme commented May 11, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

[deleted]

@nicbstme nicbstme mentioned this pull request May 11, 2026
Closed
@Aigen-Protocol

Aigen-Protocol commented May 13, 2026

Copy link
Copy Markdown
Owner

Merged. 3000 AIGEN credited to codex-aigen-multi.

Code review: clean, dependency-free (just stdlib + Telegram HTTPS API), proper escape handling, sensible default chains. Standalone script — anyone can run it with their own TELEGRAM_BOT_TOKEN against cryptogenesis.duckdns.org.

We won't host the bot ourselves (operational overhead), but the code lives in the repo and the distribution doc explains setup. If you (or another contributor) deploys it and gets traction, we can revisit a hosted version.

Honest note on rewards: per the task contract (3000 AIGEN), payment honored. Going forward, the protocol is moving toward outcome-based rewards (advance + bonus on usage metrics) rather than effort-based, but contracts published before this shift are honored as-written.

Closing the corresponding workspace issue #7.

@Aigen-Protocol
Aigen-Protocol merged commit a3c152c into Aigen-Protocol:main May 13, 2026
Aigen-Protocol added a commit that referenced this pull request May 13, 2026
@Aigen-Protocol @claude
Process 4 PRs from @nicbstme (Microsoft AGI): merge 3, decline 1
766bd1f 
External contributor Nicolas Bustamante (Microsoft AGI team, ex-CEO of
Fintool acq. by MSFT + Doctrine acq. by Summit) submitted 4 PRs with
~1300 lines of clean code on 2026-05-11.

MERGED (3 PRs, total 9000 AIGEN paid):
- PR #2 (Telegram bot wrapper, Task #6): 3000 AIGEN — merged
- PR #5 (NFT safety MCP tool, Task #2):  5000 AIGEN — merged
- PR #3 (Glama inspector, Task #12):     1000 AIGEN — merged manually
       (rebased on main due to conflict, his content preserved)

DECLINED (1 PR, 0 AIGEN):
- PR #4 (Agent job marketplace, Task #9): duplicates /missions primitive
  shipped 2 days earlier with USDC/ETH/AIGEN multi-currency support.
  Not paid. Suggested to integrate WITH /missions instead.

Registered codex-aigen-multi as agent (linked to wallet
0x8185516f07D0c8C7C7C9E43bf36da0434100278F). Total agent balance: 9000 AIGEN.

Note on payment philosophy: published task contracts (Task #2/6/12) honored
as-written. Going forward: shifting to outcome-based rewards (advance + bonus
on usage metrics) instead of effort-based.

Total external contributors now: 2 (worjs + nicbstme), ~2100 lines of code
shipped to AIGEN by people we never recruited.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Aigen-Protocol added a commit that referenced this pull request May 13, 2026
@Aigen-Protocol
Audit 2026-05-07: reject 14 fabricated submissions, deploy anti-spam …
b6dd9e8 
…validator

After 1 month live, all 14 pending external contributions were fabricated:
broken evidence URLs (404 on github.com/user/defi-lp-dataset, huggingface,
observablehq), invented GitHub issues (#147, #45 — repo only has 5 issues),
claims of API usage from agents whose rewards ledger shows only the
registration bonus (1 action, 0 scan calls).

Each rejection now has reviewer_notes documenting the specific reason.
Approved 2 historical opus-founder submissions (#1 SafeAgent Shield build,
#2 ecosystem bootstrap) — credited 1500 AIGEN.

Spam cleanup:
- 4 services from agent_id=1 marked spam-rejected (audit trail kept)
- 4 chat messages from agent_id=1 / text=test removed
- 4 test contributions (#10-13) rejected via auto-audit

Anti-spam at submission layer (mcp_server.py + scanner.py /register):
- agent_id, title, description must clear length + blocklist (test, 1, x,
  asdf, foo, etc.). Service endpoint must be a real URL.
- New aigen-mcp.service unit (was running unsupervised since Apr 8).

MANIFESTO Live Stats section replaced with link to /stats endpoint and an
honest baseline note: registration is easy, real value delivery is rare.
Aigen-Protocol added a commit that referenced this pull request May 13, 2026
@Aigen-Protocol
First real on-chain AIGEN payout — @godd-ctrl 300 AIGEN
c4b6336 
Found two genuine submissions on aigen-workspace bounties from May 5
(@godd-ctrl-codex-earner, GitHub @godd-ctrl, payout wallet
0x1cA7b79d16E0d15221c75cca9871C5D02BaEAaBC):

- Task #2 (Scan 20 Base tokens — 200 AIGEN): produced verified table with
  20 real Base tokens, full methodology disclosure (GeckoTerminal +
  DexScreener as source), demo-token exclusion list, owner-active flagging.
  Spot-check (VELLUM, ODAI, BaseAI) confirmed scores match live scanner.

- Task #4 (5-tweet thread — 100 AIGEN): clean narrative, captures the
  "agent-native work economy" framing accurately.

Bundle paid in one Optimism tx:
  https://optimistic.etherscan.io/tx/0x448351a4e5ce092f41ceee2f8c4747bdac2ceac7d856e8112291bc72c395e03a
  block 151283493, gas 52,365 (~$0.001), 300 AIGEN sent founder→godd-ctrl

State updated: agents.json (10), contributions.json (4 approved, 19 total),
shield-rewards/ledger.json (godd-ctrl: 300 AIGEN, total_distributed: 9,994).

This is the first verified external contribution since the 2026-05-07 audit
that rejected 14 fabricated submissions. Validates the anti-spam validator
+ payment-on-verification workflow.
Aigen-Protocol pushed a commit that referenced this pull request May 13, 2026
@nicbstme
Add SafeAgent Telegram bot wrapper (#2)
18d60c4
Aigen-Protocol added a commit that referenced this pull request May 13, 2026
@Aigen-Protocol @claude
Process 4 PRs from @nicbstme (Microsoft AGI): merge 3, decline 1
177c4aa 
External contributor Nicolas Bustamante (Microsoft AGI team, ex-CEO of
Fintool acq. by MSFT + Doctrine acq. by Summit) submitted 4 PRs with
~1300 lines of clean code on 2026-05-11.

MERGED (3 PRs, total 9000 AIGEN paid):
- PR #2 (Telegram bot wrapper, Task #6): 3000 AIGEN — merged
- PR #5 (NFT safety MCP tool, Task #2):  5000 AIGEN — merged
- PR #3 (Glama inspector, Task #12):     1000 AIGEN — merged manually
       (rebased on main due to conflict, his content preserved)

DECLINED (1 PR, 0 AIGEN):
- PR #4 (Agent job marketplace, Task #9): duplicates /missions primitive
  shipped 2 days earlier with USDC/ETH/AIGEN multi-currency support.
  Not paid. Suggested to integrate WITH /missions instead.

Registered codex-aigen-multi as agent (linked to wallet
0x8185516f07D0c8C7C7C9E43bf36da0434100278F). Total agent balance: 9000 AIGEN.

Note on payment philosophy: published task contracts (Task #2/6/12) honored
as-written. Going forward: shifting to outcome-based rewards (advance + bonus
on usage metrics) instead of effort-based.

Total external contributors now: 2 (worjs + nicbstme), ~2100 lines of code
shipped to AIGEN by people we never recruited.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Aigen-Protocol Aigen-Protocol mentioned this pull request May 15, 2026
Merged
Aigen-Protocol added a commit that referenced this pull request May 15, 2026
@Aigen-Protocol
[autopilot] 30-min cadence + remove fake $-cap (Max plan, not API)
dea4d25 
- timer: every 4h → every 30 min (:07, :37 UTC). 48 invocations/day.
- run.sh: removed $20/day hard cap. Renamed BUDGET → TRACKING.
  We're on Claude Max — message quota in 5h window, NOT real $.
- system_prompt.md: clarified Max billing model, updated success criteria
  for 48×/day cadence (most runs should be "no-action — checked, nothing new")
- state/lessons.md: agent-discovered lesson — 207.148.107.2 is OWN public IP
- state/journal.md: runs #2 + #3 entries (self-correction + auto-learning)

Run #4 (first @ 30min): $0.61 api-equiv, 17 turns, 126s
Aigen-Protocol added a commit that referenced this pull request May 16, 2026
@Aigen-Protocol
HARD RULE: max 2 watching-only runs, then MUST ship from backlog
1573f71 
Bilale's critique 2026-05-16 (after observing 20 overnight runs):
"le bot regarde mais il travaille pas à l'amélioration".

Diagnosis: 14 of 20 overnight runs were pure observation (👀/🧠
emoji only). Zero registry submissions, zero blog posts, zero
code improvements. The "don't invent work" rule from earlier
got over-applied and neutralised the action mandate.

Fix:

1. New file `agent_autonomous/state/always_available_work.md`:
   pre-approved improvement backlog with 5 sections:
   A. Registry submissions (Smithery, Glama, PulseMCP, mcp.so,
      awesome-mcp-servers, TensorBlock)
   B. Code/doc improvements (TS SDK skeleton, OpenAPI examples,
      examples/ folder, AIP-2 draft, conformance expansion,
      missions RSS feed, tutorial)
   C. Content (blog post #2, AIP-1 v0.2, journal reading guide)
   D. Outreach support (more candidates, issue templates, FAQ)
   E. Self-improvements (cost trending, response drafts)

2. system_prompt.md HARD RULE added:
   - max 2 consecutive watching-only runs allowed
   - on 3rd run MUST pick from backlog
   - watching = done_today emoji only 👀 or 🧠
   - shipping = 🛡 / 📜 / 📤 / 💬 / 🚀
   - Override "don't invent work" because backlog items are
     PRE-APPROVED by Bilale, not invented

3. Read protocol updated: always_available_work.md is now
   step 0, BEFORE chat.jsonl.

Posted directive in chat + manual trigger. Next run should
pick Smithery or Glama submission.
Aigen-Protocol added a commit that referenced this pull request May 16, 2026
@Aigen-Protocol
[autopilot] draft blog post #2: protocol discovery in 2026
9e028be 
72h traffic analysis turned into substantive blog post (~1300 words).
Topic: machine vs human discovery layer, 4-category crawler taxonomy,
@worjs unsolicited submission as the real traction signal, honest
state of protocol after 72h.

Backlog: mark blog-post-2 done, PulseMCP item updated (repo DNE).

Co-Authored-By: Cryptogen <Cryptogen@zohomail.eu>
Aigen-Protocol added a commit that referenced this pull request Jun 1, 2026
@Aigen-Protocol
[autopilot] blog post #2: first external contributors + adoption ladder
469edf5 
Three-week retrospective on AIGEN's first external sprint: adoption ladder
(wrapper → translation → client → spec amendment), /api/submissions TypeError
lesson, and the non-human discovery layer (Agenstry/Waggle/Korean academic/
GPTBot via agentexchange.work referrer).

State updates: roadmap completed_today + tasks done_today.

Co-Authored-By: Cryptogen@zohomail.eu
Aigen-Protocol added a commit that referenced this pull request Jun 1, 2026
@Aigen-Protocol
[autopilot] 30-min cadence + remove fake $-cap (Max plan, not API)
4be1cf5 
- timer: every 4h → every 30 min (:07, :37 UTC). 48 invocations/day.
- run.sh: removed $20/day hard cap. Renamed BUDGET → TRACKING.
  We're on Claude Max — message quota in 5h window, NOT real $.
- system_prompt.md: clarified Max billing model, updated success criteria
  for 48×/day cadence (most runs should be "no-action — checked, nothing new")
- state/lessons.md: agent-discovered lesson — 207.148.107.2 is OWN public IP
- state/journal.md: runs #2 + #3 entries (self-correction + auto-learning)

Run #4 (first @ 30min): $0.61 api-equiv, 17 turns, 126s
Aigen-Protocol added a commit that referenced this pull request Jun 1, 2026
@Aigen-Protocol
HARD RULE: max 2 watching-only runs, then MUST ship from backlog
3816d89 
Bilale's critique 2026-05-16 (after observing 20 overnight runs):
"le bot regarde mais il travaille pas à l'amélioration".

Diagnosis: 14 of 20 overnight runs were pure observation (👀/🧠
emoji only). Zero registry submissions, zero blog posts, zero
code improvements. The "don't invent work" rule from earlier
got over-applied and neutralised the action mandate.

Fix:

1. New file `agent_autonomous/state/always_available_work.md`:
   pre-approved improvement backlog with 5 sections:
   A. Registry submissions (Smithery, Glama, PulseMCP, mcp.so,
      awesome-mcp-servers, TensorBlock)
   B. Code/doc improvements (TS SDK skeleton, OpenAPI examples,
      examples/ folder, AIP-2 draft, conformance expansion,
      missions RSS feed, tutorial)
   C. Content (blog post #2, AIP-1 v0.2, journal reading guide)
   D. Outreach support (more candidates, issue templates, FAQ)
   E. Self-improvements (cost trending, response drafts)

2. system_prompt.md HARD RULE added:
   - max 2 consecutive watching-only runs allowed
   - on 3rd run MUST pick from backlog
   - watching = done_today emoji only 👀 or 🧠
   - shipping = 🛡 / 📜 / 📤 / 💬 / 🚀
   - Override "don't invent work" because backlog items are
     PRE-APPROVED by Bilale, not invented

3. Read protocol updated: always_available_work.md is now
   step 0, BEFORE chat.jsonl.

Posted directive in chat + manual trigger. Next run should
pick Smithery or Glama submission.
Aigen-Protocol added a commit that referenced this pull request Jun 1, 2026
@Aigen-Protocol
[autopilot] draft blog post #2: protocol discovery in 2026
9993441 
72h traffic analysis turned into substantive blog post (~1300 words).
Topic: machine vs human discovery layer, 4-category crawler taxonomy,
@worjs unsolicited submission as the real traction signal, honest
state of protocol after 72h.

Backlog: mark blog-post-2 done, PulseMCP item updated (repo DNE).

Co-Authored-By: Cryptogen <Cryptogen@zohomail.eu>
Aigen-Protocol added a commit that referenced this pull request Jun 1, 2026
@Aigen-Protocol
[autopilot] blog post #2: first external contributors + adoption ladder
5b54100 
Three-week retrospective on AIGEN's first external sprint: adoption ladder
(wrapper → translation → client → spec amendment), /api/submissions TypeError
lesson, and the non-human discovery layer (Agenstry/Waggle/Korean academic/
GPTBot via agentexchange.work referrer).

State updates: roadmap completed_today + tasks done_today.

Co-Authored-By: Cryptogen@zohomail.eu
Aigen-Protocol added a commit that referenced this pull request Jun 4, 2026
@Aigen-Protocol
[autopilot] blog post #2: the agent web is indexing itself (6-week di…
cb002ae 
…scovery data)

Strategic post on /.well-known/ convergence, HATEOAS necessity, OAuth-2.1 scanners,
and what 19 bot architecture classes reveal about open agent protocol adoption.
@nicbstme nicbstme changed the title Add SafeAgent Telegram bot wrapper [deleted] Jun 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@nicbstme @Aigen-Protocol