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

Exactly! I remember reading about this.

In defense, most topics/anns are full of scam alerts (even for legitimate coins). Qtum looks promising but their ICO price seems high considering how many coins are going to be distributed.

The Dag concept was first in iota while byteball is a mix of a blockchain and a dag

there are problem with qtum...i'm not so sure that they are 100%legit.
Qtum topic is full of scam alert

"Byteballs is the first coin (besides skycoin) to be able to achieve consensus in a public network, without mining."

This is not correct. IOTA was there first.

Did you try downloading the wallet from the website?
- http://skycoin.net

Did you try downloading and running it from source?
- http://github.com/skycoin/skycoin

We have fixed many wallet bugs, but Electron still has bugs in it. Some web browsers have trouble with Angular 2.0 web apps too.

Update:

Skycoin is finally getting an order book. This took too long.
- next exchange upgrade/rewrite skycoin will float against bitcoin

The blog is going to be ready tomorrow and we will start migrating content.

We are going to announce several partnerships with large mainstream institutions, so have to cleanup a bunch of stuff and will migrate anything relevant to blog.

We will put a lot of content on the blog and things we have not revealed yet.
- information about coin distribution plans and any loose ends will go on the blog
- for the blog we are using hugo for the blog, which takes flat files in markup and generates static html files. So will work over IPFS and eventually CXO.

We are doing rewrite and improving the narrative on
- http://skycoin.net
- it will be easier for people to take a simple message away from the website about long term project goals, what is skycoin, etc
- we will test out a new, simpler narrative and see how people react. We will deemphasize the software aspects and infrastructure

We need to get the first application for the platform/ecosystem on the website.

The blockchain explorer is up at
- http://explorer.skycoin.net

We are doing the third generation skycoin wallet and completely redoing the wallet frontend and design, to start multicoin support (for Skycoin, Bitcoin, Ethereum and Qtum). The new wallet will be based upon the design of the Byteballs wallet.

We are getting more developers and focusing on improved project management process and expanding the development team further.

The CXO standard for immutable data objects and CXO daemon is almost done
- http://github.com/skycoin/cxo
- Skycoin block and transactions will eventually be stored, synchronized and exchanged over the network as CXO objects. The skycoin blockheaders and the transaction list in the Skycoin blocks will be stored as separate objects, to allow headers first download.

Congestion control on the meshnet is done. We have ~4 tickets left before will have something working. It works very well at 2 MB/s per core but needs optimization and there are still bottlenecks in the congestion control.

We have a skycoin introduction video in production now. We need to find a good narrative and message.

Development Chat:

http://skycoin.chat

We have a mattermost server now.

Byteballs and Qtum Crowdsales:

These are very interesting. Everyone should look at these

- http://byteball.org/
- https://qtum.org

Qtum, will probably replace ethereum because it is simpler and has fewer problems. The UXTO model is much cleaner. They have a lot of previous developers and have already done two previous coins and are the best team I have seen so far.

Byteballs is the first coin (besides skycoin) to be able to achieve consensus in a public network, without mining. They have gotten rid of the blockchain and replaced it with a DAG. I think the future is going to be with a variant of this approach. We have been considering this for years, for a Skycoin 2.0. I have not reviewed their code or implementation, but the concept is extremely innovative.

The new website looks great and I'm happy to hear the news on distribution to nodes.

I read and read till hours about skycoin. Any simple explaination about skycoin as im not a very well in english. Does skycoin have a forum to join any? Only about sky to discuss.

never been able to get skycoin to work and still cant, starting to think there is something not quite right here

Update:

The blockchain explorer is up
- http://explorer.skycoin.net

The next generation of the skycoin website is online
- http://skycoin.net

Several bug fixes
- race conditions in networking pool fixed
- blockchain explorer moved from node to golang backend server
- congestion control added in meshnet library
- new wallet build etc...
- CXO was completely written from scratch and is now half the size and simpler
- the CLI interface is battle tested and all the major bugs fixed. Automated deposits and withdrawals are working flawlessly now
- reenabled peer to peer exchange of peers (PEX) and several improvements, such as only relaying peers that allow incoming connections.
- skycoin now has installer on OSX and Windows. We do not have auto update or anything advanced yet

