The way the virtualEnv is created in windows seems to be kind of funky. For example I had to add Pythonpath for pretty table and appdirs in the counterparty.py as it did not want to find them. Also what's the meaning of this code (under def setup_startup) for windows: runcmd("sudo cp -a %s/linux/init/counterpartyd.conf.template /etc/init/counterpartyd.conf" % paths['dist_path'])
runcmd("sudo sed -r -i -e \"s/!RUN_AS_USER!/%s/g\" /etc/init/counterpartyd.conf" % run_as_user) You shouldn't have had to do that. If you just run setup.py on Windows, it should do everything from you. How are you trying to run counterpartyd.py (directly, or using the run.py script?) If using the build system, you should use run.py. If not, you'll have to install the deps manually, but you can run ./counterpartyd.py directly. I could change this in the future to install the python dependencies to the global python directory (instead of making its own virtualenv), but at that point I'm messing with people's python installs, which could conflict with other libraries, etc they may have installed, so I'd rather not do that. The meaning of those lines you pasted is to take a template config file, and replace the string !RUN_AS_USER! with the actual username that the counterpartyd daemon will be run as (since we don't know that beforehand, and we need to supply that into in the upstart Linux script). |
|
|
|
Assuming that I have follow the step of Installing for Windows there : http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.htmlThen what exactly should I do to running it? In the first post you say : Assuming that you are running Bitcoind locally, run the following command in the downloaded project directory, replacing 'PASSWORD' with RPC password used by Bitcoind:
./counterpartyd.py --testnet --rpc-password=PASSWORD server
For more information, e.g. about how to use a configuration file with counterpartyd, see the README. And here ( http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.html) you say : After installing, open a command window and run counterpartyd in the foreground via:
cd C:\counterpartyd_build
C:\Python33\python.exe run.py --log-file=-
You can then run any of counterpartyd’s other functions, like the examples listed here.
To run the counterpartyd testsuite:
cd C:\counterpartyd_build
run.py tests Yeah, if you use the build system, then you will run via the run.py script.... so, for instance, instead of running: ./counterpartyd.py --testnet --rpc-password=PASSWORD server You would run: C:\Python33\python.exe run.py --testnet server (This assumes you have a counterpartyd.conf file setup with an rpc-password specified in it. If not, or if you want to specify your password explicitly, you can just do: C:\Python33\python.exe run.py --testnet --rpc-password=PASSWORD server The run.py script basically just runs counterpartyd.py in a dedicated python virtual environment, which has all the libraries at all the versions necessary (to keep things consistent), and is written to work on multiple platforms. So basically, you just use that run.py script, and pass in whatever args you need to (which are automatically passed to counterpartyd.py). |
|
|
|
Are you discounting the reward of just the building and using counterparty.
If your endeavor can make use of it, having a few weeks head start on that can be worth more than +50%
50% seemed like a good balance to us. Other similar projects had used 40%, for instance, and we wanted to find a mix that rewarded early adopters (and people that got counterpartyd running/working and were helping us out through the alpha/beta process), while avoiding a situation of having excessive early rewards that would unfairly benefit any "project insiders" or "highly technical opportunists" over those of the general community, as well as hopefully eliminating any kind of "instamine"/"scam" type feeling to this. Could you please elaborate on what uses I could have for this during these few weeks? Maybe I don't fully understand the project. Honestly 50% (45% now) of a bonus is not worth the risk and time value of money for me to invest now rather than 25 days later; but if there is some value in having these earlier I'd be happy to "buy" in. Edit: and I just want to make clear I'm not asking to be convinced or sold on this idea; I like the project and I know you have nothing to gain by getting me in. Just trying to understand and make a smart financial decision. I totally understand what you're saying. The value in getting involved now is I think more technical than purely financial. Our current focus is on establishing the base technology footprint and vetting it through the community (giving input, finding bugs, etc). For those that are willing to spend the time (in getting counterpartyd up and running, etc) and take the risk of investing earlier, the 50% max bonus was to motivate them. They also benefit from being first to adopt this technology, which they can then (hopefully) start to build neat applications on, and be first to market/introduce these apps. In your case, if you would rather wait until the end of the period to invest (either to mitigate the risk as much as possible, which makes sense, or, because you think you can make more money than the benefit of the 50% you would receive here in that time), then that's no problem. At the end of the day, we want each person to make the investment decisions they are personally comfortable with. Thanks for your interest and your support of the project. |
|
|
|
If I may, I do think the intent was to release a working protocol and to encourage people to use it -and Not to create something where someone who was watching the forums more intently, or was tipped off as an insider for example, could get in to merely multiply their money at the expense of others.
I am aware that most people browsing alt-currency forums may very well be people looking to "make money out of thin air" if you will, on account of being early investors in something (having missed the early investment into bitcoin per say), without much caring as to what something does, or whether it offers any kind of potential benefit to others, or mankind at large. While this approach may in fact make a select number of people rich, nevertheless I think it is ultimately detrimental to the acceptance and development of digital monetization and finance in the broader sense.
I understand what you are saying but disagree. I'm not looking for a quick 100,000% profit; just a smart investment in a good vehicle. But, what is the incentive for me to invest right now as opposed to 3 weeks from now? 1,470 XCP instead of 1,000? As days and weeks pass, theoretically the risk will go down exponentially. Why should the reward remain largely the same? Are you discounting the reward of just the building and using counterparty. If your endeavor can make use of it, having a few weeks head start on that can be worth more than +50% 50% seemed like a good balance to us. Other similar projects had used 40%, for instance, and we wanted to find a mix that rewarded early adopters (and people that got counterpartyd running/working and were helping us out through the alpha/beta process), while avoiding a situation of having excessive early rewards that would unfairly benefit any "project insiders" or "highly technical opportunists" over those of the general community, as well as hopefully eliminating any kind of "instamine"/"scam" type feeling to this. |
|
|
|
If I see this does it mean it's working now:
2014-01-04-T11:34:11Pacific Standard Time Burn: 12ZhgyXFYvWRtpwEAV3t8thgTto2yMM5
R6 burned 1.0 BTC for 1465.54545455 XCP (86f56382\u20268ec50a9d)
2014-01-04-T11:34:11Pacific Standard Time Block: 278690
2014-01-04-T11:34:11Pacific Standard Time Burn: 17LntpaSiQL4pa8moojZGRqe8nLsjibZ
fm burned 0.9999 BTC for 1465.308 XCP (d3cce6dd\u20262f95e3ab)
2014-01-04-T11:34:11Pacific Standard Time Burn: 16nUhvJJZifpdWyqni13AWQwm6GGrAci
bp burned 0.9999 BTC for 1465.308 XCP (a8656bb4\u20268b8c621b)
2014-01-04-T11:34:11Pacific Standard Time Burn: 1CNqtdhXUVBgHdPanpUJZd2osFiYSCYY
cR burned 0.99990499 BTC for 1465.31531262 XCP (26f84ab6\u20261088643a)
2014-01-04-T11:34:11Pacific Standard Time Burn: 1CVEtRWVfx7fovcUK94DJB6Vwz7MdkdY
d1 burned 0.99990499 BTC for 1465.31531262 XCP (49f786b0\u20269c50d383)
2014-01-04-T11:34:11Pacific Standard Time Block: 278691
2014-01-04-T11:34:11Pacific Standard Time Burn: 1AKVdmoAUwcdSjwjTiamcUneDNTF1WvW
CE burned 1.0 BTC for 1465.36363636 XCP (0e0decaf\u2026d53d7d2c)
2014-01-04-T11:34:11Pacific Standard Time Burn: 1h9GvFNK3Ccn2Au8C8BHPeaUamQgArvg
K burned 1.0 BTC for 1465.36363636 XCP (a301bbca\u2026b3f6bb35)
2014-01-04-T11:34:11Pacific Standard Time Block: 278692
2014-01-04-T11:34:11Pacific Standard Time Block: 278693
2014-01-04-T11:34:11Pacific Standard Time Block: 278694
2014-01-04-T11:34:11Pacific Standard Time Block: 278695
2014-01-04-T11:34:11Pacific Standard Time Block: 278696
2014-01-04-T11:34:11Pacific Standard Time Block: 278697
2014-01-04-T11:34:11Pacific Standard Time Burn: 12bsGWBQneVK5M8LqrtonubHeKWRj3gZ
2J burned 0.9999 BTC for 1464.6717 XCP (275b9570\u2026196f8934)
2014-01-04-T11:34:11Pacific Standard Time Block: 278698
Yes, it is working. Congrats!!  |
|
|
|
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
With that bitcoin.conf configuration, your bitcoin server listens on port 8332. Worse case, edit bitcoind.conf, and add the following lines: 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. |
|
|
|
Don't you think it's a bit rush to launch the coin ? mac wallet not ready/ most ppl don't have txindex=1 and having to reindex and it may take a few days/ etc, creating the situation to have somebody to burn on behalf of somebody. It sounds like an unfair launch.
How about shifting the launch period for another 7 days, make sure everything is ready, ppl who already burnt the coin will get the reward as if it's burnt in the first day.
If we shift the launch period, what about the people who have already contributed? What does that say about fairness, as well as the trust that the community has in the Counterparty team to not shift any requirements, unless absolutely necessary (e.g. major security bug, or some other totally blocking issue), AND, if done, do so in a way that preserves existing stakeholders. Shifting the window would be a major fail on both of those fronts. The fact is, you guys are not losing out, so don't worry. We are barely three days out from launch, and the bonus is still quite close to the 1500 mark. Also, there now exists a way to burn coins without requiring counterpartyd or any extra software, and documentation is available for burning via blockchain.info (which anyone can do). For instructions on that, see: http://counterpartyd-build.readthedocs.org/en/latest/HowToBurn.html#without-using-counterpartydIf you are uncomfortable doing any of that, we have a well known and trusted member that will be buying and escrowing XCP on others behalf. I'd rather he announce it when he's ready, but it should be in a day or two. Regarding the Mac wallet, I will try to make that a priority this week, but given that you can burn without a wallet/counterpartyd (or will soon be able to have someone burn for you), it is much less of an issue, IMO. Leo: I will respond to your issue shortly (I think I know the problem now, it's an easy one). The build system was working, but we had an unexpected backend library dependency release that broke it. I have modified it to be fixed to a specific version so that shouldn't happen again. This was all done within a day of it being discovered. We are doing our best to be responsive to the community and trying to give everyone a fair chance. |
|
|
|
have you thought of doing it over Peercoin blockchain as BTC is so precious that it would be much sad to see it burnt ? Ppc inflates 1% on POS minting (although it also destroys 0.01 transaction fee), so the burnt coins will hopefully be regenerated and we can keep our XCP.
We have been exploring taking the concept of Counterparty out to additional blockchains. From a technical standpoint, Counterparty uses the OP_RETURN feature of Bitcoin to store its data (full support for which will be included in Bitcoin v0.9, which will most likely be out and deployed across the major mining pools in about a month to two based on Gavin's estimates). The advantage of this is that it's a very clean way of encoding the data: Counterparty transactions can be easily pruned from the blockchain. The disadvantage is that any altcoin looking to implement Counterparty support would need to have this feature (or, fork and extend the Counterparty protocol to use a slightly different encoding method, such as multisig or something similar to Mastercoin's Class A transactions). Currently, Peercoin is moving to 0.8.4 code I believe. Once SunnyKing syncs up to 0.9, this may be possible (however, there may still need to be some adjustment made to deal with the stake blocks that Peercoin has). This all being said, we are interested in speaking to altcoin developers (and especially ones that can work with the OP_RETURN featureset) as this develops. Counterparty becomes stronger as its standards are deployed across multiple blockchains. So, are you saying that, in the future, Counterparty could possibly link directly into different block chains enabling atomic trade of currencies from both chains, nearly natively? For example, I could have a PC with bitcoind and ppcoind fire up and counterparty running and I can sell BTC for PPC and actually see PPC appear in my peercoin wallet and BTC disappear from my bitcoin wallet, natively? If so, then this is amazing stuff! P.S. Does Mastercoin support this? Does Mastercoin use OP_RETURN? No, actually, my response was limited to talking about Peercoin implementing counterparty on its blockchain. What you mentioned is not possible today, however, there are several parties (including Counterparty) discussing the feasibility of it. Mastercoin will eventually support OP_RETURN as "Class C" transactions, but currently, AFAIK, there is no support for this. |
|
|
|
Assuming windows Right click computer -> properties -> advanced system settings -> environmental variables -> highlight path and click edit Add this to the end of whatever is in variable value ;C:\Program Files (x86)\Git\cmd Now, could someone please help me with my issue? I can't get counterpartyd to work http://pastebin.com/ZzAJbrSWI see you are trying to run it like: c:\counterpartyd_build>C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py If you installed with the counterpartyd_build system, then you have to run it like the build system docs say: cd C:\counterpartyd_build
C:\Python33\python.exe run.py --log-file=-
or, for no logging to screen (log to log file instead): cd C:\counterpartyd_build
C:\Python33\python.exe run.py
Reason for this, is that run.py runs counterpartyd in a dedicated Python virtualenv, which has all the python libraries at versions that are tested with counterpartyd. |
|
|
|
Is there any form of mining with XCP, either in the minting of new CXP (which I doubt) or in the form of harvesting transaction fees?
Thanks.
No, and all of the transaction fees are in BTC, except for those paid in XCP to the operators of 'feeds'. Does that mean we collect fees in BTC by processing XCP transactions or does it go to the normal bitcoin miners? Also, what about those pain in XCP to the operators of feeds? Can you please explain a bit more about who that works or provide a link to the documentation about this. Highly interesting. The BTC fees go to the normal Bitcoin miners. The address which broadcasts a feed picks a fraction of every bet made on it that it would like to receive in fees. On testnet, for instance, the feed published by mt1N2qE4wHkjdDeumCtRg1NKwxXGMCAx5X takes .01% of every bet made on it, when that bet is matched and settled. So if I bet 100 XCP that the value of that feed, then 100 + (100 * .0001) XCP is deducted from my address, and if/when the bet is settled, .01 XCP goes to mt1N2qE4wHkjdDeumCtRg1NKwxXGMCAx5X. This is really cool stuff. I'd like to setup a feed on the test net. Is there someone I could look for some info on how to do that? I wrote an additional section to the docs that may help here: http://counterpartyd-build.readthedocs.org/en/latest/AdditionalTopics.html#testing-counterpartyd-on-testnet |
|
|
|
|
Support for Ubuntu 12.04 LTS added to the build scripts (I had actually been testing with 13.10, but now it works on both). Documentation has been updated to state that Linux support is limited to Ubuntu 12.04 and 13.10 for now.
Pull requests welcome for additional OS support (especially Mac OS)!
|
|
|
|
Followed all the instructions but am getting an error when I run setup.py for the first time.
line 956, in install_wheel
'PIP_NO_INDEX': '1'
File "c:\python33\lib\site-packages\virtualenv-1.11-py3.3.egg\virtualenv.py",
line 898, in call_subprocess
% (cmd_desc, proc.returncode))
OSError: Command c:\counterpartyd_build\env\Scripts\python.exe -c "import sys, p
ip; pip...ll\"] + sys.argv[1:])" setuptools pip failed with error code 1
2014-01-03 16:35:35,134|ERROR: Command failed: 'c:\python33\Scripts\virtualenv.e
xe --system-site-packages c:\counterpartyd_build\env'
What version of Windows? Also, can you please post the full traceback on pastebin.com and give me the link (or, you can file a bug report at https://github.com/xnova/counterpartyd_build/issues) Actually, putting all of the output from the run of setup.py on pastebin.com would be most helpful. Here is the pastebin with my full command prompt. I followed the instructions to the letter from http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.htmlWindows 7 64 bit http://pastebin.com/iSTJ1uNkThank you for that bug submission! The problem was virtualenv version 1.5 was just released on Jan 2 that had a number of backwards-incompatible changes. This broke the setup (as the script was just fetching the newest version of virtualenv). I've tied the version the setup uses to the previous versions of virtualenv and pip, and it appears to work fine. Here's what you need to do: * Update your counterpartyd_build code from git (e.g. "cd C:\counterpartyd_build && git pull origin master") * Remove Python3.3.3 from your system (via Add/Remove Programs), along with all Python3.3.3 child dependencies listed in the add/remove programs list with it (pywin32, cg_freeze ..remove them before removing Python itself) * Manually delete the C:\Python3.3 directory (make sure it doesn't exist anymore) * Reinstall Python3.3.3 and related packages (just follow the instructions again) * Try to rerun the setup.py script as normal I just rebuilt using these instructions under Win7 64-bit and it worked fine. Let me know if you have any more issues. |
|
|
|
How is the price determined? Right now, XCP are being rewarded to those that burn BTC at a price between 1500 XCP/BTC and 1000 XCP/BTC. The exact formula is:
XCP_EARNED = BTC_BURNED * (1000 * (1 + .5 * ((END_BLOCK - CURRENT_BLOCK) / (END_BLOCK - START_BLOCK)) Thank you PhantomPhreak. I would need both bitcoind and counterpartyd running? It sounds like there are plans to have intermediaries do the burning for people soon so they don't have to set this up? That's right. What is the end block number? Approximately. The end block number is listed in the spec, in this section: https://github.com/PhantomPhreak/Counterparty#burn |
|
|
|
Some help anyone?
We are implementing a change that will address this issue of burns currently not working, and make them a lot easier to do. The change will be complete and we will have an announcement within 2 hours from this point with the full details. Thanks everyone for your patience. |
|
|
|
1) I reinstalled/rebuilt counterpartyd from your fresh code. Now when I run counterpartyd --rpc-password=rpcpw1234 burn --from=1CrmTo7Rtk6keeBHbN93B3tAMCm31sG5Tc --quantity=0.01 I get the following error message, Burn did *not* appear to be successful. Full output from Eligius: <HTML> <HEAD> <TITLE>Eligius - Push Transaction</TITLE> </HEAD> <BODY> <FORM METHOD="POST"><TEXTAREA NAME="transaction" COLS=80 ROWS=10></TEXTAREA><BR><INPUT TYPE="submit" NAME="send" VALUE="Push"></FORM> <BR><BR> <PRE> Trying to send... NULL Response = 0 </PRE> </BODY> </HTML> false 2) Additionally, when I tried to run the following command, counterpartyd --rpc-password=rpcpw1234 address 1CrmTo7Rtk6keeBHbN93B3tAMCm31sG5Tc to check my address balance, I got this following output, Balances
+-------+--------+
| Asset | Amount |
+-------+--------+
+-------+--------+
Burns
+-------------+--------+--------+---------+
| Block Index | Burned | Earned | Tx Hash |
+-------------+--------+--------+---------+
+-------------+--------+--------+---------+
Sends
+--------+-------+--------+-------------+---------+
| Amount | Asset | Source | Destination | Tx Hash |
+--------+-------+--------+-------------+---------+
+--------+-------+--------+-------------+---------+ Is this expected or should I be seeing my btc balance in my account 1CrmTo7Rtk6keeBHbN93B3tAMCm31sG5Tc in the above display? Thx. If the burn is successful, counterpartyd will print back something like this: Burn transaction *appeared* to be successful. Eligius returned hash: 814f7c960cb219e258f3414b043938881d9b959686c07be7836528a38b3a6d45
Please note that it may take up to 2 or 3 hours for Eligius to publish your burn to the blockchain.
Once published, it will be visible from https://blockchain.info/address/1CounterpartyXXXXXXXXXXXXXXXUWLpVr
true
As it failed, don't worry, no funds will be lost...either the transaction is successfully read and processed by Eligius or it is not. Please make sure you have the newest version of the source from git (cd into the counterpartyd directory and run "git pull origin master", and you can verify with "git log"). If your code is current, then the problem is most likely on the Eligius side (which from the error message, it appears to be). You may want to try it again a bit later, or, try a higher amount (e.g. 0.05). |
|
|
|
The following link can be visited to see up to date burn activity for Counterparty: https://blockchain.info/address/1CounterpartyXXXXXXXXXXXXXXXUWLpVrNote that since the burn blocks are being processed by only one pool at this time (Eligius), investments spanning an hour or two will tend to be "grouped" within single blocks. I will be releasing a Windows installer for counterpartyd this weekend. |
|
|
|
Followed all the instructions but am getting an error when I run setup.py for the first time.
line 956, in install_wheel
'PIP_NO_INDEX': '1'
File "c:\python33\lib\site-packages\virtualenv-1.11-py3.3.egg\virtualenv.py",
line 898, in call_subprocess
% (cmd_desc, proc.returncode))
OSError: Command c:\counterpartyd_build\env\Scripts\python.exe -c "import sys, p
ip; pip...ll\"] + sys.argv[1:])" setuptools pip failed with error code 1
2014-01-03 16:35:35,134|ERROR: Command failed: 'c:\python33\Scripts\virtualenv.e
xe --system-site-packages c:\counterpartyd_build\env'
What version of Windows? Also, can you please post the full traceback on pastebin.com and give me the link (or, you can file a bug report at https://github.com/xnova/counterpartyd_build/issues) Actually, putting all of the output from the run of setup.py on pastebin.com would be most helpful. |
|
|
|
Running setup.py on ubuntu, get this error: Setting up sqlite3 (3.7.13-1) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
sudo: pip3: command not found
2014-01-02 16:46:30,314|ERROR: Command failed: 'sudo pip3 install appdirs==1.2.0'
$ sudo pip-3.2 install appdirs==1.2.0
Requirement already satisfied (use --upgrade to upgrade): appdirs==1.2.0 in /usr/local/lib/python3.2/dist-packages
Cleaning up...
$ ./counterpartyd.py
Traceback (most recent call last):
File "./counterpartyd.py", line 17, in <module>
import dateutil.parser
ImportError: No module named dateutil.parser
$ sudo pip-3.2 install dateutil
Downloading/unpacking dateutil
Real name of requirement dateutil is dateutil
Could not find any downloads that satisfy the requirement dateutil
No distributions at all found for dateutil
so setup.py fails on pip3 appdirs, counterpartyd complains about missing dateutil, and I'm not sure how to install dateutil. Hmm. I think that dateutil is called python-dateutil in pip. btc4ever, let me know the Ubuntu version and I'll see if I can reproduce the problem, as I am maintaining the build system. I developed on Ubuntu 13.10, but I want this to be able to run on 12.04 LTS, 12.10, 13.04 and 13.10. Support for other Linux versions can be added as well (I take pull requests!  |
|
|
|
|
Show Posts
