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

Update:

90 commits.
- The Command Line Interface is done.
- The first version of the WebRPC interface is in the repo!



Almost done with check box for floating on exchange.

Now have to fix the remaining wallet bugs.

Update:

Development:

The CLI in next push will have
- adding private key to wallet by private key hex
- transactions for spending outputs held by a single address by private key
- working send

The wallet gui will be fixed in dev head, within the next few days.

Update:

We need to fix the GUI on the dev branch.

We need to debug the CLI (command line interface, for exchange))

We need to get the WebRPC (for exchanges)

We need to start building out the community.
- need a chat room
- need a forum or BBS
- need a messaging system

We need to get the three white papers done and the website
- Coin / Consensus Paper
- Meshnet Paper
- Aether Paper

We have to decide if we will float and do the first market internally or use a third party.

We have to get the roadmap up on the website.

We have to create the third version of the website.

We have to get a windows installer (to install under program menu)

We need to do ansible and docker, build/installation automation scripts.

Skycoin Website:

The website is a flat file. No-script (no javascript).

This was first version of website (which was complete shit). It was actually very bad.



Second version is much better.



In the third version
- will be stripped down (fewer text, fewer icons, nothing that is not needed)
- will be focused on directing the user to the wallet download or to the roadmap and infographics
- links to wallet download, white paper, github, roadmap (infographics)
- remain very focused on why user is at website and what they are trying to do. With very little text/icons to distract them

Aether: Skyhash

This is the new internet

The first version of Skyhash/Aether is done
- https://www.youtube.com/watch?v=fXD_rdwoKsc
- https://github.com/gagliardetto/skyhash-pub-sub
- github.com/skycoin/skyhash

- A person takes their public key and publishes content
- The content is replicated peer-to-peer to all subscribers to the public key

There are no servers. It is completely peer-to-peer.

This can be used for
- static websites (shops)
- IoT pub-sub channel
- DNS (looking up public keys, by human readable identifiers)
- caching static content
- blogs
- twitter
- image boards
- building TOX like communication system
- server orchestration
- replacing Bitorrent/IPFS

We trying to get a developer to work on the content browser for Aether.

Instead of going 120 hops in the network, to get data. It will just get the data from whoever is near you that has copies.
- in the current internet, if a content publishers server is in Los Angeles and the requester is in Hong Kong, ever content request and packet will go from Hong Kong to Los Angeles, for each request.
- in Aether, the first copy of the data goes from Hong Kong to Los Angeles, and each subsequent copy can be served from a local content cache or another user

This is also called "Content Addressable Storage" or "Source Independent Networking".

For instance, a file is requested by the SHA256 hash of the data contained in the file. You do not care where the file is downloaded from, as you can verify the contents of the file once it has been received from any source.

If you are using 100 MB/s over 100 hops of fiber (going through 100 routers). You are using 20x the network resource usage, as if you are going through only 5 hops
- resource usage is number of hops times bandwidth usage per hop

So by pushing content to the edge, the aggregate network resource usage is reduced and latency is reduced.

This also enables Multi-cast and enables a higher level of network redundancy (automatic geographically distributed content mirroring).

The next generation HTML, websites, services, social media and video streaming will be built on this principal. The existing model of a CDN is an intermediate stage of the evolution of this type of "EdgeNet". The military, commercial and home IoT and the next generation of "cloud" services will largely be enabled by networking protocols designed on these principals.

We have our object format and serialization format defined and are starting to integrate it into Aether.

We are building the skycoin consensus and block distribution on top of this model, because of the security and speed advantages. It also has the advantage of being a simple three packet protocol.

Aether: Tox-like messaging

Aether at the basic level, enables cryptographic, peer to peer replication pub-sub channels.

We can take two public keys
- have pubkey A subscribe to pubkey B's pubsub channel
- have pubkey B subscribe to pubkey A's pubsub channel

- A publishes a message to B
- the message is replicated peer-to-peer to all subscribers to pubkey A
- B receives the messages
- B publishes an ACK into their message stream, confirming that they have received the message from A

So we now have a two way channel
- can be used like Bitmessage
- can implement Tox like messaging
- can implement a cryptographic ratchet
- can implement asynchronous messaging (for configuring servers, SSH, process monitoring, status monitoring, etc)

The implementation is completely in golang, so no buffer overflows.

The messages are stored, by everyone replicating the public key
- so if a server is offline when the message is published, when the server comes back online, it will receive the message
- if the server is online, it will receive the message instantly and will see response

This is a very powerful messaging primitive. Especially when you have mobile devices or an unreliable network that is going on and off. This type of network can deliver messages, even over latencies of minutes, hours or months. It is
- source independent
- asynchronous
- scale invariance in time

For instance,
- you can put a node on a ship sailing between japan and new zealand
- when the node on the ship is near japan, it will drop off new messages and get new messages for any pubkeys the node is subscribed to.
- then when it sails to New Zealand, it will drop off the messages and grab the latest messages
- it will still operate automatically, to distribute blogs and tweets, even if the internet cables are cut and the satellites have been shotdown and it takes two months to send a message back and forth. Only a single copy of a blog posts or static data needs to enter the country, to be replicated peer-to-peer.

The latency can literally be days or months and the protocol still operates reliably (scale invariance in time).

Also, all applications built upon the distributed object store, will operate automatically offline with no additional coding
- Google maps works while you have internet
- when you lose internet, you no longer have a working map
- when a map application is run off of map data in the asynchronous, distributed object store there is no difference to the application between being online and offline. You can cache the map for a whole country locally and it will operate the same regardless of internet connectivity.

I think this will find a lot of applications for drones (drone swarms, mobile communication nodes), satellites, mobile devices (cell phone applications), IoT or mobile networking.

Meshnet

The data channel and control channel is separated now. We have three things left to do, before its working again. It could be one or two weeks, before the full stack is working end-to-end.

I think we will have someone get the VPN application working again, so that we will have at least one useful application to run over the network.

The long term goal of Aether is to create content and website that are internal to the network only.

Aether will look exactly like IPFS
- there will be a content browser
- you will put in a public key, then slashes, to navigate to content example: ipfs://QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/readme
- then it will find peers and fetch the content

Roadmap:

Our application stack is
Skycoin + Skywire (Meshnet) + Aether (Skyhash) + CX (application language)

We almost have the coin completed. Then Skywire and Aether in development/demo state.

Do we have any small exchanges, that want to QA the command line interface and web-RPC? I think twelve of them messaged us but do not remember the names.

We could enable shape-shift type functionality in the wallet. We are ready to do that now.

You may have a weird keyboard. Japanese keyboard or Windows 10 bug? Sometimes electron (embedded chrome) can have problems with language localization and might do unicode characters and then we only use ASCII internally. I have not tried to put in a unicode wallet seed, to see what it does.

I put in "123456" for seed and checked the wallet and seed said "123456" in wallet file. Another developer on OSX tried and could not replicate problem.



- the seed can generate an infinite number of private keys, public keys and addresses
- there is one private key per address

The password feature is "wallet encryption". We are still implementing wallet encryption. Wallet encryption will encrypt your private keys and the seed, so that if the wallet file is stolen, no one can spend your coins, without knowing the password. We are using sha256 + secp256k1hash (very slow on ASIC, GPU, CPU 1000x attempts per second max) for password derivation function and then ChaCha20.

---

We added a lot of new features to the wallet and have not had time to QA everything.
- we now have a version number, so we can automatically upgrade old wallets to newer wallet formats
- we now have a "last seed" value, so that we can generate an infinite rolling series of addresses quickly
- the software now supports multiple addresses and adding new addresses to the wallet
- we are moving the seed and private key values into their own area, so we can encrypt them for wallet encryption

These upgrades and changes to software broke the GUI and we are cleaning that up now.

Ok. This is annoying thing, that golang forces you to do. The skycoin folder must be in the gopath ($GOPATH)

- You can do "go get github.com/skycoin/skycoin" and go will automatically install skycoin to the go path
- then do cd $GOPATH/src/ to look around your gopath and see what is in there
- symlink the $GOPATH/src/github.com/skycoin/skycoin folder, to a folder in your home directory or development directory, for easy access
- ln -s $GOPATH/src/github.com/skycoin/skycoin $HOME/skycoin

Then it will work

We are creating
- ansible scripts
- docker scripts
- dev ops scripts for automatic setup, verifying configuration, asking user where they want the files to go etc
- scripts for automating build and containerized deterministic builds
 
In theory, three things need to happen
- Golang must be installed and must work
- The skycoin directory must be in the gopath
- The golang libraries in the GLOCKFILE, must be in the gopath

Then it will work perfectly 100% of the time. So we need to automate doing those three things.

Update:

Someone try
- run a skycoin node with go run ./cmd/skycoin/skycoin.go
- go run ./cmd/cli/skycoin.go

This is the command line interface.
- do `go run ./cmd/cli/skycoin.go help GenerateWallet`
- etc

You should be able to
- generate wallets
- generate addresses
- check balances
- create transactions
- inject transactions into the network
- track transaction status

This is new code and still being heavily tested/modified. I would not use the 12 word wallet phrase feature yet.

We wrote too much code and added too many features at the same time. I was not watching them and they went wild, without polishing enough and we need to polish the existing things first.

We will expose the same functions over WebRPC and we are 100% done for exchange listing.
- Then we need to find a small exchange who wants to do QA and testing. Then will list and test there.

