Search

Filter

Blockchain Keystore SDK 50
Sorry, no results
found for "Blockchain Keystore SDK" on the website

news blockchain

news

Samsung Blockchain Keystore SDK v1.3.0 Released

an updated version of the samsung blockchain keystore sdk has been released. new features in v1.3.0 include: added apis to support stellar transactions added apis to support sign personal message in tron transactions

Samsung Developers

https://developer.samsung.com/sdp/news/en-us/2020/02/18/samsung-blockchain-keystore-sdk-v130-released

tutorials mobile, blockchain

blog

Optimize Address Fetching in the Samsung Blockchain Keystore SDK with Seed Hash

last june, samsung introduced samsung blockchain keystore (sbk), a secure built-in cold wallet in galaxy devices. the cold wallet is isolated with samsung knox and encapsulated within a defense-grade trusted execution environment (tee). the samsung blockchain keystore sdk enables use of this wallet in android applications. in this article, we discuss how to optimize the address fetching process with seed hash. fetching addresses from the samsung blockchain keystore using the sdk is an expensive operation, so this blog teaches you how to store your seed hash values to avoid delays in fetching information whenever you launch your app. the samsung blockchain keystore (sbk) sdk enables users to get blockchain public addresses from the samsung blockchain keystore and sign a cryptocurrency transaction to authenticate. a public address is the hashed version of the public key and is used to recognize a blockchain cryptocurrency account. as the blockchain protocol goes, anyone can fetch the balance and transaction history of an account with its public address. developers can invoke the getaddresslist() api of the sbk sdk to fetch the address list. every time this api is called with the same request, you get the same address list. a change to the list occurs only when the wallet's root seed has been changed. the programming guide: api flow and use cases provides more detailed information. seed hash the sdk uses the term seed hash (see figure 1, inside the green rectangle). figure 1: sbk sdk api flow and use case the sdk glossary says: seed hash: a pseudo seed hash that is generated randomly when the hd wallet is created. if the master seed of a wallet is changed, the seed hash will be changed as well. the getseedhash() api gets the current seed hash from the samsung blockchain keystore. fetching the address list from the samsung blockchain keystore using the sbk sdk initiates an expensive operation that requires a considerable amount of time. to provide the user with a seamless experience, the sbk sdk programming guide recommends that developers store information from the getseedhash() api. developers then need to invoke the getaddresslist() api only when the stored seed hash is different from the seed hash fetched using the sbk sdk. prerequisites before you begin, be sure you've met these prerequisites: you have already imported the sdk in your android app you have completed samsung blockchain keystore wallet setup you meet supported device and regions restrictions if not, download the sbk sdk and check out the programming guide: getting started section to integrate the sbk sdk. i also recommend reading this blog on address fetching basics: "where's my crypto coin? featuring samsung blockchain keystore sdk” . enable developer mode in the samsung blockchain keystore to bypass api key verification. the sample application in this blog is not a partner app, so you must enable developer mode to run and test the app features. store the seed hash i recommend using android sharedpreferences to store the seed hash. remember, the seed hash value is not sensitive data; it's not the wallet's root seed itself. it's a hash value generated to keep track of change in the wallet. because high-level security is not a concern, and when you have a relatively small collection of key values that you'd like to save, sharedpreferences is an easily implemented solution. all you need to do is get the sharedpreferences file and then read and write key-value pairs on it. if you prefer another method of storing data, you can select any one of the methods described in the android: data and file storage overview. the following code snippet refers to sharedpreferences: private static final string seedhashkey = "seed_hash"; private static final string defaultseedhashvalue = ""; private static sharedpreferences msharedpreference; msharedpreference = getactivity().getpreferences(context.mode_private); public static string getseedhash() { return msharedpreferences.getstring( seedhashkey, defaultseedhashvalue); } public static void setseedhash(string seedhash) { sharedpreferences.editor editor = msharedpreferences.edit(); editor.putstring(seedhashkey, seedhash); editor.commit(); } } //fetch seedhash from sbk and store on shared preference string seedhashsdk = scwservice.getinstance().getseedhash(); setseedhash(seedhashsdk); get the address list from the samsung blockchain keystore the getaddresslist() api of the sbk sdk requires the hd path list and callback function parameters. hd path list parameter: an arraylist, a list of strings in which every string denotes an hd path. see understanding keystore > key management for more information. callback function parameter: a callback function of type scwservice.scwgetaddresslistcallback. the address fetching method is performed asynchronously; on completion onsuccess() or onfailure() method is invoked. onsuccess() holds the required address list as a list, whereas onfailure() holds the error code. the following code snippet retrieves four addresses at one time: private scwservice.scwgetaddresslistcallback mscwgetaddresslistcallback = new scwservice.scwgetaddresslistcallback() { @override public void onsuccess(list<string> addresslist) { log.i(util.log_tag, "accounts fetched from sdk successfully."); } @override public void onfailure(int errorcode) { // error codes doc: // https:developer.samsung.com/blockchain/keystore/ log.e(util.log_tag, "fetch accounts failure. error code: " + errorcode); } }; public void getpublicaddress(arraylist<string> hdpathlist) { mscwservice.getaddresslist( mscwgetaddresslistcallback, hdpathlist); } arraylist hdpathlist = new arraylist<>(); hdpathlist.add(scwservice.gethdpath(scwcointype.eth, 0)); //m/44'/60'/0'/0/0 hdpathlist.add(scwservice.gethdpath(scwcointype.eth, 1)); //m/44'/60'/0'/0/1 hdpathlist.add(scwservice.gethdpath(scwcointype.eth, 2)); //m/44'/60'/0'/0/2 hdpathlist.add(scwservice.gethdpath(scwcointype.eth, 3)); //m/44'/60'/0'/0/3 // btc -> "m/44'/0'/0'/0/0"; getpublicaddress(hdpathlist); representation for an accounts info demonstration, i've used android's recyclerview. for detailed information, see create a list with recyclerview and this android recyclerview example. figure 2: fetching an address list from the samsung blockchain keystore store address information on an application database once you have fetched the required addresses from the samsung blockchain keystore, design your mechanism to store this information. let’s look at requirements at this stage: storage for account information: accounts presented at app launch have to remain consistent on subsequent app launches, unless the wallet has been changed. provide users with a seamless experience: information should not be fetched from samsung blockchain keystore using sdk every time the app launches, because it causes delays. this leads us to android room. room provides an abstraction layer over sqlite to allow fluent database access while harnessing the full power of sqlite. the three major room components are: database: contains the database holder entity: represents a table within the database. dao interface: contains the methods used for accessing the database. for more information about android room, see the documentation, blogs, and samples. database database class extends the roomdatabase and builds the required database file. @database(entities = {accountmodel.class}, version = 1) public abstract class accountsdb extends roomdatabase { private static accountsdb accountsdb; public abstract iaccountsdao iaccountsdao(); public static accountsdb getinstance(context context) { if (accountsdb == null || !accountsdb.isopen()) { accountsdb = room.databasebuilder (context, accountsdb.class, util.db_name) .build(); } return accountsdb; } } entity here, we have declared our model class as a room entity using annotations. room converts “the members of the class” to “columns of the table,” reducing boilerplate code. @entity public class accountmodel { // accountid used as primary key & indexing, auto generated @primarykey(autogenerate = true) private int accountid; private string publicaddress; private string hdpath; // getter & setter methods .. .. } dao interface here, you have to declare methods and corresponding database sql queries to be run. this interface is implemented by the room persistence library; corresponding codes are generated automatically to perform required database operations. @dao public interface iaccountsdao { @query("select * from accountmodel") list<accountmodel> fetchaccounts(); @insert(onconflict = onconflictstrategy.replace) void insertaccounts(arraylist<accountmodel> accountmodels); @query("delete from accountmodel") void removeaccounts(); } on invoking the java method, corresponding queries are performed on the database. for example, invoking the removeaccounts() method executes the delete from accountmodel query. database operations room doesn’t allow you to issue database queries on the main thread, as it can cause delays. database crud operations must be performed on a separate thread. i’ve used asynctask on this example to perform database operations. asynctask allows you to perform background operations and publish results on the ui thread without manipulating threads and/or handlers yourself. asynctask gives a high-level wrapper over multithreading, so you don't need expertise in concurrent threads or handlers. doinbackground(params...): performs a computation on a background thread. onpostexecute (result): posts on the ui thread once doinbackground() operation is completed. the result parameter holds the execution result returned by doinbackground(). execute(params...): on invocation, executes the task specified with given parameters. see the api reference for details. the following example code snippet shows the database retrieve data task: private static class fetchasynctask extends asynctask<void,void,arraylist<accountmodel>> { @override protected arraylist<accountmodel> doinbackground(void...voids){ arraylist<accountmodel> accountmodels = new arraylist<accountmodel>(accountsdb.iaccountsdao().fetchaccounts()); return accountmodels; } @override protected void onpostexecute (arraylist<accountmodel> accountmodels) { log.i(util.log_tag, "db fetch successful"); accountrepository.setmaccountmodels(accountmodels); } } public static void fetchaccounts() { // db crud operations has to be performed in a separate thread new fetchasynctask().execute(); } figure 3: fetching an address list from database next steps it's a lot of technical info for one blog. however, it will be worth it to have your apps launch quickly and seamlessly once you've optimized address fetching in the samsung blockchain keystore sdk. for more detailed information, see the following references, and don't hesitate to reach out with any queries and feedback. source code for sample application "optimize address fetching with seed hash" "where's my crypto coin?” featuring samsung blockchain keystore sdk samsung blockchain keystore programming guide: api flow and use cases android data and file storage: sharedpreferences save data in a local database: android room

Md. Armaan Ul Islam

https://developer.samsung.com/sdp/blog/en-us/2020/02/04/optimize-address-fetching-in-the-samsung-blockchain-keystore-sdk-with-seed-hash

tutorials blockchain

blog

“Where's My Crypto Coin?” Featuring Samsung Blockchain Keystore SDK

distributed ledger-based technologies are becoming more popular and easy to use. anyone can now build a new cryptocurrency or token in the blockchain world. this rise in popularity and value makes crypto assets a big target for hackers. if you want to keep your valuable crypto assets safe, using a hardware cold wallet such as trezor or ledger nano s has become a necessity. unfortunately, that adds up to one more item in your pocket that you always have to carry around. thankfully, gone are the days of carrying clunky, old wallets. recent galaxy phones, such as the s10e, s10, s10+, note10, and fold, can now securely store your cryptocurrency wallet using the samsung blockchain keystore (sbk). along with storing your cryptocurrency wallet, the sbk sdk allows you to get your blockchain address and sign cryptocurrency transactions. in this article, we explore one of the key features offered by the keystore sdk--how to get your blockchain address from the sbk sdk and three ways to share it: display as qr code copy to clipboard share through android’s share intent setting up the project and handling sbk data to set up your android project with the sbk sdk, follow these instructions. to use functionalities offered by the sdk, first fetch an instance of the service. private scwservice mscwservice = scwservice.getinstance(); after you have fetched the scwservice instance, you can check whether your device is keystore-supported. if (mscwservice == null) { log.e("keystoreapp", "keystore is not supported on this device."); } if the device is keystore-supported, you can fetch the address list with getaddresslist(): mscwservice.getaddresslist(addresslistcallback, hdpathlist); the first parameter to getaddresslist() is a scwgetaddresslistcallback, which is executed after getting a response from keystore. scwgetaddresslistcallback() has two functions: onsuccess(): this function is called when the address list has been fetched successfully from keystore. onfailure(): this function is called if any errors occur while fetching the address list from keystore. scwservice.scwgetaddresslistcallback addresslistcallback = new scwservice.scwgetaddresslistcallback() { @override public void onsuccess(list addresslist) { //you can share your address from the address list here } @override public void onfailure(int failurecode) { //based on the failure code you can show appropriate alerts here } }; the second parameter is an arraylist of hierarchical deterministic (hd) path(s) whose addresses you want to fetch. if you want to learn more about hd paths, please refer to bip-44. for example, if you want to find the public address of your first five accounts, pass the following list as a parameter: arraylist hdpathlist = new arraylist<>(); hdpathlist.add("m/44'/60'/0'/0/0"); hdpathlist.add("m/44'/60'/0'/0/1"); hdpathlist.add("m/44'/60'/0'/0/2"); hdpathlist.add("m/44'/60'/0'/0/3"); hdpathlist.add("m/44'/60'/0'/0/4"); a sample app with the sbk sdk now that we are familiar with getaddresslist(), let’s dive into our sample application. features of our public address with sbk app are: fetch your public address from the keystore switch between multiple public addresses display qr code of the selected account copy selected address into the clipboard send the selected address with supported applications with android’s share intent initially, only the address of the first account is loaded. when you press the add button, the hd path of a new account is added to hdpathlist, and public addresses are fetched. public void addaccount(view view) { //account index is incremented by 1 to get the new account accountindex++; //hdpath of new account is added to hdpathlist hdpathlist.add("m/44'/60'/0'/0/" + accountindex); showtoast("hdpath added to list"); //public address of new account is fetched getpublicaddress(); } public addresses are fetched using the getpublicaddress() function depicted below. if the address list is fetched successfully, onsuccess() is called, and: the spinner’s previous data is cleared. the newly fetched list is added to the spinner. the ui is updated. if an error occurs, it is logged and available from logcat. common errors such as error_invalid_scw_app_id can be fixed very easily by enabling developer mode from the keystore application. you can find instructions on how to enable developer mode here. private void getpublicaddress() { scwservice.scwgetaddresslistcallback addresslistcallback = new scwservice.scwgetaddresslistcallback() { @override public void onsuccess(final list publicaddresslist) { //after address list has been fetched spinner is updated with new list runonuithread(new runnable() { @override public void run() { //clear existing list spinneradapter.clear(); //new list is added spinneradapter.addall(publicaddresslist); spinneradapter.notifydatasetchanged(); if (publicaddresslist.size() == 1) { showtoast(publicaddresslist.size() + " address fetched."); } else { showtoast(publicaddresslist.size() + " addresses fetched."); } } }); } @override public void onfailure(int errorcode) { switch (errorcode) { case scwerrorcode.error_invalid_scw_app_id: log.e(log_tag,"developer option not enabled."); break; case scwerrorcode.error_check_app_version_failed: log.e(log_tag,"check internet connection."); break; case scwerrorcode.error_op_fail: log.e(log_tag,"operation failed"); break; default: log.e(log_tag,"error with error code: "+errorcode); break; } } }; if (mscwservice == null) { log.e(log_tag, "keystore is not supported in this device."); } else { //if keystore is supported on device address list is requested mscwservice.getaddresslist(addresslistcallback, hdpathlist); } } after loading all addresses into the spinner, we can now select any address from it. once an address is selected, its qr code is generated and displayed. publicaddressspinner.setonitemselectedlistener(new adapterview.onitemselectedlistener() { @override public void onitemselected(adapterview<?> adapterview, view view, int position, long l) { //get selected address from spinner selectedaddress = adapterview.getitematposition(position).tostring(); selectedaddresstextview.settext(selectedaddress); qrcodeimageview.setimagebitmap(generateqrcode(selectedaddress)); } } in this application, we used “zxing” to generate the qr bitmap of the selected public address. private bitmap generateqrcode(string text) { multiformatwriter multiformatwriter = new multiformatwriter(); bitmap bitmap = bitmap.createbitmap(10, 10, bitmap.config.rgb_565); try { //text encoded to qr bitmatrix bitmatrix bitmatrix = multiformatwriter.encode(text, barcodeformat.qr_code, 1000, 1000); barcodeencoder barcodeencoder = new barcodeencoder(); //qr bitmatrix encoded to bitmap bitmap = barcodeencoder.createbitmap(bitmatrix); } catch (writerexception e) { e.printstacktrace(); } finally { return bitmap; } } when you press the copy button, the address is copied to the clipboard. public void copyaddress(view view) { clipboardmanager clipboardmanager = (clipboardmanager) getsystemservice(context.clipboard_service); clipdata clipdata = clipdata.newplaintext("public address", selectedaddress); clipboardmanager.setprimaryclip(clipdata); toast.maketext(this, "address copied", toast.length_short).show(); } we can also share the selected public address using the android action_send intent. public void shareaddress(view view) { intent sendintent = new intent(); sendintent.setaction(intent.action_send); sendintent.putextra(intent.extra_text, selectedaddress); sendintent.settype("text/plain"); startactivity(sendintent); } conclusion now that you know more about the samsung blockchain keystore sdk, you can use it to enrich your blockchain application. additional resources: download the sbk example app more information on keystore sdk

Shuvo Saha

https://developer.samsung.com/sdp/blog/en-us/2019/10/10/wheres-my-crypto-coin-featuring-samsung-blockchain-keystore-sdk

Develop Samsung Blockchain

doc

Release Note

release notes release updates release version 1 6 0 release date dec 12 2023 release contents sdk provides samsung blockchain keystore sdk libraries in aar format documents api references for more information on samsung blockchain keystore apis programming guide includes getting started, api flow and use cases, explanation on how to implement apis, and glossary change history samsung blockchain keystore sdk v1 6 012/12/2023 added an api method to check whether pin authentication is required after reboot added support for android 14 android api level 34 modified the minimum supported android version to android 9 - pie android api level 28 samsung blockchain keystore sdk v1 5 104/12/2021 added apis to support eip-155 trasaction modify signxlmtransaction api to allow sign multi operation in a transaction samsung blockchain keystore sdk v1 4 111/10/2020 added apis to check a backup of root seed samsung blockchain keystore sdk v1 3 002/17/2020 added apis to support stellar transactions added apis to support sign personal message in tron transactions samsung blockchain keystore sdk v1 2 010/29/2019 added apis to support tron transactions samsung blockchain keystore sdk v1 1 008/08/2019 added apis to support bitcoin and klaytn transactions samsung blockchain keystore sdk v1 0 107/11/2019 removed minimum sdk version in samsung blockchain keystore sdk samsung blockchain keystore sdk v1 0 006/27/2019 samsung blockchain keystore sdk release

https://developer.samsung.com/blockchain/keystore/release-note.html

Develop Samsung Blockchain

doc

Integrating Keystore SDK

integrating samsung blockchain keystore sdk integration benefits samsung blockchain keystore leverages security measures that are inherent in a safe execution environment, also known as trusted execution environment tee by integrating with samsung blockchain keystore, decentralized app or wallet developers can make your app secure developers no longer will have to worry about key management, from how guarantee the randomness of key generation, how to store the root seed safely, and to how to use it to sign a transaction in a secure environment even if an app running in ree maliciously modified display and tried to make user sign a fake transaction, trusted user interface tui run in tee by samsung blockchain keystore will make sure that the user can manually check and confirm the exact transaction details the user will also have the ownership to keep keys safe on the device itself, no longer having to rely upon other third party servers user will manually confirm all the transactions and make sure that there is absolutely no transaction that the user does not know about integrations that samsung blockchain keystore team look for because samsung blockchain keystore is a preloaded app on selected galaxy devices, samsung blockchain keystore sdk is also designed for only native android apps for now decentralized apps and wallets must support a native android app to integrate the sdk for web-based apps, please refer to samsung blockchain sdk not keystore for integration samsung blockchain keystore welcomes integrations of decentralized apps and wallets in diverse areas we will be excited to have samsung blockchain keystore sdk integrated into services that provide intuitive user interaction with the blockchain and easy use of the blockchain technology for applications that seek to provide good, long-run blockchain services with greater security, do not hesitate to make this quick integration with samsung blockchain keystore decentralized apps and wallets can use samsung blockchain keystore for selected samsung devices that support samsung blockchain keystore and other keystore or wallets for devices that do not support it samsung blockchain keystore sdk provides an api to check whether it is supported by the device or not, so diverging keystores within the dapp or wallet should not be an obstacle the smart phone is the bridge that can bring blockchain technology one-step closer to our everyday lives with samsung blockchain keystore, we anticipate to contribute to expanding the blockchain ecosystem, helping users use blockchain services more conveniently, but with greater security so why not secure your app with samsung blockchain keystore and join us in expanding this blockchain ecosystem!

https://developer.samsung.com/blockchain/keystore/understanding-keystore/integrating-keystore-sdk.html

Develop Samsung Blockchain

doc

Keystore Architecture

samsung blockchain keystore architecture samsung blockchain keystore leverages the arm’s trustzone, which is one of the best known technology to implement trusted execution environment tee in mobile devices trusted execution environment tee is a secure area inside a main processor as an isolated environment, it makes sure that the code and data loaded in the tee are protected from software attacks and vulnerabilities in the rich execution environment ree in parallel to the apps that we use every day in ree, there are trusted applications tas , authorized security software that run in tee samsung blockchain keystore leverages this tee and implements tas to run operations that require a high level of security, such as generating keys and signing a transaction in the blockchain network samsung blockchain keystore also provides users with a trusted user interface tui that runs in the tee, so that the display that the user sees is not maliciously modified, and user’s input is securely protected this is feasible because the information displayed on the tui is run by an approved trusted application and the input that the user entered is isolated from other applications that run in ree moreover, the use of samsung knox allows samsung blockchain keystore to guarantee that the device is running an approved binary and that the kernel has not been tampered with samsung blockchain keystore will be disabled for compromised device in order to protect your data architecture and key components to understand samsung blockchain keystore architecture, we will first look at the key components dapp/wallet that has integrated samsung blockchain keystore, samsung blockchain keystore sdk, samsung blockchain keystore app, and trusted execution environment that samsung blockchain keystore leverages key components decentralized apps dapps and wallets dapps and wallets usually provide users an interface to the blockchain network, by connecting to a node in the blockchain network they help users manage cryptocurrencies or crypto-assets by creating and submitting a transaction to the blockchain network dapps and wallets that have integrated samsung blockchain keystore sdk can leverage samsung blockchain keystore to get the user’s blockchain address, which is like a user’s account on the blockchain network also, after creating transactions, dapps and wallets can request samsung blockchain keystore to sign transactions safely samsung blockchain keystore sdk dapp and wallet developers can download samsung blockchain keystore sdk from the samsung developers site, and integrate it the sdk directly communicates with samsung blockchain keystore samsung blockchain keystore samsung blockchain keystore is a preloaded app on selected galaxy devices when requests are received from dapps or wallets via the samsung blockchain keystore sdk, the app controls operations and communicates with trusted applications that run in trusted execution environment in the samsung blockchain keystore app, user can setup the wallet, edit settings, like enabling fingerprint as an authentication method or changing alarm settings for notifications, and get more information about the service trusted execution environment tee samsung blockchain keystore leverages trusted execution environment, where only authorized applications are able to be executed key features that are handled in this environment is generating root seed root source of all the keys , parsing and showing transaction details, and signing a blockchain transaction also, trusted user interface tui for secure display and user input protection is also executed in tee end-to-end service flow taking one step further from the main components, the following is an end-to-end service flow of what happens when there is a request from a dapp or a wallet to samsung blockchain keystore to sign a blockchain transaction before we begin, there are two assumptions 1 samsung blockchain keystore is already set up and 2 dapp/wallet knows the user’s address, by deriving it from the samsung blockchain keystore in other words, the root seed, which is the root to many keys, is already generated in the tee, and safely saved in samsung blockchain keystore keeping this in mind, let’s look into each step dapp/wallet creates an unsigned blockchain transaction the transaction could be triggered by the user to buy a crypto-asset, or send cryptocurrencies transaction details, like recipient address, amount, fees, and etc are used to create a transaction dapp/wallet uses samsung blockchain keystore sdk to request samsung blockchain keystore to sign the transaction samsung blockchain keystore receives the transaction via the sdk and handles the operation request in order controller in samsung blockchain keystore that communicates with trusted application ta passes the transaction to tas in the trusted execution environment to parse the transaction details samsung blockchain keystore displays the parsed transaction details on the trusted user interface, which also runs in the trusted execution environment the user checks the transaction details on the trusted user interface and manually confirms that all the transaction details is correct by either entering pin or authenticating with a fingerprint samsung blockchain keystore signs the transaction with the key derived from the root seed in the trusted execution environment transaction signed by ta in samsung blockchain keystore is now returned to samsung blockchain keystore app through samsung blockchain keystore sdk, samsung blockchain keystore returns the signed transaction to dapp/wallet dapp/wallet receives the signed transaction and submits it to the blockchain network once the transaction is confirmed by the nodes, it is applied on the blockchain ledger

https://developer.samsung.com/blockchain/keystore/understanding-keystore/keystore-architecture.html

Learn Code Lab

codelab

Develop a Secure Blockchain App

develop a secure blockchain app objective learn how to create your own decentralized applications dapp using samsung blockchain keystore sdk overview integrating with new technology like blockchain is a burden to most developers for this reason, we offer a way to interwork with samsung blockchain keystore sdk with less effort developers can easily become a dapp developer with our samsung blockchain keystore sdk decentralized applications dapps run and store data on the blockchain network instead of a central server dapps offer increased security and reliability compared to centralized applications moreover, it provides a simple method for in-app payments using cryptocurrency samsung blockchain keystore sdk is used to obtain account information and sign a transaction to transfer cryptocurrency or execute smart contract execution in this code lab, you can learn how to integrate samsung blockchain keystore sdk into your app and how to implement blockchain basic concepts such as account information and signing transactions set up your environment you will need the following java se development kit 8 or later android studio latest version recommended mobile phone which supports samsung blockchain sample code here is a sample code for you to start coding in this code lab download it and start your learning experience! keystore sdk sample code 897 12 kb enable developer mode the developer mode helps developers test the samsung blockchain keystore in developer mode, app id verification is bypassed, so samsung blockchain keystore apis will be enabled to activate developer mode on your mobile device, follow the steps below navigate through settings > biometrics and security > samsung blockchain keystore and click about blockchain keystore tap the samsung blockchain keystore app name quickly, ten times or more if succeeded, developer mode will show noteonly a limited number of devices can be activated for one test app open project file after downloading the sample code, open the given android application project this project is a simple comments dapp based on ethereum ropsten test network it retrieves comments data from smart contract, displays them on the screen, and makes a transaction to execute smart contract function to post user’s comment in the next steps, you can get an account address and execute dapp service with blockchain keystore and you can see the result of successful dapp execution set the app id here, you don’t need to set the application id to use samsung blockchain keystore sdk instead, you must enable developer mode as described previously for the release version of your android app, in your android manifest file, add a metadata with a name as scw_app_id and a value as the app id issued by samsung blockchain keystore team samsung blockchain keystore aar file will read this value when your android app is initialized and help your android app connect to samsung blockchain keystore <manifest xmlns android="http //schemas android com/apk/res/android" package="com samsung android sdk coldwallet test" android versioncode="1" android versionname="1 0"> <application> <meta-data android name="scw_app_id" android value= <!-- put your app id here --> /> </application> </manifest> import samsung blockchain keystore sdk library into the project the sdk library is located at aar/keystoresdk_v1 5 1 aar of the project file to import the library go to gradle scripts > build gradle and enter the following dependencies dependencies { repositories { flatdir{ dirs 'aar' } } implementation 'com samsung android sdk coldwallet keystoresdk_v1 5 1@aar' } check the status of samsung blockchain keystore the first thing to do is to check the status of samsung blockchain keystore in the sample application, it is implemented at initializekeystore in presenter intropresenter java you can find the following steps to check the status of keystore in your android app, call scwservice getinstance if the returned value is an instance and not null, then it means samsung blockchain keystore is supported on the device however, if null is returned, the user must use a different keystore in the sample code, toast a message to notify that the device doesn’t support the keystore // check samsung blockchain keystore is supported or not if scwservice getinstance == null { mcontract toastmessage "samsung blockchain keystore is not supported on your device " ; } call getkeystoreapilevel api to see if the current samsung blockchain keystore being used, properly supports the features that your android app is currently aiming for if the required api level is higher than the current samsung blockchain keystore level, users are directed to samsung blockchain keystore app page in galaxy store through the provided deeplink to update // check installed api level else if scwservice getinstance getkeystoreapilevel < 1 { // if api level is lower, jump to galaxy apps to update keystore app mcontract showdialog "" , "ok" , "the api level is too low jump to galaxy store" , -> mcontract launchdeeplink scwdeeplink galaxy_store ; } check if a user has set up the samsung blockchain keystore and is ready to use it by calling getseedhash api if the seed hash value in string is zero-length, this means the user has not set up samsung blockchain keystore yet hence, your app will need to guide the user to jump to samsung blockchain keystore via deeplink to either create or import a wallet // check seed hash exist else if scwservice getinstance getseedhash length == 0 { // if seed hash is empty, // jump to blockchain keystore to create or import wallet mcontract showdialog "" , "ok" , "the seed hash is empty " + "jump to blockchain keystore to create/import wallet " , -> mcontract launchdeeplink scwdeeplink main ; } if the getseedhash api returned value is not zero-length, it means that the user has successfully set up samsung blockchain keystore if there is a previously saved or cached seed hash value, compare the two seed hash values if those two values are not equal, nor if there is no such saved cached seed hash value, then the address has to be checked again if the seed hash value has been changed, it means the master seed has been changed as well, meaning the address that your android app was linked to may no longer be the same address // check seed hash cached else if !textutils equals cachedseedhash, scwservice getinstance getseedhash { // if the seed hash is different from cached, update seed hash and address // go to next activity final string ethereumhdpath = "m/44'/60'/0'/0/0"; getethereumaddress ethereumhdpath , success, errorcode, address, seedhash -> { if success { updateaddress address ; updateseedhash seedhash ; mcontract showtimelineactivity true ; } else { mcontract toastmessage "cannot get address error code " + errorcode ; } mcontract setloading false ; } ; return false; } if those two values are equal, it means checking the keystore status was successful, and you can move on to the next step // success else { // set address from cached value // go to next activity string address = prefshelper getinstance getcachedaddress ; updateseedhash cachedseedhash ; updateaddress address ; mcontract showtimelineactivity false ; } get the ethereum address in the blockchain network, the address can be used like a user’s account as the balance and the transaction history can be checked using the address in this sample project, get the address from keystore and display the address and account balance in the bottom sheet of the screen keystore is a hierarchical deterministic hd wallet, a standard tree structure represented by derivation paths for the ethereum address, use “m/44'/60'/0'/0/0” follow bip44 it is implemented at getethereumaddress string hdpath, getethereumaddresscallback callback in presenter/intropresenter java arraylist<string> path = new arraylist<> ; path add hdpath ; scwservice getinstance getaddresslist new scwservice scwgetaddresslistcallback { @override public void onsuccess list<string> list { string seedhash = scwservice getinstance getseedhash ; string address = list get 0 ; callback onaddressreceived true, 0, address, seedhash ; } @override public void onfailure int errorcode, string errormessage { callback onaddressreceived false, errorcode, "", "" ; } }, path ; sign a transaction ether value transfer or smart contract execution is executed by transactions that users create and sign signing a transaction is the process of generating a signature on it using the private key of the transaction sender samsung blockchain keystore can be utilized to sign a cryptocurrency transaction, such as ethereum by implementing the following steps creates an unsigned transaction, and requests samsung blockchain keystore to sign the transaction via apis like signethtransaction then the user will see a transaction confirmation page on a secure screen called, trusted user interface tui executed in trusted execution environment tee by samsung blockchain keystore once the user confirms the transaction with pin or biometrics authentication, like fingerprint, samsung blockchain keystore will sign a transaction with the private key derived from the given hd path when samsung blockchain keystore returns the signed transaction, your app can submit or send the signed transaction to the blockchain network in this sample project, create an unsigned transaction to execute posting a comment smart contract in addition, sign the transaction with keystore and send the transaction it is implemented at signtransaction in presenter/writefeedpresenter java // sign the transaction with samsung blockchain keystore // use hdpath m/44'/60'/0'/0/0 final string hdpath = "m/44'/60'/0'/0/0"; scwservice getinstance signethtransaction new scwservice scwsignethtransactioncallback { @override public void onsuccess byte[] signedtransaction { boolean result = sendsignedtransaction signedtransaction ; listener transactiondidfinish result, "" ; } @override public void onfailure int errorcode, string errormessage { listener transactiondidfinish false, "error code " + errorcode ; } }, unsignedtx, hdpath, null ; run the app and try it out the app screen should look like below you're done! congratulations! you have successfully achieved the goal of this code lab now, you can create a decentralized app by yourself! if you're having trouble, you may download this file keystore sdk complete code 897 07 kb

https://developer.samsung.com/codelab/blockchain/keystore-sdk.html

Develop Samsung Blockchain

doc

Overview

samsung blockchain keystore sdk essential contents samsung blockchain keystore sdk v1 6 0 | dec 12, 2023 431 47 kb api reference v1 6 0 160kb release note programming guide sample application 340 78kb overview samsung blockchain keystore puts consumers in control of their data by providing a platform to consolidate and easily manage private information and digital keys with vaultlike security samsung blockchain keystore is isolated within the samsung knox trustzone and protected by defense-grade trusted execution environment tee software to ensure complete security, the private key and information located in the samsung blockchain keystore are never saved to a samsung or external cloud, nor is it seen by the devices’ android os this allows samsung blockchain keystore to provide security unlike ever before, protecting information from data breaches, malware, or other threats the samsung blockchain keystore stores and processes private data to allow create, store, manage, and backup of a private key, including the ability to import already generated private keys from third-party applications this can be protected through a preset mandatory pin, with the option of further protection through fingerprint authentication authorization of digital signatures for use with your android app and services that require a private key for stronger security during encrypted transactions or purchases the facilitation of a trusted user interface trusted ui ensures the information exchanged between trusted applications and consumers that can’t be accessed or modified by any malware or unauthorized application enabling cryptocurrency transactions please refer to keystore sdk restrictions section for more details integration process api key will be issued after the internal team’s review it may take several weeks to complete the review process if there are many submissions an additional dapp partnership is required for listing on the samsung blockchain wallet please refer to the getting started section in the programming guide for more details in each step benefits samsung blockchain keystore sdk allows your android dapp to communicate directly with samsung blockchain keystore, a preloaded feature on selected galaxy devices by integrating samsung blockchain keystore sdk into your android app, you can leverage the following get blockchain address to link to the samsung blockchain keystore developers can link user’s blockchain address like a user’s account with the address returned from samsung blockchain keystore, developers can check and show users how much cryptocurrency balance is in the account as well as view the transaction history samsung blockchain keystore supports bip-39 compatible hd hierarchical deterministic wallet – a standard tree structure, represented by derivation paths developers can use samsung blockchain keystore api to enter an hd path samsung blockchain keystore will derive the address from the public key that corresponds to the hd path so developers can simply receive and utilize the address in return sign a cryptocurrency transaction developers can use samsung blockchain keystore api to request the samsung blockchain keystore to sign a cryptocurrency transaction samsung blockchain keystore will show the requested transaction to the user on a secure screen called, trusted user interface tui , executed in the trusted execution environment tee once the user checks the transaction information and confirms the transaction with a pin or a biometric authentication like fingerprint, samsung blockchain keystore will sign the transaction with a private key derived from the root seed stored in the secure file system check samsung blockchain keystore status developers can use an api provided by the samsung blockchain keystore to check if a user is ready to use samsung blockchain keystore if the user has not created a wallet yet, developers can direct the user to create a new wallet to leverage samsung blockchain keystore features when a user chooses “create a wallet”, it implies that a root seed is created and stored safely in the secure file system the user can also “import a wallet” by entering mnemonic words created from a different wallet, thereby restoring the root seed samsung blockchain will check the existence of a root seed and return the status value

https://developer.samsung.com/blockchain/keystore/overview.html

FAQ security, blockchain, mobile

doc

FAQ

faq q01 what is the difference between samsung blockchain sdk and samsung blockchain keystore sdk? a samsung blockchain platform sdk is a superset of sdks it focuses to offer a friendly blockchain solution especially for mobile developers you can use keystore sdk if you already have dapp development experience when you need a hardware wallet but still, you may need a deeper knownledge to use it so that platform sdk may be a better option for beginners the main difference is the existence of network module samsung blockchain platform sdk is available to communicate with an external blockchain node providing a payment solution also samsung blockchain platform sdk has cucumber web-based dapp browser which is built using android webview so it is helpful to reduce costs to build your dapp for mobile environment q02 what would be a good choice among sdks? a samsung blockchain sdk the blockchain dapp developer needs a simple payment solution, dapp without handset limitation, integrated with various cold wallets, and a legacy player who already has an experience with e-commerce ex online shopping app especially it can be a better option for web based dapp partners who has a plan to integrate the service into mobile environment samsung blockchain keystore sdk for dapp partners who needs a key storage to directly handle it q03 which coin is supported? a it supports ethereum and tron you can see erc20, erc721 and trc10, trc20 item information when it follows the specification q04 does it have any device limitations / restrictions? a no samsung blockchain platforms sdk doesn’t have any device or region dependency but, please note that it needs a cold wallet so that it follows the cold wallet’s restriction for example, you can use your dapp integrated with sdk on any device released by samsung when you connect to external cold wallet but if you use the samsung keystore, it has to be same with the keystore’s restriction q05 what should i do using keystore via platform sdk? a you need an api key for getting a permission to access keystore please refer request for api key note that, in case of integrating ledger devices, you don't need this process q06 what should i do when i get the following build error "failed to transform artifact 'bcprov-jdk15on jar"? a add the following to your project's gradle properties android jetifier blacklist=bcprov

https://developer.samsung.com/blockchain/platform/platform-sdk/faq.html

FAQ security, blockchain, mobile

doc

FAQ

faq 1 what can users do with samsung blockchain keystore? with samsung blockchain keystore preloaded on select galaxy devices, users can now easily create a key storage in the secure file system for blockchain transactions users can run samsung blockchain keystore to check the 12 mnemonic words that correspond to the root seed that is used to derive both public and private keys when using a decentralized app dapp or cryptocurrency wallet that have integrated samsung blockchain keystore sdk, users will be able to confirm their transactions on a secure screen and sign the transaction with a private key 2 what happens if a user switches from a non-samsung blockchain keystore-supported device to a samsung blockchain keystore-supported device? if the dapp is integrated with a wallet that supports bip39-standard hd-wallet hierarchical deterministic wallet , such as metamask, dapps will need to make sure that users have saved the 12 to 24 mnemonic words from the wallet afterwards, users can restore the same wallet on samsung blockchain keystore by entering the 12 to 24 mnemonic words however, simply installing the same dapp or using smart switch from a non-samsung blockchain keystore supported device to a supported one will not move the user’s account directly 3 how does the authentication method work? personal identification number pin and biometrics authentication like fingerprint are all executed on samsung devices, and are not dependent on any type of network samsung blockchain keystore will authenticate users via pin or biometrics when a user’s confirmation is needed, such as signing a transaction 4 how is the key pair generated? samsung blockchain keystore generates the key pair on the device itself and safely stores them on the device samsung blockchain keystore does not rely on other network or third party to generate these keys 5 what are mnemonic words? mnemonic words are compatible to bip-39 standard and is the root to creating public and private keys users can check their mnemonic words, also known as recovery phrase, in samsung blockchain keystore settings the recovery phrase is the only way a user can recover the wallet when a device is lost or stolen 6 what is tui? trusted user interface allows users to make an input and show display safely, in a trusted execution environment tee supported by samsung knox a mobile security platform samsung blockchain keystore leverages this tui to help users to enter a pin and confirm transactions with greater security 7 what should i do if i get an error code, error_package_signature_verification_failed? it means your app does not have the authorization to access samsung blockchain keystore developers can use developer mode to bypass the app verification and enable apis however, for your release version, an api key, issued by samsung blockchain keystore team, will need to be included in your app to work properly 8 how can i send a signed transaction? sending a signed transaction is not in the scope of samsung blockchain keystore developers will need to setup their own nodes or use other public nodes 9 can i test samsung blockchain keystore by downloading it from galaxy store? no, samsung blockchain keystore is preloaded on selected devices only if your device is not supported, then you won’t be able to find it in the galaxy store either developers will need to test and integrate on the supported devices, or try out the remote test lab in samsung developers site to experience devices needed for samsung blockchain keystore sdk integration 10 what is the purpose of a seed hash? a seed hash aims to help developers distinguish if a user has setup samsung blockchain keystore and whether the root seed has been changed or not every time a root seed or a wallet is created, a random string, or a “seed hash” value will be created and returned to the developers this is not related to the contents of the seed, but developers can use the seed hash to check if a user’s root seed has been changed if the root seed has been changed due to user deleting and re-creating a wallet, then the developers will need to get user’s address again from samsung blockchain keystore and link it to your android app, since a different root seed implies a different address 11 is there a plan to support other cryptocurrencies as well as expand supported regions? yes, we plan to support more cryptocurrencies and expand supported regions in the near future

https://developer.samsung.com/blockchain/keystore/keystore-sdk/faq.html

Didn’t find what you were looking for?

FAQ

Search frequently asked
questions
by keywords.

Join the Forum

Visit the Forum to ask
questions and exchange
ideas with other developers.

Get Support

Submit a 1:1 Support request
and receive a response
within 2 business days.

Preferences Submitted

You have successfully updated your cookie preferences.