[tdprajwal]

Resolves OpenAgriNet/network-adapter#74 (parent OpenAgriNet/network-adapter#48).

What

networkofnetwork/ stands up two OAN networks on one machine. For #74, make host-descriptor (bin/oanfed.py publish) builds each network's Network Descriptor from its registry entry, signs it, and writes it together with its JWKS. nginx serves both as static files at the fixed paths:

• GET https://{networkId}/.well-known/openagrinet
• GET https://{networkId}/.well-known/jwks.json

The open decision from #74

• Signature algorithm: Ed25519. That is its fully-specified JOSE name (RFC 9864, which deprecates EdDSA).
• Canonical encoding: RFC 8785 (JCS) over the descriptor without signature. Keys are ordered by UTF-16 code units. Floats, integers above 2^53 and lone surrogates are refused, so every implementation rebuilds identical bytes.

Keys (matches Trust and signatures / Trust and key lifecycle in the doc)

Key	Where	Signs	Published
Governance	keys/governance.key, generated mode 600, never in the registry	The Descriptor only	JWKS; signature.keyId
Operational	The registry entry's active, unexpired Ed25519 keys (the adapters' traffic keys)	Traffic	JWKS; delegated by kid in the signed operationalKeys

• kid = RFC 7638 thumbprint, so a rotated key gets a new kid without any configuration. The overlap comes from the registry entry, which already holds keys as a list with validUntil / status.
• Peers' admit stores only the delegated operational keys. The governance key can never pass a traffic check, and a key slipped into the JWKS without being delegated in the descriptor is ignored.

Validation (before signing, and on verify)

The descriptor is checked against the contract table:

• version is 1.0; networkId is a lowercase DNS domain.
• name, operator.name and status (Active/Suspended/Retired) are present; revision is an integer ≥ 1.
• issuedAt is UTC and not in the future (5 min skew allowed); operatingProfile is non-empty.
• schemaPacks and services.discovery are https URLs; contacts and projectionTtl are well-formed.

The JWKS is checked too: no duplicate kids, Ed25519 keys are 32 bytes, and alg/use are correct. The signer must not also be delegated for traffic, and every delegated kid must be published.

publish refuses to write when:

• the revision does not increase over what is already published (a corrupt published file is an error, not revision 0);
• the governance key is also a registered traffic key;
• the key file is readable by group or others;
• there is no usable traffic key;
• the document fails its own verification.

It writes the JWKS before the descriptor, each atomically, so a peer never sees a descriptor whose key is not yet published.

Proof

• python3 -m unittest networkofnetwork/bin/test_oanfed.py: 21 tests pass. They cover the JCS RFC 8785 vectors, tampering with every signed field, malformed signatures and JWKS, contract fields, revision rollback, key-file permissions, the key split, delegation-only admit, and revoked/expired/upcoming keys.
• Ran publish against a live registry: the output verifies.

Out of scope (sibling issues)

• 55/66-run-a-single-adapter-through-the-helm-charts-and-run-a-single-adapter-at-the-network-layer-in-docker-compose #75 admit: "same revision with different content → integrity conflict", and recording a governance trust anchor.
• feat: wire the PMFBY grievance plugin into quick-start #78: delegation expiry/revocation beyond the registry key's validUntil/status.

Secrets

networks/ (per-network keys, TLS, .env) is git-ignored. .env.example holds only local demo defaults.

[tdprajwal]

Closing; a new PR will follow.