Topic: [SKY] Skycoin Launch Announcement - page 104. (Read 381579 times)

It seems to be working better than it was a few weeks ago; back then no connection attempts succeded, but now there seems to be some network activity.

Done, sent the IP in a PM.

Update:

Can someone pull and run some servers.

Open ports 5999 and 6000 (preferably VPN server) for UDP/TCP

Then run
git pull
go run ./cmd/skycoin/skycoin.go

It should work now. Except all of the servers in network are behind firewalls, VPN and cannot get incoming connections.

Update:

Unit tests work for networking. It works locally. It works with multiple clients on the internal virtual private network for testing. It is 100% working. However, on public internet cannot connect to anything and there are strange errors. The peers/connection list is empty.

[skycoin.daemon:DEBUG] Removing 89.110.41.155:23547 because failed to connect: dial tcp 89.110.41.155:23547: i/o timeout
[skycoin.daemon:DEBUG] Removing 122.31.215.119:9721 because failed to connect: dial tcp 122.31.215.119:9721: no route to host
[skycoin.daemon:INFO] Removing 124.11.192.188:10167 for not sending a version
[gnet:DEBUG] Failed to read from 124.11.192.188:10167: read tcp 124.11.192.188:10167: use of closed network connection
[skycoin.daemon:INFO] 124.11.192.188:10167 disconnected because: Version timeout
[skycoin.daemon:DEBUG] Sending introduction message to 111.250.149.229:23790
[gnet:DEBUG] Failed to read from 111.250.149.229:23790: EOF
[skycoin.daemon:INFO] 111.250.149.229:23790 disconnected because: Read failed

to see list of connections do:
http://skycoin-chompyz.c9.io/api/network/connections
http://127.0.0.1:6420/api/network/connections

We are getting
- "no route to host"
- "i/o timeout"
- connection opens and version (first packet) is never sent
- EOF when trying to read from socket

