Fix initial guardian set expiration on mainnet
Change-Id: I41adacc68687d0c638e79c834b7441896dc4ed98
This commit is contained in:
parent
610bf76902
commit
1a8bf4456e
|
@ -161,6 +161,11 @@ fn check_active<'r>(
|
||||||
guardian_set: &GuardianSet<'r, { AccountState::Initialized }>,
|
guardian_set: &GuardianSet<'r, { AccountState::Initialized }>,
|
||||||
clock: &Sysvar<'r, Clock>,
|
clock: &Sysvar<'r, Clock>,
|
||||||
) -> Result<()> {
|
) -> Result<()> {
|
||||||
|
// IMPORTANT - this is a fix for mainnet wormhole
|
||||||
|
// The initial guardian set was never expired so we block it here.
|
||||||
|
if guardian_set.index == 0 && guardian_set.creation_time == 1628099186 {
|
||||||
|
return Err(PostVAAGuardianSetExpired.into());
|
||||||
|
}
|
||||||
if guardian_set.expiration_time != 0
|
if guardian_set.expiration_time != 0
|
||||||
&& (guardian_set.expiration_time as i64) < clock.unix_timestamp
|
&& (guardian_set.expiration_time as i64) < clock.unix_timestamp
|
||||||
{
|
{
|
||||||
|
|
Loading…
Reference in New Issue