what is the reason for monero not having an OP_RETURN?

hahsun: monero doesn't have scripting

I know. but what do we do when we wanna use data?

tx_extra is deprecated.

OP_RETURN does not exist.

payment ids deprecated (and were not meant for data).

so I am wondering, what to do if I wanna make use of data on the blockchain.

Data that will be readable by anyone, or encrypted so only the recipient can decrypt ?

tx_extra was deprecated?

moneromooo: I would accept both versions.

main point is having data on the blockchain

let's start with the version: readably by anyone.

tx_extra is readable, but using it for non-standard purposes is bad for distinguishability

one could use it for recipient-encrypted data if one wished

but again, bad for distinguishability

yeah

well again. maybe we will have the need for putting data onto the blockchain sooner or later. worth to give it a thought.

I mean put yourself in my position. I love to build apps on top of monero. but unfortunately I can't make use of the blockchain as what it is. a slow database.

because this database can't hold data.

What kind of data do you need ?

It is nontrivial to have indistinguishable transactions holding arbitrary data

And again: tx_extra exists

hahsun, i think tari is meant to fill the role for aps on the blockchain in the monero ecosystem

Would anyone here be able to spare some testnet XMR for development of a library around Monero, please? I do have a miner running but it hasn't been too successful so far...

i wonder how much it would cost to build a monero backbone on he.net layer 2 transport

.

@Derivator, try this faucet: community.xmr.to/faucet/testnet

looks like it's currently down - I pull stagenet funds from this site whenever I need them

try later

Thanks for the link _lza. I did manage to find a couple blocks after bumping my thread count.

np

Does ` 5/20 Test #5: check_missing_rpc_methods ........***Failed` fails for others too?

-s

ok I had to install requests

So... Snipa is now supposed to merge PRs, right ?

For whoever is now supposed to, the current waiting list is: 6105 6110 6112 6115 6119 6120 6124 6125 6127 6128 6130 6133 6134 6139 6140 6141 6143 6144 6145 6146 6153 5154 6157 6158 6159 6160 6164 6170 6172 6173

are they all reviewed?

hello

for new blockchain im trying to process genesis block on wallet but is not succesful until now

function on old version works but not in the latest

there are 2 proccess_parsed_blocks

im not sure where to insert

Do you know when it broke ? ie, do you know how to use git bisect ?

no moneromooo im not so good...

Can you narrow down when it started breaking ?

middle 2018

1.5 year before

function changed from parsed_blockcs to process_parsed_block

i inserted on the first process_parsed_block but didnt work

Ah, this is for another coin right, not monero ?

yes

Then try asking in #monero, this channel is for monero development.

moneromooo does #6251 fix a specific issue?

It fixes the gitian builds looking for the source tarball update, not the "insert arch here" update.

Can someone test if reproducible builds work currently?

using master + monero-project/monero #6231

would be nice if someone who has it setup can test it so that I know if the issue is on my side

selsta: master + 6231 builds fine here for our normal x86_64-apple-darwin11 target, not x86_64-apple-darwin19.2.0 you seem to be building for.

^ gitian build, not a manual depends build.

iDunk: did you test reproducible builds using Ubuntu?

I get a compile error for some dependency.

I just did a gitian build for all platforms. Everything built fine.

On Ubuntu, yes.

ok thanks for testing, will have to try it again

Btw, libiconv didn't get rebuilt here after libsodium change.

19:20 <iDunk> selsta: master + 6231 builds fine here for our normal x86_64-apple-darwin11 target, not x86_64-apple-darwin19.2.0 you seem to be building for. <-- Can you explain this again?

Looking at your 6256 issue, you seem to be building for x86_64-apple-darwin19.2.0 target.

Maybe you are doing it an a Mac, not on Linux. Idk.

ah right that was me trying out depends, not related to reproducible builds issue I have

My build was without 6255, just with 6231.

iDunk: I think I found the issue, I had to install `pkg-config`. It failed with a weird error that’s why it wasn’t obvious at first.