It's pretty obvious from a cursory glance that the devs have at least 4 BTC invested in this project, if not more. Also, they do have a donation address if you feel inclined to contribute to bounties...
If I had to take a guess, I would say more like close to at least 20 BTC invested  |
|
|
|
You can check for confirmed XCP balances at http://blockscan.com. Just enter your BTC address in the search box. |
|
|
|
405.22870838 BTC https://blockchain.info/address/1CounterpartyXXXXXXXXXXXXXXXUWLpVr?offset=0&filter=0¤cy=BTC
403.99070000 BTC http://www.blockscan.com/default.aspx
404.02770838 BTC = my calculus 405.22870838 - 0.5 - 0.7 - 0.001 (which mean that if blockscan.com is correct, additional unspotted ~0.037 BTC burn failed) Just for clarification ... The data from BlockScan only includes all confirmed transactions as per the Counterparty client. So unless the Counterparty client burn transactions database is incorrect this is what is recorded by the official client |
|
|
|
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. Yes, it does look like that is what is happening. Therefore the safest solution as far as the QT client is concerned, is to do a "full" burn from a "NEW" wallet which you have newly funded to a single address. However, after the first burn any remaining balance could get allocated to a different change address. The QT client lacks coin control at the moment. |
|
|
|
That's not a Counterparty transaction, though both it and Counterparty use OP_RETURN. Ok, but the Couterparty client is logging the transaction in the sqlite transaction table. So it does look like the client is logging all transactions with an OP_RETURN? Cheers |
|
|
|
I am seeing a first non burn message in the transaction logs DB (tx_index = 423) with the message data "Hello world, @maraoz was here!!!" Any idea how did that get in? Looks like spam  |
|
|
|
Newbie into XCP, so I have some questions:
Do I need to run Counterpartyd 24/7 to keep alive for the network?
If I burn the coins, will I get XCP right now or after the burning period? Will XCP be hardcoded by the creator after burning period ends? If not, can I change the parameter in the python code for XCP rewarding to get more XCP?
Thanks.
1. No 2. You will get them now after 1 block confirmation |
|
|
|
Where is that "Network protection scheme" when you actually need one |
|
|
|
Hi Just as a heads up.. I started working on a XCP CounterParty block explorer shortly after the project was publicly posted, and I would like to announce that I have a live beta version available at http://www.blockscan.comThere is some basic search functionality to allow you to look up your block balance easily and also to see the transaction history for burned blocks. At the moment this only included confirmed blocks as per the CounterParty client If you have any suggestions, feedback or bug reports do let me know. Cheers Very cool site. Much better than my version.  I think I really need to squeeze some time to learn bootstrap. Thank you I wasn't aware you were working on a block explorer too or I might have given this a pass But I had already started this earlier and it was a good opportunity to play with bootstrap. Anyway it's always good to have alternate sites and backups Cheers |
|
|
|
Noted.. I've renamed the thread a bit I did make a post on the official thread but I think it got buried a bit |
|
|
|
Hi Blockscan.com is a Counterparty Block Explorer built from scratch for the sole purpose of looking up any Counterparty related transactions. The block explorer was developed and is maintained independently In addition to the block explorer functionality, there is also an account services module where you can perform additional functions such as setting up email alerts (to alert you when you receive tokens at your address) and or updating/adding additional blockscan metadata information for your assets. The official site is available at http://www.blockscan.com and can also be accessed via https://www.blockscan.comIf you have any suggestions, feedback or bug reports do let us know by posting here. We can also be contacted via http://www.blockscan.com/contact for matters relating to blockscan only Cheers <Edited> |
|
|
|
Hi Just as a heads up.. I started working on a XCP CounterParty block explorer shortly after the project was publicly posted, and I would like to announce that I have a live beta version available at http://www.blockscan.comThere is some basic search functionality to allow you to look up your block balance easily and also to see the transaction history for burned blocks. At the moment this only included confirmed blocks as per the CounterParty client If you have any suggestions, feedback or bug reports do let me know. Cheers |
|
|
|
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/e7497296b6c1409b3108bca3818dc1b89a452007LeoC: 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_binariesTry 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 <u ndefined> |
|
|
|
Thank you. Are there any special parameters that need to be included. I've got this up and running however, I am not entirely sure if its running correctly. Solo mining I am getting the "New block detected on network" every 1-2 seconds and there does not appear to be any load on the CPU. Cheers |
|
|
|
Will the mining work with GPUs instead of Asics?
yes, you should use the modified bfgminer. Thank you. Do you know if there are any compiled binaries for the modified bfgminer ? not at the moment; but we can prepare them. for what platform do you need them? Windows please. Thank you! |
|
|
|
Will the mining work with GPUs instead of Asics?
yes, you should use the modified bfgminer. Thank you. Do you know if there are any compiled binaries for the modified bfgminer ? |
|
|
|
|
Small suggestion here... One of the things that need to be fixed is to recompile the qqminer to a build that does not throw so many virus alerts when using virus total for the scan
Cheers
|
|
|
|
|
Will the mining work with GPUs instead of Asics?
|
|
|
|
|
Show Posts
