 Show Posts
|
|
Pages: [1] 2 »
|
@denravonska @natekicks @Mercosity
Thanks guys for the updates. Honestly I just don't have the time to be on multiple platforms (besides here, FB, and sometimes Slack). If you guys could make at least a once a week presence on here, it would be appreciated!!
Same for us  We have naturally and unintentionally streamlined the development process to github and Slack. Beyond that there is also reddit, IRC, Telegram, Facebook, Bitcointalk, Cryptocointalk, Twitter and Steemit, so keeping everyone updated has become a chore. I can try to make a bigger presence here but as of right now the best bet for the most up to date status with the least effort is probably reddit. |
|
|
|
Why is the project so dead price terms wise? Is there any development happening in this project? Is there anything I'm missing? I do understand the BTC rally has affected the price of all alts, but GRC seems dead.
Even the dev forum seems lacking now. These guys have the potential to be in the top 10 but they're doing F all. Nah, we just hang on different platforms The day to day communication is done on Slack while the more permanent work is done on Github. See the staging branch for what's being tested for the next release, and the development branch for the changes coming in the release after. I wrote a summary covering the main changes coming up in the Gridcoin 3.7.0.0 release. |
|
|
|
That does not make any sense. Can you double check that you are on 3.6.2.0? Besides a now removed low disk space check I cannot find any place where the wallet would shut down on its own.
Edit: If it is 3.6.2.0 then please post debug.log and debug2.log the next time it happens.
I did THAT before the previous post - it's 3.6.2.0 Also, as I said, it REBOOTED not "shut down". I saw it resynching after it rebooted the second time (the wallet, not the entire machine, rebooted) but didn't see the first time when it happened (I was asleep). I'll keep the debug logs in mind if it happens again soon. Alright, no need to yell. I'll do some more investigation to see if there are any other ways for the wallet to spontaneously reboot. |
|
|
|
I'm also getting tired of the "every day or two" wallet reboots in the current version - though that was supposedly fixed MONTHS ago, more than a bit irritating that bug is BACK AGAIN.
Are you still having problems with 3.6.2.0? That one was just released a few days, not months, ago. 2 reboots yesterday alone, though it's usually been one every other day or so for the past 2-3 weeks. Did NOT have this issue for a long time (the "months ago" comment), but now it has returned. That does not make any sense. Can you double check that you are on 3.6.2.0? Besides a now removed low disk space check I cannot find any place where the wallet would shut down on its own. Edit: If it is 3.6.2.0 then please post debug.log and debug2.log the next time it happens. |
|
|
|
Waiting for new wallet to be released. The one I'm using right now(3.6.2.0) crashes every 1,2 days, and does not stake anymore  EDIT:I'm sorry it was 3.6.1.0 that I was using, and I just updated to 3.6.2.0 I expect it won't crash with 3.6.2.0. Sorry to post wrong information. phew, you had me worried there  Thanks for the update. |
|
|
|
Why doesn't the wallet AUTOMATICALLY stake instead of having to do that stupid "unlock for staking" every bloody time the wallet is started up?
It gets OLD having to "unlock for staking" every bloody time the wallet is started up.
You can if you want to. http://wiki.gridcoin.us/Wallet_Auto-unlock_for_staking Thanks for posting the work-around. Still doesn't explain why a work-around is needed though. Because you encypted the wallet with a password. In order to do modifications to it (spend a UTXO to stake) you have to decrypt it with the same password. If you prefer not using the auto unlock option you can always use the wallet unencrypted. I'm also getting tired of the "every day or two" wallet reboots in the current version - though that was supposedly fixed MONTHS ago, more than a bit irritating that bug is BACK AGAIN.
Are you still having problems with 3.6.2.0? That one was just released a few days, not months, ago. |
|
|
|
Why doesn't the wallet AUTOMATICALLY stake instead of having to do that stupid "unlock for staking" every bloody time the wallet is started up?
It gets OLD having to "unlock for staking" every bloody time the wallet is started up.
You can if you want to. http://wiki.gridcoin.us/Wallet_Auto-unlock_for_staking |
|
|
|
I am one of the Top 20 research magnitude producers in Gridcoin (top 16 if you exclude the 3 GRCPOOL entries that aren't single producers, and sometimes in recent times Top 15 COUNTING them).
In order to stake at least MONTHLY on a semi-reliable basis, I have to keep about a month worth of coin in the wallet - and I HATE that they're just sitting there USELESSLY instead of my being able to use them to add more hardware.
(don't even MENTION "staking income", I get better return on that out of a SAVINGS ACCOUNT out of my credit union - BEFORE I have to factor in the GRC price drop of the last couple-three months).
For folks with small research numbers, they'd have to keep YEARS of coin on hand to get payouts at all (don't forget the 6 months "lose it if you don't stake by then" limit).
I probably should move my wallet to a LINUX machine - though the Win7 machine it's on now is fairly reliable, generally only needs a reboot every couple months or so since I don't DO a lot on it.
However, I went with NO wallet crash/reboots for MONTHS prior to the recent wallet changes, the last two-three weeks I have been seeing a wallet crash/reboot on average every other DAY.
The last weeks issues were due to old, failing fallback mechanisms. If you upgrade to 3.6.2.0 it should run much more stable. |
|
|
|
That's great news. Windows was throwing a Low Memory error for me earlier today, telling me to close the GRC wallet. I have 16GB of RAM, I shouldn't be getting errors like this at idle. We'll see how the update treats me. I think you got hit by this one which happened frequently when trying to get back to the right chain. https://github.com/gridcoin/Gridcoin-Research/issues/261It's been fixed and it looks like when can schedule 3.6.2.0 for tomorrow. |
|
|
|
With the previous stake engine researchers with high mag brought the difficulty (and thus approximated network stake weight) way way up due to the mag stake multiplication issue. This made it harder for small researchers to stake since they were not only competing against the large holders but also the multiplied large maggers. If that makes sense.
OK, I can see that as being a good thing for the smaller participants in a way, but having to have YEARS worth of their average monthly earnings tied up "staking" just to get a payout once a month or so for the small folks STILL seems like a very bad idea and contradictory to the CORE stated intent of Gridcoin to "support BOINC research". That is indeed less than ideal. Hopefully we can reach an agreement soon on which route to take so we can start working. |
|
|
|
Btw, with your mag out of the network stake weight it probably got easier for small researchers to stake with V8 No clue what you mean by that? With the previous stake engine researchers with high mag brought the difficulty (and thus approximated network stake weight) way way up due to the mag stake multiplication issue. This made it harder for small researchers to stake since they were not only competing against the large holders but also the multiplied large maggers. If that makes sense. Unlike Curecoin/Foldingcoin (where one of the DEVELOPERS is actively working to depress the profitability through his actions to the point of driving folders AWAY including ME over the next couple days), I'm still active in Gridcoin/BOINC.
I wonder how Moo folks would feel if I pointed my Folding farm at BOINC for a few days..... 9-)
Now is a great time to be a part of Gridcoin. The wallet development is booming and there is a ton of future improvements being discussed. Anything from the rebranding to porting the NeuralNet to Linux and improving it. |
|
|
|
Good or not, it had to be released to tackle the security issues. And also, remember that before V8 you were stake competing against other peoples' mag. pomegranate currently has 12667 mag and dutch has 4562. Split either of their wallets into 1 GRC UTXOs and what's going to happen to the net weight? Or even just 100 UTXOs each? Additionally, most of the people I've talked to stake about as much as with V3. The crashes (which were actually fallback restart attempts) have been fixed in the version which was just merged to staging for release test. I would be surprised if we even see a tiny increase in the net weight after it is released. I'm not worried about staking daily - but having to keep ANY coin around rather than being able to use it to pay electric bills or fund expansion is VERY irritating - and having to keep weeks or months worth of coin on hand to even manage to stake once in a WEEK is excessive. That's speaking as one of the biggest Gridcoin earners in existence (Like I said, I'm Top 15 on magnitude) - folks that only pull in a couple coins a day ARE going to need years worth of income to stake more often than the "6 month cutoff" which is a TOTAL WASTE for them. The point is that the whole "have to keep tons of GRC around just to be ABLE to get paid for your RESEARCH WORK" is total violation of the whole basic concept that Gridcoin is supposed to be SUPPORTING THE RESEARCHERS. That I agree on. Personally I'm not too fond of the whole PoR+PoS marriage either and I would also like to see a more streamlined way to reward the researchers, but we need to reach a consensus on where to go from here. Like I said, there are several proposals being worked on, for example staking with your beacon, dividing your mag up to all UTXOs connected to your beacon address, or simply rewarding all researchers in superblocks. Btw, with your mag out of the network stake weight it probably got easier for small researchers to stake with V8 |
|
|
|
This will probably be the last time I try to explain this. You do NOT need $1000 worth of GRC to stake every day. With the current net weight you are estimated to stake daily with a balance of 10k GRC, which is closer to $322. If you actually have a need to stake daily. If you can get away with weekly staking you need $46 worth of GRC. Take a look at my stats for before and after V8 (2017-09-01). IIRC the days before and after averaged to exactly the same amount of stakes. Okay, I admit my rough estimation was too rough. But the current net weight staying low because the buggy windows wallet crashes all the time, people are too lazy to restart it, once it get fixed you will need far more than 300 bucks. I am afraid of what's gonna happen when team requirement will be no longer necessary... so in mine opinion v8 stake engine is not good and something new should be created. Good or not, it had to be released to tackle the security issues. And also, remember that before V8 you were stake competing against other peoples' mag. pomegranate currently has 12667 mag and dutch has 4562. Split either of their wallets into 1 GRC UTXOs and what's going to happen to the net weight? Or even just 100 UTXOs each? Additionally, most of the people I've talked to stake about as much as with V3. The crashes (which were actually fallback restart attempts) have been fixed in the version which was just merged to staging for release test. I would be surprised if we even see a tiny increase in the net weight after it is released. |
|
|
|
Still waiting for a reply from anyone that has gotten a GRC payout in the last *3 weeks*.
Gridcoin has got me very close to the point of saying "forget about it, it's NOT paying out" and shifting back to working directly with the Distributed.Net project instead of with BOINC at all.
Don't even get me started on the BROKEN current BOINC client.
Oh, it happened after developers removed research weight from formula, you need something like 1000$ in your wallet now to stake every day. To get more accurate numbers just take a look at some users who stake every day. This will probably be the last time I try to explain this. You do NOT need $1000 worth of GRC to stake every day. With the current net weight you are estimated to stake daily with a balance of 10k GRC, which is closer to $322. If you actually have a need to stake daily. If you can get away with weekly staking you need $46 worth of GRC. Take a look at my stats for before and after V8 (2017-09-01). IIRC the days before and after averaged to exactly the same amount of stakes. The bug with the old stake engine was that the magnitude was applied to each UTXO regardless of its size. This meant that a strong researcher could split their assets into tiny UTXOs and massively increase their stake weight which posed a great risk of double spending. For example, with my current balance of 54k GRC and 85 magnitude I have around 54k stake weight. With the previous engine I could abuse this and get 4.6 million stake weight. And, no, you can't just apply it to one UTXO since it cannot be verified on the receiver end. We are looking into alternative, more secure ways of either rewarding researchers passively or use a secure way of applying the magnitude as stake weight. Tomas has written about some of the proposals in the Gridcoin Github wiki: https://github.com/gridcoin/Gridcoin-Research/wiki/DPoR-Payments. Edit: If you want to know more about this or the currently discussed fixed size block rewards change then feel free to join us on Slack where we are very active. |
|
|
|
the algos which gonna fail
miner stops after checking first block , crash is then reported by miner as illegal instruction
3.5.11 tested , same results as in 3.5.10 nothing changes for Amd cpu
Thanks for testing. I think I've done all I can to get thosre old AMDs to work. An illegal instruction usually means the CPU hasn't implemented it, often when trying to ue AES instructions on a CPU that doesn't support AES. In this case it appears these AMD CPUs don't have the full SSE2 implementation. Even if there was a way for the compiler to detect this condition the result would be a build without any optimizations, ie it would be the same as cpuminer-multi. My recommendation is to use cpuminer-multi on those algos. Oh, I didn't realize my Athlon64 was _that_ old, failing at SSE3 instructions. Reverting back to 3.4.12 then |
|
|
|
Thanks. That was a lot of work, very much appreciated. It will help with my testing.
I don't often test for these architectures.
Edit:
I've tested the algos that failed for you on a i7-6700K compiled with gcc 4.8 using -march=core2 and they work.
You can retest hmq1275 in the next release. Some of the other algos have the same bug that caused x11 to crash
on Windows (The x11 bug affected only AVX2, not an issue on your x2). How did those algos fail?
Did the miner crash? Produce rejects? Do something else?
I'm trying on an Athlon64 X2 4000+ with gcc-5.2.1 using CFLAGS "-fomit-frame-pointer -Ofast -march=core2 -Wall". I made a super quick and dirty Python script which assumes that the algo works if it can run in the benchmark for 10 seconds: - axiom: Fail - bastion: Fail - blake: OK - blakecoin: Fail - blake2s: OK - bmw: Fail - c11: Fail - cryptolight: OK - cryptonight: OK - decred: OK - deep: OK - drop: OK - fresh: Fail - groestl: OK - heavy: Fail - hmq1725: Fail - hodl: OK - keccak: Fail - lbry: OK - luffa: Fail - lyra2re: OK - lyra2rev2: OK - lyra2z: Fail - lyra2zoin: Fail - m7m: OK - myr-gr: OK - neoscrypt: OK - nist5: OK - pluck: Fail - pentablake: OK - quark: OK - qubit: Fail - scrypt: OK - scryptjane:nf: Fail <- Not sure how to test this. - sha256d: OK - shavite3: Fail - skein: OK - skein2: OK - timetravel: Fail - vanilla: Fail - veltor: Fail - whirlpool: Fail - whirlpoolx: Fail - x11: Fail - x11evo: Fail - x11gost: Fail - x13: Fail - x14: Fail - x15: Fail - x17: Fail - xevan: Fail - yescrypt: Fail - zr5: OK When failing it's always "Illegal instruction (core dumped)". CPU:
CPU features: SSE2
SW built on Mar 1 2017 with GCC 5.2.1
SW features: SSE2
Algo features: SSE2
Start mining with SSE2
|
|
|
|
Looks like it was some china and russian farms moving around miners. Seems ok now?
It still refuses to mine on zpool while other pools work, and the miner count keeps increasing. |
|
|
|
Scrypt port dropping out like crazy
bfgminer/5.4.2 c=BTC,d=512 scrypt 512
bfgminer/5.4.2 c=BTC,d=512 scrypt 512
...
Just now?? the server hasn't crashed or anything.... been going ~24h since last restart.... I have also been having issues the past couple of days: [2017-02-11 06:27:49] Checking main pool: ^P^K<9C>
[2017-02-11 06:27:49] Stratum connection failed: Could not resolve host: http(null)
[2017-02-11 06:28:49] Checking main pool: `<F5><9B>
[2017-02-11 06:28:49] Stratum connection failed: Could not resolve host: http(null)
My stats says I currently have 28 scrypt miners connected I'm not alone though. The total number of scrypt miners went from 900 to 6000 and is now hovering at 9000. |
|
|
|
|
Are there any improvements to make by building it with gcc-6 over gcc-4?
|
|
|
|
|
