How is an Algorand's address made?

Hilariously it seems that the whole thing about imputing the implied vol of the puts was only part of the story because of the accredited investor discount! This is a component of the auction price of algo that wasn’t previously discussed but seems so obvious now.

Algorand implied volatility

If you have guys on your side that are calculating the implied vol on the puts after the auction based on the price in the secondary market I would love to see the results. It would probably be interesting to others as well. I doubt that it’s going to be anywhere near the 100% mentioned here th…

Algorand's fork of libsodium

Cool! I love that you guys added in the VRF primitives. Do you think it will ever get merged upstream? Has this gone through security audit? Thanks for posting a link to the diff. Regarding having the fork in-tree, submodules is actually a pretty common approach depending on language. Normally, th…

Very interesting to see libsodium fork in tree. Forking libsodium is not entirely unusual but I have never seen it in tree before. Is there an easy way to see what you guys have changed? How about security audit reports?

How anonymous/private are transactions, versus say Monero, Zcash?

Also worth mentioning here is that when algorand open sources their blockchain the mimblewimble protocol of grin/beam could also be implemented with algorand POS/consensus but it is a different blockchain format and would require a new chain.

What is Algorand's binary serialization format?

It makes sense to me, it is somewhat unique in my experience. Interestingly, you then are implicitly sort of requiring language support so you need to re-implement all of this in each language you want to use. And there are a lot of languages. It looks to me like there is a nice microservice brewing…

Wow this is cool, I am surprised to see this in the client code though, I will definitely be taking a closer look into the clients. Usually they’re pretty dumb, you generally want them to do as little as possible. I am surprised to see the base32 representation rather than the more common and compa…

I am looking at this transaction for example transaction link. How would I convert FBPLS3VDAG7FU36BSD2WWGLX4QI223G52HKMK7N65NZKCEEOPY6E5R5MIU to a byte stream for the public key bytes? I am also curious about the tx id IAHIOLPF4274MPUQV4CRGTPL7QWKIHWTQHEXFX2XIGLTUE2EYTCQ.

TestNet v0.2.11 Release

That’s interesting, I had the sync time 0.0 seconds.

Sorry if this has been answered before, I just started algod and it’s running at a high CPU. Is this expected behavior? It almost looks like it’s CPU mining. My understanding from Silvio’s talk is that running this process should be very minimal on compute.

Bitcoin rpc compatibility layer

Yes those are the RPC calls that I’m talking about. Interestingly, there is a comprehensive test suite here that is independent of implementation.

Because there are so many bitcoin forks supporting their RPC format would be a huge win for compatibility. 100% coverage of wallet and node functionality would be safe but not mining would not be necessary for exchange integration.

It would be extremely useful if algorand implemented a bitcoin RPC compatibility layer. This will help very much with exchange listing, you will be listed on more exchanges more quickly in this way. This does not need 100% coverage and should be fairly straightforward. I can be more precise if you…