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.

Sign up for GitHub

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

Jump to bottom

Inactivating delaying slot owners #9

Closed
jgraef opened this issue Nov 1, 2019 · 3 comments
Closed

Inactivating delaying slot owners #9

jgraef opened this issue Nov 1, 2019 · 3 comments
Assignees
@paberr
Labels
enhancement New feature or request
Milestone
Albatross Protocol

Comments

@jgraef
Copy link
Contributor

jgraef commented Nov 1, 2019

From our discussion:

Instead of slashing (with fine) misbehaving validators, we can deactivate all stakes of that slot owner. The deactivation of the stakes will be done after a grace period of 2 epochs. The slot owner than either has to:

  • Produce a block in the next epoch (where their stake is still active) - optional
  • Send a restaking transaction in the next epoch - this should be the default behavior

The restaking transaction can be done using a warm address that is linked to that stake. Thus the validator only needs to keep a private key of the warm wallet which only needs funds for transaction fees.
@jgraef jgraef added the enhancement New feature or request label Nov 1, 2019
@paberr paberr changed the title Inactivating misbehaving slot owners Inactivating delaying slot owners Nov 5, 2019
@paberr
Copy link
Member

paberr commented Nov 5, 2019

This only affects view changes.

@paberr
Copy link
Member

paberr commented Nov 5, 2019

Moreover, one question: Do these validators still get parts of the reward?

@paberr paberr mentioned this issue Nov 5, 2019
Closed
@paberr paberr added this to the Albatross Protocol milestone Nov 10, 2019
@paberr paberr self-assigned this Nov 10, 2019
@jgraef jgraef mentioned this issue Nov 12, 2019
Closed
@paberr
Copy link
Member

paberr commented Nov 12, 2019

Moreover, one question: Do these validators still get parts of the reward?

See #21: They won't get the reward for the particular slot.

@paberr paberr mentioned this issue Nov 16, 2019
Merged
2 tasks
@paberr paberr closed this as completed Nov 16, 2019
@sisou sisou mentioned this issue Apr 7, 2021
Closed
hrxi added a commit that referenced this issue Mar 12, 2022
@hrxi
tracingify blockchain::push
d59bcaa 
Changes log messages a little, not sure if it affects readability too
much.

Old:
```
2022-03-11T17:25:45.637897Z DEBUG push                 | Accepted block #9.0:MI:df4a6595d1 with 0 transactions (extend)
2022-03-11T17:25:45.660765Z DEBUG push                 | Accepted block #10.0:MI:be38f68765 with 0 transactions (extend)
2022-03-11T17:25:45.687445Z DEBUG push                 | Accepted block #11.0:MI:2600b77a25 with 0 transactions (extend)

```

New:
```
2022-03-11T23:46:59.815181Z DEBUG push                 | Accepted block block=#9.0:MI:d846e5a8b4 num_transactions=0 kind="extend"
2022-03-11T23:46:59.863129Z DEBUG push                 | Accepted block block=#10.0:MI:1ea7fa1e4e num_transactions=0 kind="extend"
2022-03-11T23:46:59.899362Z DEBUG push                 | Accepted block block=#11.0:MI:a97db2b9df num_transactions=0 kind="extend"
```

Also, these haven't been tested for ingestion into Grafana yet, so maybe
we should hold off merging them.
hrxi added a commit that referenced this issue Mar 12, 2022
@hrxi
tracingify blockchain::push
273d73c 
Changes log messages a little, not sure if it affects readability too
much.

Old:
```
2022-03-11T17:25:45.637897Z DEBUG push                 | Accepted block #9.0:MI:df4a6595d1 with 0 transactions (extend)
2022-03-11T17:25:45.660765Z DEBUG push                 | Accepted block #10.0:MI:be38f68765 with 0 transactions (extend)
2022-03-11T17:25:45.687445Z DEBUG push                 | Accepted block #11.0:MI:2600b77a25 with 0 transactions (extend)

```

New:
```
2022-03-11T23:46:59.815181Z DEBUG push                 | Accepted block block=#9.0:MI:d846e5a8b4 num_transactions=0 kind="extend"
2022-03-11T23:46:59.863129Z DEBUG push                 | Accepted block block=#10.0:MI:1ea7fa1e4e num_transactions=0 kind="extend"
2022-03-11T23:46:59.899362Z DEBUG push                 | Accepted block block=#11.0:MI:a97db2b9df num_transactions=0 kind="extend"
```

