click here if you want to see your banner on this site

Author Topic: [ANN] Ethereum: Welcome to the Beginning  (Read 99941 times)

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #270 on: May 20, 2020, 05:53:56 PM »
Ethereum Released ETH2 Specifications Version 0.11.3

Details Here:
« Last Edit: July 17, 2020, 12:52:09 PM by cryptoking »
Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

cyberG

  • Novice
  • *
  • Posts: 11
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #271 on: May 23, 2020, 09:54:00 PM »
The whole community has long been waiting for the launch of the Ethereum 2.0 mаinnet. I think this can greatly change the cryptocurrency market.

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #272 on: May 28, 2020, 04:32:24 PM »
New Mining Pool for Ethereum  - 0%fee. DDos protection

Minimum Pay out 0.05 Eth

Website: https://ethpool.coinfly.cc/
Connection settings:

stratum://<WALLET>@core.coinfly.cc:3072/<NAME>
Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #273 on: July 04, 2020, 05:59:20 AM »
Ethereum 2 Devlopment Update No.53 - Altona Testnet Launched


https://eth2stats.io supporting the new Altona testnet for eth2
There’s a new testnet in town, and with incredible results so far since its launch. Altona is a coordinated, multi-client testnet for eth2 phase 0, different than Prysmatic Labs’ Onyx testnet as it had 4 eth2 clients (Prysm, Lighthouse, Teku, and Nimbus) at genesis instead of just Prysm! Altona was a coordinated effort organized by Afri Schoedon and the Ethereum Foundation as a smaller multiclient testnet. The goal of Altona is to ensure some degree of stability before there is an official announcement of a large scale, “official” multiclient testnet for eth2. You can connect Prysm to Altona using the ` — altona` flag when running your beacon node and validator. Additionally, you can monitor the Altona network on https://altona.beaconcha.in created by Bitfly, showing some awesome graphs regarding its liveness so far. You can monitor some of the nodes in the network by using https://eth2stats.io/altona-testnet. Keep posted for the big announcement of a large-scale multi-client testnet within the coming weeks!

Read Full Article Here:
« Last Edit: July 17, 2020, 12:49:10 PM by cryptoking »
Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #274 on: July 04, 2020, 08:10:24 AM »
 xMOON Exchange is Live ⚖️Liquidity between Reddit's MOON tokens and the Ethereum mainnet through xDAI!
https://youtu.be/_ikHSyThDiA
Bridge MOONs to xMOONs to xDAI to DAI to ETH!
Built with 🏗Scaffold-eth: https://github.com/austintgriffith/sc...
https://xmoon.exchange
Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #275 on: July 17, 2020, 12:47:32 PM »
Ethereum Released remix desktop version 1.0.7

RemixD bug fix support

Source Code:
« Last Edit: July 18, 2020, 10:08:44 AM by cryptoking »
Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #276 on: July 20, 2020, 07:33:52 PM »
Ethereum Released geth Version 1.9.17 - Mount Milgrom

Geth v1.9.17 is a small maintenance release (trying to get back onto the biweekly schedule), though it does pack a few punches as well!

Enable historical garbage collection for light clients (#19570).
Apply --rpc.txfeecap to a few missed endpoints (#21231).
Drastically reduce allocations in the transaction pool (#21328).
Drastically reduce allocations on certain EVM opcodes (#21222).
Raise the default gas limit in --dev mode to 12 million (#21323).
Fix ethstats reconnect issue and fix constant Görli drops (#21347).
Fix gas estimation if balance / price overflown uint64 (#21346).
For a full rundown of the changes please consult the Geth 1.9.17 release milestone
Download:
Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #277 on: July 21, 2020, 05:50:25 PM »
Ethereum Announcing eth2 attacknets -- beta-0

This repository tracks public "attacknets" maintained by the EF.

beta-0
This program is currently in "beta-0" and all details are subject to change.

Active beta-0 attacknets:

lighthouse-attack-0
prysm-attack-0
Each network has a possible reward of $5k! Click specific attacknet links above for more details about configuration, rules, and rewards.

lighthouse-attack-0 and prysm-attack-0 are real networks, ready for you to attack, but they are beta in the sense that it's our first go at this -- we expect to learn and iterate quickly. These networks are also very small (only 4 nodes each!) so should be pretty easy to take down.

Deposits are not enabled in beta-0 testnets so you'll have to try non-validator based attacks for this run.

See README for each net for network configuration and rules/rewards.

Attacknet directory structure

Each attacknet is contained within it's own sub-directory within ./attacknets.

Within the attacknet directory, a README.md is provided with human readable, high-level configuration as well as the rules and any rewards associated with the attacknet.

The attacknet directory also provides configuration files that might be useful in running clients and connecting to the network.

prysm_config.yaml -- is a YAML configuration file that can be ingested by the Prysm client via the --chain-config-file commandline flag
lighthouse-testnet -- is the testnet configuration directory that can be ingested by the Lighthouse client via the --testnet-dir commandline flag
General rules
In addition to attacknet specific rules provided for in each attacknet. The following are the general rules for the program. [Note: This program is in beta-0 and all rules are subject to change without prior notice].

The Ethereum Foundation is solely responsible for judging the attack and deciding on rewards
Awards can be redeemed in ETH or DAI
Eth2 client teams are eligible to participate only on attacknets that do not contain their specific client
How to report
All claims on attacknet rewards must be reported as an issue in this repo.

Please follow this reporting structure to aid in prompt review:

Prefix the name of the Issue/PR with "[{ATTACK_NET_NAME} Reward]"

Use the following structure for the body of the Issue/PR

Description: High-level description of the attack [1 sentence]

Attack scenario: More detailed description of the attack scenario and how it was carried out [1 to 3 sentences]

Impact: Describe the effect had on the attacknet [1 to 2 sentences]

Details: Very specific details about the attack including the specific slots/epochs where it can be observed

Privacy
The Ethereum Foundation is not responsible for any private information that might be leaked as a result of this program.

In the event that the reporting of an attack does leak private information (e.g. logs from a testnet containing IP addresses), we ask that you withhold any such information in the public report. Instead, please note that there are additional accompanying resources to be shared, and the attacknet evaluators will be in touch.

Important legal information
We give explicit permission to attack these attacknets over the internet.

This attacknet program is an experimental and discretionary rewards program for our active Ethereum community to encourage and reward those who are helping to improve the platform. It is not a competition. You should know that we can cancel the program at any time, and rewards are at the sole discretion of Ethereum Foundation. In addition, we are not able to issue rewards to individuals who are on sanctions lists or who are in countries on sanctions lists (e.g. North Korea, Iran, etc). You are responsible for all taxes. All rewards are subject to applicable law. Finally, your testing must not violate any law or compromise any data that is not yours.

Source Code:
Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #278 on: July 23, 2020, 01:38:31 PM »
Ethereum Released Solidity version 0.6.12
This release of Solidity adds more flexibility to inheriting NatSpec and improves the handling of the stack.

Language Features:

NatSpec: Implement tag @inheritdoc to copy documentation from a specific base contract.
Wasm backend: Add i32.ctz, i64.ctz, i32.popcnt, and i64.popcnt.
Compiler Features:

Code Generator: Avoid double cleanup when copying to memory.
Code Generator: Evaluate keccak256 of string literals at compile-time.
Optimizer: Add rule to remove shifts inside the byte opcode.
Peephole Optimizer: Add rule to remove swap after dup.
Peephole Optimizer: Remove unnecessary masking of tags.
Yul EVM Code Transform: Free stack slots directly after visiting the right-hand-side of variable declarations instead of at the end of the statement only.
Bugfixes:

SMTChecker: Fix error in events with indices of type static array.
SMTChecker: Fix internal error in sequential storage array pushes (push().push()).
SMTChecker: Fix internal error when using bitwise operators on fixed bytes type.
SMTChecker: Fix internal error when using compound bitwise operator assignments on array indices inside branches.
Type Checker: Fix internal compiler error related to oversized types.
Type Checker: Fix overload resolution in combination with {value: ...}.
Build System

Update internal dependency of jsoncpp to 1.9.3.
We especially thank all the contributors that made this release possible:

a3d4, Alex Beregszaszi, Alexander Arlt, Bhargava Shastry, Daniel Kirchner, Djordje Mijovic, Kamil Śliwak, Leonardo Alt, Mathias Baumann, Sachin Grover, Tiny熊,

If you want to perform a source build, please only use solidity_0.6.12.tar.gz and not the zip provided by github directly.
Source Code :

Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #279 on: July 27, 2020, 06:24:19 PM »
Ethereum Released Geth Version 1.9.18 - Illium Elite

Geth v1.9.18 is a bugfix release, fixing an occasional fast sync hang in the throttling mechanism (among other improvements):

Memory allocation micro-optimizations to improve raw EVM number crunching by 5% (#21336).
Fix a regression that made previously persisted --dev chains unable to load back up (#21352).
Support configurable developer account (and passphrase) in --dev mode (#21301).
Fix downloader throttling that degraded sync and occasionally locked it up (#21263).
Fix local gomobile building and fix iOS framework builds (#21361, #21362).
Fix stale transaction eviction bug, stabilizing pool churn (#21300).
For a full rundown of the changes please consult the Geth 1.9.18 release milestone

Update Here:
Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #280 on: July 30, 2020, 05:03:28 PM »
Ethereum.org Translation Program: Milestone and Updates

Today we’re excited to celebrate a huge milestone - Ethereum.org now supports 30 languages! 🎉🎉🎉

Since we launched the Website Translation Program seven months ago, we’ve seen how decentralized collaboration can result in a significant impact in the ecosystem, benefiting hundreds of thousands of community members around the world.

As of today, 467 volunteers from 52 language groups have helped make ethereum.org accessible to non-English speaking communities in their mother tongues.

Thanks to these volunteers, 16% of all traffic to ethereum.org is now directed towards non-English versions of the site. Over time, this number has grown significantly.



Two months ago, the website team set a Q2 goal of adding six more languages to the 24 that existed at the time. We’re honored to have accomplished this milestone by integrating the languages listed below:

Norwegian v.1.1
Chinese Traditional v.1.1
Malayam v.1.1
Ukrainian v1.1
Lithuanian v.1.0
Portuguese v.1.0
Italian v1.0 -> v.1.1 (updated)


Q3: Upgrading existing languages to site v1.1
In Q3, we’ve set a new goal of upgrading all languages to the latest version of ethereum.org, v1.1, which reflects to current content on the site. Currently, we have 16 languages waiting to be upgraded to v.1.1, which builds on previous content. Moreover, there will be more content updated in Q3/Q4. The languages we’re focused on now are listed below, paired with a percentage to show the progress of the translation:

Portuguese Brazilian (83%)
Lithuanian (79%)
Dutch (69%)
Spanish (69%)
Russian (59%)
Portuguese (56%)
Igbo (52%)
Japanese (48%)
Korean (48%)
Greek (48%)
Polish (48%)
Slovenian (48%)
Czech (48%)
Persian (44%)
Thai (38%)
Vietnamese (19%)
Interested in contributing to our translation effort? We encourage you to work towards the latest version (v 1.1). If you’ve already started working on a lower version, that’s fine too! We’ll add any completed version to the website.

Again, we wish to have your continuous support in our Q3 goal. Of course, support with unlisted languages is always welcome.

How to get involved?

Read full article here:




Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #281 on: August 15, 2020, 08:55:38 AM »
Ethereum Released Remix-desktop Version 1.0.8

Merge pull request #18 from ethereum/yann300-patch-3

use remix-project origin

Download Link:

Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #282 on: August 18, 2020, 06:00:15 PM »
Lighthouse Update #28

Update Summary
It has been all hands on deck since the last update, and a lot has been happening. In quick dot point form, here are the highlights:

Medalla - a large, public multiclient testnet was launched
v0.2.0 of Lighthouse was released (coinciding with the Medalla testnet)
Rust-gossipsub 1.1 is ready for testing
Key-management improvements and EF launchpad integration
Advanced peer management and peer scoring
Significant work on stability, performance and testnet improvements
The Medalla Testnet
Since the last update the Medalla public multiclient testnet was launched. It has over 20,000 validators and at least 5 different client implementations running.

It's launch had a rough start with a number of large stakers being offline during genesis. This lead to a lower participation rate than expected. Many of these Stakers soon joined and the testnet achieved finality and was running relatively smoothly. We've had a chance to do a lot of client interoperability testing and performance tweaking over the past few weeks on this testnet.

Attestation Inclusion
One of the main concerns we witnessed on this testnet, is rate of attestation inclusions. Each validator must produce an attestation each epoch. These get included in future blocks and, once included, the validator associated with the included attestation gets rewarded. Although on a Lighthouse-only network we see 100% attestation inclusion (all produced attestations get included in blocks) on Medalla some attestations were being missed (not included in a future block). This is not a straightforward problem to solve as the process is somewhat complicated, as I'll outline.

Each epoch, validators get shuffled into committees. Each validator of a committee must publish their attestations to a specific gossipsub subnet (related to their committee). Of all the validators in a committee a pseudo-random subset of validators (around 16) are required to collect all the attestations and aggregate them. These "aggregators" then publish the aggregate attestations onto a global "aggregate" gossipsub channel. This allows block proposers to subscribe only to the "aggregate" channel and hence only see the grouped attestations of each committee rather than all individual attestations that occur in the gossipsub subnets. A block proposer should then select the aggregate attestations it deems will make it the most profit and include them into its proposed block.

Now there are many points of failure that can occur that could prevent a validators attestation from being included into a block. Firstly, a client needs to find other peers that are also subscribed to the required subnet. If no such peers exist, the published attestation cannot propagate and will not reach any of the proceeding steps to be included into a block. If a client has found sufficient peers, it is then up to the "aggregators" of the subnet to firstly receive the attestation from the gosispsub subnet and aggregate it. The aggregators could be different client implementations and may not agree on the attestations they have received on the subnet. Timing is also somewhat important between clients here to ensure the attestation is published before the aggregator aggregates it. The aggregator must then publish on the global "aggregate" channel. A block producer (within an epoch of publishing the attestations) must see the aggregate attestation and decide to include it in it's block. These last two steps could be done by any node on the network and the challenge lies in getting all client implementations to work together harmoniously throughout the entire process.

It is our (and I'm sure other client implementer team's) goal to achieve 100% attestation inclusion rate for our all validators. But this will be a cross-client debugging and engineering effort which will likely involve a number of iterations and likely continuously improve as clients progress.

In the past week we've already seen large gains from various teams in this regard. We've managed to increase our inclusion rate on low-performance nodes through reduced load in processing in other parts of the client.

The Medalla Hiccup
On the 14th of August there was an issue with Cloudfare's Roughtime server which caused all Prysm nodes to exhibit a clock skew negating all their attestations and blocks. This effectively removed all Prysm nodes from the chain, which was around 70% of the network (a detailed account can be found here). The chain lost finality, due to a large number of validators being effectively offline. This is one of the primary reasons for a multi-client chain and client diversity, such that in these events, the chain continues to run if a single implementation is taken offline.

Despite this being a catastrophic failure (having such a large portion of the network simultaneously taken offline) this has been a very fruitful event for implementers to see how their clients handle such an event.

For us, there we saw an influx of invalid blocks and attestations flooding the gossipsub channels which lead to some processing bottlenecks in Lighthouse. We've seen bizarre memory consumption usage and also some interesting syncing edge cases due to the various forks from the Prysm clients. This has allowed us to identify these hot-spots which occur in adverse conditions and correct them, ultimately stabilising our client further allowing it to handle such extreme conditions going forward.

We are in the process of completing many of these updates, but imagine we will have a significantly more robust and performant client once completed.

Gossipsub 1.1
We have completed our first version of rust-gossipsub 1.1. We have integrated it into Lighthouse and ran it on the Medalla testnet successfully. Gossipsub 1.1 is a more secure version of its predecessor which primarily incorporates a scoring mechanism for peers which is designed to mitigate a number of attacks and maintain a healthy mesh-network for message propagation.

We are in the early stages of this development however. Our plan over the next few weeks is to perform some more internal testing, attempt to do some large scale simulations and design and document a set of scoring parameters that should be applicable to the Ethereum 2.0 gossipsub channels. The end result should be a more resilient network of Ethereum 2.0 nodes for message propagation.

Stability, Performance and Peer Management
The events that have taken place on the Medalla testnet have helped us identify some key areas of improvement in Lighthouse. We have been profiling the client, searching for processing bottlenecks, excessive memory usage and overall client stability.

We have seen performance degradation when decoding/processing large amounts of blocks/attestations. These were originally being processed on the core-executor (a threadpool managing basic client operation) which meant that core parts of Lighthouse would be delayed whilst block/attestation processing was underway. We have been identifying heavy processes and lifting these off the core-executor into their own tasks such that core Lighthouse components continue to run as expected, even in high-load conditions. This has shown to enhance the attestation inclusion rate of some Lighthouse users.

We have also identified areas of Lighthouse that allocate more memory than required. We are actively hunting and chasing for memory leaks and unnecessary allocations as we've observed some Lighthouse nodes spike in memory usage during the Medalla hiccup.

There is also a known deadlock in the client which occurs more regularly on nodes with low CPU counts. We are actively hunting this lock (and have been for a while) and are narrowing it down. We should have this resolved soon.

Finally, since our last update, we have enhanced our peer management system. Additionally to the scoring, we actively track current and past-known peers. When a Lighthouse node is run with default parameters, typically it will connect to 50 peers and oscillate somewhere between 50 and 55. Lighthouse by default, targets 50 peers to connect to and has a 10% threshold which allows additional incoming connections. This allows new peers to easily join a network (we don't reject them if we've already reached 50 peers) and allows us to cycle our peer-pool with new peers which can potentially remove other non-performant or malicious peers.

If your Lighthouse node is fluctuating between 50 and 55 peers, this is the desired behaviour and it is running as expected.

Still to come
The Medalla hiccup has brought with it a number of improvements to the Lighthouse code base. We are still working on some of these and we expect a series of updates to the client to occur within the next week to handle all the issues we've witnessed over the last few days.

We will be continuously working (with other client teams) to increase the attestation inclusion rate. This will be a long-running endeavour and hopefully we can achieve 100% inclusion rate for all our validators soon.

Lighthouse will be completing its first audit around October (this will be primarily focused on the networking components) and will undergo it's second audit around the same time.

We will be working to have everything complete and working smoothly for these audits.

Author:
Dr Adrian Manning
Physicist turned blockchain scientist. An avid fan of the Ethereum community and the projects being built in the space. @agemanning on Github & Twitter.

Source:https://lighthouse.sigmaprime.io/update-28.html
« Last Edit: August 18, 2020, 06:03:14 PM by cryptoking »
Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

cryptoking

  • Full Member
  • ***
  • Posts: 133
  • Karma: +0/-0
    • View Profile
Re: [ANN] Ethereum: Welcome to the Beginning
« Reply #283 on: October 31, 2020, 03:47:32 PM »
Ethereum pre release-0.8.0

Re-structure list of breaking changes.

Source Code:
Cryptoking
BTC: 16xketUq2PjHuEnFFpWCxaymrozwMLMjuo
ETH: 0xE6DBA365b77F2d8bA983a975Fa59c26acdb7a062

 

Bitcoin Garden 2013-2020, All rights reserved | Privacy Policy | DMCA | About Bitcoin Garden | Support & Services