[{"data":1,"prerenderedAt":331},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fhardware-wallet\u002Ftrezor":3,"docs-surround-\u002Fdocs\u002Fhardware-wallet\u002Ftrezor":320},{"id":4,"title":5,"body":6,"description":311,"extension":312,"image":313,"meta":314,"navTitle":313,"navigation":315,"path":316,"seo":317,"stem":318,"__hash__":319},"docs\u002Fdocs\u002Fhardware-wallet\u002FTrezor.md","Trezor",{"type":7,"value":8,"toc":294},"minimark",[9,13,17,21,24,28,31,35,38,50,54,67,86,90,98,102,129,133,139,149,154,187,191,214,218,271,275,279,282,285,288,291],[10,11,5],"h1",{"id":12},"trezor",[14,15,16],"p",{},"We currently do not support smart contract transactions for the Hardware Wallets.",[18,19,5],"h3",{"id":20},"trezor-1",[14,22,23],{},"According to Trezor they don't consider accepting new coins (not clones of existing ones) to their official release.\nCurrently we investigate the possibility to add our app to an unofficial release.",[10,25,27],{"id":26},"instructions-for-the-host-machine","Instructions for the host machine",[14,29,30],{},"We support Linux, Windows and Mac, i.e. all the platforms on which the Beam Wallet is already supported. No additional tools\u002Fprerequisites are required. Just plug the HW wallet, it should be detected by our desktop wallet automatically.",[18,32,34],{"id":33},"note-for-linux-users","Note for Linux users",[14,36,37],{},"On Linux, however, the Beam desktop wallet should have appropriate permissions to connect to the HW wallet.",[14,39,40,41,45,46,49],{},"Desktop wallet can be run with elevated privileges (",[42,43,44],"code",{},"sudo",") but this is not recommended. Instead it's possible to enable device access for all the users in the system.\nTo allow this the following file should be downloaded, and copied ",[42,47,48],{},"\u002Fetc\u002Fudev\u002Frules.d"," into directory. After the device is re-plugged the new permissions should be in effect.",[18,51,53],{"id":52},"installation","Installation",[18,55,57,58,62,63,66],{"id":56},"install-git-and-python3-with-pip3","Install ",[59,60,61],"strong",{},"Git"," and ",[59,64,65],{},"Python3"," (with pip3)",[68,69,70,77],"ul",{},[71,72,73,74],"li",{},"Debain\u002FUbuntu: ",[42,75,76],{},"sudo apt-get -y install git python3 python3-pip",[71,78,79,80],{},"Windows\u002FMacOS: download from ",[81,82,83],"a",{"href":83,"rel":84},"https:\u002F\u002Fwww.python.org\u002Fdownloads",[85],"nofollow",[18,87,89],{"id":88},"install-trezor-bridge","Install Trezor Bridge",[14,91,92,93,97],{},"Go to ",[81,94,95],{"href":95,"rel":96},"https:\u002F\u002Fwallet.trezor.io\u002F#\u002Fbridge",[85],", download and install.",[18,99,101],{"id":100},"install-protobuf-compiler","Install Protobuf Compiler",[14,103,92,104,108,109,112,113,116,117,120,121,124,125,128],{},[81,105,106],{"href":106,"rel":107},"https:\u002F\u002Fgithub.com\u002Fprotocolbuffers\u002Fprotobuf\u002Freleases",[85]," and download the latest ",[42,110,111],{},"protoc"," for your OS.",[114,115],"br",{},"\nExtract it and add ",[42,118,119],{},"\u003Cpath to protoc folder>\u002Fbin"," path to the system ",[42,122,123],{},"PATH",": ",[42,126,127],{},"export PATH=$PATH:\u002F\u003Cpath to protoc folder>\u002Fbin",".",[18,130,132],{"id":131},"build-firmware-loader","Build Firmware Loader",[14,134,135,136,138],{},"Run the following commands (don't use ",[42,137,44],{}," prefix on Windows):",[140,141,146],"pre",{"className":142,"code":144,"language":145},[143],"language-text","git clone https:\u002F\u002Fgithub.com\u002FBeamMW\u002Fpython-trezor.git\ncd python-trezor\ngit checkout beam\ngit submodule update --init --recursive --force\n\nsudo pip3 install protobuf click requests mnemonic construct ecdsa pyblake2 typing_extensions\npython3 setup.py prebuild\n","text",[42,147,144],{"__ignoreMap":148},"",[150,151,153],"h2",{"id":152},"install-the-firmware","Install the firmware",[68,155,156,163,172,180],{},[71,157,158,159,162],{},"Wipe your Trezor device using ",[42,160,161],{},"python3 .\u002Ftrezorctl wipe-device"," command.",[71,164,92,165,108,169,128],{},[81,166,167],{"href":167,"rel":168},"https:\u002F\u002Fgithub.com\u002FBeamMW\u002Ftrezor_beam_minimal_wallet\u002Freleases",[85],[42,170,171],{},"firmware.bin",[71,173,174,175,179],{},"Restart the device to enter bootloader mode (video how to do it ",[81,176,177],{"href":177,"rel":178},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=xVBiSFTx0qQ",[85],").",[71,181,182,183,186],{},"Call ",[42,184,185],{},"python3 .\u002Ftrezorctl firmware-update -f \u003Cpath to firmware folder>\u002Ffirmware.bin"," to install firmware.",[18,188,190],{"id":189},"windows","Windows",[68,192,193,204,209],{},[71,194,57,195,198,199,203],{},[42,196,197],{},"trezorctl"," ",[81,200,201],{"href":201,"rel":202},"https:\u002F\u002Fwiki.trezor.io\u002FInstalling_trezorctl_on_Windows",[85]," .",[71,205,174,206,179],{},[81,207,177],{"href":177,"rel":208},[85],[71,210,182,211,186],{},[42,212,213],{},"trezorctl firmware-update -f \u003Cpath to firmware folder>\u002Ffirmware.bin",[150,215,217],{"id":216},"test-beam-with-trezor","Test Beam with Trezor",[68,219,220,227,235,246,258,268],{},[71,221,92,222,226],{},[81,223,224],{"href":224,"rel":225},"https:\u002F\u002Fbuilds.beam.mw\u002F#trezor_build",[85]," and download\u002Finstall the latest build.",[71,228,229,230,234],{},"Connect your device, go to ",[81,231,232],{"href":232,"rel":233},"https:\u002F\u002Ftrezor.io\u002Fstart",[85],", create a new wallet or recover with your seed phrase.",[71,236,237,238,241,242,245],{},"Run installed ",[59,239,240],{},"Beam Wallet"," and push ",[42,243,244],{},"create new Trezor wallet"," button.",[71,247,248,249,252,253],{},"Agree with generating ",[59,250,251],{},"Owner Key"," on Trezor device and wait, it usually takes about 15 sec.\n",[254,255],"img",{"alt":256,"src":257},"image","https:\u002F\u002Fuser-images.githubusercontent.com\u002F1101448\u002F65770926-c5d87f80-e13f-11e9-9095-a9fbac692917.png",[71,259,260,261,264,265],{},"Remember generated password from the ",[42,262,263],{},"Key Password"," page and enter it in the Beam Wallet.\n",[254,266],{"alt":256,"src":267},"https:\u002F\u002Fuser-images.githubusercontent.com\u002F1101448\u002F65770789-7e51f380-e13f-11e9-899e-33dc09d96787.png",[71,269,270],{},"Hurray, the wallet is initialized, now try to send\u002Freceive beams to test how it works...",[10,272,274],{"id":273},"usage","Usage",[150,276,278],{"id":277},"implications-of-device-auto-lock","Implications of device auto-lock",[14,280,281],{},"HW wallets usually auto-lock if idle for some time. This makes sense of course (otherwise, if left unlocked and unattended, it could be used by any stranger or intruder to steal your funds).",[14,283,284],{},"However in Beam the HW wallet is used not only to send funds, but also to receive. Hence the desktop wallet won't be able to receive funds while the device is locked. Our desktop wallet (both CLI and UI) gives an appropriate message if it can't access the HW wallet, and if\u002Fwhen the user unlocks it - the transaction will proceed. But if the user is not around then there will be no one to unlock the device, and all transactions will end stuck.",[14,286,287],{},"At the moment we recommend the following options:",[14,289,290],{},"Receiver: if you don't expect to receive eventual transactions, then we recommend keeping the auto-lock feature. If, however, you prefer to be able to receive transactions constantly, then consider disabling the auto-lock feature.",[14,292,293],{},"Sender: If you expect the receiver to be online, then send transactions as usual. Otherwise it's always possible to use offline transactions types (public offline, or max privacy), since those are non-interactive transactions, and the receiver is not involved.",{"title":148,"searchDepth":295,"depth":295,"links":296},2,[297,299,300,301,303,304,305,306,309,310],{"id":20,"depth":298,"text":5},3,{"id":33,"depth":298,"text":34},{"id":52,"depth":298,"text":53},{"id":56,"depth":298,"text":302},"Install Git and Python3 (with pip3)",{"id":88,"depth":298,"text":89},{"id":100,"depth":298,"text":101},{"id":131,"depth":298,"text":132},{"id":152,"depth":295,"text":153,"children":307},[308],{"id":189,"depth":298,"text":190},{"id":216,"depth":295,"text":217},{"id":277,"depth":295,"text":278},"Trezor Hardware Wallet support","md",null,{},true,"\u002Fdocs\u002Fhardware-wallet\u002Ftrezor",{"title":5,"description":311},"docs\u002Fhardware-wallet\u002FTrezor","ujZafuLaK_NzxL2as3le_b0scZQzZOT_4AjOxS3Zx34",[321,326],{"title":322,"path":323,"stem":324,"description":325,"children":-1},"Hardware Wallets","\u002Fdocs\u002Fhardware-wallet\u002Freadme","docs\u002Fhardware-wallet\u002FREADME","Hardware Wallet Support Overview",{"title":327,"path":328,"stem":329,"description":330,"children":-1},"Beam Hash III","\u002Fdocs\u002Fmining\u002Freadme","docs\u002Fmining\u002FREADME","Similar to most cryptocurrencies, Beam relies on miners to add transactions to the blockchain. While all nodes in the Beam network confirm the validity of transactions, Beam counts on miners to take on the massive heavy lifting in securing the Beam network.‌",1783006096272]