ah, I don't speak yet rust or zig and only fixed some go code without knowing go really either. I went through the wallet folder a bit, but couldn't find key images import/export, I assume you implement there only what is usefull for the serai project, or?

<b​oog900:monero.social> NGL I haven't really used `monero-serai`'s wallet functionality. I am pretty sure it is not "batteries included" though, it handles tx scanning, spending, etc. Something like key images import/export would need access to the full wallet history.

<b​oog900:monero.social> kayabanerve

<k​ayabanerve:monero.social> It isn't only what's useful for Serai. It's all the functionality necessary for a wallet.

<k​ayabanerve:monero.social> It isn't monero-wallet-{rpc, cli}

<k​ayabanerve:monero.social> There is a scanner, representations of scanned outputs, and a way to spend outputs. It doesn't have a database, any networking code, nor a UI.

<k​ayabanerve:monero.social> Exporting a key image would be taking a scanned output, calculating the one time key for it, and scaling the key image generator. It used to have a function for it but I believe was considered sufficiently primitive it no longer does?

<k​ayabanerve:monero.social> And then communicating those bytes in some format of your choice.

them main issue with it is the encryption I have, not the encryption itself, but the key generation with cn_slow_hash, I implemented all, and at the end I put the key generation, could not be sooo hard, could it, but then there is some magic sauce, well I will look into it the next days, still don't know rust in reality, so this will take me also some days. Thank you for all the answers! :)

<r​brunner7:monero.social> monero-project/meta #1054

<m​atrix3893:matrix.org> Right now I'm raffling off 0.777 ETH among the conference participants at Zoom us80web-zoom.us/j/7681681573?pwd=EYRvEXpSguQGrDMLW4JVlGZC8tYtnwPO

<m​atrix3893:matrix.org> I am a trader with 7 years of experience and I am showing others my thorny path to success. I will be glad to everyone!

.merges

luigi1111: are you still available tomorrow for tagging? or only today?

tomorrow

k

also gui merges afterwards please

.merges

slow bot

9287 and 9380 have conflicts

jeffro vtnerd

luigi1111 You can also ping PR authors directly on github

jeffro256

true just wasn't sure they read the emails or pay attention to "stale" approved prs

done. Also sorry vtnerd it wasn't your pr.

<j​effro256:monero.social> kk 9287 is rebased

<t​obtoht:monero.social> Guix builds (#8929) now produce bit-by-bit identical release binaries on x86_64 and aarch64 based machines for linux, windows and macos targets. With gitian, it is only possible to build natively on x86_64.

<t​obtoht:monero.social> FreeBSD and Android targets use pre-compiled x86_64 toolchains and libraries.

<t​obtoht:monero.social> It should also be possible to run Guix builds on riscv64 machines, but I presently don't have access to a board with decent enough specs to test this.

tobtoht you can test riscv on github CI: github.com/jirutka/setup-alpine

see example github.com/SChernykh/p2pool/blob/ma…ter/.github/workflows/c-cpp.yml#L13

It will be an emulation, but it's 4 vCPUs, 16 GB RAM and 14 GB storage on the CI runner (Linux)

<t​obtoht:monero.social> sech1: Cool, I'll give that a try. CI runs take ~2h so emulation performance overhead would need to be less than 3x in order for jobs to not time-out.

tobtoht where woud you start to get enlightend as quick as possible about cross compiling and tool chains, I mean enough to be dangerous. And what you think is the minimum time to figure out to crosscompile monero for armv6?

If it's a full build with all dependencies, then it will probably not fit in 6 hours limit

<t​obtoht:monero.social> sech1: ok, will set it up locally then until I have access to metal

<t​obtoht:monero.social> vthor_: Honestly, I've learned everything from: Try to build something. It produces an arcane error message. Dig in the docs/code until I understand how to fix it. Repeat this until the build succeeds. Haven't found the ultimate quick start guide. I'd be happy to help / answer more specific questions, though.

understand, seems like reality, hoped only you had the golden gral to not go down the rabbit hole, thank you tobtoh

<t​obtoht:monero.social> vthor_: I was able to cross-compile for armv6 using depends (with a couple quick hacks). Haven't tested the binaries. I can prepare a Dockerfile for you.

this is supercool tobtoh 8) thank you very very much!

do you now if it is then a static build or I need to solv that still?

<t​obtoht:monero.social> Runtime dependence on glibc 2.27 (or higher) and common system libraries (similar to release binaries). All build dependencies are statically linked including openssl.

yeah, this sound more than great, no more 20+h for a build, and it should run then out of the box on build root, and I can revert all this brainless dependencies :)