Does anybody know what this list is about? github.com/monero-project/monero-site/blob/master/_data/donators.yml It's a list of donators and dates

It's before the FFS/CCS existed

You could reach different tiers corresponding to the amount donated

Iirc rpietala designed it

Got it. Does it make sense to keep it? otherwise i'll just remove it

IIRC there was a discussion about it before, and it would be unfair to these people to remove their listing after the fact.

Why do you want to remove it ?

I would say we could keep it somewhere else, but i wouldn;t know where. So makes sense to keep it there. I'm just cleaning up some unused/broken files in monero-site: monero-project/monero-site #954

i wonder.... are particular blocks faster to parse by a wallet?

as a hack to possible slightly decrease scan times, im curious if a wallet provider could create /publish an index of blocks with their associated processing factor

or attributes

thus, when a wallet user needs to scan a segment of chain, the wallet would scan these first (randomly or sequentially)

Yes. Mostly proportional to number of outputs in the block.

so a low output / transaction factor could do it

though high output / transaction is mostly exchange and pool outputs.... the thing that us actually being used prolly

You want to... avoid scanning txes with lots of outs ? Txes with few outs ?

Wait, on second thought, pretend I did not ask.

well, if its the overall # of outputs per transaction ....

ok. done. what are we doing?

woodser: paste.debian.net/hidden/bda98b48

(replaces the previous one)

or, even just an index of empty blocks

which would hopefully get less and less useful over time

moneromooo: the patch isn't applying correctly

Dear chatters, please remove yourselves from the #freenode channel if you are currently in there. We are working to combat bot spam, and if the users can remove themselves from that channel so that only bots remain, we can more easily execute our cleanup. Thanks! - freenode staff P.S. Fuck you.

Dear chatters, please remove yourselves from the #freenode channel if you are currently in there. We are working to combat bot spam, and if the users can remove themselves from that channel so that only bots remain, we can more easily execute our cleanup. Thanks! - freenode staff P.S. Fuck you.

Dear chatters, please remove yourselves from the #freenode channel if you are currently in there. We are working to combat bot spam, and if the users can remove themselves from that channel so that only bots remain, we can more easily execute our cleanup. Thanks! - freenode staff P.S. Fuck you.

no thanks

Dear chatters, please remove yourselves from the #freenode channel if you are currently in there. We are working to combat bot spam, and if the users can remove themselves from that channel so that only bots remain, we can more easily execute our cleanup. Thanks! - freenode staff P.S. Fuck you.

Dear chatters, please remove yourselves from the #freenode channel if you are currently in there. We are working to combat bot spam, and if the users can remove themselves from that channel so that only bots remain, we can more easily execute our cleanup. Thanks! - freenode staff P.S. Fuck you.

Dear chatters, please remove yourselves from the #freenode channel if you are currently in there. We are working to combat bot spam, and if the users can remove themselves from that channel so that only bots remain, we can more easily execute our cleanup. Thanks! - freenode staff P.S. Fuck you.

moneromooo: getting "error: corrupt patch at line 12" against master

Remove line breaks.

It was made off master this time.

There are three line breaks in the paste.

Ah, long lines. Right.

I have it built now

yes this seems to fix it

not seeing any issues

Thanks. I'll PR then.

Hey. I'm implementing a client for the wallet RPC. If I was implementing a web-app that gives users addresses to deposit to, I would want to generate an address (RPC call), and then update the page with various transaction statuses (this is what my question is about). I see that the wallet-cli has a "tx-notify" flag and some ZeroMQ stuff going on.

Are either of these options the recommended approach for implementing transaction notifications, or should I poll the wallet using an rpc method, or is there something else entirely?

Also, is the RPC the best way to deal with this usecase? I was confused a few days ago when I realized you can't generate non-sub-address addresses using the wallet RPC, even with different accounts in the wallet, and I now understand why. Is that an indication that using the wallet-rpc for this sort of thing an anti-pattern?

I've seen alternatives using JNI and I had the idea of just doing some offline cryptography in-place to generate new standard addresses. I could recover the funds later on by writing raw transactions to sweep balances... or something like that.

Sorry for such a long series of questions, been spending a bunch of time on this for the last few days :P