The ICAP is a method of representing an Ethereum address with a built-in checksum and in a way that is compliant with most bank software due to compliance with the International Bank Account Number (IBAN) format. But many block explorers and other tools are still using the raw hexadecimal representation for Ethereum addresses. Which Ethereum clients/wallets/apps actually support the ICAP?
asked Jan 22 '16 at 1:07
Add a comment
|
Found ethereumjs-icap
Utilities for handling ICAP (Ethereum in IBAN) encoding
API Says
fromAddress(address, print, nonstd)- try encoding an address into an IBANfromAsset(asset, print)- try encoding an asset description into an IBANtoAddress(iban)- try decoding an IBAN into an address descriptiontoAsset(iban)- try decoding an IBAN into an asset descriptionencode(address/asset)- encode an address or an asset description into an IBANdecode(iban)- decode an IBAN into an address or asset descriptionencodeBBAN(address/asset)- encode an address or an asset description into a BBANdecodeBBAN(bban)- decode a BBAN into an address or asset description
Status of Ethereum Wallet 0.3.8 (Beta 5)
Not yet implemented source
Geth does not support ICAP yet. It's planned for the 1.4.1 release which are scheduled sometime after the Homestead release.
Eth does support ICAP, it's build in for a while now, but I never heard of anyone actually using it. I would recommend using it with care.
-
1Small corrections on Geth. Homestead is 1.3.4, and will roll out with only the consensus changes. We don't want feature in there so if something goes wrong, we know where to look and fix. We'll release 1.4 maybe a week after homestead, which will roll out all the features worked on over the last months. ICAP is planned for 1.4.1 only, as we're freezing 1.4 and a new addressing scheme isn't so simple as to do a quick merge. Feb 19 '16 at 11:25
-
-