Big claims that you are going to beat $BTC and $ETH. Although the project has some solid fundamentals, I'm not sure if it will get the project as big as BTC. I think it will be on the top 10 though.
When is the estimated release on this one?
Q4 2018 |
|
|
|
So 1.6 testnet launched, and we already have code for 1.6.1 (it is needed to review it carefully, and then test and merge it).
From big conceptual parts of the final design not implemented yet:
- PoW: we're in the process of working on the whitepaper and the corresponding code
- fee modes: almost finalized, will be in 1.7
- voting system: nothing big and hard, but a lot of work is needed to get details properly done.
On the transactional language, costing remains and some new functions.
https://twitter.com/ergoplatformorg/status/1040702596460281857 |
|
|
|
Next testnet, 1.6, will be launched within next few days. Every functionality is ready and now under merging.
New features:
- threshold signatures, minor updates to transactional language
- wallet API
- new block section to store auxiliary block data, the extension section
- networking layer improvements and various bugfixes
Also, we're considering a PoW scheme now. It seems conceptually it is more or less done. The PoW scheme would be ASIC-resistant (at least, more than ZCash's) and also non-outsourceable (no pools, at least as we know them). We're working on parametrization at the moment.
https://twitter.com/ergoplatformorg/status/1038166420755017728 |
|
|
|
What about plans switching from CPU to GPU mining? Will this be done before mainnet release or that switch will occur in some point in future time? What about asics and its possible effect on mining algo, already have solution? Anyway guys good luck! I'm ready to support mainnet with some GPU miners  PoW will be finalized near the testnet end and it will be based on own research on proof-of-data-possession as a PoW scheme https://arxiv.org/pdf/1603.07926.pdf and fight with pooling (i.e. outsourceability, the initial idea is here https://github.com/ergoplatform/ergo/issues/218). First, there will be a new version with initial wallet prototype, threshold signatures, next there will be new versions with fee model, voting, system reconfiguration and next PoW so it will take some time to see more details but GPU mining should be there from the start of the mainnet. Good. No problem to set miners in different locations and make them work separately to achieve better decentralization and network protection from possible mining power consolidation. But what about luck factor? As number of possible endpoints/nounce's/miners increase and possible maximum setting of GPU's per rig is lets say 13 then at some point in time GPU miners with less GPU-s are probably much less lucky than with higher "hashpower", or there will be something similar to Waves FairPOS and eventually even small miners will get their chance proportionally to get a block let#s say within 50k of blocks (even if only 1) - that approach will definitely help increase decentralization by "small" miners' participation. You can follow progress through existing pull requests https://github.com/ergoplatform/ergo/pull/407/commits/fe034c84ea03b46cc51f9d15d3e9b0c361cba18chttps://github.com/ergoplatform/ergo/pull/407/commits/ab8259fca5a8beb59925249ae5269a881aed9de9#diff-0e9a50b725ab1750ec188eac6c627857 |
|
|
|
How to convert Ergo tokens on waves platform to native tokens of Ergo?
Here is the latest info on it: 1.53 is ready and will be released this week. It contains significant improvements in bootstrapping and networking layer efficiency.
Initial wallet prototype is ready, code is under review.
Maybe we will rollout new testnets, say, bi-weekly, as it is hard to manage a huge codebase update properly. So, instead of a single enormous Testnet2 release, we'll roll-out few updates (fee model, system reconfiguration, PoW finalization).
On EFYT <-> ERGO exchange:
1. Before the mainnet launch, we'll send EFYTD (EFYT alternative for data chain).
2. Waves <-> Ergo gateway will exist. Thus Ergo token will exist on top of Waves as well.
3. With money got via founders rewards, the Foundation will create orders on Waves exchange, to buy EFYT for ERGO, the price is 1.00
|
|
|
|
What about plans switching from CPU to GPU mining? Will this be done before mainnet release or that switch will occur in some point in future time? What about asics and its possible effect on mining algo, already have solution? Anyway guys good luck! I'm ready to support mainnet with some GPU miners PoW will be finalized near the testnet end and it will be based on own research on proof-of-data-possession as a PoW scheme https://arxiv.org/pdf/1603.07926.pdf and fight with pooling (i.e. outsourceability, the initial idea is here https://github.com/ergoplatform/ergo/issues/218). First, there will be a new version with initial wallet prototype, threshold signatures, next there will be new versions with fee model, voting, system reconfiguration and next PoW so it will take some time to see more details but GPU mining should be there from the start of the mainnet. |
|
|
|
Next testnet will be named 1.6 and planned to be released in ~10 days.
New features:
- threshold signatures (preserving zero-knowledge, thus from k-out-of-n signature it could not be concluded which k signers were real)
- initial prototype wallet API implementation (we are going to outsource UI implementation immediately after the release)
- a new block section, which will in follow-up releases contain e.g. protocol changes voting information
- stricter block validation according to the specification
- a lot of small improvements
https://twitter.com/ergoplatformorg/status/1033448169160552448 |
|
|
|
So apparently what has been written so far, ERGO will be officially released this week and the starting price will be $1 or 1 WAVES on par with it? Blockchain technology is fantastic and always rewarding to find new projects, although some have little ability to put their proposals into practice, I hope it will be different with ERGO!
What has been written is, hopefully, real Bitcoin 2.0 mainnet will launch in Q4, there will be two chains because, with different parameters and built-in sidechains, Ergo is good for data-intensive applications. |
|
|
|
1.53 is ready and will be released this week. It contains significant improvements in bootstrapping and networking layer efficiency.
Initial wallet prototype is ready, code is under review.
Maybe we will rollout new testnets, say, bi-weekly, as it is hard to manage a huge codebase update properly. So, instead of a single enormous Testnet2 release, we'll roll-out few updates (fee model, system reconfiguration, PoW finalization).
On EFYT <-> ERGO exchange:
1. Before the mainnet launch, we'll send EFYTD (EFYT alternative for data chain).
2. Waves <-> Ergo gateway will exist. Thus Ergo token will exist on top of Waves as well.
3. With money got via founders rewards, the Foundation will create orders on Waves exchange, to buy EFYT for ERGO, the price is 1.00
https://twitter.com/ergoplatformorg/status/1029766801612255232is there still going to be a 1 + 1 swap, or will it just be EFYT for ERGO? Yes, 1+1, for 1 EFYT you will get 1 cash and 1 data |
|
|
|
1.53 is ready and will be released this week. It contains significant improvements in bootstrapping and networking layer efficiency.
Initial wallet prototype is ready, code is under review.
Maybe we will rollout new testnets, say, bi-weekly, as it is hard to manage a huge codebase update properly. So, instead of a single enormous Testnet2 release, we'll roll-out few updates (fee model, system reconfiguration, PoW finalization).
On EFYT <-> ERGO exchange:
1. Before the mainnet launch, we'll send EFYTD (EFYT alternative for data chain).
2. Waves <-> Ergo gateway will exist. Thus Ergo token will exist on top of Waves as well.
3. With money got via founders rewards, the Foundation will create orders on Waves exchange, to buy EFYT for ERGO, the price is 1.00
https://twitter.com/ergoplatformorg/status/1029766801612255232 |
|
|
|
Summer is hot! - Transaction and block validation rules has been added to the specification (Yellow Paper)
- We consider names for our transactional languages. Low-level language will be called ErgoTree (as it is a typed abstract syntax tree, to be written into the blockchain in a serialized form).
Higher-level language is called ErgoScript, an example in this language:
guard CrowdFunding(timeout: Int, minToRaise: Int,
backerPubKey: Sigma, projectPubKey: Sigma) {
let c1 = HEIGHT >= timeout && backerPubKey
let c2 = allOf(Array(
HEIGHT < timeout,
projectPubKey,
OUTPUTS.exists(fun (out: Box) = {
out.value >= minToRaise && out.propositionBytes == projectPubKey.propBytes
})
))
c1 || c2
}
- EFYT <-> Ergo transfer details will be announced next Fri hopefully.
- We have a lot of material to be included into the next minor release (1.53): various improvements to the network layer and synchronization (https://github.com/ScorexFoundation/Scorex/pull/280 and https://github.com/ergoplatform/ergo/pull/386), and first stage of the wallet implementation (https://github.com/ergoplatform/ergo/pull/362). Both sets of features are now under review & testing. Probably 1.53 will be out next week with one set of new features or another, or both.
|
|
|
|
|
Show Posts
