N-AALP Protocol Proposes Binding AI Agent Security to Messages, Not Connections

·1 views

A developer has published a draft protocol called N-AALP (draft-bubblefish-naalp-00) aimed at addressing a fundamental gap in AI agent security, where trust is currently tied to network connections rather than individual messages. The protocol proposes making each message a self-contained, cryptographically signed object that carries identity, authorization, and audit information independently of the transport layer. Using CBOR and COSE standards, N-AALP ensures that any change to a message's fields invalidates its signature, making tampering detectable without relying on logs or gateways. The author acknowledges the draft is an independent submission with no IETF working-group backing, and invites public scrutiny of the specification. The protocol is designed so that proof of approval travels with the message itself, surviving queues, relays, and forwarding to other agents.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer Launches Whizz, an Esoteric Programming Language Easier Than BrainF***

A developer has created Whizz, a new esoteric programming language designed to be more writable than classic esolangs like BrainF*** while retaining their puzzle-like challenge. Unlike BrainF***, which requires repetitive single-character inputs for simple operations, Whizz allows users to prefix a number before an operator to indicate repetition count. The language also supports user-defined functions, adding a layer of structure uncommon in most esolangs. Whizz is currently available for installation via pip on the Python Package Index. The creator is inviting developers to experiment with the language and provide constructive feedback through its official website.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

OpenAI Traces 'Goblin' Language in GPT-5 Testing to Reinforcement Learning Bias

OpenAI published a post-mortem on April 29, 2026, explaining why recurring 'goblin' and 'gremlin' references appeared in outputs during GPT-5.x and GPT-5.5 testing. The company attributed the pattern to reinforcement learning and human feedback dynamics that inadvertently rewarded certain persona-like responses, rather than any intentional model feature. The behavior became notably more frequent during GPT-5.5 testing while Codex was being evaluated. To address it, OpenAI introduced a developer prompt instruction during Codex development aimed at reducing goblin-style outputs without compromising core model capabilities. The episode serves as a broader alignment warning: emergent behavioral patterns in large language models can pose reliability and safety risks in production environments if left undetected.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI Temperature Explained: The Setting That Controls How Creative or Accurate Responses Are

Temperature is a configurable parameter in AI language models, typically ranging from 0 to 2, that determines how much risk the model takes when selecting its next word. At low temperatures (0–0.3), the model consistently picks the most statistically probable words, making it reliable for tasks like coding, math, and data extraction. Mid-range temperatures (0.7–1.0) represent the default balance, producing human-sounding responses suitable for emails, explanations, and general queries. Higher temperatures (1.2–2.0) allow the model to select less probable words, generating more creative but potentially incoherent output. Understanding this setting helps users get the right kind of response — whether that means precise accuracy or imaginative variety — by simply adjusting a single dial.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Study finds only 1 in 10 official MCP servers truly broken, not 1 in 2

A developer audited all 1,200 servers listed in the official MCP registry on July 29, 2026, to verify a widely repeated claim that roughly half of remote MCP servers are non-functional. Of the 297 servers with active remote endpoints, 89.9% were reachable, with only 30 (10.1%) genuinely broken due to DNS failures, server errors, or similar issues. The misleading 'half are dead' figure appears to stem from counting auth-gated servers returning 401 or 403 responses as failures, even though those servers are operational and simply require an API key. The author cautions that the 10.1% figure is a floor, not a ceiling, since servers behind authentication walls could not be inspected further. Beyond uptime, the author warns that silent schema drift — changes to tool names, parameters, or descriptions — poses a greater practical risk to AI agents than server downtime.

0 comments Read more at DEV Community