grin/dev

Grin development , for general questions use the #support channel- https://github.com/mimblewimble/grin

lever

@1971192997

hi there How are tx fees calculated?

John Tromp

@tromp

see https://github.com/mimblewimble/grin/blob/2ee8d06d483649647e39a172693a7522496b8a27/core/src/libtx/mod.rs

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

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!

phyro

@phyro

I've banned 11 peers due to FraudHeight today. Is this expected?

lever

@1971192997

@quentinlesceller how to access grin_wallet owner_api from another PC？

i found it only support local

127.0.0.1

johndavies24

@johndavies24

@phyro same with me, all day every day. I rebuilt from latest master and get the same result

then i often find it suggesting it isnt fully sync'd

I've been told that the bans are not something to be very concerned about, especially during initial sync (but I rebuilt 6 days ago or so and everything persisted)

johndavies24

@johndavies24

(it has said that it was running and fully sync'd multiple times and this status reappears)

Blade Doyle

@bladedoyle

@1971192997 Loopback address 127.0.0.1 is hard coded and no confirmation option exists. You will have to edit the source code and rebuild to get it to listen on the public interface.

lever

@1971192997

yeah got it thanks @bladedoyle

Lolliedieb

@Lolliedieb

Hey, just wanted to check back if there is already a date when v3 will be released - since we only got 15 days to go until the fork :)

mattt21

@mattt21

Hey guys, 2 questions regarding grin-wallet 3.0 - hoping I could get some help/feedback on them:

1). Having this issue when sending a grin transaction via RPC

{
"id": 1,
"jsonrpc": "2.0",
"result": {
"Err": {
"GenericError": "Wallet Communication Error: Tor Configuration required"
}
}

The curl command is:

curl -0 -XPOST -u grin:password --data '{ "jsonrpc": "2.0", "method": "init_send_tx", "params": {"args":{"src_acct_name":null, "amount":"500000000", "minimum_confirmations":10, "max_ouputs":500, "num_change_outputs":1, "selection_strategy_is_use_all":true, "message":null, "target_slate_version":null, "estimate_only":null,"payment_proof_recipient_address":null, "ttl_blocks":null, "send_args": {"method":"http", "dest":"http://xxxxxxx.onion", "finalize":true, "post_tx":true, "fluff":false}}}, "id": 1}' http://127.0.0.1:3420/v2/owner

Tor is running, I have a listener and a owner_api process running and have successfully received my tor receiving address when launching 'grin-wallet -e listener'

2). Is there a way to direct the tor process grin-wallet controls to a directory? For example, packing grin-wallet into an application with a tor executable and specifying that directory instead of checking the system path

AlexSpain

@AlexSpain

@mattt21 this not work without tor too

they change owner api init_send_tx

Where communities thrive

People

Repo info

Activity