Skip to content

fix: start the XanV2Vesting recipients as an empty list - #201

Merged
heueristik merged 1 commit into
heueristik/xan-vestingfrom
jonaprieto/xan-v2-vesting-empty-recipients
Oct 16, 2026
Merged

heueristik merged 1 commit into
heueristik/xan-vestingfrom
jonaprieto/xan-v2-vesting-empty-recipients

Conversation

@jonaprieto

Copy link
Copy Markdown
Contributor

follow-up from reviewing #184. the recipients file starts as an empty list instead of address(1) with 1 XAN, so the committed payload is addRecipients([]) and adds nothing if someone submits it before the real list lands. the generator's empty-list guard goes away: it came from the deploy script, which no longer reads the recipients.

The placeholder recipient, address(1) with 1 XAN, produced a payload
that passed CI and targeted the real proxy. Submitted by mistake, it
would add a principal that can never unlock and cannot be removed.

An empty list produces addRecipients([]), which adds nothing. The
generator no longer rejects an empty list: that guard came from the
deploy script, which no longer reads the recipients.

Refs #184
@jonaprieto jonaprieto added the fix Bug fix label Oct 16, 2026
@jonaprieto jonaprieto self-assigned this Oct 16, 2026
@heueristik
heueristik merged commit fec1f1c into heueristik/xan-vesting Oct 16, 2026
2 checks passed
@heueristik
heueristik deleted the jonaprieto/xan-v2-vesting-empty-recipients branch October 19, 2026 12:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fix Bug fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants