If you are an autodidact in English that's even better. It mean that you yourselves as your own teacher are very intelligent and very effective. The communication barrier you are experiencing has nothing to do with your language skills. It stems from the fact that you concoct a fake reality where you believe that you have some skills, discovered profitable market segments and could achieve certain business success. But people sooner or later see through your lies and you start getting ignored. That in turn makes you angry and you redouble in your lies until you are getting lost in them.

What I would suggest is to see the movie "A Beautiful Mind" http://www.imdb.com/title/tt0268978/ . It is loosely based on life of John Nash. The key takeaway for you is to see how he used his intelligence (not medications) to to cure himself from his psychological problem, to build up his mental strength to be brave enough and ask other people whether they see the people he had seen (that was in the movie, in reality he only hear voices, but that would be hard to show in a film.)

What you could do is to put your dream project on hold. Find something that would be still interesting to you and immediately useful to somebody else. "Somebody" means here both a person and an existing company that needs help in developing their own ideas. Use that to build up your own real experience and real business development skills. Your own current argumentation for your dream project could be summed up: "During a hurricane even pigs could fly."

Note to the moderators:

This thread has nothing to do with Bitcoin mining, not even the mining of altcoins. As such it should probably belong in the off-topic sub-forum. But you can leave it here if you think some reader could use the links I provided to learn something about developing and prototyping custom mining hardware.

Well, Andrew, you can congratulate your English teacher, you've fooled me (and at least one other person) into thinking that you are at least fluent English writer even if not a good English reader. I apologize I made certain incorrect assumptions about your goals, but you've provided very little information about yourself or your dream project http://rpcdram.com/ .

I believe that before anyone can help you'll need to answer a number of questions:

1) Are you a young person or are you already a mature person looking for a change in life?
2) What can you say about your educational background? How did you found yourself in a situation where the school didn't provide you with the basic knowledge in the field you have so much interest in?
3) Please read http://www.nothingisreal.com/mentifex_faq.html and describe to us why you feel that you are different from Arthur T. Murray?

I think I can feel your pain, but please help us help you.

Even the 10+ year old books will help you formulate your thoughts better. You seem to be either native English speaker or at least have long experience in English. Yet you've used the phrase "integrated dynamic memory matrix" which for me made you sound like a crackpot. Why would "idea" be a "dynamic memory device"?

Please don't immediately get offended by my use of the word crackpot. Here is a better explanation of crackpots in physics:

http://math.ucr.edu/home/baez/crackpot.html

There's no ready-made crackpot index for microelectronics and ASIC design field, you'll have to use your intelligence to apply it to yourself and your chosen field of endeavor.

Anyway your "integrated dynamic memory matrix" is called eDRAM. First result in my Google search for "FPGA eDRAM" explains why it isn't some panacea to everybody's problems:

http://www.eevblog.com/forum/microcontrollers/intelaltera-brings-fpga-to-xeon-broadwell-chip/msg896237/#msg896237

Our initial conversation was in early April. Couple of weeks later Amazon announced that their EC2 FPGA instances are generally available for rent.

https://aws.amazon.com/blogs/aws/ec2-f1-instances-with-fpgas-now-generally-available/

What's wrong with prototyping your "idea" on one of those? Why can't you use Intel Quick Path Interconeect to at least approximate eDRAM?

I already answered your further questions from the today's message of yours. If you want me to reword my advice to match your reworded question it will be: the free advice you'll get will be worth every penny you've paid for it. Now that you've mentioned a "business expert" and the need of secrecy to protect your "idea" it all begins to look very much like a version of some "long con" updated for the XXI century.

https://www.amazon.com/Big-Story-Confidence-Man/dp/0385495382

The purpose is (mostly) to save time and (possibly) wear and tear on the storage hardware.

Bitcoin Core uses extremely primitive methods for maintaining the blockchain storage: it is quite slow and needlessly, extremely, write-intensive: to write effectively about 125GB of data to disk it will actually write multiple terabytes more in the process of internal reorganizations and pointless optimizations.

Good quality SSD devices have no problem handling it, but cheap eMMC or SD-card devices can be completely worn out before the initial synchronization finishes. Flash storage is always limited by the write endurance: how many times the storage cell can be erased and rewritten.

Dude, you are so disconnected from reality that it isn't funny anymore.

Your "real conditions" consist of:

1) Not running Windows natively on the hardware as a matter of core dev team policy, but on virtualized high-end hardware.

