annotated-spec
teku
annotated-spec | teku | |
---|---|---|
44 | 50 | |
312 | 630 | |
0.0% | 1.0% | |
0.0 | 9.8 | |
3 months ago | 6 days ago | |
Java | ||
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
annotated-spec
- Daily General Discussion - February 17, 2023
-
Can't the Sync Committee be cheaply bribed, and therefor serves no real purpose for security?
My current understanding: The Sync Committee selects 512 validators to continually sign off on block header. Any block headers that get >2/3 are "valid"1, such that Light Clients using this header for verification can trust it.
-
Ethereum Mainnet Merge Announcement
https://github.com/ethereum/annotated-spec/blob/master/phase...
Here we have slashing fields in the block body where you insert your proofs of slashable offense. There are functions with a “slash” in the name that describes precise state transition.
The hard part of slashing is finding these proofs because you have to do more work than necessary to detect slashing and produce proofs - that’s what this software does. It’s more expensive to run a slasher but you need only one and it does not matter who runs it, anyone can run it. The link that you sent says that this slasher broadcasts proofs by default - that way anyone can include it.
-
Explaining Ethereum's consensus mechanism after The Merge
According to Eth docs:
> One validator is randomly selected to be a block proposer in every slot. This validator is responsible for creating a new block and sending it out to other nodes on the network. Also in every slot, a committee of validators is randomly chosen, whose votes are used to determine the validity of the block being proposed.
The annotated code for this can be found in [2].
[1] https://github.com/ethereum/annotated-spec/blob/master/phase...
[2] https://notes.ethereum.org/@vbuterin/Sys3GLJbD#Misc
-
Daily staking income was irregularly high, anyone knows why?
Here's some more info on Sync committees if you are interested. https://github.com/ethereum/annotated-spec/blob/master/altair/sync-protocol.md
- Daily General Discussion - February 20, 2022
-
My First Impressions of Web3
The crux of the article is that the front-ends are all routing calls through centralized APIs to get their message included on the blockchain. Infura and Alchemy don't do much. They just pass a JSON-RPC message to an Ethereum node running on their servers. There is some additional indexing services they provide, but there are many open, decentralized alternatives for that such as TheGraph Protocol. And it's not unfeasible for an application to run its own Postgres instance to index data from the ETH blockchain.
As for full-fat clients on normal mobile devices, the main issue is the data requirements. Running a full node can take hundreds of gigabytes. It is possible on light hardware. People are running Beacon chain nodes on Raspberry Pis. But you do need the storage and that tends to be scarce on mobile.
Meanwhile, the Ethereum core devs are aware of this issue and are actively working towards it. They shipped the Altair hard fork this year that has adds sync committees which make it possible to do without needing the whole chain history (using merkle trees): https://github.com/ethereum/annotated-spec/blob/master/altai...
The light client to follow from those improvements is forthcoming:
-
ETH2.0 withdrawal roadmap post merge
It's not about validators going offline, it's about the validator set changing. To quote the annotated specs
-
Proof of stake is a scam and the people promoting it are scammers
Even a relatively light reading of the Annotated Spec[1] for Eth2 and/or the Eth Org's Proof of Stake FAQs[2] suggests the designers (and independent implementer-teams who gave feedback to designers... lather, rinse, repeat) understand it's important to consider the overall system "outside of the comfort zone".
[1] https://github.com/ethereum/annotated-spec/blob/master/phase...
[2] https://eth.wiki/en/concepts/proof-of-stake-faqs
-
Help understanding staking factors
Alpha leak: I am currently finishing up a full revision of my annotated specification for Altair, and plan to get it published in a couple of weeks. Meanwhile Vitalik's annotated spec has some info on how base rewards work under Altair.
teku
- Teku Release 23.5.0 - recommended upgrade
- Daily General Discussion - May 12, 2023
-
Besu 23.1.2 => vert.x-worker-thread-0 | WARN | WithdrawalsValidator$AllowedWithdrawals | withdrawals must not be null when Withdrawals are activated
You can try to upgrade it to the latest version https://github.com/ConsenSys/teku/releases/tag/23.3.1 and see if it fixes your issue, but if that doesn't work then you'll probably need to resync your clients.
-
Daily General Discussion - March 29, 2023
I discovered a bug in Lodestar that causes it to fail to preserve queued BLS-to-execution messages on shutdown.
- Teku v23.3.0 released
-
Is there any service that sends notifications when I have to update by validator software (i.e. consensus (e.g. lighthouse) and execution (e.g. geth)?
Teku: https://github.com/ConsenSys/teku/releases
-
Gnosis Merge-ready release clients
Consensus Layer client ✅ Teku v22.11.0: https://github.com/ConsenSys/teku/releases/tag/22.11.0 ✅ Lodestar v1.2.2: https://github.com/ChainSafe/lodestar/releases/tag/v1.2.2 🟡 Lighthouse: coming soon 🟡 Nimbus: coming soon ❌ Prysm: advised to switch to other clients
-
Anyone else encounter the failure to register validator with builder network error?
create an issue here? https://github.com/ConsenSys/teku
-
is it common to miss an attestation once or twice a day?
It's all coming from besu's slow processing of blocks https://github.com/ConsenSys/teku/issues/6205
-
Daily General Discussion - September 16, 2022
Teku v22.9.1-RC1 released today
What are some alternatives?
ethmerge.com-content - Markdown formatted content for the ethmerge.com website.
prysm - Go implementation of Ethereum proof of stake
consensus-specs - Ethereum Proof-of-Stake Consensus Specifications
nimbus-eth2 - Nim implementation of the Ethereum Beacon Chain
pm - Project Management: Meeting notes and agenda items
Log4jAttackSurface
ens - Implementations for ENS core functionality: The registry, registrars, and public resolvers.
staking-deposit-cli - Secure key generation for deposits
crypto-fees - Website for comparing total daily fees of various blockchain protocols.
airdrop-addresses
EIPs - The Ethereum Improvement Proposal repository
solidity - Solidity, the Smart Contract Programming Language