Update - 5

  1. I am facing an issue with injecting Buffer (Nodejs) polyfill into my vite project. I have hightlighted the issue with the crxjs team which I feel is the main reason for the issue - https://github.com/crxjs/chrome-extension-tools/issues/617.
    To move forward I have made the following changes in my node_modules:

    Image Not Showing Possible Reasons
    • The image file may be corrupted
    • The server hosting the image is unavailable
    • The image path is incorrect
    • The image format is not supported
    Learn More →

  2. Added ability to auto-lock the keyring controller using chrome.alarms/

  3. Created a simple Account, that could perform all the functions of an EOA.

  4. Explored other SCW design to incorporate manual inputs, wrote about potential life cycle when a custom input from a user in needed in a wallet's lifecycle - https://hackmd.io/@plusminushalf/wallet-life-cycle

  5. The orignal design of the extension was the the App would coordinate with background script using redux actions using webext-redux. Then background script will send communications to Sandbox environment running inside an iframe where SCW's implementation will be executed. The problem came when we need custom user inputs and we have to validate every custom user input before sending it to the SCW. If you checkout KeyringViewInputField type in the link above, it exposes a function isValid. Since the defination of this function is inside the sandbox environment, everytime a value had to be validated App had to fire a redux action which will call background script which will call the sandbox and then the validation data will be returned.
    Since it was not the most optimised way, I am working on a new structure where App & sandbox environment can safely interact with each other without the need of interaction with the background script.

  6. Created a demo wallet locally which will be accepting a user input while creating a new account.