2) Using well tested hardware, probably with ECC RAM and SSD storage.

3) Using static (or nearly static) IPv4 address that isn't shared with other users of the ISP providing cabled/fixed service.

The real users' conditions are vastly different:

1) Windows running natively, frequently on cheap computers or external drives connected with USB.

2) Untested hardware that had never run any sort of database application, only web browsers and games. Most users will try to put Bitcoin on a mechanical drive and to compound problems will run various online anti-virus and other lame security applications.

3) Outside of the USA static IPv4 are quite rare commodity, most users have either forcibly changed dynamic IPv4, shared IPv4 through CG-NAT or dual-stack-lite IPv6 deployments where only IPv6 is static and IPv4 is shared. Large fraction of Bitcoin users use various non-cabled ISPs either radio-line or cellular. Bittorrent deals with those much better than Bitcoin Core.

4) In practice the beginning users have to attempt initial synchronization several times until their resolve problems with their configuration following the usual recipe: blow away everything except wallet.dat and restart from scratch, very much in the days of MS-DOS on a PC-compatible. Downloading the data separately at least allows them to start cleanly in an reproducible configuration that allows sensible troubleshooting.

5) For many users the proper metric to optimize is not "minimum total time" but "minimum total costs". Especially those users on non-cabled ISPs have non-metered, well-performing connections only through 8 to 12 hours during night time. For them separating download (via Bittorrent or cloud file locker) and local synchronization makes obvious sense.
 
It isn't the 1% waste that is the problem. It is lack of reproducibility and lack of possibility of making sensible incremental backups and incremental synchronization amongst multiple machines.

Your paranoia is largely unfounded for two reasons:

1) even if you (or your friends stateside) don't know the providers of pre-initialized state directories, those people are frequently quite well-known outside of the USA and can be reasonably trusted.

2) most of the users desiring shortcuts to initialize don't have any coins in their wallet and don't plan on putting any just yet. They are planning on learning or demonstrating the technology.

3) the "crafted leveldb exploit to put user on a fake fork" is largely theoretical so far, whereas the practical exploits were social engineering related to fraudulent technical help with extremely fragile and problematic Bitcoin Core that has almost no internal RAS features (reliability - availability - serviceability) and laughable error messages like "there was checksum error, aborting".

Don't even get me started on using sensible storage architecture for Bitcoin Core. I tried to explain the benefits of storage layer abstraction to etotheipi in 2013:

https://bitcointalk.org/index.php?topic=144015.0

His position was that he rather have his company fail than use a database engine that is more than an educational toy. By the time they tried to switch to LightningDB he was out of money and out of patience from the prospective enterprise customers.

This is very questionable statement. They are more of "software museum curators" than "developers".

They already tried to deal with scaling and failed badly when working on the "low-end pre-configured node" using some ARM development board. The type of mistakes they made shows that their skill level is at most baccalaureate, certainly not someone who had master's degree at anything related to modern computing and information retrieval. Seriously, I've seen more knowledgeable people among high school graduates that studied and got certified for some proprietary database administration courses. I mean, if you continue to use Berkeley DB for bulk data at least read the fine manual!

If you want to do it and have fast hardware do it properly: initialize an instance isolated from the Internet syncing to a single node in a reproducible way. Trim that single node to the exact height as the most recent checkpoint in the source code for that version.

Lots of people post torrents than have few seeders because their torrents are barely useable: created with multiple restarts of the Bitcoin client, needlessly keep track of orphaned blocks, keep track of transactions in somebody's wallet, etc.

This is especially important if you're using some web-server-grade cloud hardware without ECC memory or DDR3 memory susceptible to row hammer. People then wonder why their block storage doesn't pass self verification.

Edit: Oh and one more thing: don't compress it with RAR. The RAR decompression utilities create severely fragmented files. Both Bitcoin Core client and most of Bittorrent clients at least create files in a way to avoid fragmentation.

Please don't listen to bullshit from non-technical people. Bitcoin Core does initial download faster only in certain conditions, that nowadays could be considered laboratory-like. With the real user environments (especially technical newbies or people outside USA) it is much more reliable and oftentimes faster to do this using Bittorrent or cloud file storage.

Depending on ones own level of paranoia there are two most common ways of initialization:

1) low-paranoia: download and unpack the pre-initialized "blocks" and "chainstate" directories

2) high-paranoia: download "bootstrap.dat" and do initialization and verification with local disks or LAN disk mounts

