thanks for update! so this one:  https://twitter.com/XCPCounterparty is not owned by Counterparty team ?or we just need to follow  a new official twitter account?

Has the majority of discourse moved to native channels ?

Blockchain.info queries
Regarding the blockchain.info site hits, those were necessary for retrieving an arbitrary account balances as well as unspent outputs (UTXOs) for an arbitrary address. This was only required when we needed to get this information on an address that was not in the local wallet (e.g. for counterwallet itself, as we do not keep web wallet users' addresses in the server's bitcoind wallet). As of our commits to develop this weekend, these blockchain.info calls are no longer necessary, due to us now using Bitpay's Insight daemon, which is a free, open source product that provides an API with similar services and is installed on the local machine, parsing through the blockchain files stored by bitcoind. More info: https://github.com/xnova/counterpartyd_build/blob/develop/docs/SettingUpInsight.rst)

However, regarding this, note that counterpartyd has a new "insight-enable" config setting. By default, on mainnet, this is set to 0 (off), due to the overhead with setting up insight (e.g. it's similar complexity to setting up bitcoind, and takes about 30GB on disk once the mainnet data is indexed -- we didn't want to force doing this on people that just wanted to use counterwalletd to run the GUI on mainnet, for instance). If this setting is off, blockchain will still be used to get the required data (and note this is not a persistent connection, it's just a simple HTTP query as we need to get the data). Moreover, Insight is required to be used on testnet, since blockchain.info's APIs do not support testnet.

I'm glad that we could remove this dependency on blockchain.info. We feel the same way about consulting 3rd party sites in the code of a "decentralized" system like Counterparty. It was a hack at first due to the limitations of bitcoind, and we've been able to move past it this weekend, employing a more proper solution that preserves decentralization (i.e. using insight, which is free, open source, installed locally and works off of the local blockchain data).

Version check (github.com query)

This is a simple (i.e. non-persistent) query to a single .json file on github, to make sure the client is up to date with the most recent major modifications. This was done to avoid forks (i.e. situations where someone starts up old code, and ends up sending out an invalid txn, which is seen as valid by those running counterpartyd on the same old code, but not by people on the newer code, for instance). These are serious situations, and due to the rapid pace of counterpartyd development, this was seen as the most acceptable option, as the file it hits is a) public and b) under version control, in the same location as the code, and c) published/updated in the same manner as the code is (signed push by the devs).

Also, even with this check, note that if the client is NOT up to date, counterpartyd will simply complain and not start. It will NOT automatically update any code, or make any changes.

Moreover, Phantom has just today enhanced the --force flag to avoid this version check, so if you REALLY want to run without this functionality (not recommended!), you can just use --force. Again, we do not want to make people have to have their client check an external 3rd party site. It's just in this case, it's a Really Good Idea that we default to. This check will remain, at least until development has slowed down. We think it's a good idea beyond that though, to avoid forks as much as possible.


Hopefully that clears up some of these concerns. Thanks guys for working with us and being patient as things continue to take form.

So would it not be possible for the Bitcoin development team to simply implement all of counterparty features directly into the protocol ? Like say, in version 1.0 ...

And if so would they have any incentive to do so?

The hard-coded fee is temporary.

It's hard to burn BTC without creating unspendable txouts.

The difference is from the Asset Issuance fees.

From what I understand it was supposed to be 5 XCP per asset issuance but there was a bug in the calculation (which I already reported very much earlier) which only deducted the divisible amount instead of a full 5 XCP.

Announcement: Counterparty's weekly blog is live!

We will be writing a blog post every week, collating the most important information, so that the community does not have to sift through pages of forum threads to stay up-to-date.

The blog will focus on developments within the Counterparty project and community. Topics may include: significant updates to the reference client, announcement of bounties, interesting uses of the Counterparty protocol, as well as new collaborative efforts with members in- and outside the digital currency community.

On that note, in the first blog post, we announce that the Counterparty team has hired two Bitcoin security experts to audit Counterparty's code! For further information, continue reading here: https://counterparty.co/news/.

Cross-posted from the "blog thread"  on the official Counterparty forums.

Watching the gay candy crush ripoff logo and seeing that people are giving BTC away to be on crappy exchanges will sure scare away many people, I agree.
Can't believe people have funds for this, but nothing to support the GUI... Crazy.

so i got bored over the weekend and went on odesk and paid a little change to have someone make a banner for one of the reddit pages

this is not the final since he misunderstood the directions and made the candies way too small and a few other errors...  the role of this imagery is to encourage people who are game designers and not finance oriented people. i'm sure the other reddits will have that all covered for you traders.

Developers: The API has changed a decent amount in the newest updates to the develop branch. This includes several enhancements, function name changes, changes in semantics, etc.

Please check out the updated API documentation at: http://counterpartyd.readthedocs.org/en/develop/API.html

I just did a push. Please update.

- update for counterpartyd 6.1
- adding a passphrase field
- Adding a confirmation before each transaction (temporary, it is planned to make a dialog box that summarizes the parameters of the transaction)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
https://github.com/JahPowerBit/BoottleXCP

Perhaps an official press release would help, rather than the aggrieved parties having to trawl through this thread, which consistently refers to the action as a roll-back of the database/ledger.

Perhaps, technically, this is inaccurate,  but the fact is in the real world of commerce, transactions occurred and actions were taken; the effect being that the ledger was altered, and those transactions were invalidated.

+1
Now someone trustworthy to handle the details

Yeah I did have some ideas:

1. Lets get the bets rolling. Maybe a Superbowl bet would be good, if its not too late.

2. Getting a video commercial type gig like what Colored Coins has.

I don't have many ideas right now but I will brainstorm on it.

I believe the bet and broadcast commands still need to be published.

Patel if you have some particular suggestions, please PM me.