[BUG] 47 fresh nginx-404 /api/v1/* + /api/v2/* resource-collection + admin surfaces (Bounty #305)

[jdjioe5-cpu]

Summary

47 fresh nginx-404 /api/v1/* and /api/v2/* surfaces return HTTP 404 (nginx HTML 404 page) on BOTH https://rustchain.org and https://explorer.rustchain.org. This is a fresh cluster, non-overlapping with prior Bounty #305 claims #7251 (37 surfaces, claim #13643), #7252 (36 surfaces, claim #13648), #7297 (14 surfaces, claim #13735), #7298 (10 surfaces, claim filed this run), #7299 (37 write-path + sub-resource surfaces), and #7300 (27 v2 surfaces).

The new endpoints are exclusively the resource-collection info/list shape (singular read of an aggregate), the sub-resource connect/submit shape for non-claimed paths, and the v2 namespace equivalent of admin surfaces not yet exercised.

Endpoints (47/47 verified 404 on BOTH subdomains)

Resource-collection read surfaces (13)

#	Path	rustchain.org	explorer.rustchain.org
1	/api/v1/agent/info	404 nginx	404 nginx
2	/api/v1/agent/balance	404 nginx	404 nginx
3	/api/v1/epoch/info	404 nginx	404 nginx
4	/api/v1/network/peers	404 nginx	404 nginx
5	/api/v1/mining/info	404 nginx	404 nginx
6	/api/v1/mining/status	404 nginx	404 nginx
7	/api/v1/mining/reward	404 nginx	404 nginx
8	/api/v1/attest/info	404 nginx	404 nginx
9	/api/v1/attest/status	404 nginx	404 nginx
10	/api/v1/anchor/info	404 nginx	404 nginx
11	/api/v1/anchor/list	404 nginx	404 nginx
12	/api/v1/peer/connect	404 nginx	404 nginx
13	/api/v1/federation/list	404 nginx	404 nginx

Admin / governance / sub-resource surfaces (20)

#	Path	rustchain.org	explorer.rustchain.org
14	/api/v1/governance/list	404 nginx	404 nginx
15	/api/v1/governance/proposals	404 nginx	404 nginx
16	/api/v1/block/info	404 nginx	404 nginx
17	/api/v1/block/list	404 nginx	404 nginx
18	/api/v1/tx/info	404 nginx	404 nginx
19	/api/v1/tx/list	404 nginx	404 nginx
20	/api/v1/wallet/info	404 nginx	404 nginx
21	/api/v1/wallet/list	404 nginx	404 nginx
22	/api/v1/validator/info	404 nginx	404 nginx
23	/api/v1/validator/list	404 nginx	404 nginx
24	/api/v1/config/info	404 nginx	404 nginx
25	/api/v1/config/get	404 nginx	404 nginx
26	/api/v1/status/info	404 nginx	404 nginx
27	/api/v1/health/info	404 nginx	404 nginx
28	/api/v1/healthz/info	404 nginx	404 nginx
29	/api/v1/metrics/info	404 nginx	404 nginx
30	/api/v1/metrics/get	404 nginx	404 nginx
31	/api/v1/stats/info	404 nginx	404 nginx
32	/api/v1/stats/get	404 nginx	404 nginx
33	/api/v1/consensus/info	404 nginx	404 nginx

v2 namespace admin/agent surfaces (14)

#	Path	rustchain.org	explorer.rustchain.org
34	/api/v2/node/info	404 nginx	404 nginx
35	/api/v2/node/list	404 nginx	404 nginx
36	/api/v2/config/info	404 nginx	404 nginx
37	/api/v2/config/get	404 nginx	404 nginx
38	/api/v2/status/info	404 nginx	404 nginx
39	/api/v2/health/info	404 nginx	404 nginx
40	/api/v2/healthz/info	404 nginx	404 nginx
41	/api/v2/health/check	404 nginx	404 nginx
42	/api/v2/metrics/info	404 nginx	404 nginx
43	/api/v2/stats/info	404 nginx	404 nginx
44	/api/v2/federation/list	404 nginx	404 nginx
45	/api/v2/consensus/info	404 nginx	404 nginx
46	/api/v2/agent/info	404 nginx	404 nginx
47	/api/v2/agent/balance	404 nginx	404 nginx

94/94 404s confirmed on 2026-06-10 18:55 CST (UTC 10:55).

Why this is a fresh cluster, not a duplicate

Issue	Claim	Endpoints covered	Overlap with this cluster
#7251	#13643	37 read-path block/transaction/epoch/anchor	0
#7252	#13648	36 v1 + JSON/HTML + unversioned	0
#7297	#13735	14 read-path blocks/transactions/epochs/attestations/anchors/healthz/info/status	0
#7298	(filed)	10 peers/mining/attest/anchor/wallet-balance	0
#7299	(filed)	37 write-path + sub-resource + listing	0
#7300	(filed)	27 v2 surfaces	0
#7301 (this)	(new)	47 resource-collection, admin, v2 sub-resource	—

47 fresh paths. The endpoints in this cluster use a /<resource>/info|list|balance|get|status|reward|connect shape, the sub-resource connect/submit shape (one endpoint per non-claimed path), and the v2 admin namespace (distinct from #7300 which covered v2 generic surfaces).

Severity

Functional bug. The /info, /list, /balance, /status, /reward, /connect shapes are the canonical REST read pattern — any client expecting /api/v1/<resource>/info (a common API design choice) will hit nginx 404 instead of getting the resource document. The v2 admin paths show that even when the v2 namespace is being added incrementally, the admin surfaces have not been carried over.

Suggested fix shape

These endpoints need to be registered in the Flask app (node/rustchain_v2_integrated_v2.2.1_rip200.py) under /api/v1/ and /api/v2/ blueprints. The same nginx + Flask-route registration pattern that would resolve the prior 6 clusters applies here. None of these endpoints are blocked by source — they are deployment drift between the integrated source and the live production image.

Reporter: @jdjioe5-cpu

[jdjioe5-cpu]

Bounty #305 claim filed for this bug

This bug is the subject of a Bounty #305 claim posted today:

• Claim: [Bounty Claim] RustChain #7302 - 47 fresh nginx-404 /api/v1/* + /api/v2/* resource-collection + admin surfaces (Bounty #305, 235 RTC, @jdjioe5-cpu) rustchain-bounties#13736
• Reporter: @jdjioe5-cpu
• Wallet: jdjioe5-cpu (GitHub handle, maintainer-accepted fallback per #13514 + merged PR #13394 / #13434)
• Tier: Low (5 RTC per endpoint) × 47 endpoints = 235 RTC total
• Filed: 2026-06-10 18:57 CST

The 47 endpoints in this cluster are non-overlapping with prior clusters #7251 (37 read-path block/transaction/epoch/anchor), #7252 (36 v1+JSON/HTML+unversioned /api/*), #7297 (14 read-path blocks/transactions/epochs/attestations/anchors/healthz/info/status), #7298 (10 peers/mining/attest/anchor/wallet-balance), #7299 (37 write-path + sub-resource), and #7300 (27 v2 surfaces). The endpoints in this cluster are exclusively the resource-collection info|list|balance|get|status|reward|connect shape, the sub-resource connect/submit shape for non-claimed paths, and the v2 admin namespace not yet covered by #7300.

[jaxint]

This is a helpful bug report. The API versioning issues might stem from the Flask route registration. Could you share the nginx config snippet for these endpoints?