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

Thanks for the link.
"The client can't spend just 10.00 BTC out of a 10.89 BTC payment anymore than a person can spend $1 out of a $20 bill."

So I guess this is one aspect about Bitcoin I didn't grasp before now.
Which reduce quite a bit it's awesomeness I must say...

Maybe it's because I made most of my transfert from online exchange and wallet.
Where it's not a problem to send 1/10 of my coin, and just 2sec after send 2/10 of the rest elsewhere.
I'm not froze for a blocktime.

Yeah I got it now. The abstraction of online exchange hided this "default".
At least it send the change to the same pubkey, and not randomly-without-control like bitcoind.

Just noticed that server shows block No 278338 with current time. What is it and how to fix?

I suggest also rebuilding the db from your end.

This is just how bitcoin works, after all.

Does this help?

https://en.bitcoin.it/wiki/Change

There used to be a picture somewhere...

I did not understood the beginning.
Maybe on a technical point of view it is hard or not possible in this case to not have change, I don't know.
Understood last part.
What I don't get is why *all* BTC must be moved.
No change = no need for confirmation = annoyance solved.


avkinp, we're around 1300 XCP/BTC now

Update to new version wininstaller. Server is running well just started but after current block reach it stopped with no accsess to Bitcoind. I cant even open wallet until i close counterpartyd server. Am i missed something?
By the way is it 1400+ for 1BTCstill???     

Unfortunately I don't think bitcoin works that way. When you are trying to send an amount (0.0002172) that does not exactly match an unspent output, a transaction has to be made that takes the remaining amount and sends it back as change. The "problem" is that the amount sent back as change is unconfirmed, and counterpartyd does not allow spending of unconfirmed outputs (while I think the main client/blockchain.info does).

There seems to be an error where only assets set to divisible can have dividends distributed.

I made some test.
Here is a list of thing to improve ASAP:

- with send command (XCP or assets), some BTC are send along.
  without warning, nor choice on the amount...
  and it's a weird amount (0.0001086 BTC), which is totally useless
  Reason: with multisign, every command other than burn need a minimum of 0.0002086 BTC
  (the send command cost 0.0002172 BTC, so 0.0001086 is not enough to move again)
  I'd like at least a warning (cost x fee + y BTC moved to this destination, total = z BTC : do you accept?)
  Ideally I'd like to be able to choose this amount (0 BTC by default, or x)

- if asset == 'BTC': raise exceptions.BalanceError('Cannot send bitcoins.')
  it's such a pity, can't you modify it to be able to send (only) BTC from a selected pubkey?
  bitcoind miss this basic feature, which is annoying
  Beside, *it is possible* to send BTC trough counterprotocold, as send-cmd sent 0.0001086 BTC

- edit for this one: online exchange hided the "change" limitation to me, 'guess it cannot be improve
  every command freeze the total amount of BTC of the selected pubkey for 1 blocktime
  Example: pubkeyN has 1000 XCP & 1000 BTC, send-cmd cost 0.0002172 BTC
                  if I enter the command to move my XCP, all these BTC are frozen...
                  why does the other 999.999 BTC need to be unavailable for 1 blocktime?
                  awesome if you can improve that by stopping to move what doesn't need to move
                  just take the 0.0002172 or what it will cost in v0.9 with OP_RETURN (back to 0.0001 BTC I hope)
                  If I moved 500 XCP, I need to wait 1 blocktime to be able to move other XCP => annoying
                 
- your man help page are wrong, and unclear for new user (most important: miss = sign, which is obligatory to work)

Result example:

What I'd like to get:

Is the "dividend" command already working? I'm trying to pay dividends to an asset I just created ("MAXM"), but the total amount is 0:

Am I missing something here?

Yes, I am currently working on the order display and have updated the latest changes.. I believe I am getting closer :-). I have swapped columns for the buy/sell so that it follows the sequence of the "order" parameters command. Every order is a "buy" first


The buy prices are actually available in the order database so I am picking those up from there. However, I believe the divisibility (0 or 1 value) of NON BTC/XCP Assets can be set on a per individual basis when the asset is initially issued(generated).

The transaction looks right, but the TEST/XCP value from the log looks wrong, again.

Also on blockscan:
- "Price" should include the pair (e.g. XCP/TEST) instead of just "XCP"
- For BTC/XCP, buy and sell prices look right; the "price" column is still wrong (you could derive/verify the price column by dividing the buy by the sell price...) - more confusingly only some of the prices look wrong.

(I hope this "intensive" testing is useful, BTW).

Oddly I see that my order for selling 5 TEST (that I put in later, at a slightly lower price) matched first on blockscan. Do we have a fork, or will this be resolved somehow?

EDIT: need to rebuild database. Check back later.

I just rebuild the database and I can see the orders being matched now. My address received 11 TEST (1+10) so this seems to be working well now.


I think the expiration value is just the amount of blocks the order is valid for. When creating a new order you can set the expiration value yourself.

Sorry about that. The assets (like TEST) should not be divided as they are not denominated in "satoshi's style". I have updated the view->order page on blockscan

How is the expiration value calculated and what is this based on? I assume this is countdown from a specific start time? If yes, is the specific start time based on the block time or some other value?

Cheers

When will I be able to trade XCP? Are you planning to start an exchange?

With the new version, that has those rounding errors fixed, I do see 10 TEST transacted:

(Obviously that last match is funny. I'll fix it.)

On the old version, it's only 1 TEST.

Only part of your order matched due to rounding errors (?) I'm putting up more orders to better assess this.

We are in a position to be able to support bounties at least during that crucial initial 3-6 month period post-burn. Our goal for bounties is that the amount awarded is enough to motivate people to build things around Counterparty, which themselves will quite often generate revenue (or give them benefit in some other way). Publicity and community awareness will also be a big focus as well (and a way in which non-developers can easily get involved). This all being said, bounties won't be nearly as large as with Mastercoin, for instance -- due to their different offering model. However, we believe that the functionality and opportunity that Counterparty already provides as a base framework creates ample opportunity, and bounties will really help kickstart community and possibly corporate developments around it, as well as getting the word out to people and organizations that would find what we have here to be useful.

I created a matching order (0.04 XCP <-> 10 TEST), let's see how this works out.
EDIT: it did work, I now have 1 TEST in my wallet. Awesome! Hm, I should have received 10 TEST, will wait a couple of blocks to see what happens.