Also, these haven't been tested for ingestion into Grafana yet, so maybe
we should hold off merging them.
hrxi added a commit that referenced this issue Mar 19, 2022
@hrxi
tracingify blockchain::push
0da82ee 
Changes log messages a little, not sure if it affects readability too
much.

Old:
```
2022-03-11T17:25:45.637897Z DEBUG push                 | Accepted block #9.0:MI:df4a6595d1 with 0 transactions (extend)
2022-03-11T17:25:45.660765Z DEBUG push                 | Accepted block #10.0:MI:be38f68765 with 0 transactions (extend)
2022-03-11T17:25:45.687445Z DEBUG push                 | Accepted block #11.0:MI:2600b77a25 with 0 transactions (extend)

```

New:
```
2022-03-11T23:46:59.815181Z DEBUG push                 | Accepted block block=#9.0:MI:d846e5a8b4 num_transactions=0 kind="extend"
2022-03-11T23:46:59.863129Z DEBUG push                 | Accepted block block=#10.0:MI:1ea7fa1e4e num_transactions=0 kind="extend"
2022-03-11T23:46:59.899362Z DEBUG push                 | Accepted block block=#11.0:MI:a97db2b9df num_transactions=0 kind="extend"
```

Also, these haven't been tested for ingestion into Grafana yet, so maybe
we should hold off merging them.
hrxi added a commit that referenced this issue Mar 22, 2022
@hrxi
tracingify blockchain::push
6f8aa4d 
Changes log messages a little, not sure if it affects readability too
much.

Old:
```
2022-03-11T17:25:45.637897Z DEBUG push                 | Accepted block #9.0:MI:df4a6595d1 with 0 transactions (extend)
2022-03-11T17:25:45.660765Z DEBUG push                 | Accepted block #10.0:MI:be38f68765 with 0 transactions (extend)
2022-03-11T17:25:45.687445Z DEBUG push                 | Accepted block #11.0:MI:2600b77a25 with 0 transactions (extend)

```

New:
```
2022-03-11T23:46:59.815181Z DEBUG push                 | Accepted block block=#9.0:MI:d846e5a8b4 num_transactions=0 kind="extend"
2022-03-11T23:46:59.863129Z DEBUG push                 | Accepted block block=#10.0:MI:1ea7fa1e4e num_transactions=0 kind="extend"
2022-03-11T23:46:59.899362Z DEBUG push                 | Accepted block block=#11.0:MI:a97db2b9df num_transactions=0 kind="extend"
```

Also, these haven't been tested for ingestion into Grafana yet, so maybe
we should hold off merging them.
styppo pushed a commit that referenced this issue Mar 25, 2022
@hrxi @styppo
tracingify blockchain::push
4aaf4cd 
Changes log messages a little, not sure if it affects readability too
much.

Old:
```
2022-03-11T17:25:45.637897Z DEBUG push                 | Accepted block #9.0:MI:df4a6595d1 with 0 transactions (extend)
2022-03-11T17:25:45.660765Z DEBUG push                 | Accepted block #10.0:MI:be38f68765 with 0 transactions (extend)
2022-03-11T17:25:45.687445Z DEBUG push                 | Accepted block #11.0:MI:2600b77a25 with 0 transactions (extend)

```

New:
```
2022-03-11T23:46:59.815181Z DEBUG push                 | Accepted block block=#9.0:MI:d846e5a8b4 num_transactions=0 kind="extend"
2022-03-11T23:46:59.863129Z DEBUG push                 | Accepted block block=#10.0:MI:1ea7fa1e4e num_transactions=0 kind="extend"
2022-03-11T23:46:59.899362Z DEBUG push                 | Accepted block block=#11.0:MI:a97db2b9df num_transactions=0 kind="extend"
```

Also, these haven't been tested for ingestion into Grafana yet, so maybe
we should hold off merging them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@paberr paberr

Labels
enhancement New feature or request
Projects
None yet
Milestone
Albatross Protocol
Development

No branches or pull requests
2 participants
@jgraef @paberr