[PRE-ANN] Ergo Platform is coming, the AAA class of blockchains

[mxxxxxx]

Ergo Platform Testnet 1.9.1 released. Digest state type recovery and parameters parsing fixes. Correct mempool implementation. Testnet 2.0 in few weeks after code is reviewed and merged.

https://github.com/ergoplatform/ergo/releases/tag/v1.9.1

https://twitter.com/ergoplatformorg/status/1093090045601505280

[kushti]

How to deploy sigma smart-contract to Ergo testnet

https://github.com/ergoplatform/blog/blob/master/content/posts/Ergo_Script_How_To.md

[coinfiziert]

Thanks for the tutorial. I wanted to ask for this, but you were faster!

Do you have any plans for the going live? Any date?

[kushti]

Thanks for the tutorial. I wanted to ask for this, but you were faster!

Do you have any plans for the going live? Any date?

Thanks! Let me answer you along with providing some update.

2.0 will include almost all the features previously planned  as 2.x. Thus this testnet release will be pretty much like the mainnet. The biggest question to solve after 2.0 testnet is about
soft-forkability, i.e. decide rules how the protocol can evolve in the mainnet with no hardforks (so with miners consent and old nodes continuing to operate on the old chain after a fork).

Other issues are audit to be done, specification finalization etc.

Thus the biggest problems we are going to have in order to launch are not just about the reference implementation  but the infrastructure:

