hello nexus community... nice to see our early mined nxs stash going to the moon by almost x50 increasing it's value in the last 12 months  this bought nexus back to my attention and since i wonder how many nxs we can mine right now by pushing some hashes to the wallet (solo mining is still the only option for the gpu channel, isn't it?), i've stopped the etherminers and fired up the very same skminer i've used to mine nexus a couple of years ago: ***** skMiner for nVidia GPUs by djm34 *****
This is version v0.2
based on ccMiner by Christian Buchner and Christian H. 2014 ***
and on primeminer by Videlicet
Copyright 2014 djm34
BTC donation address: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze
CSD: 2S2pCpRXyb8Lpre52U3Xjq2MguSdaea5YGjVTsJqgZBfL2S24ag
and started generating a total of more than 2gh/s to a full synchronized wallet for about 10 hours without finding any block...  is the gpu channel that difficult or is the miner just obsolete? since the op only lists this as source code for the nvidia miner, why does it not even build under linux with syntax errors and missing files? also the amd miner cannot be compiled under linux, is nexus becoming a windows only currency? that would be sad imho... thank you |
|
|
|
 should i worry? that's after upgrading to latest v1.10.1 linux wallet... Did you read the upgrade instructions? "Linux users who upgrade from 1.10.0 will have to delete all files (but not subdirectories!) in ~/.config/byteball/Default in order to get rid of the annoying (but harmless) popup about profile format. This is because we had to revert to an older version of nwjs to address #201. Backup before deleting." ok, thank you. |
