An ERC-20 bug enabled coins to be lost when users accidentally sent tokens to a smart contract using the same mechanism they would use to transfer tokens to a conventional wallet. This has resulted in the loss of more than $3 million in ERC-20 tokens. 
ERC-223’s architecture addresses this problem by allowing users to move tokens to smart contracts and wallets that provide the same purpose. While resolving the aforementioned problems, ERC-223 keeps all of the original functionality. 
The transfer function checks if the destination address is a smart contract and returns tokens to the sender's account using the smart contract’s token
Fallback function if it is, ensuring no token loss. 
The ERC-223 token is powered by automated smart contracts that ensure transparent user transaction details. The ERC-223 token development platform offers investors instant liquidity and high ROI as passive income. Additionally, it allows tokens to be deposited into a contract in a single transaction, preventing additional blockchain bloat. 
The ERC 223 token creation platform has multi-level security features including HTTP authentication, end-to-end encryption, and escrow protection to prevent hacking. 
ERC223 tokens should be sent by calling the
transfer function on token contract with no difference if the receiver is a contract or a wallet address.
- If the receiver is a wallet, an ERC223 token transfer will be identical to an ERC20 transfer.
- If the receiver is a contract, the ERC223 token contract will try to call the
tokenReceivedfunction on the receiver contract. If there is no
tokenReceivedfunction on the receiver contract, the transaction will fail. 
How was your experience?
Give this wiki a quick rating to let us know!