Bitcoin Forum
October 09, 2024, 10:35:19 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 [127] 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 ... 661 »
  Print  
Author Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread  (Read 1276539 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
supersuber
Member
**
Offline Offline

Activity: 118
Merit: 104


Counterparty


View Profile
February 08, 2014, 05:41:33 AM
 #2521

issuance --source=YOUR_ADDRESS --asset=ASSETNAME --quantity=QUANTITY divisible

Code:
   if asset[0] == 'A': raise exceptions.AssetNameError('starts with ‘A’')
lib.exceptions.AssetNameError: starts with ‘A’

 Embarrassed


What is your version of countepartyd? You need to update to the latest version v0.3.

已经升级到最新版了

520Bit
Sr. Member
****
Offline Offline

Activity: 602
Merit: 252



View Profile
February 08, 2014, 05:52:55 AM
 #2522

issuance --source=YOUR_ADDRESS --asset=ASSETNAME --quantity=QUANTITY divisible

Code:
   if asset[0] == 'A': raise exceptions.AssetNameError('starts with ‘A’')
lib.exceptions.AssetNameError: starts with ‘A’

 Embarrassed


What is your version of countepartyd? You need to update to the latest version v0.3.

已经升级到最新版了

Try this command:

counterpartyd issuance --source 1xxx --quantity 100 --asset XXXXX --divisible
qwertyasdfgh
Newbie
*
Offline Offline

Activity: 36
Merit: 0


View Profile
February 08, 2014, 05:55:02 AM
 #2523

issuance --source=YOUR_ADDRESS --asset=ASSETNAME --quantity=QUANTITY divisible

Code:
   if asset[0] == 'A': raise exceptions.AssetNameError('starts with ‘A’')
lib.exceptions.AssetNameError: starts with ‘A’

 Embarrassed


What is your version of countepartyd? You need to update to the latest version v0.3.

已经升级到最新版了
You can't have asset names that start with the letter A.
520Bit
Sr. Member
****
Offline Offline

Activity: 602
Merit: 252



View Profile
February 08, 2014, 05:58:26 AM
 #2524

issuance --source=YOUR_ADDRESS --asset=ASSETNAME --quantity=QUANTITY divisible

Code:
   if asset[0] == 'A': raise exceptions.AssetNameError('starts with ‘A’')
lib.exceptions.AssetNameError: starts with ‘A’

 Embarrassed


What is your version of countepartyd? You need to update to the latest version v0.3.

已经升级到最新版了
You can't have asset names that start with the letter A.

Correct. Never put an 'A' in front of any asset! This is prohibited by Counterparty protocol.
supersuber
Member
**
Offline Offline

Activity: 118
Merit: 104


Counterparty


View Profile
February 08, 2014, 06:20:59 AM
 #2525

issuance --source=YOUR_ADDRESS --asset=ASSETNAME --quantity=QUANTITY divisible

Code:
   if asset[0] == 'A': raise exceptions.AssetNameError('starts with ‘A’')
lib.exceptions.AssetNameError: starts with ‘A’

 Embarrassed


What is your version of countepartyd? You need to update to the latest version v0.3.

已经升级到最新版了
You can't have asset names that start with the letter A.

Correct. Never put an 'A' in front of any asset! This is prohibited by Counterparty protocol.

Got it. But why?

mtbitcoin
Legendary
*
Offline Offline

Activity: 876
Merit: 1000


Etherscan.io


View Profile
February 08, 2014, 07:08:00 AM
 #2526

issuance --source=YOUR_ADDRESS --asset=ASSETNAME --quantity=QUANTITY divisible

Code:
   if asset[0] == 'A': raise exceptions.AssetNameError('starts with ‘A’')
lib.exceptions.AssetNameError: starts with ‘A’

 Embarrassed


What is your version of countepartyd? You need to update to the latest version v0.3.

已经升级到最新版了
You can't have asset names that start with the letter A.

Correct. Never put an 'A' in front of any asset! This is prohibited by Counterparty protocol.

Got it. But why?

this was explained somewhere back in the thread. It has to do with how the AssetId is calculated based on the asset names and there are certain requirements for this

EtherScan::Ethereum Block Explorer | BlockScan::Coming Soon
mtbitcoin
Legendary
*
Offline Offline

Activity: 876
Merit: 1000


Etherscan.io


View Profile
February 08, 2014, 07:09:54 AM
 #2527

I have the counterpartyd running fine but now am lost.
When a bid is matched, for example I place a request to buy XCP with and it matches an order to sell XCP.
Is the transaction then completed automatically by counterpartyd or do I need to complete the transaction manually?
You would need to do a 'btcsend' to complete the transaction.

Thank you. And would the seller also need to send the XCP to the buyer manually?
Does the system prevent scammer from taking advantage of the exchange?



If anything the buyers of XCP are the most protected as the seller's XCP coins are locked in (balance deducted) by the protocol and only released upon a matching BTCPAY or expiration


EtherScan::Ethereum Block Explorer | BlockScan::Coming Soon
led_lcd
Sr. Member
****
Offline Offline

Activity: 262
Merit: 250


View Profile
February 08, 2014, 08:12:23 AM
 #2528

Clearly, we need a solution that doesnt require sending all this BTC in an unrecoverable way. I had thought there is a way to extract the BTC used for multisig. Why not make the GUI automate this process of recovering it?

A key part of XCP vs MSC is that XCP has lower fees, so this is a critical issue as far as I am concerned

Is this still a problem with OP_RETURN? Multisig is a fallback until OP_RETURN is available in Bitcoin 0.9.
mtbitcoin
Legendary
*
Offline Offline

Activity: 876
Merit: 1000


Etherscan.io


View Profile
February 08, 2014, 08:22:39 AM
Last edit: February 08, 2014, 08:56:43 AM by mtbitcoin
 #2529

I am seeing orders that are supposed to be matching but not matching??

For instance this order http://blockscan.com/tx.aspx?q=3444 (before it got cancelled) should been matched with http://blockscan.com/tx.aspx?q=3443 , but did not?

another Example

3447 100 XCP 0.006000 BTC/XCP 0.6 BTC

Should have matched with

3443 200 XCP 0.006 BTC/XCP 1.2 BTC


But are not

EtherScan::Ethereum Block Explorer | BlockScan::Coming Soon
520Bit
Sr. Member
****
Offline Offline

Activity: 602
Merit: 252



View Profile
February 08, 2014, 11:59:52 AM
 #2530

Quote from: mtbitcoin link=topic=395761.[code
ms[/code]g5012798#msg5012798 date=1391847759]
I am seeing orders that are supposed to be matching but not matching??

For instance this order http://blockscan.com/tx.aspx?q=3444 (before it got cancelled) should been matched with http://blockscan.com/tx.aspx?q=3443 , but did not?

another Example

3447 100 XCP 0.006000 BTC/XCP 0.6 BTC

Should have matched with

3443 200 XCP 0.006 BTC/XCP 1.2 BTC


But are not


There are two orders not matched. Why?

Code:
Open Orders
+---------------------+------------+---------------+--------------------+------------------+------------------+-----------+------------------------------------------------------------------+
|    Give Quantity    | Give Asset |     Price     |    Price Assets    | Required BTC Fee | Provided BTC Fee | Time Left |                             Tx Hash                              |
+---------------------+------------+---------------+--------------------+------------------+------------------+-----------+------------------------------------------------------------------+
|      0.00000167     |    XCP     |     0.0060    |    BTC/XCP ask     |      0.0001      |      0.0001      |    4999   | 0d8e10c598ea3b07f2cdb8587ae78f900d2f77544c5ec67bde3413ee25a69e84 |
|         0.12        |    BTC     |     0.0060    |    BTC/XCP bid     |       0.0        |      0.0001      |    280    | 08b608caf1354272bd19b92fd782b26af987416f2af4a6fa7b0bc7a6c9af99f3 |

Order Matches Awaiting BTC Payment from You
+------------------+-----------+
| Matched Order ID | Time Left |
+------------------+-----------+
+------------------+-----------+
BitThink
Legendary
*
Offline Offline

Activity: 882
Merit: 1000



View Profile
February 08, 2014, 12:43:02 PM
 #2531

rounding issue?
PhantomPhreak (OP)
Sr. Member
****
Offline Offline

Activity: 476
Merit: 300

Counterparty Chief Scientist and Co-Founder


View Profile
February 08, 2014, 12:43:38 PM
 #2532

Quote from: mtbitcoin link=topic=395761.[code
ms[/code]g5012798#msg5012798 date=1391847759]
I am seeing orders that are supposed to be matching but not matching??

For instance this order http://blockscan.com/tx.aspx?q=3444 (before it got cancelled) should been matched with http://blockscan.com/tx.aspx?q=3443 , but did not?

another Example

3447 100 XCP 0.006000 BTC/XCP 0.6 BTC

Should have matched with

3443 200 XCP 0.006 BTC/XCP 1.2 BTC


But are not


There are two orders not matched. Why?

Code:
Open Orders
+---------------------+------------+---------------+--------------------+------------------+------------------+-----------+------------------------------------------------------------------+
|    Give Quantity    | Give Asset |     Price     |    Price Assets    | Required BTC Fee | Provided BTC Fee | Time Left |                             Tx Hash                              |
+---------------------+------------+---------------+--------------------+------------------+------------------+-----------+------------------------------------------------------------------+
|      0.00000167     |    XCP     |     0.0060    |    BTC/XCP ask     |      0.0001      |      0.0001      |    4999   | 0d8e10c598ea3b07f2cdb8587ae78f900d2f77544c5ec67bde3413ee25a69e84 |
|         0.12        |    BTC     |     0.0060    |    BTC/XCP bid     |       0.0        |      0.0001      |    280    | 08b608caf1354272bd19b92fd782b26af987416f2af4a6fa7b0bc7a6c9af99f3 |

Order Matches Awaiting BTC Payment from You
+------------------+-----------+
| Matched Order ID | Time Left |
+------------------+-----------+
+------------------+-----------+

Because 0.00000167 XCP * 0.006 BTC/XCP = 1 satoshi... It's the finite divisibility of Bitcoin.
PhantomPhreak (OP)
Sr. Member
****
Offline Offline

Activity: 476
Merit: 300

Counterparty Chief Scientist and Co-Founder


View Profile
February 08, 2014, 01:51:29 PM
 #2533

I am seeing orders that are supposed to be matching but not matching??

For instance this order http://blockscan.com/tx.aspx?q=3444 (before it got cancelled) should been matched with http://blockscan.com/tx.aspx?q=3443 , but did not?

another Example

3447 100 XCP 0.006000 BTC/XCP 0.6 BTC

Should have matched with

3443 200 XCP 0.006 BTC/XCP 1.2 BTC


But are not


There was a rounding bug, whose fix will go into effect with block 286000 (which will be in around a week) in a completely backwards-compatible way. The new version is v0.4.
cityglut
Full Member
***
Offline Offline

Activity: 216
Merit: 100


View Profile
February 08, 2014, 02:08:44 PM
 #2534

Just as a warning, SFMSTOCK currently list on DEX was not issued by owner of this company, and does not have evidence of share ownership nor any direct authorization to sell these shares in official capacity. I would advise not to send any XCP or BTC balance to this asset


Thank you very much for this warning.

To both issuers and purchasers of assets: A link to an official website should be provided in the description space for an asset, and on that official website should be a list of each address that has stocks on the Counterparty distributed exchange, as well as the asset name(s) associated with each address.

I will sticky a post on the official forum to the same effect.
PhantomPhreak (OP)
Sr. Member
****
Offline Offline

Activity: 476
Merit: 300

Counterparty Chief Scientist and Co-Founder


View Profile
February 08, 2014, 02:17:14 PM
 #2535

I am seeing orders that are supposed to be matching but not matching??

For instance this order http://blockscan.com/tx.aspx?q=3444 (before it got cancelled) should been matched with http://blockscan.com/tx.aspx?q=3443 , but did not?

another Example

3447 100 XCP 0.006000 BTC/XCP 0.6 BTC

Should have matched with

3443 200 XCP 0.006 BTC/XCP 1.2 BTC


But are not


There was a rounding bug, whose fix will go into effect with block 286000 (which will be in around a week) in a completely backwards-compatible way. The new version is v0.4.

Note: This fix should also handle the overlaps of the bid and the asks in the order book.
520Bit
Sr. Member
****
Offline Offline

Activity: 602
Merit: 252



View Profile
February 08, 2014, 02:30:28 PM
 #2536

I am seeing orders that are supposed to be matching but not matching??

For instance this order http://blockscan.com/tx.aspx?q=3444 (before it got cancelled) should been matched with http://blockscan.com/tx.aspx?q=3443 , but did not?

another Example

3447 100 XCP 0.006000 BTC/XCP 0.6 BTC

Should have matched with

3443 200 XCP 0.006 BTC/XCP 1.2 BTC


But are not


There was a rounding bug, whose fix will go into effect with block 286000 (which will be in around a week) in a completely backwards-compatible way. The new version is v0.4.

Note: This fix should also handle the overlaps of the bid and the asks in the order book.

Is the counterpartyd_build updated accordingly?
mtbitcoin
Legendary
*
Offline Offline

Activity: 876
Merit: 1000


Etherscan.io


View Profile
February 08, 2014, 02:56:50 PM
 #2537

I am seeing orders that are supposed to be matching but not matching??

For instance this order http://blockscan.com/tx.aspx?q=3444 (before it got cancelled) should been matched with http://blockscan.com/tx.aspx?q=3443 , but did not?

another Example

3447 100 XCP 0.006000 BTC/XCP 0.6 BTC

Should have matched with

3443 200 XCP 0.006 BTC/XCP 1.2 BTC


But are not


There was a rounding bug, whose fix will go into effect with block 286000 (which will be in around a week) in a completely backwards-compatible way. The new version is v0.4.

Ok. That makes sense because I checked the DB directly and the figure should have matched

EtherScan::Ethereum Block Explorer | BlockScan::Coming Soon
trilli0n
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
February 08, 2014, 02:59:24 PM
 #2538

ATTN PhantomPhreak - I left you a PM concerning the reimbursement of invalid orders caused by the order matching cq. rounding issue.

Thanks
520Bit
Sr. Member
****
Offline Offline

Activity: 602
Merit: 252



View Profile
February 08, 2014, 03:10:07 PM
Last edit: February 08, 2014, 03:26:19 PM by 520Bit
 #2539

Only the matched seller or buyer could see a matched order in counterpartyd_build, right? I could not see any matched order by typing counterpartyd market command.
520Bit
Sr. Member
****
Offline Offline

Activity: 602
Merit: 252



View Profile
February 08, 2014, 03:45:49 PM
 #2540

I am seeing orders that are supposed to be matching but not matching??

For instance this order http://blockscan.com/tx.aspx?q=3444 (before it got cancelled) should been matched with http://blockscan.com/tx.aspx?q=3443 , but did not?

another Example

3447 100 XCP 0.006000 BTC/XCP 0.6 BTC

Should have matched with

3443 200 XCP 0.006 BTC/XCP 1.2 BTC


But are not


There was a rounding bug, whose fix will go into effect with block 286000 (which will be in around a week) in a completely backwards-compatible way. The new version is v0.4.

Ok. That makes sense because I checked the DB directly and the figure should have matched

Yes, v0.4 looks fine now:

Code:
Order Match: 1E-8 BTC for 0.00000167 XCP at 0.0060 BTC/XCP (0d8e10c598ea3b07f2cdb8587ae78f900d2f77544c5ec67bde3413ee25a69e84e99f02130953b989da98f2d862069d6f6b8b4aa98fc59c457433b96467b8b023)
Order Match: 0.00999999 BTC for 1.50499849 XCP at 0.0066 BTC/XCP (9ce90757c8f8d9c0c3cffb429d01c737cac39ccfc630d783e8812b468c01e76ce99f02130953b989da98f2d862069d6f6b8b4aa98fc59c457433b96467b8b023)
Pages: « 1 ... 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 [127] 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 ... 661 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!