17:11:03
rbrunner7:monero.social:
Meeting in 50 minutes
17:59:53
rbrunner7:monero.social:
Meeting time. Hello! https://github.com/monero-project/meta/issues/1304
18:00:35
jberman:monero.social:
*waves*
18:01:37
sneedlewoods_xmr:matrix.org:
hey
18:02:04
rbrunner7:monero.social:
Alright, let's start with the reports
18:03:51
jeffro256:monero.social:
Howdy
18:03:51
sneedlewoods_xmr:matrix.org:
not much, some small local fixes (e.g. review comment from iamamyth), will push when there is more
18:04:03
sneedlewoods_xmr:matrix.org:
also noted something related to the issue where the CLI prints `Height x / y` in the case when we create a transaction and wait for confirmation,
18:04:03
sneedlewoods_xmr:matrix.org:
we use `pauseRefresh()` [src](https://github.com/monero-project/monero/blob/41ad5238a05dfc1867469eff8336ade312598cbe/src/wallet/api/wallet.cpp#L2472-L2479) in `createTransactionMultDest()` [src](https://github.com/monero-project/monero/blob/41ad5238a05dfc1867469eff8336ade312598cbe/src/wallet/api/wallet.cpp#L1622), but `m_refreshEnabled` gets set to `true` after a while. IIUIC this<clipped
18:04:05
sneedlewoods_xmr:matrix.org:
`LOCK_REFRESH()` [src](https://github.com/monero-project/monero/blob/41ad5238a05dfc1867469eff8336ade312598cbe/src/wallet/api/wallet.cpp#L61-L72) macro from jberman may be a better fit do make sure this doesn't happen, testing at this moment
18:05:07
sneedlewoods_xmr:matrix.org:
nah, didn't work lol
18:05:19
jeffro256:monero.social:
Made a tweak to Carrot account derivation in the spec https://github.com/jeffro256/carrot/pull/6, wrote a concrete PQ turnstile design around it https://gist.github.com/jeffro256/146bfd5306ea3a8a2a0ea4d660cd2243, and implemented it in the C++ lib https://github.com/seraphis-migration/monero/pull/250
18:05:21
rbrunner7:monero.social:
Sounds like quite some edge case
18:05:34
jberman:monero.social:
me: opened a new CCS proposal, continuing investigating sync issues reported in the stressnet channel (a newly reported connection drop issue [244] & slower than expected sync on one of the stressnet participant's machine [246]), then stressnet release v1.5. I didn't have much availability the last week for thanksgiving, back at 100% availability now
18:06:06
jeffro256:monero.social:
Also sending out quote requests for a carrot_core code audit, so we can get that audit out of the way
18:06:11
sneedlewoods_xmr:matrix.org:
I think creating transaction is not the only place where this happens, but it's easy to reproduce for not
18:06:14
sneedlewoods_xmr:matrix.org:
for now*
18:06:31
rbrunner7:monero.social:
I see
18:07:31
rbrunner7:monero.social:
jeffro256: Those turnstiles will get important if/when somebody comes along with a working quantum computer? If yes, isn't it awfully early to program something already now? Or is this to verify / prove the design?
18:09:07
jeffro256:monero.social:
This issue is that if you don't prepare for it now, you can't use it later. The tweaks were relatively small and provable that hashes didn't bind to anything less than they were currently binding
18:09:19
jeffro256:monero.social:
took a couple hours at most
18:09:38
rbrunner7:monero.social:
Ah, ok, imagined this quite a bit bigger then
18:09:41
jeffro256:monero.social:
It would be nice to validate that the design can do what it claims it can tho
18:10:36
rbrunner7:monero.social:
Yes
18:11:46
rbrunner7:monero.social:
I saw from discussions over last week that there are still quite differing opinions about the future design of fees and related issues like block size growth limits. Does that hold up anything right now? Guess not.
18:12:52
rbrunner7:monero.social:
That goes on for quite a while now, no? :)
18:14:32
jeffro256:monero.social:
Right now? Probably holding up an accurate beta stressnet
18:15:11
jeffro256:monero.social:
some of the fee policy can be deciding in relay fees, but the scaling rules as it relates to block subsidy penalty need to be decided in consensus
18:15:49
rbrunner7:monero.social:
And if you change such growth parameters later, that will invalidate tests that you do now.
18:16:53
rbrunner7:monero.social:
I guess sometimes reaching consensus takes time, it's in the nature of complex questions. I hope that the dust will soon settle.
18:17:35
rbrunner7:monero.social:
Alright, is there something to discuss beyond these reports?
18:17:37
jeffro256:monero.social:
Yes, if we want an accurate view of how mainnet will scale, we need to know the paramaters before starting a new stressnet IMO
18:18:30
jberman:monero.social:
also going to spend some more time focusing on that discussion soonish
18:19:59
rbrunner7:monero.social:
That would certainly be useful; seems to me not many people have the necessary background knowledge to take part. I certainly don't.
18:20:39
rbrunner7:monero.social:
I don't know much more than "It's complicated" :)
18:21:34
rbrunner7:monero.social:
I think we can close the meeting here. Thanks everybody for attending, read you again next week!
18:22:18
sneedlewoods_xmr:matrix.org:
thank you