Can you please check my last btcd deposit transaction. It was about 800 blocks ago.
http://cryptobe.com/address/bbQ3vYxDVW121iRGR7Gif7HLJyV1J5kGpx
OK, this one was strange as none of the MGW servers saw the txid
but it turns out the block explorer must have been on a fork as the txid is not on the blockchain
This required me to go back and forth with the user to get the details and then search all three MGW server logs and not so big of a deal, but my internet is very flakey so I had to relogin 7 times before I could confirm that none of the MGW servers knew about this, plus this acct is very active so needing to sort through that.
turns out it is not on the blockchain, so anybody running a node could just go to debug console and:
gettransaction <txid>
and get an error. so there is no way for MGW to process this (redundancy and automatic fork avoidance and emergency abort)
so PLEASE come up with some sort of first line of support for MGW. I do not mind investigating real bugs, but this sort of pre screening is not something the end user can do. Neither should an overworked dev who hasnt had time to eat anything except 2 bananas all day should either.
I will not do any more MGW support until there is some sort of first line of support in place. This means one or more people who can trouble shoot the most obvious problems and they PM me when there is an issue. I do not mind tracking down real issues. I mind having to do front line support that somebody else can do.
So, from now I will not be monitoring this thread and only responding to PM's about verified issues.
Thank you for understanding
James