Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JUICEIT BOT #1309

Closed
verabehr opened this issue Feb 23, 2024 · 1 comment
Closed

JUICEIT BOT #1309

verabehr opened this issue Feb 23, 2024 · 1 comment
Assignees

Comments

@verabehr
Copy link

verabehr commented Feb 23, 2024

@taariq
Copy link
Member

taariq commented Feb 26, 2024

Rug pull. Closing due to change in strategy.

@taariq taariq closed this as completed Feb 26, 2024
maharifu added a commit that referenced this issue Oct 8, 2024
# Related Github tickets

- Closes #2250
- Closes #2251
- Closes #2252

# Background

Keep an on-chain list of activated lightnodes. When a new node is
activated, we add it to the list. To bootstrap the list with the
existing lightnodes, we add a new transaction. This is instead of a
governance vote, so we don't waste more time. The transaction can be
executed at any time after the upgrade.
For each lightnode we keep track of: address, activated timestamp, last
authentication timestamp. This way we can also know which nodes are
active and performing authentications.

# Testing completed

- [ ] test coverage exists or has been added/updated
- [x] tested in a private testnet

# Breaking changes

- [x] I have checked my code for breaking changes
- [x] If there are breaking changes, there is a supporting migration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants