Previously, there was the Bit Browser, and now there is the Fingerprint Browser, both of which pose the risk of wallet assets being stolen. Besides using fingerprint + hardware wallet or Google multi-login methods, what other good methods are there? Here, Momo introduces another idea.
Regardless of the method used, the goal is to sandbox the browser environment. Using Docker in a development environment is also a good isolation solution.
By packaging 'remote control + Google Chrome' into a Docker environment, and configuring the proxy with Docker environment variables, you can run an environment with IP proxy.
There is a very suitable environment for our needs on Docker Hub: kasmweb/chrome
Command reference:
docker create -it --shm-size=2048m -e VNC_PW=xxxx -p:6901 --name chrome_monad_ -v :/home kasmweb/chrome
This method requires certain technical skills and server environment. Besides kasmweb/chrome, you can also create your own image for personal use.
