Get Ethereum anonymity set

Find how to get this dataset, then add code to programmatically generate it on the fly

Found some inspo here: https://www.trmlabs.com/post/classifying-one-million-ethereum-addresses
There is this link to a google BigQuery dataset: https://bigquery.cloud.google.com/dataset/bigquery-public-data:ethereum_blockchain
But it doesn't seem to work

Here is another source: https://github.com/blockchain-etl/public-datasets?tab=readme-ov-filehttps://github.com/blockchain-etl/public-datasets?tab=readme-ov-file
Links to another Google BigQuery dataset: https://console.cloud.google.com/marketplace/product/ethereum/crypto-ethereum-blockchain
This one seems to work. Under the crypto_ethereum you can find the balances table, where you can use this SQL to get the top 10M addresses:
SELECT * FROM `bigquery-public-data.crypto_ethereum.balances` ORDER BY eth_balance DESC LIMIT 10000000

10M winds up being ~600MB, which you can add to your drive (without paid api access) and then download.

Here is another option: https://github.com/blockchain-etl/ethereum-etl
Not sure if you can easily get top-N addresses tho

Not going to add the programmatic step


Bump module version to v2

Resolves #50. When this repo cut a v2 release, it accidentally "broke" the conventions for go modules in v2.
I think this is all that is necessary to fix the issue.
See https://blog.golang.org/v2-go-modules for more details.

From my understanding:

Make directory: github.com/bradleyfalzon/ghinstallation/v2
Copy  .go files from github.com/bradleyfalzon/ghinstallation/  to github.com/bradleyfalzon/ghinstallation/v2
Undo the changes I've made from last tag to v2 tag
Ensure github.com/bradleyfalzon/ghinstallation/go.mod refers to module github.com/bradleyfalzon/ghinstallation
Ensure github.com/bradleyfalzon/ghinstallation/v2/go.mod refers to module github.com/bradleyfalzon/ghinstallation/v2
Update the README.md about how to fetch v2.

This allows everyone using github.com/bradleyfalzon/ghinstallation to be using v1 and everyone that wants to upgrade to v2 makes it an explicit command by changing import paths. Simple go get will continue to use v1 on updates etc.

If you want to continue supporting both v1 and v2, then what you described is correct. It's up to you if you want to support both, as it can be a bit awkward. Large projects like go-github will often just bump the gomod version without much issue without keeping the old vn-1 directories.
I can amend this PR to include the "updated" install instructions in the readme.

@bradleyfalzon , i'm thinking who not release 1.2.0 instead of 2.0.x? i don't see break changes with recent commits. and 2.0.x has not been consumed by anybody due to the golang v2 issue.

2.0 was because of jwt
On Thu, 13 May 2021 at 1:07 pm, Nick Tan @.***> wrote:

@bradleyfalzon https://github.com/bradleyfalzon , i'm thinking who not
release 1.2.0 instead of 2.0.x? i don't see break changes with recent
commits. and 2.0.x has not been consumed by anybody due to the golang v2
issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bradleyfalzon/ghinstallation/pull/51#issuecomment-840268951,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN74UKKYXSWMMOKUQZGPO3TNNCP5ANCNFSM44WHQUXA
.

--
Bradley Falzon
@.***

If there was no breaking change to this module's API, I think its generally accepted that the change shouldn't require a major version bump. There are some additional thoughts in the go v2 module post.
Perhaps the 2.x line could be retracted or otherwise abandoned (until a new release changes this modules api in a breaking fashion?

@bradleyfalzon did you still want to take a look at this, create a new 1.x release, or would you prefer an approach where a v2 directory is created where both versions are maintained at the same time?

Hey @bradleyfalzon, anything we can do/help with to speed this up?

Hey @wlynch, do you mind taking a look at this PR as well?

LGTM. Approving to fix go get installation. Following the go-github model seems fine, and it should be easy enough to move to a separate v2 folder later if we want.

Verified this is now fixed for go get<EMAIL_ADDRESS>

Thanks a lot @wlynch and all others involved in this.


installDevTools is not a function

Hi,
I am using React-Native 0.18 and get the error:
installDevTools is not a function.
What am I doing wrong?

try installDevTools.default

Related to #15

Closed by #15


[ENH] Python packaging

Closes #1
This PR moves things around a little bit to create a bare bones Python package setup (i.e., so it is installable with python setup.py install). I also added the skeleton for testing and continuous integration with TravisCI! We just need to turn that on.

@rmarkello - you're the man! Thanks for the all this. That looks awesome.


Automate processes

Is your feature request related to a problem? Please describe.
Automate scraping, downloading, and extracting.
Describe the solution you'd like
Can we reuse existing management commands and just setup cron jobs?
https://github.com/Code4PuertoRico/contratospr-api/tree/master/contratospr/contracts/management/commands
Can we wrap up this process into an artifact report? What was created, updated, etc?

@smendez were you able to take a look at this since the last time we talked (obv, it's okay if you didn't)? I have a bit of downtime and might be able to spike on it.


feat: Settings Controller UI, fixes #3

add settings UI
add gitignore file
add popover for settings button item

@chashmeetsingh Thank you. Let's move to a similar commit policy like at other FOSSASIA projects. Please open issues first and match PRs to issues. Cheers.

Sorry, you did that, but please add the issue number into the description as well.

Sure, will do from now on.
Thanks!


Apply the "new" label to every new issue without labels in rust-lang/rust

The release team would like to get a label new added to every new issue in rust-lang/rust. The label doesn't need to be applied to PRs that have labels already.

Btw having a bug and a feature request issue templates has helped both guide the reporter to giving valuable information and auto-labeling the issue bug or feature request.

I saw that now new issues have the needs-triage label. Is it sufficient? Can we close this issue?

Yes, I think this can be closed.

Closing this because I got 3 thumbs up on zulip.
If anybody feels like this is still needed, let me know and we can open it again


Update to use new optparse-applicative

Helps with building with many other packages which use newer versions (or have dependencies which do), one specific example being hasql-postgres.

I've messed around with Travis after your PR a little, and I just can't fix it. This library needs an update of the Criterion dependency, which unfortunately I won't have any time to do any time soon.

I was messing around with trying to update that as well, don't have a lot of time but I might take a swing at that as well and make another PR.

BTW, some major updates to the "hasql" ecosystem are coming and the new versions are likely to be using "criterion" directly.

Righto. Took a crack and I'm unsure I'd be able to reasonably update criterion-plus and preserve functionality. Good to hear about the updates!


Fix typo

As per title, this PR fixes a typo in one of the framework assertions (potision -> position).
I've also added a space between a couple of words and the open bracket next to them, as it is more proper 👍
Please keep up the awesome work!! 💪💪💪

Thanks, @zntfdr!!


Add support for parallelism flag

This allows setting the -parallelism flag in terraform.Options. Includes a handy test.

@yorinasub17 we ended up working on this for part of this week's Ticket Jam. I didn't file an issue in the end.

Tests passed. Reviewed live during TicketJam. Merging now!

@robmorgan https://github.com/gruntwork-io/terratest/releases/tag/v0.28.9


/admin/users should show when a user has spam tracks

Closing for now, as spam accounts aren't a current issue.