How did you create wallets?
"New address" button seems doesn't work for me.
I had the same issue. I assume its related to the bug I filed here:
https://github.com/skycoin/skycoin/issues/16Basically the current version ( 5afc6d2105b29c59e2259d1a842ad6f6458417ec ) doesn't seem to work, and there hasn't been a commit in the last ~6 days, so its just been in this broken state for a while. As least thats how it seems to me.
Even if I had a fixed version, I couldn't distribute it due to licencing issues (So I'm not going to spend time looking into it further): I still haven't found where the license is specified so I can comply with the terms if distributing. Knowing it's "Its either GNU or MIT" is nice, but I can't comply with even the MIT terms without knowing the copyright... (Note, GNU isn't even a license, its just not unix. GNU GPL version 2 is a license (so is GNU GPL v3 or GNU LGPL). And that seems like a rather silly duel license choice anyway)
Apparently there is a license for it on github somewhere: has anyone found it? I looked through the repo, readme and wiki, and searched the github pages: nothing to be found.
One developer merged in the new wallet RPC and the wallet GUI developer has not updated the wallet to use the new RFC yet. There is a --web command line option for running GUI in browser, for debugging. Its better for development than the QT client. You can inspect the javascript and see the errors.
The new wallet JSON interface allows loading and using multiple wallets in the same client, but broke the wallet GUI.
update: wallet dev will fix it tomorrowMost of the work in last week has been in the new wire protocol repo. Should be on github soon.
Skycoin License:The license will be a standard open source license. Current license is
- you can distribute code for non-commercial use
- you can modify code for non-commercial use
- You agree to copyright assignment under the to be determined open source license
- you grant perpetual license to use, distribute and modify any contributed code
We might have terms like "no forking coin without permission for 24 months after date X" and then license is MIT or GNU after that. We have already had to remove build scripts from the repo because someone tried to fork and launch the coin before us.
Skywire: Skycoin Wire Protocol:The wire protocol is almost done.
The new connection pool has "channels" (uint16). Each channel expose a "service" (a thing that sends/receives packets within a channel). Each connection between two peers in the connection pool can support multiple services running over the same TCP connection.
This is implemented by a connection pool and length prefixed messages with a "dispatcher" that handles the messages for each channel. Raw bytes can be read and written from channels, but gnet has a default dispatcher that allows you to register structs as network messages. When a message is received, the .Handle(...) method of the corresponding struct is called on the receiving end. The struct fields on receiving end are already set to the values that were transmitted. This makes building distributed P2P services very easy (summary: you put data in struct, hit send and on receiving end the .Handle() function is called on the struct).
Current services:
- block chain relay server
- transaction relay server
- emergency messaging server
- obelisk node server
There are tools for finding peers running particular servers using DHT (distributed hashtable) and exchanging peer lists between peers (PEX, peer exchange). Example, If you have a blockchain genesis hash, you can use the hash to find peers running a blockchain server for that chain and download the blocks from them.
If a user wants to create a new, more efficient system for blockchain replication, they can create their own service/server and put it on github and other people can use it. Its extremely modular and not monolithic like the Bitcoin wire protocol.
Darknet Service Example:This service architecture is the starting point for many of the darknet services. I will write a tutorial with code snippets, for creating a new darknet service.
This is a toy example for creating a distributed exchange through the Skycoin wire protocol, in a few hundred lines of code. You define structs for "check balance" and buy/sell commands and order book listing command. You run the exchange service and it automaticly connects to peers running the exchange service. You say "I want to sell 5000 dogecoin for 1 Skycoin", someone takes the order. The service negotiates the receiving address, receives the Skycoin and sends the 5000 Dogecoin.
That is a fully functional distributed exchange, but does not address cheating. What if you send coins, but do not receive coins? You could
- use a white list and only send coins to trusted exchange services (simpliest and works right away)
- use a more complicated protocol
To prevent cheating you might both agree "I will send 5000 dogecoin to address A within one hour. You will send 1 skycoin to address B within one hour". You both sign the hash of the agreement. If the person does not send the coins, you publish the transaction to Bitcoin talks and everyone can verify it and prove he is a scammer.
Or You both have coins in escrow with mutually agreed upon third party C. The signed agreement is given to C. If one side fails to execute the agreement, the amount is taken out of escrow and C executes that person's side of the agreement at current price.
Skycoin has a protocol under development, called the "gateway protocol" that will simplify these types of transactions. This is an outline for doing a simple distributed exchange with a "raw" service on top of what is implemented right now.
