121
General Discussion / Re: http://www.ptsbuy.com/ Protoshares to/from Bitcoin Online Exchange!
« on: November 12, 2013, 12:47:49 pm »
Withdrawal done after 5 minutes aprox.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Now appears BTC on my account. Tried to use "Withdrawal BTC" but it doesnt work, it gives me this error:
"Minimum 0.01 BTC"
Tried to withdrawal > 0.01
sorry
bitcoid download data
waiting...
Deposited some BTC to test it, and after 5 confirmations my account is 0 BTC.
Seems to be a SCAM. I will report if it works.
it needs 6 confs to be added
Deposited some BTC to test it, and after 5 confirmations my account is 0 BTC.
Seems to be a SCAM. I will report if it works.
sorry
bitcoid download data
waiting...
(08:55) Silfax: In case some people don't scroll, the exchange is unpausing at 4pm Europe time, 10am EST.
En el momento del lanzamiento, anunciado con anterioridad, Invictus inicializará el bloque
génesis de la DAC para que correspondan exactamente las salidas no gastadas de su correspondiente
cadena de bloques ProtoShares.
At our DAC’s pre-published launch time, Invictus will initialize the DAC’s genesis block
to precisely match the current unspent outputs of its corresponding ProtoShares blockchain.
Ok, it appears that crash may be limited to linux only. FreeTrade is working to add a checkpoint right after the fork and hopefully that will fix that issue.
In the mean time, I am going to work on a hack to allow me to host protosharesd from my mac client and if that works without crashing then the pool will be up soon.
Well I atleast can´t conect ...was there anything anounced that the server would go down?Yes:
"the typical behaviour for the miner when the connection is lost is to continue mining for 5 minutes (this is when the "force reconnect if possible!" log line appears) and when a thread finds a share during this period, the thread waits until the connection is back again to submit it. unfortunately the triggers are not always working correctly (the current implementation is a bit 'clunky' regarding connection loss) and a thread continues mining forever on the old block. especially when you have unstable connections or partly blocked connections or any behaviour that's far off from (let's say) "normal".http://www.peercointalk.org/index.php?topic=501.240
#!/bin/bash
#Tips welcome :) PYfnvSc9CRHCebGDtVkSijo6k7pCbpPthX
function launchptsminer {
echo "######## Starting ptsminer... ########"
cd ~/src/ptsminer/src/
./ptsminer -poolip=ptsmine.beeeeer.org -poolport=1337 -poolpassword=0 -pooluser=PYfnvSc9CRHCebGDtVkSijo6k7pCbpPthX -genproclimit=4 > ~/ptsminer.log &
}
control_c()
{
echo "######## Stopping ########"
ps aux | grep tail | grep ptsminer | awk '{print "kill "$2}' | sh
killall ptsminer
exit 0
}
trap control_c SIGINT
mv ~/ptsminer.log ~/ptsminer.log.old 2> /dev/null
launchptsminer
tail -f ~/ptsminer.log &
while true
do
grep "force reconnect" ~/ptsminer.log
if [ $? -eq 0 ]
then
echo "######## Force reconnect DETECTED ########"
echo "######## Killing ptsminer... ########"
killall ptsminer
echo "######## Wait 5 secs... ########"
sleep 5s
launchptsminer
fi
sleep 1s
done