Is there any solid guide how to send some funds, without risking loosing them?
Btw, is BitcoinQT the only way to burn, any plans for a web-wallet support?
Thanks
. 
Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread - page 631. (Read 1276928 times)
January 10, 2014, 09:35:11 PM
Hi,
Is there any solid guide how to send some funds, without risking loosing them?
Btw, is BitcoinQT the only way to burn, any plans for a web-wallet support?
Thanks.
Is there any solid guide how to send some funds, without risking loosing them?
Btw, is BitcoinQT the only way to burn, any plans for a web-wallet support?
Thanks
. January 10, 2014, 09:13:19 PM
I have a noob question, I burn some BTC through blockchain.info, how can i claim my XCP and is it possible to claim it after the burn period has ended?
Perhaps we may need to wait until wallet will be released. Months? /Years? 
The wallet software has already been released...
There's no need to 'claim' XCP that you earn through burning: it is automatically credited to your address.
Is it fully functional? May I download it?
The wallet he's referring to is counterpartyd itself. It is command line for now, but GUI and/or web wallets (which will work on top of counterpartyd) will be forthcoming at some point in the future.
January 10, 2014, 09:09:29 PM
@PhantomPhreak
Hello,when I saw your XCP,I was surprised to find that it's characterized is very similar to my previous thoughts.
This is my postings at December 26.
https://bitcointalksearch.org/topic/m.4154105
Maybe a coincidence?
January 10, 2014, 07:29:27 PM
I have a noob question, I burn some BTC through blockchain.info, how can i claim my XCP and is it possible to claim it after the burn period has ended?
Perhaps we may need to wait until wallet will be released. Months? /Years? The wallet software has already been released...
There's no need to 'claim' XCP that you earn through burning: it is automatically credited to your address.
Is it fully functional? May I download it?
January 10, 2014, 07:16:52 PM
PhantomPhreak don't you think its important to have "reward XCP" to be able to pay developers?
for example in the case of MSC: 10% of the total 619478 MSC are "reward mastercoins" granted to the MasterCoin foundation over the years following launch. The formula for percent vested is: 1-(0.5^y) where y is the number of years since launch, including partial years.
for example in the case of MSC: 10% of the total 619478 MSC are "reward mastercoins" granted to the MasterCoin foundation over the years following launch. The formula for percent vested is: 1-(0.5^y) where y is the number of years since launch, including partial years.
January 10, 2014, 07:12:10 PM
For comparison, mastercoin issued 563,162.
The initial value for mastercoins came out of the fundraiser "anchoring". People were willing to "sacrifice" 1 BTC in exchange for about 100 MSC, so it anchored the initial value of MSC in at least 0.01 BTC per MSC.
XCP has the initial value of 0.001 BTC per XCP
January 10, 2014, 07:02:41 PM
I have a noob question, I burn some BTC through blockchain.info, how can i claim my XCP and is it possible to claim it after the burn period has ended?
Perhaps we may need to wait until wallet will be released. Months? /Years? The wallet software has already been released...
There's no need to 'claim' XCP that you earn through burning: it is automatically credited to your address.
Yep just to clarify, i read in the thread about claiming XCP. Thanks
January 10, 2014, 06:46:51 PM
I have a noob question, I burn some BTC through blockchain.info, how can i claim my XCP and is it possible to claim it after the burn period has ended?
Perhaps we may need to wait until wallet will be released. Months? /Years? The wallet software has already been released...
There's no need to 'claim' XCP that you earn through burning: it is automatically credited to your address.
January 10, 2014, 06:13:48 PM
I have a noob question, I burn some BTC through blockchain.info, how can i claim my XCP and is it possible to claim it after the burn period has ended?
Perhaps we may need to wait until wallet will be released. Months? /Years? January 10, 2014, 05:17:23 PM
I have a noob question, I burn some BTC through blockchain.info, how can i claim my XCP and is it possible to claim it after the burn period has ended?
January 10, 2014, 04:48:59 PM
For comparison, mastercoin issued 563,162.
Btw what became bitcoins sent for mastercoin funding ? January 10, 2014, 04:21:51 PM
For comparison, mastercoin issued 563,162.
January 10, 2014, 04:20:25 PM
answering my own question:
Asset Name: XCP
Asset ID: 1
Total Issued: 653967.10719604
Divisible: True
Issuer: None
Asset Name: XCP
Asset ID: 1
Total Issued: 653967.10719604
Divisible: True
Issuer: None
so how many XCP total issued so far?
January 10, 2014, 03:13:14 PM
so how many XCP total issued so far?
January 10, 2014, 01:10:48 PM
ok i figured it out... on this new laptop i had file extensions hidden so bitcoin.conf was actually bitcoin.conf.conf
i knew i did something dumb ... thanks for the help
i knew i did something dumb ... thanks for the help
January 10, 2014, 01:00:28 PM
Still couldnt getting run.py to work properly so I am now trying the beta installer, but once again I get an error:
C:\Users\Leo>"C:\Program Files\counterpartyd\counterpartyd.exe"
Could not connect to Bitcoind. Sleeping for five seconds. (Try 0/12)
Bitcoin.conf
rpcuser=rpc
rpcpassword=XXXX
server=1
daemon=1
txindex=1
Counterpartyd.conf
[Default]
rpc-connect=localhost
rpc-port=18832
rpc-user=rpc
rpc-password=XXXX
Tried port 18832 and 8332, same error. I'm getting really close to just giving up
C:\Users\Leo>"C:\Program Files\counterpartyd\counterpartyd.exe"
Could not connect to Bitcoind. Sleeping for five seconds. (Try 0/12)
Bitcoin.conf
rpcuser=rpc
rpcpassword=XXXX
server=1
daemon=1
txindex=1
Counterpartyd.conf
[Default]
rpc-connect=localhost
rpc-port=18832
rpc-user=rpc
rpc-password=XXXX
Tried port 18832 and 8332, same error. I'm getting really close to just giving up
With that bitcoin.conf configuration, your bitcoin server listens on port 8332. Worse case, edit bitcoind.conf, and add the following lines:
Code:
rpcport=8332
port=8333
So given that, that you are not running on testnet, your counterpartyd.conf is configured to listen on the wrong port. With your specified bitcoin.conf file, "rpc-port" in counterpartyd.conf should be "rpc-port=8332", NOT "rpc-port=18832".
Please make those changes, restart both bitcoind/bitcoin-qt and counterpartyd, and let us know if that fixes it.
konfet: Your issue is probably pretty similar to this. Please verify these port numbers, as well as verifying that your bitcoind/bitcoin-qt is actually running, and listening (you can open up a DOS window and run "netstat -an" then search through the list of ports...see if you see those bitcoind ports.
I tried this and it is still not connecting. when i run netstat -an i get 8333 showing up but not 8332. any ideas what I might be doing wrong??
Can you post up your bitcoin.conf? Also, if all else fails, try messing with the values of rpcport and port in bitcoin.conf and see how it's reflected in netstat -an.
Important note: In the latest versions of counterpartyd, the rpc-host, rpc-port, etc parameters have changed. Please view the most up to date documentation on this at http://counterpartyd-build.readthedocs.org/en/latest/AdditionalTopics.html#editing-the-config
bitcoin.conf
Code:
rpcport=8332
rpcconnect=localhost
rpcuser=rpc
rpcpassword=XXX
server=1
daemon=1
txindex=1
testnet=0
counterpartyd.conf
Code:
[Default]
rpc-connect=localhost
rpc-port=8332
rpc-user=rpc
rpc-password=XXX
i am just running bitcoin-qt without any special commands on win8. i know i can get this to work on linux but each time i have tried this on windows machines i just can never get rpc to work. so i probably am doing something really stupid.
January 10, 2014, 12:54:37 PM
Still couldnt getting run.py to work properly so I am now trying the beta installer, but once again I get an error:
C:\Users\Leo>"C:\Program Files\counterpartyd\counterpartyd.exe"
Could not connect to Bitcoind. Sleeping for five seconds. (Try 0/12)
Bitcoin.conf
rpcuser=rpc
rpcpassword=XXXX
server=1
daemon=1
txindex=1
Counterpartyd.conf
[Default]
rpc-connect=localhost
rpc-port=18832
rpc-user=rpc
rpc-password=XXXX
Tried port 18832 and 8332, same error. I'm getting really close to just giving up
C:\Users\Leo>"C:\Program Files\counterpartyd\counterpartyd.exe"
Could not connect to Bitcoind. Sleeping for five seconds. (Try 0/12)
Bitcoin.conf
rpcuser=rpc
rpcpassword=XXXX
server=1
daemon=1
txindex=1
Counterpartyd.conf
[Default]
rpc-connect=localhost
rpc-port=18832
rpc-user=rpc
rpc-password=XXXX
Tried port 18832 and 8332, same error. I'm getting really close to just giving up
With that bitcoin.conf configuration, your bitcoin server listens on port 8332. Worse case, edit bitcoind.conf, and add the following lines:
Code:
rpcport=8332
port=8333
So given that, that you are not running on testnet, your counterpartyd.conf is configured to listen on the wrong port. With your specified bitcoin.conf file, "rpc-port" in counterpartyd.conf should be "rpc-port=8332", NOT "rpc-port=18832".
Please make those changes, restart both bitcoind/bitcoin-qt and counterpartyd, and let us know if that fixes it.
konfet: Your issue is probably pretty similar to this. Please verify these port numbers, as well as verifying that your bitcoind/bitcoin-qt is actually running, and listening (you can open up a DOS window and run "netstat -an" then search through the list of ports...see if you see those bitcoind ports.
I tried this and it is still not connecting. when i run netstat -an i get 8333 showing up but not 8332. any ideas what I might be doing wrong??
Can you post up your bitcoin.conf? Also, if all else fails, try messing with the values of rpcport and port in bitcoin.conf and see how it's reflected in netstat -an.
Important note: In the latest versions of counterpartyd (on git), the rpc-host, rpc-port, etc parameters have changed. Please view the most up to date documentation on this at http://counterpartyd-build.readthedocs.org/en/latest/AdditionalTopics.html#editing-the-config
January 10, 2014, 12:07:21 PM
Still couldnt getting run.py to work properly so I am now trying the beta installer, but once again I get an error:
C:\Users\Leo>"C:\Program Files\counterpartyd\counterpartyd.exe"
Could not connect to Bitcoind. Sleeping for five seconds. (Try 0/12)
Bitcoin.conf
rpcuser=rpc
rpcpassword=XXXX
server=1
daemon=1
txindex=1
Counterpartyd.conf
[Default]
rpc-connect=localhost
rpc-port=18832
rpc-user=rpc
rpc-password=XXXX
Tried port 18832 and 8332, same error. I'm getting really close to just giving up
C:\Users\Leo>"C:\Program Files\counterpartyd\counterpartyd.exe"
Could not connect to Bitcoind. Sleeping for five seconds. (Try 0/12)
Bitcoin.conf
rpcuser=rpc
rpcpassword=XXXX
server=1
daemon=1
txindex=1
Counterpartyd.conf
[Default]
rpc-connect=localhost
rpc-port=18832
rpc-user=rpc
rpc-password=XXXX
Tried port 18832 and 8332, same error. I'm getting really close to just giving up
With that bitcoin.conf configuration, your bitcoin server listens on port 8332. Worse case, edit bitcoind.conf, and add the following lines:
Code:
rpcport=8332
port=8333
So given that, that you are not running on testnet, your counterpartyd.conf is configured to listen on the wrong port. With your specified bitcoin.conf file, "rpc-port" in counterpartyd.conf should be "rpc-port=8332", NOT "rpc-port=18832".
Please make those changes, restart both bitcoind/bitcoin-qt and counterpartyd, and let us know if that fixes it.
konfet: Your issue is probably pretty similar to this. Please verify these port numbers, as well as verifying that your bitcoind/bitcoin-qt is actually running, and listening (you can open up a DOS window and run "netstat -an" then search through the list of ports...see if you see those bitcoind ports.
I tried this and it is still not connecting. when i run netstat -an i get 8333 showing up but not 8332. any ideas what I might be doing wrong??
January 10, 2014, 09:53:12 AM
https://blockchain.info/tx/9615ea60603430587f67a82f4bf62eaa1a4cae4a156807cb62b7ccaaab3ba4f9
Another invalid transaction with 0.5 BTC !
Attention:
Please stop burning from a wallet with multiple addresses !!!!!!
PhantomPhreak:
I really think it's better to credit the XCP to the first input address. This will not cause any serious issue (at most adding 2 to 3 lines of code) in my opinion.
Another invalid transaction with 0.5 BTC !
Attention:
Please stop burning from a wallet with multiple addresses !!!!!!
PhantomPhreak:
I really think it's better to credit the XCP to the first input address. This will not cause any serious issue (at most adding 2 to 3 lines of code) in my opinion.
Does this happen only sometimes? Beacause i did burn from multiple addresses from the same wallet and the burn seem to go through fine and I was able to verify the xcp balance on those addresses as well.
Yes, it only happens when the client combine two previous outputs of two different addresses. It usually happens when there's no enough BTC in any single addresses.
Take the above transaction as an example. Because both addresses have less than 0.5 BTC, but the user wanted to burn 0.5 BTC, so the client has to combine previous outputs in two addresses.
Normally, the client only shows the sum of all its addresses, so it's not so easy to know when the client will combine inputs from the different addresses. Therefore, the safest solution is to only burn from a wallet with only one address.
got it
January 10, 2014, 09:28:37 AM
@PhantomPhreak
Hello,when I saw your XCP,I was surprised to find that it's characterized is very similar to my previous thoughts.
This is my postings at December 26.
https://bitcointalksearch.org/topic/m.4154105
Maybe a coincidence?
Jump to: