Upgrading Ethereum to Constantinople risks failure if it does not fully support every decentralized application and its full lifecycle. Constantinople must support all phases and features of all dApps or it will be considered a failure since dApps made for proof-of-work may break under proof-of-stake. The failure of Constantinople could be slow and painful.

1. Why Ethereum falls?
17 Feb. 2019

2. Ethereum Constantinople shall fail

3. ERC-721 Tokens ERC-820 Tokens
ERC-223 Tokens
ERC-777 Tokens
ERC-20 Tokens
ERC-721 Tokens ERC-820 Tokens
ERC-223 Tokens
ERC-777 Tokens
ERC-20 Tokens
Why Constantinople shall fail?
Upgrading Ethereum Mainnet should support each and every dApp on its mainnet.
Single fail on supporting any Ethereum dApp shall be the failure of Constantinople.

4. ERC-721 Tokens ERC-820 Tokens
ERC-223 Tokens
ERC-777 Tokens
ERC-20 Tokens
Once upgraded to Constantinople, Ethereum must support the full life cycle of a
dApp. If it only supports certain phase of dApps it shall fail eventually causing the
failure even slower and more painful.
Fail of Constantinople shall be slow and painful

5. Constantinople must meet all dApp’s all phase & feature
Publish Delist
selfdestruct()Create
...
...
Every dApp and its functions coded inside the dApp program must meet Constantinople,
otherwise Constantinople hard fork shall be considered as a failure.

6. How can dApps made for PoW work for PoS?
PoW PoS
Eventually dApp made for PoW mainnet shall break down on PoS mainnet somehow!
Ethereum coders are known to make so many mistakes & this hard fork is no exception.

7. Ethereum Constantinople shall fail