-
ollof2003[m]
Добрый день хотел бы узнать пояему монеро не работает ?
-
jozsef[m]
но это работает! 😜
-
selsta
ollof2003[m]: if you have issues please ask in #monero and ideally in English otherwise we might not be able to help
-
jozsef[m]
He is asking "why monero does not work". I told him that it does. 😃
-
ollof2003[m]
#monero-dev:monero.social I am respected, I ask you to help me, I threw money on mega through the xmr exchanger, the money has not arrived for two days, I wrote to the mega site, to which he replied that monero does not work temporarily, when will it work?
-
moneromoooo
Monero currently works. I assume that person said their own install is temporarily borked.
-
moneromoooo
Though if you have node/wallet logs showing something isn't working, you can paste them to paste.debian.net.
-
ollof2003[m]
bro, I won’t go through any links, I’ve already written to everyone who can wait for funds, thank you bro!
-
jozsef[m]
I suspect an exchange is withholding ollof2003 's XMR. If that's the case, unfortunately, I don't think he has any other choice but to contact the exchange.
-
sech1
ollof2003[m] what exchange? do you have xmr transaction id?
-
sech1
ты им xmr высылал, или они тебе?
-
ollof2003[m]
бро я покупал xmr через обменник всегда так делаю, в этот раз не пришло ничего
-
sech1
Monero работает, это обменник мутит. Есть id их xmr транзакции?
-
ollof2003[m]
-
ollof2003[m]
По нему давно уже все пришло, обменник пишет что деньги отправлены
-
ollof2003[m]
но на аккаунте денег не вижу, как и пополнения как было раннее
-
sech1
Есть такая транзакция, уже 1320 подтверждений. На каком аккаунте, где? Какой кошелёк используешь? Надо сделать rescan в кошельке
-
afungible[m]
This transaction just shows it's confirmed and if receiver's address was correct, the funds are in the receiver's wallet. You may want to wait for your wallet to sync fully.
-
ofrnxmr[m]
<selsta> "ollof2003: if you have issues..." <- #monero:monero.social ^
-
ollof2003[m]
What should I do with it?
-
ofrnxmr[m]
This room (-dev) is for hacking. -dev is the wrong place for tech support.
-
ofrnxmr[m]
We'll continue conversation in #monero:monero.social
-
sneurlax[m]
We are wrapping Monero built from source into an app and it's being detected as malware due to the mining code. Is there an easy way to disable or remove this or will we be playing include whackamole til it works? I'd rather not edit too much so maintainability with upstream Monero is maintained
-
sech1
It can't verify blocks without mining code
-
selsta
should be fine for just a wallet?
-
sneurlax[m]
It's a full node that afaik verifies blocks and detects outputs as well, I'll have to double-check that point
-
selsta
but no, there's no easy way to disable all that code
-
sneurlax[m]
Maybe disabling just enough of it that isn't used for mining will change the binary enough to skip the scanners
-
sneurlax[m]
That isn't used for verification* rather
-
sneurlax[m]
And and all thoughts welcome :)
-
sneurlax[m]
s/And/Any/
-
selsta
I think cn_fast_hash is used in wallet code and AV look for that too
-
selsta
though I could be wrong, don't know how much cn_fast_hash differenteres itself, I just know AV also look for some cryptonight code from before we used RandomX
-
selsta
differentiates*
-
sneurlax[m]
I was mistaken, we don't run a full node, we use a remote node and run wallet2, so it may be more feasible
-
selsta
CryptoNight is used for KDF and I don't think you will be able to remove that:
monero.stackexchange.com/a/7045
-
tobtoht[m]
While you won't be able to get rid of CryptoNight for the reason stated above (see also:
docs.featherwallet.org/guides/wallet-files#Encryption), you can get rid of RandomX if you're not planning to support RPC pay.
-
moneromoooo
cn_fast_hash is used everywhere. Can't get rid of it. But I suppose you could reimplement it stupidly (but correctly).
-
jeffro256[m]
I understand why for PoW, but why was cn_slow_hash chose for KDF instead of say, multiple rounds of cn_fast_hash?
-
sech1
KDF must be resistant to password cracking
-
xmr-pr
vorot93 opened issue #8657: SIGSEGV on MacBook M1
-
xmr-pr
-
afungible[m]
Its should be possible to find the cause of segfault, i.e. file & line number of fault, with a small piece of platform agnostic C++ code, backtrace. Kind of like GDB bt integrated in SW at runtime. Not sure if this issue is MAC specific, or happens on other platforms too?
-
ofrnxmr[m]
Youre replying to a bot
-
ofrnxmr[m]
-
xmr-pr
Kuplynx opened pull request #8658: fix a tiny typo (I think)
-
xmr-pr