Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jun 13 08:02
    @jaspervdm banned @matrixbot
  • May 06 2018 21:29
    User @ignopeverell unbanned @maesitos
  • May 06 2018 00:41
    @ignopeverell banned @maesitos
rash5638
@rash5638
i want open Grin coin wallet
energyburn
@energyburn
Hello @rash5638 ! You may be interested in the getting started guide: https://grin.mw/get-started
Welcome :)
BLOCKCHAINSMOKER
@BLOCKCHAINSMOKER
Hello @rash5638 ! You may be interested in the getting started guide: https://grin.mw/get-started
Is there a get started guide for mining?
energyburn
@energyburn
@BLOCKCHAINSMOKER usually the mining pools each have a good guide for mining to their pool. IE: https://grinmint.com/help.html
As far as solo mining goes, Im not aware of a guide
Tony Jin
@nijynot
I can take a look at adding keybase-live-feed to grin.mw. :smile:
Quentin Le Sceller
@quentinlesceller
:+1: that'd be great
lehnberg
@lehnberg
Awesome @nijynot!
Jesse Posner
@jesseposner
It looks like the public blind excess and public nonce use the standard SEC compressed encoding, prefixed by 0x02 or 0x03 depending on whether the Y coordinate is even or odd, however, the pedersen commitments look like they are prefixed with 0x08 and 0x09. Does 0x08 indicate even and 0x09 indicate odd?
Jesse Posner
@jesseposner
I'm working on a proof of concept cold storage for Grin, leveraging MPC threshold signatures.
Jesse Posner
@jesseposner
Jesse Posner
@jesseposner

output[0] = 9 ^ secp256k1_fe_is_quad_var(&ge.y)

9 ^ 1
=> 8
9 ^ 0
=> 9

jaspervdm
@jaspervdm
Yes, correct
Jesse Posner
@jesseposner
Thanks!
Jesse Posner
@jesseposner
I'm having trouble figuring out the first 32 bytes of the part_sig added to the slate by the recipient. For example: for a part_sig 8bbf9597966291057e0c9c271e63f5bc6ab7b5d906062ba4126c654d040b5ee9cc6b26ffa9dbadce1f6af6fc6f120f8f59b48624dd35509d11bd02d0d62eb7c2, the first 32 bytes are 8bbf9597966291057e0c9c271e63f5bc6ab7b5d906062ba4126c654d040b5ee9. This should be the nonce commitment for the signature, but it doesn't match the recipient's public_nonce [02]e95e0b044d656c12a42b0606d9b5b76abcf5631e279c0c7e059162969795bf8b nor the aggregation of both public_nonces ([02]e95e0b044d656c12a42b0606d9b5b76abcf5631e279c0c7e059162969795bf8b + [02]d5a9770e4058e10de2a84a5d2f672627e47e7d4ad5751ab26d3f9e6ad66990ed = [03]919b3530148ab2ae420b17f6a53cf2783a0901492cb5817a7419336cd9b7ca00).
samholmes
@samholmes
How can I delete a wallet and all it's data in Grin++?
Jesse Posner
@jesseposner
cool, I'll try that
Kareem Moussa
@itstehkman
hi! can i get some testnet grins for playing with? i'm running a grin node listening with the api at http://54.145.25.164:3413
Kareem Moussa
@itstehkman
also do you know how i can run usernet on grin server 2.1.1? i got it working in the latest 3.0.0-beta1 release with grin --usernet but realized i shouldnt be running beta and downgraded. usernet broke when i downgraded, so im just using floonet now
Antioch Peverell
@antiochp
@itstehkman I would recommend using the latest 3.0.0-beta1 release right now - its only going to be a couple of weeks before the 3.0.0 release is finalized
D Midnight
@dmidnight_gitlab
I'm curious if any of the work the ethereum devs are doing on zk rollups is applicable to grin... Anybody know? The claims of 3000 tps is quite interesting
Blade Doyle
@bladedoyle
@mcdallas Does grin.report need a restart?
Mike Dallas
@mcdallas
yes it keeps running out of disk space
Added a cronjob to remove the txhashsets
Blade Doyle
@bladedoyle
Thanks @mcdallas
Though, last time I complained about the txhashsets I was told that the issue had been fixed. Maybe we need another issue filed? mimblewimble/grin#2924
Mike Dallas
@mcdallas
Im running 2.0.0 but i think it was supposed to be fixed even then
Maybe it was fixed later
valdok
@valdok
                                                                                                                                                                                                                bbbbbbvbn 010401.....
Chronos
@ChronosCrypto
what is the meaning of the number in parentheses after Transaction Pool Size in grin3 beta? For example, 4 (15)
Antioch Peverell
@antiochp
@ChronosCrypto its the number of tx kernels currently in the pool. If we assume one kernel per tx then these would match with no aggregation occurring. But if we see fewer txs relative to kernels then we get a (rough) idea of the level of aggregation.
Chronos
@ChronosCrypto
thanks, that makes sense!
samholmes
@samholmes
20191214 14:59:17.811 ERROR grin_wallet_impls::node_clients::http - Unable to contact Node to get version info: Request error: Wrong response code: 401 Unauthorized with data Body
This is the message I'm getting from grin-wallet info while in a wallet directory created from grin-wallet init -hr.
I have my grin node running.
Chronos
@ChronosCrypto
we published a critique of bitgrin today. You might enjoy. https://youtu.be/F9D1DmJc84s
Blade Doyle
@bladedoyle
@samholmes Check your grin-wallet.toml file and make sure that the node_api_secret_path config is set correctly
daldev
@daldev
hi guys can you help me with something
image.png
Getting an error when running the grin-wallet saying my grin node needs to be v.2+ but my node is v3
Blade Doyle
@bladedoyle
@daldev You are sure the grin node running is v3? You restarted it after installing the v3 binary? One way to test is:
curl -ugrin:$(cat ~/.grin/main/.api_secret) localhost:3413/v1/status and check the user_agent value
You may also want to update to 3.0.0-beta.2 which is released now
daldev
@daldev
Yup, i'm sure i'm running v3. It's the only binary i installed in this machine
daldev
@daldev
If i want to update to 3.0.0-beta.2 what're the best practices?
daldev
@daldev
image.png
Updated to 3.0.0-beta2 and still having the same issue
image.png
daldev
@daldev
Ok weird but i changed the listener port on the wallet config
And now it works