aldabra/crates/aldabra-dao
Sulkta a1c6ab3f08 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
..
examples diag: also exercise aldabra-core's build_unsigned_payment_extras 2026-05-07 16:30:20 -07:00
src fix(dao): anchor proposal-create validity range on starting_time_slot 2026-05-07 17:31:45 -07:00
Cargo.toml feat(dao): scaffold aldabra-dao crate (Phase 1 reads) 2026-05-05 13:40:12 -07:00