#KEYCARD STATUS SERIAL#

The signature of the meta-transaction is performed by the keycard tapped. Any dApps can use web3 javascript API that will prompt Status browser to sign a meta-transaction provided by the dApp. Keycard embeds a second applet (Keycard Cash) with a lower security profile than the main applet (used for high security hardware wallet scenarios). Keycard can be easily integrated with dApps browsed on Status browser. Its form factor, tangibility and cost effectiveness can also be leveraged as an adoption tool, to bring new comers to decentralized services. Keycard can be used as a easy-to-use and mobile friendly hardware wallet, bringing security and ownership over their keys to end users. Smartcards are cost-effective, highly secure hardware, that can generate & store private keys, sign transactions with a tap on a mobile (android & ios sdk available), or with a desktop (with a usb reader). Keycard is an open framework for smartcards in the crypto sphere.

**About Keycard:** Secure, Contactless, Open Source Hardwallet Please express interest in the bounty with your project idea detailed in the work plan, and we will reach out to get your information and send you a Keycard ASAP!'ĭevelop a dApp that uses the Keycard Cash applet with the Web3 javascript API to enable any type of use cases with smart contracts (e.g but not restricted to payments or redeeming assets for smart contracts) '**Important** To participate in this bounty you'll need a physical Keycard mailed to you. This primary user ID is shown if the corresponding public OpenPGP key is available.- Integrate Keycard with a dApp status-im keycard, hardware, wallet, defi, status Other tools like PAM modules or ssh use this key for authentication services. This key is commonly used as an encryption subkey. This key is commonly used as the primary OpenPGP key. It is only reset if a new signature key is created on or imported to the card. This number keeps track of the signatures performed with the stored key. The third PIN represents the retry counter for the AdminPIN. The second PIN is only required due to peculiarities of the ISO-7816 standard gpg tries to keep this PIN in sync with the first PIN.

gpg makes sure that the two numbers are synchronized. The first and second PIN are for the standard PIN. They are reset whenever a correct AdminPIN is entered. They are decremented whenever a wrong PIN is entered. This field saves how many tries still are left to enter the right PIN. The values are put on the card right after personalisation - this is the moment after the chip has been glued on the card. When set to 'non forced', gpg may cache the PIN as long as the card has not been removed from the reader. When set to 'forced', gpg requests the entry of a PIN for each signature operation.

This is a field reserved for arbitrary data. See the source (app-openpgp.c) for some special features of the login-name field. gpg does not enforce any match of this name with a name used in the key. This field may be used to store the account name of the card holder. It may contain an URL to be used to retrieve the public key. Used by the fetch command of gpg -edit-card. Only plain ASCII characters are Allowed here. ManufacturerĪ unique number for all cards from this manufacturer. This is a unique identifier for any card.

#KEYCARD STATUS SERIAL#

This includes the type of the card, the implemented version of the specification, the manufacturer and the serial number.

Keycard status