WHAT
changes the big query data set to the public crypto-stellar.crypto_stellar_2 one instead of the hubble-261722 internal one.
also adds directions for connecting locally.
WHY
originally the internal data set was selected because it updated quicker than the public one. But for hubble 2.0 the public and internal datasets update at the same rate (slack convo). The advantages of using the public data set is that any developer (including external devs) who wants to contribute can get started quicker, w/o having to go through the process of copying over the public data set first.
WHAT changes the big query data set to the public
crypto-stellar.crypto_stellar_2
one instead of thehubble-261722
internal one.also adds directions for connecting locally.
WHY originally the internal data set was selected because it updated quicker than the public one. But for hubble 2.0 the public and internal datasets update at the same rate (slack convo). The advantages of using the public data set is that any developer (including external devs) who wants to contribute can get started quicker, w/o having to go through the process of copying over the public data set first.