Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jun 13 2019 08:02
    @jaspervdm banned @matrixbot
  • May 06 2018 21:29
    User @ignopeverell unbanned @maesitos
  • May 06 2018 00:41
    @ignopeverell banned @maesitos
daldwinc
@daldwinc
awesome, that is working
and for others: dont forget to disable cpu mining if you want. It probably degrades performance in a GPU rig
daldwinc
@daldwinc
@tromp Would you expect similar graph rates between cuckarood29 and cuckaroom29 ?
I was getting 20 before, and now 6
Photis Phudge
@photis
Where do you read that?
And what kind of cards are we talking?
John Tromp
@tromp
Cuckaroom is expected to be 50-60% slower than Cuckarood
and have half as many 42-cycles
daldwinc
@daldwinc
@photis I am just looking at my hashrate graph on grinmint
I have two 2070 and one 1070 Ti
image.png
Blade Doyle
@bladedoyle
@tromp Have you communicated the new POW speed changes to all PPS pools so they can adjust appropriately prior to the fork?
It’s very disruptive for these types of POW changes to be made. Is it not possible for you to make HF changes that are less disruptive and don’t require intimate knowledge of your changes and manual updates to all the pools?
daldwinc
@daldwinc
@quentinlesceller Will the payout logic on grintmint be adjusted to reflect the differences in PoW ?
Quentin Le Sceller
@quentinlesceller
It already is
daldwinc
@daldwinc
by changing PoW, im only earning a third of what I was before?
image.png
John Tromp
@tromp
@bladedoyle you mean pool operators can't be bothered to read any info on a PoW change? how are they supposed to validate shares if they refuse to be informed about the new PoW?
Btw, I did send out a big warning message on keybase pool emergencies channel
Quentin Le Sceller
@quentinlesceller
Looking at our big miners that's not realy the case. Send me your login. Also what was your hashrate before and now?
Blade Doyle
@bladedoyle
Ok, if you think this type of change is appropriate, and you have done due diligence to notify the community then we are good.
I personally think its sub-optimal to make pow changes altering the GPS at every fork, but if thats the best you can do then thats what we get.
I dont think I saw any details about 50-60% slower than Cuckarood & half as many 42-cycles in the release notes (or anywhere else before your post here a few hours ago. Maybe you made it clear and I just missed it
John Tromp
@tromp
the release notes pointed to my forum post which detailed these slowdowns
John Tromp
@tromp
the reference miner has been available for months for anyone to benchmark
btw, the speed of solvers doesn't matter that much because AR_scale always compensates
the expected nr. of solutions does matter for gps estimations, as detailed in my post
Blade Doyle
@bladedoyle
@tromp 👍
Blade Doyle
@bladedoyle
@mcdallas - please check grin.report when you get a chance.
zillabytes
@zillabytes
How to mine this coin, im new here
xiaojay
@xiaojay
Hello, Niffler wallet v0.5.0 for grin3 released.
Please upgrade now
https://github.com/grinfans/Niffler/releases/tag/v0.5.0
aleqx
@aleqx

@bladedoyle @tromp to be fair, I kind of agree with both of you - I also find it annoying that the GPS changes (especially when it doesn't change with exactly known values, like this time, since halving the number of solutions in a cycle isn't the only factor affecting GPS in the new c29m variant), but I did find all the needed info on the forum in the post above which was available for quite a while before the fork.

I do however wish there was a more proper channel to disseminate this info. A forum post is hardly the appropriate manner. In my opinion, this should, at the very least, be in the README.md file and wiki of the main cuckoo repo, and with very visible links straight from the main GRIN website in big bold letters "Cuckoo Cycle mining algo changes", also with links to the docs of the previous versions, so that pool ops, miners, etc can understand what will change and can prepare the pools.

It's not really cool to have to use Google to find out these things ...

lehnberg
@lehnberg
@aleqx I think that’s a great idea. If you would consider submitting a pull request to the repo with an improved README, I could help with reviewing it. :+1:
aleqx
@aleqx
thanks, but I'll leave that to @bladedoyle or someone else or @tromp himself
davesie
@davesie
John Tromp
@tromp
use forum.grin.mw from now on
davesie
@davesie
Thank you!
samholmes
@samholmes
Any idea why my Grin++ client would not be connected?
samholmes
@samholmes
Is tor supported in grin-wallet 3.x?
invertedcrosss
@invertedcrosss_twitter
Yes TOR is supported!
David Burkett
@DavidBurkett
@samholmes A few people are having connection issues with 0.7.3. I'm tracking down the issue now, and will release a new version once fixed. Keep an eye out for 0.7.4
samholmes
@samholmes
I’ll keep an eye out
Is TOR supported at exchange withdraw for any exchanges yet?
David Burkett
@DavidBurkett
@samholmes Not yet, but here's a way you can put your tor address to use: https://forum.grin.mw/t/an-easier-way-to-receive-grins/6959
samholmes
@samholmes
Interesting. Though, exchanges will most likely support TOR I’m going assume. If they don’t, then what does everyone think about the idea of implementing a TOR client within grin-wallet itself?
Exchanges typically update wallet client versions, so by building a TOR client within the wallet client itself, there is no excuse for an exchange to not support the TOR protocol. Furthermore, the newer wallet versions could drop support for transactions over HTTP altogether
E Lokk
@elokk1111_twitter
I tried to send some funds from my grinmint account to Niffler, connection was lost, transaction cancelled on Niffler. Where do the funds go at that point?
David Burkett
@DavidBurkett
The cloud
The transaction will expire on Grinmint, and they'll credit your account
E Lokk
@elokk1111_twitter
just for clarification: grinmint says "sent", Niffler "cancelled"
E Lokk
@elokk1111_twitter
updated wallet to newer version, fixed problem😁