kakarot
Kakarot is a zkEVM written in Cairo, leveraging the STARK proof system. (by kkrt-labs)
ConsensusLayerWithdrawalProtection
By benjaminchodroff
kakarot | ConsensusLayerWithdrawalProtection | |
---|---|---|
3 | 18 | |
865 | 35 | |
2.0% | - | |
9.5 | 6.8 | |
7 days ago | 12 months ago | |
Cairo | Go | |
MIT License | The Unlicense |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
kakarot
Posts with mentions or reviews of kakarot.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-10.
-
StarNet is getting closer to full Ethereum virtual machine compatibility with the Kakarot test network
🖥 https://kakarot.org
-
[AMA] We are EF Research (Pt. 9: 11 January, 2023)
One totally different route we could take is eventually moving away from the EVM to some ZK-friendly EVM like Cairo. Existing EVM code would be replaced with execution of an EVM interpreter written in Cairo. This is all fairly long-term speculation at this point though.
- Welcome to Kakarot ZK-EVM
ConsensusLayerWithdrawalProtection
Posts with mentions or reviews of ConsensusLayerWithdrawalProtection.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-10.
-
I am struggling to establish the withdrawal address for my validator. Help is welcome!
I have been also reading also about EIP-4736 and Consensus Layer Withdrawal Protection, but apparently, they don't accept more submissions.
- What is from_bls_pubkey in change_operations.json?
-
Daily General Discussion - April 5, 2023
git clone https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection.git cd ConsensusLayerWithdrawalProtection
-
My eth validator has been down, can I withdraw without getting it running again?
I did basically the same on goerli network as i did not want to bother resync a validator node from scratch: 1. go here and get the offline preparation file: https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection 2. on a live ubuntu (from an usb stick) + ethdo and the offline preparation file, prepare the json file to sign the exit, instructions here: https://github.com/wealdtech/ethdo/blob/master/docs/changingwithdrawalcredentials.md 3. once shapella is live on main net, use the beaconcha.in endpoint to broadcast the json file ref: https://beaconcha.in/tools/broadcast
-
Daily General Discussion - March 27, 2023
There's some group trying to do this https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection
-
0x00 to 0x01
The easiest is using ethdo using the offline process. You don't have to run a node yourself, if you download the offline preparation file from here: https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection/tree/main (offline-preparation.json is just a big text file containing the ids, validator pubkeys, and withdraw pubkeys of all validators).
-
to all stakers/node operators: consider helping broadcast withdrawal address change requests submitted via CLPW by following these simple steps:
# Navigate to the folder containing the "ethdo" utility cd /path/to/ethdoFolder # Download the CLWP submissions: git clone https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection.git # Install jq (Example: apt install -y jq) and use it to combine all CLWP submissions together into a single change-operations.json file jq -s 'add' ConsensusLayerWithdrawalProtection/mainnet/*.json > change-operations.json # Run ethdo to connect to your beacon node (specify the valid host and port), allowing local insecure connections using HTTP, and it will broadcast all messages in the change-operations.json file. ./ethdo validator credentials set --connection http://YourNodeIP:5052 --allow-insecure-connections echo $?
- Withdrawal address generation
-
CLWP for validator withdrawal address due by 2/28
If you have an Ethereum validator, and have not stored your validator seed phrase securely offline, we would encourage you to consider using CLWP (EIP-4736) to set your withdrawal address. We will broadcast these submissions at the Capella hard fork. This may help you win against an attacker. We are accepting open submissions until 2/28. Over 750 validators have used CLWP. We are happy to help anyone who has questions. https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection
-
Reminder: monitor if someone is maliciously trying to broadcast your BLS address change before you do via CLWP
#!/bin/bash NOT_FOUND="Not Found" if [ $# -eq 0 ] then echo "You must provide at least one argument. \n Use with ./clwpCheck.sh ..." fi # Check cURL command if available (required), abort if does not exists type curl >/dev/null 2>&1 || { echo >&2 "Required curl but it's not installed. Aborting."; exit 1; } echo "🕵️ Checking the public CLWP list at https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection/tree/main/mainnet" for i in "$@"; do echo RESPONSE=`curl -s "https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection/commits/main/mainnet/"$i".json.atom"` if [ "$RESPONSE" == "$NOT_FOUND" ]; then echo "🟢 Validator $i not found in the broadcast list." else JSONRESPONSE=`curl -s "https://raw.githubusercontent.com/benjaminchodroff/ConsensusLayerWithdrawalProtection/main/mainnet/"$i".json"` startIndex=$(echo $JSONRESPONSE | grep -b -o 'to_execution_address' | cut -d: -f1) withdrawalAddress=${JSONRESPONSE:$startIndex+23:42} echo "🔴 Validator $i: Watch out, there is a request to change the withdrawal address to "$withdrawalAddress echo " If you didn't request this change, you should contact CLWP right away 👉 https://clwp.xyz/index.php/contact.html" echo " This signed message will be broadcast at Shangai 👉 https://raw.githubusercontent.com/benjaminchodroff/ConsensusLayerWithdrawalProtection/main/mainnet/"$i".json" fi done
What are some alternatives?
When comparing kakarot and ConsensusLayerWithdrawalProtection you can also consider the following projects:
fee-feed - Minimal fee data viewer
research
reth - Modular, contributor-friendly and blazing-fast implementation of the Ethereum protocol, in Rust
eth2-knowledge-base
starknet-erc721 - Learn how to deploy and customize an ERC721 token on StarkNet
docs.rocketpool.net - Rocket Pool Documentation & Guide Hub
awesome-cairo - Resources for Cairo 1.0 development.
starknet-cairo-101 - Learn how to read Cairo code
akula - Fastest Ethereum archive node ever built
ethereum-burn-stats - Website that showcases EIP-1559 Burn
kakarot vs fee-feed
ConsensusLayerWithdrawalProtection vs research
kakarot vs reth
ConsensusLayerWithdrawalProtection vs eth2-knowledge-base
kakarot vs starknet-erc721
ConsensusLayerWithdrawalProtection vs docs.rocketpool.net
kakarot vs awesome-cairo
ConsensusLayerWithdrawalProtection vs reth
kakarot vs starknet-cairo-101
kakarot vs research
kakarot vs akula
kakarot vs ethereum-burn-stats