Update:
I reset the genesis block, so if you had a copy of the old blockchain and run it, you get error after updating. You have to delete the old blockchain. I forgot to mention this.
Pull repo
In "~/.skycoin" there are files
blockchain.bin <-- delete
blockchain.sigs <-- delete
blockchain.bin.bak <-- delete
blockchain.sigs.bak <-- delete
peers.txt
blacklisted_peers.txt
wallets <-- this is where your wallets are
"rm blockchain*"
Delete the blockchain related files. Then run client and you will have new genesis block.
!!! Make sure to keep the "wallets" folder. Maybe back that up first
In the future, I think different blockchains will be in different sub directories by hash, but that is not implemented yet.
I haven't been able to find the files you are specifying.
The skycoin folder on desktop contains these files - src folder, address_gen, blockchain, blocksigs, cert, libg_s_dw2-1.dll, libgmp-10.dll, and skycoin.
I can also find wallet files in .skycoin in document and settings, but the files you have mentioned I can not see anywhere.
What do you mean by "Pull repo"
Could you please specify exactly how to locate these files.
and "You have to nuke the blockchain files in .skycoin again. "rm ~/.skycoin/blockchain*"
Skycoin Can you please answer this and explain what to do.
or
can we save our wallets folder and just delete the skycoin-win folder and files that was in the zip file, and re-download them. Have they been updated?
Yes. Keep your wallets! This only affects the blockchain.
If you know your wallet seed, you will be fine. You can open up the wallets with text editor and grab the seed. As long as you have this value, your wallet can never be lost. You can also just copy and paste the wallet directory.
Eventually, I want to change the wallet deterministic generation function to SHA3/Keccak sponge function based instead of SHA256, but it is too late for this. It is best to not make major changes like this at beginning. In a year or so, there may be a major overhaul of the wallet.
There is a huge backlog of refactoring and improvements with
- wallets
- wire protocol
- networking
- block storage
- etc
Getting architecture "perfect" is a lot of work and can only be done incrementally and over months and years. We already delayed over a year for launch, so will just get this over will and make incremental improvements over time (even if the balances need to be moved to a new ledger). For Skycoin, improvements mean that the libraries are smaller, modular, simpler, more specific, have fewer edge cases and have less code. We are not adding things, but simplifying things.
The crypto library is almost perfect, but this will have another iteration of improvement too. The new library will be pure go, to allow cross compilation, wallet encryption and will have support for external key storage devices. The blockchain library is very good too and cannot be improved much. These are the two areas with security implications and where attention and testing has been exhaustive.
As you go from the crypto/blockchain, to networking and then to javascript/GUI you get more errors and more areas that need polish and can be made more elegant.
Skycoin has an onion structure
- the inner parts of the onion are almost perfect (crypto, blockchain, address/hash utilities)
- the mid layers are working but could be improved (visor, daemon, networking, blockchain storage, json API, consensus)
- the outer libraries are still being implemented (next gen DHT, skywire, merkle-dag block storage for bitorrent like block downloads in parallel, darknet application framework, communication addresses, distributed exchange)
The team for the inner layers and mid layers is done. There are a very large number of outer layer projects that rely upon the inner layers. These are independent and can be worked on by multiple teams and developers. Each project is designed to be short, limited scope, something that a single developer can get working quickly (lightning project).
The inner parts have to be exhaustively tested and cannot permit failures or error. A failure here is a lose of coins or major error (such as Ethereum integer overflow allowing you to send negative balances from your account to another person and steal their coins). This increases development effort, attention requirement and code review by 10x to 20x over normal code. These layers can only be worked on by very small group of people and require specialized skills and heavy testing (fuzzing, 100% coverage unit testing, failure analysis).
The outer layers can tolerate failure and can be developed cowboy style and duct taped back together if it falls apart. These are the easiest part to develop. The fastest and easiest.
Libraries and interfaces that are used by other applications, have to be high quality and clean, requiring about 8x the time/effort as code that is functional but not intended for reuse. The crypto library, address generation library and JSON interface are intended for use by other applications and hence development time requirement, attention and elegance requirements are higher. Where as the web-wallet is something that merely needs to work and function as intended ("throwaway code") and can tolerate cowboy development.
Then there are open ended research problems and infrastructure projects. These are things like personal blockchains, merkle-DAG, project ARA, SDR hardware, languages, compiler toolchains/environments for deterministic builds and next-generation infrastructure that gives us new capacities. Once things in this category are figured out, enough to break them into a finite scoped project, then we can push that on queue.
After the coin is launched and working 100%, it will be extremely boring. You will be able to check balances and to send coins. The coin only does two things. The functionality of a cryptocoin is underwhelming. The external functionality is simple and trivial, but the internals (the crypto, blockchain, networking) are precision components. The engineering has a similar analogy to a jet-engine or pocket watch.
There are watches that have micron machined titanium components, a minimum of components, ruby bearings, sapphire watch face, illumination by tritium. The difference from a $5 watch is only on the edge cases.
- the $5 watch stops functioning after 15 years because it has an oil bearing that drys up, while the dry ruby bearing watch keeps functioning. See:
http://en.wikipedia.org/wiki/Jewel_bearing- the $5 watch does not work in the dark, while the watch illuminated works. (the tritium is produced in the Russian fast breeder reactors that are used to produce materials for thermonuclear nuclear weapons)
- the $5 watch stops working and "freezes" after Hiroshima or Nagasaki because the EMP blast from the nuclear weapon magnetized the watch internals, while the titanium watch continues to function
- the $5 watch is machined on commodity hardware, while the titanium watch assembly required years in investment for the design of a new type of CNC machine specialized to the components and materials in the assembly
- the $5 watch cracks easily and its face scratches, while the sapphire watch face can only be scratched by diamond and can withstand pressures that will easily kill the owner
- A watch with twice as many components is more likely to break if subjected to a 50 g shock, than a simpler watch. Every component adds more surfaces for wear, more things that can break and more things that need to be replaced.
Each design choice, each material has a very specific reason. Some of the materials are extremely exotic. The owner probably does not understand the neutron irradiation process for breeding tritium, the design of the fast neutron reactor, the tritium extraction process or how radioluminescence and tritium beta decay can be used for illumination. See:
https://en.wikipedia.org/wiki/Tritium_illumination
The owner of the watch will never open it. They will never see the inside. They will never know the material it was made from. They will never see the bearings or have any idea that there is tritium in the watch or where it came from. Yet that level of engineering and the use of the best materials and engineering for each respective function is what defines luxury. Luxury is quality, purposeful design and the best in each aspect.
Faux luxury is advertising. A multitude of features, buzz words, hype, endorsement and marketing over substance. Bling and branding.
- The most accurate watch (Marine chronometers) has seven jeweled bearing. Jeweled bearings are better than normal bearings, so more becomes associated with "better" in the minds of consumers. 15 Jeweled bearing become "better" than 11 Jeweled bearings and soon there is a Jewel marketing arms race and watches are manufactured with 150 Jewels, even through 136 of them are non-functional. See:
http://en.wikipedia.org/wiki/Mechanical_watch#.27Jewel_inflation.27- watches proliferate that are full of bling and branding at the cost of quality. "Quality" becomes associated with the number of buzz words. There is a proliferation of features. Watches begin to sacrifice elegance to show you the time in three different time zones, the day of the week, the month and to remind you of your birthday. Until the watch is heavy, prone to failure and impossible to repair or understand.
- Marketers create a slew of new buzz words for products to compete on and to be thrown around. They try to create a meaningless standard metrics. In watches, the number of jeweled bearings. In CPUs, the number of megahertz, until the CPUs are so fast that frequent cache misses stalls the CPU for 30 clock cycles. In altcoins hashing functions, blocktimes and increasingly esoteric and useless contracts and features. In CMOS cameras the sensor size. The easily marketed attributes are oversold, beyond any gain in performance or quality.
- Faux luxury is taking a product that is essentially corn processed in a chemical plant and injecting it with some oil and then advertising the fact that it has 200 mg of Omega-3 in it and stamping a paid endorsement form the American Medical Association on the box.
False luxury is the belief that a $2 shirt is "worth" $120 because of a "luxury" brand on it, that advertises the price you paid. It is the belief that value of a $2 shirt is twice as much if you pay $120 for it than if you pay $60. Where as true luxury comes from the quality, design, beauty, elegance and materials and hides the brand behind the artifact.
Normally, you would take existing materials and create a best of breed design. Satoshi took visual studios, SVN, openssl, berkleyDB and the software libraries that were available at the time and cobbled together Bitcoin. You can still see the effects of these libraries, long after they have been deprecated and removed. Such as the weird endianess flips in the calculation of block hashes.
When the Skycoin project started, we took the best tools available and began there. I believed the project was going to be finite, that we would fix Bitcoin, change the hashing function and a few things and the launch. That turned into
- writing a new cryptography library
- new consensus algorithm
- new programming language (golang instead of C++)
- new deterministic wallet generation function
- new bipartite transaction graph structure instead of a multigraph
- local webwallet
- new blocksync algorithms
- new networking primitives
- etc...
Most of these things were driven by external events and became requirements for any new coin, rather than "features" . The amount of new things that need to be designed and implemented, left me feeling like an insane watch maker who was forced to invent a nuclear reactor to get tritium, just to build the perfect watch. The existing materials and libraries were everywhere insufficient. The scope of the project is becoming clear and its is very large. We are finally getting a clear perspective of everything that needs to be done.
I want to get the IPO over will and then break this up into smaller, finite projects and get more developers working on the pieces.
IPO Update:We are doing exhaustive tests and code review. There was a frustrating bug that set us back a week. 10e6 is actually 10 million in golang, not 1 million. 1 million is 1e6. This is trivial, but caused error in the coin locking system. The 100 million coins are being sent, 1 million coins to each of 100 addresses with multiparty lock system to prevent theft. There is also a time capsule lock on the private keys. The addresses are
var AddrList []string = []string{
"R6aHqKWSQfvpdo2fGSrq4F1RYXkBWR9HHJ",
"2EYM4WFHe4Dgz6kjAdUkM6Etep7ruz2ia6h",
"25aGyzypSA3T9K6rgPUv1ouR13efNPtWP5m",
"ix44h3cojvN6nqGcdpy62X7Rw6Ahnr3Thk",
"AYV8KEBEAPCg8a59cHgqHMqYHP9nVgQDyW",
"2Nu5Jv5Wp3RYGJU1EkjWFFHnebxMx1GjfkF",
"2THDupTBEo7UqB6dsVizkYUvkKq82Qn4gjf",
"tWZ11Nvor9parjg4FkwxNVcby59WVTw2iL",
"m2joQiJRZnj3jN6NsoKNxaxzUTijkdRoSR",
"8yf8PAQqU2cDj8Yzgz3LgBEyDqjvCh2xR7",
"sgB3n11ZPUYHToju6TWMpUZTUcKvQnoFMJ",
"2UYPbDBnHUEc67e7qD4eXtQQ6zfU2cyvAvk",
"wybwGC9rhm8ZssBuzpy5goXrAdE31MPdsj",
"JbM25o7kY7hqJZt3WGYu9pHZFCpA9TCR6t",
"2efrft5Lnwjtk7F1p9d7BnPd72zko2hQWNi",
"Syzmb3MiMoiNVpqFdQ38hWgffHg86D2J4e",
"2g3GUmTQooLrNHaRDhKtLU8rWLz36Beow7F",
"D3phtGr9iv6238b3zYXq6VgwrzwvfRzWZQ",
"gpqsFSuMCZmsjPc6Rtgy1FmLx424tH86My",
"2EUF3GPEUmfocnUc1w6YPtqXVCy3UZA4rAq",
"TtAaxB3qGz5zEAhhiGkBY9VPV7cekhvRYS",
"2fM5gVpi7XaiMPm4i29zddTNkmrKe6TzhVZ",
"ix3NDKgxfYYANKAb5kbmwBYXPrkAsha7uG",
"2RkPshpFFrkuaP98GprLtgHFTGvPY5e6wCK",
"Ak1qCDNudRxZVvcW6YDAdD9jpYNNStAVqm",
"2eZYSbzBKJ7QCL4kd5LSqV478rJQGb4UNkf",
"KPfqM6S96WtRLMuSy4XLfVwymVqivdcDoM",
"5B98bU1nsedGJBdRD5wLtq7Z8t8ZXio8u5",
"2iZWk5tmBynWxj2PpAFyiZzEws9qSnG3a6n",
"XUGdPaVnMh7jtzPe3zkrf9FKh5nztFnQU5",
"hSNgHgewJme8uaHrEuKubHYtYSDckD6hpf",
"2DeK765jLgnMweYrMp1NaYHfzxumfR1PaQN",
"orrAssY5V2HuQAbW9K6WktFrGieq2m23pr",
"4Ebf4PkG9QEnQTm4MVvaZvJV6Y9av3jhgb",
"7Uf5xJ3GkiEKaLxC2WmJ1t6SeekJeBdJfu",
"oz4ytDKbCqpgjW3LPc52pW2CaK2gxCcWmL",
"2ex5Z7TufQ5Z8xv5mXe53fSQRfUr35SSo7Q",
"WV2ap7ZubTxeDdmEZ1Xo7ufGMkekLWikJu",
"ckCTV4r1pNuz6j2VBRHhaJN9HsCLY7muLV",
"MXJx96ZJVSjktgeYZpVK8vn1H3xWP8ooq5",
"wyQVmno9aBJZmQ99nDSLoYWwp7YDJCWsrH",
"2cc9wKxCsFNRkoAQDAoHke3ZoyL1mSV14cj",
"29k9g3F5AYfVaa1joE1PpZjBED6hQXes8Mm",
"2XPLzz4ZLf1A9ykyTCjW5gEmVjnWa8CuatH",
"iH7DqqojTgUn2JxmY9hgFp165Nk7wKfan9",
"RJzzwUs3c9C8Y7NFYzNfFoqiUKeBhBfPki",
"2W2cGyiCRM4nwmmiGPgMuGaPGeBzEm7VZPn",
"ALJVNKYL7WGxFBSriiZuwZKWD4b7fbV1od",
"tBaeg9zE2sgmw5ZQENaPPYd6jfwpVpGTzS",
"2hdTw5Hk3rsgpZjvk8TyKcCZoRVXU5QVrUt",
"A1QU6jKq8YgTP79M8fwZNHUZc7hConFKmy",
"q9RkXoty3X1fuaypDDRUi78rWgJWYJMmpJ",
"2Xvm6is5cAPA85xnSYXDuAqiRyoXiky5RaD",
"4CW2CPJEzxhn2PS4JoSLoWGL5QQ7dL2eji",
"24EG6uTzL7DHNzcwsygYGRR1nfu5kco7AZ1",
"KghGnWw5fppTrqHSERXZf61yf7GkuQdCnV",
"2WojewRA3LbpyXTP9ANy8CZqJMgmyNm3MDr",
"2BsMfywmGV3M2CoDA112Rs7ZBkiMHfy9X11",
"kK1Q4gPyYfVVMzQtAPRzL8qXMqJ67Y7tKs",
"28J4mx8xfUtM92DbQ6i2Jmqw5J7dNivfroN",
"gQvgyG1djgtftoCVrSZmsRxr7okD4LheKw",
"3iFGBKapAWWzbiGFSr5ScbhrEPm6Esyvia",
"NFW2akQH2vu7AqkQXxFz2P5vkXTWkSqrSm",
"2MQJjLnWRp9eHh6MpCwpiUeshhtmri12mci",
"2QjRQUMyL6iodtHP9zKmxCNYZ7k3jxtk49C",
"USdfKy7B6oFNoauHWMmoCA7ND9rHqYw2Mf",
"cA49et9WtptYHf6wA1F8qqVgH3kS5jJ9vK",
"qaJT9TjcMi46sTKcgwRQU8o5Lw2Ea1gC4N",
"22pyn5RyhqtTQu4obYjuWYRNNw4i54L8xVr",
"22dkmukC6iH4FFLBmHne6modJZZQ3MC9BAT",
"z6CJZfYLvmd41GRVE8HASjRcy5hqbpHZvE",
"GEBWJ2KpRQDBTCCtvnaAJV2cYurgXS8pta",
"oS8fbEm82cprmAeineBeDkaKd7QownDZQh",
"rQpAs1LVQdphyj9ipEAuukAoj9kNpSP8cM",
"6NSJKsPxmqipGAfFFhUKbkopjrvEESTX3j",
"cuC68ycVXmD2EBzYFNYQ6akhKGrh3FGjSf",
"bw4wtYU8toepomrhWP2p8UFYfHBbvEV425",
"HvgNmDz5jD39Gwmi9VfDY1iYMhZUpZ8GKz",
"SbApuZAYquWP3Q6iD51BcMBQjuApYEkRVf",
"2Ugii5yxJgLzC59jV1vF8GK7UBZdvxwobeJ",
"21N2iJ1qnQRiJWcEqNRxXwfNp8QcmiyhtPy",
"9TC4RGs6AtFUsbcVWnSoCdoCpSfM66ALAc",
"oQzn55UWG4iMcY9bTNb27aTnRdfiGHAwbD",
"2GCdwsRpQhcf8SQcynFrMVDM26Bbj6sgv9M",
"2NRFe7REtSmaM2qAgZeG45hC8EtVGV2QjeB",
"25RGnhN7VojHUTvQBJA9nBT5y1qTQGULMzR",
"26uCBDfF8E2PJU2Dzz2ysgKwv9m4BhodTz9",
"Wkvima5cF7DDFdmJQqcdq8Syaq9DuAJJRD",
"286hSoJYxvENFSHwG51ZbmKaochLJyq4ERQ",
"FEGxF3HPoM2HCWHn82tyeh9o7vEQq5ySGE",
"h38DxNxGhWGTq9p5tJnN5r4Fwnn85Krrb6",
"2c1UU8J6Y3kL4cmQh21Tj8wkzidCiZxwdwd",
"2bJ32KuGmjmwKyAtzWdLFpXNM6t83CCPLq5",
"2fi8oLC9zfVVGnzzQtu3Y3rffS65Hiz6QHo",
"TKD93RxFr2Am44TntLiJQus4qcEwTtvEEQ",
"zMDywYdGEDtTSvWnCyc3qsYHWwj9ogws74",
"25NbotTka7TwtbXUpSCQD8RMgHKspyDubXJ",
"2ayCELBERubQWH5QxUr3cTxrYpidvUAzsSw",
"RMTCwLiYDKEAiJu5ekHL1NQ8UKHi5ozCPg",
"ejJjiCwp86ykmFr5iTJ8LxQXJ2wJPTYmkm",
}