The marketing people want to
- have white papers up (the three papers)
- have website done with infographics
- do marketing for one month
- then do listing on the first large exchanges
- then add large exchanges over time (not all the exchanges at once)

We can sell a few coins over private messaging or bitmessage, until the exchange is up.
- either private message on Bitcoin Talks
- Or Bitmessage BM-2cU8XJp3GPVQG75ZwMjiyzdDEa9eD4B7iM

- Send your skycoin address and how many coins you want to buy
- we will send you back a Bitcoin address and put you in the ledger
- Then we will send out coins when we get the invoice notification

For reserving coins, it is same process. As long as it is in ledger will be fine.

---


We have to get the market up ASAP. The CLI works now
- WebRPC is almost done
- fixing bugs and improving the command line interface

So we are ready to list. We actually wrote an exchange but have not used it yet
- github.com/skycoin/skycoin-exchange

We have to
- improve website
- fix problems with wallet
- bug fixes on CLI

Then we need to
- start community
- start marketing
- launch the applications

Update:

First version of Skyhash/Aether is done
- https://www.youtube.com/watch?v=fXD_rdwoKsc
- https://github.com/gagliardetto/skyhash-pub-sub

there is no real marketplace right now as fas as I know. I think we have to wait for the Zico

Hi there , i'd like to know if there's a marketplace for this coin or if anyone's interrested to sell .

How to claim our coins?

What do you think about Zcash trusted setup?

Update:



Development Update:

- The Skycoin CLI is done. We can do exchange listing now.
- The v2.0 of the Skycoin.net website is done (but needs dozens of changes)





- The CLI tool is in skycoin/cmd/cli .
- We will have documentation for usage and exchange integration
- Right now, there are help commands

Zcash:

Zcash just hit $5000 USD per coin. Then went to $10,000 USD per coin.

The total market cap is starting at 3 billion dollars (half of Bitcoin).

This is what I mean by "inelastic capital inflows". People buy a fixed amount of each coin, regardless of current price. They will continue to add a fixed amount per month, into a basket of coins regardless of the current price of each coin (inelastic capital inflows).

I have been trying to figure out how to stop this for Skycoin, because it can result in massive bubbles and then it pops and people who bought at top lose money. However its easily possible for prices to increase to absurd levels, because people are only buying and no one is selling (market with only capital inflows and not capital outflows).

After two years of thinking about this, I do not believe there is a solution and will just have to accept whatever the market does in terms of capital inflows and outflows.

Equilibrium pricing exists, where the capital inflows match the capital outflows and where the capital in/out flows are stable. Or when the capital inflows/outflows are periodic and predictable and can be buffered by market markers. Absent those conditions, there is no stable or fair price and nothing we can do about it.

I am excited to see what will happen.

Can somebody help, please:



and this:




This is a lot! Especially for a project "nobody" s aware of.
Don´t get me wrong. I love this project, but this "ico" price is too much.

Why the daemon posts "Got 0 blocks since 440" and "no new block need to parse" all the time?

http://127.0.0.1:6420/blockchain/blocks?start=0&end=500
http://127.0.0.1:6420/blockchain
http://127.0.0.1:6420/connections

aren't valid urls for API?

Update:

Now that
- the coin is almost done
- the website is almost done
- we are almost done will all requirements for listing

Now we are on meshnet and distribution. We are working on pilot, to distribute coins for people running nodes.



This is prototype/example and will change.

Update:

The CLI and webRPC, for Skycoin exchange integration. Is here
- https://github.com/skycoin/skycoin/tree/master/cmd/cli

I am not sure if this works yet. Still fixing bugs.

It should be possible to list the coin soon.

Its a gopath issue. The repo has to be in the gopath.

Golang will look for dependencies and imports in the gopath.

The way to do this is
- `go get github.com/skycoin/skycoin`
- now skycoin is installed to the gopath
- now do `ln -s $GOPATH/src/github.com/skycoin/skycoin ./skycoin
- now you have a sym link into the repo

Then you should be able to
- `./run.sh`
- which is same as `cd cmd; go run ./cmd/skycoin/skycoin.go`
- there are other commands in that directory too

Update

There is a new wallet format
- https://github.com/skycoin/skycoin/pull/168/files


- BACKUP YOUR CURRENT WALLET
- Write down your wallet seeds and store them somewhere safely
- Open wallet with a text editor and look for "seed" value

As long as you have your wallet seed, you will get the same addresses and private keys

Questions about installation

Skycoin can be installed in one line

However, $GOPATH has to be setup. gvm is supposed to do this.

The installation instructions are in readme.md
- https://github.com/skycoin/skycoin/blob/master/README.md
- https://github.com/skycoin/skycoin