Kayos f44a4f209c fix(dao): anchor proposal-create validity range on starting_time_slot ... Public Koios's tip endpoint can lag the actual chain by 100+ slots. Under a 29-slot governor window that lag pushes invalid_after into the past before the tx ever reaches a node — every retry hits OutsideValidityIntervalUTxO no matter how fast we sign+submit. Now: caller passes starting_time_slot derived from starting_time_ms via the network's shelley constants; builder uses it as valid_from. Caller can shift starting_time_ms slightly into the future to compensate for MCP roundtrip latency. The on-chain 'pvalidateProposalStartingTime' is still satisfied because starting_time_slot ∈ validRange by construction.		2026-05-07 17:31:45 -07:00
..
aldabra-chain	v0.2: 8 chain_* read-only Koios passthrough MCP tools	2026-05-05 07:01:32 -07:00
aldabra-core	plutus_mint: thread additional_signers into tx body's required_signers	2026-05-07 10:33:55 -07:00
aldabra-dao	fix(dao): anchor proposal-create validity range on starting_time_slot	2026-05-07 17:31:45 -07:00
aldabra-mcp	fix(dao): anchor proposal-create validity range on starting_time_slot	2026-05-07 17:31:45 -07:00