-
xmr-pr
xiphon opened pull request #6892: core_rpc_server: on_send_raw_tx - fix bootstrap daemon mode check
-
xmr-pr
-
xmr-pr
xiphon opened pull request #6891: core_rpc_server: on_get_blocks - forward bootstrap daemon error
-
xmr-pr
-
xmr-pr
xiphon opened pull request #6893: [release-v0.17] core_rpc_server: on_get_blocks - forward bootstrap dae...
-
xmr-pr
-
selsta
luigi1111w: could you merge 6868 now so that we avoid merge conflict later?
-
selsta
grydz: we will release v0.17.1.0 relatively soon, please update the ledger app to support both v0.17.0.0 and v0.17.1.0
-
selsta
the release contains only bug fixes, no ledger specific testing is required
-
luigi1111w
yes
-
selsta
hyc: please rebase 6887
-
selsta
.merge+ 6893
-
xmr-pr
Added
-
xnbya
Hi, I've submitted a bugfix in pr #6894, hopefully theres time to include it in the next release
-
selsta
still time if it gets reviewed
-
selsta
please PR also against master if necessary
-
xmr-pr
xnbya opened pull request #6894: [release-v0.17] core_rpc_server: getblocktemplate - fix next_seed_heig...
-
xmr-pr
-
xnbya
ok thanks
-
xmr-pr
xnbya opened pull request #6895: core_rpc_server: getblocktemplate - fix next_seed_height
-
xmr-pr
-
selsta
Seeing that I don’t have a way to contact anyone at Ledger I guess we are forced to use v0.17.0.2...
-
binaryFate
selsta: someone must have a way to reach somebody at ledger?
-
selsta
hyc: please rebase
monero-project/monero #6887 we plan to tag in a couple hours
-
dEBRUYNE
We could PM their CTO on Reddit I suppose
-
dEBRUYNE
He is quite active there
-
selsta
doubt he will reply in 1-2 hours
-
dEBRUYNE
Well, last comment was a few hours ago ->
reddit.com/user/btchip
-
hyc
ok looking
-
hyc
selsta: rebased
-
selsta
thanks
-
selsta
.merges
-
xmr-pr
6808 6822 6828 6833 6869 6870 6880 6883 6884 6887 6893
-
selsta
.merge+ 6894
-
xmr-pr
Added
-
grydz
selsta, indeed we'll do that!
-
grydz
Do you plan to release CLI and GUI at the same time?
-
selsta
yes, both tomorrow if everything works well :)
-
selsta
all from Ledger side that has to be done is add support for both v0.17.0 and 0.17.1 here:
github.com/LedgerHQ/app-monero/blob/master/src/monero_init.c#L182
-
grydz
Sure.
-
moneromooo
Does anyone here have a machine that can mine randomx with a large number of threads that's tuned ? I have a patch which might affect performance with lots of threads and I want to know if it does.
-
selsta
sech1: ^ ?
-
moneromooo
-
Inge-
does mining with xmrig count?
-
sech1
that shouldn't affect performance much
-
moneromooo
No, monerod only.
-
grydz
We'll release version 1.7.4 of the app before tomorrow:
LedgerHQ/app-monero #88
-
selsta
awesoe thank you :)
-
selsta
awesome*
-
selsta
We need a review for 6888 and 6889, then we can tag v0.17.1.0
-
selsta
.merge+ 6888 6889
-
xmr-pr
Added
-
Inge-
Quick q: if 0.17.1.0 is a monerod update, is it a correct assumption that it should be fine to run 0.17.0.x + Ledger monero app 1.7.3 until next major release?
-
selsta
not sure what monerod update means
-
selsta
v0.17.0.x + Ledger 1.7.3 is fine until the next network upgrade, yes
-
selsta
but I would recommend updating as there are multiple wallet fixes too
-
selsta
.merges
-
xmr-pr
6808 6822 6828 6833 6869 6870 6880 6883 6884 6887 6888 6889 6893 6894
-
selsta
luigi1111w: we would be ready to merge and tag now
-
Inge-
selsta: ack
-
luigi1111w
yup
-
luigi1111w
what is the effect of 6894?
-
moneromooo
AFAIK it allows miners to start setting up the next dataset while still mining on the old one.
-
selsta
I assume rw lock stuff is not necessary for this release?
-
xmr-pr
moneromooo-monero opened pull request #6896: crypto: add a rw lock to rx_slow_hash for robustness
-
xmr-pr
-
moneromooo
Not necessary.
-
luigi1111w
so the effect of it missing is just an optimization thing?
-
moneromooo
AFAIK yes, it is just that.
-
moneromooo
xnbya: is that what you use this for ?
-
selsta
luigi1111w: looks like we are good to tag
-
luigi1111w
does moneromooo double confirm?
-
selsta
(v0.17.1.0)
-
moneromooo
I think so
-
aubergine
Hi everyone
-
aubergine
monero php integration no longer works after the recent fork. What has changed?
-
moneromooo
hi
-
aubergine
-
moneromooo
CLSAG probably.
-
moneromooo
SerHack: ^
-
aubergine
mmm what does CLSAG mean?
-
aubergine
the curl RPC call?
-
moneromooo
Exact meaning doens't matter, it's a change to the signatures.
-
moneromooo
Do you have any error message ?
-
aubergine
yes
-
aubergine
Invalid response data structure
-
aubergine
-
moneromooo
Can you paste the remainder of the message on paste.debian.net ? It seems to also log the response it got.
-
aubergine
-
moneromooo
CLSAG changes should not have caused that.
-
moneromooo
Do you know how to log pMethod/pParams ?
-
moneromooo
Oh, looks like it logs request, which should be that.
-
aubergine
no but I saw a debug function within the code
-
moneromooo
So switch to debug, and paste the request please.
-
aubergine
I'm pretty sure something has changed, such error has never appeared in two months
-
luigi1111w
like that?
-
luigi1111w
selsta
-
selsta
yay
-
selsta
now we also have to do gui
-
SerHack
Aubergine: Thanks. I'll look for that tonight
-
aubergine
SerHack ok ping me if you need help
-
selsta
iDunk: hyc: TheCharlatan: scoobybejesus: v0.17.1.0 is tagged
-
selsta
(reproducible builds), and whoever else wants to participate
-
xnbya
moneromooo: yes the next_seed_hash is used to set up the next dataset for share verification
-
xnbya
and its also sent to pool miners, I'm unaware of any miners which currently use it tho
-
sech1
xmrig doesn't use it
-
hyc
xmrig doesn't even use it? ironic
-
hyc
although I'm wondering how it would ever be an optimization - it would eat CPU & memory bandwidth to prep the next dataset in advance anyway
-
hyc
which would hurt mining throughput while generating
-
hyc
if no one uses it ... and it's actually of questionable usefulness, maybe better to drop it entirely
-
dEBRUYNE
selsta: I can write something for the mailing list I guess
-
moneromooo
I can think of a very special case. Say it takes you 2 minutes to generate the data set (extreme example of course). You connect to a pool on the last block before an epoch change.
-
dEBRUYNE
Now that the tag has been set
-
moneromooo
You then decide to generate the next epoch's data set and not bother wit the current one.
-
selsta
dEBRUYNE: thanks
-
hyc
yeah quite a rare case moneromooo
-
moneromooo
I'm a coder. I think of these things -_-
-
hyc
but I guess so. if any miner actually bothers to implement it
-
gingeropolous
so whats 17.1 all about?
-
selsta
gingeropolous: bug fixes
-
gingeropolous
but a full decimal delimiter hop .. ?
-
scoobybejesus
-
iDunk
-
hyc
starting a build now
-
xmr-pr
vtnerd opened pull request #6897: Add support for i2p and tor seed nodes
-
xmr-pr
-
selsta
.merge+ 6867 6863
-
xmr-pr
Added
-
sethsimmons
-
luigi1111w
iDunk scoobybejesus is the linux 64 available to dl somewhere
-
selsta
-
luigi1111w
thx
-
gingeropolous
ok, so with the "nodes-syncing-don't-relay-so-borks-stem" issue, is it possible for a node to check (and thus relay) a transaction even if the node doesn't have complete chain info?
-
gingeropolous
i.e., can you validate a tx if you can only access n/11 inputs?
-
moneromooo
If you have all the outputs if refers to, yes.
-
moneromooo
That's assuming you're on the partial main chain though.
-
gingeropolous
ok, so you *do* need all of the outputs it refers to
-
gingeropolous
so if my node was 1k blocks behind, and a tx came in and 5/11 outputs i have access to, but I don't have the other 6, I can't say "well, these 5 check out, so the other 6 must be good"
-
gingeropolous
the outputs it uses as inputs
-
binaryFate
if you miss just one then you can't check it's not a trickery of sort
-
binaryFate
<moneromooo> If you have all the outputs if refers to, yes. <--- conceptually yes but in practice isn't a daemon currently syncing not relying anything?
-
moneromooo
We could implement RFC 3514 for those cases.
-
gingeropolous
ok. i was just curious if there's some cryptohashmagic that says hash(N sub 1-5) + hash(N sub 6-11) = hash(N sub 1-11)
-
moneromooo
When a daemon is syncing, it drops txes currently.
-
gingeropolous
replace hash with "curve dither monomer" or whatever else it may be
-
moneromooo
hash(N shub - niggurath)
-
gingeropolous
shubadubdub, 3 hash in a tub
-
selsta
comment in code says "while syncing, core will lock for a long time, so we ignore those txes"
-
gingeropolous
i guess im curious what "while syncing" means. does that mean IBD? Or does that mean anytime a peer says "hey I have a new block", because that's technically syncing.
-
gingeropolous
or u bring a node back online, and it needs 10 blocks.
-
gingeropolous
cause it seems that dandelion works best with a lotta nodes
-
gingeropolous
--- OR - why not just let daemons relay without checking while in stem phase, and then validate in fluff?
-
selsta
What problem are you trying to solve right now?
-
Alex_LocalMonero
Is there a document we can look up to see the wallet RPC API changes between v0.16.0.3 and v0.17.1.0?
-
Alex_LocalMonero
Every time there's an upgrade we have to figure out API changes by trial and error, it's quite annoying.
-
gingeropolous
<selsta> What problem are you trying to solve right now? >>> the network not being able to utilize all available nodes as relays for dandelion routing.
-
dEBRUYNE
Alex_LocalMonero: I suppose you could use this (partly) ->
github.com/monero-project/monero/commits/master/src/rpc
-
gingeropolous
i imagine the steady state of the network will be n% of always on machines, and 100-n% of machines that come and go sporadically
-
gingeropolous
these come and go are most likely syncing-up when they come on, so they are re-integrating into the network in preparation to submit a transaction
-
gingeropolous
but mebbe its nothing
-
hyc
-
hyc
matches iDunk
-
luigi1111w
let's see how long this little box takes to sync
-
xmr-pr
xiphon opened pull request #6898: device: Ledger - update status codes
-
xmr-pr