Line 424, func (self *ConnectionPool) connectionReadLoop(conn *Connection) {

That is the read loop
https://github.com/skycoin/gnet/blob/master/pool.go

TCP/ip has bizarre error conditions. It is also forced in golang. We have
- a listening go routine for each pool of sockets
- a go routine for accepting new connections
- two go routines per socket. a goroutine for reading from socket and a goroutine for sending over socket, with queues for messages
- a goroutine for checking the messages and processing them, that came from the goroutines

We have a full refactor and rewrite of daemon and networking, but cant use it because of other major refactoring, which is a bit exhausting. There is no way to do the refactor incrementally without introducing circular imports, which prevents compilation. I think I want to deprecate TCP/ip completely because it is too frustrating.

Also, we have other issues
- running skycoin is disconnecting some people's VPN
- skycoin appears to disconnecting some people's wifi connections

Skycoin is using the Bitorrent kadmelia DHT, so it might be mistaken for a bitorrent client and could be seeing some type of purposeful disruption. I have no idea why the client appears to work on local host and on the internal VPN for testing, but does not work on the public internet.

Skycoin is using DHT with UDP on port 5798 for Bitorrent DHT and listening with TCP on port 5798 for incoming connections. It is possible that this condition causes crashes or confusing behavior on some operating systems, virtual private network implementations and may crash some poorly implemented routers.

This may be some weird NAT traversal and VPN problem.

I will try to fix the port number, to something else and hardcode it, then see if it works.

I can't download from there either. I just want to generate a skycoin address for the IPO, is there another way that's easier?
thanks

Update:

This is security vulnerability in 2-factor auth for coin base

http://qntra.net/2015/03/security-as-a-coffin/

More OpenSSL problems. This is why we are not using OpenSSL.

"A vulnerability existed in previous versions of OpenSSL related to the
processing of base64 encoded data. Any code path that reads base64 data from an
untrusted source could be affected (such as the PEM processing routines).
Maliciously crafted base 64 data could trigger a segmenation fault or memory
corruption."

"Reusing a structure in ASN.1 parsing may allow an attacker to cause
memory corruption via an invalid write. Such reuse is and has been
strongly discouraged and is believed to be rare."

"A malicious client can trigger an OPENSSL_assert (i.e., an abort) in
servers that both support SSLv2 and enable export cipher suites by sending
a specially crafted SSLv2 CLIENT-MASTER-KEY message."

http://qntra.net/2015/03/march-19th-openssl-vulnerabilities-overview/

There is a heart bleed bug every six months. I am very worried about the fact that Bitcoin is still using OpenSSL.

IPO Update:

The network is running. Transactions are working. However, connecting to other clients and block replication appears to be experiencing problems.

There appears to be an issue with servers connecting peer to peer. Something may have broken in the refactor. There is an EOF error on socket read and not sure what cause is and have to check that the keep alive packet for connections is working. Clients from another application may be connecting because of the kadmelia DHT requests, but not sure.

The developer who wrote this part of the code has been traveling on vacation for a few months and different person refactored it and I have no idea where the unit testing suite for networking went (but we had tool for this before refactor, but cannot find it). So will just do it by hand with printf. There may not even be problem and it may be that http://127.0.0.1:6420/api/network/connections is broken.

As soon as the existing networking is fixed, then another refactor begins to replace it with skywire and move rest to functions out of /src/daemon into other modules.

Getting the coin to "perfect" will take years. The crypto and blockchain are almost in a perfect state right now. The rest could use refactoring, cleanup and simplification. However that can be done over years and should not be rushed. The priority is to get core coin checked off and then move onto more important libraries (like skywire). There are still a few thousand lines of code that can be refactored out and simplification.

I think we fixed too many of the bugs before launching. We should have done it cowboy style.

Someone has also reported that using Skycoin behind a VPN breaks the VPN connection. I have no idea. I am not experiencing that issue.

Here, this is web-wallet and client, exposed publicly
http://skycoin-chompyz.c9.io/
http://skycoin-chompyz.c9.io/api/network/connections

This list should not be empty. There should be three or four servers it connects to, but we are not seeing them and its not clear why its not connecting to network.

What is the regulatory aspect of such mesh network that is described in the above post? Wouldn't be illegal to operate such communication network in most developed countries?

Links:


IPFS Demo:

This is IPFS. This is the successor to Bitorrent.

https://www.youtube.com/watch?v=8CMxDNuuAiQ

Skycoin Merkle-dag system is based upon this.
- A directory is a list of nodes. The id of the node is the hash of its serialization
- Each node is either a folder or a file.
- The contents of files are hashes
- The owner signs the root hash with their private key
- The node metadata and files are replicated peer-to-peer
- the directory is referenced by a

Users can update the files after they upload them. If you have a javascript file, instead of rerequesting the file from the server, everytime the page is loaded, the file is named by its hash. If the hash is in the local cache, it does not need to redownload it.

This will speed up blockchain downloads, but has other applications. The Skycoin version is
- a stripped down version of IPFS using skycoin cryptography primitives
- runs over Skywire

Cuba Meshnet:

This is a good article on the Cuba meshnet

http://www.detroitnews.com/story/business/2015/01/26/cuban-youth-computer-network/22367037/

This article shows several things
- it is pathetic that people in most parts of the world need to beg their governments for permission to have internet
- government regulation is designed to control and enslave people, not for their benefit. The meshnet cannot be connected to the real internet, because it would compete with the government telecom monopoly
- if people in the middle of the network can see the traffic and protocols you are running, they will be compelled to block pornography or other arbitrary content. They are forced by terror into erecting an NSA police state, even on a network of 9000 nodes, to keep the government from putting them in a black van and disappearing them.
- the state monopoly and control of communications is the primary way that oppressive dictatorships remain in power.
- oppressive governments are funded by resource and service monopolies. The Cuban government anti-freedom thugs are funded by raping citizens with an oppressive telecom monopoly. The corrupt Brazilian government is funded by the state oil company and by state electricity and distribution monopolies. The Venezuelan government is funded by state oil monopolies. Governments put in place monopolies, rape citizens with high costs and then use the money to high thugs to stay in power.
- It is absolutely pathetic, how citizens have to beg and pleat like slaves begging to their masters, for even the scraps of freedom they have. People should not live under terror and total domination by the state. This is slavery.

Meshnet Hardware: 1 Gb/second over IR laser over 100 meter range

This is one of the second generation RONJA projects.



"KORUZA system enables 1Gbps networking connectivity for locations up to 100m apart, by using an eye-safe infrared light beam. It is an open-source open-hardware ultrafast networking technology, innovating use of free-space optical networks. Mass produced electro-optical modules are combined with 3D printing technology to simplify the design and create a system significantly more affordable then current solutions."

https://dev.wlan-si.net/wiki/KORUZAbut
https://dev.wlan-si.net/wiki/KORUZA/Prototype

The hardware for gigabit freespace communication, multi gigabit wifi, SDR and other technologies for meshnet are in development and will be commodity within a few years. We are are dropping all direct involvement in the hardware side and focusing only on the software and encryption side now.

The collective progress that has been made in the open source community on the hardware side of the meshnet in the last six months is just incredible.

I cannot connect to download this. Was this the latest windows executable?

Great update again, thanks for that!

Can I generate an address from Windows?

https://bitcointalksearch.org/topic/m.10555070

I have been following for a while (almost 1.5 years) and I haven't got time to sift throught the thread everyday. Skycoin, could you update the heading and op of this thread please. Also, has the IPO started? I haven't been able to determine it.

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",
}

Consensus Paper: http://arxiv.org/abs/1501.06238
Github: https://github.com/skycoin

Hi, I want learn skycoin's consensus, where is the source code?

Any exchanges?

still waiting for this.

I have done this and I cant find anything in the skycoin folder specified. There is only the wallet files. There is no blockchain folders or files.

When you run the skycoin client, you can see the following output in the console


If you are in Linux/OS X, then {YOU_SKYCOIN_DIR} should be "~/.skycoin",
if you are in windows, then {YOU_SKYCOIN_DIR} should be some other directory like "C:\Users\{YOUR_USER_NAME}\.skycoin" if you are using windows 7 with english locale.

Open the {YOU_SKYCOIN_DIR} directory with your file manager, and delete all files with name beginning with "blockchain".