<j​effro256:monero.social> vthor: by UR do you mean QR or URI ?

UR is animated QR protocol, and has QR and URI somehow in common.

It is used to transport data in a standarized (and bastardized) way which would not fit into one QR code alone (although there can as far as I understood also be on frame QR, but the point is that it is similar as an URI, and feather/anonero defined the standard inside UR y using it, means I will need to send also the key images in the same way so feather and anonero and future wallets are compatible. Unfortunately the key images in json are absolute raw (what

makes also somehow sense, and the binary file exports are encrypted, what makes also sense. But the encryption is pretty NOT simple because of the key generation using not only cn_fast_hash but also cn_slow_hash. That forces or implement Cryptonight (and I don't know what there comes all behind with dependencies, or compiling half monero source in it - what I would prefer to avoid). About UR: github.com/BlockchainCommons/Research/blob/master/papers/bcr-

2020-006-urtypes.md (but this is not the relevant part about the need of key images encrypted blob instead of json....

broken links are fucked: github.com/BlockchainCommons/Resear…ster/papers/bcr-2020-006-urtypes.md

<j​effro256:monero.social> But you're saying that you can't put JSON in these URs?

<j​effro256:monero.social> Why not? Also why does base64url'ing it not work?

so any update on the s390x thing? Does somebody know how to make sense of that CMake infrastrucutre in regards to cross compilation?

024-07-16 11:29:54.277        7fface5737c0    INFO    global    src/cryptonote_core/cryptonote_core.cpp:523    Loading blockchain from folder /media/saah15121472/d76c22d2-6ed4-46be-91ab-99e147d83e3a/monero/lmdb ...

2024-07-16 11:29:54.277        7fface5737c0    WARNING    global    src/blockchain_db/lmdb/db_lmdb.cpp:1354    The blockchain is on a rotating drive: this will be very slow, use an SSD if possible

2024-07-16 11:29:54.277        7fface5737c0    FATAL    blockchain.db.lmdb    src/blockchain_db/lmdb/db_lmdb.cpp:1534    Existing lmdb database is incompatible with this version.

2024-07-16 11:29:54.277        7fface5737c0    FATAL    blockchain.db.lmdb    src/blockchain_db/lmdb/db_lmdb.cpp:1535    Please delete the existing database and resync.

41% sync was fine, and now it showed this error , the monerod is unable to start

Guest81: what version of monerod are you using? compare it with the current version

jeffro256, you can put json in that UR's but it would be incompatible to feather and anonero because they use the binary format how they use wallet2 internally. I don't like to swallow the whole monster (wallet2, what extends then as far I see to almost everything) For that I'm using for now wallet-rpc with the intent to implement later just what I need on each side. Again, the point is only the compatibility and that json is not encrypted but the blob is, an

not really in a standard/easy way because cn_slow_hash is involved in the encryption

Monero 'Fluorine Fermi' (v0.18.3.3-release)

dear users, is there anyway to repair the lmdb data file

.merges