Regression from #266: every metalgear2 fetch takes 14 s issue #271 closed: completed andymccall opened this 16 days ago · 0 comments

Since the issue #266 deploy (2026-10-19 ~14:50), 1,302 fetches of doomsdayone/metalgear2 averaged 14.4 s (none were slow before). The fetch bundle now carries every bookmark attestation's signers, computed on each fetch call: one pointer read and one signature list per bookmark. metalgear2's store is a bucket, where each signature list is a LIST request, and it has 145 bookmarks; a client sends one fetch per bookmark, so a clone was ~145² LISTs. Fix: compute the signer set once per operation head and keep it (oxy-core served_attest_signers), pinned into the hub and deployed. Found while Andy's oxy seal --proposal on supermarioland2 was slow.