fix: aggregate ERC-8004 registration services

[bussyjd]

Summary

• aggregate ERC-8004 registration across registration-enabled ServiceOffers into one shared agent document
• fan the shared registration status back out to all participating offers instead of marking non-owners as SingletonConflict
• hand the singleton registration request off cleanly when the current owner offer disappears, and refresh the shared document whenever offer state changes
• add controller/render tests covering aggregated services, shared registration status, and the final published registration payload

Context

Fixes#361.

ERC-8004 expects a single agentURI / /.well-known/agent-registration.json document with a services array. The previous controller behavior treated the path as singleton but still rendered the document from exactly one offer, which broke multi-service agents and demo flows.

Before / After

Old behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B{"Which offer owns /.well-known/agent-registration.json?"}
B -->|Oldest offer| C["Publish registration doc from one ServiceOffer only"]
B -->|All later offers| D["Registered=False\nSingletonConflict"]
C --> E["Only owner gets Registered=True"]
E --> F["Only owner can contribute to Ready-dependent discovery surfaces"]

Loading

New behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B["Select canonical registration owner"]
B --> C["Build one shared ERC-8004 document"]
C --> D["Append all eligible offer endpoints into services[]"]
D --> E["Publish shared /.well-known/agent-registration.json"]
E --> F["Propagate shared agentId / txHash / registration status to all participating offers"]

Loading

Owner Handoff

sequenceDiagram
participant OfferA as "Owner Offer"
participant Ctrl as "serviceoffer-controller"
participant Req as "Shared RegistrationRequest"
participant OfferB as "Next Eligible Offer"
OfferA->>Ctrl: deleted or disabled
Ctrl->>Req: stop using old owner identity
Ctrl->>OfferB: enqueue reconcile
Ctrl->>Req: recreate or refresh under new owner
Req->>Ctrl: shared status updated
Ctrl->>OfferB: set Registered=True via shared agent doc

Loading

Concrete Examples

Before

Two offers:

• demo/review-hello
• demo/review-blocks

Observed result:

• review-hello gets Registered=True
• review-blocks gets Registered=False with SingletonConflict
• shared registration document contains only the review-hello endpoint

Representative status on the later offer:

conditions:
- type: Registeredstatus: "False"reason: SingletonConflictmessage: Registration path /.well-known/agent-registration.json is reserved by demo/review-hello

Representative registration document before this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] }
]
}

After

With the same two offers active, both participate in one shared document.

Representative registration document after this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] },
{ "name": "web", "endpoint": "https://example.com/services/review-blocks" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "blocks"] }
]
}

Representative non-owner offer status after this fix:

conditions:
- type: Registeredstatus: "True"reason: Registeredmessage: Shared registration via demo/review-hello recorded agent 42

Why this matches ERC-8004

The fix aligns the controller with the EIP's intended model:

• one agentURI
• one agent registration document
• many services inside services[]
• optional domain verification via /.well-known/agent-registration.json

Validation

• go test -v ./internal/serviceoffercontroller
• go test -run TestNope ./cmd/obol ./internal/erc8004 ./internal/monetizeapi ./internal/x402 ./internal/stack
• TestBuildRegistrationConfigMap_PublishesAggregatedAgentRegistration verifies that the published agent-registration.json payload contains every expected service endpoint, not just the aggregated in-memory document

[bussyjd]

Summary

• aggregate ERC-8004 registration across registration-enabled ServiceOffers into one shared agent document
• fan the shared registration status back out to all participating offers instead of marking non-owners as SingletonConflict
• hand the singleton registration request off cleanly when the current owner offer disappears, and refresh the shared document whenever offer state changes
• add controller/render tests covering aggregated services, shared registration status, and the final published registration payload

Context

Fixes#361.

ERC-8004 expects a single agentURI / /.well-known/agent-registration.json document with a services array. The previous controller behavior treated the path as singleton but still rendered the document from exactly one offer, which broke multi-service agents and demo flows.

Before / After

Old behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B{"Which offer owns /.well-known/agent-registration.json?"}
B -->|Oldest offer| C["Publish registration doc from one ServiceOffer only"]
B -->|All later offers| D["Registered=False\nSingletonConflict"]
C --> E["Only owner gets Registered=True"]
E --> F["Only owner can contribute to Ready-dependent discovery surfaces"]

Loading

New behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B["Select canonical registration owner"]
B --> C["Build one shared ERC-8004 document"]
C --> D["Append all eligible offer endpoints into services[]"]
D --> E["Publish shared /.well-known/agent-registration.json"]
E --> F["Propagate shared agentId / txHash / registration status to all participating offers"]

Loading

Owner Handoff

sequenceDiagram
participant OfferA as "Owner Offer"
participant Ctrl as "serviceoffer-controller"
participant Req as "Shared RegistrationRequest"
participant OfferB as "Next Eligible Offer"
OfferA->>Ctrl: deleted or disabled
Ctrl->>Req: stop using old owner identity
Ctrl->>OfferB: enqueue reconcile
Ctrl->>Req: recreate or refresh under new owner
Req->>Ctrl: shared status updated
Ctrl->>OfferB: set Registered=True via shared agent doc

Loading

Concrete Examples

Before

Two offers:

• demo/review-hello
• demo/review-blocks

Observed result:

• review-hello gets Registered=True
• review-blocks gets Registered=False with SingletonConflict
• shared registration document contains only the review-hello endpoint

Representative status on the later offer:

conditions:
- type: Registeredstatus: "False"reason: SingletonConflictmessage: Registration path /.well-known/agent-registration.json is reserved by demo/review-hello

Representative registration document before this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] }
]
}

After

With the same two offers active, both participate in one shared document.

Representative registration document after this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] },
{ "name": "web", "endpoint": "https://example.com/services/review-blocks" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "blocks"] }
]
}

Representative non-owner offer status after this fix:

conditions:
- type: Registeredstatus: "True"reason: Registeredmessage: Shared registration via demo/review-hello recorded agent 42

Why this matches ERC-8004

The fix aligns the controller with the EIP's intended model:

• one agentURI
• one agent registration document
• many services inside services[]
• optional domain verification via /.well-known/agent-registration.json

Validation

• go test -v ./internal/serviceoffercontroller
• go test -run TestNope ./cmd/obol ./internal/erc8004 ./internal/monetizeapi ./internal/x402 ./internal/stack
• TestBuildRegistrationConfigMap_PublishesAggregatedAgentRegistration verifies that the published agent-registration.json payload contains every expected service endpoint, not just the aggregated in-memory document

[bussyjd]

Summary

• aggregate ERC-8004 registration across registration-enabled ServiceOffers into one shared agent document
• fan the shared registration status back out to all participating offers instead of marking non-owners as SingletonConflict
• hand the singleton registration request off cleanly when the current owner offer disappears, and refresh the shared document whenever offer state changes
• add controller/render tests covering aggregated services, shared registration status, and the final published registration payload

Context

Fixes#361.

ERC-8004 expects a single agentURI / /.well-known/agent-registration.json document with a services array. The previous controller behavior treated the path as singleton but still rendered the document from exactly one offer, which broke multi-service agents and demo flows.

Before / After

Old behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B{"Which offer owns /.well-known/agent-registration.json?"}
B -->|Oldest offer| C["Publish registration doc from one ServiceOffer only"]
B -->|All later offers| D["Registered=False\nSingletonConflict"]
C --> E["Only owner gets Registered=True"]
E --> F["Only owner can contribute to Ready-dependent discovery surfaces"]

Loading

New behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B["Select canonical registration owner"]
B --> C["Build one shared ERC-8004 document"]
C --> D["Append all eligible offer endpoints into services[]"]
D --> E["Publish shared /.well-known/agent-registration.json"]
E --> F["Propagate shared agentId / txHash / registration status to all participating offers"]

Loading

Owner Handoff

sequenceDiagram
participant OfferA as "Owner Offer"
participant Ctrl as "serviceoffer-controller"
participant Req as "Shared RegistrationRequest"
participant OfferB as "Next Eligible Offer"
OfferA->>Ctrl: deleted or disabled
Ctrl->>Req: stop using old owner identity
Ctrl->>OfferB: enqueue reconcile
Ctrl->>Req: recreate or refresh under new owner
Req->>Ctrl: shared status updated
Ctrl->>OfferB: set Registered=True via shared agent doc

Loading

Concrete Examples

Before

Two offers:

• demo/review-hello
• demo/review-blocks

Observed result:

• review-hello gets Registered=True
• review-blocks gets Registered=False with SingletonConflict
• shared registration document contains only the review-hello endpoint

Representative status on the later offer:

conditions:
- type: Registeredstatus: "False"reason: SingletonConflictmessage: Registration path /.well-known/agent-registration.json is reserved by demo/review-hello

