hello

has anyone experienced the bug that says

"invalid signature' when you try to login

I know that my password is right because if i enter it wrong it says 'invalid password'

any thoughts?

anyone there?

hello?

edwardosanchez[m: be patient. somebody will respond when they're available

edwardosanchez[m: Do you still have the 25 word mnemonic seed?

Do you think Atomic Swaps will come available within 2021?

yes

Thanks sech, hopefully by that time iv accumilated enough haha

How does one interact with the blockchain DB? Tried to use the python lmdb module, and it threw me an MDB_VERSION_MISMATCH

koork, i don't know for sure, but its possible the python repo you found isn't updated. whats the link?

also, and again im no expert, but you can interact with the monero blockchain using monerod directly or through curl

you need to build the python module against the version of liblmdb that monerod uses

which is usually newer/different from whatever version py-lmdb uses by default

tbh I just pip installed it... Where can I find which version monerod uses? I'm new to the codebase

external/db_drivers/liblmdb

Thank you!

How would you best go about making a provably fair monero lottery? Would taking the last two chars of a given block to choose the winner be enough?

block hash*

of course

something like monero.win

yes, almost the same mechanism but the coins are collected from multiple users and given to one winner

Remember kids. If you call project coral reef for what it is - fluffy embezzling half a mil usd from the monero fund for a website with smaller adoption than monero woo plugin, you will get excommunicated.

did some commands get purged from the daemon?

not seeing many of these: web.getmonero.org/resources/developer-guides/daemon-rpc.html

Hello community, I have a little noobish question, since I want to dig in the monero project I also have to learn about make and cmake. Now the question: In the top directory makefile: Where a the variables {$target} and {$CURDIR} defined?

ah, I see. all the "get" commands have been renamed to "print"

I studied the GNU make documentation, but it not find an answer where those variables come from, if they are set automatically or something like that

Ok {$CURDIR} is automatic, but {$target}?

You pass the target on the command line when building depends.

No obviously with "target" the target plattform is meant, value of variable is "MINGW64_NT-10.0-19041" in my case

No.

the thing is I cannot read something about such a variabel in the GNU make documentation

Makefile in top root dir. Line 54 "cd build/$(target)/release"

Where is the variabel "target" defined?

That's for depends target. Are you building depends ?

Or are you trying to build for Win64 in MSYS2 ?

Yes, I did built on the latter

And you are confused by depends ?

It is just an educational question where I can find a predefined variable documented

It is not predefined. You pass it on the command line.

On Linux: make depends HOST=x86_64-w64-mingw32

x86_64-w64-mingw32 is the target.

It may even be `make depends target=x86_64-w64-mingw32`. I don't remember any more.

Ok now I see what you mean by confusion

I often use "make debug-static-win64" so there is no such variable

depends targets are used for gitian builds. Nothing to do with native builds.

Thanks a lot, question is answered now