Wallet Address:
Yin- YdYraaEmAeD3GPKPKaQKZDbMDusK4XdLmY (This is the Yincoins that are currently sitting my Poloniex account. I know the address is weird, but if you remember we had blockchain issues, and our blockchains we're reversed, this is why it's taking so long to find addresses. Subtract like 700K from this amount from the coins I showed I sold.
Yang- Posted when found
Yincoin addresses start with 'y', not with 'Y', plus your blockchain explorer is not working right now because of a certificate issue. I know the explorer had the addresses reversed, but that is easy to fix, just put the right address-version in abe-explorer: YIN "address_version": "\u008c" YANG "address_version": "\u004e" I think you should post the right Yincoin and Yangcoin addresses not the ones reversed. |
|
|
|
Not sure what the issue is; if you can generate a wallet and sync the chain though, you can start mining in the daemon to your address directly though with the following command: start_mining <address> <number_of_threads> This seems to work partially: the load average is only 1.00 and it should be equal to the number of threads ( 8 ). After 5 minutes nothing has changed. set_log 1 in daemon likely you are not synchronized and it is validating headers You were right. It is now working. Thanks! |
|
|
|
Not sure what the issue is; if you can generate a wallet and sync the chain though, you can start mining in the daemon to your address directly though with the following command: start_mining <address> <number_of_threads> This seems to work partially: the load average is only 1.00 and it should be equal to the number of threads ( 8 ). After 5 minutes nothing has changed. |
|
|
|
I'm unable to start_mining. I synchronize the blockchain with bitmonerod, and then I use simplewallet to start_mining, but I get: 2014-Apr-25 22:34:26.724501 Read command: start_mining 8 2014-Apr-25 22:34:31.724750 Failed to invoke http request to http://localhost:18081/start_mining2014-Apr-25 22:34:31.724776 Error: mining has NOT been started: possible lost connection to daemon In the bitmonerod terminal: 2014-Apr-25 22:40:16.245240 [RPC1][sock 28] Some problems at write: Broken pipe:32
2014-Apr-25 22:40:54.008484 [RPC1]Mining has started with 8 threads, good luck!
2014-Apr-25 22:40:54.008539 [miner 1]Miner thread was started [5]
2014-Apr-25 22:40:54.008530 [miner 0]Miner thread was started [4]
... I'm using Ubuntu 13.10, and I've followed the instructions in the OP. The cpu is an old 8 core intel i7 860 Any idea of what I'm doing wrong? |
|
|
|
Why not exlude funds that are affected by possible CC and ACH chargebacks and payout the non affected funds to investors in the next few weeks? When the chargeback windows have closed the remaining funds could be paid out?
Likely a much better solution than waiting up to 12 months to pay out everybody
+1 Hopefully not all the remaining funds are affected by the chargeback windows ... |
|
|
|
GPU mining doesn't seem to work, all my blocks end up rejected. Anyone else tried it yet? I left out -Nfmin -Nfmax and -StartT because I don't know what they stand for or how to find out and could never find an explanation! Also, whilst googling for an answer, I found a post somewhere saying Onecoin uses different mix and hash functions than YAC and other scrypt-janes so possibly this is why it isn't working? Assuming the standard scrypt-jane GPU miner needs to be tweaked specifically for Onecoin, as a dozen blocks all ending up as rejects in a hour doesn't seem right.
NFactor 11, kynda obvious GPU wont work. Can still mine GPU mine YAC just fine with N factor 14, play around with settings enough and all scrypt-jane coins yet released are still GPU mineable. Profitably mine @ Nfactor+ 10? nah hard to believe Well it isn't so profitable now, but thats not because you can't GPU mine it, crank up the thread conncurrency and lookup gap and it'll work. Trust me, scrypt-janes were my bread and butter for a long time while everyone was staring at coinchoose and coinwarz. In any event, I suppose it doesn't matter much at the moment as my i5 is still finding blocks right now. I'm gonna mine it for a bit and see what happens. I always liked onecoin and was sad to see it go away, hope there is still life in the old girl yet! Well, it does not use the same functions as yacoin, so AFAIK you cannot use the existing GPU miners: Okay, so now scrypt-jane is using BLAKE 512 and Salsa 64. Also I rewrote GetNfactor() to make Nfactor increase more uniform.
cpuminer for Onecoin is coming soon (it should be a lot faster on 64 bit machines than the built-in miner).
Also, from makefile.unix: # scrypt-jane specific parameters
DEFS+=-DSCRYPT_SALSA64 -DSCRYPT_BLAKE512 -DSCRYPT_CHOOSE_COMPILETIME
YAC and another scrypt-jane coins use # scrypt-jane specific parameters
DEFS+=-DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME I think you can mine blakecoin using a custom cgminer, so maybe it can be adapted to mine onecoin ... blakecoin uses blake256, I think ... |
|
|
|
|
The new estimated portfolio value at the redesigned balances page does not include the coins held for orders ...
|
|
|
|
We should also continue to talk to the issuers of the other assets that underly BTCINVEST. I've sent a similar plea on 2013-12-05 to TF for the direct AM shares, but I haven't received a response. We still need to find out what happened to the assets in btct.co, and talk to dooglus of JD. Does anyone (who won't make threats) want to help?
According to dooglus when the inputs.io "hack" happened:
The current situation is that I took 42 BTC from TradeFortress' Just-Dice account to replace the stolen coins, and then let him withdraw the rest.
So we current are not holding any of his coins "hostage", and therefore can no longer accept inputs.io deposits without risking client funds.
Not idea if that was a personal TradeFortress JD account or these funds belong to BTCINVEST ... |
|
|
|
But I still have a zombie order cancelled days ago that keeps appearing at the Points/BTC market ...
About zombie order - try to place new same order and then cancel. It worked three times for me at different coins. Thanks, that worked. |
|
|
|
|
It seems that finally cryptsy is starting to work again, at least from here.
After 36 hours I have recovered my coins and I can access to the site faster than past week.
But I still have a zombie order cancelled days ago that keeps appearing at the Points/BTC market ...
|
|
|
|
You need to replace the A in the grep of the myinfo script for addr in $(quarkcoind listtransactions | grep --color=never -o "A[A-Za-z0-9]\{32,35\}" | sort -u);
with a Q to get quarkcoin addresses. BTW, after rerunning your updated script I cannot get any connections in a digital ocean droplet. Are the nodes working? Thanks |
|
|
|
Why is the old HVM value used in the 31 july repport 0,56322737 instead of 0,613322737(the adj NAV from previous week) and why is the weeks result shown as a profit of 2.34%(2,61% ?) instead of a loss of 7,01% like it would have been if you used the correct? adj NAV like it has been done in all previous repports ?
A 0.05 dividend was paid ... |
|
|
|
I've updated to cuda-5.5 (and driver 319.21) Running with cuda-gdb I get the following error: Have 2400 candidates after main loop
Cuda start!
[New Thread 0x7fffacc38700 (LWP 14248)]
[Context Create of context 0x7fff700234f0 on Device 0]
[Launch of CUDA Kernel 0 (runPrimeCandidateSearch<<<(25,1,1),(192,1,1)>>>) on Device 0]
Program received signal CUDA_EXCEPTION_10, Device Illegal Address.
[Switching focus to CUDA kernel 0, grid 1, block (15,0,0), thread (0,0,0), device 0, sm 3, warp 0, lane 0]
0x00007fff7091b760 in long_multiplication(unsigned int * @generic, unsigned int * @generic, unsigned int * @generic, unsigned int, unsigned int) (
product=0x3fff6b4, op1=0x3fff734, op2=0x3fff634, num_digits=17,
prod_capacity=1073741824)
at primecoin/src/cuda/digit.h:406
406 product[i] = 0;
|
|
|
|
Seems to be working very nicely, but I have worries that this will not be profitable thing to do
0.01 btc per day cost is 1.1 XPM
so within 6 hours need to get 0.275 XPM
So far I have got 0.037689 unconfirmed and only 4 hours left, so in next four hours I need to get ~0.24 xpm
In about one hour I've got 5 shares and 0.012 XPM. I would need 100 hours at this step to get 1.1 XPM ... Maybe the pool has been unlucky. Let's see in 5 more hours ... |
|
|
|
|
I get "invalid bid input" when trying to buy. I've sent a support request.
|
|
|
|
BFGMiner prime is definitely using getwork when talking to primecoind.
I'm still poking around the source code to see if there is anyway to force it to use GBT.
--no-getwork or is that to obvious? I tried that as well, and while bfgminer does not fail for me, it will not connect to primecoind with the --no-getwork option. I think there is a problem with blkmk_address_to_script function in libblkmaker/base58.c I added case 23 and 83 (primecoin PUBKEY_ADDRESS and SCRIPT_ADDRESS), but after 4 hours I have got no blocks ... |
|
|
|
|
linux client just core dumped. Cannot restart it ...
|
|
|
|
version 1.1 released. Download links updated in OP. After block 750, it will revert back to ppcoin's diff retarget algorithm (still adjust each block). Hopefully this will fix the diff oscillation issue.
github? Edit: thanks! |
|
|
|
|
userid: liteuser
GYMkfBwwWvxtj1x5i2UG9rvnBCM7HRheiR
Thanks
|
|
|
|
|
GYMkfBwwWvxtj1x5i2UG9rvnBCM7HRheiR
|
|
|
|
|
Show Posts