We are
- creating a skycoin blog and moving appropriate content there
- creating marketing content and a press kit
- creating our next generation infographic set, revealing more about the project. We need to communicate more clearly and with a message that audience will understand and which they will come away with and be able to transmit or communicate to others. We will have another set of messages for developers/technology focused segment.


We also made a significant mathematical breakthrough on the skycoin economy
- you already receive coin hours for holding Skycoins (holding 10 coins for 1 hour, gives you 10 coin hours). These are used to pay transaction fees right now
- we figured out how to make Skycoin and coinhours convertible into tokens exchangeable for networking services
- This means that Skycoin holders will be able to collect a bandwidth or network services reward
- We are still evaluating if we should do this and if it would making holding Skycoin more attractive.

For marketing

We are
- opening up development community
- starting chatrooms for the development community and skycoin community
- starting a systematic and sustained marketing effort (content creation, internal channels, push to external channels, press kit). This area we have put no effort in to date. This has to be ready, by the time the first applications on our platform launch.

>Any technical updates on mesh network and all those exciting topics?

Yes. We are trying to get the first application working on CXO. Which is our peer-to-peer immutable data storage/exchange standard. We will start with a simple BBS system.

The meshnet works. Except when you try to send 50 MB at once, it dies because there is no congestion control. Look in skycoin/src/mesh . You can run a skycoin meshnet daemon and command line client now.

As soon as we have congestion control implemented and working, then we will get the old VPN application working on top of the new meshnet.

After almost a year of development, our cross platform terminal/app store/application widget is almost done. This will allow us to bundle and distribute all Skycoin applications with a single executable and installer.

Right now we want to package
- skycoin daemon (and web + CLI client)
- CXO daemon (and CLI client)
- meshnet daemon (and CLI client)
- the BBS application (and web client)

Those will be the first applications.

The meshnet, we may rename "SDN" for "Software defined Networking" or just call it "Skywire". "Meshnet" will just be a specific transport module or configuration. This type of networking is more general than "Meshnet" and is something new completely. This is a new type of networking, mathematically and it is its own namespace and independent from the current internet.

The meshnet or this new type of network, requires a centralized coordinator (Which can be decentralized, using a decentralized, shared state machine, like a blockchain). Eventually we will federalize the network into "Domains" or server groups and are trying to figure out what the best way to federate the network is.

This type of networking will work very well for a few hundred or thousand server, but to go to a trillion devices, we run into the BGP problem and have to logically split the network up into smaller groups, so that each node does not have to maintain the state information for the whole network.

The test network will have a "Coordinator" service, which will be federated like XMPP, that will act as a messaging backbone, to allow nodes to message each other and do route setup and teardown. The messaging backbone will also handle payment settlement and clearing for bandwidth.

This will create a sort of "bandwidth bank" that will create demand for Skycoin tokens. Then we may have a second token that only exists on an internal ledger on the communication backbone for network coordination.

I think people will give away bandwidth for free or allocate a fixed percentage of excess capacity to free level, but in congested areas where bandwidth demand is high (such as between cities and crossings of national borders), where there is congestion, there will be speed and throughput advantage for payment to receive a lower packet queuing delay (latency) or higher throughput. We are trying to figure out the best economic incentives and how to structure the Quality of Service and economic factors. For instance, the lowest latency and highest capacity routes will naturally be "congested" and there is a natural premium that will be earned to create an incentive for more network capacity in the choke point regions. For simplicity, we are starting with a fixed cost model, but will evaluate auction models later.

We also found several trade offs in testing. A node operator to have the lowest latency path, wants to minimize his packet queuing delay by keeping 10-50% congestion rate (only utilizing less than 50% of capacity on network). While a node operator who wants to have the highest capacity route and to carry latency insensitive traffic, will queue up to two times the product of his transmission rate, times the latency to receive a packet ACK from the other end.

