Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Apr 07 00:51
    dagonharett closed #3192
  • Apr 07 00:51
    dagonharett commented #3192
  • Apr 06 17:35
    antiochp edited #3268
  • Apr 03 15:38
    lehnberg edited #3288
  • Apr 03 15:37
    antiochp edited #3288
  • Apr 03 13:19
    jaspervdm closed #3290
  • Apr 03 10:44
    antiochp commented #3290
  • Apr 03 10:42
    antiochp commented #3290
  • Apr 03 10:41
    antiochp commented #3290
  • Apr 03 05:21
    HatemAMA opened #3290
  • Apr 02 21:15
    lehnberg labeled #3289
  • Apr 02 21:14
    lehnberg labeled #3288
  • Apr 02 21:14
    lehnberg labeled #3286
  • Apr 02 21:09
    lehnberg milestoned #3289
  • Apr 02 21:09
    lehnberg labeled #3289
  • Apr 02 21:09
    lehnberg assigned #3289
  • Apr 02 21:09
    lehnberg labeled #3289
  • Apr 02 21:09
    lehnberg opened #3289
  • Apr 02 21:07
    lehnberg opened #3288
  • Apr 02 21:06
    lehnberg milestoned #3288
lehnberg
@lehnberg

@DavidBurkett I could definitely be convinced to move the meetings to keybase. Reason we've been reluctant to do it so far is that we've had a big group of people here and wouldn't want to make the meetings less visible, but perhaps it's time to start making a more serious effort to move over main comms over to Keybase?

Gitter is pretty awful. I read that their desktop/mobile apps were getting less frequent updates, so I started using it in the browser instead, but it's just as bad.

David Burkett
@DavidBurkett
Yea, gitter is unusable on an android, and buggy AF on Windows. Keybase works quite well on Windows, Mac, Ubuntu, and Android. Keybase is far from perfect, but imho, it's worth the effort of transitioning. We all have more than enough messaging apps to monitor.
lehnberg
@lehnberg
@energyburn there wasn't, but I just created grincoin#dev and grincoin#crypto for good measure.

If I read the Keybase documentation correct, and if you've got Keybase installed, try running this from your terminal:

keybase chat join-channel grincoin '#dev'
keybase chat join-channel grincoin '#crypto'

Please report back if it works!

David Burkett
@DavidBurkett
That works on mac
lehnberg
@lehnberg
wicked
@DavidBurkett will add to governance meeting agenda next week a point on switching meeting locations
David Burkett
@DavidBurkett
Thanks!
lehnberg
@lehnberg
done
Joseph Goulden
@JosephGoulden
I would also prefer meetings to be on keybase. Don't really like that conversation is split between here and there.
Yeastplume
@yeastplume
:+1: for moving to keybase
Jason Comito
@jcomito
anyone know, does keybase work okay with Brave browser?
David Burkett
@DavidBurkett
@jcomito There's no web version. It requires installing the client, unfortunately
Antioch Peverell
@antiochp
making some progress on the Changelog for 3.0.0 here mimblewimble/grin#3166
also feel like we are in a really good shape with respect to fast sync stability (current master, soon to be 3.0.0 beta.2)
its a lot better than 2.1.1 put it that way
lever
@1971192997
hi there How are tx fees calculated?
lever
@1971192997
got it, thanks
Quentin Le Sceller
@quentinlesceller
@tromp could you fix the merge conflict here mimblewimble/grin-miner#231 ?
John Tromp
@tromp
will take a look
Quentin Le Sceller
@quentinlesceller
:+1:
John Tromp
@tromp
should be good now?!
Quentin Le Sceller
@quentinlesceller
Yes it is :)
Quentin Le Sceller
@quentinlesceller
@tromp trying to build latest Cuckaroom plugin but getting:
/home/op/mimblewimble/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckaroom/mean.cu(148): warning: variable "sizeC" was declared but never referenced

/home/op/mimblewimble/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckaroom/mean.cu(534): error: expected a comma (the one-argument version of static_assert is not enabled in this mode)

/home/op/mimblewimble/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckaroom/mean.cu(535): error: expected a comma (the one-argument version of static_assert is not enabled in this mode)

/home/op/mimblewimble/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckaroom/mean.cu(536): error: expected a comma (the one-argument version of static_assert is not enabled in this mode)

/home/op/mimblewimble/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckaroom/mean.cu(537): error: expected a comma (the one-argument version of static_assert is not enabled in this mode)
Issue opened here mimblewimble/grin-miner#232 with complete error log
John Tromp
@tromp
taking a look
John Tromp
@tromp
try latest cuckoo commit
Quentin Le Sceller
@quentinlesceller
Ok
Quentin Le Sceller
@quentinlesceller
Looking good thanks !
Blade Doyle
@bladedoyle
It seems like grin discussions are bifurcating. Gitter, discord, keybase, telegram, more? Its hard to even find all of them, harder to try to check them all.
energyburn
@energyburn
Consequences of decentralization?
Blade Doyle
@bladedoyle
Now there appears to be several different parallel keybase groups? There are grincoin .teams.node_dev #general and grincoin.teams.wallet_dev #general and also grincoin #dev , and grincoin #general, etc.
We have almost as many chat groups as API versions :-/
johndavies24
@johndavies24
lol, i agree, hard to keep up
Quentin Le Sceller
@quentinlesceller
Floonet HF latest estimation: 2019-12-22 22:25:01
lehnberg
@lehnberg

I agree @bladedoyle there are many teams and channels. The intention when we set it up was to allow wallet dev and node dev work to proceed more independently, possibly with different people engaging where they were more interested.

Now after it’s been running for a while we can ask ourselves whether it’s really necessary at this stage and whether it would be more beneficial for development work to have a single team with different channels instead?

Dunno, I can see merit to both approaches tbh. At least now that we’ll try to migrate gradually away from gitter we’ll have one place less to check!

John Tromp
@tromp
Floonet HF latest estimation: a few minutes ago
phyro
@phyro
it forked?
John Tromp
@tromp
sure did
lever
@1971192997
sorry to bother you up : grin-wallet3.0beta2 init_send_tx what is the token?
i send ""token":null" but the responce is ""message": "ExtraNamedParameter token""
phyro
@phyro
curl --user grin:supersecretpw -i http://localhost:3413/v2/owner/get_status
HTTP/1.1 404 Not Found
What am I missing? I'm assuming I have to create .api_secretwhere the binary is?
phyro
@phyro
the api.md says that the password is in .api_secret
phyro
@phyro
the subcommands on grin client work though. Btw, is it expected that out of 20 peers I'm connected to, 9 of them are on 2.X version?
phyro
@phyro
just to update, I've found the .api_secret and I use it but I'm still getting 404
Blade Doyle
@bladedoyle
@phyro the V2 API uses JSON RPC so you have to pass the query as JSON data.
ex: curl -ugrin:$secret -s -d '{"jsonrpc":"2.0","method":"get_status","params": [], "id": 1 }' http://localhost:3413/v2/owner
phyro
@phyro
@bladedoyle my bad, thought it was REST, thanks!