Skip to content
Branch: master
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
94 lines (63 sloc) 5.01 KB

Meeting Notes: Development, Mar 05 2019

Development meeting held @ 3PM UTC in grin/Dev channel on Gitter, full chat transcript here. Meeting lasted ~ 75 min.

Notes are truncated, and conversations sorted based on topic and not always chronological. Quotes are edited for brevity and clarity, and not always exact.

Community attendance:

  • antiochp
  • bladedoyle
  • davidburkett
  • garyyu
  • hashmap
  • jaspervdm
  • kargakis
  • lehnberg (30 minutes late)
  • quentinlesceller
  • rentenmark
  • tromp
  • yeastplume

(apologies if I missed someone - submit a PR or contact @lehnberg to add)

Agenda points & Actions

1. Retrospective

  • ignopeverell:
    • I believe the larger things in the works have been the wallet being moved to a separate repo, windows fixes/build becoming supported, and continuing work on Dandelion++.
    • Windows now have travis-ci built pre-release binaries for both grin and grin-wallet, courtesy of yeastplume. Targeted for 1.1.0.
    • garyyu also did some cleanup on the libsecp side to get Travis working on those tests.
    • jaspervdm has some additions to a few wallet-related APIs.
    • Jeremy Rubin has also done multiple nice cleanup PRs, a couple of them still pending.
    • GandalfThePink dropped a paper, related discussion here
    • I've been looking fairly closely at i2pd, expecting that to continue for some time.

2. Agenda review

Proposed agenda accepted.

3. Action point follow-up

3.1 Error management alternatives collated

  • hashmap: Not ready, but some results are here. I checked tokio, actix and some other projects. Rust error management story is still a bit pathetic, so I’d try to simplify what we have mostly by removing mutual wrapping of errors and reducing the number of such layers. I no longer think that mega error makes sense.

4. Grin v1.0.2

  • ignopeverell: My peers show about 50%, which I guess isn't too bad at this point. A quick reminder to service operators that may have a look at this later that regular upgrades are always a good idea.

5. Enabling nightly builds and test runs for windows + MacOS

  • ignopeverell: Could we trigger them with some cron job that would trigger a specific travis build?
    • garyyu: Yes it does, I can take this task.

6. New release of rust-secp

7. Grin v1.1.0

  • ignopeverell: anything still holding 1.1.0? beside perhaps Dandelion++?
    • yeastplume: From my perspective it's just wallet split and windows support, which are in a good enough state to go.
    • hashmap: Async stratum real world test, will ask @hendi and @bladedoyle for help.
    • davidburkett: Even if code complete is coming soon for Dandelion++, it should probably have a decent bit of testing around it before making it into a release.
  • ignopeverell: So no release date for v1.1.0 yet but mostly testing left and we'll see what we do with d++.

8. Grin v1.0.3?

  • ignopeverell: Whether we'll need a v1.0.3 before v1.1.0 or not I think is too early to tell. There's nothing new that would justify it for now I think but I wouldn't rule it out.

9. Improvement proposals

9.1. Provable interactive transactions

  • yeastplume: Do we need a particular discussion of these proposals at the moment? The discussion is ongoing on the issues and I don't think most people would have had a chance to think about them yet.
    • ignopeverell: Agreed, I need to have a read as well.
    • jaspervdm: Yeah I think its too early to bring up in a meeting. It's at least on everyone's mind now so I suggest people post their thoughts in the issue.
    • garyyu: OK, please take a review on this Provable Tx solution and let’s continue discussion there when needed :-)

9.2. Read Only Wallet Database User and Read Only Wallet API

  • ignopeverell: Let's discuss on the relevant issue(s) again then, and adding the use case you have in mind would be helpful as well @garyyu.

10. Other questions

rentenmark: UTXO selection. It would be really nice to have in the wallet a target utxo size or something similar. Current wallet is not very smart about utxo management.

  • yeastplume: Sure, different selection strategies can be added, might be worth some refactoring to allow different strategies to be added in a pluggable manner.
  • ignopeverell: Want to start a PR with a first rough impl for discussion?
  • rentenmark: Yep, i can work on it.

Meeting adjourned.

You can’t perform that action at this time.