Bitcoin Forum
June 16, 2024, 09:35:05 PM *
News: Voting for pizza day contest
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Economy / Speculation / Re: If you were to start a position on bitcoinica RIGHT NOW... on: November 26, 2011, 09:50:27 AM
To answer the caps question above "HOW DOES IT RELATE TO BITCOINICA" bitcoinica works pretty much the exact same way as well, any market, be it stocks or forex.

Orders page =  http://puu.sh/9m9o
What happened in that image is: I bought 26 bitcoins, my original bid was $2.50 (You cannot see this here) however a cheaper price was available at $2.471 so that was the final buying price, it purchased coins at the best available price because I used a 'buy limit' order.

Positions Page: http://puu.sh/9m9K
A position is an order that has been filled, so since I bought 26 coins (and 1 more in a trade I didnt screenshot) my position is 27 bitcoins, although there are no deliveries the best way to think about it is that I now, after buying them, have 27 coins in my wallet.  The P/L field is simply profit/loss, red means a loss, green means profit. P/L % Same except in percent form. The liquidate button is the button you use to close your position (Either secure profits or cut losses), if you bought coins, I like to think of it as bitcoinica is selling them back to other people and giving you the USD value of them credited to your account.

To the guys above me, I don't mean to be rude here, but if you dont have a decent understanding of margin/leverage, order types and the ideas behind going long and short, you shouldn't be on bitcoinica, all you will do is lose your money unless you get lucky, in which case you will lose your money at a later time. Simply google some basic forex tutorials, the concepts are all the same.

imho expecting bitcoinica to teach you how to trade is like expecting adidas to teach you how to play soccer.


This guy speaks the truth, it is not bitcoinicas role to teach you how to trade, they offer you a platform, not a school.
2  Bitcoin / Bitcoin Technical Support / Re: Pushpool - Tech Support on: July 31, 2011, 06:27:19 AM
An interesting note to add to my issue, If I set bitcoin.conf to run on testnet it runs 100% perfectly Huh

Which makes me thing I have got my ports setup correctly, however bitcoin cannot connect to the real network for some reason, does anyone agree with this?


edit: I have just tried installing it on a different server using the same settings and I am still getting error 500s. Can someone please PM me or post their server.json and/or bitcoin.conf (with senstive data removed of course  Wink ) from a working box? I really want to figure this out.


2nd edit: On the second server now, I have the exact same issue still, it connects perfectly to the bitcoin testnet. However the moment I take testnet=1 out of bitcoin.conf, and restart both bitcoind and pushpool I receive error: 500s. Please can someone provide some insight into this. It must be something Im doing wrong...
2 BTC up for grabs to whoever can tell me whats wrong  Embarrassed

Thanks
3  Bitcoin / Bitcoin Technical Support / Re: Pushpool - Tech Support on: July 31, 2011, 04:47:07 AM

Where is everyone getting the change their port to 8332?

Notice this line:

Quote
RPC settings | Notice how this ISN'T port number 8332 this is becuase the same port number should not becuase inconjunction with the JSON RPC port other wise you'll get 500 errors

You're getting those 500 errors.

I might retire from people needing help and paying for support on pushpool haha.

Make sure you can connect to bitcoin rpc on your port 8331. I would recommend changing it to 8332 in both the bitcoin config and in the server.json unless you are using that port for something else.

Something I also see a lot of people doing which is such a security issue is: rpcallowip=*.*.*.*

Set that to frikken rpcallowip=127.0.0.1  If you have bitcoind running on the same machine as your pushpool why would you let everyone on the internet have rpc access to your bitcoin if they can guess your username and password and then drain your wallet?

You're getting a 500 error because two things look like they are trying to hit 8331. Give us a netstat before you start pushpoold.


If you read the codes you would notice that in fact, bitcoin.conf listens on port 8331, and server.json is configured to port 8331. I have no idea where you got the idea otherwise, nowhere is port 8332 used at all. rpcallowip is *.*.*.* because I was directly connecting to bitcoind from my computer to try debug where the issue was.
I dont understand why you pointed out port 8332, its not in there Huh
4  Bitcoin / Bitcoin Technical Support / Re: Pushpool - Tech Support on: July 30, 2011, 05:43:46 PM
Willing to pay 1.5 btc to anyone that can tell me how to fix my issue!
I have installed pushpoold following the tutorial on the first page however I am stuck Sad

Whenever I run pushpoold I receive this error: http://puu.sh/3PLK  (After initialised I tried to connect using guiminer from my machine, pushpool is being hosted on a VPS)

my bitcoin.conf:
Code:
rpcuser=user
rpcpassword=pass
rpcport=8331
rpcallowip=*.*.*.*


