Show Posts
|
Pages: [1] 2 3 4 5 »
|
I understand that you are not not happy with the service. Thank you for reaching out to us. Our developers are working already on all topics you mentioned and yes, we fixed the LTC topic. As an explanation to share with everybody here: We recently changed our BTC API provider so that adjustments are needed in case of issues provided by customers. And we are working on Top10 altcoin API wallet imports to make things easier for everyone that means importing transactions automatically. For more then 200 altcoins we rely on a third party provider cryptochainz. As a semi automatic solution we offer Excel and CSV Importer for importing transactions from wallets / exchanges in bulk. A feedback loop does always help us to improve our software. And we are working on this improvement daily. Thank you for your patience, testing effort and providing feedback.
Unfortunately the LTC address import is still broken for my job. I've updated the support ticket with the new details and believe have diagnosed the likely issue for the developer. This isn't about being "happy" - this is about usability and trusting your service is accurate.
|
|
|
I recently purchased the "Unlimited" service and it has not worked anywhere near satisfactorily and remains useless to me for accurate recordkeeping. I'm happy to share my support tickets with anyone in this forum.
First, the BTC address import API failed and apparently it had to completely rewritten or new source code licensed and adapted. It was eventually fixed.
Second, the LTC address import API failed and it wouldn't properly import an address into the tool. From the support tool "This may take time to fix, we appreciate your patience and understanding.". I waited over two days without response and had to ask for an update. It is still not fixed.
These are BTC and LTC, the #1 and #6 currencies by market cap. These should be bullet proof, rock solid, at this point in the product lifecycle.
I'm posting this out of sheer frustration.
*** 11/3/19 ***
Developer fixed the LTC address import problem - testing now.
*** 11/4/19 *** So the problem is still not fixed - import is still wrong, but in a new way! I deleted the old job and created a new one with the same address.
|
|
|
@coins101 I was looking at the Helium leadership team at https://heliumchain.org/team/ and I don't see your profile as part of the leadership. What is your official capacity at Helium? I see the CCO is responsible for community so don't understand where you fit into the scheme of things (unless you're the CCO and I missed that). Perhaps you're the CMO as you're making new announcements? He is the co-founder / CTO I'm sure that's possible, but I can't establish that from any posts here at BTCTalk or anywhere. Even on the Helium site everyone on the leadership team has a "mouseover" bio but the "co-founder / CTO" so that role and background is mysterious in itself. Easy for coins101 to just re-state what you wrote.
|
|
|
@coins101 I was looking at the Helium leadership team at https://heliumchain.org/team/ and I don't see your profile as part of the leadership. What is your official capacity at Helium? I see the CCO is responsible for community so don't understand where you fit into the scheme of things (unless you're the CCO and I missed that). Perhaps you're the CMO as you're making new announcements?
|
|
|
Any active nodes? Would like to try mining this coin. getpeerinfo returns zero results
|
|
|
I am having a similar issue. My Baikal is connecting to the pools but no devices are running. Also I only see red lights on the Baikal, no blue lights. When I check with Baikal Monitor it shows this miner as 'sick'. Anyone run into this? Anyone have a fix? I had a new unit shipped that had this exact problem - red light, no blue or green lights. Because I had multiple units I was able to isolate the problem by swapping both the SD card and the OPi with a functioning unit and determined it was a defective OPi unit as both controllers and all hash boards worked. You'll need to contact Baikal to get a replacement OPi - no need to ship the unit back IF that's the problem. It's way faster to have them send you an OPi than a round trip of the entire unit. ** NOTE ** OrangePis are not covered by Baikal's warranty so you have to pay for the new units
|
|
|
Will POW return for a period of time at relaunch?
|
|
|
No exchanges now on Coinmarketcap.com - is this officially dead?
No! CCex just synced blockchain. We are waiting for wallet maintenance... C-CEX home page says this is being marked for delisting.
|
|
|
Will there be more exchanges for BoostCocin in 2018?
Definitely. Currently we are in touch with 3 exchanges. No exchanges now on Coinmarketcap.com - is this officially dead?
|
|
|
The initial difficulty on the p2pool's at bongger.com is set extremely low (at 1), raising the initial difficulty, or adding in a port with a higher difficulty would help a lot. I couldn't really hook up to the pool effectively with only 12 MH
Thanks for the tip! It's now working.
|
|
|
I've pointed an L3 at the p2pool01.bongger.com:7072 but pool side shows just a small fraction of the machine rate (50KH).
It appears the entire BGR network is about 500MH so something seems weird. What am I missing?
|
|
|
This is completely misleading - the logo for Helium Blockchain Alliance is not associated with Robert Longden's presentation (starting at 8:33) but rather the previous presenter's discussion (name unidentified). Longden's presentation is clearly about the Hyperledger Fabric and the importance of that to the construction industry. The Helium Alliance logo appears to be just a paid sponsor logo for the event which is an extremely common and acceptable business practice (along side of the Hyperledger logo). I sincerely appreciate RzeroD taking the time to document that the Helium Alliance in fact presented nothing to the industry at this event other than a sponsor logo and actually promoted the importance of Hyperledger to the construction industry.
|
|
|
Does anyone know the manufacturer of the two fans (and model numbers) on the L3+s? I've been to Bitmain's support site and tried to order replacement fans but they are not on the pick list.
UPDATE: Bitmain is not stocking the fan as a spare part so if there is a fan failure you'll have to go through warranty repair. Looks like you won't have to return the unit and they will ship out a new fan. Would still be best if we know the fan manufacturer as we know it could easily take a week to get a spare part and lose 5-14x that much in mining revenue while waiting.
|
|
|
Easy to say after the fact my man. No one knew the L3 was coming or that Inno would get it this wrong for early buyers.
OK - I'll leave it at don't ever (again) buy pre-orders. Before the fact there was a big history of problems in this industry with this practice but now I'm just belaboring the obvious...
|
|
|
How do I reflash the firmware rather than the software on the sd card?
If you have a Batch 1 or 2 miner you need to put your name on the list with Inno to have a jig sent to you. We currently have 1 jig being sent around in the US, but I understand a second jig is coming. So you should reach out to Inno ASAP to get your name on the list. I continue to be fascinated that hostages customers put up with this from Inno. Imagine you bought a new washing machine only to find the wiring was completely crap! The manufacturer's solution is send a whole new set of wiring harnesses and computer chips with instructions on how to replace them yourself. I don't think so! Every A4 owner is suffering from Stockholm Syndrome at this point. I'm really glad to see the L3 is coming (I have two running now and they are GREAT) so people will stop throwing away their hard earned money & time on this wretched A4 technology and once again re-learn, NEVER BUY PRE-ORDERS.
|
|
|
But this calculator doesn't count the increase of difficulty, and it's the crucial thing for ROI. 1y of ROI is fine, but with ASIC you find it to be more like 2+ years. This calculator does account for difficulty. http://www.vnbitcoin.org/litecoincalculator.php
|
|
|
Could just as easily be A4, just because you see 'workers' with 250-280 mh/s that doesn't prove anything. Using the Nicehash chart, they've been averaging 251Mh per miner (40728/162) for the last 1.5 hours. That's pretty close to the L3 specification of 250MH which would incline one to believe these are L3s given the A4 instability issues.
|
|
|
|