by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 14:51
    antiochp assigned #3341
  • 14:47
    antiochp milestoned #3341
  • 14:47
    antiochp labeled #3341
  • 14:47
    antiochp opened #3341
  • 11:34
    lehnberg commented #3340
  • Jun 04 14:56
    BurtonQin edited #3340
  • Jun 04 14:55
    BurtonQin opened #3340
  • Jun 04 14:39

    yeastplume on v4.0.0-beta.1

    (compare)

  • Jun 04 14:38

    yeastplume on v4.0.0-beta.1

    (compare)

  • Jun 04 13:53

    yeastplume on v4.0.0-beta.1

    (compare)

  • Jun 04 13:52

    yeastplume on master

    4.0.0-beta.1 Version Bump (#333… (compare)

  • Jun 04 13:52
    yeastplume closed #3339
  • Jun 04 13:27
    yeastplume opened #3339
  • Jun 04 13:05

    quentinlesceller on master

    header version 4 accompanied by… (compare)

  • Jun 04 13:05
    quentinlesceller closed #3334
  • Jun 03 17:01
    quentinlesceller reopened #3338
  • Jun 03 17:01
    quentinlesceller closed #3338
  • Jun 03 16:02
    quentinlesceller labeled #3338
  • Jun 03 16:02
    quentinlesceller opened #3338
  • Jun 03 11:34

    hashmap on master

    servers: fix possible deadlock … (compare)

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!
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
image.png
then i often find it suggesting it isnt fully sync'd
image.png
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
lol if I read correct
lehnberg
@lehnberg

In 2 hours from now (3PM UTC) we're having the first dev meeting of 2020.
Agenda: 
mimblewimble/grin-pm#231



We’re conducting the meeting on Keybase rather in this channel.

Instructions for how to join:

  1. Install Keybase (https://keybase.io) and create an account.
  2. Join the grin community:

    • From the app: Select “Teams” » “Join a team” and then type “grincoin”
    • From the command line: keybase team request-access grincoin
  3. Join the #dev channel:
    • From the app: Select “Chat” » “grincoin”, then press the cog wheel » ”Manage chat channels" and tap "#dev"
    • From the command line: keybase chat join-channel grincoin '#dev'

Keybase supports tor and command line access. More instructions and information available here:
https://keybase.io/docs

rostfrei
@rostfrei
@tromp I'm having the same issue that @phyro had, I'm trying to build latest grin-miner and I get
-- Build files have been written to: /root/Developement/grin-miner/target/debug/build/cuckoo_miner-5c210461fdbc31a2/out/build
running: "cmake" "--build" "." "--target" "" "--config" "Debug" "--"
[  1%] Building NVCC (Device) object CMakeFiles/cuckaroom_cuda_29.dir/cuckoo/src/cuckaroom/cuckaroom_cuda_29_generated_mean.cu.o

--- stderr
/root/Developement/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)

/root/Developement/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)

/root/Developement/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)

/root/Developement/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)

4 errors detected in the compilation of "/tmp/tmpxft_00001efc_00000000-14_mean.compute_75.cpp1.ii".
CMake Error at cuckaroom_cuda_29_generated_mean.cu.o.Debug.cmake:279 (message):
  Error generating file
  /root/Developement/grin-miner/target/debug/build/cuckoo_miner-5c210461fdbc31a2/out/build/CMakeFiles/cuckaroom_cuda_29.dir/cuckoo/src/cuckaroom/./cuckaroom_cuda_29_generated_mean.cu.o


gmake[2]: *** [CMakeFiles/cuckaroom_cuda_29.dir/build.make:72: CMakeFiles/cuckaroom_cuda_29.dir/cuckoo/src/cuckaroom/cuckaroom_cuda_29_generated_mean.cu.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:72: CMakeFiles/cuckaroom_cuda_29.dir/all] Error 2
gmake: *** [Makefile:84: all] Error 2
thread 'main' panicked at '
command did not execute successfully, got: exit code: 2

build script failed, must exit now', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.42/src/lib.rs:861:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

warning: build failed, waiting for other jobs to finish...
error: build failed
John Tromp
@tromp
you can pull it into grin-miner with something like git submodule update --remote --recursive
rostfrei
@rostfrei
@tromp This helped, but now I get another
Scanning dependencies of target cuckarood_cuda_29
[ 41%] Building C object CMakeFiles/cuckarood_cuda_29.dir/cuckoo/src/crypto/blake2b-ref.c.o
[ 42%] Linking CXX shared library plugins/cuckarood_cuda_29.cuckooplugin
[ 44%] Built target cuckarood_cuda_29

--- stderr
/root/Developement/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckatoo/mean.cu(209): error: static assertion failed with "TRIM0_TPB must divide BITMAPWORDS"

/root/Developement/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckatoo/mean.cu(211): warning: pointless comparison of unsigned integer with zero

/root/Developement/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckatoo/mean.cu(262): error: static assertion failed with "TRIM1_TPB must divide BITMAPWORDS"

/root/Developement/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckatoo/mean.cu(264): warning: pointless comparison of unsigned integer with zero

/root/Developement/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckatoo/mean.cu(313): error: static assertion failed with "TRIM_TPB must divide BITMAPWORDS"

/root/Developement/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckatoo/mean.cu(315): warning: pointless comparison of unsigned integer with zero

3 errors detected in the compilation of "/tmp/tmpxft_00003e25_00000000-14_mean.compute_75.cpp1.ii".
CMake Error at cuckatoo_mean_cuda_19_generated_mean.cu.o.Debug.cmake:279 (message):
  Error generating file
  /root/Developement/grin-miner/target/debug/build/cuckoo_miner-5c210461fdbc31a2/out/build/CMakeFiles/cuckatoo_mean_cuda_19.dir/cuckoo/src/cuckatoo/./cuckatoo_mean_cuda_19_generated_mean.cu.o


gmake[2]: *** [CMakeFiles/cuckatoo_mean_cuda_19.dir/build.make:65: CMakeFiles/cuckatoo_mean_cuda_19.dir/cuckoo/src/cuckatoo/cuckatoo_mean_cuda_19_generated_mean.cu.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:442: CMakeFiles/cuckatoo_mean_cuda_19.dir/all] Error 2
gmake[1]: *** Waiting for unfinished jobs....
gmake: *** [Makefile:84: all] Error 2
thread 'main' panicked at '
command did not execute successfully, got: exit code: 2

build script failed, must exit now', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.42/src/lib.rs:861:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.