and my server.json (With my SQL details removed, however I know they are correct)
Code:
{
# network ports
"listen" : [
# binary protocol (default), port 8342
{ "port" : 8342 },

# HTTP JSON-RPC protocol, port 8341
{ "port" : 8341, "protocol" : "http-json" },

# HTTP JSON-RPC protocol, port 8344,
# with trusted proxy appserver.example.com forwarding
# requests to us
{ "port" : 8334, "protocol" : "http-json",
 "proxy" : "127.0.0.1" },

# binary protocol, localhost-only port 8338
{ "host" : "74.63.212.182", "port" : 8338, "protocol" : "binary" }
],

# database settings
"database" : {
"engine" : "mysql",
"host" : "localhost",
"port" : 3306,
"name" : "---",
"username" : "---",
"password" : "---",
"sharelog" : true,
"stmt.pwdb":"SELECT `password` FROM `pool_worker` WHERE `username` = ?",
"stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?)"

},

# cache settings
"memcached" : {
"servers" : [
{ "host" : "127.0.0.1", "port" : 11211 }
]
},

"pid" : "/tmp/pushpoold.pid",

# overrides local hostname detection
"forcehost" : "localhost.localdomain",

"log.requests" : "/tmp/request.log",
"log.shares" : "/tmp/shares.log",

# the server assumes longpolling (w/ SIGUSR1 called for each blk)
"longpoll.disable" : false,

# length of time to cache username/password credentials, in seconds
"auth.cred_cache.expire" : 75,

# RPC settings | Notice how this ISN'T port number 8332 this is becuase the same port number should not becuase inconjunction with the JSON RPC port other wise you'll get 500 errors
"rpc.url" : "http://127.0.0.1:8331/",
"rpc.user" : "user",
"rpc.pass" : "pass",

# rewrite returned 'target' to difficulty-1?
"rpc.target.rewrite" : true
}

Frankly im completely confused. Also here is a screenshot of my IPtables: http://puu.sh/3PMh
As you can see the ports that i think pushpool use are open... Any suggestions? Huh
5  Other / Beginners & Help / Re: Help with bitcoind on: July 27, 2011, 07:26:19 AM
Are you saying i include the json-rpc files into the apache startup? Sorry epic noob at linux :p
6  Other / Beginners & Help / Re: Help with bitcoind on: July 27, 2011, 05:19:37 AM
This is what Im having difficulties with :/ I Download the JSON-RPC php package, but what do I do with it then? What do I have to configure? Is there a certain directory I should place the files?

Also with the file we each quoted, where does that go? anywhere?


Make sure to go download the JSON-RPC class and have it on your webserver.  Your code should then look like:

7  Other / Beginners & Help / Re: Help with bitcoind on: July 27, 2011, 04:59:26 AM
Yes I have the latest version of LAMP running on it, basically ive got a little ubuntu box on a VPS I rent to use with my TS server. So its on a completely different network and we are trying to connect to it Sad
8  Other / Beginners & Help / Re: Help with bitcoind on: July 27, 2011, 04:55:40 AM
Thats what I thought too, I have done that in the config file and set rpcallowip to rpcallowip=*.*.*.* to test it until it is up and running, however any connections I send to it just dont work.

Dont I need some kind of RPC script to interface with bitcoind? For example:

Code:
require_once 'jsonRPCClient.php';
 
  $bitcoin = new jsonRPCClient('http://user:password@127.0.0.1:8332/');
 
  echo "<pre>\n";
  print_r($bitcoin->getinfo()); echo "\n";
  echo "Received: ".$bitcoin->getreceivedbylabel("Your Address")."\n";
  echo "</pre>"

Which was found on: https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)

Or do I not need this?
9  Other / Beginners & Help / Re: Help with bitcoind on: July 27, 2011, 04:39:54 AM
Look, I understand that pool mining would probably be more profitable. However this isn't really about making an extra $20 down the track, I would like to set it up basically for the hell of it, try it all out, play around with it etc. If anyone can help me where I'm stuck it'd be appreciated, however if you have come in just to say "Pool mining is more profitable" then please don't post because it isn't about that.
10  Other / Beginners & Help / Re: Help with bitcoind on: July 27, 2011, 03:41:28 AM
Bitcoind is for managing your wallet, you're probably going to want to look at pushpool.
http://forum.bitcoin.org/index.php?topic=10321.0

[Edit]: Or, just check my sig Smiley

You can run bitcoind as a server with the -daemon -server arguments, or put server=1 in bitcoin.conf

Thanks anyway though Smiley
11  Other / Beginners & Help / Re: Help with bitcoind on: July 27, 2011, 03:25:53 AM
Maybe 6-7 ghashes? There is 10 of us. Can I ask why you wondered that?
12  Other / Beginners & Help / Help with bitcoind on: July 27, 2011, 03:08:18 AM
Hey all, Im trying to setup a sort of mini-pool for a group of friends, we have a little ubuntu box that we have on 24/7 for our teamspeak server so we figured why not give 'solo' mining a go. I understand its probably a better idea to go with a pool but together we do get a respectable hash rate in my opinion.

Ive installed bitcoind on the server and got it running, opened the port 8332, created bitcoin.conf, but from here I am lost as to what to do?
I understand that i need to setup some kind of JSON RPC system for the computers to communicate with bitcoind externally. Can anyone offer some assistance with this? Or point me in the direction of some information regarding it?

Thanks!  Smiley
 
Look, I understand that pool mining would probably be more profitable. However this isn't really about making an extra $20 down the track, I would like to set it up basically for the hell of it, try it all out, play around with it etc. If anyone can help me where I'm stuck it'd be appreciated, however if you have come in just to say "Pool mining is more profitable" then please don't post because it isn't about that.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!