3) extreme-paranoia: do (1) or (2) and initialize new secure node totally over LAN without allowing Internet access from the secure node.

This site is buggy and undercounts the nodes. I still occasionally use it, but the numbers there are not even statistically reliable, they are skewed downwards.

Part of it is because of simple bugs (e.g. incorrect pruning of inactive nodes) or routing problems on their end.

Part of it is because of some rather strange ways it attempts to deal with Sybil attacks and cannot reliably distinguish them for legitimate address reuse (e.g. CG-NAT or certain forms of IPv6 deployment like DS-Lite).

Of course if would be beneficial. The problem is that people tend to attack those hosting Bitcoin torrents.

Try to make a post in the historical one of the historical, more popular threads:

https://bitcointalk.org/index.php?topic=1310261.0

You'll get the quickest uptake if you trim your bottstrap.dat to the exactly same height as the torrent posted there on May 30th. That torrent already has at least 10 leechers.

The torrent from the previous page, made on May 30th does work just fine. Another working torrent is from May 18th from the post that somebody deleted, but the web link still works.

http://blockchainbootstrap.com/index.html

Those are respectively 110.46 GB and 126.39 GB, unlike the torrent in the original post that was less than half of those.

 

This is bullshit. Not just garden-variety bullshit, but military-grade weaponized bullshit.

This is exactly what happens when people willfully don't read documentation as a matter of development policy.

It is exactly like the proverbial "giving people just enough rope to hang themselves".

I posted about this on the same night it happened because I was driving long distance and couldn't really stop for a full post earlier.

https://bitcointalk.org/index.php?topic=152208.0
https://bitcointalk.org/index.php?topic=152030.msg1616542#msg1616542

Those threads are interesting read for anyone wondering how Bitcoin ended up with a fragmented development community that we have now. You'll understand how the division lines were drawn and what methods of disinformation were applied. I certainly was enlightened on that very afternoon-evening-night about what was really going on amongst the leading developers and pool operators.

Another attempt at rewriting the history of the Internet.

Consensus was and is quite easy to achieve within the framework of cooperation. Internet didn't split into incompatible islands because from the start the architects intended to cooperate. To debunk comparisons between the Internet and Bitcoin it is sufficient to quote the legacy RFC 1025 "TCP and IP Bake Off":

Whereas very early shifted from cooperation to aggression and competition. I don't even really know how the fights started. i first observed it in the intensive and extensive efforts to derail any clone/alt-coins. It then shifted more intensely into internal infighting by derailing any possibility of alternative implementations or even relatively trivial and not externally visible changes like supporting alternate database engines.

Bitcoin is a fine example of "live by the sword, die by the sword".

An open-source pool that supports ASICBOOST would certainly find a niche. Both overt and covert ASICBOOST would be of interest to various groups. Just be aware that some of the interest would be negative, i.e. they would try to DDoS you off the Internet if you host it yourselves or you would receive various forms of threats and insults if you just publish the code.

AFAIK there's no open documentation on how the Bitmain's miners extended "stratum mining" protocol to support ASICBOOST, but apparently someone reverse-engineered it sufficiently enough to get it to work.

Hello Officer!

We are very sorry that our developers removed the dependence on OpenSSL and the backdoors that you've planted there. The community felt it would be better without backdoors or with backdoors that are controlled by us.

Sincerely,

/* illegible signature */

By the way: how is the coffee being served nowadays at NSA/CIA/other TLAs?

For you, personally, it would make a great difference. You would learn a great deal about computers and networking. Whether it is worth investing your time, only you can make a true answer.

1) Bitcoin-Qt's window getting black is due to the design decisions made by the Core developer's to keep the reference client tightly integrated. It is more of a cosmetic issue for vast majority of users who don't try to integrate with other financial software.

2) You computer is kinda crappy, from the vendor that is recently known to ship borderline-scam computers to meet marketing targets. Learn to make use of what you have or buy/assemble something better, even using older parts. Notwithstanding the above comment the reference Core client is quite well-optimized and serves as a decent hardware stress-test for CPU, memory, disks and their controllers.

3) Your network connection definitely seems sub-standard. Do you even have a real Internet connection or are you using some CG-NAT cheapie?

4) Avoid posting your actual IP address on this board. It is full of sharks who probably run all kinds of scans on your computer to find possible misconfiguration and steal your coins. There were all kinds of scammers offering remote help via TeamViewer (or similar tools) to rip people off.