Representative registration document before this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] }
]
}

After

With the same two offers active, both participate in one shared document.

Representative registration document after this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] },
{ "name": "web", "endpoint": "https://example.com/services/review-blocks" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "blocks"] }
]
}

Representative non-owner offer status after this fix:

conditions:
- type: Registeredstatus: "True"reason: Registeredmessage: Shared registration via demo/review-hello recorded agent 42

Why this matches ERC-8004

The fix aligns the controller with the EIP's intended model:

• one agentURI
• one agent registration document
• many services inside services[]
• optional domain verification via /.well-known/agent-registration.json

Validation

• go test -v ./internal/serviceoffercontroller
• go test -run TestNope ./cmd/obol ./internal/erc8004 ./internal/monetizeapi ./internal/x402 ./internal/stack
• TestBuildRegistrationConfigMap_PublishesAggregatedAgentRegistration verifies that the published agent-registration.json payload contains every expected service endpoint, not just the aggregated in-memory document

[bussyjd]

Summary

• aggregate ERC-8004 registration across registration-enabled ServiceOffers into one shared agent document
• fan the shared registration status back out to all participating offers instead of marking non-owners as SingletonConflict
• hand the singleton registration request off cleanly when the current owner offer disappears, and refresh the shared document whenever offer state changes
• add controller/render tests covering aggregated services, shared registration status, and the final published registration payload

Context

Fixes#361.

ERC-8004 expects a single agentURI / /.well-known/agent-registration.json document with a services array. The previous controller behavior treated the path as singleton but still rendered the document from exactly one offer, which broke multi-service agents and demo flows.

Before / After

Old behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B{"Which offer owns /.well-known/agent-registration.json?"}
B -->|Oldest offer| C["Publish registration doc from one ServiceOffer only"]
B -->|All later offers| D["Registered=False\nSingletonConflict"]
C --> E["Only owner gets Registered=True"]
E --> F["Only owner can contribute to Ready-dependent discovery surfaces"]

Loading

New behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B["Select canonical registration owner"]
B --> C["Build one shared ERC-8004 document"]
C --> D["Append all eligible offer endpoints into services[]"]
D --> E["Publish shared /.well-known/agent-registration.json"]
E --> F["Propagate shared agentId / txHash / registration status to all participating offers"]

Loading

Owner Handoff

sequenceDiagram
participant OfferA as "Owner Offer"
participant Ctrl as "serviceoffer-controller"
participant Req as "Shared RegistrationRequest"
participant OfferB as "Next Eligible Offer"
OfferA->>Ctrl: deleted or disabled
Ctrl->>Req: stop using old owner identity
Ctrl->>OfferB: enqueue reconcile
Ctrl->>Req: recreate or refresh under new owner
Req->>Ctrl: shared status updated
Ctrl->>OfferB: set Registered=True via shared agent doc

Loading

Concrete Examples

Before

Two offers:

• demo/review-hello
• demo/review-blocks

Observed result:

• review-hello gets Registered=True
• review-blocks gets Registered=False with SingletonConflict
• shared registration document contains only the review-hello endpoint

Representative status on the later offer:

conditions:
- type: Registeredstatus: "False"reason: SingletonConflictmessage: Registration path /.well-known/agent-registration.json is reserved by demo/review-hello

Representative registration document before this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] }
]
}

After

With the same two offers active, both participate in one shared document.

Representative registration document after this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] },
{ "name": "web", "endpoint": "https://example.com/services/review-blocks" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "blocks"] }
]
}

Representative non-owner offer status after this fix:

conditions:
- type: Registeredstatus: "True"reason: Registeredmessage: Shared registration via demo/review-hello recorded agent 42

Why this matches ERC-8004

The fix aligns the controller with the EIP's intended model:

• one agentURI
• one agent registration document
• many services inside services[]
• optional domain verification via /.well-known/agent-registration.json

Validation

• go test -v ./internal/serviceoffercontroller
• go test -run TestNope ./cmd/obol ./internal/erc8004 ./internal/monetizeapi ./internal/x402 ./internal/stack
• TestBuildRegistrationConfigMap_PublishesAggregatedAgentRegistration verifies that the published agent-registration.json payload contains every expected service endpoint, not just the aggregated in-memory document

[bussyjd]

Summary