|
|
|
should i worry? that's after upgrading to latest v1.10.1 linux wallet... |
|
|
|
|
hello, i've sent all my bytes to a new mutidevice wallet, will it be still a candidate for the next airdrop or shall i do something?
thank you
|
|
|
|
hello, sorry if i'm missing something obvious but if: $ ./dcrctl --wallet listaccounts
{
"default": 1475.0859285,
"imported": 0
}
$ ./dcrctl --wallet getaccountaddress default
DsbSffXRkKPhX9LsajXceBg5WAwhemrTyoL then why does the block explorer show a 0 balance? thank you... From devs on slack: "well the default account can have millions of addresses so looking up a single address on the block explorer will never work unless you send your entire balance to that single address" "getaccountaddress simply doesn't do what that user expects. it returns the next address from the acccount that hansn't been used yet so of course the block explorer will show a 0 balance" oh, ok, thank you... i suppose there's no way to check the whole balance without querying directly the wallet then... |
|
|
|
hello, sorry if i'm missing something obvious but if: $ ./dcrctl --wallet listaccounts
{
"default": 1475.0859285,
"imported": 0
}
$ ./dcrctl --wallet getaccountaddress default
DsbSffXRkKPhX9LsajXceBg5WAwhemrTyoL then why does the block explorer show a 0 balance? thank you... |
|
|
|
|
hello, my wallet last mint time was on 30 may and it's fully synced with almost 2 billion sprts... what's the deal?
|
|
|
|
i'd 534 shf on shift's web wallet on this address and about 2 moths ago they were stolen by somebody, how is it possible? my passphrase was secure with many others on my desktop and shift is the only cryptocurrency i'm missing. i suggest you to check about security holes into the web wallet. i guess there's no chance to recover the loss... If someone stole your Shift out of your wallet, you could at least see where the funds were sent using the block-explorer. The FIRST thing you should do is join the SHIFTNRG group on Ryver. There are a lot of helpful members and devs that can assist you. do i need an invitation? |
|
|
|
i'd 534 shf on shift's web wallet on this address and about 2 moths ago they were stolen by somebody, how is it possible? my passphrase was secure with many others on my desktop and shift is the only cryptocurrency i'm missing. i suggest you to check about security holes into the web wallet. i guess there's no chance to recover the loss... |
|
|
|
|
hey!
could somebody at polo please give a look to ticket #113134?
i've opened it 3 days ago and got no answers yet...
thank you
|
|
|
|
hello! i had my dcr wallet offline for a long while because i've lost connection to the host where it's installed. once the host went online again, i've restarted the wallet and saw how all my live tickets went missed, amen... i didn't re-enable staking, however after about two months from restart i notice most of my budget is still locked: $ ./dcrctl --wallet getstakeinfo
{
"blockheight": 117763,
"poolsize": 40866,
"difficulty": 99.33280417,
"allmempooltix": 0,
"ownmempooltix": 0,
"immature": 0,
"live": 0,
"proportionlive": 0,
"voted": 285,
"totalsubsidy": 498.5092128,
"missed": 56,
"proportionmissed": 0.16422287390029325,
"revoked": 13,
"expired": 0
}
$ ./dcrctl --wallet getstakeinfo
{
"blockheight": 117763,
"poolsize": 40866,
"difficulty": 99.33280417,
"allmempooltix": 0,
"ownmempooltix": 0,
"immature": 0,
"live": 0,
"proportionlive": 0,
"voted": 285,
"totalsubsidy": 498.5092128,
"missed": 56,
"proportionmissed": 0.16422287390029325,
"revoked": 13,
"expired": 0
}
$ ./dcrctl --wallet getbalance "*" 1 all
1445.22367482
$ ./dcrctl --wallet getbalance "*" 1 locked
1038.48773844
why? when can i expect my dcr to get unlocked? thank you |
|
|
|
The snapshots for the 3rd round will be taken on the Full Moon of March, on March 12 at 14:54 UTC. In this round, you receive:
- 62.5 MB for every 1 BTC of proven balance
- 0.1 new bytes for every 1 byte you own at the moment of the snapshot
i've applied since the 1st round and before this last 2rd round it stated that the next rounds would use the snapshots of this 2nd round, but now it states that there will be more snapshots... so my question is: if i move my bitcoins around, the bytes i'll get will be proportional to my 2nd round snapshot balance or to the balance when the 3rd distribution begins? The idea is quite simple, just make sure your linked addresses have your funds when the snapshot occurs, whatever you do before or after with your funds, doesn't matter ... but if i decide to spend my btc, my part of the byteball distribution will decrease... will the 4th and onward distributions still be based on new time snapshots from btc accounts?thank you yep. ok, then i'll give up, leaving btc aging in a wallet doesn't make any profit... |
|
|
|
The snapshots for the 3rd round will be taken on the Full Moon of March, on March 12 at 14:54 UTC. In this round, you receive:
- 62.5 MB for every 1 BTC of proven balance
- 0.1 new bytes for every 1 byte you own at the moment of the snapshot
i've applied since the 1st round and before this last 2rd round it stated that the next rounds would use the snapshots of this 2nd round, but now it states that there will be more snapshots... so my question is: if i move my bitcoins around, the bytes i'll get will be proportional to my 2nd round snapshot balance or to the balance when the 3rd distribution begins? The idea is quite simple, just make sure your linked addresses have your funds when the snapshot occurs, whatever you do before or after with your funds, doesn't matter ... but if i decide to spend my btc, my part of the byteball distribution will decrease... will the 4th and onward distributions still be based on new time snapshots from btc accounts? thank you |
|
|
|
The snapshots for the 3rd round will be taken on the Full Moon of March, on March 12 at 14:54 UTC. In this round, you receive:
- 62.5 MB for every 1 BTC of proven balance
- 0.1 new bytes for every 1 byte you own at the moment of the snapshot
i've applied since the 1st round and before this last 2rd round it stated that the next rounds would use the snapshots of this 2nd round, but now it states that there will be more snapshots... so my question is: if i move my bitcoins around, the bytes i'll get will be proportional to my 2nd round snapshot balance or to the balance when the 3rd distribution begins? |
|
|
|
Videlicet, latest nexus cli wallet compiled from head is segfaulting under linux: $ ./nexus -debug -logtimestamps -printtoconsole
Nexus version 0.2.2.3 - LLD Stable (January 5th, 2017)
Default data directory /home/skunk/.Nexus
Initializing Unified Time...
***** Unified Time Initialized to 0
Loading addresses...
dbenv.open LogDir=/home/skunk/.Nexus/database ErrorFile=/home/skunk/.Nexus/db.log
0 Host: node1.nexusearth.com
DNS Seed: 104.192.170.130
Added 104.192.170.130:9323 from 104.192.170.130: 0 tried, 1 new
1 Host: node1.mercuryminer.com
DNS Seed: 52.63.26.48
20 Host: node7.mercuryminer.com
DNS Seed: 54.173.118.111
Added 54.173.118.111:9323 from 54.173.118.111: 0 tried, 17 new
21 Host: node7.nxs.efficienthash.com
DNS Seed: 35.167.17.105
Added 35.167.17.105:9323 from 35.167.17.105: 0 tried, 18 new
22 Host: node8.nexusearth.com
23 Host: node8.mercuryminer.com
DNS Seed: 52.57.54.37
Added 52.57.54.37:9323 from 52.57.54.37: 0 tried, 19 new
24 Host: node8.nxs.efficienthash.com
DNS Seed: 52.34.127.167
Added 52.34.127.167:9323 from 52.34.127.167: 0 tried, 20 new
25 Host: node9.nexusearth.com
26 Host: node9.mercuryminer.com
27 Host: node9.nxs.efficienthash.com
Loaded 1056 addresses
addresses 18ms
Loading block index...
Nexus Network: genesis=0x00000bb8601315185a0d nBitsLimit=0x8007ffff nBitsInitial=0x8001ffff nCoinbaseMaturity=100
DNS Seed: 52.34.189.250
Added 52.34.189.250:9323 from 52.34.189.250: 17 tried, 1040 new
28 Host: node10.nexusearth.com
29 Host: node10.mercuryminer.com
DNS Seed: 58.6.103.173
30 Host: node10.nxs.efficienthash.com
DNS Seed: 52.14.2.93
Added 52.14.2.93:9323 from 52.14.2.93: 17 tried, 1041 new
31 Host: node11.nexusearth.com
32 Host: node11.mercuryminer.com
DNS Seed: 23.92.86.148
33 Host: node11.nxs.efficienthash.com
DNS Seed: 35.154.123.88
Added 35.154.123.88:9323 from 35.154.123.88: 17 tried, 1042 new
34 Host: node12.nexusearth.com
35 Host: node12.mercuryminer.com
DNS Seed: 52.27.153.235
36 Host: node12.nxs.efficienthash.com
DNS Seed: 54.94.154.228
Added 54.94.154.228:9323 from 54.94.154.228: 17 tried, 1043 new
37 Host: node13.nexusearth.com
38 Host: node13.mercuryminer.comnode13.nxs.efficienthash.com
39 Host: (null)
Segmentation fault
while checking out 668cec832811d60f3ca270eb1ceeff65eac42a13 makes it work again... since commit d35aea2f92264ff6e38ec3e64c3219ce158e9577 is a trivial seed nodes update, is it possible that some of the new nodes is the cause? |
|
|
|
strange, i can reproduce it with "-a blake", "-a blakecoin" beside "-a decred" (even with --benchmark)
blake2s, vanilla and other algos are fine
well, i'll stick with alexis78's ccminer for decred...
Are you waiting long enough for the cards to start? I've seen cards take up to 2 minutes before they report any hash. no, didn't wait 2 minutes but even, with alexis78's miner all cards starts immediately... |
|
|
|
|
strange, i can reproduce it with "-a blake", "-a blakecoin" beside "-a decred" (even with --benchmark)
blake2s, vanilla and other algos are fine
well, i'll stick with alexis78's ccminer for decred...
|
|
|
|
never seen a problem like that...
maybe it happens just on linux? i don't have windows rigs to try... |
|
|
|
hi, just to inform that current head (on decred algo and since this commit) only mines on one random card out of 5 installed: I am not seeing this with a pair of 980's. I just did a fresh build 2 days ago. i can reliably reproduce the issue on a 5x950 and a 6x970 rig, on both rigs only one card starts hashing (even if the cards are specified with the -d flag or if the number of cards are specified with the -t flag) I will say that yiimp site is only seeing 1 card for the benchmarks. It does show total hash correctly.
it has nothing to do with yiimp, i'm not mining there... |
|
|
|
|
Show Posts
