You are viewing a single comment's thread from:

RE: Life is a Cabaret... Or how to split and merge a blockchain.

in #eos7 years ago

something with "chain scoped id's" could work? any message will have an origin identifier which was generated using the chain's id / characteristics and render invalid on forks?

Sort:  

yes, something like that. It would be nice if there was a clear distinction between the two forked chains, but that's part of the problem - they've forked so in some sense they are both the original chain. REf: arguments about which is the correct BTC or which is the correct ETH... reduce to becoming power and brand fights.

With TAPOS or transactions as proof of stake, a transaction refers to its branch and therefore cannot be processed on the other fork. Which suggests it is hard to create a single message that is acceptable to both forks.

Coin Marketplace

STEEM 0.21
TRX 0.26
JST 0.040
BTC 100671.43
ETH 3655.73
USDT 1.00
SBD 3.14