|
Why are you guys using a WMA format to broadcast? Why not mp3? I can't listen.
|
|
|
|
Glad to know this is how the trezor people conduct business when confronted with a serious problem. Extremely rude and unprofessional.  Do you guys not get it? You built something that allows the transfer and storage of money, when you have an issue, patients isn't going to last forever. Get use to it if you are going to be conducting business in this manner. |
|
|
|
|
Bitcoinjs-lib 0.2.0 deserializes the transaction hex perfectly and I just tested it. I don't know what version you are running but I suggest using that version.
|
|
|
|
Pay me $250 an hour and I will gladly add it. Sorry I don't work for free  If it's tanking your business it's in your self interest to fix it for "free". Just sayin' Not really this is kinda why I paid for this device, so they would handle all that. If I wanted to do this myself I would build my own hardware wallet. I am looking into it but I am not setting up a dev environment. I just don't have the time. I have actually been using bitcoinjs so I will for sure be passing in this into that and looking. I doubt this since they have pretty good test at bitcoinjs. |
|
|
|
As well as I posted the EXACT line and error which should be a quick fix sorry but transaction parser in javascript isn't that hard.
https://github.com/trezor/webwalletPull requests are welcome Bottom line: It seems that the bug is in bitcoin.js library, which is not our, which makes the fix much more complicated that it seems to be. Pay me $250 an hour and I will gladly add it. Sorry I don't work for free |
|
|
|
I AM TROLLING?
I'm glad you posted the screenshot, so I don't have to do it and anyone can see that: a) we always responded within 24 hours timeframe b) I told you that you can check if the transaction was broadcasted on blockchain.info c) you never told us what is this problematic transaction that holds your business, otherwise we would check it for you on blockchain.info if you are not capable of doing it by yourself d) you are demanding a fix (not an answer, but A FIX!) after 48 hours which is ridiculous -- even the biggest IT companies like Apple, Microsoft, Google can't and won't provide this kind of support to their end costumers e) you are putting off the solution because 2 of 3 developers have to debunk your accusations on the forum instead of working on the problem FWIW This is my last post on this topic here as I am putting you on my ignore list to protect my mental health. I am sure most of the people that will read your posts will do the same. I will leave the communication with you to our support team which is still learning but is already very capable at handling difficult individuals. A) 14 hours is not a good time frame when you have such a small user base. As well as I posted the EXACT line and error which should be a quick fix sorry but transaction parser in javascript isn't that hard. B) I have been checking but how do I know if the transaction will/will not be broadcasted after the problem is solved? That is the whole question which I still have gotten an answer. Also Slush was recommending that I use a program, that doesn't even support trezor at all. C) I have actually mentioned it many times, but what does business transactions have over regular stuck transactions there should be no difference. D) I can call apple microsoft and get a straight answer. Also this isn't a bug it is pure laziness. E) I am not putting off any solution, the solution was to use a program that doesn't stable support trezor. That is horrible service sorry. Thanks for putting me on your ignore list as this shows that you can't answer my question and response. Also your support is very unprofessional and rude. I want my situation taken care of now, since my reputation IS AT STAKE, but I guess that means nothing to you. I also not removing my trust feedback from any accounts that are associated with trezor as I am clearly seen they need to plan better and NOT DO LAZY coding. |
|
|
|
I am going on 36 hours waiting to see if they are going to fix my balance, as well as if my transaction that is signed is going to be broadcasted.
This isn't any problem of Trezor itself, rather, as stick said, mytrezor cannot deal (yet) with this specific non-standard transaction. If you hurry with your transaction, you can give a try to Electrum, which has finally Trezor support. There's quite a good chance that the transaction will go thru there. I believe that gweedo is able to send btc to his client via other means. He is just concerned than the original transaction may still get broadcasted (double spend), but that can be easily prevented. You just need to resend the money spent in your dangling unbroadcasted transaction. Then the dangling transaction cannot be accepted anymore thus the doublespend is avoided and everybody is happy. Edit: It might not be so simple if the transaction history is broken because of the issue stick talks about above. I'd like to hear when and how this resolves. Also trezor support can't you not insult your customers... It is very rude and unprofessional. Dear gweedo, if you are referring to me calling you retarded than I want it to be noted that I'm not a Trezor support guy and I'm in no contract relationship with satoshilabs. So it's not "trezor support insulting customers". I understand that you have your balance blocked and that is frustrating. And it also seems that I misunderstood the problem, so please accept my apology for being rude. Even though I have no obligation to you, because you are not my customer. I was clearly referring to slush and the support ticket I opened about 3 days ago. |
|
|
|
Bugs are normal in the software world ! We find them by using intensively the product, inform the programmers, and wait for a fix ... Does Microsoft sell free bug products ? NO ! Does Linux work without bugs ? NO ! So... Wait for the fix, or apply the workaround !
By the way, I am currently not an owner of a Trezor, but I like the concept and will buy one very soon !
But to be honest this isn't a bug that should be in the release, right now if I get your trezor address, I can DDOS you by sending a p2sh transaction to it. That is basically a part of the bitcoin protocol and should have never been released. I understand, but accept the fact that bugs are in the nature of each software ... I do work on encryption devices with smartcards, fingerprints, several encryption protocols... Believe me, a stupid bug can not be seen up to the moment it is discovered by some angry customer ... After that, it is a big chance you found that bug, so they will fix it ... You are the lucky guy ! Try to negociate another Trezor as per compensation (and send it to me  ) ) It isn't a bug to be honest, it is laziness in not building out the entire bitcoin protocol. And no... |
|
|
|
Bugs are normal in the software world ! We find them by using intensively the product, inform the programmers, and wait for a fix ... Does Microsoft sell free bug products ? NO ! Does Linux work without bugs ? NO ! So... Wait for the fix, or apply the workaround !
By the way, I am currently not an owner of a Trezor, but I like the concept and will buy one very soon !
But to be honest this isn't a bug that should be in the release, right now if I get your trezor address, I can DDOS you by sending a p2sh transaction to it. That is basically a part of the bitcoin protocol and should have never been released. |
|
|
|
but what happens if electrum chooses different inputs than mytrezor?
a) You can send all balance to another trezor's address, then everything will be working in mytrezor again. b) Or you can just send amount of out Trezor in Electrum which you need right now. We'll release fix of this issue very soon. Will you reimburse me for sending two transactions, due to the faultiness of your web wallet?
No. No bitcoins has been lost. Edit: Also the Trezor support in electrum, isn't even full working... So how is this even an option for anyone?
Sending and receiving works normally (well, normally in electrum style). What's not working yet is setup and recovery, but it's not necessary in your use case. Please don't spit out things to save face.
Please stop trolling. I'm not refusing the fact that you triggered a bug in mytrezor, but I'm proposing you instant solutions. a) I can't because your web wallet took those credits because it thinks it sent that transaction out, so right now I can't send any amount to any address so this is not an option. b) Electrum has no trezor support in a stable version so stop recommending THIS AS IT IS NOT AN OPTION I CAN USE! But you want me to do another transaction so no bitcoins are lost YET, but if I do another transaction and the other transaction broadcast, will you reimburse me for that, SINCE IT IS YOUR DIRECT FAULT. Otherwise you can talk to my lawyer about this, if you wish. Electrum and Trezor DON"T WORK TOGETHER STOP RECOMMENDING THAT AS AN OPTION IT ISN"T! I AM TROLLING?  I BEEN NOTHING BUT PATIENT and even being helping as much, but your SUPPORT IS PLAIN RUDE! SO YOU STOP TROLLING. |
|
|
|
It is still an issue that it is your guy's fault... Also what if electrum picks different inputs than what mytrezor picked, then that transaction will still go thru.
Yes, there's very minor bug in myTREZOR which you triggered by non-standard transaction. We're aware of it and which we're working on fix. I gave you a hint for solution - use Electrum. If you don't like downloading Electrum, just sit and wait until we fix myTREZOR. Rome was not built in a day. Wait I never said I didn't like downloading Electrum, but what happens if electrum chooses different inputs than mytrezor? Will you reimburse me for sending two transactions, due to the faultiness of your web wallet? Edit: Also the Trezor support in electrum, isn't even full working... So how is this even an option for anyone? Please don't spit out things to save face. |
|
|
|
...
This is the worst service ever, this is dealing with money! I am trying to do business with people and YOU GUYS are holding me up. Then I get bad ratings because I decided to use a web wallet that doesn't work. Welcome to Czech Republic I guess so... This is not an issue of TREZOR, no coins were lost, but myTREZOR transaction history is choking up because of some nonstandard transaction was used to pour-in coins.
It isn't an issue of trezor, but it is an issue of mytrezor which you guys still run, so it is your fault. I am going on 36 hours waiting to see if they are going to fix my balance, as well as if my transaction that is signed is going to be broadcasted.
This is the worst service ever, this is dealing with money! I am trying to do business with people and YOU GUYS are holding me up. Then I get bad ratings because I decided to use a web wallet that doesn't work.
The web wallet never works well, and there is always an issue. Get your stuff together and FIX THIS. Not only have I provided the exact error from my console log, I have to see if my transaction is dropped or not, so I don't send double the money.
I want some compensation not only for my patients but for my business transaction that YOU GUYS are holding up.
I have left negative trust feedback on everyone I know that is involved in this project.
Dude, send all your money to a new address. If this new transaction does confirm, the old one cannot confirm anymore. Then send BTC to your client again. If any of that fails, then it *might* be a trezor issue. If this does work then you or server had some network glitch, with no harm whatsoever and you are just retarded to scream like a child about it. Why should I corrupt the seed of my trezor by loading it into another wallet? I am going on 36 hours waiting to see if they are going to fix my balance, as well as if my transaction that is signed is going to be broadcasted.
This isn't any problem of Trezor itself, rather, as stick said, mytrezor cannot deal (yet) with this specific non-standard transaction. If you hurry with your transaction, you can give a try to Electrum, which has finally Trezor support. There's quite a good chance that the transaction will go thru there. It is still an issue that it is your guy's fault... Also what if electrum picks different inputs than what mytrezor picked, then that transaction will still go thru. I am going on 36 hours waiting to see if they are going to fix my balance, as well as if my transaction that is signed is going to be broadcasted.
This isn't any problem of Trezor itself, rather, as stick said, mytrezor cannot deal (yet) with this specific non-standard transaction. If you hurry with your transaction, you can give a try to Electrum, which has finally Trezor support. There's quite a good chance that the transaction will go thru there. I believe that gweedo is able to send btc to his client via other means. He is just concerned than the original transaction may still get broadcasted (double spend), but that can be easily prevented. You just need to resend the money spent in your dangling unbroadcasted transaction. Then the dangling transaction cannot be accepted anymore thus the doublespend is avoided and everybody is happy. Edit: It might not be so simple if the transaction history is broken because of the issue stick talks about above. I'd like to hear when and how this resolves. Yes this, but I don't remember the inputs of the transaction, because stupid me thought it would work. Also trezor support can't you not insult your customers... It is very rude and unprofessional. |
|
|
|
|
I am going on 36 hours waiting to see if they are going to fix my balance, as well as if my transaction that is signed is going to be broadcasted.
This is the worst service ever, this is dealing with money! I am trying to do business with people and YOU GUYS are holding me up. Then I get bad ratings because I decided to use a web wallet that doesn't work.
The web wallet never works well, and there is always an issue. Get your stuff together and FIX THIS. Not only have I provided the exact error from my console log, I have to see if my transaction is dropped or not, so I don't send double the money.
I want some compensation not only for my patients but for my business transaction that YOU GUYS are holding up.
I have left negative trust feedback on everyone I know that is involved in this project.
|
|
|
|
|
Is there a way to tell if my transaction will be dropped or broadcasted? I have an open ticket but this is going on for 36 hours and I need to get some coins to a person, and I don't want it to be broadcasted twice.
Maybe add a pending tx tab or something like that.
|
|
|
|
I been seeing this for a couple of days.  It's reported, we know about the problem and we are working on it. And yes, it's caused by multisig transactions. I didn't get any multi sig transactions... Also when is someone going to answer my ticket as it has been sitting for a long time. Over 14 hours! |
|
|
|
I been seeing this for a couple of days. Did you send any multisig (m-of-n) transactions to it by any chance? This happend to me. I feel like this is needed to be said since so many people report in with a similar problem: I believe some of the stock USB cables are broken (white and blue) due to a wrong wiring. If the device is not recognized, unplug the cable immediately and if it works with another one, never use the stock cable again. Playing devils advocate: using a broken cable may harm the device. No I didn't send any multi sig to it. The cable isn't broken as I was able to sign transaction. |
|
|
|
Can someone please explain why SQRL was not sufficient, and what BitID fixes over that?
SQRL and BitID, are basically the same thing, just one uses bitcoin addresses. Also since bitcoin addresses are becoming more ubiquitous it would be a better way. Technically we could also ask the question why not use PGP keys? |
|
|
|
Will there ever be a point where I won't have to download software for the mytrezor site to recognize it? My school doesn't allow installing third party apps on OSX
Probably not, it is the short answer. Also can stick, slush or someone answer my open ticket, it has been quite a while now. |
|
|
|
I been seeing this for a couple of days.
Reaching our support is usually better way how to deal with this kind of stuff. Just did I been seeing this for a couple of days.
Click forget device, then disconnect and then reconnect. Did this and it didn't work. |
|
|
|
I been seeing this for a couple of days. |
|
|
|
|
Show Posts
