![2befa747c9ee9da5e3e973a21f42db81.jpg](https://steemitimages.com/DQmWA9MfNguLbTpq6SjFrD7Z9G7JnP21vx1GfthDFC2CruZ/2befa747c9ee9da5e3e973a21f42db81.jpg)![1.JPG](https://steemitimages.com/DQmPnPGAZoDXytkz8iExWRRpaGS8mDpV34myggEg4Dx4QVL/1.JPG)![2.JPG](https://steemitimages.com/DQmRPtCXZq2LFEhDcyuLTEJLWP4dfwhj42orgJCRmk8bko8/2.JPG)![3.JPG](https://steemitimages.com/DQmUhqukAxVMdNLdTHVjpb3X4RQf5NQ5aovnCWn9TecJjaK/3.JPG)![4.JPG](https://steemitimages.com/DQmX5VPtGkE4ufmy634TNVvt3a82UktgSksGbqBU7LLHzcH/4.JPG)![5.JPG](https://steemitimages.com/DQmPw3qAXkPaw7EW1h61Km44bnwe5pvrcjbhJeLyCFcPSx9/5.JPG)
source : https://news.bitcoin.com/fork-watch-take-extra-precaution-when-trying-to-access-post-fork-tokens/