Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread - page 114. (Read 1276789 times)

https://github.com/CounterpartyXCP/counterwallet/issues/2

This message was too old and has been purged

I believe there's a bounty for this. Just surprised why still nobody claims for it. With the Trezor API, it is not so difficult to add this function. Actually, for personal usage, it is possible to develop a super lightweight wallet to support 'send' function at least. The idea is like this:

1: Check the balance by using Blockscan API (it is safe to skip this step if you are sure you have enough balance in your address. But I don't think BlockScan will mind if we use their API, since it is not so different with we just querying the balance in their website. Correct me if I am wrong, Mtbitcoin. :-) )
2: Generate the 'send' transaction with the help of counterparty lib (coding it follows the specification in other language is also easy. Recommend to use the OP_RETURN version if you don't mind maybe a little bit longer confirmation time).
3: Sign the transaction with Trezor API.
4: broadcast the transaction in https://blockchain.info/pushtx.

This client does not need any bitcoin full node and even counterpartyd running. I just don't have time to implement by myself. If anyone is interested, feel free to implement it to get the bounty.


Moreover, I think if Mtbitcoin can implement this in Blockscan, it will be even better. All these can be written in Python and Javascript. Due to the feature of Trezor, nobody needs to worry about leaking the private key when using this function.


  

This message was too old and has been purged

The trade between XCP and BTC in the DEX is troublesome (because the BTC cannot be escrowed) and that's why it is no longer supported by the counterwallet.

I see. Thanks. I just wish these transactions are signed offline.

The problem is people using those exchanges for other than daytrading, obviously storing those big amounts of money in those shady exchanges is asking for trouble.
If you follow some trivial security guidelines, your own computer is safer that all those exchanges.

XCP has a decentralized exchange built in that is the answer to this.

The problem is that there will be one less exchanges for XCP, which already suffers from lacking of reliable exchanges. I don't think most people will still trust Bter and keep their coins there after this disaster.

BTW: where can we know the XCP addresses of the exchanges? Why do you know 1NFE... belongs to Bter? Thanks.

This message was too old and has been purged

Wish Bter will be back and return every XCP deposited there. Hopefully the situation of once largest exchange of XCP will not affect Counterparty much.

Instead of copy pasting the steps, I'm going to post a link to a Counterwallet tutorial (how to work with Armory). I believe your question was addressed in support, so this is for anyone else having the same problem: http://counterparty.io/docs/create_armory_address/

If I'd be the judge I also would say you don't administrate it but that term (administrate) is so vague that a request for clarification would bring more legal certainty which is also what the article suggests.

I don't know what kind of clarification you're looking for. I don't have any comment to make on that article or BitLicense. (Obviously, we don't administer XCP or any other currency.)

http://www.coindesk.com/bitlicense-2-0-latest-revisions-mean-bitcoin-businesses/

Would the Counterparty team want to clarify things here?

Most important Counterparty news since Medici

JPJA has figured out how to revive BTC trading on the DEx with no bullshit.

The problem with DEx BTC trading is it's slow and costs fees. This is fundamentally impossible to work around short of drastically reducing Bitcoin's block time, and even then, a per-trading-action fee may still irreparably harm liquidity compared to centralized exchanges, which already have a tough enough time getting liquidity.

JPJA has devised a method to overcome these fundamental limitations with BTC trading, with the introduction of a BTC DEx auction mechanism akin to Ebay.

An auction mechanism is unbeatable for two reasons:

1. The fees and delay inherent to the DEx become much less of an issue.

If you've ever used an auction site like Ebay, you know how it works. You place a bid, and you wait, usually for hours or days unless you're sniping the auction. High frequency trading isn't in high demand, and you go into the auction expecting to pay Ebay a fee at least upon winning.

2. DEx BTC liquidity is solved.

Imagine an auction sale of 1 BTC for XCP with no reserve. The BTC could be bought at below market rates. Market participants will pay attention to the auction regardless of lacking liquidity. The less popular the auction is, the higher the potential for profit.

Compare auctions to an order book. Without liquidity, the order book's value for traders rapidly deteriorates. This is why traders will almost always tend to prefer centralized order books where it's easy to enter and exit positions instantly.

JPJA's auction format concept adds tremendously to the core value of the Counterparty platform, and deserves serious attention from all XCP investors.

In other news, the favored currency symbol for Counterparty XCP is arguably the unicode ℂ (U+2102).


It makes sense for the currency symbol of Counterparty to contain a clearly visible C. The cent symbol ¢ comes close to ℂ in this regard, but ¢'s use for the cents subunit cheapens it too much. ℂ renders better for me, too - it's the closest unicode character to a capital C that qualifies as a currency symbol - compare ℂ to €. Edit: the Ghanaian Cedi (₵) symbol is also of interest, but to my untrained eye the cedi ₵ appears overly similar to the cent ¢.

WOW !!! 

https://bittrex.com/Market/Index?MarketName=BTC-XCP

Nice address.

Forgot to post this yesterday. For everyone who missed this week's update, here it is: http://counterparty.io/news/counterparty-update-feb-13/

https://bittrex.com/Market/Index?MarketName=BTC-XCP

Sure. For whatever the work might be, I'll take a picture or do a scan of the object showing enough irreproducible detail to ensure it is of this one instance of the object. Then take a RIPEMD-160 hash of the image file and add it as the description when the token is issued. RIPEMD-160 is chosen because it outputs 40 bytes which will fit in the description field and of course is used by Bitcoin itself. Then I'll probably host the image file so they or anyone else could verify authenticity in the future.

I worked with mtbitcoin to get Blockscan.com to ensure that it's easy to see the description set at time of issuance. Previously, you could only see the latest update to the description. This way, the description can be updated to provide a link to the enhanced info json file(icon image, extended informational text, etc.).