how to avoid for block unlock_time to get block number and not usual unlock_window (60)

without changes in my case block unlock_time = block height

anyone here

is it currently still recommended to run monerod with torsocks or rather with --tx-proxy?

what cpu is best for mining monero?

best by which criteria?

AMD 3900x is pretty good

Inge-, biggest hashrate

I have about 10k in the bank

I wanna start up a crypto mining shop

so then perhaps a new epyc 64-core system?

threadripper 3970x does 35+ KH/s

hmm

ok

best hashrate per dollar

take 10k and buy monero

you will get more monero that way

^

.mine 35000

niocbrrrrrr: who does actually mine monero then? I mean, for someone out there it must be profitable...

The matrix has broken.

reddit.com/r/glitchinthematrix

hm. BTC congesting

buy buy buy

is it still recommended to run monerod with torsocks or rather with --tx-proxy?

hello

I am unable to create a wallet on my Nano X from the Monero GUI. I keep getting this message: Error writing wallet from hardware device. Check application logs

Please help.

Al97: Are you running the most recent Ledger Monero App and Ledger Live firmware?

I just downloaded the most recent .15.0.4 and I just did the same with the ledger. I would think that the ledger would have given me the most up to date. I downloaded the ledger about a week ago.

Al97: What is the exact error? It should say more.

That's all it says in red under the advanced options arrow whenever I click create wallet

Are you running Ledger Monero app v1.5.1? Is the Ledger Monero app opened?

is Ledger Live closed?

it was closed. Now its open. I think this may have been a breakthrough (noob learning). I will reach back out if not. Thanks.

Ledger Live should be closed

so that it does not interfere with Monero

Al97: Which operating system are you using btw/

It was closed when my error message came.

But I opened ledger live and the device asked me to accept or reject when I clicked create wallet. I have not selected either on the device yet.

Al97: see on the bottom there should be a second message usercontent.irccloud-cdn.com/file/tdG7atJc/error

this is the important message

also when creating a wallet you have to accept it on the ledger by exporting your view key

I am running windows 10 64 bit

I just didn't know if you wanted me to accept it yet because ledger live is open

yes, accept it

even with ledger live open?

Ledger Live being open can be a problem but not necessary

ok

so if there is a problem try again with Ledger Live closed

ok. asking me to give wallet a PSWD

okay, seems to work now

I think so. I'll reach out if problems arise. You guys are moneyJ! Thanks!

no problem

@M5M400 are you there?

hey i was just poking around and it seems the hashes for cli in hashes.txt on getmonero.org are for a newer release than what is downloadable (0.15.0.4)

the hashes are for 0.15.0.5

ping binaryFate I think

pong

I'm a noobie to Monero and am trying to learn a bit more about it. Ring signatures provide plausible deniability from a blockchain analysis perspective, but if a passive network adversary observes you broadcasting a send transaction does that effectively negate the senders anonymity?

numin0us, not really

possibly degrades it, but the adversary still doesn't know which input is the broadcasters

there's also a new feature called dandelion++ that helps mitigate passive observer information collectors

Ah cool that seems pretty neat! Can it be used in conjunction with TOR/VPNs, and does that add extra protection?

Also, is there any documentation about how new features are added to Monero? I'd be interested to know how it differs from bitcoin @jwintern

@jwinterm

uh, it's a more speedy process for sure numin0us

not sure how much formalized structure there is around it

also, I believe it can be used with tor, definitely vpn

numin0us, #monero-dev is the development channel here and there are discussions on github issues

#monero-research-lab is a channel for discussing lower TRL type changes I guess

further out changes

22:00 <grubles> hey i was just poking around and it seems the hashes for cli in hashes.txt on getmonero.org are for a newer release than what is downloadable (0.15.0.4) <-- GUI is v0.15.0.4 CLI is v0.15.0.5

right but 0.15.0.5 is not on getmonero.org, and the non-gpg-signed hashes displayed on the web page are for 0.15.0.4 as well

grubles: it is on getmonero.org

can you make a screenshot?

can you try a different browser / clear your caches

oh yeah that's my mistake

i somehow downloaded the gui

hey grubles: The CLI version downloadable on getmonero.org should be 0.15.0.5 and this is indeed the case as far as I can see. Did you maybe confuse with GUI version (still 0.15.0.4)?

ah I missed the last lines of discussion above. Nevermind, glad you sorted it out

on blockchain.cpp there is "unlock_time is either a block index or a unix time"

in my case is always block index

without changes

any suggestion?

if i'm not mistaken, it is unix time only for very old transactions, like a few years ago now.

for new chain without changes when mining start always unlock_time = block number

i cant understand why decide that unlock_time must be block number and not time

i cant understand why decide that unlock_time must be block number and not 60

it's easier for every node to agree on the same block number than the same time, i think

you would only see the old behavior if you were running very old software

u mean that if i inert v12 i wont c this

also, minutes per block varies randomly. so if you only have 2 blocks in 20 minutes, instead of 10, using the time instead of the block number would result in weakened security

i'm not sure in which version the change was made. older than 0.12, i think

even if i insert v12 on 2block same behaviour!

i don't understand what you mean by that.

if i change hardfork file to start with v12 on 2block

why would you expect that to change the behavior? and why do you want to change it in the first place?

block number is the correct way, using timestamp in the beginning seems to have been a mistake.

if block number is 999 unlock_time will be 999

is this positive?

what are you using to construct the transaction? monero-wallet-cli sets it to 0 by default, at least in v0.15

im talking about new chain

but having it be the current block number has the same effect (tx can be spent immediately)

ndorf: he is trying to fork monero for a few months now lol

lol

the wallet that constructs the tx picks the unlock_time. why is new chain relevant?

ah

thanks for the heads up, lol

assume everyone is i guess?

anybody who's anybody has their own monero fork

anybody who's anybody ??

I am nobody :(

nobody is nobody