Push: a bookmark update signed by a delegate is refused as 'unknown key' until the delegate has signed a change issue #129 closed: completed andymccall opened this · 1 comment
andymccall set labels bug, gap ·
andymccall
Fixed in oxygen 623c88fb (refs this issue): a push that moves a bookmark now carries the identity that signed the move and the one it acts for, so the hub can check a delegate it has never seen a change from. Test: oxy-core a_delegate_s_first_push_of_a_bookmark_carries_its_identity (without the fix: unknown key). It reaches the agents with the next oxy release (or install).
andymccall closed ·
From oxygen_feedback.md (supermarioland2, 2026-10-10): an agent delegate (ea5f78160088 of Andy's identity 8bc05e0a) pushed a new bookmark at an existing change of Andy's and was refused 'unknown key'; after it pushed a change it had signed, the same push went through. The hub learns a delegate only from an identity object travelling with a change it signed. Ask: resolve the signer through the identity the hub already holds, or have the client send the identity with any push it signs; and an error that says how to fix it.