Uh, there is development going on:
https://counterparty.io/news/counterparty-lib-9-55-2/

That link also contains a link to our slack chat which is the best way to stay up to date.

Nope they are totally differently things.

Offline (cold storage) wallet: here is one for ledger S -- https://github.com/mandelmonkey/ledger-cp

Main BCT thread: https://bitcointalk.org/index.php?topic=1617264.0

Check out all the links there and join the telegram group

Because, math and stuff... each card is a Counterparty asset (embedded into the Bitcoin blockchain).

Sure, you could save the image itself to your computer, but that doesn't mean you own the card.

http://Counterparty.io

EDIT: here is the asset info for Pepecash, for instance: http://blockscan.com/assetInfo/PEPECASH
(Click on AssetHolders to see which addresses own PEPECASH)

Blockscan.com is one of the Counterparty explorers.

The first time I saw HAIRPEPE was within a data dump, as I was trying to figure out how the network crashed. I think my initial reaction was wondering what the hell a "hair pepe" was.

IIRC, the parameters chosen for a HAIRPEPE order hit up on an obscure bug where the calculated integer value chosen for the order quantity was higher than the max integer value for sqllite, but equal to the max int value used in the python validation code (they differed by 1). Thus, the value was not further limited in the sanity check code, and  when the daemon was attempting to store the record in sqllite it caused an exception.... we now handle this situation in a way that should avoid this kind of issue in the future anywhere in the code.

Because of all of this, as well as the excellent artwork, today it is my favorite card. That hair...

No, since contract executions can modify a state shared across the nodes.

However, there are other options, like a side chain of some sort, that could be employed in the future.

EDIT: See https://github.com/CounterpartyXCP/Documentation/blob/master/Basics/FAQ-SmartContracts.md#can-payment-channels-be-used-with-the-evm

Also see: https://github.com/CounterpartyXCP/Documentation/blob/master/Basics/FAQ-SmartContracts.md#how-does-bitcoins-10-minute-block-time-affect-the-evm

Try not using MAX (use slightly less. MAX appears to be slightly off due to the new fee estimation code in the new release. We will get that fixed.)

The link is old, will fix/remove that too.

Blockscan is currently updating and is down. You can use counterpartychain.io until it is back up

Try now. I updated wallet.counterwallet.io ... the problem 90% probably an insufficient BTC error (i.e. you lack the BTC at the address to make the transaction, as CP transactions require BTC fees), but that error message was not coming through due to a bug that has been fixed.

Will need some more info to be able to troubleshoot. Can you join our slack and DM me on there (@robby-dermody)?

Hey guys, can you update the forums link for Counterparty to https://counterpartytalk.org ?

the first part is true (Bitcoin does not validate Counterparty transactions), but it doesn't follow that there is thus no record of consensus. counterparty keeps its own "ledger in a ledger" that it assembles from decoding Counterparty protocol data payloads from any Bitcoin transaction that contains them, using the reference client code at  https://github.com/CounterpartyXCP/counterparty-lib ,

it has been working well for over 2.5 years now

With regard to "tangible new developments" I think that was a valid view 6 months ago, but the project has been revitalized on several fronts. We have daily code commits on our github repos that outpaces most other crypto projects by a wide margin. In the last month, developments include:

* all the EVM work being done (almost live on testnet)... Faq at http://counterparty.io/docs/faq-smartcontracts/
* p2sh support added (https://github.com/CounterpartyXCP/counterparty-lib/pull/818)
* payment channels work (https://github.com/F483/picopayments) that will soon be merged in
* revamped docker based build system. Works on Linux, Windows and Mac OS. (http://counterparty.io/docs/federated_node/)
* numerous counterwallet updates (https://github.com/CounterpartyXCP/counterwallet/compare/1.7.0...master)
* revamped website (Chinese and Japanese translations in the works)
* Counterparty-lib test suite overhaul
* tons of bug fixes (eg https://github.com/CounterpartyXCP/counterparty-lib/commits/develop)

Feel free to join our slack and ask away/get involved, as well: http://slack.counterparty.io

Yes

900 XMR

#8 - 0.57

#3 - 500 XMR

It's a fundamentally different approach. BTCRelay as I understand it allows validation of bitcoin transactions in Ethereum smart contracts. Counterparty executes the Ethereum smart contracts essentially as mainnet Bitcoin transactions. A smart contract execution, once kicked off, will execute within a single block (e.g. each instruction in the smart contract is not a Bitcoin transaction, or anything like that...they execute independently and modify the state of the Counterparty internal ledger, not Bitcoin).

Re: freezing, I'm not sure the amount of XCP frozen at any one time would be material to the total amount of XCP in existence. If that is not the case, then some "scale down" coefficient can be introduced that will reduce the amount of coins frozen for a given smart contract execution as the total # of coins frozen at any one time increases. Schemes like that do add complexity, however, and I'd like to avoid them if it's not deemed totally necessary, at least for a first pass.

Sure, they're not linked (that is more the theme with something like BTCRelay).

What we are working on is a port of the Ethereum Virtual Machine (EVM) to Counterparty. This means that one can take an ethereum smart contract (e.g. written in solidity) and run it "on Counterparty, on Bitcoin". There is no link to the Ethereum blockchain.

Counterparty works via a mechanism called embedded consensus, where we embed our protocol data within regular Bitcoin transactions, and maintain our own embedded ledger within Bitcoin's. Executions of Ethereum smart contracts would modify the state of this ledger.

See the announcement here: https://counterparty.io/news/proposal-for-ethereum-smart-contracts-on-counterparty-mainnet/

Feel free to join our slack channel to discuss. We'll also try to answer questions posted here as well.

We are working to improve on this front, and have some plans here.

In the meantime, you're welcome to help out. Feel free to join the #marketing channel our slack chat.