There is no easy way to do it now.

In theory, you get the master key of the deterministic wallet via `cw-cli getval dw_master_key` and write it down on a piece of paper.

Later you can restore it via `cw-cli setval dw_master_key "<key here>"` on a new installation. Then add assets, generate new addresses (as many as there were in old wallet, it won't discover them automatically), and then `cw-cli full_rescan` to fetch history.

However, I haven't really tested it.. And, of course, we'll add a simpler way to do this some time later.

Alternatively, you can get private keys via `cw-cli privatekeys <asset name kere>`. But there is no command to import private keys yet. In this case it's pretty similar to normal Bitcoin paper wallets, but you should remember that it's colored, of course.


Yes, but user interface won't let you to transfer to a normal Bitcoin address.

Yep, we can add it to ChromaWallet... epobc color kernel (which we use now) has no special meaning for OP_RETURN, so you can just a contract hash (or, really, anything) in there.

But I believe this should be a separate layer, and for now we focus on the core layer.

I doubt we'll have a lot of assets worth buying, so things like automatic discovery are largely unnecessary.

In any case, it is up to investor to perform due diligence, this cannot be automatized in the general case, and checking PGP signature is a small part of it.

Here's what I think is a normal way to issue shares via colored coins: http://www.alefbit.com/investor/issue/

The contract: http://www.alefbit.com/pr/AlefBitIssuance.txt is PGP-signed by the issuer.
Of course, it is meaningful only if one believes that it was really signed by Ariel Horwitz, and that Ariel Horwitz is trustworthy.

Use of contract hashes and Namecoin doesn't really solve the main issue, issue of identity and trustworthiness check, so I don't think it's worth the effort atm.

But it was mentioned more than once, so there is something in it, I guess. Still, PGP integration could be orders of magnitude more useful.

Thanks

Yes, it's possible to make a block explorer, in fact we had one, but it isn't being maintained. I gotta check what's the current status...

I've made a bid for your asset.

We plan to add it at some point, but it isn't high priority, since issuer can easily publish this meta-data on his own web site (or, if anything, on forum).


Color is identified by a hash of the issuing transaction (in ChromaWallet), each transaction will thus create a new color, and so issuing coins of the same color is simply impossible. (Unless you can produce another transaction with the same hash.)

It works differently in CoinPrism: color is identified by address which was used when coins were issued. However, only the original issuer controls private key which is linked to that address, and thus only he is able to issue more coins.

You might have a better luck trading with me. If you create an offer to buy frobz:


I'll try to fill it.

I've tried trading with LOL but found two problems:

1. I can't fill his offers due to "Not enough money" problem. (It looks like we messed up check for available balance in p2ptrade page.)
2. When LOL tries to fill my offer it doesn't work because it hits the fee limit. Apparently it is one of those rare cases when buyer has to pay for two paddings + a fee on top of that (i.e. 8192 * 2 + whatever is the fee).

So p2ptrade is basically unusable for now. (Although it worked fine when I was testing it on my asset.) I'll try to fix this ASAP, and also next release will have SPV support.

On the bright side, fee limit seems to work correctly.

You can edit moniker when you add an asset, just call it lol2 or something like that. That name exists only in your wallet, it doesn't affect anything.

Currently there is no button for deleting assets, and doing it via command-line is a bit tedious.


No.


We plan to add compatibility with CoinPrism some time later.

What do you mean by broader definition options?

Just to clarify, market is more-or-less real-time. You will only see offers if people who posted these offers are online.

Trade can be closed in about 10 seconds.

It is possible to cancel an offer before somebody fills it. It is cancelled immediately, but will still appear on others' orderbooks for about 30 seconds.

New version doesn't need local bitcoind/bitcoin-qt.

You can get it here: https://bitcointalk.org/index.php?topic=106373.msg6767249#msg6767249

Distributed exchange isn't a part of colored coin protocol, but it is possible to build a distributed exchange on top of colored coins protocol.

helloblock.io is used to get information about transactions. (E.g. scan for payments we received.) We also get information about transaction confirmations from them.

We create and sign transactions ourselves, via pycoin library.


Yes, local bitcoind isn't required.


SPV allows us to verify whether transaction was published in the blockchain. (Cryptographically.)

If helloblock.io gives us wrong information, it won't pass the check, and thus no damage will be done.

There is also an option to use Electrum servers. It isn't quite ready now, but in future it's going to be about as secure as Electrum.

New build:

Linux 64-bit: http://killerstorm.xen.prgmr.com/alex/chromawallet-linux-x86_64-0.0.6.tbz
Windows 32-bit: http://killerstorm.xen.prgmr.com/alex/chromawallet-win32-0.0.6.zip

 * There is a history tab now.
 * It scans for received payments automatically in a background thread, there is no need to click 'Update', and it starts faster.
 * We use helloblock.io instead of blockchain.info because there were problems with blockchain.info. Also, helloblock.io works with testnet
 * Problem with invalid balances and things like that were solved. (Well, hopefully.) People who used older versions needs to run cw-cli full_rescan first
 * For now it simply trusts data it receives from helloblock.io. We already have 99% of SPV implementation, it will be present in the next version.
 * p2ptrade got several improvements, but might still be finnicky

Note: People who used older versions needs to run cw-cli full_rescan first.

Known issues: Old send and trade transactions will be displayed as 'unknown' in the history. We will address this later.

Some of problems which were reported by LOL were not fixed, particularly, it's possible to confuse it with 1-satoshi transaction, but it won't be in a permanently-stuck mode.

You can see the development progress here: https://github.com/bitcoinx/ngcccbase/commits/master

As you see, the last commit was 2 days ago. (But we also have commits which are yet to be merged, the last was 2 hours ago.)

I already explained that progress is much slower than I want it to be, but we keep working on it. (One of reasons for delay is civil unrest in the region I live in. (I live in Donestk.) It is hard to focus on code when we are on the brink of a civil war, and armed people on streets are a norm. Sorry.)

Our goal is to implement a thin SPV wallet (which gets data from servers, but verifies all the data it receives, so it doesn't need to trust that server), with p2ptrade and, potentially, other goodies.

It is very different from the web wallet CoinPrism have implemented: it is 100% dependent on server and lacks p2ptrade. (Which I'd say is the most complex component.)

Currently we have all main functions working, we are finishing SPV support and fixing smaller problems. p2ptrade is working as long as there is no abuse, we are going to add protection against abuse later.

Ehm, managing it requires:

 * renting space
 * paying for cooling and heating
 * hiring somebody to manage devices
 * doing currency conversions
 * logistics

That's a lot of work, and it's not clear if it can be profitable at this point...

You see, when Garr was managing it as a hobby of sorts we had many of these things more-or-less for free, but it clearly doesn't work now. You need more professional approach to get good results, and that requires money. While, on the other hand, difficulty is pretty high now and gets higher and higher.

Talking specifically about Goat, he has a lot of bitcoins... Do you think it makes sense to waste a lot of time to get a tiny profit out of a mining operation when you're in such a position?

Nope. It makes a lot more sense to liquidate it ASAP and forget about it.

There is no API for that right now, I'll try to make it soon.

Yep, thanks a lot.


0.00028 BTC is the total extra amount which buyer needs to add. 0.0001 BTC goes into a fee, and 0.00018 BTC might be necessary as padding for two colored outputs. (Up to 8192 satoshi per output.)

Of course, in many cases padding is not necessary, so buyer might be overpaying, but it is simpler to implement it this way. We'll optimize it later, of course.


This is a known feature, seller gets 'change' if padding was not needed.


It is more like a notification popup, I consider removing it. However, I'm going to add confirmation on cancel action.


Yep, this is interesting.[/list]

This is interesting, indeed.

I think 'history' command is defunct now, I'll try to add it back tomorrow and we'll see what happened

New build:

Linux 64-bit: http://killerstorm.xen.prgmr.com/alex/chromawallet-linux-x86_64-0.0.5.tbz
Windows (32-bit): http://killerstorm.xen.prgmr.com/alex/chromawallet-win32-0.0.5.zip

Now if your wallet got "corrupted" like mentioned above, you can do "cw-cli full_rescan" to repair it. (It takes about 10 seconds.)

I haven't addressed the root cause yet, though.

Information about unspent transaction outputs got out of sync with blockchain because one of wallet transactions wasn't accepted by the network.

Wallet file is an sqlite database, you can use sqlite3 or sqlitebrowser to open it. If you delete contents of coin_data and coin_spends tables, they will be populating according information about unspent outputs from blockchain.info. (It is an equivalent of `bitcoind -rescan`.) You might need to click 'update' twice until it shows right numbers.

Of course, there is some bug in chromawallet which caused this, I'm investigating...


Yep, that page isn't working properly. It creates addresses, but they aren't displayed.