Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread - page 591. (Read 1276933 times)

+1 - awesome post.

It's so refreshing to finally find people who launch a new project for the sake of advancing the crypto community, and not for getting rich fast (NXT, I'm looking at you! ).

Yes, that is, in general, correct.

Maybe a noob question but I hope someone can answer.

How do user created assets work? If I create an asset called Bitcoin, and issue 10 of those. Is that asset backed by the trust of the address which issued it? I am guessing people would sign messages with the address saying, "These 10 issuances of User Created Asset Bitcoin represent my full faith to issue one Bitcoin to whoever owns this asset?"

So the asset is only as good as the address/person who issues it.

Is this correct?

Come on ya cheapskates, we all want a GUI, we get an announcement that bounty is being raised to fund one, and one dude donates 0.1 BTC.  Now I understand a lot of small investors may not have much to give, but I know we got a handful of whales among all these burnt BTC who are cheaping out.  Typical, crypto-community always wants something for nothing and all devs to work for free.

Sent over another donation, I am now approx. a 0.45% stakeholder in XCP and a 9.5% stakeholder in the dev fund 

Thank you all the same!
updated.

 

Did you specify the --reindex switch again by accident? (is it in your bitcoin config file?... if that's even possible with that particular parameter...I'd check it just in case)

Thank you brite_enclave for taking the time. I am away from my bitcoin wallet computer so I can't check but I think I was forgetting to

to include the full command line before I input the desired command. Thank you kindly for pointing it out to me.

You're almost there.  You're exactly right -- you need to keep the one cmd window open and running the counterpartyd server (there are easier ways to do this as a service but if you only want to do it once this is fine).  While you're doing this, open another cmd window, and run the exact same command, only replacing "server" with whatever command you want to run ("wallet" would be a good one first time).

But you have to wait until the server has caught up with the current bitcoin block.  You can check the current number on blockchain.info or on blockscan.com

Yes -- stupid mistake on my part.  I wasn't thinking that one through.  rpc-host just specifies which IP address cherrypy binds to.  The only way you can accept external IP connections is to bind to 0.0.0.0, and there's no way to limit that by IP.  Actually, I'm not sure how bitcoind even implements rpcallowip -- I'll have to check it out.  But agreed that firewalls are the way to go.

It's also pretty simple to configure nginx as reverse proxy to limit external connections to certain hosts, using the "location" block and `allow x.x.x.x` then `denyall`.  Check me on that if you do it, can't quite remember if there's anything else to do.

If anybody has the patience to help a newbie I'd appreciate it. I am not a computer technical person. I followed the steps to install from source
on windows. I installed everything I needed and brought up a cmd.exe command window. I typed the

cd C:\
git clone https://github.com/xnova/counterpartyd_build
cd counterpartyd_build
C:\Python32\python.exe setup.py

I then follow the directions to run from source.

cd C:\counterpartyd_build
C:\Python32\python.exe run.py server

After doing this it takes a while showing all the blocks and transactions and burns up till now correct?

Well my question is after it has caught up, what do I do to use counterparty exactly? In the same command window it doesn't let me

type anything. So do i open a new command window while that one is running? If so when i go to counterpartyd_build prompt in a new cmd

all the commands do not work. Everything says is not a recognized command or something. I do not understand where the actualy

counterparty progam is. Please explain to me in a literal step by step manner like you would explaining to your grandmother. I just want to be able

to use counterpary to confirm my balance has successfully transferred when I transferred my private key from blockchain.info. And to move my xcp

to another bitcoin address. Thank you so much to any member willing to explain it layman to me.

Actually, rpc-host is set to what local interface IP counterpartyd will bind to (with 0.0.0.0 meaning "all interfaces"). So, it must be a local interface on the box (e.g. rpc-host=68.122.255.122 will bind to the local interface that has IP 68.122.255.122... that interface must exist on the system).

That being said, rpcallowip semantics do not exist in counterpartyd currently. We can consider adding them in a future release (or a pull request with the feature is welcome!). So currently, to restrict connections to that port down to a specific IP or set of IPs, please use your firewall (i.e. windows firewall, linux iptables, or some other firewall device like Cisco ASA/PIX or pfsense, etc).

In thinking about it, that is the best way to do it. Firewalls have much better (and proven!) feature sets for restricting access like this.

Thanks for bringing that up to my attention. The build system actually did not have the zmq deps for Ubuntu in there. Fixed in the newest push to git (should work for 12.04 for 13.10 -- they have different approaches due to python3-zmq not existing on 12.04).

rerunning setup.py didn’t work but installing python3-zmq with apt-get did it. Thanks.

If I'm not mistaken, rpc-host is essentially the same as rpcallowip.

This will allow any IP to connect:

If you specify the IP number, connections should be limited to that IP only:


However, IP addresses can be spoofed, so make sure you're using a very strong password if you've opened the connection to the Internet (20+ chars).  I would be very, very careful about exposing the API on the open Internet if you're storing any significant amount of XCP/BTC on that wallet.  It would be better to put it behind a proxy server, like nginx.

You probably know all this, but I mention this for the sake of others reading.

Thank you.

Is there an equivalent rpcallowip?

Yes, edit the counterpartyd.conf file and insert something like the following:

(you should also set rpc-user and rpc-password if you haven't already)

Yes, that should work. You could also just re-run setup.py, which should issue that command as it rebuilds the environment.

If you're on ubuntu, just run: sudo apt-get install python3-zmq

As long as you're using the system Python3 (running commands with `python3 cmd`) then you should be ok.

I’m on xubuntu 13.10 and get the same "import zmq" error after updating.

Hi PhantonPhreak/Xnova

With reference to the Counterparty API, is there a way to set it up so that It accepts request from non local IP (external public IP)

Cheers