• aggregate ERC-8004 registration across registration-enabled ServiceOffers into one shared agent document
• fan the shared registration status back out to all participating offers instead of marking non-owners as SingletonConflict
• hand the singleton registration request off cleanly when the current owner offer disappears, and refresh the shared document whenever offer state changes
• add controller/render tests covering aggregated services, shared registration status, and the final published registration payload

Context

Fixes#361.

ERC-8004 expects a single agentURI / /.well-known/agent-registration.json document with a services array. The previous controller behavior treated the path as singleton but still rendered the document from exactly one offer, which broke multi-service agents and demo flows.

Before / After

Old behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B{"Which offer owns /.well-known/agent-registration.json?"}
B -->|Oldest offer| C["Publish registration doc from one ServiceOffer only"]
B -->|All later offers| D["Registered=False\nSingletonConflict"]
C --> E["Only owner gets Registered=True"]
E --> F["Only owner can contribute to Ready-dependent discovery surfaces"]

Loading

New behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B["Select canonical registration owner"]
B --> C["Build one shared ERC-8004 document"]
C --> D["Append all eligible offer endpoints into services[]"]
D --> E["Publish shared /.well-known/agent-registration.json"]
E --> F["Propagate shared agentId / txHash / registration status to all participating offers"]

Loading

Owner Handoff

sequenceDiagram
participant OfferA as "Owner Offer"
participant Ctrl as "serviceoffer-controller"
participant Req as "Shared RegistrationRequest"
participant OfferB as "Next Eligible Offer"
OfferA->>Ctrl: deleted or disabled
Ctrl->>Req: stop using old owner identity
Ctrl->>OfferB: enqueue reconcile
Ctrl->>Req: recreate or refresh under new owner
Req->>Ctrl: shared status updated
Ctrl->>OfferB: set Registered=True via shared agent doc

Loading

Concrete Examples

Before

Two offers:

• demo/review-hello
• demo/review-blocks

Observed result:

• review-hello gets Registered=True
• review-blocks gets Registered=False with SingletonConflict
• shared registration document contains only the review-hello endpoint

Representative status on the later offer:

conditions:
- type: Registeredstatus: "False"reason: SingletonConflictmessage: Registration path /.well-known/agent-registration.json is reserved by demo/review-hello

Representative registration document before this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] }
]
}

After

With the same two offers active, both participate in one shared document.

Representative registration document after this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] },
{ "name": "web", "endpoint": "https://example.com/services/review-blocks" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "blocks"] }
]
}

Representative non-owner offer status after this fix:

conditions:
- type: Registeredstatus: "True"reason: Registeredmessage: Shared registration via demo/review-hello recorded agent 42

Why this matches ERC-8004

The fix aligns the controller with the EIP's intended model:

• one agentURI
• one agent registration document
• many services inside services[]
• optional domain verification via /.well-known/agent-registration.json

Validation

• go test -v ./internal/serviceoffercontroller
• go test -run TestNope ./cmd/obol ./internal/erc8004 ./internal/monetizeapi ./internal/x402 ./internal/stack
• TestBuildRegistrationConfigMap_PublishesAggregatedAgentRegistration verifies that the published agent-registration.json payload contains every expected service endpoint, not just the aggregated in-memory document

[bussyjd]

Summary

• aggregate ERC-8004 registration across registration-enabled ServiceOffers into one shared agent document
• fan the shared registration status back out to all participating offers instead of marking non-owners as SingletonConflict
• hand the singleton registration request off cleanly when the current owner offer disappears, and refresh the shared document whenever offer state changes
• add controller/render tests covering aggregated services, shared registration status, and the final published registration payload

Context

Fixes#361.

ERC-8004 expects a single agentURI / /.well-known/agent-registration.json document with a services array. The previous controller behavior treated the path as singleton but still rendered the document from exactly one offer, which broke multi-service agents and demo flows.

Before / After

Old behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B{"Which offer owns /.well-known/agent-registration.json?"}
B -->|Oldest offer| C["Publish registration doc from one ServiceOffer only"]
B -->|All later offers| D["Registered=False\nSingletonConflict"]
C --> E["Only owner gets Registered=True"]
E --> F["Only owner can contribute to Ready-dependent discovery surfaces"]

Loading

New behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B["Select canonical registration owner"]
B --> C["Build one shared ERC-8004 document"]
C --> D["Append all eligible offer endpoints into services[]"]
D --> E["Publish shared /.well-known/agent-registration.json"]
E --> F["Propagate shared agentId / txHash / registration status to all participating offers"]

Loading

Owner Handoff

sequenceDiagram
participant OfferA as "Owner Offer"
participant Ctrl as "serviceoffer-controller"
participant Req as "Shared RegistrationRequest"
participant OfferB as "Next Eligible Offer"
OfferA->>Ctrl: deleted or disabled
Ctrl->>Req: stop using old owner identity
Ctrl->>OfferB: enqueue reconcile
Ctrl->>Req: recreate or refresh under new owner
Req->>Ctrl: shared status updated
Ctrl->>OfferB: set Registered=True via shared agent doc

Loading

Concrete Examples

Before

Two offers:

• demo/review-hello
• demo/review-blocks

Observed result:

• review-hello gets Registered=True
• review-blocks gets Registered=False with SingletonConflict
• shared registration document contains only the review-hello endpoint

Representative status on the later offer:

conditions:
- type: Registeredstatus: "False"reason: SingletonConflictmessage: Registration path /.well-known/agent-registration.json is reserved by demo/review-hello

Representative registration document before this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] }
]
}

After

With the same two offers active, both participate in one shared document.

Representative registration document after this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] },
{ "name": "web", "endpoint": "https://example.com/services/review-blocks" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "blocks"] }
]
}

Representative non-owner offer status after this fix:

conditions:
- type: Registeredstatus: "True"reason: Registeredmessage: Shared registration via demo/review-hello recorded agent 42

Why this matches ERC-8004

The fix aligns the controller with the EIP's intended model:

• one agentURI
• one agent registration document
• many services inside services[]
• optional domain verification via /.well-known/agent-registration.json

Validation

• go test -v ./internal/serviceoffercontroller
• go test -run TestNope ./cmd/obol ./internal/erc8004 ./internal/monetizeapi ./internal/x402 ./internal/stack
• TestBuildRegistrationConfigMap_PublishesAggregatedAgentRegistration verifies that the published agent-registration.json payload contains every expected service endpoint, not just the aggregated in-memory document

[bussyjd]

Summary

• aggregate ERC-8004 registration across registration-enabled ServiceOffers into one shared agent document
• fan the shared registration status back out to all participating offers instead of marking non-owners as SingletonConflict
• hand the singleton registration request off cleanly when the current owner offer disappears, and refresh the shared document whenever offer state changes
• add controller/render tests covering aggregated services, shared registration status, and the final published registration payload

Context

Fixes#361.

ERC-8004 expects a single agentURI / /.well-known/agent-registration.json document with a services array. The previous controller behavior treated the path as singleton but still rendered the document from exactly one offer, which broke multi-service agents and demo flows.

Before / After

Old behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B{"Which offer owns /.well-known/agent-registration.json?"}
B -->|Oldest offer| C["Publish registration doc from one ServiceOffer only"]
B -->|All later offers| D["Registered=False\nSingletonConflict"]
C --> E["Only owner gets Registered=True"]
E --> F["Only owner can contribute to Ready-dependent discovery surfaces"]

Loading

New behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B["Select canonical registration owner"]
B --> C["Build one shared ERC-8004 document"]
C --> D["Append all eligible offer endpoints into services[]"]
D --> E["Publish shared /.well-known/agent-registration.json"]
E --> F["Propagate shared agentId / txHash / registration status to all participating offers"]

Loading

Owner Handoff

sequenceDiagram
participant OfferA as "Owner Offer"
participant Ctrl as "serviceoffer-controller"
participant Req as "Shared RegistrationRequest"
participant OfferB as "Next Eligible Offer"
OfferA->>Ctrl: deleted or disabled
Ctrl->>Req: stop using old owner identity
Ctrl->>OfferB: enqueue reconcile
Ctrl->>Req: recreate or refresh under new owner
Req->>Ctrl: shared status updated
Ctrl->>OfferB: set Registered=True via shared agent doc

Loading

Concrete Examples

Before

Two offers:

• demo/review-hello
• demo/review-blocks

Observed result:

• review-hello gets Registered=True
• review-blocks gets Registered=False with SingletonConflict
• shared registration document contains only the review-hello endpoint

Representative status on the later offer:

conditions:
- type: Registeredstatus: "False"reason: SingletonConflictmessage: Registration path /.well-known/agent-registration.json is reserved by demo/review-hello

Representative registration document before this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] }
]
}

After

With the same two offers active, both participate in one shared document.

