Topic: GreenAddress: open source multisig wallet service - page 5. (Read 28195 times)

OK, I am BACK.

I got an emailed notice yesterday that said:

>>>Some of your deposits will soon expire because of nLockTime.
>>>
>>>Please log in at https://greenaddress.it/wallet/ to re-deposit them.

...which I assume is related to my problem (above) of having screwed up my 2FA/GoogleAuth setup in my GreenAddress wallet.

So: what do I need to do here? 

I want to either get the small amount of bitcoin OUT of that wallet, moved into a new GreenAddress wallet I will set up again from scratch (hopefully not goofing up the 2FA this time) -OR- just somehow re-set the existing wallet again (turn off 2FA?) so I can use it... what's the best way to go here?

Please "ELI5" to a noob (me) as simple as possible LOL

I'm having trouble accessing my funds in the GreenBits app and can't login on the website either (it just keeps saying that I'm already logged in - maybe my phone didn't log out correctly?)

I'm using the LG Nexus 5 with a TREZOR.

I have the app GreenBits installed on my Android phone.

When I try to sweep a Wallet after scanning the private keys the following message is displayed:
"Not Enough Money"

The wallet has 0.5$ in BTC
Isn't that enough to sweep the funds?

is the bug confirmed / fixed?

Sounds to me like that might be a bug....

Just a suggestion: if you're only using different accounts for keeping funds separate, it might make more sense to use the built-in multiple accounts feature (near the bottom of the settings page).

Ok, it works, but if i login with my other wallet (with passphrase) and logout and login again (with pin number, same pin) then i will be logged in into my 1st wallet and not into my 2nd wallet that i used the last time.

Do you not have a "Show other logins" option just below the PIN field?

If somebody has 2 or more greenaddress wallets then he has to clear the browser history (cookies, etc.)  to be able to login to another wallet, because at login page you can only enter your pin number and there is no button to forget current wallet data. (login with another account/wallet)

thx  for do nothing

When i add a new entry to the address book and want to use it at the send money tab I almost always got an error:  "Invalid recipient address."  (I have to select it many times before your system will accept it after send money button click )
Please fix it.

I never got my Trezor to pair with the Chrome app. tryexcept was helping me, starting here (but we never solved the problem): https://bitcointalksearch.org/topic/m.10398518

Question: Do you have to wipe the Trezor to use it with GreenAddress? I already have a regular Trezor wallet on there. Maybe that is the problem? I see that there is the option to clone a GreenAddress wallet to a hardware device, but it has to wipe the device to do so.

OK, thanks.

I got the emailed ZIP file... not really sure yet what that enclosed "nlocktimes.encrypted" file is for, but I suppose it'll become clearer later.

Anyway, last transaction was on 03-17-2015 so gotta wait till about mid-June to proceed here I guess... at least it's only about $35 worth of bitcoin stuck there, good thing I didn't move more into GreenAddress until I've thoroughly learned/understand all of this stuff.

BTW I should say I do like the GreenAddress wallet overall, it's just pretty clear that users need to be fully informed of the pitfalls and hazards of this more ADVANCED encryption and wallet protection technology, before using it seriously. "Being Your Own Bank" with bitcoin means nobody else can fix it for you if YOU screw it up (like I did, by not having a second 2FA option enabled).

So, hopefully my messing this up here and talking about it on the forum might help others avoid problems: my pain is your gain LOL

I'll be back after about 6-17 to continue this saga, Stay Tuned 

No bright ideas from me....

The only other troubleshooting step I can think of would be to extract the shared secret from Google Auth, and check to see if it matches the shared secret on GA's side. Doing so would require your phone be rooted, and would require some work on your part (and on GA's).


