Search content
Sort by
Showing 4 of 4 results by takeshibaconsuzuki
Re: [ANN] RIALTO.AI Cryptocurrency Arbitrage and Market Maker ★ OFFICIAL THREAD ★
50% of the trade log (in appendix 2), containts positions which require shorting on bitstamp.
However you cant short on bitstamp, so how would you do this?
Because otherwise half of your appendix 2 is false information.
the whitepaper discussing their trades: https://www.rialto.ai/wp-content/uploads/2017/06/RIALTO.AI_Whitepaper.pdf \
appendix 2: https://www.rialto.ai/wp-content/uploads/2017/06/Appendix2.pdf
However you cant short on bitstamp, so how would you do this?
Because otherwise half of your appendix 2 is false information.
the whitepaper discussing their trades: https://www.rialto.ai/wp-content/uploads/2017/06/RIALTO.AI_Whitepaper.pdf \
appendix 2: https://www.rialto.ai/wp-content/uploads/2017/06/Appendix2.pdf
Arbitrage is the simultaneous buying and selling of an asset on two different exchanges to profit from the price difference. Why would you need to short anything?
I know I can putty into a rpi. But everytime I close the connection it closes the session on the pi. Is there an easy command that can continue the process when closing the connection?
I tried google, probably didn't search the proper terms.
You win a cookie if you know
I tried google, probably didn't search the proper terms.
You win a cookie if you know
screen or nohup can be used.
Alternatively vnc and keep a terminal open on the desktop.
example
screen -dmS MINER /usr/local/bin/cgminer --config /etc/cgminer.conf
Adding to his reply, to bring it back, enter:
screen -x MINER
and to get back to the terminal again hit ctrl-d.
I have a raspberry pi (with a static ip) that is connected to a windows desktop via ethernet. On my windows desktop, I am running an instance of bitcoin-qt, and I am trying to access this.
First, I looked up my desktop's ip address using ipconfig, which turned out to be 192.168.0.18. Since I have an apache web server on my desktop as well, I curl'd it from the raspberry to test that the ip was indeed correct.
Next, I tried to curl my desktop on port 8332 (which is where bitcoin-qt is listening) with the correct credinals. It gave me a "forbidden" message.
I double checked my firewall to make sure that wasn't the problem. I also checked my rpcallowip to make sure my raspberry wasn't being blocked there.
I then went onto my desktop and curl'd localhost port 8332 from there. I got a json output, as expected. Curl'ing 192.168.0.18 on port 8332 still gave me a forbidden message.
Does anybody have any idea what is going on?
First, I looked up my desktop's ip address using ipconfig, which turned out to be 192.168.0.18. Since I have an apache web server on my desktop as well, I curl'd it from the raspberry to test that the ip was indeed correct.
Next, I tried to curl my desktop on port 8332 (which is where bitcoin-qt is listening) with the correct credinals. It gave me a "forbidden" message.
I double checked my firewall to make sure that wasn't the problem. I also checked my rpcallowip to make sure my raspberry wasn't being blocked there.
I then went onto my desktop and curl'd localhost port 8332 from there. I got a json output, as expected. Curl'ing 192.168.0.18 on port 8332 still gave me a forbidden message.
Does anybody have any idea what is going on?
Is it normal to see almost no updates while running cgminer? I just wanted to make sure my solo mining setup was working, since cgminer's output was bare compared to when mining in a pool.
All I see occasional are "block height changes". I have 0 HW errors, but my accepted rate is also 0 and I see no work being sent to me. The hash rate is normal, so I think my miner is working.
All I see occasional are "block height changes". I have 0 HW errors, but my accepted rate is also 0 and I see no work being sent to me. The hash rate is normal, so I think my miner is working.