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

Poloniex was hacked again

Hahahahaha! I love this. (Can I use it?) You're the bitcointalk winner today!

I would just like to announce the first additional color theme for donations by user Flayway!
I will be adding an ocean/turquoise theme and naming it after him for his support of JahPowerBits development fund.

The official account will be a bit more restrained and will be used to issue timely updates, alerts, and announcements in a convenient format.

This +1

Yup, I could barely see a difference with the official account :
https://twitter.com/CounterpartyXCP

1 Million Dollar Austin Bitcoin Hackathon could be right up XCP Developers' alley.

http://www.reddit.com/r/Bitcoin/comments/1zh0rj/im_the_one_putting_up_1_million_for_the_austin/

Wow! That's a super active Twitter account from the community. Kudos to whoever publishes that feed. Well done.

That is correct. The owner of that handle, to his credit, has offered to change the name of the account to prevent further confusion.

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?

Small announcements, version changes, and similar items will be pushed to the following channels. These are the only official Counterparty channels outside of the Counterparty.co forums and this thread.

http://www.reddit.com/r/counterparty_xcp/
https://twitter.com/CounterpartyXCP
https://www.facebook.com/pages/Counterparty/1463675043856592?ref=hl


Major news and events will be published on the Counterparty news feed.

https://counterparty.co/news/

Once again, a professional attitude to development and communication which is rare in the alt coin sub forums. Thanks guys.

Yeah I bet the farm on the Counterparty mojo.

If we all want to get rich from Counterparty, we need to build more and the conversations on the Counterparty forums seems to be focused on building mainly. Not sure its the majority of discourse, but hopefully a path to profits for everyone?

Has the majority of discourse moved to native channels ?

I updated my proposal for Asset Issuance fees to be reduced to 2 XCP from the current temporary 5XCP that is burned in each asset issuance.

Here: https://forums.counterparty.co/index.php/topic,150.msg1060.html#msg1060

If the community has any comments or views on this request for a change in the temporary asset issuance pricing, will you post your views?  This will cut the cost of asset issuance immediately as we continue to review and propose new approaches to smart property asset fees.

Changelog in YO FACE! Yeah!

Really sorry guys, we ran into a couple snags but we are still working away on it!
Also taking suggestions of forum members into account has added a bit of work for me.
I would say we are 90% complete, color themes and all!

Want a specific color theme combination added to the code? donate a small amount to JahPowerBits donation fund and send me a PM with the colors you like!

Post your address, one of us can send you some coin.

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.