First step: log in, go to Settings -> Security, and click the "Send all nLockTime transactions by email", and save the nlocktimes.zip file you receive via email in a safe place (and be sure to keep your mnemonic around somewhere too, it'll also be required later).

Second step: figure out when you can perform the recovery. Use a block explorer to determine the date and the tx height (in blocks) of your most recent tx (inbound or outbound). Assuming you haven't changed the defaults, add 12960 to this tx height, and add 90 days to the date. Set a reminder on your calendar for this +90 days date.

Step three: visit here: http://greenaddress.github.io/gentle/, and do a "File -> Save as" to save the web page recovery tool to your PC. Keep it along side the file you saved from the first step.

Step four: Wait.... when your reminder date comes nears, check the block height of the most recent block at your favorite block explorer, and if it exceeds the the height you recorded in step two, open the page you saved in step three and follow the instructions. You'll need your full mnemonic at this point as well.

The recovery page only works with Firefox and Chrome (but see here to work around a problem when using it with Chrome). I've tested this procedure once in the past, and had no trouble getting it to work (except for the Chrome issue I just mentioned).

Hi Folks:

Okay I'm back here to this thread, and over the last week or so I've tried *everything* I can, based on info above, to get my GreenAddress wallet working again.

But nothing I do works, the GoogleAuth 2FA simply just always says invalid.

I've tried rebooting my iPhone, I'm even using another instance of Google Auth via the Chrome applet (and both iPhone and applet are giving the same codes, simultaneously, on totally different hardware: so that would SEEM to indicate that everything is sync'ed up correctly, right?)

I could've sworn that I had it working *at first* though... I saved the QR code and text info and checking that against my GAuth setup appears to be okay.  And ALL OTHER instances of GoogleAuth I'm using everywhere else, like on my blockchain.info wallet and for localbitcoins etc, are ALL working fine!

So, WHAT could have gone wrong here, really? What am I missing?

Anyway, if the GoogleAuth thing can't be fixed somehow, what's next?

Do I have to wait for the 90 days time-out and get the coin out of this wallet that way? That'll be around end of June or early July I guess.

How exactly do I do that?  OR would it be better to wait until then and address it in another forum topic?

TIA for all help.

I just installed the Chrome app and I've got to say I love the wallet. Great work!

It is... it means it is possible (although a small bit painful) to recover your funds, even in the worst case.


tryexcept is a GA employee, I'd wait for his response, perhaps he can help. (edited: oops, looks like he beat me to the punch)


I agree, if someone enables only a single 2FA method that offers no recovery option, it would be nice to warn them of potential issues.

As far as I know there's nothing wrong with you Google Authenticator seed and assuming your phone didn't flip some bits internally you just need to synchronize your phone properly.

It happens often that Google Authenticator goes out of sync.

We can't just enable any other 2FA ourselves. With the email what you can do is unlock the funds yourself when the timelock expires, which is by default 90 days from your last transaction unless you have changed this value. This is by using a zip attached to the emails and a tool called Gentle you can use with Firefox.

I would not concentrate on this option just yet as I am pretty sure a resync to Google Authenticator will do the trick, it is always this in the end when it doesn't work properly.

Hi, thanks for replies.

I tried the "enter GAuth code after time expired" trick... but no go.  Didn't work, still just says invalid code.

This wallet DOES have my email associated with it, so that's good news, I suppose?  What can be done at GA's end with this info?  Maybe manually turn on email 2FA or something??

The main problem here, I suppose, is that the ONLY setting enabled for this wallet's 2FA at the moment is Google Authenticator.  And since GA saw fit to stop working for whatever reason, I'm locked out prevented from doing anything.

Earlier, I had the voice phone option enabled at first (before GAuth) but I found it annoying so I turned it off.  So the only 2FA enabled now is JUST Google... clearly in hindsight my main mistake here I guess is not keeping a second 2FA choice turned ON, but for some reason I was thinking there had to be only one at a time enabled.

Might be a good idea in the GreenAddress UI to make a note that "more is better" (?) to prevent others in the future from making this mistake?

So... next step here? HOW to get some other 2FA going somehow, so I can turn OFF and/or re-install or re-initialize GoogleAuth???

Hi,

Google auth works for our accounts too. if it works for other sites it may mean they have a more relaxed timeout while GreenAddress only allows the codes in the window shown in the authenticator app.

this is to say that this points to a tiny synchronization issue that usually is fixed by a resync of the app (sometimes a full restart of the phone seems necessary)

let us know if this fixes it and if not we can try to work out something.

some users have found a way by using codes after they expire (which assumes the phone has the clock slightly ahead)

Hmm... the one time I emailed them, they got back to me the next morning....


I'm not sure what the technical issue might be. FWIW it's working for me at the moment.


The whole point of 2FA w/multisig wallets is that you can't access them without your 2FA... if there was a simple recovery procedure, that'd mostly defeat the purpose. I take it you only set up one 2FA method, with no backup method?

Did you ever add an email address to your GA account (you can't add one now because it requires a 2FA code)? If so, it is possible to regain access to your funds even w/o GA's help but there will be a pretty long delay (probably around 90 days). Let me know and I'll point you towards the directions to do this, in case GA doesn't get back to you.

Hi GreenAddress People:

I'm posting this here just 'cuz I'm not sure where it should go... already tried emailing for support (over a week ago) but got no reply as of yet, so... 

Topic is: I am having a problem with the GoogleAuth 2FA on my GreenAddress wallet/account.  GAuth is working fine for other sites I use it with (LBC, BC.INFO, etc) so it's not likely a time-sync issue.

Obviously the QRCode for my GreenAddress wallet *SHOULD BE* okay since it worked at first, i.e. when I first set it up!

But it's now stopped working, for some reason.

Any time I enter the GAuth code for anything in GreenAddress all I get is the "code is wrong" error.  I've tried it on the website based wallet, on my iPhone using the app, and even using the GoogleChrome standalone app. Same problem each time.  GAuth just not recognized as correct, ever, anywhere.  Just ain't working.

So I then tried turning OFF the 2FA entirely, but doing that requires a GoogleAuth code!  So, duh, that's not gonna work either.

At the moment I have only about $20-$30 worth of bitcoin in my GreenAddress wallet (was just using it to test out how GreenAddress works, before committing more funds to it perhaps) but those bitcoin are now essentially locked away from me, can't MOVE anything without the 2FA code.

I *do* still have my mnenomic for the wallet, so hopefully that means that I can, somehow, still get the bitcoin out of this wallet, if the 2FA problem/issue cannot be resolved?  How would I go about doing that, exactly?

Again, sorry if this is posted in the wrong place or should be on it's own topic here... moderators please feel free to move topic if so.

TIA for any/all help anyone can provide.