Michael Altfield

awesome! unfortunately I get a syntax error on that too ``` user@disp3192:~$ x=$(curl -sd '{"jsonrpc":"2.0","id":"0","method":"get_info"}' https://node.monerod.org/json_rpc | grep 'database_size' | sed -e 's/.[^0-9]([0-9]+)[^0-9]$/\1/'); sed: -e expression #1, char 28: invalid...

Still sed errors :( ``` user@disp14:~$ x=$(curl -sd '{"jsonrpc":"2.0","id":"0","method":"get_info"}' http://xmr.coinspace.net:18081/json_rpc | grep database_size | sed -e 's/.[^0-9]([0-9]+)[^0-9]$/\1/'); sed: -e expression #1, char 28: invalid reference \1 on `s' command's RHS...

Here's an alternative without sed :) ``` x=$(curl -sd '{"jsonrpc":"2.0","id":"0","method":"get_info"}' http://xmr.coinspace.net:18081/json_rpc | grep database_size | cut -d: -f2 | grep -o "[0-9]*"); y=$((x/1024/1024/1024)); echo -e "\tCurrent uncompressed Monero block chain...

But how do we know that's the actual uncompressed, unpruned monero block chain size and not the pruned size?

> you are simply missing the key I'm reporting a social/organization problem, not simply a technical problem. Of course users can download the latest release, check the signature, then just...

> I can confirm that I have known binaryFate for a LONG time...I trust him implicitly...I may sign releases in future @fluffypony This is all great info. Can we please...

I think what you're doing by having individual devs alternate signing of releases is a sane trade-off to get authenticity & integrity in a simple way. However, I should point-out...

> I actually didn't know you could have an ASCII armored exported public key includes some signatures from another key, but if it's possible, I have no problem adding this....

So if fulcio is the "Let's Encrypt for code signing" then this begs the question: > Question: How did Let's Encrypt get into the trusted root store? > Answer: Let's...

can you please link to the script that builds android apps using a fork of this repo?