Representative registration document after this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] },
{ "name": "web", "endpoint": "https://example.com/services/review-blocks" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "blocks"] }
]
}

Representative non-owner offer status after this fix:

conditions:
- type: Registeredstatus: "True"reason: Registeredmessage: Shared registration via demo/review-hello recorded agent 42

Why this matches ERC-8004

The fix aligns the controller with the EIP's intended model:

• one agentURI
• one agent registration document
• many services inside services[]
• optional domain verification via /.well-known/agent-registration.json

Validation

• go test -v ./internal/serviceoffercontroller
• go test -run TestNope ./cmd/obol ./internal/erc8004 ./internal/monetizeapi ./internal/x402 ./internal/stack
• TestBuildRegistrationConfigMap_PublishesAggregatedAgentRegistration verifies that the published agent-registration.json payload contains every expected service endpoint, not just the aggregated in-memory document

[bussyjd]

Summary

• aggregate ERC-8004 registration across registration-enabled ServiceOffers into one shared agent document
• fan the shared registration status back out to all participating offers instead of marking non-owners as SingletonConflict
• hand the singleton registration request off cleanly when the current owner offer disappears, and refresh the shared document whenever offer state changes
• add controller/render tests covering aggregated services, shared registration status, and the final published registration payload

Context

Fixes#361.

ERC-8004 expects a single agentURI / /.well-known/agent-registration.json document with a services array. The previous controller behavior treated the path as singleton but still rendered the document from exactly one offer, which broke multi-service agents and demo flows.

Before / After

Old behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B{"Which offer owns /.well-known/agent-registration.json?"}
B -->|Oldest offer| C["Publish registration doc from one ServiceOffer only"]
B -->|All later offers| D["Registered=False\nSingletonConflict"]
C --> E["Only owner gets Registered=True"]
E --> F["Only owner can contribute to Ready-dependent discovery surfaces"]

Loading

New behavior

flowchart TD
A["Registration-enabled ServiceOffers"] --> B["Select canonical registration owner"]
B --> C["Build one shared ERC-8004 document"]
C --> D["Append all eligible offer endpoints into services[]"]
D --> E["Publish shared /.well-known/agent-registration.json"]
E --> F["Propagate shared agentId / txHash / registration status to all participating offers"]

Loading

Owner Handoff

sequenceDiagram
participant OfferA as "Owner Offer"
participant Ctrl as "serviceoffer-controller"
participant Req as "Shared RegistrationRequest"
participant OfferB as "Next Eligible Offer"
OfferA->>Ctrl: deleted or disabled
Ctrl->>Req: stop using old owner identity
Ctrl->>OfferB: enqueue reconcile
Ctrl->>Req: recreate or refresh under new owner
Req->>Ctrl: shared status updated
Ctrl->>OfferB: set Registered=True via shared agent doc

Loading

Concrete Examples

Before

Two offers:

• demo/review-hello
• demo/review-blocks

Observed result:

• review-hello gets Registered=True
• review-blocks gets Registered=False with SingletonConflict
• shared registration document contains only the review-hello endpoint

Representative status on the later offer:

conditions:
- type: Registeredstatus: "False"reason: SingletonConflictmessage: Registration path /.well-known/agent-registration.json is reserved by demo/review-hello

Representative registration document before this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] }
]
}

After

With the same two offers active, both participate in one shared document.

Representative registration document after this fix:

{
"name": "review-hello",
"services": [
{ "name": "web", "endpoint": "https://example.com/services/review-hello" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "hello"] },
{ "name": "web", "endpoint": "https://example.com/services/review-blocks" },
{ "name": "OASF", "version": "0.8", "skills": ["x402-demo", "blocks"] }
]
}

Representative non-owner offer status after this fix:

conditions:
- type: Registeredstatus: "True"reason: Registeredmessage: Shared registration via demo/review-hello recorded agent 42

Why this matches ERC-8004

The fix aligns the controller with the EIP's intended model:

• one agentURI
• one agent registration document
• many services inside services[]
• optional domain verification via /.well-known/agent-registration.json

Validation

• go test -v ./internal/serviceoffercontroller
• go test -run TestNope ./cmd/obol ./internal/erc8004 ./internal/monetizeapi ./internal/x402 ./internal/stack
• TestBuildRegistrationConfigMap_PublishesAggregatedAgentRegistration verifies that the published agent-registration.json payload contains every expected service endpoint, not just the aggregated in-memory document