You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wallets will be named using three mnemonic words. Only 1 word will be displayed (with ...) in wallet listing screen. The full name will be used in Google Authenticator. The full 3-word name will also be displayed in detailed view. The address of the wallet will be abbreviated by default to save space.
Address Input
Addresses used in the past will be stored and suggested as input in all applicable places (such as transfer)
Settings
Developer related settings and tools will be hidden by default (such as relayer password and address). They can be toggled to become visible by visiting https://1wallet.crazy.one/dev. To hide them again, visit https://1wallet.crazy.one/nodev
Address Style
ETH-style address (a.k.a hexadecimal address, or checksum address) will be displayed when the user hovers their mouse over any address for at least 1 second. The copy button will copy the address-format currently being displayed. ETH-style address will be displayed using a slightly different color to highlight the visual difference.
The recovery address will become mandatory. If the user has at least one existing 1wallet, the first wallet will be chosen by default. For users creating their very first 1wallet, the default option will be 1wallet treasury, at address:
A warning box would be displayed to strongly advises the user to use a recovery address under their control instead of 1wallet treasury, such as one obtained from the Chrome extension wallet.
The warning will explain to the user what 1wallet treasury is: a safe-box controlled by a multi-signature DAO that requires 3 signatures from its 5 owners to authorize any transfer. If the user chooses 1wallet treasury as the recovery address, the funds can be recovered to 1wallet treasury if the user loses the authenticator, or there are bugs in the software (such as #72) that causes the wallet to be inaccessible. However, the process to reclaim the funds from the treasure may be complex.
The text was updated successfully, but these errors were encountered:
Upcoming changes for v0.8.2:
Wallet Name
Wallets will be named using three mnemonic words. Only 1 word will be displayed (with ...) in wallet listing screen. The full name will be used in Google Authenticator. The full 3-word name will also be displayed in detailed view. The address of the wallet will be abbreviated by default to save space.
Address Input
Addresses used in the past will be stored and suggested as input in all applicable places (such as transfer)
Settings
Developer related settings and tools will be hidden by default (such as relayer password and address). They can be toggled to become visible by visiting https://1wallet.crazy.one/dev. To hide them again, visit https://1wallet.crazy.one/nodev
Address Style
ETH-style address (a.k.a hexadecimal address, or checksum address) will be displayed when the user hovers their mouse over any address for at least 1 second. The copy button will copy the address-format currently being displayed. ETH-style address will be displayed using a slightly different color to highlight the visual difference.
Recovery Address
This is related to issue #72
The recovery address will become mandatory. If the user has at least one existing 1wallet, the first wallet will be chosen by default. For users creating their very first 1wallet, the default option will be 1wallet treasury, at address:
A warning box would be displayed to strongly advises the user to use a recovery address under their control instead of 1wallet treasury, such as one obtained from the Chrome extension wallet.
The warning will explain to the user what 1wallet treasury is: a safe-box controlled by a multi-signature DAO that requires 3 signatures from its 5 owners to authorize any transfer. If the user chooses 1wallet treasury as the recovery address, the funds can be recovered to 1wallet treasury if the user loses the authenticator, or there are bugs in the software (such as #72) that causes the wallet to be inaccessible. However, the process to reclaim the funds from the treasure may be complex.
The text was updated successfully, but these errors were encountered: