Quote from: Muhammed Zakir on January 09, 2015, 04:14:27 PM

Quote from: pankogulo on January 09, 2015, 03:42:01 PM

Developers are making great progress as usual: Counterparty Development Update #10: New Counterwallet Release, Desktop Wallet Development & More http://counterparty.io/news/counterparty-development-update-10/

I'm waiting for counterparty-GUI. Do you know when it will release? Approx. time?

Bumping the post:

Quote from: Muhammed Zakir on January 09, 2015, 03:36:06 PM

Is there a possible way to sent an asset with custom BTC fee?

~~MZ~~

This same question was posted and answered recently -

Quote from: Anotheranonlol on December 18, 2014, 12:48:27 PM

Not sure if this any of these have been posted before, I had just noticed them browsing github

Auction platform that works with counterparty assets:

http://auction.letstalkbitcoin.com/ source: https://github.com/deweller/auction-machine

Smart Contracting As A Service platform (alpha stage):

http://etherparty.io source: https://github.com/etherparty/etherparty.io

Ruby gem for communicating with a Counterparty (Bitcoin / XCP) API server:

source: https://github.com/brighton36/counterparty_ruby

Quote from: Jpja on December 18, 2014, 12:29:37 PM

When you transfer a Counterparty Asset, you send a dust-amount of BTC as well.

Is it possible to transfer any amount (>= dust limit) of BTC in a Counterparty transaction?

For example, an electronics store sells a TV for 1 BTC. However, if you have a discount token, you'll get the TV for 0.9 BTC + 1 discount token. Can the 0.9 BTC + token be transferred in one transaction?

usually you apply the discount at the shopping cart stage, the price is then recalculated at checkout, could be done that way but it's a little cumbersome. (Especially if the user doesn't pay in the end) I think it is possible though. see: https://wiki.counterparty.io/w/Sendmany
Maybe there has been some newer developments on that front though or a more appropriate way

Quote from: PhantomPhreak on December 18, 2014, 03:43:26 PM

Quote from: BitThink on December 18, 2014, 01:30:00 PM

Quote from: Jpja on December 18, 2014, 01:23:11 PM

Quote from: Anotheranonlol on December 18, 2014, 12:48:27 PM

usually you apply the discount at the shopping cart stage, the price is then recalculated at checkout, could be done that way but it's a little cumbersome.

One way to implement a token-based discount is that whoever owns/holds a token gets the discount. Another way (that I had in mind) requires you to transfer it back to the store. In this case it is lot more convenient to transfer both BTC and Counterparty token in the same transaction.

theoritally it's fine to replace the antidust amount sent to the recipipient with any amount larger. However, it's not implemented in the current counterpartyd yet. Maybe later we can customize the amount of BTC we sent in xcp transactions, but I am not sure whether this is really useful.

It actually is implemented, both in the CLI and the API, at a per-transaction level:

Code:

--regular-dust-size REGULAR_DUST_SIZE
value for dust Pay‐to‐Pubkey‐Hash outputs, in BTC
--multisig-dust-size MULTISIG_DUST_SIZE
for dust OP_CHECKMULTISIG outputs, in BTC

It's useful if you're making a *lot* of (similar) transactions, and want to lower your costs as much as possible. The default fee and dust values are very generous, because they have to work well in all circumstances.