Example. If you can transmit one packet in 1 ms. And you have 100 packets queued up, then it will be 100 ms until the last packet in the current queue is sent. So the node wants to make sure that the rate the packets are coming in, is equal to the rate the packets are leaving. The node also wants to minimize the number of packets queued up, to minimize queuing delay.

For bulk traffic (like files or video) or latency insensitive traffic, the queuing delay becomes irrelevant and we only care about maximizing the throughput.

So the packets in/ packet out rate only has to be equal and average out over a large time horizon (1 to 30 seconds), while for real time traffic (video games and voip) the packet in/out rate needs to be balanced so that we keep the packet out rate above the packet in rate at nearly all times, to avoid queuing delay.

So for real time traffic, we want to have the transmitting, upstream node, commit to a data rate. Or the data rate over the transport, needs to change more slowly than twice the latency between when we send a packet and receive an ACK from the next node in the chain.

This works perfectly for constant rate, real time traffic but does not allow for instant burst capacity. Information about rate limits and expansion of transmission rates, propagates ~twice as slowly as data packet flow through the network. So the packet rate ramp up will be much better than UDP and the maximum rate will be discovered automatically and more quickly than TCP, but it will not be as fast as UDP.

So still researching the best way to do this. The congestion control is very important part of the network design and we are just researching it.

A node operator, who is maxing out his throughput, will incur larger latencies. While the lowest latency path operators, will want to minimize their capacity utilization.
- file download, video streaming, CDN and latency insensitive traffic will flow naturally along one type of route. Asynchronous communication
- real time traffic and VOIP or video game will flow naturally on the lowest latency route. Synchronous communications

Our congestion control algorithm, will have a single parameter for allowing the node operator to set the desired congestion level (percentage of capacity utilization and buffer size) to specialize the node for each type of traffic (lowest latency real time traffic, or throughput maximization latency insensitive bulk traffic).

We have the low level infrastructure and architecture working. We are now building the higher level coordination infrastructure.

Coin Supply Update:

Many people are confused about what the Skycoin supply is.

We added function to the blockchain info and to the blockchain explorer. It will automatically calculate the total supply, by subtracting out the locked coins.

This will make it clear what the Skycoin free float is.

We will also be adding a time lock, to make the locked coins unspendable until a certain date. We will post details to the blog when we figure out details.

ICO Update:

No matter what we do, three people end up buying all of the ICO. A few hundred people bought ~100 or 300 coins, but 2 or 3 people buy up the rest of the ICO round in 50 or 100 Bitcoin blocks.

We have decided we will distribute a portion of the Skycoin over time to people running Skycoin meshnet nodes. To promote network usage and to get users on to the network and balance out the whales.

This is probably the most fair way to distribute a lot of coins and no one will complain about it. If distribution lowers the price, we will cut back the distribution rate. We will have to determine empirically what the right amount should be.

So this will be very similar to mining and will be a good way of getting coins into the hands of the user community.

bei zhe SB keng le!

diaobaole

Any technical updates on mesh network and all those exciting topics?

From c2cx you can withdraw coins to your skycoin address (wallet).

I have installed the latest wallet with electron and it runs but nothing seems to happen, it doesn't look like it is connecting to anything. Is there anything that needs to be done once it is started?

This is very expensive at $.60 per coin. Does it have to be so expensive for such a new release coin?
How does purchasing work at C2CX. Does each purchase provide the amount of coins purchased at a single address which can then be copied into wallet or can you send them over the network to wallet? Some simple tutorial would be good to get started, some simple short video.

How can a noobie buy this coin?

german translation would be a good start. Believe me!

pm me!

There are only ~120 people on earth that know about it.

Only a fraction understand what we are trying to do and we need to improve communication. We are studying messaging and method of communicating the project to a mass audience.

The coin is almost 100% done, but we do not have any documentation explaining clearly what we have built.

The rest is in development and we are even worse at explaining that. We need more technical diagrams, story boards, sequence diagrams and we need overview of the project and then need each component explained in one or two sentence.

I am not sure there are twenty people on earth who have looked at our repos and understood what it is that we have built. They will have to see it, to understand.

Then we need working applications that people can see and use and we need to build up a userbase and community.