• Some guys are doing reference GPU miner, however, we would like to organizer GPU miners contest as well, as ZCash guys did.
• Wallet development. We are going to switch to secp256k1 (Bitcoin's) from current choice of 25519 (Nxt / Waves Monero) we're using now. We have some Wallet API in the reference client implementation, some UI is needed.
• Foundation formation, exchanges etc
• EFYT <-> Ergo swapping rules

So the precise dates are going to be defined not just on tech, unfortunately or not.

Come to us to help Ergo to grow!

[mxxxxxx]

Thanks for the tutorial. I wanted to ask for this, but you were faster!

Do you have any plans for the going live? Any date?

Thanks! Let me answer you along with providing some update.

2.0 will include almost all the features previously planned  as 2.x. Thus this testnet release will be pretty much like the mainnet. The biggest question to solve after 2.0 testnet is about
soft-forkability, i.e. decide rules how the protocol can evolve in the mainnet with no hardforks (so with miners consent and old nodes continuing to operate on the old chain after a fork).

Other issues are audit to be done, specification finalization etc.

Thus the biggest problems we are going to have in order to launch are not just about the reference implementation  but the infrastructure:

• Some guys are doing reference GPU miner, however, we would like to organizer GPU miners contest as well, as ZCash guys did.
• Wallet development. We are going to switch to secp256k1 (Bitcoin's) from current choice of 25519 (Nxt / Waves Monero) we're using now. We have some Wallet API in the reference client implementation, some UI is needed.
• Foundation formation, exchanges etc
• EFYT <-> Ergo swapping rules

So the precise dates are going to be defined not just on tech, unfortunately or not.

Come to us to help Ergo to grow!

https://twitter.com/ergoplatformorg/status/1093534968792387584

[kushti]

We have some more example contracts:

• Rock-Paper-Scissor game contract, which is widely covered in Ethereum tutorials
• Non-interactive tumbler: Alice creates a coin on the chain and then just listens to incoming transactions. Bob comes and do mixing, in the way that new coins created by mixing transactions
  are indistinguishable to external observer, one coin could be spent only by Alice, another only by Bob, and this is ensured by the Alice's coin contract!

Code and unfinished documentation are online: https://github.com/ScorexFoundation/sigmastate-interpreter/pull/380

[mxxxxxx]

We have some more example contracts:

• Rock-Paper-Scissor game contract, which is widely covered in Ethereum tutorials
• Non-interactive tumbler: Alice creates a coin on the chain and then just listens to incoming transactions. Bob comes and do mixing, in the way that new coins created by mixing transactions
  are indistinguishable to external observer, one coin could be spent only by Alice, another only by Bob, and this is ensured by the Alice's coin contract!

Code and unfinished documentation are online: https://github.com/ScorexFoundation/sigmastate-interpreter/pull/380

https://twitter.com/ergoplatformorg/status/1093913698303987713

[kushti]

More quick facts on Ergo:

Ergo has Bitcoin-like UTXO transactional model. Namely, a transaction is spending one-time objects and creating new one-time objects. We call this object a box. A box is immutable object which could be only created or removed. A box is not simply a coin, rather, it is contains registers with data (and code). Even more, there's nothing in box but registers. There are four predefined registers, with monetary value, protecting script, and identifier of a transaction which created the box and output index in the transaction (and also creation height). Because data of transaction which created the box is included into it, the box has unique contents and thus unique id. A box is first-class citizen in the Ergo protocol. Active boxes set is authenticated via a hash-based data structure, which allows to build lightweight full-nodes (as described in https://eprint.iacr.org/2016/994). A box may have up to six additional registers with typed data. A script may access its registers (as welll as registers of input and output boxes of the spending transaction).

This design with immutable boxes is more friendly to light clients than a cryptocurrency with long-living accounts (such as Nxt and Ethereum), see e.g. https://eprint.iacr.org/2018/968 , and also simpler in regards with some security problems.


 

[mxxxxxx]

More quick facts on Ergo:

Ergo has Bitcoin-like UTXO transactional model. Namely, a transaction is spending one-time objects and creating new one-time objects. We call this object a box. A box is immutable object which could be only created or removed. A box is not simply a coin, rather, it is contains registers with data (and code). Even more, there's nothing in box but registers. There are four predefined registers, with monetary value, protecting script, and identifier of a transaction which created the box and output index in the transaction (and also creation height). Because data of transaction which created the box is included into it, the box has unique contents and thus unique id. A box is first-class citizen in the Ergo protocol. Active boxes set is authenticated via a hash-based data structure, which allows to build lightweight full-nodes (as described in https://eprint.iacr.org/2016/994). A box may have up to six additional registers with typed data. A script may access its registers (as welll as registers of input and output boxes of the spending transaction).

This design with immutable boxes is more friendly to light clients than a cryptocurrency with long-living accounts (such as Nxt and Ethereum), see e.g. https://eprint.iacr.org/2018/968 , and also simpler in regards with some security problems.

https://twitter.com/ergoplatformorg/status/1096455156919615488

[kushti]

Testnet 2.0 release date is planned to be around March, 14th.

This [PRE-ANN] topic will be abandoned after that, and a new [ANN] topic will be started.

2.0 conceptually will be very close to mainnet.

Security audit will be started about the same time.

[mxxxxxx]

Testnet 2.0 release date is planned to be around March, 14th.

This [PRE-ANN] topic will be abandoned after that, and a new [ANN] topic will be started.

2.0 conceptually will be very close to mainnet.

Security audit will be started about the same time.

https://twitter.com/ergoplatformorg/status/1099021658541699073

[kushti]

The plan is still the same: testnet 2 will be released around March, 14th.

It will include the following:

• Used cryptographic group is replaced with secp256k1 (used in Bitcoin)
• Header is of constant size as interlinks vector (described in KLS16 paper http://fc16.ifca.ai/bitcoin/papers/KLS16.pdf )
• Networking protocol is now versioned (to allow updates in future), also a peer now is signalling its operation (full node, light node storing all the blocks, or number of last blocks stored etc). 
• Memory pool reworked
• Language interpreter reworked, many operations added to the language, included operations on authenticated trees (it allows to do ICO/LETS systems and other complex contracts with dynamic data, more examples soon)
• Foundation script and bootstrapping method are finalized
• Tokens per transaction limit has been removed: now every token, input, and output has some cost (adjustable via miners voting), which is added to the total computational cost of the transaction (thus costs a node is bearing to parse and check a transaction are explicitly defined).

No major changes after Testnet2, only finishing some things in the language interpreter, security audit, networking protocol improvements etc. Thus the team already feels the heat of the Ergo starship launch.

Also, ErgoScript tutorial will be published within next few days.

[mxxxxxx]

The plan is still the same: testnet 2 will be released around March, 14th.

It will include the following:

• Used cryptographic group is replaced with secp256k1 (used in Bitcoin)
• Header is of constant size as interlinks vector (described in KLS16 paper http://fc16.ifca.ai/bitcoin/papers/KLS16.pdf )
• Networking protocol is now versioned (to allow updates in future), also a peer now is signalling its operation (full node, light node storing all the blocks, or number of last blocks stored etc). 
• Memory pool reworked
• Language interpreter reworked, many operations added to the language, included operations on authenticated trees (it allows to do ICO/LETS systems and other complex contracts with dynamic data, more examples soon)
• Foundation script and bootstrapping method are finalized
• Tokens per transaction limit has been removed: now every token, input, and output has some cost (adjustable via miners voting), which is added to the total computational cost of the transaction (thus costs a node is bearing to parse and check a transaction are explicitly defined).

No major changes after Testnet2, only finishing some things in the language interpreter, security audit, networking protocol improvements etc. Thus the team already feels the heat of the Ergo starship launch.

Also, ErgoScript tutorial will be published within next few days.

https://twitter.com/ergoplatformorg/status/1103597129333989376

[mxxxxxx]

"We would be happy to get feedback! ErgoScript, a Cryptocurrency Scripting Language Supporting Noninteractive Zero-Knowledge Proofs"

https://docs.ergoplatform.com/ErgoScript.pdf

https://twitter.com/chepurnoy/status/1105501885732016128

[mxxxxxx]

A lot of great events around Soho in Hong Kong today during a Token2049 conference and massive pub crawl. You can meet Ergo Platform community members with its own station at Peak Cafe Bar from 8pm.

https://twitter.com/ergoplatformorg/status/1105805624237912064

Big thank you to everyone hanging out with us thanks to Token2049 pub crawl organized by Bitcoin Association

https://twitter.com/ergoplatformorg/status/1106144840092446730

[mxxxxxx]

Ergo Platform Testnet 2.0 is live. Smart contracts language updated. Different improvements details in the description of the release. Off to preparing Ergo starship launch.

https://github.com/ergoplatform/ergo/releases/tag/v2.0.0

https://twitter.com/ergoplatformorg/status/1106208325191065602

[kushti]

Another Q&A session will be held on Tuesday. Time will be announced on Monday, here, and also over our Telegram and Twitter channels.

On latest changes:

1. Unlike Bitcoin and other UTXO-based cryptocurrencies, an Ergo transaction has inputs to spend (and outputs to create), but also read-only inputs not to be spent. This simplifies a lot oracles, token-level contracts, contracts depending on other contracts etc.

2. Operations on trees gives possibility to have data storage authenticated with a coin (or UTXO, or "box" as we call it) with no data itself being stored in the UTXO set. This allows to have persistent authenticated storage, with possible authenticated modifications, with no much burden on full-nodes (unlike Ethereum).

With these new feature, such complex contracts as ICOs, whitelisted token trading, LETS systems etc become possible. Some examples soon.

[mxxxxxx]

Another Q&A session will be held on Tuesday. Time will be announced on Monday, here, and also over our Telegram and Twitter channels.

On latest changes:

1. Unlike Bitcoin and other UTXO-based cryptocurrencies, an Ergo transaction has inputs to spend (and outputs to create), but also read-only inputs not to be spent. This simplifies a lot oracles, token-level contracts, contracts depending on other contracts etc.

2. Operations on trees gives possibility to have data storage authenticated with a coin (or UTXO, or "box" as we call it) with no data itself being stored in the UTXO set. This allows to have persistent authenticated storage, with possible authenticated modifications, with no much burden on full-nodes (unlike Ethereum).

With these new feature, such complex contracts as ICOs, whitelisted token trading, LETS systems etc become possible. Some examples soon.

https://twitter.com/ergoplatformorg/status/1107029765570134016

[mxxxxxx]

Next Q&A with  Ergo Platform core developers on March 19, 5 PM Moscow time, 2 PM UTC on Telegram

https://twitter.com/ergoplatformorg/status/1107729639420674049

[coloredcoin]

What's the asset ID of EFYT on waves,and where to trade it?
Seems can not found the trading pair on tidex.