The decision is really up to you.

Well, enjoy your HTTP bookmark.

I just wanted to provide additional, mental bookmark, for those that are still confused. It is better to not call that weird asymmetric connection with single word "delta". It is properly called "high-leg delta" or "four-wire delta". The unqualified "delta" is a three-wire, no-neutral, type of service hookup. The eventual 4th conductor is just protective grounding, explicitly prohibited from carrying any significant current under normal operating conditions. In many high-power installation the "ground" is the actual ground of the Earth, there isn't any 4th conductor.

NotFuzzyWarm mentioned the historical origin of this weird service in the USA. The legacy of it still stays in the intentional and accidental misinformation in many sources on the web and even in many lower-level textbooks and training materials.

It looks like the original poster Hockeybum had already budgeted for electrical engineer's consulting expenses. For many people (not familiar with peculiarities of the North American grid) this would be an unnecessary expense, sort of a tax on lack of knowledge of trigonometry or calculus. Rest of the world wouldn't have to concern themselves with strangeness like "split-phase", "high-leg delta" or "corner-grounded delta". It seems like sidehack had avoided this tax by intentionally opting for the safest choice of "wye"  (known as "star" throughout the rest of the world).

For the benefit of future readers who want to avoid additional EE consulting expenses I have the following advice: search for a electrician who is at least familiar with things that are outside of "the code"/NEC . The good thing to ask for is a https://en.wikipedia.org/wiki/Zigzag_transformer or https://en.wikipedia.org/wiki/Scott-T_transformer
even if you don't plan on getting one. It will probably mark you as an "educated buyer" not as somebody who is relatively easy to bamboozle with jargon to buy both belt and suspenders to match their new Bermuda shorts.

You may have difficulty obtaining/upgrading center-tapped delta service. Electric utilities don't like them because they are a source of asymmetry in the grid. Look at the transformer diagram in

https://en.wikipedia.org/wiki/High-leg_delta

from the point of view of the utility. If you pull 200A each from the low legs (SA & SC on the diagram) than means 48kW of power on the a single primary transformer winding (PA & PC) but zero power on the primary windings PA-PB and PB-PC. This is inefficient use of the capital spent on the transformer(s).

So they will push you to either:

1) use very little (about 5%-10%) power on the high-leg. They will then use two transformers, one much smaller than the other.

2a) buy equal amounts of power through each of the transformer windings. That would mean the amperage on the high-leg will be different than on the low-legs.

2b) use symmetric hookup with all leg voltages equal.

The exact rules in the USA are state-dependent and utility-tariff-dependent. Most likely they will flatly refuse upgrade if they sense that you don't understand the basic trigonometry required to balance the load. Then you will be forced to get not only certified electrician but "engineering supervision" before they agree to upgrade the asymmetric service.

It may be worthwhile (moneywise) for you to understand the equations before you talk to the utility people. Avoid burning bridges by asking stupid question when talking with them. They can legally refuse or stall your install when hooking you up would significantly unbalance their grid.

I wasn't precise enough. I didn't mean "your equipment damages building" but "building damages your equipment".

That could be fire damage, water damage, dust/residue damage, etc. You are basically repurposing heavy, dirty industry facility into something much more sensitive to the environmental factors.

I have no first hand experience with coin mining facilities, but I do have experience with more conventional temporary computing/data centers. One of our facilities caused equipment damage via horse hair getting sucked into fans and seizing them. That was because the attached building was dual use: in an emergency it was used as a livestock shelter.

Edit: in another location we had equipment failures (this time mostly temporary shorts) caused by copper wire shavings/cuttings embedded in packed dust. The facility was used for wiring harness manufacturing (cutting, crimping, soldering, shaping, shrink-wrapping).

Edit2: on the flip side of the coin: in one another facility the hot-running computer equipment (no air-conditioning) was instrumental in fixing the water/mold damage to the premises.

In general I think you have a good opportunity on your hands. Just research some pitfalls of "brownfield" location before you actually move in. Good luck.

Don't give to much value to what is shown by https://bitnodes.21.co , that site isn't very reliable. For two reasons:

1) it is quite buggy
2) it was subject to various attacks and attempt to skew statistics, therefore it employs various strange algorithms to defend itself and other servers on their ISP

I have very reliable connection and frequently get less than 50% availability score on that site. It isn't completely useless, but it isn't even statistically correct.