Putting private keys directly into websites is not safe or secure. Even ones run by SteemIt, Inc. Yet this is currently how nearly every Steem-based site or service currently works. On top of that, most Steem users likely use their master password which is even worse
The Vessel desktop wallet software is a secure alternative, but it is too difficult to use for the majority of Steem users and does not easily interact with websites - which is Steem's primary use case.
On Ethereum, you never have to enter your private key into a website to use a dApp, you can just use a browser extension like Metamask, which dApp websites can interface with to securely store your keys and broadcast transactions to the blockchain.
Steem Keychain aims to bring the security and ease-of-use of Metamask to the Steem blockchain platform.
The Steem Keychain extension includes the following features:
- Store an unlimited number of Steem account keys, encrypted with AES
- View balances, transaction history, voting power, and more
- Send STEEM and SBD transfers right from the extension
- Securely interact with Steem-based websites that have integrated with Steem Keychain
- Manage transaction confirmation preferences by account and by website
- Locks automatically on browser shutdown or manually using the lock button
Websites can currently request the Steem Keychain extension to perform the following functions / broadcast operations:
- Send a handshake to make sure the extension is installed
- Decrypt a message encrypted by a Steem account private key (commonly used for "logging in")
- Post a comment (top level or reply)
- Broadcast a vote
- Broadcast a custom JSON operation
- Send a transfer
An example of a web page that interacts with the extension is included in the "example" folder in the repo. You can test it by running a local HTTP server and going to http://localhost:1337/main.html in your browser.
cd example
python -m http.server 1337 //or any other method to run a static server
NOTE: On localhost, it will only run on port 1337.
The Steem Keychain extension will inject a "steem_keychain" JavaScript into all web pages opened in the browser while the extension is running. You can therefore check if the current user has the extension installed using the following code:
if(window.steem_keychain) {
// Steem Keychain extension installed...
} else {
// Steem Keychain extension not installed...
}
Additionally, you can request a "handshake" from the extension to further ensure it's installed and that your page is able to connect to it:
steem_keychain.requestHandshake(function() {
console.log('Handshake received!');
});
Sites can request that the extension sign and broadcast a transfer operation for STEEM or SBD. Note that a confirmation will always be shown to the user for transfer operations and they cannot be disabled.
steem_keychain.requestTransfer(account_name, to_account, amount, memo, currency, function(response) {
console.log(response);
});
Sites can request that the extension decode a memo encrypted by the Memo, Posting, or Active key for a particular Steem account. This is messaged to the user as "Verify Key" since it is typically used to verify that they have access to the private key for an account in order to "log them in".
steem_keychain.requestVerifyKey(account_name, encrypted_message, key_type, function(response) {
console.log(response);
});
The values for "key_type" can be: "Memo", "Posting", or "Active".
Sites can request that the extension sign and broadcast a "comment" operation (which can be a top-level post or a reply).
steem_keychain.requestPost(account_name, title, body, parent_permlink, parent_author, json_metadata, permlink, function(response) {
console.log(response);
});
Sites can request that the extension sign and broadcast a "vote" operation:
steem_keychain.requestVote(account_name, permlink, author, weight, function(response) {
console.log(response);
});
Sites can request that the extension sign and broadcast a "custom_json" operation using either the posting or active key for the account:
steem_keychain.requestCustomJson(account_name, custom_json_id, key_type, json, display_name, function(response) {
console.log(response);
});
Where "key_type" can be "Posting" or "Active" and "display_name" is a user-friendly name of the operation to be shown to the user so they know what operation is being broadcast (ex. "Steem Monsters Card Transfer").
Sites can request that the extension sign messages:
steem_keychain.requestSignBuffer(account_name, message, key_type, function(response) {
console.log(response);
});
Where "message" is any string and "key_type" can be "Posting" or "Active". This is equivalent to
Signature.signBufferSha256(hash.sha256(message), wif).toHex();
Sites can request that the extension sign and broadcast general operations allowed by the steem-js library:
steem_keychain.requestBroadcast(account_name, operations, key_type, function(response) {
console.log(response);
});
Where "operations" is the list of operations and "key_type" can be "Posting" or "Active". This is roughly equivalent to
broadcast.send({ extensions: [], operations }, keys, errorCallback);
Sites can request that per sign RPCs using steem authorities as specified in https://github.com/steemit/rpc-auth
and implemented in the steem-js library method signedCall:
steem_keychain.requestSignedCall(account_name, method, params, key_type, function(response) {
console.log(response);
});
Where "method" is the method name, e.g. conveyor.get_feature_flags, "params" are the method parameters,
and "key_type" can be "Posting" or "Active".
- ngx-steem-keychain - Native Angular framework integration.