F5 Room | Buôn Gió Muôn Nơi

Yukin · August 30, 2020, 8:38am

Không có , theo dõi 4room …có nó báo chớ tui lính lát sao biết được :))~

Kudinh · August 30, 2020, 9:01am

OK! Haha hành trình kiếm level bắt đầu.

Bobovl · August 30, 2020, 10:30am

Ok thanks bác. …

Yukin · September 3, 2020, 8:58am

Yukin · September 5, 2020, 5:42am

Cùng nhau thảo luận và khám phá xu hướng hot nhất hiện nay DeFi tại Binance Summit: “The World of DeFi”, vào ngày 10/09/2020 - 4:00 PM to 7:30 PM (UTC)

Chi tiết:

Yukin · September 5, 2020, 6:41pm

Muốn tạo topic ở đâu cũng đc, nhưng mà vô room nào thì phải nói tiếng đó.
Ra room quốc tế thì phải nói tiếng Anh, vô room Nga thì phải nói tiếng Nga…
Ra room quốc tế spam ad nó ban đấy :))~
VD: có ông nước ngoài nào nhãy vô nhà mình, xí xô xí xào … là mình điên lên liền =)))~

Yukin · September 8, 2020, 7:25am

github.com/ethereumclassic/ECIPs

ETC Core Devs Call 13 & 14

opened 12:51PM - 03 Sep 20 UTC

closed 06:00PM - 25 Sep 20 UTC

q9f

meta:5 call meta:1 governance

# ETC Core Devs Call 14 * When: **Friday, September 25, 2020, 4pm UTC,** 90 min…utes max * Where: [ETC Discord](https://discord.gg/x3WHgrU) * Focus: Mining Algorithm, Last-Call Proposals, and other 51%-Attack Solutions. ### Agenda * Last-Call Proposals * ~~ECIP 1049 KECCAK256 (Last Call)~~ Moved to call 15 on request * [ECIP 1099](https://ecips.ethereumclassic.org/ECIPs/ecip-1099) Calibrate Epoch Duration (Last Call) * 51% Proposals * [ECIP 1092](https://ecips.ethereumclassic.org/ECIPs/ecip-1092) 51-percent attack solution PirlGuard by Callisto (Draft) * [ECIP 1094](https://ecips.ethereumclassic.org/ECIPs/ecip-1094) VeriBlock Proof-of-Proof 51%-Attack Prevention (Draft) * [ECIP 1096](https://ecips.ethereumclassic.org/ECIPs/ecip-1096) 51% Attack protection system based on Bitcoin Merged Mining (Draft) * [ECIP 1097](https://ecips.ethereumclassic.org/ECIPs/ecip-1097) Checkpointing based 51% attack resistance (Draft) * [ECIP 1100](https://ecips.ethereumclassic.org/ECIPs/ecip-1100) Modified Exponential Subjective Scoring (Draft) Live-Agenda: https://hackmd.io/@q9/etc-dev-14 ~~_Please post all relevant proposals below that should be discussed and evaluated._~~ Agenda submissions are closed. Audio recording: https://youtu.be/_VChbJd87WM # ETC Core Devs Call 13 * When: **Friday, September 11, 2020, 4pm UTC,** 90 minutes max * Where: Jitsi * Web/App [ETCCoreDevsCall13](https://meet.jit.si/ETCCoreDevsCall13#config.startWithVideoMuted=true&config.startVideoMuted=true) * Dial in PIN `1401 7587 98` for [ETCCoreDevsCall13](https://meet.jit.si/static/dialInInfo.html?room=ETCCoreDevsCall13) numbers * Focus: Mining Algorithm, Last-Call Proposals ### Agenda * ECIP 1043 Fixed Dag Size Restriction (Last Call) * ECIP 1099 Calibrate Epoch Duration (Draft, alternative to 1043) * ECIP 1049 KECCAK256 (Last Call) * ECIP 1095 SHA3-256 (Last Call, alternative to 1049) Audio recording: https://youtu.be/9r_q_z81eh4

github.com/ethereumclassic/ECIPs

ECIP-1092 51attack solution: PirlGuard & Callisto proposal

opened 05:01PM - 07 Aug 20 UTC

closed 04:16AM - 21 Nov 21 UTC

Dexaran

type: std-core status:1 draft

--- lang: en ecip: 1092 title: 51% attack solution: PirlGuard & Callisto sta…tus: Draft type: Core author: dexaran (@dexaran) created: 8/7/2020 license: LGPLv3 --- # Abstract The following describes a method of preventing a 51% attack on Ethash-based POW chains. # Motivation Ethereum CLassic suffered a number of 51% attacks already. [Here](https://cointelegraph.com/news/is-etc-102-screwed-after-second-51-attack) you can find an article from Cointelegraph describing the 51% attack on 6 Aug 2020. [Here](https://cointelegraph.com/news/ethereum-classic-51-attack-the-reality-of-proof-of-work) you can find another article describing the 51% attack on 10 Jan 2019. As long as ETC protocol remains unchanged it is susceptible for more 51% attacks. # Specification The proposed solution refers to the [PirlGuard protocol](https://pirl.io/en/pirlguard-innovative-solution-against-51-attacks/). The description of the protocol states that instead of automatically syncing with any privately-mined chain branch the new protocol should require the peer proposing the privately-chain (and the reversal of the publicly mined and synced blocks) to mine a number of "penalty" blocks. The number of penalty blocks must depend on the number of the original blocks that would be reverted if the chain will reorganize and sync to the proposed (privately-mined) branch. Thus the cost of the 51% attack will dramatically increase as the attacker will not be able to mine his private branch and then broadcast it to the network thus reverting all the transactions from the "main" branch. # Rationale This protocol is already implemented in Pirl and Callisto Network. The protocol has a working time tested reference implementation. The proposed change requires minimal modifications of the Ethereum CLassic protocol while offers a reliable method of protecting against the recent attacks and the relevant threat of newer similar attacks. # Implementations Here is a reference implementation of the protocol in GO lang: https://github.com/EthereumCommonwealth/go-callisto/blob/master/core/pirl_guard.go https://github.com/EthereumCommonwealth/go-callisto/blob/master/core/blockchain.go#L1540 # Presentation Made by @padenmoss http://padenmoss.com/public/ECIP-1092_proposal.pdf # Copyright This ECIP is licensed under [GNU Lesser General Public License v3.0](https://www.gnu.org/licenses/lgpl-3.0.en.html).

Yukin · September 8, 2020, 4:25pm

gist.github.com

https://gist.github.com/Dexaran/b7c23ec264019665cffd35d35bc26ee9

Dexarans_amendment_to_Nakamoto_consensus.md

# Ultimate solution to 51% attacks: amend the Nakamoto consensus

#### TL;DR: 

The Nakamoto consensus is a set of rules that is intended to define a trustless peer-to-peer electronical cash system that can solve a double-spending problem without financial institutions involvement. It fails to do so in some circumstances.

The main flaw of the Nakamoto consensus is that it assumes the possibility to rewrite the history of transactions in the past up to a potentially unlimited point of time, while in reality not all **off-chain events** can be reversed up to any point of time. The flaw is expressed in "The longest chain is always the right chain" paradigm which is the root of all 'stealth mining' attacks. The new paradigm "**The longest chain is the right chain IF it does not suggests to reorganize more than `X` blocks of the already existing chain**" must be applied in order to make these attacks impossible.

**Another flaw of Nakamoto consensus is that it assumes that a node can trust itself**. In reality only a group of geographically spreaded nodes can trust that the whole group is on the correct chain if these nodes are at the same chain and these nodes trust each other i.e. they belong to a single owner.

This file has been truncated. show original

Yukin · September 17, 2020, 5:44am

github.com

bnb-chain/whitepaper/blob/master/WHITEPAPER.md

# BNB Smart Chain
**A Parallel Blockchain to Beacon Chain to Enable Smart Contracts**

_NOTE: This document is under development. Please check regularly for updates!_

## Table of Contents
- [Motivation](#motivation)
- [Design Principles](#design-principles)
- [Consensus and Validator Quorum](#consensus-and-validator-quorum)
  * [Proof of Staked Authority](#proof-of-staked-authority)
  * [Validator Quorum](#validator-quorum)
  * [Security and Finality](#security-and-finality)
  * [Reward](#reward)
- [Token Economy](#token-economy)
  * [Native Token](#native-token)
  * [Other Tokens](#other-tokens)
- [Cross-Chain Transfer and Communication](#cross-chain-transfer-and-communication)
  * [Cross-Chain Transfer](#cross-chain-transfer)
  * [BC to BSC Architecture](#bc-to-bsc-architecture)
  * [BSC to BC Architecture](#bsc-to-bc-architecture)

This file has been truncated. show original

Vanlinhnguyen · September 18, 2020, 12:23pm

Bác Yuk làm cái gì mà toàn mã hoá thế kia. Nhìn thoáng qua không hiểu gì gết

Yukin · September 18, 2020, 3:58pm

Bấm vô xem sẽ hiểu ! :))~

Vanlinhnguyen · September 19, 2020, 5:25am

Sao mình lập topic mà không biết nó nằm ở góc nào nhỉ. Rảnh Phá pHá chơi không biết nó bay đi đâu rồi

Xxnoproblemx · September 22, 2020, 4:10am

Xem level chỗ nào nhỉ.

Vanlinhnguyen · October 3, 2020, 8:36am

Ở đây

tandat97hg · November 17, 2020, 12:48pm

ha quá bạn ơi, mới tìm ra cách rep…

Tramnam1009 · November 27, 2020, 8:06am

Mình cần hỗ trợ. Mình lỡ rút xrp về ví trust nhưng không điền tag. Mình muốn hủy lệnh phải làm sao?

Viethungbkeps · March 13, 2021, 4:14am

Mình stake BNB trên ví trust quA ARARAT validator. Nhưng nay ko unstake, cũng ko làm gì đc với số BNB của mình ai giúp mình với ạ. Ví tên trust mà ko thấy trust chút nào
A4C6A31D8645A930D1495948772EC47B5D169FEF715D5B75671050CAD925FA6C

Yentrang0204 · September 5, 2021, 10:31am

Tại sao lịch sử giao dịch của đồng twt trên ví tự nhiên mất vậy?bạn nào thông thái làm ơn chỉ giúp