Good to know, I'm working on a Boost 1_55 static build at the moment. To mine with wallet you need to compile external CPU miner from my Github and run command: "make -f makefile.unix" which requires openssl and boost. You could then start it from linux commandline: alias miner='/home/viz/coinshield-cpuminer/coinshield_prime 127.0.0.1 4447' then 'miner' to run and see debug output. I'll post once I have the updated wallet build. Would you like a cpu miner binary while I'm at it? As to pools, as mentioned in my post; I will be developing a pool as soon as my TODO gets smaller. This will be how the server side LLP templates will be released, since Coinshield is incorporating so many new features, all existing pool software will not work. Solo mining should work fine for now and early launch until I get to developing the pool. Thank You, Viz.thank you viz, building miner from source was easy enough under linux (i usually never install binary blobs but always build from source). solo mining is not a problem until the net hash rate is low, but a pool is critical imho when it raises for desktop miners like me... |
|
|
|
[How to run minerd] 1. Setup: magi.conf, then run the wallet rpcport=8232
daemon=1
rpcallowip=127.0.0.1
rpcallowip=SOME-IP
rpcuser=rpcuser
rpcpassword=rpcpass 2. Download minerd; and run in command line: minerd.exe --url http://127.0.0.1:8232 --user rpcuser --pass rpcpass --threads 1 Code: ./minerd --url http://127.0.0.1:8232 --user rpcuser --pass rpcpass --threads 1 here, rpcport - 8232, user and pass should match with settings in magi.conf. hi, i've started mining this coin right now... is there any reason for using less threads than the default? i've tried with 4 (my i7 has 4 physical cores) and got 50 kh/s, while with 8 i get 70 kh/s, however i haven't found any block yet... |
|
|
|
skunk,
The source code will be made fully available post-launch, at the launch of the Coinshield Exchange Channels. I will be releasing Doxygen documentation for the Coinshield Core [Pre Launch] to help amplify just that, trust, while protecting the innovation.
Viz.
then hopefully there will be some pools available at launch because my system is on boost 1.55 so your linux builds don't works here... please either rebuild for boost 1.55 or rebuild it statically. |
|
|
|
|
no sources for the wallet?
please make source code available before launch else the coin will miss trust...
|
|
|
|
scrypt(N, 1, 1) support was added on may 25, i can't tell if there is a windows build somewhere, but there are building instructions on github. Yeah, I made one pass using my coin developer box where I build the Windows wallets, but the MinGW environment isn't quite right for building minerd and I would hate to screw it up and break things. Took me several months of playing to get it working for coin building... sorry, can't help you there as i'm windows free since year 2000, but you can gently ask cbuchner1 on this thread for an updated windows build... |
|
|
|
Anybody have a link to a Windows 2.4 version with scrypt:131072 support in it?
I have it running on about 7 Linux boxes just fine, but the 2.4 Windows version from Sourceforge generates:
minerd: unknown algorithm -- 'scrypt:131072'
For reference:
minerd -V
cpuminer 2.4
built on May 20 2014
features: x86_64 SSE2 AVX AVX2 XOP
libcurl/7.34.0 zlib/1.2.8
scrypt(N, 1, 1) support was added on may 25, i can't tell if there is a windows build somewhere, but there are building instructions on github. |
|
|
|
are you sure it is your gpu ? Mine reported every blocks it found (I can't say precisely it was my gtx660, as I was running a 780ti a 750ti and the 660 at the same time.
well, my cpu wasn't as i know for sure i get the yay from cpuminer: $ ./minerd --algo=scrypt:131072 -o 127.0.0.1:30201 -q
[2014-09-06 13:51:11] 8 miner threads started, using 'scrypt' algorithm.
[2014-09-06 13:51:11] No payout address provided, switching to getwork
and the wallet runs with gen=0, so if it wasn't cudaminer, the holy ghost should be the culprit  edit: found another block right now and no output from either miner... |
|
|
|
cassey, was the launch of this coin even promoted? judging from from current network rate (~8kh/s) 4 days after launch, seems that just 4 cats are mining it... i never thought i would ever mine with 1/16 of total net hash power with a common desktop  |
|
|
|
Regarding block being not reported in cudaminer, you need to use -q to remove all the hashrate info, this way you will see the "yay" when a block is found (haven't had any problem at that level)
nope, all output was redirected to a file and there wasn't any yay... however i've also restarted cudaminer with the -q about 4 hours ago and the gpu found a block but nothing new was printed: $ ./cudaminer --algo=scrypt:131072 -l k6x11 -L6 -o 127.0.0.1:30201
*** CudaMiner for nVidia GPUs by Christian Buchner ***
This is version 2014-02-28 (beta)
based on pooler-cpuminer 2.3.2 (c) 2010 Jeff Garzik, 2012 pooler
Cuda additions Copyright 2013,2014 Christian Buchner
LTC donation address: LKS1WDKGED647msBQfLBHV3Ls8sveGncnm
BTC donation address: 16hJF5mceSojnTD3ZTUDqdRhDyPJzoRakM
YAC donation address: Y87sptDEcpLkLeAuex6qZioDbvy1qXZEj4
[2014-09-06 14:03:16] NVML GPU monitoring is not available.
[2014-09-06 14:03:16] 1 miner threads started, using 'scrypt' algorithm.
[2014-09-06 14:03:17] GPU #0: GeForce GTX 660 with compute capability 3.0
[2014-09-06 14:03:17] GPU #0: interactive: 1, tex-cache: 0 , single-alloc: 0
[2014-09-06 14:03:17] GPU #0: 8 hashes / 21.3 MB per warp.
[2014-09-06 14:03:17] GPU #0: using launch configuration k6x11
|
|
|
|
i get 0.26kh/s out of my gtx660 with k6x11 but no blocks where ever found after several hours...
update: cudaminer works indeed, it just doesn't print out that the block was accepted (the "yay!!!"), i can tell because overnight cpuminer just found 5 blocks, but the wallet shows up 10 mined blocks, so i assume the other 5 were mined by the gpu... |
|
|
|
i get 0.26kh/s out of my gtx660 with k6x11 but no blocks where ever found after several hours...
at the same time, the cpu already found 4 blocks with pooler's cpuminer, getting an average of 0.25kh/s out of a i7-3770 (the wallet gives me at most 77h/s).
Very cool. Out of town for the weekend, but will player with cpuminer when I get back. Can you share your startup string for cpuminer? nothing fancy, just the algo selection: --algo=scrypt:131072 |
|
|
|
the "t" kernel if for titan, ie for compute 3.5.
Try the fermi kernels "f" or "F", they should work on your card
Yes! That did the trick. Seeing a hashrate of about 0.03 khash/s, e.g. 30 hashs/sec - virtually identical to my quad-core CPU - as expected. Nice to see that validated. Cassey i get 0.26kh/s out of my gtx660 with k6x11 but no blocks where ever found after several hours... at the same time, the cpu already found 4 blocks with pooler's cpuminer, getting an average of 0.25kh/s out of a i7-3770 (the wallet gives me at most 77h/s). |
|
|
|
Which version of CudaMiner are you using? I'm getting an odd error:
*** CudaMiner for nVidia GPUs by Christian Buchner ***
This is version 2014-02-28 (beta)
based on pooler-cpuminer 2.3.2 (c) 2010 Jeff Garzik, 2012 pooler
Cuda additions Copyright 2013,2014 Christian Buchner
LTC donation address: LKS1WDKGED647msBQfLBHV3Ls8sveGncnm
BTC donation address: 16hJF5mceSojnTD3ZTUDqdRhDyPJzoRakM
YAC donation address: Y87sptDEcpLkLeAuex6qZioDbvy1qXZEj4
[2014-09-05 13:22:39] 1 miner threads started, using 'scrypt' algorithm.
[2014-09-05 13:22:41] HTTP request failed: Failed connect to 127.0.0.1:64096; No
error
[2014-09-05 13:22:41] json_rpc_call failed, retry after 15 seconds
[2014-09-05 13:22:58] HTTP request failed: Failed connect to 127.0.0.1:64096; No
error
[2014-09-05 13:22:58] json_rpc_call failed, retry after 15 seconds
[2014-09-05 13:23:15] HTTP request failed: Failed connect to 127.0.0.1:64096; No
error
user/password/rpcallowip are all set in imacredit.conf and the windows wallet is up and running on the machine.
Any thoughts?
did you also add "server=1"? |
|
|
|
how can i avoid it ending again on the wrong chain if i resync after redownloading the blockchain from scratch?
thank you
Download the blockchain, make a copy of it. If your sync fails, you can go back to the copy and try again. are you saying it is just a 50/50 probability issue? No because more and more people will be on the right chain. There are still some nodes on the broken chain but it should become increasingly rare so you will be less likely to sync with them. ok, then i'll wait some hours before trying to sync again, thank you for explaining smooth. |
|
|
|
how can i avoid it ending again on the wrong chain if i resync after redownloading the blockchain from scratch?
thank you
Download the blockchain, make a copy of it. If your sync fails, you can go back to the copy and try again. are you saying it is just a 50/50 probability issue? |
|
|
|
after starting my wallet it seems to be stuck on block 202651: 2014-Sep-04 13:13:11.279692 [P2P1][36.33.57.101:18080 OUT]Sync data returned unknown top block: 202651 -> 203025 [374 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-04 13:13:33.371112 [P2P3]ERROR /home/skunk/bitcoin/bitmonero/src/cryptonote_core/blockchain_storage.cpp:771 alternative chain have wrong connection to main chain
2014-Sep-04 13:13:33.371288 [P2P3]Block recognized as orphaned and rejected, id = <43e9468e7d2092b07cf1a2d81af36dead969f4403b27388771de414ecc1dad9b>
2014-Sep-04 13:13:33.371414 [P2P3][36.33.57.101:18080 OUT]Block received at sync phase was marked as orphaned, dropping connection did it end on the wrong chain? since the wallet wasn't running during the fork, how can i avoid it ending again on the wrong chain if i resync after redownloading the blockchain from scratch? thank you |
|
|
|
I like the name Napoleon Coin. Small but powerful.  at this point even mon petit sarkozy coin could be fine |
|
|
|
uh? shouldn't the stake amount be the same even if the wallet is not running 24/7? my wallet is running 24/7 since the coin launch, but my staking is considerably less than what your calculator says: i've "mined" 391.3610 coins, last transaction was on 8/5. since then i've got 6.034261 coins from staking which if i divide by 23 days (without counting compound) gives me only 0.26235917391304347826 coins per day (total pos orphan blocks amount is just 0.490665). however your calculator gives me 0.3216 coins/day which is the expected stake with a 30% annual interest... is this just because bad luck? would transferring the entire balance to myself help minting performance? thank you. |
|
|
|
@ david, yes, it's normally addnode instead of connect. But to make sure, prior to the checkpoints and exclusions, connect will ONLY connect to the noted IP, whereas addnode will allow you to connect to as many peers as it can find. That is in fact one way to make a test chain. Get the ip of the other guy's wallet, remove or comment out all addnodes, put in the connect statement for ONLY that wallet, and voila! new chain  Thanks for these explanations, stop believing that I know more than you do 
By the way: I can't compile TEK's new version because it is looking for mingw-specific libraries ( -lboost_system-mgw48-mt-s-1_55 -lboost_filesystem-mgw48-mt-s-1_55 -lboost_program_options-mgw48-mt-s-1_55 -lboost_thread-mgw48-mt-s-1_55). Sure, I could manually edit the makefile, but that's not the point of compiling from source to manually edit and I don't know how to commit a tekcoin-qt-linux.pro file (which should be updated manually everytime the tekcoin-qt.pro file would be updated). I am using Manjaro (Arch-based, not a Debian-based Linux) Makefile:418: recipe for target 'Tekcoin-qt' failed
Can you confirm step 2 and step 4? make sure you ran "qmake tekcoin-qt-linux.pro" an not "qmake tekcoin-qt.pro" |
|
|
|
|
Show Posts
