Bitcoin Forum

https://i.imgur.com/GVt9vMT.png

ælf is a decentralized self-evolving cloud computing blockchain network that aims to provide a high performance platform for commercial adoption of blockchain. In order to establish a blockchain infrastructure for various commercial requirements, ælf provides a highly efficient multi-chain parallel-processing system with cross-chain communication and self-evolving governance. It brings 4 key innovations:

1. Scalable nodes on cluster of computers
2. Parallel processing for maximum utilization of processing power
3. Resource isolation for smart contracts via independent and specialized side chains
4. Interoperability to run on and flexibility to choose from different consensus protocols (DPoS — native, PoW, PoS) and private / public chain

ELF tokens are used to pay resource fees in the system, such as deployment of smart contracts, operating and upgrading of systems (transaction fees, cross- chain data transfer fees). It also enables the community to vote on major on-chain decisions, such as electing mining nodes, introducing new features to the system and other major decisions, which collectively enable self-evolution capability of the network.

aelf foundation is the governance entity for aelf based in Singapore. As a non-profit entity, its primary goal is to promote the development of aelf technology and its various applications while facilitating corporation and startups to establish on top of or transform their infrastructure into blockchain. aelf foundation will implement comprehensive management and governance model, fully compliant with regulations and laws in Singapore.

aelf concepts and technological features

1. Processing power & Scalability

i. Each node is a computer cluster network (e.g., a cloud network) instead of a singular computer. By leveraging cloud networks as nodes, aelf aims to further empower the network participants with higher computational power as well as the storage capability.
ii. Parallel processing algorithm is developed and integrated to each node to ensure the optimal utilization of all the participating computers in the cloud network. When a node handles a complex set of transactions within a smart contract, it will dissect the transactions into groups of those that do not demonstrate interdependency and process them in parallel simultaneously. Consequently, the takt time is minimized and the overall processing speed maximized.
iii. A node’s capacity can be easily scaled by adding new computers to the existing network without having to upgrade the node computer’s hardware.

2. Independence & Specialization

i. Multichain network: each side chain is independent from one another and smart contracts resides are executed directly from a side chain, not through the main chain. This enables each side chain to be impervious to the high traffics on another chain, thereby localizing the traffic concentration and guaranteeing consistent transaction speed for smart contracts executed in other side chains. Each side chain would also have the ability to host its own set of nodes to guarantee low traffic and determine its own processing speed.
ii. Each side chain is specialized for a specific business scenario, e.g., token issuance (ICO), insurance database, in-game transactions, etc, and their consensus protocol, node delegation, chain privacy and various other chain qualities can be tailored to best support the specific business scenario.
iii. The main chain acts as the ledger and the communication hub, unlocking highly efficient cross chain communication, triggering of smart contracts across side chains and effective synchronization between chains with different speeds.

3. Governance & Flexibility

i. aelf aims to bestow its network participants an entirely self-evolving authority and capability through its voting protocol. aelf coin holders will have the ability vote on a diverse sets of critical decisions that will collectively shape the eco-system; this includes the decision for each side chain to host their own delegated node, choose whether the participating side chain will be public or private, determine the size and the speed of the side chain, remove or add side chains to the network, etc.
ii. aelf utilizes Merkle tree root based chain indexing to communicate and interoperate with other consensus protocol based blockchains such as PoW and PoS.
iii. aelf provides side chain templates to its developers for rapid smart contract development for those who do not have the in-depth understanding and capacity for ground-up smart contract coding

Youtube: https://www.youtube.com/watch?v=qbIP1TEX33Q

https://i.imgur.com/iVJxePN.png

aelf Whitepaper: https://aelf.io/gridcn/aelf_whitepaper_EN.pdf?v=1.6

aelf Economic and Governance Whitepaper: https://aelf.io/gridcn/aelf_economic_system_whitepaper_en_v1.0.pdf?time=1

aelf Public Testnet and Supporting Features Introduction: https://aelf.io/gridcn/aelf_public_testnet_and_supporting_features_introduction_en_v1.0.pdf?t=20200327

Developer Documentation: https://docs.aelf.io/

https://i.imgur.com/EtKzXjR.png

https://i.imgur.com/LFnmlgX.png

https://i.imgur.com/VerSwrb.png

https://i.imgur.com/ICqi2nX.png

https://i.imgur.com/iaKLbaH.png

Aelf Official WebSite: https://aelf.io/
GitHub: https://github.com/AElfProject/AElf
Twitter: https://twitter.com/aelfblockchain/
Youtube: https://www.youtube.com/c/aelfblockchain (https://www.youtube.com/c/aelfblockchain)
LinkedIn: https://www.linkedin.com/company/aelfblockchain (https://www.linkedin.com/company/aelfblockchain)
Facebook: https://facebook.com/aelfofficial/
Medium: https://medium.com/@aelfblockchain/
VKontakte: https://vk.com/aelfofficial
Reddit: https://reddit.com/r/aelfofficial/
Reddit (Chatroom): https://s.reddit.com/channel/2009921_6bb8ccf6a8f8e6dfac73865f552072d2c1cf8f0d
Slack: https://slack.aelf.io/
Discord: https://discord.gg/xaGU8hZ
Telegram : https://t.me/aelfblockchain/
Telegram 2nd: https://t.me/aelfcommunity/
Telegram (News): https://t.me/aelfnews
Telegram (中文): https://t.me/aelf_chs/
Telegram (한국): https://t.me/aelfkorean/
Telegram (日本語): https://t.me/aelfjapan/
Telegram (pyccкий): https://t.me/aelf_russian/
Telegram (العربية): https://t.me/aelf_arabic/
Telegram (Deutsch): https://t.me/aelfgerman
Telegram (Italiano): https://t.me/aelfitalian
Telegram (Español): https://t.me/aelf_spanish
Telegram (Türkçe): https://t.me/aelf_turkish
Telegram (French): https://t.me/aelf_french
Telegram (Tiếng việt): https://t.me/aelf_vietnam
Telegram (India): https://t.me/aelfindia

https://i.imgur.com/EtKzXjR.png

aelf Enterprise v1.0.0 Preview 3 officially Released

https://i.ibb.co/3sQkTXj/main-qimg-e3b675195d7adddf9b055847ecd2d842.jpg (https://ibb.co/qnVxDGc)

On Tuesday, 23th of June, aelf Enterprise v1.0.0 Preview 3 was launched. It is a comprehensive commercial blockchain solution, including a fully developed blockchain ecosystem, development suite, and supporting documents for basic applications and services. Preview 3 is optimized in terms of performance, scalability, and user experience. With a more comprehensive commercial blockchain solution, this version can provide a safe, stable, and efficient development environment for developers.

Preview 3 is an enterprise-ready, integrated blockchain solution. The ‘main chain + multi-side chain structure’, ‘cluster’ data center, a parallel computing system, AEDPoS consensus, and a multi-governance model catalyzes the deep integration of various applications with blockchain technology.

The Public Testnet Code has been upgraded to aelf Enterprise v1.0.0 preview 3 and all functions required for Mainnet launch are deployed. Supporting features, such as the Test Android, IOS, and web wallets, in addition to the Testnet Blockchain Explorer will be updated simultaneously. Based on aelf v1.0.0 preview 3, community users can experience the functional modules of aelf’s mainnet.

aelf Enterprise 1.0.0 Preview 3 Version System Integration

1.aelf Enterprise
- aelf v1.0.0 Preview 3
- DevKit v1.0.0 Preview 3

2.aelf External Applications
- aelf Blockchain scanner v0.4.1
- aelf Scanner Mysql plugin v1.0.0 Preview 3
- aelf Explorer v1.0.0 Preview 3
- aelf Wallet v1.0.0 Preview 3
- aelf JS SDK v3.2.34
- aelf-Bridge v0.0.9
- aelf CLI in Nodejs v0.1.43

3.aelf Browser Extension v1.1.1

Detailed Updates

1.aelf Enterprise Updates and Introduction

1.1 aelf v1.0.0 Preview 3

https://github.com/AElfProject/AElf

- Optimized the transaction parallel grouping mechanism to improve the parallel transaction execution efficiency
- Simplified the transaction verification mechanism and improved transaction verification efficiency
- Reconfigured the smart contract unit testing framework to improve unit testing efficiency
- Optimized log configuration scheme
- Optimized the malicious nodes marking mechanism
- Improved DPoS consensus stability

1.2 Devkit v1.0.0 Preview 3

- aelf-boilerplate: https://github.com/AElfProject/aelf-boilerplate
- Developer documents: https://docs.aelf.io/
- New version of developer documentation framework
- Added contract development tutorial module
- Added Consensus, transaction and network protocol modules

2.aelf External Applications Update

2.1 aelf Scanner Mysql plugin v1.0.0 Preview 3

- Fixed reference bug

2.2 aelf explorer v1.0.0 Preview 3

- Added all chain’s data
- Added address details
- Added token list and detailed data
- Contract event and transactions can be viewed in contract details

2.3 aelf wallet v1.0.0 Preview 3

- Fixed bug

2.4 aelf JS SDK 3.2.34

- Fixed bug

2.5 aelf-Bridge 0.0.9

- Added action to smooth the difference of calling contract methods through APP, aelf Explorer Extensions and aelf SDK.

2.6 aelf CLI in Nodejs v0.1.43

- Fixed bug

From here aelf will focus on analyzing exception cases based on the running of aelf Enterprise v1.0.0 Preview 3. At the same time, aelf will do deep and systematic research on block producing efficiency, system stability and performance, storage data structure, and network transmission efficiency optimizations. The team will continue to explore the ecosystem governance model and economic system model designs.

Preview 3 is a crucial display of aelf’s latest technical updates and the R&D achievements of the mainnet. Mainnet preparation has been initiated in accordance with the Mainnet launch Roadmap. More details will be posted in the near future! Aelf will continue to strive for excellence, providing users with high-performance, stable, and reliable blockchain infrastructure.

🔊 Exciting news! ELF is now available on ZGexchange.

Deposits and withdrawals will be authorized at 14:00 July 3 (GMT+8). 

Additionally, ELF will be available for All-Currency Futures from 16:00 July 6 (GMT+8).

https://i.ibb.co/1McCTys/Eb5g-v-AUEAA-3i-C.jpg (https://ibb.co/kJZLXb3)

🔊 Shout out to a new awesome video!

Do you know how to run single-node and multi-node on aelf boilerplate?

Check out this #tutorial from the head of aelf Enterprise Yiqi Zhao! Suggest watching in 1080 HD with popcorn!🍿

https://www.youtube.com/watch?v=jMxWrZZXLKI

🔊 As one of the leading blockchain projects in Data, Cloud & Communication Services category, aelf has been featured in the Singapore Blockchain Landscape 2020 alongside AWS, IBM Cloud & Microsoft Azure 🎉

https://cointelegraph.com/news/singapores-blockchain-landscape-has-grown-more-than-50-since-last-year

🔊 We have good news to share with you!

In 24h we will introduce THE FIRST PUBLIC TESTING of aelf blockchain in 2020!

Countdown just started. Stay tuned! 💪💪

https://i.ibb.co/5MhC1rH/Ec-Uh9za-Uw-AAWRf9.jpg (https://ibb.co/QbvhJPw)

So this project is an old one, why create a new thread? You have old threads here -

https://bitcointalk.org/index.php?topic=2981592.120
https://bitcointalk.org/index.php?topic=2454628

Why not update the first thread? You are already listed in several exchanges, is there any reason why you posted another thread for this project? Do you want a fresh start for this project?

🔊 We are thrilled to announce that #aelf First BingoGame Public Test goes live today!

A Party with amazing Prizes! 💰

There are only 40 places available for IOS on a first-come, first-served basis. And unlimited for Android.

Check out all the details 👇

https://medium.com/aelfblockchain/aelfs-first-bingogame-public-testing-in-2020-e9848d281d3e

Since we haven't shared anything here recently, we decided to open a new topic to be organized and updated. We were worried that people wouldn't see our latest updates.

🔊 aelf development team weekly #update!

✅ We would like to let you guys know that we've been working hard to provide developers a better user experience. 💪💪

https://i.ibb.co/37qY98T/Ec-Zk-R0-RUc-AAAQw-U.jpg (https://ibb.co/hyj1Jng)

🆕 aelf ecosystem team weekly #update!

Our goal: Making the infrastructure of the aelf network easier to use.

Click the image to check the updates ⬇️

https://i.ibb.co/b71qYtf/Ec-Ztc-WSVc-AAEXV.jpg (https://ibb.co/Wsnq7CT)

Comparison of Cross-Chain Solutions - aelf 🆚 Polkadot

https://i.ibb.co/yX4KWrB/Ecf-KMi-RUMAA-8-I7.jpg (https://ibb.co/R9jtzq4)

Mark your calendar! 📅July 14th

Our COO Zhuling Chen will join the #Binance 'Off the Charts' Live Panel! Don't miss it!

Topic: Emerging Applications for Blockchain and Crypto

See you on ⏰ Tuesday 14th July, 19:30 (11:30 AM UTC)

https://i.ibb.co/0CHWrjr/Ecyk-QL4-Uw-AAHl9h.png (https://ibb.co/bscyXgX)

#aelffeatures brings you highlights from last week's #aelf mentions on the web!

aelf BingoGame, @CoinUp24: http://bit.ly/2CoprZ9

Singapore’s Blockchain Landscape, @Cointelegraph: http://bit.ly/3iUst89

Hackers Failed to Breach CCTP, @publish0x: http://bit.ly/2Dw76cZ

https://i.ibb.co/ZgHJNcy/Ecz-W6gz-U0-AAzd-Xy.png (https://ibb.co/1XsnbRH)

Join us at Binance’s “Off the Charts” virtual conference this Tuesday!

When will Zhuling Chen be speaking: 11:30 AM UTC

We’ll be talking about Emerging Applications of Blockchain and Crypto.

Register for free here: https://www.binance.com/en/anniversary-3

https://i.ibb.co/wrJF6z7/Ec2u-Ag-UVAAAul-ZU.png (https://ibb.co/mFvVzc0)

Something amazing will start from here: 0x91517330816d4727edc7c3f5ae4cc5bef02ec70f 🧩

https://i.ibb.co/mNnVYTF/Eczwe-Uc-Uc-AY3-CHn.jpg (https://ibb.co/2Zz1LhY)

You can lock the old threads so this will serve as the central point of communication. Because if the other threads are still open, someone may ask something on those threads. It is better to have only one thread so people will just read the updates and other clarifications asked by your followers here. Also, seems that there's a lot going on here, if you want exposure to the community, you can run your own sig campaign to refresh the community about your project.

BinanceTurns3 Panel Discussion Part 1:

Our COO Zhuling Chen shared his idea about blockchain adoption and how aelf made it in Binance's panel discussion. Check out the highlights:

https://i.ibb.co/pRmH2XZ/11.jpg (https://ibb.co/CMrjB0v)

https://i.ibb.co/0DHTJDH/22.jpg (https://ibb.co/6njzsnj)

https://i.ibb.co/sVYk3hK/33.jpg (https://ibb.co/qrQX1zN)

BinanceTurns3 Panel Discussion Part 2:

Our COO Zhuling Chen shared his idea about blockchain adoption and how aelf made it in Binance's panel discussion. Check out the highlights:

https://i.ibb.co/68N6ByP/11.jpg (https://ibb.co/5k2qF18)

https://i.ibb.co/DVSzhZN/22.jpg (https://ibb.co/f1Pqfsb)

https://i.ibb.co/KL3Z4HP/33.jpg (https://ibb.co/k9WnbF7)

https://i.ibb.co/mNRTDHZ/44.jpg (https://ibb.co/Bnf3zgW)

➡️ aelf Enterprise Weekly #Update!

We would like to let you guys know that we've been working hard to give developers a better user experience.

https://i.ibb.co/YNJw79x/Ec99fqi-U8-AAyli-V.jpg (https://ibb.co/51CwWDP)

➡️ aelf Mainnet's R&D Team Weekly #Update!

Our goal: Making the infrastructure of the aelf network easier to use.

Click the picture below and check out the updates ⬇️

https://i.ibb.co/QNKBxK2/1.jpg (https://ibb.co/1qmV4mD)

aelf’s Hacker Bounty Phase 2 Kicks Off

https://i.ibb.co/NT7GKQm/2.jpg (https://ibb.co/PDtVg39)

On May 29th, aelf launched phase 1 of the Hacker Bounty with a reward of 88,888 ELF based on the Cross-Chain Transfer Protocol (CCTP). Phase 1 concluded on June 5th, with no successful attempts at hacking the CCTP, leaving the bounty unclaimed.

Phase 2 of the Hacker Bounty will go live on July 16th. The bounty for phase 2 has been increased to 1,000,000 ELF. The program is co-hosted by aelf and CertiK, a blockchain security company. The co-organizers are DVP, a decentralized vulnerability platform, and SlowMist Technology, a blockchain security company. PeckShield, another blockchain security company, will be the vulnerability assessment partner. The event will be covered by dozens of leading media outlets around the world and is expected to draw white hat hackers and cyber-security enthusiasts from all over the world.

During the program, users who retweet the event will also have the opportunity to share out 8,888 ELF and win 52 ELF every day. Hackers participating in the program are required to find vulnerabilities in the underlying technology based on the logic implementation method of ELF token locking and swap. Sign up now and take on the challenge!
The aelf Foundation is hosting this program to show how secure aelf’s lock-in contract and Cross-Chain Transfer Protocol (CCTP) are while also enabling users to have a better understanding of the CCTP, which was launched in May 2020. The event will be posted as a Bounty Program on the aelf DAO to ensure transparency throughout. The draft of the program has been discussed in the saelf governed Telegram community and the bounty was set at 1 million ELF by the community members.

Date
July 16th 2020 20:00 — August 5th 2020 12:00 (GMT +8)

Rules
- Participants can sign up as individuals or teams — there’s no limit on the team size.
- The Bounty Program is about finding vulnerabilities in the Cross-Chain Transfer Protocol (CCTP), so those on the Ethereum Network or aelf will not count.
- At 12:00 pm (GMT +8) on July 16th, the aelf Foundation will lock 1 million ELF in the lock-in contract.
- At 12:00 pm (GMT +8) on July 27th, a Merkle tree will be generated.
- At 12:00 pm (GMT +8) on August 5th, 1 million ELF test tokens will be swapped to the aelf testnet via the Cross-Chain Transfer Protocol (CCTP).
- Participants who are able to hack the CCTP and swap the ELF test tokens to their own account addresses during the event will be rewarded with the equivalent amount of ERC20 ELF tokens.
- The aelf Foundation will retrieve the bounty if no hackers managed to breach aelf’s CCTP by the end of the event.

Lock-in Contract Information
Ethereum Mainnet:
- Ethereum mainnet lock-in contract address: 0x91517330816d4727edc7c3f5ae4cc5bef02ec70f
- Merkle Tree generation contract address: 0x76562bD67452359b68fACbfa2d0cc9c1999F566C
aelf Testnet：
- Side-chain token mapping contract address: RXcxgSXuagn8RrvhQAV81Z652EEYSwR6JLnqHYJ5UVpEptW8Y
- Contract Explorer: https://explorer-test-side01.aelf.io/contract?#https%3A%2F%2Fexplorer-test-side01.aelf.io%2Fviewer%2Faddress.html%23%2Fcontract%2FRXcxgSXuagn8RrvhQAV81Z652EEYSwR6JLnqHYJ5UVpEptW8Y (https://explorer-test-side01.aelf.io/contract?#https%3A%2F%2Fexplorer-test-side01.aelf.io%2Fviewer%2Faddress.html%23%2Fcontract%2FRXcxgSXuagn8RrvhQAV81Z652EEYSwR6JLnqHYJ5UVpEptW8Y)
- Contract code on GitHub：https://github.com/AElfProject/aelf-boilerplate/tree/token-swap/chain/contract/AElf.Contracts.TokenSwapContract (https://github.com/AElfProject/aelf-boilerplate/tree/token-swap/chain/contract/AElf.Contracts.TokenSwapContract)

How to Collect the Bounty
- For Chinese users: contact DaYuTongXue (WeChat ID: a439714) on WeChat
- For English users: contact Itsu Ace (@Itsu_Ace) on Telegram

Hacking Proof
Participants need to show their hacking proof to the aelf team after they have hacked the Cross-Chain Transfer Protocol (CCTP).
The following information needs to be provided as the hacking proof:
- Code for the hacking process
- A document which explains the hacking process
- Self-introduction
- ELF wallet address

Retweet to Win ELF
- Simply retweet the event and you will have the opportunity to share out 8,888 ELF.
- If no one is able to hack the CCTP before the deadline (August 5th), then all the retweeters (keep the retweet until the end of the event) will share out the 8,888 ELF!

We’d like to invite white hats, technology enthusiasts, and master hackers to participate in the Hacker Bounty Program and we hope the program will give you an in-depth understanding of the Cross-Chain Transfer Protocol (CCTP). Any feedback or suggestions on how to improve the aelf ecosystem are also welcomed!

https://i.ibb.co/5rgZ33j/3.png (https://ibb.co/D9HdFFM)

#MondayMotivation

Guess what Zhuling is doing now?

💬Tip: He might be promoting aelf and blockchain with a big tech company.

https://i.ibb.co/JjCPYcC/Ed-Wy-C3-NUc-AAGPn7.jpg (https://ibb.co/Mk9Lzg9)

Aelf advocate Itsu Ace was invited by Alibaba Cloud to attend the Meeting for 'blockchain development'. 🎉

They discussed how to ensure blockchain nodes run stably and how to deal with attacks by the black industry to protect user interests.

https://i.ibb.co/2khwmHP/1.jpg (https://ibb.co/71CH8LV)

https://i.ibb.co/crmt3rH/2.jpg (https://ibb.co/jrpGfr2)

https://i.ibb.co/cxGDHq3/3.jpg (https://ibb.co/yVwW12P)

How did aelf Enterprise help businesses run more efficiently amid the COVID19 pandemic?

Click below 👇 index to start reading!

https://medium.com/predict/the-remote-economy-is-now-thriving-see-how-blockchain-is-leading-the-way-8d3186347741

🔊Our COO Chen Zhuling gave a talk on "Emerging Applications of Blockchain and Crypto" at #Binance 'Off the Charts' Live Panel!

If you didn't watch it live, watch it here! https://youtube.com/watch?v=AdlVPcKRGIQ

https://i.ibb.co/WzkHhJJ/trends60.png (https://ibb.co/hdBg6zz)

😄A Surprise for all #aelfers

▶️This is not even 1% of the it!

🔜Please Stay Tuned! #aelf & #Huawei
 
https://twitter.com/aelfblockchain/status/1286273571107479552

aelf will hold an AMA with Itsu Ace on Twitter

5 winners will be selected to share out the rewards!

⏰ 31 July, 5pm-6pm(GMT +8)

Tasks:

1️⃣ Watch the video https://youtu.be/2alA6mIAVHA
2️⃣ Like&Retweet https://twitter.com/aelfblockchain/status/1287935951730126855
3️⃣ Comment with your questions, tag @3 friends, include the hashtag #aelfHackerAMA

https://i.ibb.co/GHBntPp/Ed-q-J9-FVo-AI1k3s.jpg (https://ibb.co/6XVr1sw)

Mark your calendar 📅 👉July 29!

📖Learn how BLOCKCHAIN fit into your business

Digitalization Journey with Huawei Cloud

Also find us at the https://rebrand.ly/partnerpage

HUAWEI CLOUD ☁️ X #AELF

Premir on Cloud-Powered Blockchain Solutions available now! 🎬

Learn how blockchain fits into your business digitalization Journey.👣

More stories from here onwards! Let's go! 👫

https://www.youtube.com/watch?v=zQSWeXbiOqs&feature=youtu.be

aelf Officially Partners up with DVP

https://i.ibb.co/P5BKsx9/1-2-TJLz7z8-E3eob-RWef-9-Jjg.jpg (https://ibb.co/4jBzwWY)

The hacker bounty phase 2 was officially launched on July 16 with a bounty of up to 1,000,000 ELF. Now halfway through the competition, the bounty is still unclaimed.

The hacker bounty program is co-hosted by aelf and CertiK, a blockchain security company. The co-organizers are DVP, a decentralized vulnerability platform, and SlowMist Technology, a blockchain security company. PeckShield, another blockchain security company, is the vulnerability assessment partner. The event is covered by dozens of leading media outlets around the world.

Currently, security is the lifeblood of blockchain companies, whether it is Smart Contract Code Auditing, Node Hardening, or Penetration Testing. In particular, given the “tamper-proof” feature of smart contracts, the bugs that are inevitable in the codes are easily exploited by hackers. Since the blockchain network is decentralized, a single security vulnerability on a blockchain node may cause thousands of nodes to be attacked.

In recent years, there have been quite a few security incidents in the news, causing huge asset losses and extremely negative impact. These incidents concern all aspects of the blockchain industry, including exchanges, mining pools, wallets, smart contracts, etc. Among them, exchanges, investment wallets and other platforms which are close to users have become a focal point with frequent security incidents. It is obvious that the vulnerabilities are undermining the safety of hundreds of millions of digital assets, posing a daunting threat and challenge to the entire blockchain security ecosystem.

The decentralized vulnerability platform (DVP) was developed to solve this issue. Connecting blockchain companies, security companies and white hat hackers from all over the world, the platform aims to use blockchain technology to create anonymized security community scenarios and the consensus that decentralization and vulnerability are mining. Decentralization means that white hats and security engineers around the world can get involved in finding vulnerabilities, and this service is accessible to every blockchain company on the planet. Vulnerability mining represents an automated reward payment system for blockchain companies and white hats. Companies are required to specify the assets converge to be audited and the reward criteria, and stake the deposits into the contract. White hats can submit information about blockchain-related vulnerabilities and threats, and check the vulnerability review and claim progress at any time. They will be rewarded accordingly once their information are adopted.

aelf has officially entered into partnership with DVP. As the co-organizer of the aelf hacker bounty phase 2, DVP will continue to ensure aelf’s security and help it build a better blockchain ecosystem. This hacker bounty has also drawn the attention of many hackers, white hats, and security enthusiasts.

aelf invited hackers and white hats worldwide to participate in the bounty program is to verify the security of the Cross-Chain Transfer Protocol (CCTP) and lock-in contracts, thus ensuring the security of users’ information and assets, and enhancing vulnerability early warning and emergency response mechanisms. At the same time, the program helps users fully understand the mechanism of cross-chain transfer and helps us receive feedback from the community, so that we can continue to optimize the underlying technology, and build a more secure blockchain network ecosystem.

On July 27, aelf has generated the Merkle Tree according to the Merkle Proof process. Now users can obtain the required data on Merkle Proof and enable the swapping function after recording the Merkle tree root data (the root hash value of the Merkle tree) on the aelf network, the swapping feature can be start. At present, there is nearly a week before the end of hacker bounty program. Do not miss it, hackers!

Hacker Bounty AMA Recap

https://i.ibb.co/LRLzfjV/1.jpg (https://ibb.co/yPwnJvH)

Last Friday ( July 31, 2020), aelf hosted an AMA about hacker bounty and CCTP on Twitter, featuring aelf’s dev advocate, Ace. Below is a transcript of the questions and answers.

Q1: Why aelf Committed to Establishing a Unified Cross-Chain Protocol? And what does it take for increased use-cases and value of your Cross-Chain protocol?
Ace: The protocol is a standard for various user cases, business and scenarios, and with it, aelf can build the whole ecosystem based on the standard, mitigating the cost of designing different cross-chain methods in face of different type of scenarios. We will try to develop more and more popular and real-problem solving dapps on aelf blockchain, better develop many dapps of different type of scenarios.

Q2: What is the uniqueness and what is the purpose of the CCTP protocol, what problems does it solve and what is it applicable to?
Ace: It can support any kind of cross-chain asset transferring services whether the chains are mutually compatible or not. It can be used to transfer money value between different chains, transfer asset between these chains, and prove if an asset’s ownership exists. We can use it to any scenarios described above, for example some financial business

Q3: How does protocol achieves cross-chain transfers between independent blockchain systems?
Ace:: aelf use merkle proof to ensure the elf erc20 token is really locked and transfer equal value of elf token to the same user on aelf blockchain.

Q4: Whether the standard protocol of cross chain transfer of aelf has been attacked and destroyed in this hacker reward offering activity, and will it also be used in the main network mapping? I’m still looking forward to it.
Ace: Till now no one could ever do that, and the CCTP is absolute used for mainnet, otherwise all we have done would make no sense.

Q5: What is the main difference between aelf’s CCTP and other projects multi-chain protocol?
Ace: We use purely smart contracts to achieve this, all of these are on smart contract level. and in these contracts, we use index and merkle proof to relate contracts on two chains

Q6: What blockchains will CCTP first support?
Ace: As you see, we have supported the ETH, and any developer can use any other blockchain projects’s code to create more cross-chain functions with aelf.

Q7: Does team any partnerships or collaborations with other blockchains to use CCTP?
Ace: We don’t need such cooperation. CCTP, as a open-source protocol,is implemented by smart contracts, if another blockchain projects support smart contracts, they are all in CCTP’s territory.

Q8: BTC Relay belongs to the early side chain technology. Link the ETH network to the BTC network to enable users to verify BTC transactions on the ETH. When will ELF be able to conduct ETH and BTC network cross-chain transactions?
Ace: We will do this in nearly future.

Q9: Polkadot USES relay-chain technology, but at present it is mainly ETH. How is THE CCTP of aelf different from it?
Ace: We don’t need any relay-chain, we use smart contract to do cross-chain transferring.

Q10: What are the advantages?
Ace: We have own parallel execution mechanism, so we don’t need some parachain. Then we don’t need additional middle-layer chain. And we can do cross-chain with any other blockchain not only ETH.

Q11: When will a true AELF network cross chain be achieved without the ETH network?
Ace: We will always communicate with ETH to make data in both chains flowing between each other, we are not dependent on Ether. So at the very beginning aelf can operate normally without other chain’s aid.

Q12: Other public chain projects also have cross chain technology. What are the advantages of aelf wide face transfer standard protocol?
Ace: There are lots of projects using a middle man, which is centralized or partially centralized, but aelf cross-chain designation don’t rely on any middle-man of this type, we just need to build smart contracts on both chains and can easily achieve that, phew!

Q13: What applications will aelf cross chain technology have in the future?
Ace: Any application concerning about trust and decentralized need, because aelf is a fundamental platform and infrastructure.

Q14: Can you only transfer assets across chains?
Ace: We can transfer assets both cross-chain and in our own chain.

Q15: When will the Demo of aelf cross-chain asset trading be landed and announced to the community?
Ace: We are still planning and will broadcast the release date in the future.

Q16: Have you currently formed alliances with other projects to start implementing the CCTP protocol? If yes, in which projects is this protocol currently being used?
A16: We don’t need such cooperation. CCTP, as a open-source protocol, is implemented by smart contracts, if another blockchain projects support smart contracts, they are all in CCTP’s territory.

Q17: How will you handle the waiting times for confirmation of each transfer, is it possible that with the cross chain it will be faster or on the contrary it will be slower but safer?
Ace: That is partially related to the confirmation duration on other blockchain interoperate with aelf, say, Ether, if Ether do not accelerate its confirmation time, we could not be much faster although we optimize the speed of this on aelf blockchain, but of course, it is much safer.

Q18: Will the cross-chain you want to work with allow for effective cross-platform transactions or is there a risk that user assets will be lost?
Ace: As long as the counterpart chain support smart contract, especially token contract, the CCTP is really effective and extremely secure once the ownership is relayed on aelf chain.

Q19: Is any more powerful security system better then CCTP in the present blockchain system?
Ace: Our focus and understanding are different. We are exploring for this industry, and our technology is already the top of the industry.

Q20: What is the difference between CCTP and PoW or PoS? Why is the CCTP protocol so much more secure?
Ace: They have no correlation with each other, the CCTP are in essence smart contracts working together, and PoS and PoW are economically incentivising consensus to keep the whole distribution system behave the same.

One Year after the Public Chain Takeoff, the New Era of Blockchain 3.0 has Arrived

https://i.ibb.co/VSxsbF9/1.jpg (https://ibb.co/85bHGys)

Everyone said that 2019 is the year public blockchains took off, and 2020 will be the first year blockchain began to achieve business adoption. Although the coronavirus pandemic continues to wreak havoc on all walks of life worldwide, the blockchain industry is making great strides forward.

In just a few years, the blockchain sector has developed from 1.0 to 3.0, and each upgrade has brought about some changes in the world. As we all know, blockchain 1.0 generally refers to cryptocurrency centered around Bitcoin. Blockchain 2.0 is public chains represented by Ethereum, which can develop smart contracts. In the era of blockchain 3.0, people think that thousands of blockchains can coexist and interoperate.

In the past two years, people have had high expectations of many public chains. However, some of the so-called “blockchain 3.0” projects have either shown slow progress or failed to live up to the expectations after their mainnet went live. People then began to expect to see a killer DApp achieving wide adoption of blockchain. At the same time, as the underlying technology for blockchain connectivity, multi-chain structure and cross-chain technology have become an important part of ‘blockchain 3.0’.

aelf and other Web 3.0 projects can be seen as the underlying technology providers for the Internet of Value. On the aelf blockchain, whether it is valuable information or digital currency, everything can be connected and shared, which is where the magic of cross-chain technology lies.

If the consensus mechanism is the core competitiveness of blockchain, then the cross-chain technology is the key to realizing the Internet of Value for blockchain, particularly for alliance chains and private chains. It is the key to preventing different blockchains from being isolated islands and serves as a bridge connecting blockchain and the outside world.

Cross-chain technology is designed to prevent blockchain from being isolated islands of data

At present, although these public chain projects have seen their performance improved, none of them is able to build the much-anticipated “underlying blockchain highway’ singlehandedly. In particular, driven by the prevailing view that each public chain should be an independent ecosystem, public chains today have become isolated islands of data with different architectures incompatible systems, which poses real difficulty to DApp developers.

The cross-chain technology, as the name suggests, is aimed to realize asset circulation, information exchange and application collaboration between different blockchain platforms. It can be likened to a bridge linking different public chains, which can help realize data transmission between different blockchain networks and greatly reduce transmission costs.

It is obvious that the demand for cross-chain technology is very urgent in today’s blockchain world.

Cross-chain communication can be divided into homogeneous and heterogeneous cross-chain according to different underlying blockchain technology platforms. Cross-chain interaction between homogeneous chains is simple, since their security mechanisms, consensus algorithms, network topology, block generation verification logic are consistent. Cross-chain interaction between heterogeneous chains is quite different. For example, Bitcoin uses PoW algorithm while the alliance chain Fabric uses traditional deterministic consensus algorithm, and its block form and deterministic guarantee mechanism are very different. Since designing a direct cross-chain communication mechanism is not easy, cross-chain interaction between heterogeneous chains generally requires third-party services.


aelf is doubling down on heterogeneous cross-chain research

At present, cross-chain technology mainly includes notary schemes, hash-locking, side chains or relays, and distributed private key control. aelf uses the side chain or relay scheme.
aelf’s cross-chain logic is ‘main chain + side chain’, with an emphasis on ‘one chain, one scenario’, where each side chain can be a scenario, such as a DApp, or a DeFi app. aelf’s cross-chain architecture is centered around the main chain.

In the cross-chain process, aelf achieves intercommunication between different chains via indexing. An index is the transfer of data from one chain to another in a defined structure. The cross-chain index has two steps: parent chain indexing child chain and child chain indexing parent chain.

https://i.ibb.co/g7qSYVK/2.jpg (https://ibb.co/dcCPZgY)

* The parent chain requests data from the child-chain and the data are then sent from the child chain to the parent chain.
* The parent chain processes all the child chain’s index data, generating a Merkle tree, and stores it on the chain. The child chain block has been indexed by the parent chain, and must wait for the data to be confirmed by the network.

The above steps include the whole process of the parent chain indexing the child chain’s block and the child chain re-indexing the parent chain’s block. It’s worth noting that only irreversible blocks can be indexed by other chains.

https://i.ibb.co/Y2T2wPy/3.jpg (https://ibb.co/F6q6Cm0)

As a result, aelf does not need a Hub or a relay chain and is more of a decentralized cross-chain model. This is because communication between different chains does not necessarily require the permission of the aelf’s only main chain each time. The multi-layer child chains under the side chain can also communicate with each other with the index of the upper-layer parent chain and without the main chain getting involved.

On the premise of decentralization, aelf established that only confirmed blocks can be indexed, because only irreversible data can be trusted to ensure the network’s security. aelf also has its own solution for communicating with the Ethereum ecosystem, which can be interfaced with the Ethereum and other blockchain systems via adapters, making it compatible with existing mainstream ecosystems.

It can be seen that aelf has done a great job in homogeneous cross-chain technology, whereas some public chain projects have yet to pull it off. aelf has also begun to develop heterogeneous cross-chain technology, which will allow external chains such as Bitcoin and Ethereum to lock tokens into smart contracts and generate ccorresponding tokens on the aelf chain through contracts to achieve cross-chain communication. It is clear that aelf has taken the lead in cross-chain development.

While it’s still too early to talk about blockchain 3.0 and most projects are still trying to figure out where the underlying technologies are heading, solving the scalability issue public chains are facing today through the cross-chain technology has become the general trend. Cross-chain technology can realize communication between different chains, greatly improve blockchain’s ability to transfer value, and promote the development of IoT and cloud computing. On the other hand, without cross-chain technology, all kinds of blockchain platforms information will just be isolated islands of data, putting a significant limit on the applications of blockchain platforms.

We believe that the cross-chain mechanisms will greatly increase the value of blockchain and usher in a new era of blockchain development. With strong technical prowess and the ability to achieve commercial application, aelf will continue to explore the cross chain technology and provide strong technical support for the rapid and steady development of the industry!

aelf is proud to play a leading role in the review of IEEEorg 's Digital Asset Identification standards for blockchain, with our CEO Haobo Ma being Chair of the DAIWG (Digital Asset Identification Working Group).

https://i.ibb.co/NttnVK3/Eeud-TUz-U0-AEQMz-W.jpg (https://ibb.co/gmmFjJ7)

aelf Hacker Bounty phase 2 has concluded and no one was able to hack CCTP! The security of the CCTP (Cross-Chain Transfer Protocol) has been proven impenetrable. 💪💪

https://i.ibb.co/L545mwv/Eeu1z-Gk-VAAAy-Hcl.jpg (https://ibb.co/WtStZ9s)
https://i.ibb.co/3cC159w/2.jpg (https://ibb.co/ZxMdRp3)
https://i.ibb.co/56md37y/3.jpg (https://ibb.co/s2nh4BG)
https://i.ibb.co/HGk7sVL/4.jpg (https://ibb.co/p4928x6)

What is the CCTP?

CCTP is Cross-Chain Transfer Protocol.

☑️Solve cross-chain issues, such as usability, scalability & security.
☑️Realize cross-chain transfer between incompatible & independent blockchain systems.
☑️Support asset transfer between different blockchain systems.

https://i.ibb.co/kH3N0kQ/photo-2020-08-07-11-58-04.jpg (https://ibb.co/X2ycpNS)

✏️Sign up for the aelf Hacker Bounty Writing Contest.  Let's see how good you are at #blogging. Ledger

💰Win a prize of up to 888 ELF = 88 USD   

⏰7th August - 16th August   

You have 9 days to sign up & submit your articles.

✅ Topic: The Future of aelf Cross-Chain Transfer Protocol   

1️⃣ You can submit more than one article, but the content must be original. 

2️⃣ Explain your understanding of the CCTP or its role in blockchain security & future application in aelf-eco.

💥How to Submit: 

1️⃣ Publish your article(s) on at least 2 platforms, for example, tech blogs, forums, Medium, Twitter, etc.

2️⃣ Submit this form with the article link: : https://docs.google.com/forms/d/e/1FAIpQLSeHs34I9iQr41F9oKnIQfKMmmp28M0EWZ0HwBvRkFPceZqShA/viewform?usp=sf_link

⚠️ We will review all submissions & announce the winners at the end of the event.

https://i.ibb.co/5sWdSJt/Ee0-TY6z-U0-AEk-T0k.jpg (https://ibb.co/j3vdQjB)

https://i.ibb.co/hLNV4vm/Ef-DH08-YUw-AAOCWP.jpg (https://ibb.co/RYKcsWD)

https://i.ibb.co/VjdDnbr/Ef-Il-Kc-NU8-AAJbef.jpg (https://ibb.co/98J2KBz)

A Beginner’s Guide to Understanding the aelf WhitePaper (Part 1)

https://i.ibb.co/CnkPzp4/1-tc-Iz-Cg-Hw-SUY5-Zfpja-IGJg.jpg (https://ibb.co/xMpFDKw)

What is a blockchain?

In the Bingo game DApp demo, we’ve already talked about the aelf real random number generator, which can generate unpredictable random numbers between 0 and 255, making it a useful tool. The interaction logic of this DApp’s backend is very much the same as that of blockchain smart contract. But this DApp is so simple that it doesn’t really show what aelf is capable of. In fact, aelf’s got an awful lot more in its arsenal. When it comes to supporting enterprise-level applications, this is where aelf comes in. For someone who is new to aelf, the best way to aquaint yourself with aelf’s technology is to read the aelf technical whitepaper.

If you have read the whitepaper of some blockchain projects, you might find them difficult to understand or even make no sense. As a result, readers (not speculators) are often at a loss as to what these projects are trying to do. Unfortunately, many projects often assume their readers are all experts and can understand the whitepapers with no difficulty. In reality, most blockchain projects are much more complex than Bitcoin. Therefore, if readers only know how Bitcoin works, they still cannot understand these projects’ whitepapers. If you want to draw potential developers to your platform, it is necessary to provide a beginner’s guide to understanding your whitepaper.

That’s why we have prepared this guide. But before reading this guide, you can quickly go through our website, read our slogan, watch the promo video on the homepage, download the whitepaper and before long, you may find something you cannot understand. Don’t worry, let’s start with aelf’s slogan:
Aelf, a Decentralized Cloud Computing Blockchain Network

Cloud computing is the most fundamental feature driving the entire aelf blockchain ecosystem. Running data intensive computation on multiple computers is obviously more cost-effective than on one mainframe computer. Suppose these computers are assembled in a huge building called data center, say thousands of computers, with professional maintenance by a company, say, Amazon, then these data centers are called a cloud, such as Amazon Web Services (AWS).

Having said that, it is still hard for a beginner to understand why cloud computing gives aelf an indispensable edge. This is because most people, including some in the blockchain sector, don’t have a sound knowledge of some of blockchain’s key concepts. As a result, it is difficult for them to move on to the more complex technology, let alone analyze the pros and cons of a blockchain project and its potentials. As far as I know, I think it is necessary to set the record straight on two important blockchain concepts.
What is a blockchain?

This is nonsense! We all know blockchain is a tamper-proof distributed ledger or database technology, as any professional would explain to you. You most probably have memorized this definition by heart and would rattle it off whenever someone asks you what blockchain is. The truth is, this definition is very misleading. Blockchain is not a new invention, nor does it have any magical features (for example: the magical tamper-proof feature). In this sense, it is different from the magical stuff in an alchemist’s furnace. Instead of viewing blockchain as a ledger or database, it is better to see it as a distributed system. So what is a distributed system?

A distributed system is a large number of interconnected computers, which makes it a peer-to-peer system. It was invented around 1960, long before the advent of Internet. There are already a lot of well-known distributed-system-based softwares, such as Bit-torrent and Netflix. In these softwares, people can upload the files on their computers to the P2P network and anyone can download them. But a distributed system can do much more. In the distributed system discipline, people have to solve a big problem, that is, everyone (every node) in the P2P network need to make an unanimous decision no matter what information they receive, and this unanimous decision is what we call a consensus, and this problem is called the Byzantine General Problem.

Say there are three Byzantine generals wanting to attack the same fortress, and they are at three different locations, they could only rely on couriers to send messages. In this situation, any general can only make a decision based on the other two generals’ messages. If one general wants to attack, he let couriers send the “attack” message to the other two generals, so do the other two generals. If the generals are all loyal, each of them should receive “attack, attack” coming from other two generals, and all three generals would attack the fortress. But if one of them is a traitor, he could send one general “attack” and send the other “retreat”, this other general will receive “attack, retreat”, if he follows majority rule, he will not make a decision because the votes on attack and retreat are the same. At the same time, the other general will attack, and the result is that these three generals will not reach a consensus on attack.

The generals are just like the nodes of a distributed system (i.e. blockchain). There are at least two points worth noting: first, all massages (transactions), have to be sent to the other generals (nodes) to keep them informed; second, all the nodes have to reach a consensus.

The first point means that it takes time for sending a message to all the nodes in a huge network, the second means that after a new block has been broadcast to the entire network, there should be a mechanism for all the nodes to agree on this block (a package of messages or logs), and it also takes time.

https://i.ibb.co/HTYb2HB/Ef-N-R9-WUEAApnjr.jpg (https://ibb.co/hFH4MmL)

A Beginner’s Guide to Understanding the aelf WhitePaper (Part 2)

https://i.ibb.co/gvvcfxn/0-Nz-Ua2yt-Qv-OSRn-JA.jpg (https://ibb.co/f88Tysc)

If you have read the whitepaper of some blockchain projects, you might find them difficult to understand or even make no sense. As a result, readers (not speculators) are often at a loss as to what these projects are trying to do. Unfortunately, many projects often assume their readers are all experts and can understand the whitepapers with no difficulty. In reality, most blockchain projects are much more complex than Bitcoin. Therefore, if readers only know how Bitcoin works, they still cannot understand these projects’ whitepapers. If you want to draw potential developers to your platform, it is necessary to provide a beginner’s guide to understanding your whitepaper.

Yesterday we talked about what is the blockchain, today we would like to introduce the smart contract.

What is a smart contract?

The definition of smart contract in many books, articles and videos is very misleading from a developer’s point of view. They often explain that smart contract is a new generation of legal contract, deed, or proof of ownership, etc., and since they is code-based, smart contracts are highly intelligent. But this definition is only for those working in finance or other sectors who do not know computer science and coding. They need only to know that smart contract is very powerful, and that’s enough (in some sense, this is all very well). But what is smart contract exactly?

In fact, smart contract is neither smart nor is it a contract, it is just a string of code. So why do people call it smart contract rather than a more intuitive name? That’s because it has been called smart contract all along, and programmers are too lazy to change the name. Smart contracts, like Python or Java codes, are written in a high-level language, and compiled into bytecode to be run as opcode on a virtual machine. You might already know things like JVM and Python-VM, or EVM on the Ethereum blockchain. For the aelf project, smart contracts are written in C#, and they are run on the .NET framework after being compiled.

Calling the execution of a smart contract is in some sense similar to making an http request: In a traditional requesting process, you type in a URL to tell the remote server to send you back some data (html, css, javascripts, etc.), or tell the server to execute some server-side programs which could be written in Java to change some states of the server. The same is true for smart contracts. Just like a request, we send a transaction to the target contract address, whether it costs cryptocurrency or not. When the contract receives the calling request from the transaction, it will execute some specific functions in the smart contract code, depending on the parameters in your transaction. If there is enough gas, the executing result will change this smart contract’s state, send you the data of the result, or send you cryptocurrency.

However, in comparison to the instant response from a remote server after an http request, the execution of a smart contract will take some time after you send a transaction. As I have mentioned in the Bingo game article, when you send a transaction, the transaction will be broadcast to as many nodes as possible, and every mining node will include it into its candidate block. After a while, when one mining node produces a new block, it will broadcast this block to other nodes, of course, this block is confirmed. This process will take some time, and for most real applications only producing one new block cannot guarantee the safety and validity of the transaction, so more blocks should be concatenated consecutively after this block. On the aelf blockchain, at least 8 new blocks should be generated after the production of the block containing the transaction. Of course, if one block containing this transaction is finally packaged by a mining node, when satisfying a certain consensus condition, the target smart contract is then executed on a full node (full node can be a mining node, or vice versa). But with more and more blocks being generated after this block, it will be virtually impossible to tamper with the execution result of this smart contract by forking to another chain.

In the Bingo game example, the “bet” button is such a method in our smart contract. When we place a bet, a transaction is sent to the contract. After one block is packaged, the method is executed and thus the contract will know how much you want to bet. In order to let the contract know your bet amount and to avoid anyone tampering with your bet amount, you have to wait until 8 subsequent new blocks are produced. So how long does it take? As is shown in the last article or in the demo video, it takes about 30 seconds. In fact, no one knows exactly how long does it take to generate 8 blocks, but we know that after 30s more than 8 blocks must have been already produced.

Having explained these two basic concepts, it is much easier to understand any blockchain projects, including aelf. No matter how sophisticated the technologies a blockchain project applies, they will all be based on these two concepts.

In the next article, we will dive into the aelf blockchain whitepaper to demystify all the important features of this enterprise-level project! To be continued.

https://i.ibb.co/z4HPhdC/Ef-Sspd-YU8-AIQzk-P.jpg (https://ibb.co/QKjYF0h)

https://i.ibb.co/Lvf5r70/Ef-Xv-Jz-TUc-AEAkx-X.jpg (https://ibb.co/b7nJF96)

The launch of BancorV2 has generated lots of buzz in the last few days.

aelf Resource Token is based on Bancor, which ensures the instant exchange between resource token and ELF.

In the future, aelf will also launch its own DEX and build a decentralized lending platform.

https://i.ibb.co/ZBfKtck/Efs-Opw-LUYAAIHFd.jpg (https://ibb.co/7nSV8r6)

https://i.ibb.co/k3r4ypP/Efnp-CWl-Uc-AAGG1-E.jpg (https://ibb.co/7gTnzH0)

https://i.ibb.co/GJyGLW6/Efsq-Z2-WU8-AA-r-Zf.jpg (https://ibb.co/ZJ5vPBj)

A breakdown of the aelf blockchain whitepaper — Part 1

https://i.ibb.co/MRmx5Z9/1-BEJE6b-JO317-J-wk-L4u-W9iw.jpg (https://ibb.co/55PgxG2)

Why cloud computing is a must

We have already mentioned that cloud computing is a key feature. For Bingo Game, the aelf team only deployed 2 simple smart contracts (compile a C# file into intermediate code and upload it onto the aelf blockchain by creating a transaction with a special contract). Anyone can compile C# contracts and deploy them on the blockchain so that other people can invoke the contract to do whatever they want, say, developing a DApp. If only a few people are using the aelf blockchain, then it does not really matter. However, for any enterprise-level scenarios, this blockchain architecture is a recipe for disaster, just think of the torrent of data flowing in a supply chain. Under such circumstances, the number of deployed contracts will be in the MILLIONS, and if they are invoked by a lot of people, the transactions and contract code executions can easily soar to BILLIONS! As mentioned, a full node or mining node (also “block producer”) executes contract opcode under the dotnet framework, if we give millions of contracts for this node to execute, it will take so long a time that no application can handle. Try to imagine if there are 2,500,000 contracts queuing up to be executed by a single computer before your contract is executed, it would be so frustrating! For a common blockchain, this is called “network congestion”.
It is therefore easy to see why a cloud computing solution comes in handy. Instead of using a run-of-the-mill computer as a full node, why not use a super-computer?

Why not run in parallel?

In addition to cloud computing, nodes can also run smart contract code in parallel on the aelf blockchain. Before aelf, smart contracts on all blockchains are executed in a single-threaded way, like the event loop of the Javascript engine. But the aelf team, excelling at C#, found that the C# infrastructure can support parallel execution, so they applied this feature to the design of the aelf blockchain architecture. Combined with some designing patterns, the aelf team finally designed this mechanism, ushering in a new era of blockchain nodes with parallel execution.

For example, suppose there are 1,000 tasks to be executed (transactions or contracts), the aelf system will first check if these tasks change the same value simultaneously, if they do, then they will be executed in sequence because we don’t want these tasks to conflict with one another during parallel execution. If they don’t, then these non-conflicting tasks can be executed in parallel where they are divided into several groups according to whether they conflict with each other. So the result will be, say, 4 groups: [200 tasks, 300 tasks, 250 tasks, 250 tasks], and the overall execution speed will roughly be 4 times faster.

Just like Marvel superheroes assembled together to fight Thanos, aelf combined cloud computing and parallel processing to make sure any enterprise-level use cases have a seamless experience. Now let’s dive deeper into the technical stuff..

Delegated Proof of Stake (DPoS) and aelf Delegated Proof of Stake (AEDPoS)

As mentioned in “What is a blockchain” in the last article, in a distributed system, it always takes time for a transaction or a block to be broadcast to every node when there is a large number of nodes involved. We know that in the Bitcoin system, only mining nodes are responsible for producing new blocks, so why not reduce the number of mining nodes as much as possible? As a result, the Delegate Proof of Stake(DPoS) consensus mechanism came along. Proof of Stake is a variety of consensus algorithms that use something (for example, the token amount) as stake to package new blocks, the higher the stake, the likelier this new block will be confirmed. In DPoS, there aren’t so many mining nodes (strictly speaking, there is no mining concept in PoS, rather, they are called validating nodes), because we simply delegate a very few validation nodes to produce blocks and broadcast them to other delegated nodes. Clearly, DPoS solved the problem of long broadcast time in the blockchain distributed system. However, since there are only a few validating nodes at play, how can we prevent these nodes from plotting with each other to manipulate the whole chain and undermine the decentralized principle? That’s why all types of DPoS have a strict voting mechanism to ensure these elected delegates act fairly and transparently.

In fact, DPoS stems from the EOS blockchain project. In DPoS’s design, there are at least three types of nodes: block producer (BP, or less strictly, mining node), candidate node and common node. The candidate node is a block producer (BP) candidate who applies for the role via a smart contract. Theoretically, any common node with sufficient computing power (in aelf, we recommend a computer with at least a 8-core CPU, 8GB of RAM and 500GB SSD) can be a candidate node. In practice, only a small fraction of them can be real BP through voting by other common nodes. On the financial side, a typical blockchain project which chose DPoS as its consensus mechanism always rewards nodes with some tokens if they vote for candidates, thus encouraging participation. The voting mechanism is essentially a smart contract with voting methods that request voting node’s address, who it votes for and how many tokens they want to stake (the higher the stake, the greater the vote weight). In aelf, we don’t know how many common nodes can become candidate nodes, but only the 17 candidate nodes with the most votes can become a BP.

With some special techniques, aelf has upgraded DPoS to the unique AEDPoS (aelf DPoS). The creators have drafted a specific suite of round-based block production mechanism. If you look this up in the whitepaper you’ll see lots of mathematical expressions, but don’t worry, the core concept behind it is quite simple and straightforward.

Before explaining, let me remind you of two things: First, the real random number generation method (we’ll talk about this in details in the next articles). This method can not only generate a random number, but also shuffle a collection (say, a list), which makes the process impossible to be predicted, manipulated and plotted. Second, the Byzantine General Problem. Let’s have a quick recap of this problem: formally proposed by Lamport et. al in 1982, the Byzantine General Problem imagines a three-generals scenario, as was mentioned in the last article, if anyone of the three is a traitor who wants to alter the message, it is impossible for the three of them (the whole system) to reach consensus. Based on this observation, Lamport deduced that in the case of 3n nodes (n is a countable number) in the system, if there are at least n nodes who are traitors, the whole system can never reach a consensus. So in many other articles, you can always see the following statement:

If there are f evil nodes, there should be at least 3f+1 nodes for the distributed system to be useful.

In aelf’s DPoS, if the aelf main/test net is launched, the default setting is 2N+1 BPs, in the first year N=8, and N increases by 1 every year. There are 17 BPs at the very beginning. If 13 (no more than 5 BPs corrupt the network) of them behave normally, all the BPs will finally reach a consensus. Under this condition, aelf defines a round in which every BP packages blocks sequentially, and after that, aelf randomly picks a BP to package blocks. After this round, we shuffle the BP list, and repeat this process. The key is that the block production sequence is random enough to prevent BPs from plotting with each other. Of course, there are other designs involved, but we don’t need to know them to understand how AEDPoS works.

Like common DPoS, the BP list is always changing based on their votes. A common node can vote for BPs and candidates at any time (the aelf blockchain now supports this feature), and the aelf system will check the ranking every month, those who are at the bottom will be replaced by candidate nodes with higher rankings.

📢🔥 ATTENTION, please!

aelf Wallet is now available on Android and iOS!

Click the link 🔗 to download and try it out!

Android: http://d.alphaqr.com/aelfwalletandroid

 IOS: https://testflight.apple.com/join/TclFysmO

https://i.ibb.co/k6tzcW6/Ef3-Bd-6-UEAAZz-Ij.jpg (https://ibb.co/5xPCcfx)

https://i.ibb.co/PgsySWg/Efxx7-S5-U0-AAJIs-P.jpg (https://ibb.co/ZxRrZgx)

https://i.ibb.co/yXQZwbG/Ef8-Fl-Li-Uc-AAbg-Hr.jpg (https://ibb.co/XbCKhvN)

A breakdown of the aelf blockchain whitepaper — Part 2

https://i.ibb.co/RNShBYg/1-uty5rah3mr-P6h-KDQMe-CEAg.jpg (https://ibb.co/sCP56bg)

Breaking down the aelf side-chain

Cloud computing, parallel processing, and AEDPoS have greatly improved the execution performance of any kind of smart contract, but when they are applied to enterprise-level scenarios, new problems crop up. To begin with, in software design, it is a rather bad idea to program all the methods in the same class. We always write a series of classes to inherit a base class, in order to decouple the functionalities and make the class extensible whenever needed. The same also applies to blockchain design. Second, since all the data and transactions are accessible to anyone through a blockchain explorer, if we put the smart contract and data of different enterprises or government sectors on a single blockchain, then everyone can see them, which means there will be no data privacy. Although there are encryption techniques which can mask data, such as zero knowledge proof, it is always better to put the data of different enterprises on different blockchains.

Based on these considerations, long before other projects even realized it, aelf proposed that side-chain technology should be applied to this scenario. Unfortunately, for someone who is new to blockchain, it is almost impossible to understand how side-chain works. Side-chain is not what it literally means, it is not subordinate to the main chain. On the contrary, a side chain is a blockchain distributed system with the same functions and nodes as a main chain (say, the aelf blockchain). As mentioned above, we can put the data of different enterprises on different blockchains. This means we can build many blockchains, and work magic (of course not magic in its literal sense) to make these chains connect to the aelf main chain (in fact, we can call any of these blockchains a main chain and the rest side chains). Currently, the most popular method of connecting any two blockchains, which we also call cross-chain, is using a middle-man. When we want to use bitcoin to play a decentralized game on Ethereum, we need to send a transaction with some amount of bitcoin to a locking bitcoin address, then the middle-man will exchange the locked BTC for ETH at a certain exchange rate and allocate to you the equivalent amount of ETH on Ethereum, which you can use for playing games.

But in aelf, we use a metadata indexing method, which is more straightforward. Unlike other projects who built on the blockchains of those already successful projects (such as Ethereum or the HyperLedger fabric framework for consortium blockchains), the aelf team has writen all the code and build the infrastructure from scratch. From the beginning, the aelf team has defined how the data structure of a blockchain, a block, a transaction etc. should look like in C#. In an aelf blockchain data structure, there is an attribute called blockchain ID, which is a unique hash; and in block data structure, there are several attributes called blockchain ID , Merkle tree root and related side chain block list. There is also one more important thing: all of aelf’s data structures are serialized and stored in Redis (a popular key-value pair database system), so is the side chain information. As a result, as the aelf main chain is growing with block production by BPs, other side chains can send transactions to cross-chain contracts, which then execute the related code to connect to the main chain’s network port and request the main chain to index the side chain block and pay the indexing fee.
The core issue here is how to index a side chain: when a main chain (the block data structure on the main chain, or the data records with main chain ID in Redis), receives a request from a side chain, it adds the side chain’s block head data structure to the related side chain block list, which means theoretically we have indexed or related a side chain. We have mentioned that there is also a blockchain ID in each block, this attribute allows a main chain to index blocks from different side chains. When a user on a main chain wants to access data on a side chain or vise versa, they just need to find the target block on the main chain and its related side chain block list, and then find the target block on the side chain via key indexing.

As we will explain later, blockchains for different application scenarios generate blocks at different speeds. Under such circumstances, a chain with slower speed might index many blocks from a chain that produces blocks faster. This method can be applied to scenarios such as forking.

In practice, we can build any number of blockchains, and relate it via indexing to the aelf main chain, with a specific category of smart contracts running on each of them. For example, we can allow only banking-related smart contracts deployed on a specific blockchain, and e-commerce smart contracts on another. Our whitepaper summarizes it best:
One chain, one contract.

Moreover, the indexing method can make many blockchains into a hierarchical tree structure, the root being the so-called main chain. That’s because a related blockchain can then again index another blockchain as its side chain, and the process can keep going on. Logically, this is in perfect accordance with hierarchical taxonomy, for example, the financial sector has many subcategories, such as banking, lending, investment and insurance, and under investment banking, there are venture capital, investment bank etc… Each subcategory is supported by an indexed blockchain.

So how do these blockchains collaborate in a distributed system? First we need to be know that any node in a distributed system is just a software instance running on your computer, or a process. In TCP/IP, a node is allocated a port number, so we can run any number of this type of instances on a computer. However, each instance has its own port number: we can run several blockchain nodes, one IPFS node, one bit-torrent node and etc. simultaneously. In aelf, you should first start a main chain instance, and then you can build and run a side chain instance. Transactions broadcast on the side chain are collected by the BP nodes (block production nodes) on the main chain. When smart contracts deployed on the side chain is triggered, the BP and full nodes on the main chain will run them.

Aelf — a blockchain based operating system

To perfect the design of our software system, aelf made the system extensible, flexible and pluggable. Just as there are thousands of Linux OS with only one Linux kernel. As Ethereum Founder Vitalik Buterin has explained, Ethereum can be seen as a world computer because there are lots of smart contracts running on it, and the contract execution results are consistent in all the distributed systems around the world. This idea is also embedded in aelf’s system and we call it a “blockchain infrastructure operating system”, or a distributed operating system.

Just like any OS, aelf has a kernel and a shell. In fact, aelf’s kernel is not something like a Linux kernel, it is just an analogy. There is a special concept in aelf’s kernel called the minimum viable blockchain system, which defines the most fundamental aspect of a blockchain. If a developer wants to create a new blockchain system or a new blockchain project, he does’t have to start from scratch, instead, he can directly extend and customize using the aelf blockchain open-source code. The technologies described above are all included in the minimum viable blockchain system. With these, anyone can customize:

- Block property: block data structure, block packaging speed, transaction data structure, etc.

- Consensus type: AEDPoS is used by default, but you can also use incentive consensus, like PoW and PoS. And you can also use the consensus of traditional distributed systems, like PoS and Practical Byzantine Fault Tolerance, or PBFT. In fact, the f evil nodes of 3f+1 nodes are the upper limit for any distributed system to reach a consensus, which is called the Byzantine Fault Tolerance, or BFT. In order to do this, there is a specific algorithm, but in 1999, a much more efficient algorithm to reach this consensus came along, that is the PBFT. In scenarios like private blockchain or consortium blockchain where there is no need for a incentive model, PBFT will be a good option.

- Smart contract collection: In aelf, there are many predefined smart contracts that can be used directly by other contracts, such as token contract, cross-chain contract (also called CCTP, or cross chain transfer protocol), consensus contract, organization voting contracts, etc. Of course, you can also create your own contract with a brand new implementation logic.

- Others.

Summary

So this is our breakdown of the aelf blockchain whitepaper. In previous articles, we first introduced two basic concepts which are often misinterpreted by other articles. After helping you get these two concepts straight, we then introduced aelf’s vast arsenal of powerful technology. If these articles helped you understand the aelf blockchain better, then I have reached my goal. But I must advise you to read the whitepaper for a more detailed explanation. With all this knowledge at your disposal, I believe you will be much more comfortable developing DApps on aelf.

📢AMA Announcement 🔥

 ❗️Dear community members, aelf will hold a Live AMA with aelf COO @czhuling on Telegram https://t.me/aelfblockchain!  Come and talk about DeFi with @czhuling!

Time: August 28, 5pm - 6pm (GMT + 8)

Research the aelf project and prepare some good questions!
(Users who do not follow the rules below will not be able to share out the prize pool.)
1️⃣Twitter Session (15 Questions)
2️⃣Live Session (10 Questions)

Rules :
1️⃣Join the aelf community on Telegram https://t.me/aelfblockchain
2️⃣Follow us on Twitter @aelfblockchain https://twitter.com/aelfblockchain
3️⃣Like, Retweet & Tag 3 Friends and Comment With Your Questions  https://twitter.com/aelfblockchain/status/1298199934781411328

https://i.ibb.co/LQ4ygbV/photo-2020-08-25-13-26-17.jpg (https://ibb.co/s5L41k8)

What is AMM (automated market maker)?

AMM, short for automated market maker, is an innovative trading model derived from Defi projects. Unlike the traditional order book transaction model, AMM decentralized market makers and automated trading process.

Everyone can put token into the liquidity pool, become a small market maker, and then enjoy the profits from trading pair service fees. Funds in the liquidity pool are controlled by decentralized open source contracts, and AMM transaction data are all on the chain.

https://i.ibb.co/1Qzx6TK/photo-2020-08-26-23-01-14.jpg (https://ibb.co/YQ0GZh8)

aelf is Testing AESwap Internally

https://i.ibb.co/QMHfxCn/1-Dzxd-ODfks-U4k-Ny02n-WEirw.jpg (https://ibb.co/Yhd3Vy8)

In 2020, Ethereum’s DeFi ecosystem saw exponential growth and DEX (decentralized exchange) boomed. Against this backdrop, aelf officially launched AESwap, a decentralized trading platform.
AESwap is a smart contract protocol based on the aelf network, which adopts the constant product market maker (CPMM) model. No need for pre-mining and financing is a distinct feature of the project. Once it goes live, the product will offer free access to users around the world and help all people to participate in the open financial market. The follow-up funds will be managed by the aelf DAO Management Committee to ensure the project runs securely and efficiently.

AESwap is the first DeFi project based on the aelf network, with complete DeFi supporting infrastructure, including cross-chain assets, interoperability solutions, stablecoin, etc. AWSwap aims to be the world’s leading automatic trading platform and offer a more efficient, convenient and secure DeFi product than Uniswap. The mobile version of AESwap integrates the templates of aelf account management, which makes it easier to learn and get started and is more user-friendly.

The mobile version of AESwap (Closed Beta) has completed phase 1 of feature development and will be available for public testing soon. The desktop version is still under development. AESwap Phase 1 mainly provides two major features, one is that market makers make money by adding liquidity to trading pairs and they can also create trading pairs. The other is that token holders can exchange one token for another token by paying a 0.3% transaction fee, which will be used as the market makers’ commission. The protocol does not charge any commission.

AESwap Highlights:

Performance: Low transaction fee, fast trading without delay
Security: Self-developed based on the aelf network, High Security
User-friendly: Ease of use, available on both mobile and desktop
Profit: Achieve asset interoperability with adequate liquidity

At present, compared with many DEX, the biggest advantage of AESwap is “Transaction Speed”. Although Ethereum currently has the most popular DeFi ecosystem, it cannot handle high transaction throughput and fully support the expanding DeFi ecosystem until the Ethereum network adds layer 2 or upgrades to 2.0.
The underlying public chain of AESwap is the aelf network, so there will be no network congestion. Aelf adopts the main-side chain structure, which uses one chain for one specific scenario and thus can truly realize resource isolation, ensure transaction efficiency and avoid high gas fees. At the same time, under the premise of the main chain security, the side-chain and the main-chain can share security. Moreover, AESwap is independently developed by the aelf team, and its security is guaranteed. Recently, YAM’s collapse due to the existence of loopholes in the smart contract has caused a great stir, so contract security is also very important.

Aeswap liquidity pool uses a constant product market maker model to execute transactions, abandons the concept of limit order book, and can automatically adjust the exchange rate according to the available liquidity. Therefore, it can achieve fast trading and ensure the persistence of capital flow. Constant product can be regarded as an inverse proportional function x * y = K. No matter how x and y change, K is always a constant value. In AESwap transactions, the product of the tokens’ number in the liquidity pool is constant before and after a transaction, that is, the product before the purchase = the product after the purchase.

Because Ethereum platform has issued the largest number of cryptocurrency assets, the exchange’s value would be significantly reduced if it could not access these assets and the original ETH. aelf also takes this into account, so it will provide a set of interoperability solutions with other public chains’ tokens. AESwap will support the migration of Ethereum token. By reducing the cost of user migration, users can easily migrate to the aelf platform by using Ethereum token instead of purchasing or exchanging other aelf tokens to ensure sufficient liquidity and reduce the risk.

As the infrastructure of aelf ecosystem, AESwap is the basic tool to realize token trading. In the future, aelf will lay out other derivatives applications based on AESwap, form a stable financial system, and promote the prosperity of other APP and related token. In addition, AESwap can also be connected with other APP on aelf DeFi ecosystem to promote each other. In the future, the aelf will launch the AESwap public testing. Please stay tuned!

https://i.ibb.co/LzxmR2j/Egz-OS8m-Vg-AA4-BFr.jpg (https://ibb.co/mC9kTMZ)

📢We are thrilled to announce that AESwap Internal Testing goes live today!

The internal testing is only open to members of the saelf governed community.

⏰ 4th September - 10th September

Download AESwap🔗:
iOS: https://testflight.apple.com/join/tpHwB5t9
Android: http://d.firim.info/anaelfMarketMaker

Rules:
1️⃣Only available for members of the saelf governed community.

2️⃣Please fill in the form to collect test tokens. Apply for AESwap Test Token (https://docs.google.com/forms/d/e/1FAIpQLSfbQd1KEJQqxGXZ01dvQirN4rAg4mQ7HHl62-lSjPEkMhAlPQ/viewform?usp=sf_link)

3️⃣Share your feedback in the saelf governed community.

Once we optimise the app, the public testing will start soon.🤟

☑️AESwap does not charge any transaction fees (Gas fees). Only 0.3% commission is used for token swap. Currently, the protocol does not charge commission.

☑️Anyone can become a liquidity provider in AESwap, whoever adds liquidity to the pool can get profits from the transaction.

https://i.ibb.co/6XJmJ3v/1.png (https://ibb.co/g4F3F5v)

https://i.ibb.co/Jtmsdb6/Eg6-Mzql-U0-AAh8s0.jpg (https://ibb.co/mTbcBYZ)

Introducing Sashimi, a Fair Version of Sushi, with No Team Shares, No Pre-mine and a Cross Chain Swap Ecosystem!


https://i.ibb.co/s2b6FfK/photo-2020-09-10-16-43-44.jpg (https://ibb.co/56Gn50r)

Following the release of AESwap, a decentralized trading platform and the first DeFi project on aelf network on August 28, aelf is launching SashimiSwap, its version of SushiSwap today!

What is SashimiSwap?

SashimiSwap is a new SushiSwap project developed by aelf. Like other types of swap products, it adopts the model of automatic market maker(AMM). However, SashimiSwap is not a fork of Sushiswap, thus the two do not share liquidity. Once launched, anyone can participate in staking and mining on SashimiSwap! As an “upgraded & simplified SUSHI”, SashimiSwap is very easy to get started with and offers a smooth mining experience and high yield.

SashimiSwap gives liquidity providers on UniSwap an opportunity to earn SASHIMI tokens. UniSwap’s liquidity providers can stake some of their LP tokens and start earning SASHIMI tokens at block height 10,833,000 (around 10:00 am on September 10, SGT). We use the same token allocation mechanism as Sushi, with a 10x bonus (end height 10,933,000) for the first 100,000 blocks, which means we’ll release 1,000 SASHIMI tokens in each of the first 100,000 blocks. After 100,000 blocks, each block will release 100 SASHIMI tokens.

And the most important part is…

In the early stage, the 10 liquidity pools that can participate in mining are: ETH-USDT, USDC-ETH, DAI-ETH, YFI-ETH, LEND-ETH, LINK-ETH, SNX-ETH, ELF-ETH, WBTC-ETH, SASHIMI-ETH.

Unlike SushiSwap, which distributes 10% of its funding each time to the founding team for development, future iterations, audits, etc. SashimiSwap did away with such “development funds”. SashimiSwap charges a 0.3% transaction fee, of which 0.25% will be used to reward users for adding liquidity. After the aelf mainnet is launched, the remaining 0.05% will be sent to SASHIMI DAO contract, which will all be used for community governance.

SashimiSwap is committed to creating a fairer and more transparent DEX platform. It is already connected to Uniswap and will be connected to AESwap soon. The aelf team will continue to focus on R & D, achieve asset swap between SashimiSwap and AESwap via CCTP and other ways, thus creating a permissionless and decentralized cross-chain DEX.

Aelf is committed to making SashimiSwap a fairer and more transparent DEX platform. Now we are connected to Uniswap, and we will connect it to AESwap soon. The aelf team will continue to focus on R & D, achieve asset swap between SashimiSwap and AESwap via CCTP and other ways, thus creating a permissionless and decentralized cross-chain DEX.

The mobile version of AESwap (Closed Beta) has completed phase 1 of feature development, and the internal testing is ongoing within the saelf governed community. The public testing will be available starting September 11.

What features does AESwap provide?

1. Market makers can make profit by adding liquidity to trading pairs.
2. Allow market makers to create trading pairs.
3. Users can swap one token for another.
4. Users can withdraw their shares from the liquidity pool any time.
5. Users do not need to register an account. They can log in using the account of aelf Wallet, web wallet and aelf Explorer Extensions.
Learn how to use AESwap in this video: https://youtu.be/lVM5p1YTyig

After the mainnet launch, SashimiSwap and AESwap will be integrated. Users can swap and stake tokens on the aelf network, which can reduce gas fees and ease the issue of network congestion on Ethereum and prevent unexpected losses.

It’s pretty exciting to see decentralized and community-governed products like SashimiSwap which require no pre-mining, no investors, and no funds for the dev team. Various new fair launch products are considered as the future trend of DAO, as well as a new form of financing.

Missed Sushi? No worries, you are in for a Sashimi treat! Try out SashimiSwap now and give us your feedback!
SashimiSwap Website: https://sashimi.cool/farms
SashimiSwap Community (Telegram): https://t.me/SashimiSwap
SashimiSwap Community (Discord): https://discord.gg/zTdmUkb

#aelf101 Click the image to check out:

1️⃣ What is multi-signature address?

2️⃣ What is Oracle?

https://i.ibb.co/QbcfHW1/2.jpg (https://ibb.co/M2hs1z3)

💥Good news! #Binance has opened BEP20 (Binance Smart Chain) deposits and withdrawals for $ELF! Check out more 👉
https://www.binance.com/en/support/announcement/ca94b7a6751b4b2b9451f7a3ceb8dbce

aelf Enterprise v1.0.0 RC 1 Officially Released

https://i.ibb.co/Sd6w8zp/photo-2020-10-16-13-01-14.jpg (https://ibb.co/4YFRGHx)

On October 16th, aelf Enterprise v1.0.0 RC 1 has been launched. It is an upgraded version of aelf Enterprise V1.0.0 Preview 3, including a complete blockchain ecosystem, development suite, and developer documents for basic applications and services. aelf Enterprise v1.0.0 RC 1 has been optimized in node management, contract implementation, configuration contract, performance, scalability, and user experience. With a more comprehensive commercial blockchain solution, this version can provide a safe, stable, and efficient development environment for developers.

In addition, aelf Enterprise v1.0.0 RC 1 focuses on the user experience of developers, by making it easier to get started with. It has also added new access interfaces for developers, making it easier to use and offering a more user-friendly experience on DApp development.

aelf Enterprise v1.0.0 RC 1 is an enterprise-ready integrated blockchain solution. The ‘main chain + multi-side chain structure’, ‘cluster’ data center, parallel computing system, AEDPoS consensus, and multi-governance model can facilitate the deep integration of various applications with blockchain technology. The Public Testnet Code has been upgraded to aelf Enterprise v1.0.0 RC 1 and all functions required for Mainnet launch have been deployed. Supporting features, such as the test wallet for Android, iOS, and Testnet, in addition to the Testnet Blockchain Explorer will be upgraded at the same time.

The aelf Public Testnet has achieved all the functions planned for the Mainnet launch. Based on aelf Enterprise v1.0.0 RC 1, community users can try out the functional modules of aelf’s Mainnet right now. It is worth mentioning that the aelf Public Testnet has been running smoothly. aelf Enterprise 1.0.0 RC 1 will be the version for code auditing in near future. After the code audit is completed and the vulnerabilities found are fixed, the Mainnet will be gradually launched with this version according to Mainnet launch roadmap.

▋ aelf Enterprise v1.0.0 RC 1 System Integration

1. aelf Enterprise
- aelf v1.0.0 RC 1
- DevKit v1.0.0 RC 1

2. aelf External Applications
- aelf Blockchain Scanner v0.4.1
- aelf Scanner Mysql plugin v1.0.0 RC 1
- aelf Explorer v1.0.0 RC 1
- aelf Wallet v1.0.0 RC 1
- aelf JS SDK v3.2.34
- aelf-Bridge v0.0.9
- aelf CLI in Nodejs v0.1.43

3. aelf Browser Extension v1.1.3

▋ What’s New

1.What’s new about aelf Enterprise

1.1 aelf v1.0.0 RC 1
https://github.com/AElfProject/AElf
- Optimised node management and discovery in network layer.
- Optimized contract execution step plan.
- Configuration contract is decoupled and optimized.
- Added contract execution restriction management.
- Simplified transaction result error information of Web API.

1.2 Devkit v1.0.0 RC 1
- aelf-boilerplate: https://github.com/AElfProject/aelf-boilerplate
- Developer documentation: https://docs.aelf.io/

2.aelf External Applications Update

2.1 aelf Scanner Mysql plugin v1.0.0 RC 1
- Adjusted compatibility

2.2 aelf explorer v1.0.0 RC 1
- Fixed some bugs
- Adjusted the logic of extension login

2.3 aelf wallet v1.0.0 RC 1
- Fixed some bugs

3.aelf Browser Extension v1.1.3
- Removed redundant permission operation to make it easier for developers to get started.
- Added new unlock pop-up window to offer a more user-friendly experience on Extensions’ DApp development.
- Added new interface for developers to get new versions.

From now on, aelf will focus on analyzing exception cases based on the running of aelf Enterprise v1.0.0 RC 1. At the same time, aelf will carry out deep and systematic research on system stability, performance and security. The team will continue to explore the heterogeneous cross-chain communication and economic system designs.

aelf Enterprise v1.0.0 RC 1 is a full display of aelf’s latest technical updates and the R&D achievements of the mainnet. Mainnet preparation has been going on in accordance with the Mainnet launch Roadmap. More details will be published in the near future! Aelf will continue to strive for excellence, providing users with high-performance, stable, and reliable blockchain infrastructure.

aelf Will Launch Mainnet on 10th December

https://i.ibb.co/0Z02L8R/E0.jpg (https://ibb.co/4MbtL9n)

On June 30, 2018, the aelf testnet was launched. Now it has been running smoothly for more than two years. During this period, aelf has hosted various initiatives to encourage users to participate in product testing and share with us their valuable opinions. At the same time, the aelf team has been constantly improving and enriching the technology, aiming to provide users with a high-performance, user-friendly, and reliable large-scale commercial blockchain infrastructure.

Since the release of the aelf mainnet launch roadmap, much progress has been made. Now, the aelf public testnet has achieved all the features required for the mainnet launch. The official release of aelf Enterprise 1.0.0 RC 1 and the successful conclusion of the aelf Public Testnet Code Audit Bounty Program also mean we are one step closer to the mainnet launch.

To advance the mainnet launch process, we have updated the aelf mainnet launch roadmap. According to the roadmap, our next major milestone is: launching the aelf mainnet on December 10!

Overall Roadmap

https://i.ibb.co/mc9Yt01/E1.png (https://ibb.co/VqghDxr)

Phase I

https://i.ibb.co/Qnjz2FQ/E2.png (https://ibb.co/gwFH5M9)

Phase II

https://i.ibb.co/N7jffB4/E3.png (https://ibb.co/6NPGGCd)

Phase III

https://i.ibb.co/7tznJx7/E4.png (https://ibb.co/TMT4BDz)

Phase IV

https://i.ibb.co/FDJk4fL/E5.png (https://ibb.co/vjmC4r6)

Phase V

https://i.ibb.co/ZVyXjMV/E6.png (https://ibb.co/qdbjSrd)

aelf will launch the mainnet following the steps in the above roadmap. The realization of each stage would not be possible without the strong support of the community. Let’s work together to ensure the successful launch of the aelf mainnet.