Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Callisto (CLO) #22

Merged
merged 1 commit into from
Aug 1, 2018

Conversation

mkrufky
Copy link
Contributor

@mkrufky mkrufky commented Jul 31, 2018

Add support for Callisto (CLO)

EIP-155 is now properly working with Callisto!! Tested personally on the Ledger Nano S

homepage           : https://callisto.network
block explorer     : https://explorer.callisto.network
                   : https://cloexplorer.org
network statistics : https://clostats.net
slip0044 index     : 820
chainId            : 820

Callisto has been unable to work with hardware wallets until the following changes were applied:
8260268
74c085c

Callisto has EIP-155 Replay attack protection enabled on their network.
For documentation of this, please see https://github.com/EthereumCommonwealth/go-callisto/blob/CLO/1.0/params/config.go

@btchip btchip merged commit 2fe57f1 into LedgerHQ:master Aug 1, 2018
@mkrufky mkrufky deleted the callisto branch August 6, 2018 03:24
mkrufky added a commit to mkrufky/etherwallet that referenced this pull request Aug 27, 2018
Enable Ledger Hardware Wallet support for Callisto (CLO)

EIP-155 is now properly working with Callisto!! Tested personally on the Ledger Nano S

    homepage           : https://callisto.network
    block explorer     : https://explorer.callisto.network
                       : https://cloexplorer.org
    network statistics : https://clostats.net
    slip0044 index     : 820
    chainId            : 820

Callisto has been unable to *safely* work with hardware wallets until the following changes were applied:
LedgerHQ/app-ethereum@8260268
LedgerHQ/app-ethereum@74c085c

Callisto has EIP-155 Replay attack protection enabled on their network.
For documentation of this, please see https://github.com/EthereumCommonwealth/go-callisto/blob/CLO/1.0/params/config.go

MyEtherWallet Full 32bit Chain ID support: (merged)

Callisto is on Ledger's official roadmap:
https://trello.com/c/AawiAoSM/116-callisto-support

Ledger Nano S Full 32bit Chain ID support: (merged)
LedgerHQ/app-ethereum@8260268
LedgerHQ/app-ethereum@74c085c

Ledger Nano S Callisto (CLO) app: (merged)
LedgerHQ/app-ethereum#22

Callisto is on Ledger's official roadmap:
https://trello.com/c/AawiAoSM/116-callisto-support

cc: @yograterol
cc: @project-callisto
mkrufky added a commit to mkrufky/etherwallet that referenced this pull request Aug 27, 2018
Enable Ledger Hardware Wallet support for Callisto (CLO)

EIP-155 is now properly working with Callisto!! Tested personally on the Ledger Nano S

    homepage           : https://callisto.network
    block explorer     : https://explorer.callisto.network
                       : https://cloexplorer.org
    network statistics : https://clostats.net
    slip0044 index     : 820
    chainId            : 820

Callisto has been unable to *safely* work with hardware wallets until the following changes were applied:
LedgerHQ/app-ethereum@8260268
LedgerHQ/app-ethereum@74c085c

Callisto has EIP-155 Replay attack protection enabled on their network.
For documentation of this, please see https://github.com/EthereumCommonwealth/go-callisto/blob/CLO/1.0/params/config.go

MyEtherWallet Full 32bit Chain ID support: (merged) MyEtherWallet#1979

Callisto is on Ledger's official roadmap:
https://trello.com/c/AawiAoSM/116-callisto-support

Ledger Nano S Full 32bit Chain ID support: (merged)
LedgerHQ/app-ethereum@8260268
LedgerHQ/app-ethereum@74c085c

Ledger Nano S Callisto (CLO) app: (merged)
LedgerHQ/app-ethereum#22

cc: @yograterol
cc: @project-callisto
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants