Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread - page 636. (Read 1276928 times)
January 08, 2014, 04:32:58 PM
How is it proven that you can't access the funds at the burn address?
January 08, 2014, 04:23:52 PM
How can I burn a bitcoin for XCP using Electrum? I don't have Bitcoin-qt installed and downloading the fullblockchain will take ages on my internet connection.
Electrum isn't supported (currently). You can use Blockchain.info to burn, however.
Thank you. Reading the guide to burn via Blockchain.info, I think I understand all of the steps and I am going to try a test amount first but what I don't understand is how to claim my XCP after I have burned my BTC?
Can you please explain this?
January 08, 2014, 03:55:34 PM
The explorer seemed to indicate that burns with different inputs or more than one output to non-sending address were invalid. The only definitive confirmation though is to check the counterpatyd client.
PS The explorer seems to be down, last time I checked.
PSS I think it wouldn't be hard to programmatically check every address you get from that table with counterpartyd, and get the burn amount. In fact, an even easier way is to check the counterpartyd logfile, which has a pretty structured log syntax that you can turn into data with a few string commands. Of course this will require running bitcoind and counterpartyd on your remote server.
Example from log file:
PS The explorer seems to be down, last time I checked.
PSS I think it wouldn't be hard to programmatically check every address you get from that table with counterpartyd, and get the burn amount. In fact, an even easier way is to check the counterpartyd logfile, which has a pretty structured log syntax that you can turn into data with a few string commands. Of course this will require running bitcoind and counterpartyd on your remote server.
Example from log file:
Quote
...
2014-01-06-T10:30:27Central Standard Time Block: 278930
2014-01-06-T10:30:27Central Standard Time Burn: 1GSJoRMuFEqtx3e4UjmfZiNonoGrHnt5Wv burned 1.0 BTC for 1443.63636364 XCP (b8a27744…79d741e4)
2014-01-06-T10:30:27Central Standard Time Burn: 146FcHjXUSiJMcYWE7WKPBKSvvCedi2YuA burned 1.0 BTC for 1443.63636364 XCP (e62cd3f0…88fc3542)
2014-01-06-T10:30:27Central Standard Time Burn: 18tJnidmGRi4QxAFmUQgwdQMJm9tRVZotp burned 0.9999 BTC for 1443.492 XCP (cd68e0a1…13c4f575)
2014-01-06-T10:30:27Central Standard Time Burn: 1NULPePYzi8oz6r8D2pgKjfAcJjXQGKasc burned 0.30370714 BTC for 438.4426712 XCP (d29b8039…972e4573)
2014-01-06-T10:30:28Central Standard Time Block: 278931
2014-01-06-T10:30:31Central Standard Time Block: 278932
2014-01-06-T10:30:39Central Standard Time Block: 278933
2014-01-06-T10:30:40Central Standard Time Block: 278934
2014-01-06-T10:30:41Central Standard Time Block: 278935
2014-01-06-T10:30:44Central Standard Time Block: 278936
2014-01-06-T10:30:44Central Standard Time Burn: 1NFga6ZVsrx9wP4uRg6rNzD9drbdz5hbsA burned 0.99909597 BTC for 1441.78631162 XCP (460f00fc…c4605fbc)
2014-01-06-T10:30:44Central Standard Time Burn: 1NDBXUBa1DPbPbxLEA8r8FJufzNdrT9Pb7 burned 0.9941 BTC for 1434.57667273 XCP (93a7209d…b2c95f7f)
2014-01-06-T10:30:46Central Standard Time Block: 278937
2014-01-06-T10:30:47Central Standard Time Block: 278938
...
2014-01-06-T10:30:27Central Standard Time Block: 278930
2014-01-06-T10:30:27Central Standard Time Burn: 1GSJoRMuFEqtx3e4UjmfZiNonoGrHnt5Wv burned 1.0 BTC for 1443.63636364 XCP (b8a27744…79d741e4)
2014-01-06-T10:30:27Central Standard Time Burn: 146FcHjXUSiJMcYWE7WKPBKSvvCedi2YuA burned 1.0 BTC for 1443.63636364 XCP (e62cd3f0…88fc3542)
2014-01-06-T10:30:27Central Standard Time Burn: 18tJnidmGRi4QxAFmUQgwdQMJm9tRVZotp burned 0.9999 BTC for 1443.492 XCP (cd68e0a1…13c4f575)
2014-01-06-T10:30:27Central Standard Time Burn: 1NULPePYzi8oz6r8D2pgKjfAcJjXQGKasc burned 0.30370714 BTC for 438.4426712 XCP (d29b8039…972e4573)
2014-01-06-T10:30:28Central Standard Time Block: 278931
2014-01-06-T10:30:31Central Standard Time Block: 278932
2014-01-06-T10:30:39Central Standard Time Block: 278933
2014-01-06-T10:30:40Central Standard Time Block: 278934
2014-01-06-T10:30:41Central Standard Time Block: 278935
2014-01-06-T10:30:44Central Standard Time Block: 278936
2014-01-06-T10:30:44Central Standard Time Burn: 1NFga6ZVsrx9wP4uRg6rNzD9drbdz5hbsA burned 0.99909597 BTC for 1441.78631162 XCP (460f00fc…c4605fbc)
2014-01-06-T10:30:44Central Standard Time Burn: 1NDBXUBa1DPbPbxLEA8r8FJufzNdrT9Pb7 burned 0.9941 BTC for 1434.57667273 XCP (93a7209d…b2c95f7f)
2014-01-06-T10:30:46Central Standard Time Block: 278937
2014-01-06-T10:30:47Central Standard Time Block: 278938
...
That's all correct, but if you want to do something like that programmatically, the best way is probably to query counterpartyd's JSON-RPC API or access the SQLite3 database directly.
I highly advise querying the JSON RPC API. That is the standard method moving forward to for a 3rd party application to get any information out of counterpartyd. We will be adding documentation around it shortly, but currently, you can see the calls possible from here: https://github.com/PhantomPhreak/counterpartyd/blob/master/lib/api.py
(just call those like you'd call any JSON RPC function, after using a jsonrpc client to connect, similar to bitcoind).
Right now the port, hostname it binds to is hardcoded (this will change shortly). For more information, see https://github.com/PhantomPhreak/counterpartyd/blob/master/lib/api.py#L79
January 08, 2014, 03:50:53 PM
The explorer seemed to indicate that burns with different inputs or more than one output to non-sending address were invalid. The only definitive confirmation though is to check the counterpatyd client.
PS The explorer seems to be down, last time I checked.
PSS I think it wouldn't be hard to programmatically check every address you get from that table with counterpartyd, and get the burn amount. In fact, an even easier way is to check the counterpartyd logfile, which has a pretty structured log syntax that you can turn into data with a few string commands. Of course this will require running bitcoind and counterpartyd on your remote server.
Example from log file:
PS The explorer seems to be down, last time I checked.
PSS I think it wouldn't be hard to programmatically check every address you get from that table with counterpartyd, and get the burn amount. In fact, an even easier way is to check the counterpartyd logfile, which has a pretty structured log syntax that you can turn into data with a few string commands. Of course this will require running bitcoind and counterpartyd on your remote server.
Example from log file:
Quote
...
2014-01-06-T10:30:27Central Standard Time Block: 278930
2014-01-06-T10:30:27Central Standard Time Burn: 1GSJoRMuFEqtx3e4UjmfZiNonoGrHnt5Wv burned 1.0 BTC for 1443.63636364 XCP (b8a27744…79d741e4)
2014-01-06-T10:30:27Central Standard Time Burn: 146FcHjXUSiJMcYWE7WKPBKSvvCedi2YuA burned 1.0 BTC for 1443.63636364 XCP (e62cd3f0…88fc3542)
2014-01-06-T10:30:27Central Standard Time Burn: 18tJnidmGRi4QxAFmUQgwdQMJm9tRVZotp burned 0.9999 BTC for 1443.492 XCP (cd68e0a1…13c4f575)
2014-01-06-T10:30:27Central Standard Time Burn: 1NULPePYzi8oz6r8D2pgKjfAcJjXQGKasc burned 0.30370714 BTC for 438.4426712 XCP (d29b8039…972e4573)
2014-01-06-T10:30:28Central Standard Time Block: 278931
2014-01-06-T10:30:31Central Standard Time Block: 278932
2014-01-06-T10:30:39Central Standard Time Block: 278933
2014-01-06-T10:30:40Central Standard Time Block: 278934
2014-01-06-T10:30:41Central Standard Time Block: 278935
2014-01-06-T10:30:44Central Standard Time Block: 278936
2014-01-06-T10:30:44Central Standard Time Burn: 1NFga6ZVsrx9wP4uRg6rNzD9drbdz5hbsA burned 0.99909597 BTC for 1441.78631162 XCP (460f00fc…c4605fbc)
2014-01-06-T10:30:44Central Standard Time Burn: 1NDBXUBa1DPbPbxLEA8r8FJufzNdrT9Pb7 burned 0.9941 BTC for 1434.57667273 XCP (93a7209d…b2c95f7f)
2014-01-06-T10:30:46Central Standard Time Block: 278937
2014-01-06-T10:30:47Central Standard Time Block: 278938
...
2014-01-06-T10:30:27Central Standard Time Block: 278930
2014-01-06-T10:30:27Central Standard Time Burn: 1GSJoRMuFEqtx3e4UjmfZiNonoGrHnt5Wv burned 1.0 BTC for 1443.63636364 XCP (b8a27744…79d741e4)
2014-01-06-T10:30:27Central Standard Time Burn: 146FcHjXUSiJMcYWE7WKPBKSvvCedi2YuA burned 1.0 BTC for 1443.63636364 XCP (e62cd3f0…88fc3542)
2014-01-06-T10:30:27Central Standard Time Burn: 18tJnidmGRi4QxAFmUQgwdQMJm9tRVZotp burned 0.9999 BTC for 1443.492 XCP (cd68e0a1…13c4f575)
2014-01-06-T10:30:27Central Standard Time Burn: 1NULPePYzi8oz6r8D2pgKjfAcJjXQGKasc burned 0.30370714 BTC for 438.4426712 XCP (d29b8039…972e4573)
2014-01-06-T10:30:28Central Standard Time Block: 278931
2014-01-06-T10:30:31Central Standard Time Block: 278932
2014-01-06-T10:30:39Central Standard Time Block: 278933
2014-01-06-T10:30:40Central Standard Time Block: 278934
2014-01-06-T10:30:41Central Standard Time Block: 278935
2014-01-06-T10:30:44Central Standard Time Block: 278936
2014-01-06-T10:30:44Central Standard Time Burn: 1NFga6ZVsrx9wP4uRg6rNzD9drbdz5hbsA burned 0.99909597 BTC for 1441.78631162 XCP (460f00fc…c4605fbc)
2014-01-06-T10:30:44Central Standard Time Burn: 1NDBXUBa1DPbPbxLEA8r8FJufzNdrT9Pb7 burned 0.9941 BTC for 1434.57667273 XCP (93a7209d…b2c95f7f)
2014-01-06-T10:30:46Central Standard Time Block: 278937
2014-01-06-T10:30:47Central Standard Time Block: 278938
...
That's all correct, but if you want to do something like that programmatically, the best way is probably to query counterpartyd's JSON-RPC API
January 08, 2014, 03:17:06 PM
The explorer seemed to indicate that burns with different inputs or more than one output to non-sending address were invalid. The only definitive confirmation though is to check the counterpatyd client.
PS The explorer seems to be down, last time I checked.
PSS I think it wouldn't be hard to programmatically check every address you get from that table with counterpartyd, and get the burn amount. In fact, an even easier way is to check the counterpartyd logfile, which has a pretty structured log syntax that you can turn into data with a few string commands. Of course this will require running bitcoind and counterpartyd on your remote server.
Example from log file:
PS The explorer seems to be down, last time I checked.
PSS I think it wouldn't be hard to programmatically check every address you get from that table with counterpartyd, and get the burn amount. In fact, an even easier way is to check the counterpartyd logfile, which has a pretty structured log syntax that you can turn into data with a few string commands. Of course this will require running bitcoind and counterpartyd on your remote server.
Example from log file:
Quote
...
2014-01-06-T10:30:27Central Standard Time Block: 278930
2014-01-06-T10:30:27Central Standard Time Burn: 1GSJoRMuFEqtx3e4UjmfZiNonoGrHnt5Wv burned 1.0 BTC for 1443.63636364 XCP (b8a27744…79d741e4)
2014-01-06-T10:30:27Central Standard Time Burn: 146FcHjXUSiJMcYWE7WKPBKSvvCedi2YuA burned 1.0 BTC for 1443.63636364 XCP (e62cd3f0…88fc3542)
2014-01-06-T10:30:27Central Standard Time Burn: 18tJnidmGRi4QxAFmUQgwdQMJm9tRVZotp burned 0.9999 BTC for 1443.492 XCP (cd68e0a1…13c4f575)
2014-01-06-T10:30:27Central Standard Time Burn: 1NULPePYzi8oz6r8D2pgKjfAcJjXQGKasc burned 0.30370714 BTC for 438.4426712 XCP (d29b8039…972e4573)
2014-01-06-T10:30:28Central Standard Time Block: 278931
2014-01-06-T10:30:31Central Standard Time Block: 278932
2014-01-06-T10:30:39Central Standard Time Block: 278933
2014-01-06-T10:30:40Central Standard Time Block: 278934
2014-01-06-T10:30:41Central Standard Time Block: 278935
2014-01-06-T10:30:44Central Standard Time Block: 278936
2014-01-06-T10:30:44Central Standard Time Burn: 1NFga6ZVsrx9wP4uRg6rNzD9drbdz5hbsA burned 0.99909597 BTC for 1441.78631162 XCP (460f00fc…c4605fbc)
2014-01-06-T10:30:44Central Standard Time Burn: 1NDBXUBa1DPbPbxLEA8r8FJufzNdrT9Pb7 burned 0.9941 BTC for 1434.57667273 XCP (93a7209d…b2c95f7f)
2014-01-06-T10:30:46Central Standard Time Block: 278937
2014-01-06-T10:30:47Central Standard Time Block: 278938
...
2014-01-06-T10:30:27Central Standard Time Block: 278930
2014-01-06-T10:30:27Central Standard Time Burn: 1GSJoRMuFEqtx3e4UjmfZiNonoGrHnt5Wv burned 1.0 BTC for 1443.63636364 XCP (b8a27744…79d741e4)
2014-01-06-T10:30:27Central Standard Time Burn: 146FcHjXUSiJMcYWE7WKPBKSvvCedi2YuA burned 1.0 BTC for 1443.63636364 XCP (e62cd3f0…88fc3542)
2014-01-06-T10:30:27Central Standard Time Burn: 18tJnidmGRi4QxAFmUQgwdQMJm9tRVZotp burned 0.9999 BTC for 1443.492 XCP (cd68e0a1…13c4f575)
2014-01-06-T10:30:27Central Standard Time Burn: 1NULPePYzi8oz6r8D2pgKjfAcJjXQGKasc burned 0.30370714 BTC for 438.4426712 XCP (d29b8039…972e4573)
2014-01-06-T10:30:28Central Standard Time Block: 278931
2014-01-06-T10:30:31Central Standard Time Block: 278932
2014-01-06-T10:30:39Central Standard Time Block: 278933
2014-01-06-T10:30:40Central Standard Time Block: 278934
2014-01-06-T10:30:41Central Standard Time Block: 278935
2014-01-06-T10:30:44Central Standard Time Block: 278936
2014-01-06-T10:30:44Central Standard Time Burn: 1NFga6ZVsrx9wP4uRg6rNzD9drbdz5hbsA burned 0.99909597 BTC for 1441.78631162 XCP (460f00fc…c4605fbc)
2014-01-06-T10:30:44Central Standard Time Burn: 1NDBXUBa1DPbPbxLEA8r8FJufzNdrT9Pb7 burned 0.9941 BTC for 1434.57667273 XCP (93a7209d…b2c95f7f)
2014-01-06-T10:30:46Central Standard Time Block: 278937
2014-01-06-T10:30:47Central Standard Time Block: 278938
...
January 08, 2014, 02:50:28 PM
How can I burn a bitcoin for XCP using Electrum? I don't have Bitcoin-qt installed and downloading the fullblockchain will take ages on my internet connection.
Electrum isn't supported (currently). You can use Blockchain.info to burn, however.
January 08, 2014, 02:15:37 PM
How can I burn a bitcoin for XCP using Electrum? I don't have Bitcoin-qt installed and downloading the fullblockchain will take ages on my internet connection.
January 08, 2014, 02:06:25 PM
I think XCP is a very promising project and I think I will do something on it (maybe an counterparty explorer soon).
Nonetheless, I don't think this project is able to give you huge return (more than 10x) like Nxt, so please be warned if you want to be rich over-night.
The reason is simple. Since this is an open-source project, so anyone could replicate it without any cost. They just need to create a new un-spendable address and then there's another XCP-2, XCP-3. Once people find the price of XCP is too high, they can freely goes to XCP-2 and XCP-3.
The smart or sneaky part of Nxt is that they postpone opening their source until the price is already more than 1000x. For master-coin, they have no code at all even at current stage.
Therefore, XCP in my opinion is the most honourable project and it's the project really want to create a decentralized market rather than a be-rich-soon game (the only other one similar is colored-coin).
Any thinking about this is welcome, especially from the developers.
Nonetheless, I don't think this project is able to give you huge return (more than 10x) like Nxt, so please be warned if you want to be rich over-night.
The reason is simple. Since this is an open-source project, so anyone could replicate it without any cost. They just need to create a new un-spendable address and then there's another XCP-2, XCP-3. Once people find the price of XCP is too high, they can freely goes to XCP-2 and XCP-3.
The smart or sneaky part of Nxt is that they postpone opening their source until the price is already more than 1000x. For master-coin, they have no code at all even at current stage.
Therefore, XCP in my opinion is the most honourable project and it's the project really want to create a decentralized market rather than a be-rich-soon game (the only other one similar is colored-coin).
Any thinking about this is welcome, especially from the developers.
Thanks for the kind words!
The Counterparty team makes no promises regarding returns-on -investment. Our goal. moreover, was not to make investors rich overnight, but rather to create a working and relatively full-featured client, and to that extent returns-on-investment were secondary. At the same time, however, I believe that the situation you describe does not preclude XCP significantly increasing in value. Specifically, unless a Counterparty fork offers some real technical improvement, I think that XCP-2, etc. will be minted only when Counterparty has proved itself a financial success. And even if a Counterparty fork does offer technical advantage, the importance of being the first Counterparty must not be forgotten. In my opinion, certain alt-coins offer definite advantages over Bitcoin (e.g. faster block-time), and yet Bitcoin has still increased in value and the alt-coin market has, in my opinion, at least for now, proven itself to be by-and-large a bubble. Nothing suggests to me that the situation wouldn't be same if alt-Counterpartys were to appear.
There're years between bitcoin and its copicats, so bitcoin has enough time to grow. XCP, however, may have only months to be mature enough to secure the first arriver advantage. Nonetheless, I agree with you that there're still considerable upsite for XCP, because people will copy it and will to burn for the copicat only after XCP is successful and the price is high enough.
I'm just saying that the price will not increase as much as Nxt (>1000x) and all investors had better to keep this in mind IMHO.
I suppose this is a good time to announce my intent to borrow some of all of the counterpartyd code and put it in my catbox development tree ( https://bitbucket.org/dahozer/catcoin ) .
I was going to say sandbox, but it's going to be crap until either:
a) I get a consulting/development contract to work on this full time
b) I can make enough offering and trading counterparty commodities futures (I need some buyers who want to take physical delivery of Iowa soybeans)
EDIT: Sorry, I misunderstood.
January 08, 2014, 01:15:31 PM
I think XCP is a very promising project and I think I will do something on it (maybe an counterparty explorer soon).
Nonetheless, I don't think this project is able to give you huge return (more than 10x) like Nxt, so please be warned if you want to be rich over-night.
The reason is simple. Since this is an open-source project, so anyone could replicate it without any cost. They just need to create a new un-spendable address and then there's another XCP-2, XCP-3. Once people find the price of XCP is too high, they can freely goes to XCP-2 and XCP-3.
The smart or sneaky part of Nxt is that they postpone opening their source until the price is already more than 1000x. For master-coin, they have no code at all even at current stage.
Therefore, XCP in my opinion is the most honourable project and it's the project really want to create a decentralized market rather than a be-rich-soon game (the only other one similar is colored-coin).
Any thinking about this is welcome, especially from the developers.
Nonetheless, I don't think this project is able to give you huge return (more than 10x) like Nxt, so please be warned if you want to be rich over-night.
The reason is simple. Since this is an open-source project, so anyone could replicate it without any cost. They just need to create a new un-spendable address and then there's another XCP-2, XCP-3. Once people find the price of XCP is too high, they can freely goes to XCP-2 and XCP-3.
The smart or sneaky part of Nxt is that they postpone opening their source until the price is already more than 1000x. For master-coin, they have no code at all even at current stage.
Therefore, XCP in my opinion is the most honourable project and it's the project really want to create a decentralized market rather than a be-rich-soon game (the only other one similar is colored-coin).
Any thinking about this is welcome, especially from the developers.
Thanks for the kind words!
The Counterparty team makes no promises regarding returns-on -investment. Our goal. moreover, was not to make investors rich overnight, but rather to create a working and relatively full-featured client, and to that extent returns-on-investment were secondary. At the same time, however, I believe that the situation you describe does not preclude XCP significantly increasing in value. Specifically, unless a Counterparty fork offers some real technical improvement, I think that XCP-2, etc. will be minted only when Counterparty has proved itself a financial success. And even if a Counterparty fork does offer technical advantage, the importance of being the first Counterparty must not be forgotten. In my opinion, certain alt-coins offer definite advantages over Bitcoin (e.g. faster block-time), and yet Bitcoin has still increased in value and the alt-coin market has, in my opinion, at least for now, proven itself to be by-and-large a bubble. Nothing suggests to me that the situation wouldn't be same if alt-Counterpartys were to appear.
There're years between bitcoin and its copicats, so bitcoin has enough time to grow. XCP, however, may have only months to be mature enough to secure the first arriver advantage. Nonetheless, I agree with you that there're still considerable upsite for XCP, because people will copy it and will to burn for the copicat only after XCP is successful and the price is high enough.
I'm just saying that the price will not increase as much as Nxt (>1000x) and all investors had better to keep this in mind IMHO.
I suppose this is a good time to announce my intent to borrow some of all of the counterpartyd code and put it in my catbox development tree ( https://bitbucket.org/dahozer/catcoin ) .
I was going to say sandbox, but it's going to be crap until either:
a) I get a consulting/development contract to work on this full time
b) I can make enough offering and trading counterparty commodities futures (I need some buyers who want to take physical delivery of Iowa soybeans)
January 08, 2014, 12:37:51 PM
Can feeds or bets _automatically_ reference the price of an asset in open orders or last trade?
Hey guys even i'm curious about this...can the devs clarify this? thx
No, they cannot. The values of feeds are, as it were, manually chosen, and bets are made only on feeds. Of course, you can script counterpartyd to do whatever you want here.
January 08, 2014, 12:32:10 PM
Can feeds or bets _automatically_ reference the price of an asset in open orders or last trade?
Hey guys even i'm curious about this...can the devs clarify this? thx
January 08, 2014, 10:11:50 AM
Win8, using windows installer. Two days ago my 1BTC was burned somehow(spent a few days reading forum doing something). Today after reinstall last version of counterpartyd try to burn from other address same wallet on same PC got following error:
What is it and how to fix it?
Code:
C:\Program Files\counterpartyd>counterpartyd burn --from MY2NDADDSAMEWALLET --quantity 1.00
Confirm? (y/N) y
Traceback (most recent call last):
File "C:\Python33\lib\site-packages\cx_Freeze\initscripts\Console3.py", line 2
7, in
File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 511, i
n
File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 260, in
transmit
File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 64, in r
pc
lib.exceptions.BitcoindError: {'message': 'TX rejected', 'code': -22}
C:\Program Files\counterpartyd>
Confirm? (y/N) y
Traceback (most recent call last):
File "C:\Python33\lib\site-packages\cx_Freeze\initscripts\Console3.py", line 2
7, in
File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 511, i
n
File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 260, in
transmit
File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 64, in r
pc
lib.exceptions.BitcoindError: {'message': 'TX rejected', 'code': -22}
C:\Program Files\counterpartyd>
What is it and how to fix it?
https://bitcointalksearch.org/topic/error-umessage-utx-rejected-ucode-22-307079
or http://www.google.com/search?q=bitcoind+tx+rejected+code+22
Make sure you're not trying to burn freshly minted/deposited coins that don't have at least a few confirms.
January 08, 2014, 10:04:52 AM
Win8, using windows installer. Two days ago my 1BTC was burned somehow(spent a few days reading forum doing something). Today after reinstall last version of counterpartyd try to burn from other address same wallet on same PC got following error:
What is it and how to fix it?
Code:
C:\Program Files\counterpartyd>counterpartyd burn --from MY2NDADDSAMEWALLET --quantity 1.00
Confirm? (y/N) y
Traceback (most recent call last):
File "C:\Python33\lib\site-packages\cx_Freeze\initscripts\Console3.py", line 2
7, in
File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 511, i
n
File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 260, in
transmit
File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 64, in r
pc
lib.exceptions.BitcoindError: {'message': 'TX rejected', 'code': -22}
C:\Program Files\counterpartyd>
Confirm? (y/N) y
Traceback (most recent call last):
File "C:\Python33\lib\site-packages\cx_Freeze\initscripts\Console3.py", line 2
7, in
File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 511, i
n
File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 260, in
transmit
File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 64, in r
pc
lib.exceptions.BitcoindError: {'message': 'TX rejected', 'code': -22}
C:\Program Files\counterpartyd>
What is it and how to fix it?
January 08, 2014, 09:23:49 AM
New dep on python-werkzeug?
Which version should we use?
Which version should we use?
The build system was updated yesterday or the night before to deal with these dependencies. If you're using the build system, just rerun setup.py (as if you're redoing that part in Building from Source).
If you just want to see the version of the dependency we're using, check out: https://github.com/xnova/counterpartyd_build/blob/master/dist/reqs.txt
EDIT: I have also updated the docs to mention that rerunning setup.py is possible:
http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.html#updating-to-the-newest-source
January 08, 2014, 07:32:35 AM
New dep on python-werkzeug?
Which version should we use?
Which version should we use?
January 08, 2014, 07:12:46 AM
Another bug report
Quote
Traceback (most recent call last):
File "./counterpartyd.py", line 465, in
deadline = round(datetime.timestamp(dateutil.parser.parse(args.deadline)))
AttributeError: type object 'datetime.datetime' has no attribute 'timestamp'
File "./counterpartyd.py", line 465, in
deadline = round(datetime.timestamp(dateutil.parser.parse(args.deadline)))
AttributeError: type object 'datetime.datetime' has no attribute 'timestamp'
Hmm. What version of datetime do you have?
python3-dateutil_2.0+dfsg1-1_all.deb (debian7)
January 08, 2014, 07:04:57 AM
Looks like the code was updated to allow multiple inputs up 1, and to burn at least 1 on an overburn.
The rule has always been that all of the inputs sources have to be identical, and their number doesn't matter.
The overburn rule is new, however, yes.
January 08, 2014, 02:02:38 AM
Looks like the code was updated to allow multiple inputs up 1, and to burn at least 1 on an overburn.
January 08, 2014, 01:38:37 AM
Anyone who was having "codemap"/unicode display issues, please pull the newest counterpartyd from git and let us know if you're still experiencing issues.
We had several unicode characters in the code that were causing the Windows terminal (which cannot properly display unicode from what my research told me) to choke. This has been fixed:
https://github.com/PhantomPhreak/counterpartyd/commit/e7497296b6c1409b3108bca3818dc1b89a452007
LeoC: Also, you are running an older version of counterparty if you are using the installer. I have just pushed up a new version of the installer based off of the latest commit to https://github.com/xnova/counterpartyd_binaries
Try reinstalling using that installer (or just use the source for now as we are regulary making changes to counterpartyd)
We had several unicode characters in the code that were causing the Windows terminal (which cannot properly display unicode from what my research told me) to choke. This has been fixed:
https://github.com/PhantomPhreak/counterpartyd/commit/e7497296b6c1409b3108bca3818dc1b89a452007
LeoC: Also, you are running an older version of counterparty if you are using the installer. I have just pushed up a new version of the installer based off of the latest commit to https://github.com/xnova/counterpartyd_binaries
Try reinstalling using that installer (or just use the source for now as we are regulary making changes to counterpartyd)
I am still running into the issues after updating to the latest git
--
File "C:\counterpartyd_build\env\lib\encodings\cp437.py", line 19, in encode
return codecs.charmap_encode(input,self.errors,encoding_map)[0]
UnicodeEncodeError: 'charmap' codec can't encode character '\u2026' in position 259: character maps to
January 08, 2014, 12:50:35 AM
Your BTC and XCP values seem to be a multiple of 6 higher than expected. After all each address can't have more than 1 BTC / 1500 XCP.
Quote
Also I see a lot of unfortunate people that messed up the burn. This is why you do a test burn, people.
Particularly it's the multiple inputs part that seems to be a problem. The tutorial should emphasize that multiple inputs are NOT accepted.
Particularly it's the multiple inputs part that seems to be a problem. The tutorial should emphasize that multiple inputs are NOT accepted.
I'm not sure multiple inputs are not accepted yet. It requires the confirmation of the developers. The developers could relax the condition so that those BTCs are not wasted.
I've relaxed the condition to only invalidate those with multiple input addresses. If there're multiple inputs with same address, it is treated as valid now. Now almost all transactions are valid now except there's one address burnt slightly over 1 BTC.
Jump to: