|
Offer hereby over. I figured out what I needed.
Thanks for the inputs!
|
|
|
|
What feature?
Answered via PM. |
|
|
|
Congratulations to KnC for their successful tape-out!
Let's not compare a non-existent 20nm chip to HashFast's current 28nm chip, which is by far the fastest Bitcoin mining ASIC ever created.
I feel like you don't get it. There is nothing wrong with HashFast's technology. I have a BabyJet running right now - it works just fine. The problem is with your utter disregard for your customers. If you actually SHIPPED the stuff you make, live would be glorious. But this is a two way street. You get money - you ship something - we say HashFast is a-ok: then you get more money... see how easy that is? But let's ignore all previous customers for a second (you've beaten me there). Just tell us why you think you can ship THIS one on time. Do you actually have wafers in hand? Substrates in hand? PCB's in hand? |
|
|
|
Sorry about that. It was late at night, I was tired and should have gone to bed hours earlier, and I was also in the process of responding to some trolls and clueless newbies so my frame of mind was a bit sarcastic and overly critical. I over-reacted to your post and probably should have just logged out and gone to bed.
Hats of to you for that classy response - wish there were more people like you on here. I wish you luck in your search for a teacher. Hopefully your money will be well spent.
I'd think you'd get faster answers to the things your are trying to understand if you just create a self-moderated thread and delete the troll and flame posts. I've found that there are several knowledgeable people here that are generally eager to share their knowledge on their own time in the written format (where they can take the time to organize thoughts, link code, and review statements before posting), but my guess is that its going to be much more difficult to find someone willing to commit to an hour in an interactive conversation.
Thanks. I wonder if I should just hire someone to implement the feature for me. What is a good going rate on here? My guess would be that someone intimately familiar with the code can do it in a day. For someone not that familiar, but who have created a coin before, maybe 3. New on the code, maybe a week to 10 days. |
|
|
|
I've been goading Hashfast_CL on his new 800-ish thread and he just left all of my replies there. Until this one... Does anybody else thing HashFast has caught themselves up into a pyramid?
They don't have enough money to pay for more silicone to fulfill the Batch 2+ orders, so now they're selling another vaporware product to pay for the initial production run.
That is really the only reason I can think of that they're so quite about their intentions for their first products. There's not even promised delivery dates anymore, just silence. Interesting that he chose to delete this specific one. Did I maybe hit too close to home? |
|
|
|
As grau is pointing out, you're "proof of funds" would be more believable if you had actually signed a statement using the private key from the address in question.
As a programmer with 20 years experience, and a passing interest in the source code of the Bitcoin-Qt wallet, it is quite surprising that you didn't realize this.
I just added it in a rush at the end, since last time I had an offer out, a bunch of people questioned whether I had funds. Though (I think) it's a reasonable per-hour fee, it's in actuality such a small amount of actual money, that I didn't think something more formal would be required. But here goes - signing message for 1BoW3MiwtnDOemFmXij0Jw5tCyrD43QpUn: Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life.H9WV6H28c1YcinIsQQuf7YdOnbaFq6wMSe2Z9WbcPCMs85ZN6cAv4w19U4J0IMJhy7fPHujzGGnuutJ+IF3DNII= It certainly doesn't fill me with confidence that the hour will be well spent.
That would be my problem now, wouldn't it?
If you really want to convince people that their time won't be wasted, it might be worthwhile to place the bitcoins in escrow with a trusted member of the bitcointalk community.
I'll arranged what's needed with the individual person. If the person has a sufficiently established reputation already, I'll probably just pay upfront. Honestly though, if you just ask any questions here you'll get the benefit of extensive knowledge from multiple "experts" without having to pay a penny.
Additionally, many others will be able to refer to the discussions and learn as well. Drastically increasing the productivity of the conversations.
There isn't going to be a question that I'm going to ask that's not immediately being met with "Don't you know how to use google, you idiot", or "Go read the source code, twit" (paraphrasing), or my personal favorite "Stop doing what you're doing immediate, and go do some research"... yeah I was busy doing research, hence the question. I am indeed finding the information piecemeal, it's just taking longer that I would like. |
|
|
|
I'm busy learning the Bitcoin wallet code, and have a bunch of questions. Searching online and through forums is taking forever, and I don't want to continue spending days for what I'm sure I can learn in an hour of dedicated time by an expert. If you consider yourself an expert in the Bitcoin wallet source code, and can talk with ease on areas of: * Transaction management
* Database interaction
* Key storageand have good conversational English, I have an offer for you: I offer BTC 0.2 or $125 via Paypal (your choice) to have a Skype chat for 1 hour on the above subjects. Either voice chat or messaging is fine. I have a 20 years C / C++ background, so if you're trying to B/S me, I'll know and you won't get the full award. And don't worry, I'm not creating another coin. PM me your background information and point to things you've worked on (e.g. other coins), and I'll select the best candidate. Proof of funds: https://blockchain.info/address/1BoW3MiwtnDOemFmXij0Jw5tCyrD43QpUn |
|
|
|
|
If you're creating another coin, please consider making it a (good) SHA-256 coin.
The new SHA-256 altcoins have the potential to take away a significant amount of hashing power from BitCoin. This is a good thing for all miners, as well as for the planet.
Maybe someone can come up with a 'RecycleCoin'?
|
|
|
|
|
Does anybody have BitmainTech's contact details? They've removed it from their web site.
They just expired a paid order of mine as unpaid, even though I paid and the transaction had dozens of confirmations at the time they expired it.
I know they keep re-using their payment addresses, so I don't want it to go to the next person before they acknowledge the payment from me!
This is the first time BitmainTech has given me any problems - I've placed many orders before and had nothing but great service.
|
|
|
|
|
Wait - is this coin starting April 3rd, or March 4th?
|
|
|
|
To begin this, I'm a 59 year old dad of 4 wonderful children(3 boys 1 daughter). <snip>
In December of 2013, I exchanged most of my 401k(My retirement fund) as well as most of my savings, into Bitcoin. That was over $400,000 or around 600 Bitcoin at the time. I believed Bitcoin was the future of all currencies and was set to replace the U.S Dollar following it's inevitable crash.<snip>
No, you didn't. I get it you're trying to use the 1st person narrative to get your point across - most likely in the hopes the media picks this up. But it's not going to happen. See, Mt. Gox wasn't an exchange. It hasn't been for half a year. You couldn't exchange one thing for the other, and actually get hold of the other thing. It was merely a timing-based speculation tool. And it has been for many many months. By "suspending" the ability to withdraw USD, and not doing an arbitrage against other exchanges, they created a floating rate that was a pure flight of fantasy, held up by the people who speculated on the other side. So having money in there meant that you were doing extremely high-risk speculation, tantamount to stock options. Everybody on that exchange knew they ran the risk that Mt. Gox could have opened up USD withdrawal again at any moment, which would have caused an instant arbitrage across the Mt. Gox exchange, and a guaranteed 30% collapse. Yet, people still did it - and fair enough some made money that way, as you could do with stock options. However, nobody at the age of 59 would have put all their life savings into a position that was that risky in the first place. Didn't happen. |
|
|
|
While the supply is scarce, definitely. But now ASIC farms are mining this and supply will be much much higher.
Supply is constant. The number of miners on a particular coin has nothing to do with a coins' supply, it just affects who gets it. Even if mining drops (over time) to 2 guys in a basement mining with a Z80, they'd still be mining the same number of coins. |
|
|
|
|
So if I was a crook, it would be the easiest thing to go release a script on the web, open source it, have it scrutinized the world over, gain some trust and then ship out a Ubuntu CD with the same script on it - except this time I'll modify the Ubuntu loader that instead of loading and running that script, it would execute a piece of private code that I stick inside the loader.
But I'm not a crook. Maybe you aren't either. But someone is. How do people tell the difference?
|
|
|
|
|
Cool!
I can buy a CD that will return one of a million private keys that you have carefully selected and stored away for yourself?
Wouldn't it be easier if I just GIVE you all my BitCoin?
|
|
|
|
They've been "holding onto" 51 of my btc since last September and consistently lying about when I'd receive my product(originally supposed to be November).
They've been lying to you??? Drool!  I WISH they would lie to me. They just absolutely ignore most of us. At least when they're lying to you, you know that there is still somebody alive on the other side that you can go after. |
|
|
|
Why does hashfast keep ignoring the Overdue Upgrade modules and MPP replys?
I'm starting to get the feeling that there was a design flaw and a re-spin was required. It very well could be that the units that have shipped are the first run engineering samples. It would certainly explain why they're hardly stable. No, I have a BabyJet and it is 100% stable and works great. There's nothing wrong with their technology, they just REALLY hate their customers. |
|
|
|
|
Have you tried using pywallet to dump the private key?
Alternatively, upload your wallet.dat to blockchain.info.
|
|
|
|
Thank you for finding the upnp issue!  I have checked in a fix for the batch file. When I was first working on the miniupnp code to create a suitable project file, I forgot that I had copied the .in to a .h to get it all to build and work. My batch file doesn't put any meaningful information into those two strings but I don't think that will cause a problem. If it does, however, I can just create my own version of the .h file and copy it over to use for the miniupnp build. As far as your Qt64 build issue, it sounds like an issue with dynamic vs static libs. The statement in the batch file that calls perl to change the build options from dynamic to static in the qmake.conf file must run correctly. If you are using a different version of VS, like 2010, then the batch file needs to modify a qmake.conf file in a different directory (as well as other changes) Also, if you start building and anything goes wrong, don't start over unless you have a clean copy of the qt distribution. It's pretty picky. I hope this helps. Thanks for trying all this out--I really appreciate it! By the way, I have never used mingw on this machine--a Win 8 64 bit. I did install mingw and built the bitcoin daemon only on another Windows system and that experience convinced me that something needed to change  I am running on VS 2012 Ultimate, so that shouldn't be the problem. I finally gave up and downloaded the Qt from Digia that was already built. I also found a problem with buildboost.bat though. The bjam for x64 part works correctly, but the bjam for x86 is missing: --toolset=msvc-11.0 With the result is it builds for the 12.0 toolset, and thus you can't link on x86 due to missing libs. Adding --toolset=msvc-11.0 solves it. |
|
|
|
One more thing - the buildminiupnpc.bat script does not correctly build miniupnp. There is no header from 'miniupnpcstrings.h', it's built if you run updateminiupnpcstrings.sh, which the build script doesn't do. Of course you can't just run a .sh in conhost, but if you run it under MinGW it gives a:
/* $Id: miniupnpcstrings.h.in,v 1.5 2012/10/16 16:48:26 nanard Exp $ */
/* Project: miniupnp
* http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/
* Author: Thomas Bernard
* Copyright (c) 2005-2011 Thomas Bernard
* This software is subjects to the conditions detailed
* in the LICENCE file provided within this distribution */
#ifndef MINIUPNPCSTRINGS_H_INCLUDED
#define MINIUPNPCSTRINGS_H_INCLUDED
#define OS_STRING "MINGW32_NT-6.2/1.0.18(0.48/3/2)"
#define MINIUPNPC_VERSION_STRING "1.8"
#endif
It would be useful to however build this file from your build script as well. You probably have an old one lying around in your directory created by MinGW which may be why it builds for you. |
|
|
|
|
I have a bunch of link errors trying to build a 64-bit version of QT.
Qt5Core.lib(qstring.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MT_StaticRelease' in main.obj
Qt5Core.lib(qlist.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MT_StaticRelease' in main.obj
Qt5Core.lib(qarraydata.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MT_StaticRelease' in main.obj
Qt5Core.lib(qiodevice.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MT_StaticRelease' in main.obj
Qt5Core.lib(qcoreapplication.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MT_StaticRelease' in main.obj
Qt5Core.lib(qfiledevice.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MT_StaticRelease'
...
MSVCRT.lib(MSVCR110.dll) : error LNK2005: free already defined in LIBCMT.lib(free.obj)
MSVCRT.lib(MSVCR110.dll) : error LNK2005: malloc already defined in LIBCMT.lib(malloc.obj)
MSVCRT.lib(MSVCR110.dll) : error LNK2005: realloc already defined in LIBCMT.lib(realloc.obj)
MSVCRT.lib(MSVCR110.dll) : error LNK2005: memmove already defined in LIBCMT.lib(memcpy.obj)
MSVCRT.lib(MSVCR110.dll) : error LNK2005: memchr already defined in LIBCMT.lib(memchr.obj)
MSVCRT.lib(MSVCR110.dll) : error LNK2005: _ftelli64 already defined in LIBCMT.lib(ftelli64.obj)
MSVCRT.lib(MSVCR110.dll) : error LNK2005: _lseeki64 already defined in LIBCMT.lib(lseeki64.obj)
MSVCRT.lib(MSVCR110.dll) : error LNK2005: strcpy_s already defined in LIBCMT.lib(strcpy_s.obj)
Any idea how to resolve it?
|
|
|
|
|
Show Posts
