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

Top issues before multi client testnet #4781

Closed
16 tasks done
terencechain opened this issue Feb 6, 2020 · 8 comments
Closed
16 tasks done

Top issues before multi client testnet #4781

terencechain opened this issue Feb 6, 2020 · 8 comments
Assignees
Labels
Priority: High High priority item Tracking Gotta Catch 'Em All

Comments

@terencechain
Copy link
Member

terencechain commented Feb 6, 2020

  • Attestation signature fails to verify for fork choice accounting Attestation Signature Does Not Verify #4773
  • Increasing # of users reporting OOM Initial Sync Cache State Leads to OOMs #4813
  • A lot of forking showed on the block tree visualizer. Concerning given it's a testnet with artificially short block time
  • Dynamic subscription of committee subnet
  • Attester should submit attestation right away if head slot == current slot
  • Discv5 Infra set up
  • Update BLS library to v0.10 and IETF standard Update Prysm to V0.10.1 #4804
  • Ensure local interop works, making it easier for clients to test running a chain from genesis with
    Prysm to ensure finality, participation, and heterogenous spread of validators across the clients
  • Add Support for Noise
  • Resolve profitability issues some validators are penalized while some are rewarded #4589
  • Update to spec v0.10.1
  • Update to spec v0.11
  • Remove keystore key manager
  • Add IPv6 support
  • A proper tool to migrate DB to be new state mgmt service compatible
  • Update to spec v0.11.1
@ghost
Copy link

ghost commented Feb 11, 2020

some validators are penalized while some are rewarded #4589

@handelaar2
Copy link

ipv6 support? (#3420)

@mcdee
Copy link
Contributor

mcdee commented Mar 19, 2020

Any thoughts about removing the keystore keymanager? Now seems a good a time as any to do so.

@prestonvanloon
Copy link
Member

Yes. Let's remove keystore manager

@tzapu
Copy link
Contributor

tzapu commented Mar 24, 2020

once this is done, will validators currently using the keystore manager just fail to start after a pull?
if so, would you consider adding a console message with migrations instructions? if you think it's worth it? (non issue if it will only take effect on the testnet restart i guess)

@nisdas
Copy link
Member

nisdas commented Mar 24, 2020

@tzapu it will only happen in our testnet restart, yeah that sounds like a good idea. We can link the instructions in a validator log to our docs, so that users who are not sure can still be able to use the new key manager

@tzapu
Copy link
Contributor

tzapu commented Mar 24, 2020

@nisdas if it s on testnet restart, then it's not gonna be so important, there will be a lot of other manual things to be done anywa... but the participate website should be updated :D

@rauljordan
Copy link
Contributor

Closing in favor of #5227

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High High priority item Tracking Gotta Catch 'Em All
Projects
None yet
Development

No branches or pull requests

7 participants