Bitgo github desktop
This introduces undesirable delays when sending. Because GreenAddress 2of2 accounts only allow sending coins when they are signed by both you and us, the service can act as a kind of guarantee that your coins cannot be double spent, since the service will not sign another transaction for the same coins when one is already in-flight. Services that choose to rely on this can therefore trust that a transaction they receive from GreenAddress cannot be double spent, eliminating the need to wait for the transaction to confirm.
These are known as instant transactions and they can be sent by ticking the "instant" checkbox when sending coins from our wallet software. Funds in your main GreenAddress account or a multisignature 2of2 subaccount require 2 signatures to be spent: In order to protect you from loss of access to your funds should GreenAddress become unavailable GreenAddress automatically creates pre-signed transactions which you can subsequently countersign to recover the funds to an address controlled solely by you.
These transactions are called nLockTime transactions because they can only be spent and confirmed by the network after a specific period of time.
If the service becomes unavailable, you simply wait until the specified period 90 days by default , then sign and send the transaction using our open source recovery tool garecovery. Once the nLockTime period expires these nLockTime transactions would allow you to recover the funds in the 2of2 account without requiring GreenAddress's signature. This also means that any limits placed on your spending in GreenAddress, such as 2FA requirements, cease to be enforceable by GreenAddress, and that these funds are no longer available for use in instant transactions because GreenAddress cannot guarantee that you have not tried to double spend them.
At this point GreenAddress will prompt you to redeposit the coins by sending them to yourself. This creates a new nLocktime transaction for you, while re-protecting the coins by once again requiring a GreenAddress signature to spend them.
In this way you can take advantage of instant transactions from 2of2 accounts, while always being sure you can retrieve your funds if the service is off-line. The redeposit operation is a standard bitcoin transaction and as such is subject to the usual network transaction fees. You can place your funds in a GreenAddress 2of3 account, in which case GreenAddress does not generate nLockTime transactions and therefore no redeposits are necessary.
You can increase the nLockTime period on your account which will reduce the frequency of the redeposits.
The downside of this is that should you need to recover your funds for example, because you lose your two factor authentication you will have to wait for longer. We recommend that you redeposit your funds when reminded, however redepositing is optional and failure to redeposit will not necessarily lead to the loss of any funds.
The main consequences of not redepositing are:. The funds in the account will no longer be eligible for instant confirmations because GreenAddress can no longer guarantee that you have not tried to double spend them. It becomes possible that anyone with access to both your mnemonic and the nLockTime. No, GreenAddress does not support this. GreenAddress will only sign standard bitcoin transactions. Yes, our https site supports Tor users. Our mainnet production site is at http: Unfortunately, many banks and payment services such as PayPal don't yet support Bitcoin directly.
For the time being, you can exchange your money using bank transfers and sometimes debit or credit cards via an intermediary like a Bitcoin exchange or a broker.
There are also online services and communities where you can arrange to exchange cash for Bitcoin. This is an area of rapid change and innovation and so we do not list or specifically recommend any services in this space.
The best service for you depends on many factors. We suggest you locate local services using your favorite search engine and carefully review any potential options. You should see new transactions in your wallet within seconds of it being sent by the payer. If you can not see your transaction in a block explorer, it probably means it is still propagating or failed to do so for example, setting the fee too low can cause transactions to be dropped.
We have sensible rate limits to prevent the service from denial of service attacks. It is extremely unlikely that a user will encounter these limits under normal use. If you find that you are hitting a rate limit, please contact support with the details. If you have a requirement that exceeds the current limits, please feel free to contact us to discuss your needs further.
Addresses change constantly for privacy and security reasons. Re-using old addresses makes it easier for others to group transactions together and can be less secure.
While GreenAddress does correctly process multiple payments to the same address, we recommend not re-using them. Addresses should be thought of as one-time receipt IDs rather than as unchanging identifiers such as traditional bank wire details. Please see the API documentation for more details. All previously generated addresses are available in the Receive tab under Advanced Options when using the Chrome or Cordova wallet clients.
Your private keys are not stored. They are derived on demand from your mnemonics as a seed to a BIP32 hierarchical wallet. Your mnemonics and private keys are never sent to the server. The server receives the public key and chaincode for generated addresses only. When you create a PIN, a random bit AES password is created and used to encrypt your mnemonics and store them on your device in encrypted form. This password is sent to the server and destroyed on the client.
If the server is given the correct PIN when logging in, it will return the password to the device in order to decrypt the mnemonics. If the server is given the wrong PIN three times, it will destroy the password at which point the user must use their mnemonics to log in. Note that the server never sees your mnemonics at any point. If you can't remember the PIN you use to login to your wallet, you will need to use your mnemonics to log in instead.
After entering the wrong PIN three times, the back end service will delete its copy of your wallet's random decryption key, at which point the PIN can no longer be used. Your wallet client will then ask you to login using your mnemonics and you can resume using the service as normal. The service never knows your mnemonics or passphrase; We cannot help you recover them if they are lost.
If you have a wallet with PIN entry enabled, you can use your PIN to log in to the wallet and then view the mnemonics from the settings menu. You should then write them down and store them safely. In all other cases you will only be able to retrieve your mnemonics by brute force trying various combinations of valid words.
This is similar to how a hacker might try to break into your wallet, and is not generally feasible. You should research third party services for wallet recovery, as GreenAddress does not offer assistance or support for wallet cracking for obvious reasons. To access the Bitcoin wallet only works after BitGo wallet software setup navigate to: The information you enter will be stored on your local database. Once logged in, select the gear on the top right hand corner. Set the BTC token limit to something reasonable, and ensure that you enter the public IP address of your 21 computer.
Your token will appear at the top of the page. Please feel free to fill in anything else that you feel would be useful or to create an issue with your suggestion, with an emphasis on tools that have broad use cases Generic Boilerplate Features User account sign up, sign in, password reset, all through asynchronous email confirmation. Social media logins Twitter, Facebook, Github Form generation. HTML macros and layout file.
Websockets for example for live chatting Virtual environment example. Digital Ocean deployment example. Flask-Login for the user accounts. We recommend you print out that PDF and write your passcode on the physical paper.
Lastly, there is an advanced option in the wallet creation to provide your own Backup Key by entering the public key of a Bitcoin address you control. Our enterprise customers use this practice. Hope this clears up the confusion. You can email us at security bitgo. So are you generating the password-protected pdf on the server-side or the client-side?
From my earlier response: We absolutely do not have the keys. The PDF itself is not password-protected, the keys are encrypted with a strong passcode client-side. The PDF is useless to anyone without your passcode.
As a reminder, you do not need to email this encrypted PDF. It is an option, not required in the flow. Your email address will not be published.
You may use these HTML tags and attributes: To spend your bitcoins, you need access to two of these three keys. It means the opposite. So for the love of God, stay the fuck away from these guys. April 10, at 5: April 10, at 8: April 22, at April 23, at Back, Back, Back It Up. When Bitcoin Met Pete says: May 31, at